Bug#868350: xserver-xorg-core: X server segfaults on startup after upgrade to xserver-xorg-core 2:1.16.4-1+deb8u1

2017-07-14 Thread Joe Dennigan
Package: xserver-xorg-core
Version: 2:1.16.4-1+deb8u1
Severity: important

Dear Maintainer,

* What led up to the situation?
  Upgraded xserver-xorg-core (and xserver-common) from 2:1.16.4-1 to
  2:1.16.4-1+deb8u1

* What exactly did you do (or not do) that was effective (or
  ineffective)?
  Downgraded xserver-xorg-core (xserver-common) from 2:1.16.4-1+deb8u1
  back to 2:1.16.4-1
  
* What was the outcome of this action?
  I now have a working X server again.

As reportbug has appended the latest Xorg.0.log from a working
installation, here are the last few lines (the only relevant
differences that I can see) from the log of the last crashed X session
before I downgraded the packages:

[46.392] (II) intel(0): Allocated new frame buffer 1920x1848 stride 7680, 
tiled
[52.301] (EE) 
[52.301] (EE) Backtrace:
[52.332] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x5648f4d11b46]
[52.332] (EE) 1: /usr/bin/X (0x5648f4b59000+0x1bcd29) [0x5648f4d15d29]
[52.333] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7ffb5974+0x350e0) 
[0x7ffb597750e0]
[52.333] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7ffb5974+0x91d8a) 
[0x7ffb597d1d8a]
[52.333] (EE) 4: /usr/bin/X (0x5648f4b59000+0xc1a38) [0x5648f4c1aa38]
[52.333] (EE) 5: /lib/x86_64-linux-gnu/libdbus-1.so.3 
(dbus_connection_dispatch+0x3f1) [0x7ffb5b83a1d1]
[52.333] (EE) 6: /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7ffb5b82a000+0x10425) [0x7ffb5b83a425]
[52.333] (EE) 7: /usr/bin/X (0x5648f4b59000+0xbb619) [0x5648f4c14619]
[52.333] (EE) 8: /usr/bin/X (WakeupHandler+0x6b) [0x5648f4bb57fb]
[52.333] (EE) 9: /usr/bin/X (WaitForSomething+0x1c3) [0x5648f4d0edf3]
[52.333] (EE) 10: /usr/bin/X (0x5648f4b59000+0x57931) [0x5648f4bb0931]
[52.333] (EE) 11: /usr/bin/X (0x5648f4b59000+0x5bcb6) [0x5648f4bb4cb6]
[52.333] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7ffb59761b45]
[52.333] (EE) 13: /usr/bin/X (0x5648f4b59000+0x4602e) [0x5648f4b9f02e]
[52.333] (EE) 
[52.333] (EE) Segmentation fault at address 0x0
[52.334] (EE) 
Fatal server error:
[52.334] (EE) Caught signal 11 (Segmentation fault). Server aborting
[52.334] (EE) 
[52.334] (EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
[52.334] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[52.334] (EE) 
[52.334] (II) AIGLX: Suspending AIGLX clients for VT switch
[52.875] (EE) systemd-logind: ReleaseControl failed: Did not receive a 
reply. Possible causes include: the remote application did not send a reply, 
the message bus security policy blocked the reply, the reply timeout expired, 
or the network connection was broken.
[52.875] (EE) Server terminated with error (1). Closing log file.

Do you want/need a bug report for the complementary package
xserver-common?  All the details are the same, only the name changes.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jan  5  2017 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 2401376 Feb 11  2015 /usr/bin/Xorg

Diversions concerning libGL are in place

diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/libGL.so.1 to /usr/lib/mesa-diverted/libGL.so.1 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/libGLESv2.so.2 to /usr/lib/mesa-diverted/libGLESv2.so.2 
by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/libGLESv1_CM.so.1.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/x86_64-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 

Bug#577110: program crashes with bzr: ERROR: socket.error: (4, 'Interrupted system call')

2010-04-09 Thread Joe Dennigan
Package: bzr
Version: 2.1.1-1
Severity: important
Tags: sid

Trying to get the latest emacs source with:

bzr branch http://bzr.savannah.gnu.org/r/emacs/trunk

bzr crashes with:

bzr: ERROR: socket.error: (4, 'Interrupted system call')

This has happened three time this afternoon.  First was about 3 minutes
into the dowload, the last after more than an hour.  Traceback attached.


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bzr depends on:
ii  libc6   2.10.2-6 Embedded GNU C Library: Shared lib
ii  python  2.5.4-9  An interactive high-level object-o
ii  python-central  0.6.14+nmu2  register and build utility for Pyt
ii  python-configobj4.7.2+ds-1   simple but powerful config file re
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages bzr recommends:
ii  bzrtools  2.1.0-2Collection of tools for bzr
ii  ca-certificates   20090814   Common CA certificates
ii  python-paramiko   1.7.6-2Make ssh v2 connections with Pytho

Versions of packages bzr suggests:
ii  bzr-doc  2.1.1-1 easy to use distributed version co
ii  bzr-gtk  0.98.0-1provides graphical interfaces to B
pn  bzr-svn  none  (no description available)
ii  python-kerberos  1.1+svn4895-1+b1A GSSAPI interface module for Pyth
ii  python-pycurl7.19.0-3+b1 Python bindings to libcurl
ii  xdg-utils1.0.2+cvs20100307-1 desktop integration utilities from

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#576810: perlindex: Perlindex cron job never finishes

2010-04-07 Thread Joe Dennigan
Package: perlindex
Version: 1.605-2
Severity: important
Tags: sid

When started by cron, perlindex will run until killed - on one occasion it
ran for 11.5 hours - using ~90-95% CPU.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages perlindex depends on:
ii  debconf [debconf-2.0] 1.5.30 Debian configuration management sy
ii  libterm-readkey-perl  2.30-4 A perl module for simple terminal 
ii  libtext-english-perl  1.605-2Perl module implementing the Porte
ii  perl  5.10.1-11  Larry Wall's Practical Extraction 

Versions of packages perlindex recommends:
ii  libio-stringy-perl2.110-4Perl modules for IO from scalars a

perlindex suggests no packages.

-- debconf information:
* perlindex/removeindexonpurge: true



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#571178: xserver-xorg-video-intel: Intel 855GM GPU hangs after 3+ hours only when second monitor connected

2010-02-25 Thread Joe Dennigan

Since the initial bug report I've managed to login via ssh on a couple
of subsequent crashes and get dumps the hung GPU.  Do you want them?

Joe


-- 
ton everybody in my house had strep this winter except for me
AB  Congrats.
ton yeah I think I played the part of strepto ton
ton as carriers don't need to be sick
ton try as I might I couldn't get my coworkers sick
ton finally they asked if I could please stop licking them
  -- Afterburner's quotes file



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#525123: xserver-xorg-video-intel on Intel 82852/855GM: display corrupted

2009-04-22 Thread Joe Dennigan
Package: xserver-xorg-video-intel
Version:  2:2.7.0-1

On starting X the display is scrambled.  To correct this, I have to edit
xorg.conf to disable EXA and enable UXA.  X then starts normally but
lines of text in apps like abiword and the emacs splash screen are
corrupted into pixel high lines of dots.  Reverting xorg.conf to the
original state and restarting X now fixes all problems.  That is, on the
third startup all works normally until the next system reboot.

This problem does not arise when using the vesa driver.

Complete xorg.conf:
Section Device
Identifier  Configured Video Device
#Option CheckLid  True
#Option XAANoOffscreenPixmaps Enable
#Option AddARGBGLXVisuals Enable
#Option LinearAlloc 6144
Option AccelMethodEXA
#Option AccelMethod   UXA
Option TripleBuffer   True
Option MigrationHeuristic greedy
Option ExaNoComposite True
Option  monitor-LVDS  TFT
#Option monitor-VGA   CRT
Driver  intel
#Driver vesa
#Option BusType   PCI
BusID   PCI:0:2:0
EndSection

System details:

jd...@not-working:~$ uname -a
Linux not-working 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686 
GNU/Linux

jd...@not-working:~$ dpkg -s libc6 | grep ^Version
Version: 2.9-7

jd...@not-working:~$ lspci
Hardware:00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller (rev 02)
00:00.1 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller (rev 02)
00:00.3 System peripheral: Intel Corporation 82852/82855 GM/GME/PM/GMV 
Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated 
Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics 
Device (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) 
USB UHCI Controller #3 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI 
Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corporation 82801DBM (ICH4-M) LPC Interface Bridge 
(rev 03)
00:1f.1 IDE interface: Intel Corporation 82801DBM (ICH4-M) IDE Controller (rev 
03)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus 
Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM 
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)
00:1f.6 Modem: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 
Modem Controller (rev 03)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
01:05.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller 
(rev 02)
02:00.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)



