As we discussed on the maillist in the end of July, this is not a
blocker to our certifcate and we should create a greylist note for this.
** Tags removed: blocks-hwcert
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in
** Tags added: 201405-15042 blocks-hwcert taipei-lab
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1309550
Title:
Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-
HP Pavilion 15 Notebook PC (CID 201405-15042) has a similar issue.
00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Richland [Radeon HD 8610G] [1002:990f]
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz
XT [Radeon R7 M260/M265] [100
Ok, I found where to download the .src.rpm's for the two Fedora packages
and compare the included patches.
This bug is fixed by upstream commit 48a33fc379b17eed195875222ad773c911d9dff1:
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=48a33fc379b17eed195875222ad773c911d9dff1
--
Link to Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1133142
They had the bug in xorg-x11-drv-intel-2.99.914-2.fc21.x86_64 and
included the fix in xorg-x11-drv-intel-2.99.914-3.fc21. If I were more
familiar with Fedora's infrastructure I'm sure I could find the patch
with the backporte
The mtrack driver does allow finger resting in the bottom area, but I
found it to be too rough around the edges in other areas that I couldn't
use it. The cursor tracking feels weird and unnatural to me. It would
also seem to accelerate when I would approach the bottom of my screen.
Also, it seem
Noah E Crocker, thank you for your comment. So your problem and hardware may be
tracked, could you please file a new report with Ubuntu by executing the
following in a terminal while booted into the default Ubuntu kernel (not a
mainline one) via:
ubuntu-bug linux
For more on this, please read t
I still have this exact same problem on 14.04 x64 (but it's been around
since 12.04). It happens on new installs of either Ubuntu release.
Thankfully, the workaround here still functions and saved me a lot of
trouble ("modprobe -r usbhid" followed by "modprobe usbhid"). The only
alternative is to
This affects me too on Ubuntu Gnome 14.10 with Lenovo Yoga 13 and Intel HD
4000. Basic gnome animations are slow, or better said, they always get at least
one lag during animation. I have to say that I played with unity and unity8,
then uninstalled it.
ibus-gtk was installed so this was no fix f
I followed your advice and multiseat setup still works. And still seat-1
resume problem remains.
I noticed that if I do (as root) a number of commands like:
# DISPLAY=:1 XAUTHORITY=/var/run/lightdm/root/:1 xrandr --output DVI-I-2 --off
# DISPLAY=:1 XAUTHORITY=/var/run/lightdm/root/:1 xrandr --out
Anyway, have you tried to simplify your config files? For example, in your
udev rules, you don't need to tag anything as "seat0" explicitly, and in
your xorg.conf file, are you sure you need all that "Screen" and
"ServerLayout" sections? In principle just the "Device" sections would be
enough.
--
I GOT ENLIGHTENED.
I know what changed since yesterday. I don't have my printer installed
in the multisesat ubuntu, so I'm ocassionally booting into my Debian
install where I have my multiseat setup based on a Xephyr approach,
where both monitors are connected to the two heads of JUST ONE of the
g
*** This bug is a duplicate of bug 1338492 ***
https://bugs.launchpad.net/bugs/1338492
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1338492, so is being marked as such.
More details on todays behaviour:
After boot both screens come up, but sometimes seat-1 does appear,
sometimes not and instead seat0 display extends to both monitors.
Regardless of whether seat-1 appears or not, the initial position of
mouse pointer of seat0 is offset BUT related to seat0's monito
You could also disable light-locker for user logged in seat-1 and see if
problem persists.
Em qua, 17 de dez de 2014 18:44, Laércio de Sousa
escreveu:
> What about your lightdm.log file? And your Xorg.1.log? Any suspect
> message?
>
> Em qua, 17 de dez de 2014 18:41, Andrzej Pietrasiewicz <
> an
What about your lightdm.log file? And your Xorg.1.log? Any suspect
message?
Em qua, 17 de dez de 2014 18:41, Andrzej Pietrasiewicz <
andrzejtp2...@gmail.com> escreveu:
> Regarding the doubt whether not coming back of seat-1 greeter is caused
> by the screenscaver kicking-in: that is not the case.
John Ellis, given the issue happens in both Windows and Ubuntu, if a
firmware update is available for the TV, that would want to be applied.
Despite this, you should still be able to make the same WORKAROUND
adjustment in Windows as you do in Ubuntu. Would using arandr and the
nouveau driver allow
Regarding the doubt whether not coming back of seat-1 greeter is caused
by the screenscaver kicking-in: that is not the case. I checked again
and did a quick suspend and then resume and then looked up the
x-1-greeter.log and there was no line about the screensaver. It does
activate but far later th
Before suspend:
UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD
root 1236 1223 12 55708 73248 0 20:56 tty7 00:00:10 /usr/bin/X -core
:0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
root 1238 1223 2 36801 64892 0 20:56 ?00:
Oh sorry! I didn't catch your lightdm.conf above.
When you restart lightdm service, all Xorg processes are killed and then
restarted. That's why your seat-1 goes back to normal when you do that.
I suspect your seat-1 Xorg may be killed when suspending. You can confirm
it by running "ps -FC Xorg |
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1402966
Title:
libxcb new version 1.11
To manage notifications about this bug go to:
https://bugs.launch
I have two discrete cards. So the difference is that your integrated
card is probably on the "platform bus", while both of my discrete cards
are PCI-E devices.
I started testing multiseat setup described in this thread only last
Saturday and since then have always been using the lightdm version wh
Is this still occurring on Ubuntu 14.10 "Utopic Unicorn"?
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
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/1305334
Title:
Mesa 10 (9)
I woul like to update this issue to say that this problem still happens
with the latest Catalyst 14.12.
--
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/1390234
Title:
Unity desktop mis
** Summary changed:
- nvidia-331-updates installed by an xserver-xorg-core upgrade prevent GNOME
shell to start
+ nvidia-331-updates wrongly installed by an upgrade prevent GNOME shell to
start
** No longer affects: xorg-server (Ubuntu)
** Changed in: nvidia-graphics-drivers-331-updates (Ubunt
Hello Christopher M. Penalver:
The driver I previously tested, when
I still was using the old 1.41 bios, was the :
NVIDIA binary driver -version 331.113 from nvidia-331-updates
(proprietary).
tv/monitor (Sharp LC-32D62U) via a dvi/hdmi 10 foot cable to #4 hdm
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Critical
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Summary changed:
- nvidia-331-updates installed by update p
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1403287
Title:
Missing Mouse-Cursor After Login
To m
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity (Ubuntu)
Status: New => Invalid
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
using wine
stn wrong in amd64
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu8
Architecture
Unfortunately, I can't reproduce your error in my hardware. Both seats
wake up correctly here.
My hardware consists of an integrated Intel graphics device and a
Silicon Motion SM501 PCI graphics card. I'm also using Xubuntu with
lightdm 1.10.3 from trust-updates repo.
BTW, did you upgrade your li
Public bug reported:
Hi
This Friday i updated me system on laptop and rebooted.
And system don't want to boot. I attached external keyboard to laptop and by
boot saw kernel panic leds blinking.
But i don't get any messages on my screen(external screen to).
So i reinstalled my ubuntu 12.04(pure
I can still reproduce this issue on the same system with linux-generic-
lts-utopic 3.16.0.28.21
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits)
OpenGL version string: 2.1 Mesa 10.1.3
Not software rendered:no
Not blacklisted:
I can confirm this problem for Ubuntu 14.10 with a radeon card. It might also
be the problem in Lubuntu:
http://forum.ubuntuusers.de/topic/nach-xorg-update-bildschirm-an-hdmi-fuehrt-zu-/
and https://bugs.launchpad.net/mythbuntu/+bug/1402605
** Attachment added: "Xorg log.txt"
https://bugs.lau
34 matches
Mail list logo
