[Ubuntu-x-swat] [Bug 1522727] Re: X.org crashes intermittently, randomly

2015-12-13 Thread greg one
intel graphics here as well, clicking link in chromium crashed X server,
not much running here really, if anything at all, X will restart very
quickly (in my case) and i am back to login screen, this is a bit like
roller-caster ride, unpredictable and no warning or anything whatsoever,
i have seen crash few times over last 2 weeks, thanks for looking into
it

[39.467] (II) XKB: reuse xkmfile 
/var/lib/xkb/server-5841764B120E02BC6FD78DAB262CEA727EB95BEE.xkm
[  1308.087] (EE) 
[  1308.087] (EE) Backtrace:
[  1308.087] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55ee6548868e]
[  1308.087] (EE) 1: /usr/bin/X (0x55ee652d4000+0x1b89f9) [0x55ee6548c9f9]
[  1308.087] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f0809b25000+0x352f0) 
[0x7f0809b5a2f0]
[  1308.087] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f0805efc000+0x85dac) [0x7f0805f81dac]
[  1308.087] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f0805efc000+0x8a5a2) [0x7f0805f865a2]
[  1308.087] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f0805efc000+0xf53ef) [0x7f0805ff13ef]
[  1308.087] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7f0805efc000+0x10469f) [0x7f080600069f]
[  1308.087] (EE) 7: /usr/bin/X (0x55ee652d4000+0x185c2c) [0x55ee65459c2c]
[  1308.087] (EE) 8: /usr/bin/X (DRI2CopyRegion+0x8e) [0x55ee6545a34e]
[  1308.087] (EE) 9: /usr/bin/X (0x55ee652d4000+0x188723) [0x55ee6545c723]
[  1308.087] (EE) 10: /usr/bin/X (0x55ee652d4000+0x5818f) [0x55ee6532c18f]
[  1308.087] (EE) 11: /usr/bin/X (0x55ee652d4000+0x5c34b) [0x55ee6533034b]
[  1308.087] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f0809b45a40]
[  1308.087] (EE) 13: /usr/bin/X (_start+0x29) [0x55ee6531a6c9]
[  1308.087] (EE) 
[  1308.087] (EE) Segmentation fault at address 0x0
[  1308.087] (EE) 
Fatal server error:
[  1308.087] (EE) Caught signal 11 (Segmentation fault). Server aborting

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

Title:
  X.org crashes intermittently, randomly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1522727/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525207] Re: xserver-xorg-video-intel slow perfomance, needs updating

2015-12-13 Thread Timo Aaltonen
thanks for the update, will create a newer snapshot for xenial
eventually

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1525207

Title:
  xserver-xorg-video-intel slow perfomance, needs updating

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1525207/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1470862] Re: When using fglrx module, the virtual consoles are blank and useless

2015-12-13 Thread cogset
That was (probably) more or less a given, this is clearly  an ATI/fglrx
issue.

What I don't understand is why is considered somehow acceptable to
suffer such an issue, or why the recommended "fix" (?) would be to get
rid of the fglrx driver altogether.

ATI support for Linux may be considerably worse than Nvidia (as
recognized by many people in the know), but if the package exists in the
Ubuntu repository it should work without rendering the virtual consoles
useless, and this issue shouldn't slip all the way from 14.04 to 15.10.

That

>removing fglrx drivers is some sort of workaround, but presumably
people that did install fglrx in the first place >want fglrx for some
reason

is the appropriate line of reasoning: the official package exists and
should be installable without breaking anything major such as the
virtual consoles.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1470862

Title:
  When using fglrx module, the virtual consoles are blank and useless

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1470862/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1512527] Re: fglrx-core (not installed): fglrx-core kernel module failed to build [fatal error: asm/i387.h: No such file or directory]

2015-12-13 Thread Daniel van Vugt
** Summary changed:

- fglrx-core (not installed): fglrx-core kernel module failed to build [fatal 
error: asm/i387.h: No such file or directory] Edit
+ fglrx-core (not installed): fglrx-core kernel module failed to build [fatal 
error: asm/i387.h: No such file or directory]

** Also affects: fglrx-installer-updates (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1512527

Title:
  fglrx-core (not installed): fglrx-core kernel module failed to build
  [fatal error: asm/i387.h: No such file or directory]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1512527/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525523] Re: fglrx-updates-core 2:15.200-0ubuntu0.3: fglrx-updates-core kernel module failed to build

2015-12-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1512527 ***
https://bugs.launchpad.net/bugs/1512527

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1512527, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1512527
   fglrx-core (not installed): fglrx-core kernel module failed to build [fatal 
error: asm/i387.h: No such file or directory]

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1525523

Title:
  fglrx-updates-core 2:15.200-0ubuntu0.3: fglrx-updates-core kernel
  module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1525523/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1522922]

