*** Bug 78317 has been marked as a duplicate of this bug. ***
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR:
The intel_reg_dump of intel-gpu-tools v1.6 works fine.
** Also affects: xserver-xorg-video-intel
Importance: Undecided
Status: New
** Project changed: xserver-xorg-video-intel = oem-priority
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
The intel_reg_dumper raise SIGABRT on Intel ValleyView Gen7 [8086:0f31]
platform.
# sudo intel_reg_dumper
Gen2/3 Ranges are not supported. Please use unsafe access. (Core dump)
** Affects: oem-priority
Importance: Undecided
Status: New
** Affects:
Public bug reported:
I installed fglrx 12.6 as the latest stable for AMD RADEON HD 6630M
(since any later just crash X) and this error shows up every time I boot
up
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fglrx 2:8.980-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic
Hello again
I did a dist-upgrade last night and it seems to have fixed the issue,
although I've only had time to check it twice today before I had to rush
off to work!
Thank you very much!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Took the liberty of correcting the bug title as unity does keep getting
touch events. It's the xserver mouse pointer emulation from touch events
that breaks badly.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106243/+files/BootLog.txt
--
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/1307009
apport information
** Tags added: apport-collected ubuntu
** Description changed:
After my PC having been suspended and waked up, my second screen appears to
be disconnected, and as far as I can see, the only way to get out is a reboot.
My first screen is VGA1, the second is HDMI1.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106244/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106245/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106249/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106248/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106247/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106246/+files/DpkgLog.txt
--
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/1307009
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106253/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106254/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106252/+files/Lsusb.txt
--
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/1307009
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106258/+files/UdevLog.txt
--
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/1307009
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106259/+files/XorgLog.txt
--
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/1307009
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106257/+files/UdevDb.txt
--
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/1307009
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106262/+files/xdpyinfo.txt
--
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/1307009
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106263/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106250/+files/LightdmLog.txt
--
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/1307009
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106251/+files/Lspci.txt
--
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/1307009
Title:
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106256/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106255/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106261/+files/Xrandr.txt
--
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/1307009
Title:
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1307009/+attachment/4106260/+files/XorgLogOld.txt
--
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/1307009
** Tags added: 201305-13641
--
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/1301839
Title:
AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with
Trusty
To
(In reply to comment #66)
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after discussion on this site.
I realise there
(In reply to comment #66)
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after discussion on this site.
I realise there
TEST CASE:
1. Install 14.04 on 201305-13641
2. Boot to make sure this issue exist.
3. Reboot with nomodeset parameter in grub, enable proposed, upgrade.
4. Reboot without nomodeset parameter in grub
VERIFICATION DONE
Expected result:
* You won't be asked to enter the low-graphic mode after step
Attaching detailed xserver log. The following steps were taken:
1- sudo restart lightdm (to restart the X server. so that de have a clean slate)
2- run a very simple qml app with qmlscene
3- tapped on that qmlscene window (touch id 1)
4- tapped on the desktop area (nautilus) (touch id 2)
5- sudo
xserver packages I used to take the logs above.
** Attachment added: xserver debian packages with detailed logging of input
events
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307701/+attachment/4106288/+files/xorg_debug_packages.zip
--
You received this bug notification because
Public bug reported:
I have a 16/10 17inch screen and a graphic card nVidia GeForce. Starting UBUNTU
14.04 after upgrade, the process abort with a little window saying Correct
screen resolution not found (or something like that). With UBUNTU 13.10 I used
a 1400x900 screen size.
Hopefully I can
Excerpt from #xorg-devel:
dandrader daniels, I've the following situation: clientX has a
XISelectEvents(TouchBegin|Update|End, childWindowA, slaveDevice1); clientY has
a XIPassiveGrabDevice(TouchBegin|Update|End|Ownership, rootWindow,
AllMasterDevices)
daniels, when a touch reaches xserver,
The NVRM log messages stopped after reinstalling nvidia-331, but the
system continued to use nouveau, and hence to crash (bug 1243557).
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]
I don't know how that (which blacklists nouveau) came to be missing, but
purging and
Is there a specific reason for calling XISelectEvents() for each slave
vs using XIAllMasterDevices in QXcbConnection::xi2Select() in Qt?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Is there a specific reason for calling XISelectEvents() for each
slave vs using XIAllMasterDevices in QXcbConnection::xi2Select() in Qt?
Would have to dig into Qt code to tell that. But my guess is that
because it exposes QTouchDevice objects to applications. For every
QTouchEvent you can get
The code in Qt that subscribes to slave device events is the explicit
tablet-handling code. Checking the code, the touchscreen on my Dell XT2
is being treated as a tablet by the Qt code because it supports a stylus
mode on one of its alternate devices.
It sounds like the bug is in the Qt XCB QPA
Public bug reported:
troppo macchinosa ! meglio 11.04
grazie
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
I think the XIDeviceEvent.sourceid would tell you from which device it
originates. The XIDeviceEvent.deviceid member would be set to the
master device, which might break things in a straight conversion.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
(In reply to comment #69)
…
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after discussion on this site.
I
(In reply to comment #69)
(In reply to comment #66)
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after
(In reply to comment #69)
…
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after discussion on this site.
I
(In reply to comment #69)
(In reply to comment #66)
Regarding the voting, is there generic popular Linux-oriented site in
France? Like slashdot.org or smth...
There is a popular Linux-oriented site in France (linuxfr.org) and the
final ajustments of this layout were done after
@Stephen: I guess that means that your device passes the following
check:
if (tabletData.valuatorInfo.contains(QXcbAtom::AbsX)
tabletData.valuatorInfo.contains(QXcbAtom::AbsY)
tabletData.valuatorInfo.contains(QXcbAtom::AbsPressure))
which you can check using xinput list-props
I updated to Ubuntu 14.04 and I still have the same symptoms and error
messages as before. I also want to note that I started having these
symptoms while using 12.04 (but only since about January, I ran 12.04 up
to that point with no issues).
I'm still working on the BIOS update issue.
--
You
I've just rebuilt Qt with a partial fix which only covers the non-
tablet test case, and I'm glad to report that it solves the problem.
Maarten is working on an all comprehensive fix.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server
And here's the upstream bug I reported:
https://bugs.freedesktop.org/show_bug.cgi?id=78345
** Bug watch added: freedesktop.org Bugzilla #78345
https://bugs.freedesktop.org/show_bug.cgi?id=78345
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
(In reply to comment #72)
The old layout was never removed and kept its historical name (fr latin9)
No, we are speaking here of fr/oss, but before it got right Ctrl as
level5 modifier (what this bug end up changing).
I bet everyone complaining here was very happy with fr/oss before this
Level5
(In reply to comment #70)
If no agreement can be reached, would it be possible to have the old layout
accessible, even under another name?
The old layout was never removed and kept its historical name (fr
latin9)
--
You received this bug notification because you are a member of Ubuntu-X,
(In reply to comment #71)
And even if we wanted to please those apps, we mayb be able to without
adding a new modifier (Level5) and a key for it -- again, see (comment #46).
I'm pretty sure some of the other spacebar configurations available as
xkb options do not require level5. They are not
(In reply to comment #70)
If no agreement can be reached, would it be possible to have the old layout
accessible, even under another name?
The old layout was never removed and kept its historical name (fr
latin9)
--
You received this bug notification because you are a member of Ubuntu-X,
(In reply to comment #72)
The old layout was never removed and kept its historical name (fr latin9)
No, we are speaking here of fr/oss, but before it got right Ctrl as
level5 modifier (what this bug end up changing).
I bet everyone complaining here was very happy with fr/oss before this
Level5
(In reply to comment #71)
And even if we wanted to please those apps, we mayb be able to without
adding a new modifier (Level5) and a key for it -- again, see (comment #46).
I'm pretty sure some of the other spacebar configurations available as
xkb options do not require level5. They are not
Converting to a question because user is running unsupported kernel.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/xorg/+question/248273
--
You received this bug notification because you are a member of
Same issue here with an NVidia card, whether I use the open source
drivers or the proprietary ones.
--
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/1310071
Title:
Low graphics
The bug is not fixed, opening the lid after suspend mod, i see blank
screen of my monitor (graphics: amd 5650 mobile series , processor:
core i5 240m)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
I meant
sudo apt-get install --reinstall unity-greeter
unity, not ubuntu.
Apologies - I'll stop posting now!
--
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/1310071
Title:
Resolved for me (on NVidia) with the following commands
sudo apt-get install --reinstall ubuntu-greeter
sudo dpkg-reconfigure lightdm
And a reboot.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
Yes, that's true, sorry false alarm from me, but it really truly did
work this morning, but as soon as I got home same issue, I wish I knew
what I did right. I'm afraid I'm still very much a novice when it comes
to Linux, only did the switch a few months ago I don't know how to do an
information
Tried Cloudane's solution, but with no luck. Same problem.
--
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/1310071
Title:
Low graphics mode on logout
To manage notifications
This is an old Ubuntu 11.10 bug, can I just set it to Invalid? I'll just
set it to Invalid...
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (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/1314587
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (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/1314587
Title:
@Casey Maybe you can dive into your /var/log directory. If you are that
novice you can make use of a graphical log viewer that you can install
from the ubuntu software centre. One or two logs where you can start is
/var/log/messages or /var/log/Xorg.xxx or even /var/log/boot to see if
there was
@Casey Sorry for double posting but I forgot one important log and can't
find an edit button or option. Chechk your /var/log/pm-suspend.log too
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
Created attachment 98589
Kernel 3.14.2-1-ARCH, xf86-video-intel 2.99.911-2, mesa 10.1.2-1
--
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/1041790
Title:
[snb] GPU lockup
Seems this bug still persists in 14.04
I use 'xset dpms 0 0 1200 -dpms s off s noblank s noexpose' in my
.profile but something keeps switching dpms back on.
Even if I use xset -dpms in a teminal something re-enables it.
I am also suffering from having to hit a key every 10 mins or so when
Some additional comments:
dpms gets reactivated whether I am plugged in or running on battery.
There have been occasions when dpms has not been reactivated and I can
watch a full movie without being bothered by the dpms notifications,
though I have not identified any pattern to this.
--
You
Public bug reported:
This problem has plagued me for a few years across different laptops
and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
15z running Ubuntu 14.04 LTS.
It typically starts after I have used the chat or call feature in gmail,
by clicking on the phone icon
*** This bug is a duplicate of bug 859101 ***
https://bugs.launchpad.net/bugs/859101
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 859101, so it is being marked as such. Please look
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
You have been subscribed to a public bug:
See the letters in the alphabet when I typed with care
abxcsdefghijklmnopqrstuvwxyz
abxcsdwefghijklmnopqrstuvwxyz
ABCXSDEFGHIJKLMNOPQRSTUVWXYZ
ABCXSDWEFGHIJKLMNOPQRSTUVWXYZ
So I can't log in my Administration section without onscreen keyboard.
**
** Package changed: ubuntu = xorg (Ubuntu)
--
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/1315608
Title:
Keyboard supplies some extra letters
To manage notifications about this bug go to:
Same on Thinkpad X220 Tablet
--
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 after suspend/resume
To manage notifications about this bug go to:
Sorry, apparently the above patch was already added to the proper,
xserver-xorg-core package.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev
78 matches
Mail list logo
