[Ubuntu-x-swat] [Bug 1413710] Re: Xorg crash - Fullscreen causing crash

2016-07-29 Thread Jose Barakat
As Jullian Gafar (jullian-gafar) wrote on 2015-08-20:

I'm also having this issue with F11 or any application that goes
fullscreen in Unity.

--
System Software / Hardware Information

Hardware:
Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, 
Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate 
ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, 
Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless

Software:
OS: Ubuntu 16.04, Kernel: 4.3.0-040300-generic (x86_64), Desktop: Unity 7.4.0, 
Display Server: X Server 1.18.3, Display Driver: intel 2.99.917, OpenGL: 3.3 
Mesa 12.1.0-devel (git-7295428 2016-07-03 xenial-oibaf-ppa), Compiler: GCC 
5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768
--

I'm trying Gnome or KDE alongside Unity.

-- 
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/1413710

Title:
  Xorg crash - Fullscreen causing crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710/+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 1607966] [NEW] X doesn't start with r128 driver with PM 3, 1 PPC ATI Rage

2016-07-29 Thread Fritz Hudnut
Public bug reported:

I was working on bug #1541082 which was reporting "blotchy" graphics
images on my PowerMac3,1 with Rage ATI Pro 128 card . . . and got the
suggestion to try to add the "r128" driver, which I did.  After that the
display went black.  After fiddling around with it, I removed the r128
driver, made an xorg.conf file . . . and after numerous attempts to get
the display back, today I got "fbdev" and mode "1920 x 1200" to bring
the GUI back online . . . but, there was another "xorg" crash on reboot,
which I reported, along with filing this bug against the r128 module for
this PPC machine.

F

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
Uname: Linux 4.4.0-31-powerpc-smp ppc
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: powerpc
BootLog:
 fsck from util-linux 2.27.1
 /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Jul 29 14:34:22 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS 
[1002:5046] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2016-01-31 (179 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc 
(20160123)
Lsusb:
 Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite
 Bus 002 Device 003: ID 05ac:0201 Apple, Inc. USB Keyboard [Alps or Logitech, 
M2452]
 Bus 002 Device 002: ID 05ac:1001 Apple, Inc. Keyboard Hub [ALPS]
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet 
splash
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jul 29 14:15:13 2016
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 inputAlps Electric Apple USB Keyboard KEYBOARD, id 6
 inputKensington  USB/PS2 Wheel Mouse MOUSE, id 7
 inputPMU  KEYBOARD, id 8
xserver.errors: AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


** Tags: apport-bug powerpc 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/1607966

Title:
  X doesn't start with r128 driver with PM 3,1 PPC ATI Rage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1607966/+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


Re: [Ubuntu-x-swat] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread Fritz Hudnut
On Fri, Jul 29, 2016 at 11:20 AM, Fritz Hudnut 
wrote:

> But, I was thinking this morning I have some notes about the display
> "modes" where I have used something like "1024 x 768@60-32" . . .
> something like that, and ***that*** did make a difference on my iBook to
> get the display to work properly . . . possibly that is worth trying out .
> . . .  I'll post back on the "progress" . . . when I get there.


Good news, after trying three or four different variations, the GUI is back
using "fbdev" and I also changed the mode to "1920 x 1200" . . . and the
log in splash image is "smoother" than it was before, "blotchy" but not as
"blotchy" as it was before the xorg.conf file.

Only caveat is there was a "crash report" generated relating to
"xorg-server" or something like that.  I "reported" it.  There was an
obvious "glitch" in the mouse cursor movement when I logged in which I've
come to understand indicates a "crash."

I'm typing this in the MATE 16 GUI; we'll see how it goes on reboot.
Sending the apport-collect data to the new bug r128 related.

F

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread Christopher M. Penalver
** Description changed:

  ~ % cat /var/log/xdm.log
  
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  resize called 1920 1200
  Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xsetup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing /etc/X11/xdm/Xstartup
  Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session 
/etc/X11/xdm/Xsession
  resize called 3840 1200
  resize called 1920 1200
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
  (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
  (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3) 
[0x7f27e538b1f3]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d) 
[0x7f27e538ba5d]
  (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
  (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
  (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0) 
[0x7f27ee6db4a0]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
  (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f27efa880f8]
  (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) 
[0x7f27efa8adbb]
  (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 (nouveau_bo_wait+0xbc) 
[0x7f27ea7d103c]
  (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xc839) 
[0x7f27ea9e2839]
  (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f27ea9d6000+0xd25d) 
[0x7f27ea9e325d]
  (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
  (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
  (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
  (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
  (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f27ee6c6830]
  (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
  (EE)
  (EE) [mi] EQ overflow continuing.  200 events have been dropped.
  
- My system info:
+ WORKAROUND: Use nvidia-358 driver.
  
-  ~ % uname -a
- Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
-  ~ % cat /etc/debian_version
- stretch/sid
- 
-  ~ % lsb_release -a
- No LSB modules are available.
- Distributor ID:   Ubuntu
- Description:  Ubuntu Xenial Xerus (development branch)
- Release:  16.04
- Codename: xenial
-  ~ %
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK208 [GeForce GT 720] [10de:1288] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK208 [GeForce GT 720] 
[1462:8c90]
   NVIDIA Corporation GK208 

[Ubuntu-x-swat] [Bug 1471998] Re: [enhancement] Support copy-paste between X and Mir

2016-07-29 Thread Christopher Townsend
** Branch linked: lp:~dandrader/qtubuntu/content-hub-clipboard

** Changed in: qtubuntu (Ubuntu)
   Status: Triaged => In Progress

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel d'Andrada (dandrader)

** Tags removed: xmir

** No longer affects: xorg-server (Ubuntu)

** No longer affects: unity8 (Ubuntu)

-- 
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/1471998

Title:
  [enhancement] Support copy-paste between X and Mir

To manage notifications about this bug go to:
https://bugs.launchpad.net/libertine/+bug/1471998/+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


Re: [Ubuntu-x-swat] [Bug 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread rohshall
Yes, that is correct.

On Fri, Jul 29, 2016 at 7:41 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, to confirm, you are stating that when using nvidia-358 from
> the Ubuntu repositories (not PPA, third party installs, etc.) doesn't
> crash at all?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] EQ overflow continuing.  200 events have been dropped.
>
>   My system info:
>
>~ % uname -a
>   Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
> 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>~ % cat /etc/debian_version
>   stretch/sid
>
>~ % lsb_release -a
>   No LSB modules are available.
>   Distributor ID:   Ubuntu
>   Description:  Ubuntu 

[Ubuntu-x-swat] [Bug 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread Christopher M. Penalver
rohshall, to confirm, you are stating that when using nvidia-358 from
the Ubuntu repositories (not PPA, third party installs, etc.) doesn't
crash at all?

-- 
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/1573773

Title:
  System freezes randomly a few times a day

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1573773/+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 1607924] [NEW] fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build

2016-07-29 Thread Tristan Cormier
Public bug reported:

I installed AMD fglrx through AMD's website and upon reboot could not
get to my desktop or TTY anymore. I tried to blindly uninstall
everything and went back to X.Org open-source drivers. The bug was
encountered.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx-core (not installed)
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 4.2.0-42-generic
Date: Fri Jul 29 15:13:46 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] 
(prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Device [174b:174b]
InstallationDate: Installed on 2016-07-29 (0 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: MSI MS-7926
PackageVersion: 2:15.201-0ubuntu1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic.efi.signed 
root=UUID=8488b034-23ac-42b5-84fd-860013f162e4 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: fglrx-installer
Title: fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.13
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97 GAMING 9 AC (MS-7926)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.13:bd02/16/2016:svnMSI:pnMS-7926:pvr1.0:rvnMSI:rnZ97GAMING9AC(MS-7926):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7926
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jul 29 15:31:03 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
xserver.video_driver: radeon

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 trusty ubuntu

-- 
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/1607924

Title:
  fglrx-core 2:15.201-0ubuntu1: fglrx-core kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1607924/+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 1607856] Re: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

2016-07-29 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1607856/+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


Re: [Ubuntu-x-swat] [Bug 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread rohshall
Sorry, I meant nvidia-358 and not nvidia-258

On Fri, Jul 29, 2016 at 7:01 PM, Salil Wadnerkar 
wrote:

> nvidia-258, available in the ubuntu repository, worked mostly. I don't
> remember what didn't work. However, I can vouch for nvidia-367, which is
> avalable through ppa ppa:graphics-drivers/ppa. It worked without any issues.
>
> On Fri, Jul 29, 2016 at 6:17 PM, Christopher M. Penalver <
> christopher.m.penal...@gmail.com> wrote:
>
>> rohshall, to clarify, if you use the nvidia proprietary drivers provided
>> by the Ubuntu repositories as per
>> https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
>> problem a WORKAROUND?
>>
>> ** Tags removed: bios-outdated-2902
>> ** Tags added: latest-bios-2902
>>
>> ** Changed in: xorg (Ubuntu)
>>Importance: Low => Medium
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1573773
>>
>> Title:
>>   System freezes randomly a few times a day
>>
>> Status in xorg package in Ubuntu:
>>   Incomplete
>>
>> Bug description:
>>   ~ % cat /var/log/xdm.log
>>
>>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>>   resize called 1920 1200
>>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
>> /etc/X11/xdm/Xsetup
>>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
>> /etc/X11/xdm/Xstartup
>>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
>> /etc/X11/xdm/Xsession
>>   resize called 3840 1200
>>   resize called 1920 1200
>>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
>> existing events are processed.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x61f3) [0x7f27e538b1f3]
>>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x6a5d) [0x7f27e538ba5d]
>>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
>> [0x7f27ee6db4a0]
>>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
>> [0x7f27efa880f8]
>>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
>> [0x7f27efa8adbb]
>>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
>> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
>> [0x7f27ee6c6830]
>>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>>   (EE)
>>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
>> higher up the stack.
>>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>>   (EE)
>>   (EE) Backtrace:
>>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x61f3) [0x7f27e538b1f3]
>>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so
>> (0x7f27e5385000+0x6a5d) [0x7f27e538ba5d]
>>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
>> [0x7f27ee6db4a0]
>>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
>> [0x7f27efa880f8]
>>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
>> [0x7f27efa8adbb]
>>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
>> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
>> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>>   (EE) 16: 

[Ubuntu-x-swat] [Bug 1607856] Re: nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

2016-07-29 Thread Seth Arnold
** Information type changed from Private Security to Public

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

Title:
  nvidia-304 304.131-0ubuntu3: nvidia-304 kernel module failed to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1607856/+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


Re: [Ubuntu-x-swat] [Bug 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread rohshall
nvidia-258, available in the ubuntu repository, worked mostly. I don't
remember what didn't work. However, I can vouch for nvidia-367, which is
avalable through ppa ppa:graphics-drivers/ppa. It worked without any issues.

On Fri, Jul 29, 2016 at 6:17 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, to clarify, if you use the nvidia proprietary drivers provided
> by the Ubuntu repositories as per
> https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
> problem a WORKAROUND?
>
> ** Tags removed: bios-outdated-2902
> ** Tags added: latest-bios-2902
>
> ** Changed in: xorg (Ubuntu)
>Importance: Low => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] 

[Ubuntu-x-swat] [Bug 1607891] Re: X doesn't start with r128 driver (PowerMac 3, 1) [powerpc]

2016-07-29 Thread Bug Watch Updater
** Changed in: xserver-xorg-video-r128 (Debian)
   Status: Unknown => Confirmed

-- 
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/1607891

Title:
  X doesn't start with r128 driver (PowerMac 3,1) [powerpc]

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1607891/+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


Re: [Ubuntu-x-swat] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread Fritz Hudnut
On Fri, Jul 29, 2016 at 10:24 AM, ernsteiswuerfel 
wrote:

> Added the upstream bug to this tracker. Then I realized that strictly
> speaking this bug "X doesn't start with r128 driver (ATI RAGE)
> [powerpc]" has a different meaning from this one here "blotchy
> graphics". I think it's best to create a new Ubuntu Xorg bug and add the
> upstream info there.
>
> Sorry for the noise!
>
> @Fritz:
>
> Your xorg.conf looks fine. After altering parameters check your Xorg.log
> after you restarted X, to look what exactly went wrong with the driver you
> selected xorg.conf. Just use the different drivers "modesetting", "fbdev",
> "fbdevhw" with different bit depths and see what happens.
> If your monitor is capacle also always use the native resolution of your
> monitor. The Rage 128 is able to do 1920x1080 if you got the most recent PM
> 3,1 (http://identimac.com/modelDetails/Power%20Macintosh%20G4/23.html)
>


Yes, I'm also sorry for the "noise," but I decided to include it here as
well to show the personal efforts being expended to work on this problem .
. . and the resultant, "now it's not blotchy, now it is a blackish screen
with no images . . . that is happening, etc.

@ernsteiswuerfel:

OK, glad to hear that, yes, I thought it looked "OK" as well, but, it made
no difference in display showing up, or even trying to show up.  Although
when I booted the live DVD session it took literally 3 or 4 minutes for the
cursor to appear and then the desktop; and perhaps I haven't been letting
it take that long with these recent efforts??  It's all become a tad bit
"odd" . . . in that trying the --configure gambit was returned as "failed"
. . . and looking through "lsmod" shows none of the usual suspects as far
as video drivers goes . . . and I did "autoclean" trying to remove "r128"
to see if that would let the xorg.conf get busy . . . and r128 didn't show
up in that list, so I did "sudo rm x-x-v-r128" (spelled out) and then it
said "no such file or directory" . . . .

And, multiple reboots and so forth, makes for a lot of time . . . .
Anyway, as it is now, the graphics are not "blotchy" . . . they are "gone"
so I don't know how I can support a "new" Bugzilla r128 bug with "evidence"
because . . . now the screen is black, etc . . . and there is an xorg.conf
file whereas before there wasn't, etc.

I did look over the Xorg.log a couple times . . . nothing of any apparent
relevance showed up, but then this area is an area of weakness . . . I have
the "dual-boot" install process down, and years back I spent endless hours
trying to get 12.04 to run the display on my old iMac 800 . . . now I'm
generally finding that it is easier to do a fresh install than to mess
around with the console on the tiny details . . . .

But, I was thinking this morning I have some notes about the display
"modes" where I have used something like "1024 x 768@60-32" . . . something
like that, and ***that*** did make a difference on my iBook to get the
display to work properly . . . possibly that is worth trying out . . . .
I'll post back on the "progress" . . . when I get there.

F

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread Christopher M. Penalver
rohshall, to clarify, if you use the nvidia proprietary drivers provided
by the Ubuntu repositories as per
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
problem a WORKAROUND?

** Tags removed: bios-outdated-2902
** Tags added: latest-bios-2902

** Changed in: xorg (Ubuntu)
   Importance: Low => Medium

-- 
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/1573773

Title:
  System freezes randomly a few times a day

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1573773/+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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread ernsteiswuerfel
For the sake of correctness I added a new bug:
https://bugs.launchpad.net/xorg-server/+bug/1607891

If you like just add the relevant data with "apport-collect" to this bug
after "r128" failed.

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1607891] [NEW] X doesn't start with r128 driver (PowerMac 3, 1) [powerpc]

2016-07-29 Thread ernsteiswuerfel
Public bug reported:

X seems to start, but only produces a black display. Happens on a
PowerMac 3,1 with Rage 128 PRO AGP 4x grapics card. Driver used:
xserver-xorg-video-r128

** Affects: xorg-server
 Importance: Unknown
 Status: Unknown

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

** Affects: xserver-xorg-video-r128 (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #820233
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233

** Also affects: xserver-xorg-video-r128 (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233
   Importance: Unknown
   Status: Unknown

** Bug watch added: freedesktop.org Bugzilla #94916
   https://bugs.freedesktop.org/show_bug.cgi?id=94916

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=94916
   Importance: Unknown
   Status: Unknown

-- 
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/1607891

Title:
  X doesn't start with r128 driver (PowerMac 3,1) [powerpc]

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1607891/+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


Re: [Ubuntu-x-swat] [Bug 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread rohshall
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2902
03/31/2016


On Fri, Jul 29, 2016 at 4:46 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, as previously requested, please provide the output of the
> following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 13: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 14: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 18: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] EQ overflow continuing.  200 events have been dropped.
>
>   My system info:
>
>~ % uname -a
>   Linux linux-swadnerkar 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
> 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>~ % cat /etc/debian_version
>   stretch/sid
>
>~ % lsb_release -a
>   No LSB 

[Ubuntu-x-swat] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread ernsteiswuerfel
Added the upstream bug to this tracker. Then I realized that strictly
speaking this bug "X doesn't start with r128 driver (ATI RAGE)
[powerpc]" has a different meaning from this one here "blotchy
graphics". I think it's best to create a new Ubuntu Xorg bug and add the
upstream info there.

Sorry for the noise!

@Fritz:

Your xorg.conf looks fine. After altering parameters check your Xorg.log after 
you restarted X, to look what exactly went wrong with the driver you selected 
xorg.conf. Just use the different drivers "modesetting", "fbdev", "fbdevhw" 
with different bit depths and see what happens.
If your monitor is capacle also always use the native resolution of your 
monitor. The Rage 128 is able to do 1920x1080 if you got the most recent PM 3,1 
(http://identimac.com/modelDetails/Power%20Macintosh%20G4/23.html)

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1574425] Re: Installing nvidia-361 leaves me unable to log in

2016-07-29 Thread Christopher M. Penalver
Jeramy Rutley, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574425/comments/4
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

-- 
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/1574425

Title:
  Installing nvidia-361 leaves me unable to log in

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574425/+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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread ernsteiswuerfel
** No longer affects: xorg-server

** No longer affects: debian

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics

2016-07-29 Thread Sondra Kinsey
It took me a while to find this bug report.  For the convenience of
others, I thought I would share references to this bug on the internet.
Perhaps a friendly user could post on all these forums links to this
bug. :)

User descriptions and reports of this bug:
  
https://askubuntu.com/questions/759723/mouse-cursor-is-disappearing-after-sleep
  
https://www.reddit.com/r/Lubuntu/comments/4i5wn3/after_update_to_lubuntu_1604_mouse_cursor
  https://ubuntuforums.org/showthread.php?t=2321778=13476309#post13476309
  https://ubuntuforums.org/showthread.php?t=2321311=13474801#post13474801


Suggested workarounds I haven't tried:

gsettings set org.gnome.settings-daemon.plugins.cursor active false


/etc/init.d/gdm restart


pressing Ctrl-Alt-F1 then Ctrl-Alt-F7


opening Leafpad and then typing something (or just pressing the spacebar) 
brings back the cursor (press Ctrl-Alt-T and then type leafpad to open it).



Suggested workarounds that didn't work for me:

xrefresh


Bring up a terminal, Ctrl+Alt+t. Hit return in the terminal window and the 
mouse pointer reappears.


-- 
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/1568604

Title:
  Mouse cursor lost when unlocking with Intel graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1607212] Re: HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

2016-07-29 Thread Christopher M. Penalver
Oliver, regarding this report, please post directly here (not send
personal emails). This allows others to contribute towards this.

Despite this, to see if this is a regression, if you test earlier
versions of the nvidia driver in your present install as per
https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia does this
issue improve?

-- 
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/1607212

Title:
  HDMI connection issue (Ubuntu 16.04 and GeForce GTX 960M)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1607212/+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 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread ernsteiswuerfel
** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=94916
   Importance: Unknown
   Status: Unknown

** Bug watch added: Debian Bug tracker #820233
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233

** Also affects: debian via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820233
   Importance: Unknown
   Status: Unknown

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread Christopher M. Penalver
rohshall, as previously requested, please provide the output of the following 
terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

-- 
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/1573773

Title:
  System freezes randomly a few times a day

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1573773/+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


Re: [Ubuntu-x-swat] [Bug 1573773] Re: System freezes randomly a few times a day

2016-07-29 Thread rohshall
I updated the BIOS and still the same result.
I also tried using ppa ppa:oibaf/graphics-drivers
​.
But, still the same.
Finally, I switched to nvidia-367 drivers and it works without crashing
​(​though not everything works -
 gdm does not work with nvidia drivers - only xdm
​)​
.
Anyway, I don't like proprietory stuff and would really love to have
nouveau drivers work
​.​

On Tue, Jul 26, 2016 at 10:57 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> rohshall, as per
> https://www.asus.com/Motherboards/Z97K/HelpDesk_Download/ an update to
> your computer's buggy, insecure, and outdated BIOS is available (2902).
> When you update to this following
> https://help.ubuntu.com/community/BIOSUpdate how does this improve the
> situation?
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful.
>
> Also, you don't have to create a new bug report.
>
> Once the BIOS is updated, if the problem is still reproducible:
> 1) Please provide the output of the following terminal command (not
> perform an apport-collect):
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
> 2) Please make a comment specifically advising on what improved.
> 3) Please mark this report Status New.
>
> If it's not reproducible, please mark this as Invalid.
>
> Thank you for your help.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1573773
>
> Title:
>   System freezes randomly a few times a day
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   ~ % cat /var/log/xdm.log
>
>   (==) Using system config directory "/usr/share/X11/xorg.conf.d"
>   resize called 1920 1200
>   Fri Apr 22 06:40:03 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xsetup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1185): sourcing
> /etc/X11/xdm/Xstartup
>   Fri Apr 22 06:40:13 2016 xdm info (pid 1270): executing session
> /etc/X11/xdm/Xsession
>   resize called 3840 1200
>   resize called 1920 1200
>   (EE) [mi] EQ overflowing.  Additional events will be discarded until
> existing events are processed.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x556f1318cfd3]
>   (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 6: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b)
> [0x7f27efa8adbb]
>   (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2
> (nouveau_bo_wait+0xbc) [0x7f27ea7d103c]
>   (EE) 12: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xc839) [0x7f27ea9e2839]
>   (EE) 13: /usr/lib/xorg/modules/drivers/nouveau_drv.so
> (0x7f27ea9d6000+0xd25d) [0x7f27ea9e325d]
>   (EE) 14: /usr/lib/xorg/Xorg (DRI2SwapBuffers+0x1c8) [0x556f1317da98]
>   (EE) 15: /usr/lib/xorg/Xorg (0x556f12ff9000+0x18632c) [0x556f1317f32c]
>   (EE) 16: /usr/lib/xorg/Xorg (0x556f12ff9000+0x53bbf) [0x556f1304cbbf]
>   (EE) 17: /usr/lib/xorg/Xorg (0x556f12ff9000+0x57c43) [0x556f13050c43]
>   (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0)
> [0x7f27ee6c6830]
>   (EE) 19: /usr/lib/xorg/Xorg (_start+0x29) [0x556f1303af59]
>   (EE)
>   (EE) [mi] These backtraces from mieqEnqueue may point to a culprit
> higher up the stack.
>   (EE) [mi] mieq is *NOT* the cause.  It is a victim.
>   (EE) [mi] EQ overflow continuing.  100 events have been dropped.
>   (EE)
>   (EE) Backtrace:
>   (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x556f131ab50e]
>   (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x556f13065672]
>   (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x61f3)
> [0x7f27e538b1f3]
>   (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f27e5385000+0x6a5d)
> [0x7f27e538ba5d]
>   (EE) 4: /usr/lib/xorg/Xorg (0x556f12ff9000+0x94248) [0x556f1308d248]
>   (EE) 5: /usr/lib/xorg/Xorg (0x556f12ff9000+0xb9712) [0x556f130b2712]
>   (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f27ee6a6000+0x354a0)
> [0x7f27ee6db4a0]
>   (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x5) [0x7f27ee7a2685]
>   (EE) 8: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28)
> [0x7f27efa880f8]
>   (EE) 9: 

[Ubuntu-x-swat] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images

2016-07-29 Thread Fritz Hudnut
On Wed, Jul 27, 2016 at 4:19 PM, ernsteiswuerfel 
wrote:

> It would be a good idea to let the
> upstream devs know that. xorg/driver/xf86-video-r128 is actively
> maintained and still receives patches (last one 8 days ago). You could
> file a bug against upstream:
> https://bugs.freedesktop.org/buglist.cgi?quicksearch=r128 Just be sure
> to have a complete Xorg.log ready to post this bug upstream and state
> that it happens on an Apple PowerMac 3,1.
>

I added my comments/issues to this bugzilla bug:

94916 - X doesn't start with r128 driver (ATI RAGE) [powerpc]
https://bugs.freedesktop.org/show_bug.cgi?id=94916


** Bug watch added: freedesktop.org Bugzilla #94916
   https://bugs.freedesktop.org/show_bug.cgi?id=94916

-- 
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/1541082

Title:
  [PowerMac3,1] Blotchy GUI graphics for images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+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 1607774] [NEW] i915 kernel module stops working occasionally

2016-07-29 Thread dbacc
Public bug reported:

Occasionally my screen gets black. The machine is still alive, can login
via ssh.


journalctl -k -b-2 | grep drm
Jul 26 10:22:34  kernel: [drm] Initialized drm 1.1.0 20060810
Jul 26 10:22:34  kernel: [drm] Memory usable by graphics device = 2048M
Jul 26 10:22:34  kernel: fb: switching to inteldrmfb from VESA VGA
Jul 26 10:22:34  kernel: [drm] Replacing VGA console driver
Jul 26 10:22:34  kernel: [drm] Supports vblank timestamp caching Rev 2 
(21.10.2013).
Jul 26 10:22:34  kernel: [drm] Driver supports precise vblank timestamp query.
Jul 26 10:22:34  kernel: [drm:intel_opregion_init [i915]] *ERROR* No ACPI video 
bus found
Jul 26 10:22:34  kernel: [drm] Initialized i915 1.6.0 20151010 for :00:02.0 
on minor 0
Jul 26 10:22:34  kernel: [drm] GMBUS [i915 gmbus vga] timed out, falling back 
to bit banging on pin 2
Jul 26 10:22:34  kernel: fbcon: inteldrmfb (fb0) is primary device
Jul 26 10:22:34  kernel: i915 :00:02.0: fb0: inteldrmfb frame buffer device
Jul 27 16:25:30  kernel: [drm] stuck on render ring
Jul 27 16:25:30  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [18427], reason: Ring hung, action: reset
Jul 27 16:25:30  kernel: [drm] GPU hangs can indicate a bug anywhere in the 
entire gfx stack, including userspace.
Jul 27 16:25:30  kernel: [drm] Please file a _new_ bug report on 
bugs.freedesktop.org against DRI -> DRM/Intel
Jul 27 16:25:30  kernel: [drm] drm/i915 developers can then reassign to the 
right component if it's not a kernel issue.
Jul 27 16:25:30  kernel: [drm] The gpu crash dump is required to analyze gpu 
hangs, so please always attach it.
Jul 27 16:25:30  kernel: [drm] GPU crash dump saved to 
/sys/class/drm/card0/error
Jul 27 16:25:30  kernel: drm/i915: Resetting chip after gpu hang
Jul 27 16:36:14  kernel: [drm] stuck on render ring
Jul 27 16:36:14  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [26940], reason: Ring hung, action: reset
Jul 27 16:36:14  kernel: drm/i915: Resetting chip after gpu hang
Jul 27 17:28:30  kernel: [drm] stuck on render ring
Jul 27 17:28:30  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [27028], reason: Ring hung, action: reset
Jul 27 17:28:30  kernel: drm/i915: Resetting chip after gpu hang
Jul 27 18:55:17  kernel: [drm] stuck on render ring
Jul 27 18:55:17  kernel: [drm] GPU HANG: ecode 6:0:0x85eecffc, in plasmashell 
[27304], reason: Ring hung, action: reset
Jul 27 18:55:17  kernel: drm/i915: Resetting chip after gpu hang
Jul 27 18:55:23  kernel: [drm] stuck on render ring
Jul 27 18:55:23  kernel: [drm] GPU HANG: ecode 6:0:0x85eeeffc, in plasmashell 
[27304], reason: Ring hung, action: reset
Jul 27 18:55:23  kernel: drm/i915: Resetting chip after gpu hang
Jul 27 18:55:29  kernel: [drm] stuck on render ring
Jul 27 18:55:29  kernel: [drm] GPU HANG: ecode 6:0:0x85eefffc, in 
chromium-browse [27590], reason: Ring hung, action: reset
Jul 27 18:55:29  kernel: drm/i915: Resetting chip after gpu hang
Jul 28 15:24:23  kernel: [drm] stuck on render ring
Jul 28 15:24:23  kernel: [drm] GPU HANG: ecode 6:0:0xbc17, in 
chromium-browse [29032], reason: Ring hung, action: reset
Jul 28 15:24:23  kernel: drm/i915: Resetting chip after gpu hang
Jul 28 18:04:52  kernel: [drm:intel_dp_link_training_clock_recovery [i915]] 
*ERROR* failed to enable link training
Jul 28 18:04:52  kernel: [drm:intel_dp_link_training_channel_equalization 
[i915]] *ERROR* failed to start channel equalization


The error Jul 26 10:22:34  kernel: [drm:intel_opregion_init [i915]]
*ERROR* No ACPI video bus found happens at every boot

The last two errors coincide with the times the screen gets blank.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Fri Jul 29 08:45:47 2016
DistUpgraded: 2016-04-26 11:22:19,544 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: kubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [8086:2001]
InstallationDate: Installed on 2016-04-12 (107 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=f93cc9f4-e422-49f0-b9d8-5db514ce0a72 ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: Upgraded to xenial on 2016-04-26 (93 days ago)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: 

[Ubuntu-x-swat] [Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable

2016-07-29 Thread Alberto Salvia Novella
** Also affects: shim (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: shim (Ubuntu)
   Importance: Undecided => Critical

** Changed in: shim (Ubuntu)
   Status: New => Confirmed

** Project changed: shim => hundredpapercuts

** Changed in: hundredpapercuts
   Status: New => Confirmed

** No longer affects: hundredpapercuts

** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Status: New => Invalid

** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
   Importance: Undecided => Critical

** No longer affects: nvidia-graphics-drivers-340 (Ubuntu)

** No longer affects: xorg (Ubuntu)

** No longer affects: linux (Ubuntu)

** Changed in: shim (Ubuntu)
   Status: Confirmed => Triaged

-- 
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/1574732

Title:
  Regression: Kernel Update in 16.04 from last days renders nvidia
  driver unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1574732/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
   Status: New => Confirmed

-- 
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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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 1600576] Re: Screen rolling/rotating horizontally when using specific applications

2016-07-29 Thread Alberto Salvia Novella
Please:

1. Report to (http://tinyurl.com/zmzneso).
2. Paste the new report link here.
3. Set this bug status back to "confirmed".

Thank you.

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

** Also affects: xserver-xorg-video-intel
   Importance: Undecided
   Status: New

-- 
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/1600576

Title:
  Screen rolling/rotating horizontally when using specific applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1600576/+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 1600576] Re: Screen rolling/rotating horizontally when using specific applications

2016-07-29 Thread Alberto Salvia Novella
@ Amish Naidu

This is the correct place to report. Thanks for doing so.

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Importance: Undecided => Critical

-- 
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/1600576

Title:
  Screen rolling/rotating horizontally when using specific applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1600576/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Daniel van Vugt
** Branch linked: lp:~vanvugt/qtubuntu/correct-scroll-speed

-- 
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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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 1598904] Re: X server crashes sporadically with a segfault

2016-07-29 Thread Stefan Freyr
I've added the xenial enablement stack and will report back if the crash
occurs.

Here's my updated kernel and Xorg version info:

➜  ~ Xorg -version

X.Org X Server 1.18.3
Release Date: 2016-04-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.13.0-91-generic x86_64 Ubuntu
Current Operating System: Linux hyperion-stfs 4.4.0-31-generic 
#50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 UTC 2016 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=285091fd-ac1a-4801-8055-c356ab9083a5 ro quiet splash vt.handoff=7
Build Date: 03 July 2016  09:17:03AM
xorg-server 2:1.18.3-1ubuntu2.2~trusty1 (For technical support please see 
http://www.ubuntu.com/support) 
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.


➜  ~ uname -a
Linux hyperion-stfs 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 01:07:32 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

-- 
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/1598904

Title:
  X server crashes sporadically with a segfault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1598904/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Lukáš Tinkl
gsettings-ubuntu-touch-schemas has the default values

** Also affects: gsettings-ubuntu-touch-schemas (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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Daniel van Vugt
** Changed in: qtubuntu
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: qtubuntu (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: qtubuntu
   Importance: Undecided => High

** Changed in: qtubuntu (Ubuntu)
   Importance: Undecided => High

** Changed in: qtubuntu
   Status: New => In Progress

** Changed in: qtubuntu (Ubuntu)
   Status: New => In Progress

-- 
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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Daniel van Vugt
** Also affects: qtubuntu (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: qtubuntu
   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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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 1578011] Re: Laptop sometimes doesn't detect external monitor when docked

2016-07-29 Thread red_hood
It seems also just switching displays makes the kernel upset, please see
attached dmesg output. Also, please consider making
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568573 a
duplicate, as it seems to involve the same cases and error messages.

** Attachment added: "dmesg-switch-displays"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+attachment/4709293/+files/dmesg-switch-displays

-- 
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/1578011

Title:
  Laptop sometimes doesn't detect external monitor when docked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1578011/+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 1590553] Re: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly)

2016-07-29 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu4

---
xorg-server (2:1.18.4-1ubuntu4) yakkety; urgency=medium

  * debian/patches/xmir.patch:
- Fix button/menu focus failures (LP: #1590553)
- Implement XWMHints properly
- Add smooth touchpad scroll support (LP: #1603917)
- Fix key repeat order
- Remove links to Unity8 bugs that are now fixed.

 -- Robert Ancell   Thu, 28 Jul 2016
14:31:22 +1200

** Changed in: xorg-server (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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/1590553

Title:
  Xmir -rootless: Buttons are randomly unclickable (popups vanish
  instantly)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1590553/+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 1603917] Re: [enhancement] Implement smooth scrolling in Xmir (like Xwayland)

2016-07-29 Thread Launchpad Bug Tracker
This bug was fixed in the package xorg-server - 2:1.18.4-1ubuntu4

---
xorg-server (2:1.18.4-1ubuntu4) yakkety; urgency=medium

  * debian/patches/xmir.patch:
- Fix button/menu focus failures (LP: #1590553)
- Implement XWMHints properly
- Add smooth touchpad scroll support (LP: #1603917)
- Fix key repeat order
- Remove links to Unity8 bugs that are now fixed.

 -- Robert Ancell   Thu, 28 Jul 2016
14:31:22 +1200

** Changed in: xorg-server (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
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/1603917

Title:
  [enhancement] Implement smooth scrolling in Xmir (like Xwayland)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1603917/+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 1606103] Re: modeset driver is missing some modes that the intel driver had

2016-07-29 Thread Rocko
Thanks for the info.

So it turns out that the problem is that the modesetting driver is
pruning these modelines because it thinks their vertical refresh is
greater than the max vrefresh.

The function in question is
hw/xfree86/drivers/modesetting/drmmode_display.c#add_gtf_modes(), and it
is calculating refresh rates between 65 and 85 but thinks that the max
vrefresh is 60.58 because of these lines:

max_vrefresh = max(max_vrefresh, 60.0);
max_vrefresh *= (1 + SYNC_TOLERANCE);

However, I can see from the MonPtr variable passed to
hw/xfree86/modes/xf86Modes.c#xf86ValidateModesSync() that the driver has
figured out a range of 56.25 to 120 for this screen, so my guess is that
it shouldn't be restricting the max to 60 plus 1% in add_gtf_modes().

Looking at get_modes(), which calls add_gtf_modes(), it is also
extracting a MonPtr variable from the EDID, so perhaps it could pass
this pointer to add_gtf_modes() and add_gtf_modes() could use the actual
maximum vertical refresh for the monitor instead of locking it to 60.

-- 
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/1606103

Title:
  modeset driver is missing some modes that the intel driver had

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1606103/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

2016-07-29 Thread Emanuele Antonio Faraone
I confirm that the atom N470 processor is affected by this bug.

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Daniel van Vugt
** Changed in: qtmir
   Importance: Undecided => High

** Changed in: qtmir (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => High

-- 
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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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 1607240] Re: Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

2016-07-29 Thread Daniel van Vugt
** Branch linked: lp:~vanvugt/qtmir/fix-1607240

** Also affects: qtmir
   Importance: Undecided
   Status: New

** Changed in: qtmir
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: qtmir
   Status: New => In Progress

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

-- 
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/1607240

Title:
  Unity8 default mouse wheel speed is 7.0 (it should be 1.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607240/+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