2015-12-13 Thread Furniss-tom
Created attachment 120481
dmesg for resume from sleep flickering

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1522922

Title:
  Screen flickering in Intel i915 driver

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1522922]

2015-12-13 Thread B25ae2
Created attachment 120485
dmesg with drm.debug=14

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1522922

Title:
  Screen flickering in Intel i915 driver

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1511247] Re: Ubuntu 15.10 Could not apply the stored configuration for monitors

2015-12-13 Thread Duane Gaul
I also have this problem on my PC when I upgraded to Ubuntu 15.10. I'm
using a Samsung 32" television as a monitor. Upon bootup, it can't find
the 16080 x 1050 (16:10) display, so it defaults to (16:9).

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

Title:
  Ubuntu 15.10 Could not apply the stored configuration for monitors

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1514232] Re: nouveau E[ PFIFO][0000:01:00.0] SCHED_ERROR [ UNK06 ]

2015-12-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1514232

Title:
  nouveau E[  PFIFO][:01:00.0] SCHED_ERROR [ UNK06 ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1514232/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1514232] Re: nouveau E[ PFIFO][0000:01:00.0] SCHED_ERROR [ UNK06 ]

2015-12-13 Thread justgivemeaname
Whenever I try to boot Ubuntu with a LiveUSB on the MSI laptop of my
brother, it just repeats the exact error message over and over again
after choosing to try Ubuntu with a LiveUSB: it never will actually boot
further. Tried at least 10 times while I recreated the LiveUSB with
15.10 which is used to successfully install it on another laptop.

If anyone needs anything to help troubleshoot, please ask (and add/link
to instructions, to be sure.)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1514232

Title:
  nouveau E[  PFIFO][:01:00.0] SCHED_ERROR [ UNK06 ]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1514232/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1524099] Re: Problems with graphics video streaming

2015-12-13 Thread Hans Joachim Desserud
*** This bug is a duplicate of bug 1524098 ***
https://bugs.launchpad.net/bugs/1524098

** This bug has been marked a duplicate of bug 1524098
   Problems with graphics video streaming

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

Title:
  Problems with graphics video streaming

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525668] [NEW] Options have the wrong order

2015-12-13 Thread Sworddragon
Public bug reported:

I'm using Ubuntu 16.04 dev with xserver-xorg-core 2:1.17.3-2ubuntu2 and
I'm noticing that "man xorg" says "Xorg [:display] [option ...]" but in
the process /usr/lib/xorg/Xorg the display is being given between
options.

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Options have the wrong order

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1525668/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525735] [NEW] X server fails to start under regular user in Xenial

2015-12-13 Thread Dillon Brock
Public bug reported:

The newest ISO image of Ubuntu GNOME Xenial Xerus does not launch the
graphical installer on boot. Instead, it waits at the text-based login
screen. I can log in using the default username of 'ubuntu-gnome' and
start the X server with 'sudo startx.' Note that just 'startx' does not
work; the command must be run as root. I am able to proceed with the
installation as normal after starting X.

After the system is fully installed, the problem persists. X can still
be started manually after login.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg 1:7.7+12ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
Uname: Linux 4.3.0-2-generic x86_64
ApportVersion: 2.19.3-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Dec 13 19:43:20 2015
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2015-12-13 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151212)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-2-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
Renderer: Software
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.65-3
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151019-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sun Dec 13 19:40:19 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.3-2ubuntu2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  X server fails to start under regular user in Xenial

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525735] Re: X server fails to start under regular user in Xenial

2015-12-13 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1525735

** Tags added: iso-testing

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

Title:
  X server fails to start under regular user in Xenial

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1516531] Re: Fullscreen Freeze.

2015-12-13 Thread Vindicator
You know, I was curious about that other bug I referenced where the guy never 
mentioned what testing each kernel upgrade was supposed to do.
And what do I find? It was you Christopher.  There was too much of a similarity 
for me to just let it pass, and I just had to look that bug up again to see for 
sure.

I'm disappointed and surprised if this is the level of "bug triage".
I looked at your wiki and a handful of bugs that you've triaged and all I have 
seen is you asking for a newer kernel/bios/os to be tested.
It's like dealing with 1st-tier phone support (with any company).

I wouldn't be surprised if you dump this comment, close or invalidate
this bug for personal reasons, but I own and stand by my comments based
on what I've seen and experienced.

Like I said, if anything I'd just as soon revert to 15.04. But with
Ubuntu having been my primary experience with any linux dist, I may just
see what kind of stability others have to offer.

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

Title:
  Fullscreen Freeze.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1137510] Re: xorg-cf needs porting

2015-12-13 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xutils-dev in Ubuntu.
https://bugs.launchpad.net/bugs/1137510