Joe



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#525129: reportbug crashes every time

2009-04-22 Thread Joe Dennigan
Package: reportbug
Version: 4.1

Reportbug crashes every time I try to use it.  The latest session went
as follows:

jd...@not-working:~$ reportbug
Welcome to reportbug! Since it looks like this is the first time you have used
reportbug, we are configuring its behavior. These settings will be saved to the
file /home/jdenn/.reportbugrc, which you will be free to edit further.
Please choose the default operating mode for reportbug.

1 noviceOffer simple prompts, bypassing technical questions.

2 standard  Offer more extensive prompts, including asking about things that a
moderately sophisticated user would be expected to know about 
Debian.

3 advanced  Like standard, but assumes you know a bit more about Debian, 
including
incoming.

4 expertBypass most handholding measures and preliminary triage routines. 
This
mode should not be used by people unfamiliar with Debian's policies
and operating procedures.

Select mode: [novice] 2
Please choose the default interface for reportbug.

1 gtk2  A graphical (GTK+) user interface

2 text  A text-oriented console user interface

Select interface: 2
Will reportbug often have direct Internet access? (You should answer yes to this
question unless you know what you are doing and plan to check whether duplicate
reports have been filed via some other channel.) [Y|n|q|?]? Y
What real name should be used for sending bug reports?
[JpD] Joe Dennigan
Which of your email addresses should be used when sending bug reports? (Note 
that
this address will be visible in the bug tracking system, so you may want to use 
a
webmail address or another address with good spam filtering capabilities.)
[ergotma...@googlemail.com] 
Traceback (most recent call last):
  File /usr/bin/reportbug, line 1831, in module
main()
  File /usr/bin/reportbug, line 848, in main
return iface.user_interface()
  File /usr/bin/reportbug, line 955, in user_interface
offer_configuration(self.options)
  File /usr/bin/reportbug, line 470, in offer_configuration
default=(options.email or def_email), force_prompt=True)
  File /usr/lib/pymodules/python2.5/reportbug/ui/text_ui.py, line 245, in 
get_string
response = unicode(response, charset, 'replace')
TypeError: decoding Unicode is not supported
jd...@not-working:~$

The same error occurs when selecting the gtk2 interface.

System details:
jd...@not-working:~$ uname -a
Linux not-working 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686 
GNU/Linux
jd...@not-working:~$ dpkg -s libc6 | grep ^Version
Version: 2.9-7
jd...@not-working:~$ dpkg -s python | grep ^Version
Version: 2.5.4-2





Joe



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org