[Desktop-packages] [Bug 1849228] Re: [snap] Chinese Supplementary Unicode characters not rendered at all (but working in .deb-Google Chrome)

2019-10-21 Thread Christian Niemeyer
As said: http://www.i18nguy.com/unicode/supplementary-test.html
the page works fine on Ubuntu 18.04.3 LTS with chromium-browser via apt (.deb)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849228

Title:
  [snap] Chinese Supplementary Unicode characters not rendered at all
  (but working in .deb-Google Chrome)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi!

  This is my first bug report in a very very long time, so please bear
  with me, if the report is not that professional.

  I did a fresh install of Ubuntu 19.10 just now and I installed
  (nearly) every single fonts-* package and chromium-browser snap. And
  firefox (deb), falkon (deb) and Google Chrome (deb)

  Firefox and Falkon and Google Chrome do render all Chinese characters 
correctly and instantly:
  http://www.i18nguy.com/unicode/supplementary-test.html

  Works fine with:
  Firefox
  Falkon
  Google Chrome
  Midori
  Arora Browser (package: arora, pretty broken but it works on the test page)
  surf (package: surf, suckless browser)
  netsurf-gtk

  (all tested just now on 19.10 eoan!)

  
  Chromium Browser via snap does *NOT* display the characters at all: 
http://www.i18nguy.com/unicode/supplementary-test.html

  
  I went back to my install of Ubuntu 18.04.3 LTS with the chromium-browser via 
apt as a usual .DEB package. The test page on Ubuntu bionic does work 
absolutely fine and 100% correct. Not even much fonts installed.

  So I'm 100% sure this is snap related for Ubuntu 19.10.

  Expected: Chromium Browser (snap) should display the characters on
  http://www.i18nguy.com/unicode/supplementary-test.html

  What happens: You can't get Chromium browser (snap) in 19.10 to
  display the characters, no matter what.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849228/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1849228] [NEW] [snap] Chinese Supplementary Unicode characters not rendered at all (but working in .deb-Google Chrome)

2019-10-21 Thread Christian Niemeyer
Public bug reported:

Hi!

This is my first bug report in a very very long time, so please bear
with me, if the report is not that professional.

I did a fresh install of Ubuntu 19.10 just now and I installed (nearly)
every single fonts-* package and chromium-browser snap. And firefox
(deb), falkon (deb) and Google Chrome (deb)

Firefox and Falkon and Google Chrome do render all Chinese characters correctly 
and instantly:
http://www.i18nguy.com/unicode/supplementary-test.html

Works fine with:
Firefox
Falkon
Google Chrome
Midori
Arora Browser (package: arora, pretty broken but it works on the test page)
surf (package: surf, suckless browser)
netsurf-gtk

(all tested just now on 19.10 eoan!)


Chromium Browser via snap does *NOT* display the characters at all: 
http://www.i18nguy.com/unicode/supplementary-test.html


I went back to my install of Ubuntu 18.04.3 LTS with the chromium-browser via 
apt as a usual .DEB package. The test page on Ubuntu bionic does work 
absolutely fine and 100% correct. Not even much fonts installed.

So I'm 100% sure this is snap related for Ubuntu 19.10.

Expected: Chromium Browser (snap) should display the characters on
http://www.i18nguy.com/unicode/supplementary-test.html

What happens: You can't get Chromium browser (snap) in 19.10 to display
the characters, no matter what.

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: chromium-browser snap

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849228

Title:
  [snap] Chinese Supplementary Unicode characters not rendered at all
  (but working in .deb-Google Chrome)

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  Hi!

  This is my first bug report in a very very long time, so please bear
  with me, if the report is not that professional.

  I did a fresh install of Ubuntu 19.10 just now and I installed
  (nearly) every single fonts-* package and chromium-browser snap. And
  firefox (deb), falkon (deb) and Google Chrome (deb)

  Firefox and Falkon and Google Chrome do render all Chinese characters 
correctly and instantly:
  http://www.i18nguy.com/unicode/supplementary-test.html

  Works fine with:
  Firefox
  Falkon
  Google Chrome
  Midori
  Arora Browser (package: arora, pretty broken but it works on the test page)
  surf (package: surf, suckless browser)
  netsurf-gtk

  (all tested just now on 19.10 eoan!)

  
  Chromium Browser via snap does *NOT* display the characters at all: 
http://www.i18nguy.com/unicode/supplementary-test.html

  
  I went back to my install of Ubuntu 18.04.3 LTS with the chromium-browser via 
apt as a usual .DEB package. The test page on Ubuntu bionic does work 
absolutely fine and 100% correct. Not even much fonts installed.

  So I'm 100% sure this is snap related for Ubuntu 19.10.

  Expected: Chromium Browser (snap) should display the characters on
  http://www.i18nguy.com/unicode/supplementary-test.html

  What happens: You can't get Chromium browser (snap) in 19.10 to
  display the characters, no matter what.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849228/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)

2018-03-20 Thread Christian Niemeyer
** Summary changed:

- [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf
+ [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf (intel mesa driver)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with GLX backtrace if Composite
  Disabled in xorg.conf (intel mesa driver)

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) 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,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
  [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf

2018-03-10 Thread Christian Niemeyer
Maybe this is i915/i965 intel driver related. If someone with an in
intel IGP could reproduce this. I have xserver-xorg-video-intel
installed by the way. With not mentioning "intel" explicitly as the
driver in xorg.conf doesn't it automatically uses modesetting or
glamorgl?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with GLX backtrace if Composite
  Disabled in xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) 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,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
  [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf

2018-03-10 Thread Christian Niemeyer
Just had the idea to unload "glx" and see if I can Disable Composite
without crashing Xorg / startx / xinit.

It works!


Here's my xorg.conf:

Section "Module"
Disable "glx"
EndSection

Section "Extensions"
Option "Composite" "0"
EndSection


I'll put my resulting Xorg.0.log as an attachment. 

However logically this prevents me from getting DRI (which I need), while 
glxinfo saying:
"LIBGL_DEBUG=verbose glxinfo 
name of display: :0
Error: couldn't find RGB GLX visual or fbconfig"


Interesting though that Xorg no longer crashes with Composite being disabled 
when I disable the glx module at the same time.


 

** Summary changed:

- [bionic] startx / xinit crashes with Composite Disabled in xorg.conf
+ [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in 
xorg.conf

** Attachment added: "Xorg.0.log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5075590/+files/Xorg.0.log.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with GLX backtrace if Composite
  Disabled in xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) 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,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If 

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-09 Thread Christian Niemeyer
I suspect libglx0 (transition from libgl1-mesa-glx to libglx0)

Because now we have:
/usr/lib/x86_64-linux-gnu/libGLX.so.0.0.0 (from libglx0 in bionic, new with 
bionic)

instead of:
/usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0 (from libgl1-mesa-glx in artful, 
the packages is a transitional dummy package in bionic)


The Xorg.0.log backtrace is showing:

[   210.258] (EE) Backtrace:
[   210.258] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x5645df72591d]
[   210.258] (EE) 1: /usr/lib/xorg/Xorg (0x5645df56d000+0x1bc6b9) 
[0x5645df7296b9]
[   210.258] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f00a84af000+0x12890) [0x7f00a84c1890]
[   210.258] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) 
[0x7f00a80fce97]
[   210.258] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) 
[0x7f00a80fe801]
[   210.258] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f00a80be000+0x3039a) 
[0x7f00a80ee39a]
[   210.258] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f00a80be000+0x30412) 
[0x7f00a80ee412]
[   210.258] (EE) 7: /usr/lib/xorg/Xorg (0x5645df56d000+0x3ec17) 
[0x5645df5abc17]
[   210.258] (EE) 8: /usr/lib/xorg/Xorg (0x5645df56d000+0xe26df) 
[0x5645df64f6df]
[   210.258] (EE) 9: /usr/lib/xorg/modules/extensions/libglx.so 
(0x7f00a6473000+0x288d7) [0x7f00a649b8d7]
[   210.258] (EE) 10: /usr/lib/xorg/modules/extensions/libglx.so 
(0x7f00a6473000+0x2f851) [0x7f00a64a2851]
[   210.258] (EE) 11: /usr/lib/xorg/modules/extensions/libglx.so 
(0x7f00a6473000+0x27315) [0x7f00a649a315]
[   210.259] (EE) 12: /usr/lib/xorg/Xorg (InitExtensions+0x3d) [0x5645df63308d]
[   210.259] (EE) 13: /usr/lib/xorg/Xorg (0x5645df56d000+0x56d1f) 
[0x5645df5c3d1f]
[   210.259] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xe7) 
[0x7f00a80dfb97]
[   210.259] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x5645df5adbba]
[   210.259] (EE) 
[   210.259] (EE) 
Fatal server error:


However that libglx.so shown in the error log is part of xserver-xorg-
core.


But I suspect it has to do with the changed to vendor neutral libglx
(libglx0, libglvnd0, etc.) That would explain why it is happening with
Bionic and no other versions before for me.


Can someone reproduce this? In your Display Manager switch to a VT (or 
deinstall display manager temporarily) and modify/create a /etc/X11/xorg.conf 
file with

Section "Extensions"
Option "Composite" "Disable"
EndSection


And sudo service lightdm/gdm3 stop and then try to start the Xserver/Xsession 
with startx or xinit.



As this is the first version of Ubuntu which seems to have this problem for

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command 

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Now I remove +s bit from /usr/bin/X, /usr/bin/xinit, /usr/bin/startx,
/usr/bin/Xorg and tried to run Valgrind with it. Honestly I have no idea
about debugging. I just know that valgrind and strace can be somehow use
for it. Hope this helps!

output of valgrind -v startx 1> valgrind_v_startx.txt 2>&1

** Attachment added: "valgrind_v_startx.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5072779/+files/valgrind_v_startx.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) 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,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)