Title:
  xorg-cf needs porting

To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-aarch64/+bug/1137510/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525451] Re: Ubuntu GNOME 16.04 daily wont boot in virtualbox

2015-12-13 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  Ubuntu GNOME 16.04 daily wont boot in virtualbox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1525451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1525721] [NEW] Can't use hardware decoding (vaapi) with fglrx: Assertion `buffers' failed

2015-12-13 Thread Ales
Public bug reported:

mpv --hwdec=auto movie.mkv gives this:

  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  Using hardware decoding (vaapi).
  VO: [opengl] 1904x1036 vaapi
  mpv: dri2_util.c:132: dri2GetRenderingBuffer: Assertion `buffers' failed.
  (SIGABRT) (core dumped)

I have hybrid graphics Intel Haswell and AMD Radeon R5 M255.
I have installed fglrx-updates and in AMD Catalyst control center switched to 
dedicated GPU.
I seems to me that this setting is ignored and hardware decoding is tried on 
Intel instead. 

fglrxinfo:
  display: :0  screen: 0
  OpenGL vendor string: Advanced Micro Devices, Inc.
  OpenGL renderer string: AMD Radeon R5 M255 
  OpenGL version string: 4.5.13399 Compatibility Profile Context 15.201.1151

amdconfig --pxl : 
  PowerXpress: Discrete GPU is active (High-Performance mode).

lspci | grep VGA:
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)

vainfo:
libva info: VA-API version 0.38.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_38
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.38 (libva 1.6.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 1.6.0
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264MultiviewHigh  : VAEntrypointVLD
  VAProfileH264MultiviewHigh  : VAEntrypointEncSlice
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileH264StereoHigh : VAEntrypointEncSlice
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileH264MultiviewHigh  : VAEntrypointVLD
  VAProfileH264MultiviewHigh  : VAEntrypointEncSlice
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileH264StereoHigh : VAEntrypointEncSlice

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Dec 13 23:04:06 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: kubuntu
DkmsStatus: fglrx-updates-core, 15.201, 4.2.0-19-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2248]
   Subsystem: Hewlett-Packard Company Device [103c:224a]
InstallationDate: Installed on 2015-10-23 (51 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Hewlett-Packard HP ProBook 450 G2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic 
root=UUID=c9e0c6ee-c8a4-4d1a-a46e-a3b79c38f774 ro
SourcePackage: xorg
UdevLog: Error: [Errno 2] Adresář nebo soubor neexistuje: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/20/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M74 Ver. 01.05
dmi.board.name: 2248
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 67.22
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM74Ver.01.05:bd09/20/2014:svnHewlett-Packard:pnHPProBook450G2:pvrA3008CD10003:rvnHewlett-Packard:rn2248:rvrKBCVersion67.22:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 450 G2
dmi.product.version: A3008CD10003
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A

[Ubuntu-x-swat] [Bug 1525451] Re: Ubuntu GNOME 16.04 daily wont boot in virtualbox

2015-12-13 Thread Tim
** Bug watch added: Virtualbox Trac #14732
   http://www.virtualbox.org/ticket/14732

** Also affects: xorg-server via
   http://www.virtualbox.org/ticket/14732
   Importance: Unknown
   Status: Unknown

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

Title:
  Ubuntu GNOME 16.04 daily wont boot in virtualbox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1525451/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1516531] Re: Fullscreen Freeze.

2015-12-13 Thread Christopher M. Penalver
Vindicator, I'm not sure how attacking me, and not providing previously
requested information is going to either solve your problem, or motivate
others to want to help you with it.

Here in Ubuntu, we don't put down others for contributing on any level
they choose to provide, whether it's documentation, triage, or
development. So, if you feel compelled to put people down for their
contribution, please feel free to mark your report as Invalid, and take
it elsewhere as it's not welcomed here in Launchpad.

Despite this, if one would care to read comments fully before attacking
the poster, why one is asked to test a newer version of the kernel,
BIOS, or OS respectively is fully documented, both in those comments you
glanced at, and throughout the publicly available Ubuntu documentation.
You are welcome to start familiarizing yourself with this at
https://wiki.ubuntu.com/ReportingBugs .

To further clarify
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/comments/28
, xorg bugs aren't considered triaged unless the latest version of
Ubuntu is tested, or the root cause commit is identified. As neither has
occurred, this report is pretty much a standstill.

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

Title:
  Fullscreen Freeze.

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

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1516531] Re: Fullscreen Freeze.

2015-12-13 Thread Vindicator
I must say I'm glad you did respond as it means you take it seriously.

While you take it as a personal attack, it was merely a description of what I 
have seen and experienced.
Attacking is something I associate with name-calling with nothing backing it up.
A performance-review from a boss that describes problems with an employee's 
results is not something I would consider an attack.

I know 1st-tier phone support where the person I'm speaking with has no idea 
regarding the issue and is reading from a script that is not applicable to the 
issue, when all that is needed is to advance me to someone who would be able to 
provide deeper support (test a patch).
It's the kind of support that would be equal to "reboot your computer 3 times" 
when Excel is selecting multiple cells with a single click. It would be more 
appropriate to see if the mouse button has bounce, but even then it could still 
be a software bug.
That is the impression I get when I'm asked to test a newer kernel or OS to see 
if it would fix the issue.
It was never said "why" it was thought it would fix the issue (eg, reference a 
pull-request that addresses an issue that might be remotely applicable to the 
current issue).
I can see the value of 1st-tier in order to filter out "newbs" for the 
developers when a configuration/setting change is all that is needed, but as 
much as the tier can be helpful for the developers (and newbs), they can also 
be headaches for those with issues that need deeper triage.

"... why one is asked... documented, both in those comments..."
I must be missing those comments you are referencing that provides the "why".
My "why" questions:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/comments/29  "What 
is it about Xenial..."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1465862/comments/11  
"...wondering what this 'testing' is supposed to be doing..."
Other's bug's that ask for a test with an upgrade, but no "why" given:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1523108/comments/4
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506914/comments/4 "Can 
someone please explain what..."

With the wiki, I think you are probably referencing "Please do not complain 
because someone sent what one perceives to be a automated or "canned" response."
I also see this issue as "Please check to see if you(r) problem is a 
regression." so I'd say bisecting should be done rather than about testing 
upstream. But I know by saying just that goes against "Please avoid arguing 
with triagers and developers".

For me, testing a newer kernel is less complicated than testing a whole new OS 
that is only in the early testing stages when I'm dealing with a "production" 
(day-to-day use) computer.
It would involve:
1) backing things up and hoping that backup worked.
2) upgrading (in my case, I always start with a fresh install)
3) restore, which never goes well with an encrypted home. something I have to 
do from live-cd.
4) installing programs, which also means building some from scratch like kodi 
which also means building the addons.
Even if I got there after hours (day(s)?) of work, the testing OS may not fix 
the issue and may also have other unusable problems.

Note how I actually do the footwork that I consider reasonable. I'll do
research before submitting a report. I do research to back up my
comments. This isn't off-the-cuff stuff that I am doing.

Also I WON'T be marking this report as "Invalid" as it's VERY valid considering 
how it affected Kodi and Chrome (haven't tested totem or games in fullscreen).
But YOU may mark it as incomplete since I am unlikely to test xenial, 
especially since the break happened in 15.10 (worked in 15.04).
I may put xenial on a VM to get a feel for it's current state, but based on my 
experience with UX bugs in 15.04 and 15.10, if I'm going to have to clean house 
on my system, I'd just as soon avoid 16.04 (not even alpha yet) and see if 
other dists come through the pipeline clean(er/ly).
I'll have to back up my data anyway, so I may just do an in-place upgrade to 
xenial and if it fails with fullscreen or some other notable bug, I'll go ahead 
an move on to a different dist.

I may look at Arch since the documentation I've seen online, when searching for 
system-stuff, has been better than Ubuntu. Ubuntu does have plenty of 
documentation, but they are all over the place with multiple versions that are 
about the same exact thing.
Again, I wouldn't call that an attack, but merely pointing out a problem. I'd 
provide links to examples, but this comment is already getting long-winded and 
this paragraph doesn't relate specifically to the "help" issue (though it is 
about docs which was mentioned in your last comment).

I won't be offended or hurt if you want to reference these comments as what to 
(do/not do).
If I'm in the wrong, so be it. I currently don't see it. I'm trying to do good 
by submitting a bug and providing good data and in turn I'm only 

[Ubuntu-x-swat] [Bug 1502905] Re: package nvidia-opencl-icd-304-updates (not installed) failed to install/upgrade: próba nadpisania "/etc/OpenCL/vendors/nvidia.icd", który istnieje także w pakiecie nv

2015-12-13 Thread Launchpad Bug Tracker
[Expired for nvidia-graphics-drivers-304-updates (Ubuntu) because there
has been no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1502905

Title:
  package nvidia-opencl-icd-304-updates (not installed) failed to
  install/upgrade: próba nadpisania "/etc/OpenCL/vendors/nvidia.icd",
  który istnieje także w pakiecie nvidia-opencl-icd-331
  331.113-0ubuntu0.0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1502905/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1508683] Re: Build with multiarch support

2015-12-13 Thread Timo Aaltonen
ah, forgot it builds some libs

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-openchrome in Ubuntu.
https://bugs.launchpad.net/bugs/1508683

Title:
  Build with multiarch support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1508683/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp