Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include check
Added a "Mir" task back in, temporarily just so the team can find this
bug.
** Summary changed:
- [regression] Mir GL clients crash immediately on startup (Mesa is trying to
use X11 instead of Mir)
+ [regression] Mir 0.6 GL clients crash immediately on startup (Mesa is trying
to use X11 instead
Actually, make it "New" for Mir. If there's some symbol we've
accidentally hidden then that's a Mir bug.
** Changed in: mesa (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.
At a guess we removed/changed some symbol in libmirclient (yesterday)
and that prevents libEGL from finding/using libmirclient properly.
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Importance: Undecided => Critical
** Changed in: mir
Status: New
** Project changed: mir => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Milestone: 0.6.0 => None
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Chris Halse Rogers (raof)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubu
You have been subscribed to a public bug:
[regression] Mir GL clients crash immediately on startup.
This is on a freshly updated utopic system.
(gdb) bt
#0 0x7ff4f1b706d7 in XGetXCBConnection ()
from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1
#1 0x7ff4f352abb1 in dri2_initialize_x11_
** Tags removed: need-duplicate-check
--
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/1350104
Title:
package fglrx (not installed) failed to install/upgrade: subprocesso
novo script
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
Hello Dylan, or anyone else affected,
Accepted xorg-server into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.15.1-0ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. S
Hello Alberto, or anyone else affected,
Accepted xorg-server into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.15.1-0ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Benjamin, or anyone else affected,
Accepted xorg-server into trusty-proposed. The package will build now
and be available at http://launchpad.net/ubuntu/+source/xorg-
server/2:1.15.1-0ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Spoke too soon... Just crashed again :-(
It is certainly more stable though under 14.04 but not 100%
--
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/1184451
Title:
Ubuntu 13.10 random scr
** Summary changed:
- nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict
+ Packages nvidia-libopencl1-* should provide libopencl-1.1-1
** Changed in: nvidia-cuda-toolkit (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1307792 ***
https://bugs.launchpad.net/bugs/1307792
** This bug has been marked a duplicate of bug 1307792
nvidia-opencl-dev depend on nvidia-libopencl1-331 is too strict
--
You received this bug notification because you are a member of Ubuntu-X,
which i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304-updates
** Summary changed:
- [xorg-edgers] OCL-ICD provides a free generic OpenCL implementation, should
ubuntu policy be to build applications against this loader vs closed vendor
implementations
+ Build dependency on virtual libopencl1 with no default
--
You received this bug notification because y
Public bug reported:
mousepad stoped working after last update
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.2
** Also affects: viennacl (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fglrx-driver (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed => Invalid
** Changed in: ocl-icd (Ubuntu)
Status: Confirmed =>
** Branch linked: lp:ubuntu/trusty-proposed/nvidia-graphics-
drivers-331-updates
** Branch linked: lp:ubuntu/trusty-proposed/nvidia-graphics-drivers-331
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https
Hello Jorma, or anyone else affected,
Accepted nvidia-graphics-drivers-331 into trusty-proposed. The package
will build now and be available at http://launchpad.net/ubuntu/+source
/nvidia-graphics-drivers-331/331.38-0ubuntu7.1 in a few hours, and then
in the -proposed repository.
Please help us b
Hello Jorma, or anyone else affected,
Accepted nvidia-graphics-drivers-331-updates into trusty-proposed. The
package will build now and be available at
http://launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-331-updates/331.38-0ubuntu7.1 in a few hours, and then in the
-proposed repository.
Public bug reported:
With the hardware as shown in automatically attached files (HP ProBook
455), display never recovers from resume, although the computer works
fine otherwise (it can be connected to over ssh, in particular). I
disabled the discrete GPU BIOS (that is the current stand) but the
pr
FWIW, this is the output of radeontool ("sudo radeontool light on" had
no effect at all):
$ sudo radeontool regs
RADEON_DAC_CNTL
RADEON_DAC_EXT_CNTL
RADEON_DAC_MACRO_CNTL
RADEON_DAC_CNTL2
RADEON_TV_DAC_CNTL c100a080
RADEON_DISP_OUTPUT_CNTL
** Changed in: fglrx-installer (Ubuntu)
Importance: Undecided => Medium
--
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/1349785
Title:
Unable to open AMD Catalyst Control Center (Ad
Created attachment 103307
system log nouveau kernel linux-3.16 branch
I've compiled the kernel on the linux-3.16 branch from
http://cgit.freedesktop.org/nouveau/linux-2.6/ and X still freezes but now it
recovers temporarily.
After it I can close the program that caused the freeze and then I can
Created attachment 103302
system log
--
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/1243557
Title:
10de:1056 [Dell Latitude E6520] [NVS 4200M] X freeze, "unhandled
status
Hi, sorry for barging in but I'm also hitting this on the same graphics card
(NVS 4200M) on a Dell Latitude E6520 running Arch Linux.
I'm trying to use PRIME for a VA-API + VDPAU setup and also for some games but
as soon as I start I get this message in dmesg :
kernel: nouveau E[ PFIFO][:0
Public bug reported:
When trying to open the AMD Catalyst Control Center in Administrative
mode by using the launcher found in dash, you will be ask to enter
password for it, but it always shows "su: authentication failure" and
exit.
Steps:
1. Install 14.04 on a I+A system, boot to desktop
2. Try
Still affected by this bug in 13.04
Media keys are only partially supported.
Unsupported keys:
Reset zoom (no keycode)
Zoom in (keycode 418)
Zoom out (keycode 419)
Word key (keycode 421)
Excel key (keycode 423)
Powerpoint key (keycode 425)
Launch A (keycode 328)
Launch B (keycode 329)
Launch C (ke
Public bug reported:
https://launchpad.net/debian/sid/+source/mesa
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: mesa-common-dev 10.2.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: am
Adding SUSPEND_MODULES="wacom wacom_w8001" to /usr/lib/pm-utils/defaults works
for me.
Thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-input-wacom in Ubuntu.
https://bugs.launchpad.net/bugs/807620
Title:
Fixes tablets not working
Sorry for noise. Following Comment #2 in Bug 807620 seems to have fixed
the problem for me.
Specifically, in /usr/lib/pm-utils/defaults I uncommented the #
SUSPEND_MODULES="" line
and replaced it by SUSPEND_MODULES="wacom wacom_w8001".
When I resume my stylus & touch screen work.
--
You receiv
I have a Lenovo x201 tablet running 14.04.1 LTS. Neither of the
workarounds in #7, #15 restore the stylus.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1275416
Title:
touchscreen do not work
33 matches
Mail list logo
