Bug#989922: thunderbird: testing: NS_ERROR_NET_INADEQUATE_SECURITY?
Package: thunderbird Version: 1:78.11.0-1 Followup-For: Bug #989922 Hello, same issue here, I use a plugin to get my mails from MS Exchange OWA, but totally impossible at the moment due to NS_ERROR_NET_INADEQUATE_SECURITY. I now updated to version 89 from experimental but that one has the same problem. Best regards, Henry -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thunderbird depends on: ii debianutils 4.11.2 ii fontconfig 2.13.1-4.2 ii libatk1.0-0 2.36.0-2 ii libbotan-2-172.17.3+dfsg-2 ii libbz2-1.0 1.0.8-4 ii libc62.31-12 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libffi7 3.3-6 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libicu67 67.1-6 ii libjson-c5 0.15-2 ii libnspr4 2:4.29-1 ii libnss3 2:3.61-1 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-1 ii libx11-6 2:1.7.1-1 ii libx11-xcb1 2:1.7.1-1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxext6 2:1.3.3-1.1 ii libxrender1 1:0.9.10-1 ii psmisc 23.4-2 ii x11-utils7.7+5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages thunderbird recommends: ii hunspell-de-at [hunspell-dictionary] 20161207-9 ii hunspell-de-ch [hunspell-dictionary] 20161207-9 ii hunspell-de-de [hunspell-dictionary] 20161207-9 ii hunspell-en-us [hunspell-dictionary] 1:2019.10.06-1 Versions of packages thunderbird suggests: ii apparmor 2.13.6-10 ii fonts-lyx 2.3.6-1 ii libgssapi-krb5-2 1.18.3-5 ii libgtk2.0-0 2.24.33-2
Bug#909243: gnome-shell segfaults on start in libmutter-3
Hi Simon, the last one was incomplete, I got traces of xwayland and gnome shell this time. Regards, Henry Am Donnerstag, den 20.09.2018, 13:37 +0200 schrieb Henry Schwanbeck: > Hi Simon, > > thanks for your answer. I attached what I think is the backtrace you > requested and the syslog of a complete gdm session. > > > Regards, > > Henry > > > Am Donnerstag, den 20.09.2018, 11:48 +0100 schrieb Simon McVittie: > > Control: tags -1 + moreinfo > > > > On Thu, 20 Sep 2018 at 10:30:14 +0200, Henry Schwanbeck wrote: > > > after upgrading packages today, gnome-shell would not start > > > anymore > > > on wayland. > > > > Are you able to get a backtrace from this crash? Because you're > > using > > systemd, the easiest way is probably: > > > > * install the systemd-coredump package > > * reproduce the crash > > * run "coredumpctl gdb" (which might need to be run as root) > > * use the "bt" command as described in > > https://wiki.debian.org/HowToGetABacktrace#Running_gdb > > > > For the most useful backtrace, please install -dbgsym packages for > > relevant packages (libmutter-3-0, gnome-shell, libglib2.0-0) > > as described here: > > > > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols > > > > The messages in the systemd journal or syslog immediately before > > "Application 'org.gnome.Shell.desktop' killed by signal 11" are > > also > > likely to be useful information. > > > > Thanks, > > smcv root@telesto:/home/henry# coredumpctl debug --debugger=gdb gnome-shell PID: 7703 (gnome-shell) UID: 1000 (henry) GID: 1000 (henry) Signal: 11 (SEGV) Timestamp: Thu 2018-09-20 13:52:25 CEST (2min 12s ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-1000.slice/session-25.scope Unit: session-25.scope Slice: user-1000.slice Session: 25 Owner UID: 1000 (henry) Boot ID: 14074530d2a94bc7bf791eefe5a0eec1 Machine ID: db1f5df9f1684b819a86094c453c1730 Hostname: telesto Storage: /var/lib/systemd/coredump/core.gnome-shell.1000.14074530d2a94bc7bf791eefe5a0eec1.7703.153744434500.lz4 Message: Process 7703 (gnome-shell) of user 1000 dumped core. Stack trace of thread 7703: #0 0x7f0460f48050 meta_logical_monitor_get_layout (libmutter-3.so.0) #1 0x7f0460fd27d4 send_xdg_output_events (libmutter-3.so.0) #2 0x7f045f359fce ffi_call_unix64 (libffi.so.6) #3 0x7f045f35993f ffi_call (libffi.so.6) #4 0x7f045bdb7b2d wl_closure_invoke (libwayland-server.so.0) #5 0x7f045bdb45a9 wl_client_connection_data (libwayland-server.so.0) #6 0x7f045bdb5b72 wl_event_loop_dispatch (libwayland-server.so.0) #7 0x7f0460fb77b7 wayland_event_source_dispatch (libmutter-3.so.0) #8 0x7f0461e7ec3e g_main_dispatch (libglib-2.0.so.0) #9 0x7f0461e7eed8 g_main_context_iterate (libglib-2.0.so.0) #10 0x7f0461e7f1d2 g_main_loop_run (libglib-2.0.so.0) #11 0x7f0460fb89c6 meta_xwayland_start (libmutter-3.so.0) #12 0x7f0460fb7e04 meta_wayland_init (libmutter-3.so.0) #13 0x7f0460f8952e meta_init (libmutter-3.so.0) #14 0x55a43de4d528 main (gnome-shell) #15 0x7f0460d1fb17 __libc_start_main (libc.so.6) #16 0x55a43de4d8da _start (gnome-shell) Stack trace of thread 7706: #0 0x7f0460dea739 __GI___poll (libc.so.6) #1 0x7f0461e7ee46 g_main_context_poll (libglib-2.0.so.0) #2 0x7f0461e7f1d2 g_main_loop_run (libglib-2.0.so.0) #3 0x7f04620717b6 gdbus_shared_thread_func (libgio-2.0.so.0) #4 0x7f0461ea7135 g_thread_proxy (libglib-2.0.so.0) #5 0x7f0460ec1f2a start_thread (libpthread.so.0) #6 0x7f0460df4edf __clone (libc.so.6) Stack trace of thread 7708: #0 0x7f0460dea739 __GI___poll (libc.so.6) #1 0x7f0461e7ee46 g_main_context_poll (libglib-2.0.so.0) #2 0x7f0461e7ef6c g_main_context_iteration (libglib-2.0.so.0) #3 0x7f0454379fdd n/a (libdconfsettings.so) #4 0x7f0461ea7135 g_thread_proxy (libglib-2.0.so.0) #5 0x7f0460ec1f2a start_thread (libpthread.so.0) #6 0x7f0460df4edf __clone (libc.so.6) Stack trace of th
Bug#909243: gnome-shell segfaults on start in libmutter-3
Hi Simon, thanks for your answer. I attached what I think is the backtrace you requested and the syslog of a complete gdm session. Regards, Henry Am Donnerstag, den 20.09.2018, 11:48 +0100 schrieb Simon McVittie: > Control: tags -1 + moreinfo > > On Thu, 20 Sep 2018 at 10:30:14 +0200, Henry Schwanbeck wrote: > > after upgrading packages today, gnome-shell would not start anymore > > on wayland. > > Are you able to get a backtrace from this crash? Because you're using > systemd, the easiest way is probably: > > * install the systemd-coredump package > * reproduce the crash > * run "coredumpctl gdb" (which might need to be run as root) > * use the "bt" command as described in > https://wiki.debian.org/HowToGetABacktrace#Running_gdb > > For the most useful backtrace, please install -dbgsym packages for > relevant packages (libmutter-3-0, gnome-shell, libglib2.0-0) > as described here: > https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols > > The messages in the systemd journal or syslog immediately before > "Application 'org.gnome.Shell.desktop' killed by signal 11" are also > likely to be useful information. > > Thanks, > smcv henry@telesto:~$ sudo coredumpctl gdb PID: 3512 (Xwayland) UID: 1000 (henry) GID: 1000 (henry) Signal: 6 (ABRT) Timestamp: Thu 2018-09-20 13:22:34 CEST (56s ago) Command Line: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 Executable: /usr/bin/Xwayland Control Group: /user.slice/user-1000.slice/session-16.scope Unit: session-16.scope Slice: user-1000.slice Session: 16 Owner UID: 1000 (henry) Boot ID: 14074530d2a94bc7bf791eefe5a0eec1 Machine ID: db1f5df9f1684b819a86094c453c1730 Hostname: telesto Storage: /var/lib/systemd/coredump/core.Xwayland.1000.14074530d2a94bc7bf791eefe5a0eec1.3512.153744255400.lz4 Message: Process 3512 (Xwayland) of user 1000 dumped core. Stack trace of thread 3512: #0 0x7f1b6cc4af3b __GI_raise (libc.so.6) #1 0x7f1b6cc4c2f1 __GI_abort (libc.so.6) #2 0x55a94f42b30a OsAbort (Xwayland) #3 0x55a94f430e13 AbortServer (Xwayland) #4 0x55a94f431c79 FatalError (Xwayland) #5 0x55a94f2c846c xwl_log_handler (Xwayland) #6 0x7f1b6e11221a wl_abort (libwayland-client.so.0) #7 0x7f1b6e10e075 wl_proxy_marshal_array_constructor_versioned (libwayland-client.so.0) #8 0x7f1b6e10e2da wl_proxy_marshal_constructor (libwayland-client.so.0) #9 0x7f1b6e10f355 wl_display_sync (libwayland-client.so.0) #10 0x55a94f2c896c xwl_screen_init (Xwayland) #11 0x55a94f3f2c17 AddScreen (Xwayland) #12 0x55a94f2ca3bc InitOutput (Xwayland) #13 0x55a94f3f675f dix_main (Xwayland) #14 0x7f1b6cc37b17 __libc_start_main (libc.so.6) #15 0x55a94f2c818a _start (Xwayland) GNU gdb (Debian 8.1-4) 8.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/Xwayland...Reading symbols from /usr/lib/debug/.build-id/b0/5eff2ea3c555f3a53cada3613925b052be1363.debug...done. done. [New LWP 3512] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -d'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: Datei oder Verzeichnis nicht gefunden. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7f1b6cc4c2f1 in __GI_abort () at abort.c:79 #2 0x55a94f42b30a in OsAbort () at ../../../../os/utils.c:1350 #3 0x55a94f430e13 in AbortServer () at ../../../../os/log.c:877 #4 0x55a94
Bug#909243: gnome-shell segfaults on start in libmutter-3
Package: gnome-shell Version: 3.30.0-1 Severity: important Dear Maintainer, after upgrading packages today, gnome-shell would not start anymore on wayland. I had to disable Wayland and start a gdm3 session on X server to use my machine. Seems to be very much like https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=92 I do have a hybrid machine intel/nvidia (HP ZBook Studio G3 [T7V83ES#ABH]). But the nvidia chip is set to disables in EFI. Best regards, Henry Schwanbeck Syslog: Sep 20 09:54:29 telesto gnome-session[1665]: gnome-session-binary[1665]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 20 09:54:29 telesto gnome-session-binary[1665]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 20 09:54:29 telesto org.gnome.Shell.desktop[1697]: (EE) Sep 20 09:54:29 telesto org.gnome.Shell.desktop[1697]: Fatal server error: Sep 20 09:54:29 telesto org.gnome.Shell.desktop[1697]: (EE) Error sending request: Broken pipe Sep 20 09:54:29 telesto kernel: [ 43.356488] show_signal_msg: 21 callbacks suppressed Sep 20 09:54:29 telesto kernel: [ 43.356490] gnome-shell[1697]: segfault at 1c ip 7f026fc5d050 sp 7ffc50b25248 error 4 in libmutter-3.so.0.0.0[7f026fc46000+c4000] Sep 20 09:54:29 telesto kernel: [ 43.356494] Code: 00 c3 0f 1f 84 00 00 00 00 00 f3 0f 10 47 38 c3 66 2e 0f 1f 84 00 00 00 00 00 8b 47 3c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 47 1c 48 8b 57 24 c3 0f 1f 80 00 00 00 00 48 8b 47 48 c3 66 Sep 20 09:54:29 telesto org.gnome.Shell.desktop[1697]: (EE) Sep 20 09:54:29 telesto gnome-session-binary[1665]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 20 09:54:29 telesto gdm3: GdmDisplay: display lasted 2,045401 seconds APT history.log: Start-Date: 2018-09-20 09:52:17 Commandline: apt full-upgrade Requested-By: henry (1000) Install: gir1.2-mutter-3:amd64 (3.30.0-1, automatic), libmutter-3-0:amd64 (3.30.0-1, automatic) Upgrade: python-tdb:amd64 (1.3.15-4, 1.3.16-1), libpangoft2-1.0-0:amd64 (1.42.4-1, 1.42.4-3), libpangoft2-1.0-0:i386 (1.42.4-1, 1.42.4-3), libxdot4:amd64 (2.40.1-3, 2.40.1-4), gvfs-backends:amd64 (1.36.2-1, 1.38.0-2), gvfs-bin:amd64 (1.36.2-1, 1.38.0-2), libgirepository-1.0-1:amd64 (1.56.1-1, 1.58.0-1), gir1.2-atk-1.0:amd64 (2.28.1-1, 2.30.0-1), libcgraph6:amd64 (2.40.1-3, 2.40.1-4), at-spi2-core:amd64 (2.28.0-3, 2.30.0-2), libgupnp-1.0-4:amd64 (1.0.2-2, 1.0.3-1), python3-keyring:amd64 (15.0.0-1, 15.1.0-1), ext3grep:amd64 (0.10.2-3+b1, 0.10.2-4), python3-pyatspi:amd64 (2.26.0+dfsg-3, 2.30.0+dfsg-1), gir1.2-pango-1.0:amd64 (1.42.4-1, 1.42.4-3), gir1.2-freedesktop:amd64 (1.56.1-1, 1.58.0-1), libatk-adaptor:amd64 (2.26.2-1, 2.30.0-1), liblab-gamut1:amd64 (2.40.1-3, 2.40.1-4), mutter-common:amd64 (3.28.3-2, 3.30.0-1), gnome-tweaks:amd64 (3.28.1-1, 3.30.0-1), scalpel:amd64 (1.60-4, 1.60-5), libpangoxft-1.0-0:amd64 (1.42.4-1, 1.42.4-3), gnome- music:amd64 (3.28.2.1-2, 3.30.0-2), libpango1.0-dev:amd64 (1.42.4-1, 1.42.4-3), libuv1:amd64 (1.23.0-1, 1.23.0-2), libglib2.0-dev-bin:amd64 (2.56.1-2, 2.58.0-4), gvfs-libs:amd64 (1.36.2-1, 1.38.0-2), gvfs-fuse:amd64 (1.36.2-1, 1.38.0-2), libatk1.0-0:amd64 (2.28.1-1, 2.30.0-1), libpangocairo-1.0-0:amd64 (1.42.4-1, 1.42.4-3), libpangocairo-1.0-0:i386 (1.42.4-1, 1.42.4-3), gir1.2-glib-2.0:amd64 (1.56.1-1, 1.58.0-1), libatspi2.0-0:amd64 (2.28.0-3, 2.30.0-2), youtube-dl:amd64 (2018.06.18-1.1, 2018.09.10-1), libglib2.0-bin:amd64 (2.56.1-2, 2.58.0-4), gnome-shell-common:amd64 (3.28.3-1, 3.30.0-1), libcdt5:amd64 (2.40.1-3, 2.40.1-4), libglib2.0-dev:amd64 (2.56.1-2, 2.58.0-4), libpathplan4:amd64 (2.40.1-3, 2.40.1-4), libwebkit2gtk-4.0-37:amd64 (2.20.5-1, 2.22.0-2), libsdl1.2debian:amd64 (1.2.15+dfsg2-1, 1.2.15+dfsg2-2), gir1.2-atspi-2.0:amd64 (2.28.0-3, 2.30.0-2), python-keyring:amd64 (15.0.0-1, 15.1.0-1), libgvpr2:amd64 (2.40.1-3, 2.40.1-4), libsdl2-2.0-0:amd64 (2.0.8+dfsg1-1+b1, 2.0.8+dfsg1-2), libtdb1:amd64 (1.3.15-4, 1.3.16-1), gnome- shell-extensions:amd64 (3.29.3+really3.28.1-1, 3.30.0-1), libglib2.0-data:amd64 (2.56.1-2, 2.58.0-4), gvfs:amd64 (1.36.2-1, 1.38.0-2), libatk-bridge2.0-0:amd64 (2.26.2-1, 2.30.0-1), gir1.2-webkit2-4.0:amd64 (2.20.5-1, 2.22.0-2), gvfs- common:amd64 (1.36.2-1, 1.38.0-2), gnome-shell:amd64 (3.28.3-1, 3.30.0-1), libatk1.0-data:amd64 (2.28.1-1, 2.30.0-1), libgvc6:amd64 (2.40.1-3, 2.40.1-4), python3-flask:amd64 (1.0.2-1, 1.0.2-2), libpango-1.0-0:amd64 (1.42.4-1, 1.42.4-3), libpango-1.0-0:i386 (1.42.4-1, 1.42.4-3), libjavascriptcoregtk-4.0-18:amd64 (2.20.5-1, 2.22.0-2), libatk1.0-dev:amd64 (2.28.1-1, 2.30.0-1), graphviz:amd64 (2.40.1-3, 2.40.1-4), gvfs-daemons:amd64 (1.36.2-1, 1.38.0-2), libglib2.0-0:amd64 (2.56.1-2, 2.58.0-4), libglib2.0-0:i386 (2.56.1-2, 2.58.0-4), gir1.2-javascriptcoregtk-4.0:amd64 (2.20.5-1, 2.22.0-2), mutter:amd64 (3.28.3-2, 3.30.0-1) End-Date: 2018-09-20 09:52:42 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (900, 'testing'), (499, 'stable-updates'), (499, '
Bug#630802: xserver-xorg-core: xserver searches for AIGLX libs in wrong directory
Package: xserver-xorg-core Version: 2:1.10.2-1+b1 Severity: important Tags: wheezy Hello, I did a full-upgrade totay to install all updates since 2011-06-15. There is 2011-06-17 11:31:36 upgrade xserver-xorg-core 2:1.10.2-1 2:1.10.2-1+b1 in the dpkg log. After a reboot, I am now unable to use DRI, since the xserver is searching for some libs at the wrong place. Looking at Xorg.log, it says: [ 876.507] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux- gnu/dri/i965_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/i965_dri.so: cannot open shared object file: No such file or directory) [ 876.507] (EE) AIGLX: reverting to software rendering [ 876.507] (II) AIGLX: Screen 0 is not DRI capable [ 876.507] (EE) AIGLX error: dlopen of /usr/lib/x86_64-linux- gnu/dri/swrast_dri.so failed (/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: No such file or directory) [ 876.507] (EE) GLX: could not load software renderer [ 876.507] (II) GLX: no usable GL providers found for screen 0 while dpkg --search i965_dri.so says: ia32-libs: /usr/lib32/dri/i965_dri.so libgl1-mesa-dri: /usr/lib/dri/i965_dri.so and dpkg --search swrast_dri.so says: libgl1-mesa-dri: /usr/lib/dri/swrast_dri.so ia32-libs: /usr/lib32/dri/swrast_dri.so I dont't know where the x86_64-linux-gnu is coming from, so I blame xserver- xorg-core :) Regards, Henry -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 May 12 10:45 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1956672 Jun 14 14:37 /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 /etc/modprobe.d/radeon-kms.conf: options radeon modeset=1 Kernel version (/proc/version): --- Linux version 2.6.39.1-x64 (root@hyperion) (gcc version 4.5.3 (Debian 4.5.3-1) ) #1 SMP Wed Jun 8 23:52:59 CEST 2011 Xorg X server log files on system: -- -rw-r--r-- 1 root root 35743 Jun 17 14:48 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [ 7731.361] X.Org X Server 1.10.2 Release Date: 2011-05-28 [ 7731.361] X Protocol Version 11, Revision 0 [ 7731.361] Build Operating System: Linux 2.6.32-5-amd64 x86_64 Debian [ 7731.361] Current Operating System: Linux hyperion 2.6.39.1-x64 #1 SMP Wed Jun 8 23:52:59 CEST 2011 x86_64 [ 7731.361] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.39.1-x64 root=/dev/mapper/hyperion-root ro quiet [ 7731.361] Build Date: 14 June 2011 12:32:34PM [ 7731.361] xorg-server 2:1.10.2-1+b1 (amd64 Builddd Daemon (barber) buildd_amd64-bar...@buildd.debian.org) [ 7731.361] Current version of pixman: 0.21.8 [ 7731.361]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 7731.361] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 7731.362] (==) Log file: /var/log/Xorg.0.log, Time: Fri Jun 17 14:48:19 2011 [ 7731.362] (==) Using system config directory /usr/share/X11/xorg.conf.d [ 7731.362] (==) No Layout section. Using the first Screen section. [ 7731.362] (==) No screen section available. Using defaults. [ 7731.362] (**) |--Screen Default Screen Section (0) [ 7731.362] (**) | |--Monitor default monitor [ 7731.363] (==) No monitor specified for screen Default Screen Section. Using a default monitor configuration. [ 7731.363] (==) Automatically adding devices [ 7731.363] (==) Automatically enabling devices [ 7731.363] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. [ 7731.363]Entry deleted from font path. [ 7731.363] (==) 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, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins [ 7731.363] (==) ModulePath set to /usr/lib/xorg/modules [ 7731.363] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 7731.363] (II) Loader magic: 0x7d7b20 [ 7731.363] (II) Module ABI versions: [ 7731.363]X.Org ANSI C Emulation: 0.4 [ 7731.363]X.Org Video Driver: 10.0 [ 7731.363]X.Org XInput driver : 12.2 [ 7731.363]X.Org Server Extension : 5.0 [