[Desktop-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
tried with "strace startx"

** Attachment added: "strace startx"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5072778/+files/strace_startx_001.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1754296

Title:
  [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

Status in xorg package in Ubuntu:
  New

Bug description:
  [New bug filed with ubuntu-bug/apport. However there was nothing to
  file against in /var/crashes]

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco. Disabling the Composite extension prevents
  tearing in (some) games and sometimes is an additional performance
  boost.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [ 35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [ 35.781] X Protocol Version 11, Revision 0
  [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [ 35.787] Build Date: 22 February 2018 08:04:42PM
  [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [ 35.789] Current version of pixman: 0.34.0
  [ 35.792] Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar 7 22:43:35 2018
  [ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [ 35.803] (==) No Layout section. Using the first Screen section.
  [ 35.803] (==) No screen section available. Using defaults.
  [ 35.803] (**) |-->Screen "Default Screen Section" (0)
  [ 35.803] (**) | |-->Monitor ""
  [ 35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
  [ 35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [ 35.804] (==) Automatically adding devices
  [ 35.804] (==) Automatically enabling devices
  [ 35.804] (==) Automatically adding GPU devices
  [ 35.804] (==) Automatically binding GPU devices
  [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
  [ 35.809] Entry deleted from font path.
  [ 35.822] (==) 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,
   built-ins
  [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [ 35.822] (**) Extension "Composite" is disabled
  [ 35.822] (II) The server relies on udev to provide the list of input devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [ 35.822] (II) Loader magic: 0x55cfd2964020
  [ 35.822] (II) Module ABI versions:
  [ 35.822] X.Org ANSI C Emulation: 0.4
  [ 35.822] X.Org Video Driver: 23.0
  [ 35.822] X.Org XInput driver : 24.1
  [ 35.822] X.Org Server Extension : 10.0
  [ 35.824] (++) using VT number 1

  [ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
  [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [ 35.832] (--) PCI: (0:0:2:1) 

[Desktop-packages] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Ok, thanks!

However there was nothing in my /var/crash folder. Nonetheless I tried
to file a new bug with ubuntu-bug xorg. It added lots of system
information and logs.

here it is: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1754177

Title:
  [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [35.781] X Protocol Version 11, Revision 0
  [35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [35.783] Current Operating System: Linux bdcomputerclub 
4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [35.787] Build Date: 22 February 2018  08:04:42PM
  [35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [35.789] Current version of pixman: 0.34.0
  [35.792]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [35.792] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
  [35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [35.803] (==) No Layout section.  Using the first Screen section.
  [35.803] (==) No screen section available. Using defaults.
  [35.803] (**) |-->Screen "Default Screen Section" (0)
  [35.803] (**) |   |-->Monitor ""
  [35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
  [35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [35.804] (==) Automatically adding devices
  [35.804] (==) Automatically enabling devices
  [35.804] (==) Automatically adding GPU devices
  [35.804] (==) Automatically binding GPU devices
  [35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [35.809]  Entry deleted from font path.
  [35.822] (==) 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,
   built-ins
  [35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [35.822] (**) Extension "Composite" is disabled
  [35.822] (II) The server relies on udev to provide the list of input 
devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [35.822] (II) Loader magic: 0x55cfd2964020
  [35.822] (II) Module ABI versions:
  [35.822]  X.Org ANSI C Emulation: 0.4
  [35.822]  X.Org Video Driver: 23.0
  [35.822]  X.Org XInput driver : 24.1
  [35.822]  X.Org Server Extension : 10.0
  [35.824] (++) using VT number 1

  [35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 
paused 0
  [35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [35.832] (--) PCI: (0:0:2:1) 

[Desktop-packages] [Bug 1754296] [NEW] [bionic] startx / xinit crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Public bug reported:

[New bug filed with ubuntu-bug/apport. However there was nothing to file
against in /var/crashes]

For certain games I disable the Composite extension in my
/etc/X11/xorg.conf when using a non-composited window manager like
openbox, fluxbox or marco. Disabling the Composite extension prevents
tearing in (some) games and sometimes is an additional performance
boost.

This worked flawlessly in all previous Ubuntu versions including 17.10
(artful).

This stopped working with Ubuntu 18.04 (bionic). I tested with the
mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and
bionic. Xserver will crash with "Option "Composite" "0/False/Disable"

When I comment out the specific line in the Extensions section (that
means *enabling* Composite) it works again with this xorg.conf. I can
also do other stuff like disabling DRI3 or AIGLX. No crashes in these
cases.

My xorg.conf:
Section "Device"
Identifier "Intel GMA45" ##just a trivial name as Identifier
Driver "intel"
EndSection

Section "Extensions"
Option "Composite" "0"
EndSection

It has a backtrace and caughts signal 6.

My Xorg.0.log:
[ 35.779]
X.Org X Server 1.19.6
Release Date: 2017-12-20
[ 35.781] X Protocol Version 11, Revision 0
[ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
[ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
[ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
[ 35.787] Build Date: 22 February 2018 08:04:42PM
[ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
[ 35.789] Current version of pixman: 0.34.0
[ 35.792] Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
[ 35.792] Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: 
Wed Mar 7 22:43:35 2018
[ 35.801] (==) Using config file: "/etc/X11/xorg.conf"
[ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 35.803] (==) No Layout section. Using the first Screen section.
[ 35.803] (==) No screen section available. Using defaults.
[ 35.803] (**) |-->Screen "Default Screen Section" (0)
[ 35.803] (**) | |-->Monitor ""
[ 35.804] (==) No device specified for screen "Default Screen Section".
 Using the first device section listed.
[ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset"
[ 35.804] (==) No monitor specified for screen "Default Screen Section".
 Using a default monitor configuration.
[ 35.804] (==) Automatically adding devices
[ 35.804] (==) Automatically enabling devices
[ 35.804] (==) Automatically adding GPU devices
[ 35.804] (==) Automatically binding GPU devices
[ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f
[ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 35.809] Entry deleted from font path.
[ 35.822] (==) 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,
 built-ins
[ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 35.822] (**) Extension "Composite" is disabled
[ 35.822] (II) The server relies on udev to provide the list of input devices.
 If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 35.822] (II) Loader magic: 0x55cfd2964020
[ 35.822] (II) Module ABI versions:
[ 35.822] X.Org ANSI C Emulation: 0.4
[ 35.822] X.Org Video Driver: 23.0
[ 35.822] X.Org XInput driver : 24.1
[ 35.822] X.Org Server Extension : 10.0
[ 35.824] (++) using VT number 1

[ 35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
[ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
[ 35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 
0xd340/1048576
[ 35.833] (II) LoadModule: "glx"
[ 35.836] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 35.850] (II) Module glx: vendor="X.Org Foundation"
[ 35.850] compiled for 1.19.6, module version = 1.0.0
[ 35.850] ABI class: X.Org Server Extension, version 10.0
[ 35.850] (II) LoadModule: "intel"
[ 35.850] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 35.856] (II) Module intel: vendor="X.Org Foundation"
[ 35.856] compiled for 1.19.5, module version = 2.99.917
[ 35.856] Module class: X.Org Video Driver
[ 35.856] ABI class: X.Org Video Driver, version 23.0
[ 35.856] (II) 

[Desktop-packages] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-08 Thread Christian Niemeyer
Tried with rebooting and restarting, nothing in /var/crash

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1754177

Title:
  [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [35.781] X Protocol Version 11, Revision 0
  [35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [35.783] Current Operating System: Linux bdcomputerclub 
4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [35.787] Build Date: 22 February 2018  08:04:42PM
  [35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [35.789] Current version of pixman: 0.34.0
  [35.792]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [35.792] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
  [35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [35.803] (==) No Layout section.  Using the first Screen section.
  [35.803] (==) No screen section available. Using defaults.
  [35.803] (**) |-->Screen "Default Screen Section" (0)
  [35.803] (**) |   |-->Monitor ""
  [35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
  [35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [35.804] (==) Automatically adding devices
  [35.804] (==) Automatically enabling devices
  [35.804] (==) Automatically adding GPU devices
  [35.804] (==) Automatically binding GPU devices
  [35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [35.809]  Entry deleted from font path.
  [35.822] (==) 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,
   built-ins
  [35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [35.822] (**) Extension "Composite" is disabled
  [35.822] (II) The server relies on udev to provide the list of input 
devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [35.822] (II) Loader magic: 0x55cfd2964020
  [35.822] (II) Module ABI versions:
  [35.822]  X.Org ANSI C Emulation: 0.4
  [35.822]  X.Org Video Driver: 23.0
  [35.822]  X.Org XInput driver : 24.1
  [35.822]  X.Org Server Extension : 10.0
  [35.824] (++) using VT number 1

  [35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 
paused 0
  [35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 
0xd340/1048576
  [35.833] (II) LoadModule: "glx"
  [35.836] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [35.850] (II) Module 

[Desktop-packages] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-07 Thread Christian Niemeyer
Another interesting thing with this xserver-xorg-core is that it ignores
Option "AIGLX" "Off" in the ServerFlags section and initializes AIGLX.
This also hasn't happened before bionic.

And the crashing (see the Xorg.0.log in my previous post) seems to
happen right where normally some AIGLX initialization is logged.

Here's a Xorg.0.log with Composite *not* disabled, but trying to disable
AIGLX. Seems like it gets ignored and the crash with trying to startx
with Composite Disable happens right before the following:


[87.708] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[87.708] (II) AIGLX: enabled GLX_ARB_create_context
[87.708] (II) AIGLX: enabled GLX_ARB_create_context_profile
[87.708] (II) AIGLX: enabled GLX_EXT_create_context_es{,2}_profile
[87.708] (II) AIGLX: enabled GLX_INTEL_swap_event
[87.708] (II) AIGLX: enabled GLX_SGI_swap_control
[87.708] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[87.708] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[87.708] (II) AIGLX: enabled GLX_EXT_fbconfig_packed_float
[87.708] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[87.708] (II) AIGLX: Loaded and initialized i965


My xorg.conf:

Section "ServerFlags"
Option "AIGLX" "off"
EndSection


Section "Device"
Identifier "Intel GMA 450"
Driver "intel"
EndSection

Section "Extensions"
# Option "Composite" "0"
EndSection




** Attachment added: "Full Xorg.0.log when starting normally"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1754177/+attachment/5072490/+files/Xorg.0.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1754177

Title:
  [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

Status in xorg-server package in Ubuntu:
  New

Bug description:
  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco.

  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).

  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed
  and bionic. Xserver will crash with "Option "Composite"
  "0/False/Disable"

  When I comment out the specific line in the Extensions section (that
  means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.

  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection

  Section "Extensions"
  Option "Composite" "0"
  EndSection

  It has a backtrace and caughts signal 6.

  My Xorg.0.log:
  [35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [35.781] X Protocol Version 11, Revision 0
  [35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [35.783] Current Operating System: Linux bdcomputerclub 
4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [35.787] Build Date: 22 February 2018  08:04:42PM
  [35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [35.789] Current version of pixman: 0.34.0
  [35.792]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [35.792] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
  [35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [35.803] (==) No Layout section.  Using the first Screen section.
  [35.803] (==) No screen section available. Using defaults.
  [35.803] (**) |-->Screen "Default Screen Section" (0)
  [35.803] (**) |   |-->Monitor ""
  [35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
  [35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [35.804] (==) Automatically adding devices
  [35.804] (==) Automatically enabling devices
  [35.804] (==) Automatically adding GPU devices
  [35.804] (==) Automatically binding GPU devices
  [35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [35.809] 

[Desktop-packages] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-07 Thread Christian Niemeyer
Here's my glxinfo output when Xserver is not crashing (started with
Composite *enabled*)

** Attachment added: "glxinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1754177/+attachment/5072328/+files/glxinfo.txt

** Description changed:

  For certain games I disable the Composite extension in my
  /etc/X11/xorg.conf when using a non-composited window manager like
  openbox, fluxbox or marco.
  
  This worked flawlessly in all previous Ubuntu versions including 17.10
  (artful).
  
  This stopped working with Ubuntu 18.04 (bionic). I tested with the
  mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and
  bionic. Xserver will crash with "Option "Composite" "0/False/Disable"
  
- When I comment out the line it works again with this xorg.conf. I can
+ When I comment out the specific line in the Extensions section (that
+ means *enabling* Composite) it works again with this xorg.conf. I can
  also do other stuff like disabling DRI3 or AIGLX. No crashes in these
  cases.
  
  My xorg.conf:
  Section "Device"
  Identifier "Intel GMA45" ##just a trivial name as Identifier
  Driver "intel"
  EndSection
  
  Section "Extensions"
  Option "Composite" "0"
  EndSection
  
  It has a backtrace and caughts signal 6.
  
  My Xorg.0.log:
  [35.779]
  X.Org X Server 1.19.6
  Release Date: 2017-12-20
  [35.781] X Protocol Version 11, Revision 0
  [35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  [35.783] Current Operating System: Linux bdcomputerclub 
4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
  [35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
  [35.787] Build Date: 22 February 2018  08:04:42PM
  [35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  [35.789] Current version of pixman: 0.34.0
  [35.792]  Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  [35.792] Markers: (--) probed, (**) from config file, (==) default 
setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
  [35.801] (==) Using config file: "/etc/X11/xorg.conf"
  [35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  [35.803] (==) No Layout section.  Using the first Screen section.
  [35.803] (==) No screen section available. Using defaults.
  [35.803] (**) |-->Screen "Default Screen Section" (0)
  [35.803] (**) |   |-->Monitor ""
  [35.804] (==) No device specified for screen "Default Screen Section".
   Using the first device section listed.
  [35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
  [35.804] (==) No monitor specified for screen "Default Screen Section".
   Using a default monitor configuration.
  [35.804] (==) Automatically adding devices
  [35.804] (==) Automatically enabling devices
  [35.804] (==) Automatically adding GPU devices
  [35.804] (==) Automatically binding GPU devices
  [35.804] (==) Max clients allowed: 256, resource mask: 0x1f
  [35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not 
exist.
  [35.809]  Entry deleted from font path.
  [35.822] (==) 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,
   built-ins
  [35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
  [35.822] (**) Extension "Composite" is disabled
  [35.822] (II) The server relies on udev to provide the list of input 
devices.
   If no devices become available, reconfigure udev or disable AutoAddDevices.
  [35.822] (II) Loader magic: 0x55cfd2964020
  [35.822] (II) Module ABI versions:
  [35.822]  X.Org ANSI C Emulation: 0.4
  [35.822]  X.Org Video Driver: 23.0
  [35.822]  X.Org XInput driver : 24.1
  [35.822]  X.Org Server Extension : 10.0
  [35.824] (++) using VT number 1
  
  [35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
  [35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
  [35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 
paused 0
  [35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
  [35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 
0xd340/1048576
  [35.833] (II) LoadModule: "glx"
  [35.836] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
  [35.850] (II) Module glx: vendor="X.Org Foundation"
  [

[Desktop-packages] [Bug 1754177] [NEW] [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

2018-03-07 Thread Christian Niemeyer
Public bug reported:

For certain games I disable the Composite extension in my
/etc/X11/xorg.conf when using a non-composited window manager like
openbox, fluxbox or marco.

This worked flawlessly in all previous Ubuntu versions including 17.10
(artful).

This stopped working with Ubuntu 18.04 (bionic). I tested with the
mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and
bionic. Xserver will crash with "Option "Composite" "0/False/Disable"

When I comment out the specific line in the Extensions section (that
means *enabling* Composite) it works again with this xorg.conf. I can
also do other stuff like disabling DRI3 or AIGLX. No crashes in these
cases.

My xorg.conf:
Section "Device"
Identifier "Intel GMA45" ##just a trivial name as Identifier
Driver "intel"
EndSection

Section "Extensions"
Option "Composite" "0"
EndSection

It has a backtrace and caughts signal 6.

My Xorg.0.log:
[35.779]
X.Org X Server 1.19.6
Release Date: 2017-12-20
[35.781] X Protocol Version 11, Revision 0
[35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
[35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic 
#201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64
[35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic 
root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash
[35.787] Build Date: 22 February 2018  08:04:42PM
[35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
[35.789] Current version of pixman: 0.34.0
[35.792]Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
[35.792] Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", 
Time: Wed Mar  7 22:43:35 2018
[35.801] (==) Using config file: "/etc/X11/xorg.conf"
[35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[35.803] (==) No Layout section.  Using the first Screen section.
[35.803] (==) No screen section available. Using defaults.
[35.803] (**) |-->Screen "Default Screen Section" (0)
[35.803] (**) |   |-->Monitor ""
[35.804] (==) No device specified for screen "Default Screen Section".
 Using the first device section listed.
[35.804] (**) |   |-->Device "Intel GMA45 Express Chipset"
[35.804] (==) No monitor specified for screen "Default Screen Section".
 Using a default monitor configuration.
[35.804] (==) Automatically adding devices
[35.804] (==) Automatically enabling devices
[35.804] (==) Automatically adding GPU devices
[35.804] (==) Automatically binding GPU devices
[35.804] (==) Max clients allowed: 256, resource mask: 0x1f
[35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[35.809]Entry deleted from font path.
[35.822] (==) 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,
 built-ins
[35.822] (==) ModulePath set to "/usr/lib/xorg/modules"
[35.822] (**) Extension "Composite" is disabled
[35.822] (II) The server relies on udev to provide the list of input 
devices.
 If no devices become available, reconfigure udev or disable AutoAddDevices.
[35.822] (II) Loader magic: 0x55cfd2964020
[35.822] (II) Module ABI versions:
[35.822]X.Org ANSI C Emulation: 0.4
[35.822]X.Org Video Driver: 23.0
[35.822]X.Org XInput driver : 24.1
[35.822]X.Org Server Extension : 10.0
[35.824] (++) using VT number 1

[35.827] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_32
[35.828] (II) xfree86: Adding drm device (/dev/dri/card0)
[35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 
0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 
0x/131072
[35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 
0xd340/1048576
[35.833] (II) LoadModule: "glx"
[35.836] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[35.850] (II) Module glx: vendor="X.Org Foundation"
[35.850]compiled for 1.19.6, module version = 1.0.0
[35.850]ABI class: X.Org Server Extension, version 10.0
[35.850] (II) LoadModule: "intel"
[35.850] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[35.856] (II) Module intel: vendor="X.Org Foundation"
[35.856]compiled for 1.19.5, module version = 2.99.917
[35.856]Module class: X.Org Video Driver
[35.856]ABI class: X.Org Video Driver, version 23.0
[35.856] (II) intel: 

[Desktop-packages] [Bug 992971] Re: libavformat53 Mismatching header version

2013-11-02 Thread Christian Niemeyer
October 2013, still there:

mplayer FOO.mp3 
MPlayer svn r34540 (Ubuntu), built with gcc-4.7 (C) 2000-2012 MPlayer Team
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.

Playing Foo.mp3.
libavformat version 53.21.1 (external)
Mismatching header version 53.19.0


ubuntu saucy 64bit


The audio plays ok. But why is this mismatching header problem not fixed for 
aged? Thanks in advance!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/992971

Title:
  libavformat53 Mismatching header version

Status in “libav” package in Ubuntu:
  Opinion
Status in “mplayer” package in Ubuntu:
  Confirmed

Bug description:
  Version details should be in the auto-loaded Apport file.

  $ mplayer blah_blah.mov
  MPlayer svn r34540 (Ubuntu), built with gcc-4.6 (C) 2000-2012 MPlayer Team

  Playing blah_blah.mov.
  libavformat version 53.21.0 (external)
  Mismatching header version 53.19.0
  libavformat file format detected.
  [snip]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libavformat53 4:0.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Tue May  1 20:24:45 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libav
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/992971/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-10-27 Thread Christian Niemeyer
Regardless of that one comment above. But it is really frustrating if
now the user's of ubuntu get blamed for not filing the correct bug. Dear
folks at Canonical, you have so much information in this one thread,
about how to reproduce this error. I'm not that experienced. So please,
could someone reproduce this error (take a machine without any wireless
capabilities) and then file the correct bug, if this bug report here is
not good enough for you.

It's pretty amazing that a bug that causes **filesystem errors** (if
minor or not minor) does not get fixed at all and now the users get
partly blamed for not filing the bug on the correct package? Hello? A
default installation causes filesystem errors, reproduceable. Would
someone please take those hints in this thread seriously? Like: install
on a machine with a wired connection on no wireless adapters. I can
reproduce this 100%.

My fix is (taken from this thread): console none in /etc/init
/ureadahead-other.conf OR uninstalling ureadahead at all.

And more important in /etc/init/umountfs adding the following lines in
the beginning of the file:

service networking stop

sleep 1

service networking start

sleep 1

service networking stop

sleep 1

killall dhclient

sleep 1


That worked for me. I don't know what package to file this bug against, because 
it seems that it happens out of certain hardware and interaction between 
different packages. I'm not blaming upstart at all. I just want this CRITICAL 
bug to be fixed. It is around since 12.04/12.10. That's amazing.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : 

[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-10-21 Thread Christian Niemeyer
It occurs that the problem did *not* exist after a recent clean install
of 13.10 (64bit Desktop CD) on a friend's notebook. While it still
happens on my desktop PC.

Differences:

On the notebook we used wireless (b43 out of the box) internet during
installation. Reboot into new system, login, shutdown is clean.

On my desktop I have no wireless card at all. I use wired connection
during installation. Reboot into new system, login, using system,
shutdown is unclean.

I haven't double-checked this though. But it maybe is a hint, that this
problem occurs on machines with no wireless possibilities.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10

2013-10-01 Thread Christian Niemeyer
This still happens in 13.10 (saucy). This time I installed the Beta-2 of
Lubuntu (thus using an lxsession). Reboot or shutdown fails everytime.
It hangs for around ten seconds, then it reboots and fsck shows deleted
orphaned inode.

Only helps to uninstall network-manager-*, nm-*, modemmanager,
ureadahead.

How come this hasn't been fixed yet? It is reproduceable all the time
for me. (My router is fine and network also. I had problems with my old
router and dnsmasq in 12.04 but no unclean shutdowns.)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1073433

Title:
  Ext4 corruption associated with shutdown of Ubuntu 12.10

Status in Upstart:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete
Status in “network-manager” package in Ubuntu:
  Triaged
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  1. Format and label a target Ext4 partion using Ubuntu 12.04
  2. Install 64bit 12.10 OS using that target without reformatting it
  3. Shut down 
  4. Boot an alternate copy of Ubuntu
  5. Restart selecting the newly installed OS
  6. Login then shutdown
  6. Boot an alternate copy of Ubuntu
  7.Fsck the newly installed OS allowing corrections to be made

  Each time the the newly installed OS is executed and then shutdown,
  even if execution only consists of logging on, a subsequent fsck will
  FAIL.

  I used Acronis True Image Home 2013 to create an image of the newly
  installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4
  filesystem corruption 100% of the time by restoring from the image,
  booting, logging on and shutting down.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: linux-image-3.5.0-17-generic 3.5.0-17.28
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  aguru  1871 F pulseaudio
   /dev/snd/controlC0:  aguru  1871 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Oct 30 22:24:54 2012
  HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer P5Q-E
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic 
root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.5.0-17-generic N/A
   linux-backports-modules-3.5.0-17-generic  N/A
   linux-firmware1.95
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5Q-E
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5Q-E
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1112496] Re: python-imaging broken in raring

2013-04-05 Thread Christian Niemeyer
Found a solution from https://bugs.launchpad.net/phatch/+bug/1156583 by
user KEIII about a broken symlink. Additionally python3-imaging is
*missing* from the depencies of the phatch package. (besides python-
imaging and python-imaging-compat)

1.) sudo apt-get install python3-imaging

2.) User KEIII wrote: It seems link to 
/usr/lib/python3/dist-packages/PIL/PngImagePlugin.py are broken or missing
If copy or make symlink it to /usr/share/phatch/phatch/lib phatch start 
correctly

I just did: sudo cp -ivr /usr/lib/python3/dist-packages/PIL/*
/usr/share/phatch/phatch/lib/ (press n for No twice!)

3.) it works!

I link this bug report to the other one of the phatch package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1112496

Title:
  python-imaging broken in raring

Status in “comix” package in Ubuntu:
  Invalid
Status in “gwibber” package in Ubuntu:
  Invalid
Status in “ocrfeeder” package in Ubuntu:
  Invalid
Status in “phatch” package in Ubuntu:
  Confirmed
Status in “python-imaging” package in Ubuntu:
  Fix Released
Status in “simple-image-reducer” package in Ubuntu:
  Invalid
Status in “wsjt” package in Ubuntu:
  Invalid
Status in “comix” source package in Raring:
  Invalid
Status in “gwibber” source package in Raring:
  Invalid
Status in “ocrfeeder” source package in Raring:
  Invalid
Status in “phatch” source package in Raring:
  Confirmed
Status in “python-imaging” source package in Raring:
  Fix Released
Status in “simple-image-reducer” source package in Raring:
  Invalid
Status in “wsjt” source package in Raring:
  Invalid

Bug description:
  python-imaging in raring doesn't include a PIL.pth to point python at
  the library, so attempts to import modules from the package fail with,
  eg:

  rachel@rarity:/etc$ python -m ImageMode  echo ok
  /usr/bin/python: No module named Image

  When the PIL.pth file is manually created, so python can find it, the
  Image module itself still fails to load:

  rachel@rarity:/etc$ python -m Image
  Traceback (most recent call last):
File /usr/lib/python2.7/runpy.py, line 162, in _run_module_as_main
  __main__, fname, loader, pkg_name)
File /usr/lib/python2.7/runpy.py, line 72, in _run_code
  exec code in run_globals
File /usr/lib/python2.7/dist-packages/PIL/Image.py, line 75, in module
  from . import ImageMode
  ValueError: Attempted relative import in non-package

  The ImageMode module that line seems to be trying to import, however,
  seems to import fine by itself:

  rachel@rarity:/etc$ python -m ImageMode  echo ok
  ok

  (I've confirmed that ImageMode comes from the same place, as if I
  remove PIL.pth again, the above line just returns the No module named
  ImageMode error)

  I've tried reinstalling python-imaging already. I note in any case the
  PIL.pth file is missing on the file list available at
  packages.ubuntu.com for raring.

  This is on Ubuntu Raring as updated from Ubuntu Quantal a few days
  ago:

  rachel@rarity:/etc$ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  rachel@rarity:/etc$ apt-cache policy python
  python:
Installed: 2.7.3-10ubuntu5
Candidate: 2.7.3-10ubuntu5
Version table:
   *** 2.7.3-10ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  rachel@rarity:/etc$ apt-cache policy python-imaging
  python-imaging:
Installed: 1.1.7+1.7.8-1ubuntu1
Candidate: 1.1.7+1.7.8-1ubuntu1
Version table:
   *** 1.1.7+1.7.8-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  Affects me as it affects building/packaging XBMC post-frodo for
  raring. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/comix/+bug/1112496/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1112496] Re: python-imaging broken in raring

2013-04-02 Thread Christian Niemeyer
Still affects me. Not fixed.

phatch
Traceback (most recent call last):
  File /usr/bin/phatch, line 16, in module
main(config_paths, app_file = __file__)
  File /usr/share/phatch/phatch/app.py, line 203, in main
from core.settings import create_settings
  File /usr/share/phatch/phatch/core/settings.py, line 23, in module
from pil import IMAGE_READ_EXTENSIONS
  File /usr/share/phatch/phatch/core/pil.py, line 39, in module
from lib import openImage
  File /usr/share/phatch/phatch/lib/openImage.py, line 25, in module
import thumbnail
  File /usr/share/phatch/phatch/lib/thumbnail.py, line 62, in module
import PngImagePlugin
ImportError: No module named PngImagePlugin

apt-cache policy python-imaging
python-imaging:
  Installed: 1.1.7+2.0.0-1
  Candidate: 1.1.7+2.0.0-1
  Version table:
 *** 1.1.7+2.0.0-1 0
500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status

apt-cache policy python-imaging-compat
python-imaging-compat:
  Installed: 1.1.7+2.0.0-1
  Candidate: 1.1.7+2.0.0-1
  Version table:
 *** 1.1.7+2.0.0-1 0
500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
100 /var/lib/dpkg/status

lsb_release -a
[...]
Description:Ubuntu Raring Ringtail (development branch)
Release:13.04
Codename:   raring

uname -rms
Linux 3.8.0-16-generic x86_64

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1112496

Title:
  python-imaging broken in raring

Status in “comix” package in Ubuntu:
  Invalid
Status in “gwibber” package in Ubuntu:
  Invalid
Status in “ocrfeeder” package in Ubuntu:
  Invalid
Status in “phatch” package in Ubuntu:
  Invalid
Status in “python-imaging” package in Ubuntu:
  Fix Released
Status in “simple-image-reducer” package in Ubuntu:
  Invalid
Status in “wsjt” package in Ubuntu:
  Invalid
Status in “comix” source package in Raring:
  Invalid
Status in “gwibber” source package in Raring:
  Invalid
Status in “ocrfeeder” source package in Raring:
  Invalid
Status in “phatch” source package in Raring:
  Invalid
Status in “python-imaging” source package in Raring:
  Fix Released
Status in “simple-image-reducer” source package in Raring:
  Invalid
Status in “wsjt” source package in Raring:
  Invalid

Bug description:
  python-imaging in raring doesn't include a PIL.pth to point python at
  the library, so attempts to import modules from the package fail with,
  eg:

  rachel@rarity:/etc$ python -m ImageMode  echo ok
  /usr/bin/python: No module named Image

  When the PIL.pth file is manually created, so python can find it, the
  Image module itself still fails to load:

  rachel@rarity:/etc$ python -m Image
  Traceback (most recent call last):
File /usr/lib/python2.7/runpy.py, line 162, in _run_module_as_main
  __main__, fname, loader, pkg_name)
File /usr/lib/python2.7/runpy.py, line 72, in _run_code
  exec code in run_globals
File /usr/lib/python2.7/dist-packages/PIL/Image.py, line 75, in module
  from . import ImageMode
  ValueError: Attempted relative import in non-package

  The ImageMode module that line seems to be trying to import, however,
  seems to import fine by itself:

  rachel@rarity:/etc$ python -m ImageMode  echo ok
  ok

  (I've confirmed that ImageMode comes from the same place, as if I
  remove PIL.pth again, the above line just returns the No module named
  ImageMode error)

  I've tried reinstalling python-imaging already. I note in any case the
  PIL.pth file is missing on the file list available at
  packages.ubuntu.com for raring.

  This is on Ubuntu Raring as updated from Ubuntu Quantal a few days
  ago:

  rachel@rarity:/etc$ lsb_release -rd
  Description:  Ubuntu Raring Ringtail (development branch)
  Release:  13.04
  rachel@rarity:/etc$ apt-cache policy python
  python:
Installed: 2.7.3-10ubuntu5
Candidate: 2.7.3-10ubuntu5
Version table:
   *** 2.7.3-10ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status
  rachel@rarity:/etc$ apt-cache policy python-imaging
  python-imaging:
Installed: 1.1.7+1.7.8-1ubuntu1
Candidate: 1.1.7+1.7.8-1ubuntu1
Version table:
   *** 1.1.7+1.7.8-1ubuntu1 0
  500 http://gb.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  Affects me as it affects building/packaging XBMC post-frodo for
  raring. :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/comix/+bug/1112496/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot

2012-10-17 Thread Christian Niemeyer
*** This bug is a duplicate of bug 1061639 ***
https://bugs.launchpad.net/bugs/1061639

I'm not sure, if this isn't perhaps a bigger issue. This is definitely
NOT FIXED. But most users won't notice it (until it's too late and the
filesystem becomes more and more inconsistent). Comment posted on:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639

Sorry for the additionally comment here. But I really want to raise
awareness of this issue, because –at least for my installations- it is
so critically bad.

It has something to do with services (init-scripts), /etc/init.d/,
networking. But it's not only dns-masq, because I added an additional
killall -9 dnsmasqd; sync; sync; sleep 3 in /etc/init.d/umountfs, and
it says no process: dnsmasq, and it makes no difference. Filesystem
never gets unmounted cleanly.

Thanks and happy bug fixing!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1058987

Title:
  In Quantal, the root filesystem is not cleanly unmounted at shutdown
  or reboot

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  Ever since some update in the Quantal pre-releases, having dnsmasq-
  base installed will cause the root filesystem to not be properly
  unmounted on shutdown and reboot. In case the Plymouth splash screen
  is disabled, the message 'mount: / is busy' will be shown, but
  otherwise the user will not even be aware of this problem.

  After rebooting, the root filesystem needs recovery, as shown in
  dmesg:

  kevin@vbox-xubuntu-quantal:~$ dmesg | grep EXT4
  [1.022746] EXT4-fs (sda2): INFO: recovery required on readonly filesystem
  [1.022750] EXT4-fs (sda2): write access will be enabled during recovery
  [1.248294] EXT4-fs (sda2): recovery complete
  [1.248661] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  [1.456315] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  Yet again, the user will not be aware of this until it is too late.
  The only way to avoid this from happening (or at least what I've
  found) is running 'sudo apt-get purge dnsmasq-base'. Sadly, this also
  removes network-manager and network-manager-gnome, so it isn't really
  a viable solution.

  Another problem that might be related is that having an active
  connection with the Network Manager prior to shutting down or
  rebooting, will cause the process to hang for a few seconds, after
  which the message about / being busy is shown. Stopping the network
  service (sudo service networking stop) will solve the hanging, but not
  the unclean unmount. So far, only purging dnsmasq-base seems to do
  that, which obviously also solves the other problem, as Network
  Manager will then also be removed.

  Although I haven't experienced it yet, this could cause potential data
  loss; especially for users without a seperate /home partition.

  
  ProblemType: Bug
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 12:49:24 2012
  DistroRelease: Ubuntu 12.10
  Package: dnsmasq-base 2.63-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  SourcePackage: dnsmasq
  Tags:  quantal
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot

2012-10-17 Thread Christian Niemeyer
*** This bug is a duplicate of bug 1061639 ***
https://bugs.launchpad.net/bugs/1061639

FINALLY worked! :) (for the first time ever with quantal!)

I tried about 2 hours shutting down manually. Stopping, starting init
scripts, networking etc. I found this only way, and it was to be done
exactly in this order. Contra: I have not yet figured the problem out
exactly. I think many commands are not mandatory. Now it would be the
time to sort them out.

I wrote a pseudo log file. Out of my bash history. I'm not an expert,
but I really hope you get the idea:

(NOTE: DONE BEFORE: sudo apt-get remove --purge modemmanager
COMMENT: TESTED IT WITH REBOOT, DIDN'T DO ANYTHING GOOD OR BAD ITSELF)

BOOT, FSCK ERROR MESSAGE (EXIT 1, ERRORS RESOLVED), BOOT CONTINUING...

LIGTHDM

CTRL+ALT+F2

LOGIN TERMINAL

sudo service lightdm stop

sudo service dbus stop
COMMENT: THAT DID HANG FOR A WHILE, APPROX 5 SECONDS / THE SAME IF YOU STOP 
NETWORKING BEFORE DBUS, IT HANGS, KILLS DBUS, -- THIS ORDER IS BETTER

sudo service dbus start

sudo service dbus stop
COMMENT: NOW BOTH STARTS AND STOPS VERY FAST AND CLEAN

sudo service networking stop
COMMENT: NETWORKING STOPPED FAST AND CLEANLY

sudo service networking start
COMMENT: THEORY: FOR CLEAN SHUTDOWN WE HAVE START/STOP YET AGAIN

sudo service networking stop

sudo service rsyslog stop

sudo modprobe -r forcedeth bnep rfcomm bluetooth
COMMENT: SOMETIMES FORCEDETH MODULES BRINGS EVERYONE IN TROUBLE. WHAT ABOUT 
FORCEDETH? AND I GOT SOME MESSAGES WITH BLUETOOTH MODULE, – WHICH I DON'T HAVE 
BTW –, SO UNLOADING IT FOR A CLEAN STATE, –– BUT DIDN'T HELPED WHEN ONLY DOING 
THIS

sync

sudo init 1
COMMENT: TAKES A WHILE, AND KILLING ALL REMAINING PROCESSES SAYS IT FAILED

COMMENT: NOW WE'RE ROOT, SO NO SUDO. BUT I ADD IT FOR NO CONFUSION

sudo service udev stop
COMMENT: STILL THERE STILL GOING (I THINK THAT'S CORRECT). AND STOPS FAST AND 
CLEAN.

sudo /etc/init.d/networking start
COMMENT: AGAIN STARTING, BUT ONLY INIT.D, NOT USING SERVICE. IT SEEMS THAT 
STARTING/STOPPING THOSE SCRIPTS SOLVES OUR PROBLEM

COMMENT: ...AND NOW STOPPING POSSIBLY ALL OF THEM

sudo /etc/init.d/networking stop

sudo /etc/init.d/network-manager stop

sudo /etc/init.d/network-interface-security stop

sudo  /etc/init.d/network-interface-container stop

sudo /etc/init.d/network-interface stop

COMMENT: ALL STOPS FAST AND CLEAN, PROMPTS

COMMENT: NEARLY DONE! NOW WE MAKE SURE, THAT FSCK IS FORCED TO RUN. IF
ERRORS IT WILL SAY WAS NOT CLEANY UMOUNTED. RETURN/EXIT VALUE: [1],
PRINTED ON SCREEN. IF NO ERROR IT WILL SAY WAS MOUNTED X TIMES, CHECK
FORCED. RETURN VALUE: 0. NO EXIT/ERROR MESSAGE PRINTED, CLEAN;
CONTINUING BOOT

sudo tune2fs -c 1 /dev/sda1 #max mount counts to 1

sudo tune2fs -C 100 /dev/sda1 #make believe, it was mounted 100 times
already, will trigger fsck on reboot

COMMENT: DOING TESTING

sudo lsof /

sudo fuser /

COMMENT: AHA! LSOF STILL SHOW 2 (TWO!) PROCESSES NTPD RUNNING. BETTER
KILL THEM. HOWEVER, I DON'T THINK THEY ARE THE PROBLEM. BECAUSE IF I
ONLY KILL THEM, WITHOUT ALL THE PROCEDURE EXACTLY(!) IN ORDER ABOVE,
THEN IT DOESN'T HELP

sudo killall -15 ntpd

COMMENT: CHECKING

sudo ps -e

sudo lsmod

COMMENT: LOOKS GOOD!

sudo sync; sync; sync; sudo init 6


***REBOOOT***

AND...

== CLEAN FILESYSTEM! :-)

WORKED!



APPENDIX 01:


LSOF / (quite before the end, but before ntpd killing)

sudo lsof /
COMMANDPID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
init 1 root  cwdDIR8,1 4096 2 /
init 1 root  rtdDIR8,1 4096 2 /
init 1 root  txtREG8,1   163144  5938 /sbin/init
init 1 root  memREG8,152152  5660 
/lib/x86_64-linux-gnu/libnss_files-2.15.so
init 1 root  memREG8,147712  5664 
/lib/x86_64-linux-gnu/libnss_nis-2.15.so
init 1 root  memREG8,197272  5654 
/lib/x86_64-linux-gnu/libnsl-2.15.so
init 1 root  memREG8,135712  5656 
/lib/x86_64-linux-gnu/libnss_compat-2.15.so
init 1 root  memREG8,1   135398  5691 
/lib/x86_64-linux-gnu/libpthread-2.15.so
init 1 root  memREG8,1  1811160  5596 
/lib/x86_64-linux-gnu/libc-2.15.so
init 1 root  memREG8,131784  5699 
/lib/x86_64-linux-gnu/librt-2.15.so
init 1 root  memREG8,1   277448  5608 
/lib/x86_64-linux-gnu/libdbus-1.so.3.7.2
init 1 root  memREG8,138920  5647 
/lib/x86_64-linux-gnu/libnih-dbus.so.1.0.0
init 1 root  memREG8,196280  5649 
/lib/x86_64-linux-gnu/libnih.so.1.0.0
init 1 root  memREG8,1   149312  5574 
/lib/x86_64-linux-gnu/ld-2.15.so
kthreadd 2 root  cwdDIR8,1 4096 2 /
kthreadd 2 root  rtdDIR8,1 4096 2 /
ksoftirqd3 root  cwdDIR8,1 4096 2 /
ksoftirqd3 root  rtdDIR8,1 4096 2 /
migration6 root  cwdDIR8,1 4096 2 /
migration6 root  rtdDIR8,1 4096 2 /

[Desktop-packages] [Bug 1058987] Re: In Quantal, the root filesystem is not cleanly unmounted at shutdown or reboot

2012-10-17 Thread Christian Niemeyer
*** This bug is a duplicate of bug 1061639 ***
https://bugs.launchpad.net/bugs/1061639


** Attachment added: Text file of complete log/howto (see also appendices of 
lsof /, ps -e, lsmod)
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+attachment/3402055/+files/cleanshutdown_howto2.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1058987

Title:
  In Quantal, the root filesystem is not cleanly unmounted at shutdown
  or reboot

Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  Ever since some update in the Quantal pre-releases, having dnsmasq-
  base installed will cause the root filesystem to not be properly
  unmounted on shutdown and reboot. In case the Plymouth splash screen
  is disabled, the message 'mount: / is busy' will be shown, but
  otherwise the user will not even be aware of this problem.

  After rebooting, the root filesystem needs recovery, as shown in
  dmesg:

  kevin@vbox-xubuntu-quantal:~$ dmesg | grep EXT4
  [1.022746] EXT4-fs (sda2): INFO: recovery required on readonly filesystem
  [1.022750] EXT4-fs (sda2): write access will be enabled during recovery
  [1.248294] EXT4-fs (sda2): recovery complete
  [1.248661] EXT4-fs (sda2): mounted filesystem with ordered data mode. 
Opts: (null)
  [1.456315] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro

  Yet again, the user will not be aware of this until it is too late.
  The only way to avoid this from happening (or at least what I've
  found) is running 'sudo apt-get purge dnsmasq-base'. Sadly, this also
  removes network-manager and network-manager-gnome, so it isn't really
  a viable solution.

  Another problem that might be related is that having an active
  connection with the Network Manager prior to shutting down or
  rebooting, will cause the process to hang for a few seconds, after
  which the message about / being busy is shown. Stopping the network
  service (sudo service networking stop) will solve the hanging, but not
  the unclean unmount. So far, only purging dnsmasq-base seems to do
  that, which obviously also solves the other problem, as Network
  Manager will then also be removed.

  Although I haven't experienced it yet, this could cause potential data
  loss; especially for users without a seperate /home partition.

  
  ProblemType: Bug
  ApportVersion: 2.5.3-0ubuntu1
  Architecture: amd64
  Date: Sun Sep 30 12:49:24 2012
  DistroRelease: Ubuntu 12.10
  Package: dnsmasq-base 2.63-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  SourcePackage: dnsmasq
  Tags:  quantal
  Uname: Linux 3.5.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1058987/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp