I beleive that total stack has proper support for this now.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
Well, this still happenens in kubuntu 14.04 daily running in virtual-
box.
--
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/1228587
Title:
When selecting two cell and draggin them X locks up.
To
Well - forget all about my local system. It does still happen within
VirtualBox running current saucy daily dail.
--
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/1228587
Title:
When selecting
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839437/+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/1228587
apport information
** Tags added: apport-collected has-fix has-workaround kubuntu
reproducible saucy single-occurrence
** Description changed:
Steps to reproduce :
1. Start libreoffice-calc
2. Select 2 cells
3. Try to draw the cells to another location
Actual result:
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839440/+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/1228587
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839445/+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/1228587
Title:
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839443/+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: Dependencies.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839439/+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: Lsusb.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839446/+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/1228587
Title:
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839441/+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: LightdmLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839444/+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/1228587
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839442/+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: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839438/+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: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839448/+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: ProcModules.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839450/+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: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839447/+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: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839449/+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: UdevLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839452/+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/1228587
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839451/+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/1228587
Title:
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839456/+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/1228587
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839455/+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/1228587
Title:
It works now on my local saucy install - but the daily-build still fails
the same way. Maybe the daily build is not updated yet. I will return
again with more information when the daily build has been updated.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839457/+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: XorgLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839453/+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/1228587
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839454/+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/1228587
Hmmm ... where is that commit I can't find it in linus' kernel
tree.
--
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/1184867
Title:
Xorg crashed with intel_dri backtrace
Thanks
--
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/1184867
Title:
Xorg crashed with intel_dri backtrace whil attending a google hangout
To manage notifications
Public bug reported:
Basically I just enter a hangout and then after a while - 30 seconds or so -
the system crashes with this backtrace
[ 432.229] (EE)
[ 432.230] (EE) Backtrace:
[ 432.250] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb7751f99]
[ 432.258] (EE) 1: /usr/bin/X
Public bug reported:
I was running a git gc command, when suddenly Xorg crashed
The trace smells like a memory allocation problem.
[ 2231.463] (EE) intel(0): Failed to submit batch buffer, expect rendering
corruption or even a frozen display: No space left on device.
[ 2231.467] (EE)
[
Fixed in current maverick.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete = Fix Released
--
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/612853
It fixes it for me too. Great job Robert! I hope is gets into maverick.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of Ubuntu-X,
which is a direct subscriber.
Problably not. Would it be possible to cherry-pick commit
726210f87d558d558022f35bc8c839e798a19f0c for maverick?
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of
Can we do anything to help getting the lastest libdrm into maverick? I
can add that radeon-chipsets behave much better with the current version
in the ppa.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this
Just run apt-get upgrade. I your ppa is set up correctly it will upgrade the
relevant packages.
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of Ubuntu-X,
which
It gone from my side.
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
https://bugs.launchpad.net/bugs/607490
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
Try the xorg-edger packages - they fix the issue. Maybe if we are enough
to try them they can get into maverick
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of
Excellent.
Ubuntu guys: Would it be possible just to include the libdrm-fix in
maverick when it ships ?
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of
I have just installed the xorg-edgers packages. It works *really* nice.
I would really hope that it gets into maverick. I remember karmic that
shipped with realy broken intel drivers. It would be a real shame to
repeat that.
--
[maverick] Non-mirrored dual-screen gives narrow display on
Is this bug the same issue ?
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/612853
--
[maverick] Non-mirrored dual-screen gives narrow display on secondary monitor
https://bugs.launchpad.net/bugs/619663
You received this bug notification because you are a member of
Are you guys aware of this bug. Seems similar.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/619663
--
Dual screen setup does noet work properly
https://bugs.launchpad.net/bugs/612853
You received this bug notification because you are a member of Ubuntu-X,
which is
As of now it is fixed for me now. Problably it is the grub-pc update to
version 1.98+20100804-4ubuntu1
The log includes this :
* Go back to gfxpayload=text by default for Ubuntu 10.10, as the kernel
needs more work to avoid lockups with some video cards
Seems to be the change that fixes
I can add that the add one space-solution does not work for me ;(
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
https://bugs.launchpad.net/bugs/607490
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Yeah that does not surprise me. As I wrote ealier I just had to enter the
editing mode in grub while booting, change nothing, and press CTRL-x to boot.
It works everytime. Have you tried that also ?
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
I have nvidia-current 256.44 installed now. But it behaved the same.
If I let the system boot normally I end up in low graphics mode.
If I interrupt grub and press 'e' to edit the item it will boot, and press
CTRL-x to actually boot it everything is ok. My system starts up perfectly X
starts
Yes. Just entering grub and looking at the options is enough. But the laster
couple of day since the Xorg upgrade the problems have progressed. It seems
like the proprietary driver is no longer compatible wilth Xorg. So it is not
100% improsible to use anything else than nouveau.
--
Xorg
I'll try xorg-edgers-ppa and report back how it behaves.
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
https://bugs.launchpad.net/bugs/607490
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers
Public bug reported:
Binary package hint: xserver-xorg-video-intel
When setting my LVDS1-ouput to be place left of my DVI1-output I
actually get picture on both.
My setup is like this :
-- -
| LVDS1 | | DVI1 |
-- -
LVDS1 has a resolution of 1400x1050 and
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/52969614/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/52969615/CurrentDmesg.txt
** Attachment added: DRM.card0.SVIDEO.1.txt
Great .. do you have any ideas as to what to try to hunt it down.
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
https://bugs.launchpad.net/bugs/607490
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Read further down . for me the real difference is weither I enter grub or
not.
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
https://bugs.launchpad.net/bugs/607490
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Try 10.10 - if the problem is still there it is easier to do something
when it is a development release I think.
--
MASTER: xorg high cpu usage, general system sluggishness
https://bugs.launchpad.net/bugs/294972
You received this bug notification because you are a member of Ubuntu-X,
which is
Try 10.10 - if the problem is still there it is easier to do something
when it is a development release I think.
--
MASTER: xorg high cpu usage, general system sluggishness
https://bugs.launchpad.net/bugs/294972
You received this bug notification because you are a member of Ubuntu-X,
which is
Try 10.10 then. If the problem is still there it is easier to fix when it is a
development version.
--
MASTER: xorg high cpu usage, general system sluggishness
https://bugs.launchpad.net/bugs/294972
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I have found that my work-laptop containing an intel chip also has
issues. It sometimes end up in low-graphics mode. But on that machine it
always works to just restart Xorg.
So something races during boot in relation to graphics. How is it
decided that low graphics-mode should be initiated?
--
Have you tried 10.04 ... or 10.10 development-version ?
--
MASTER: xorg high cpu usage, general system sluggishness
https://bugs.launchpad.net/bugs/294972
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.
To sum up.
My system always boots on the low graphics mode,
When in low graphics mode and I press CTRL-ALT-F1 to get to the console,
there is usualy no text.
BUT if there are text I can restart X and get the nvidia dirver up and
running.
If I during boot enter grub and press 'e' to edit,and
Even though removing splash from the kernel commandline it only works
when doing it manualy from grub during boot. Removing splash from
menu.cfg does not work. So I'm fearing it might be related to something
that grub does when it displays the menu.
Do you guys have any ideas as to what I could
2.6.35-10-generic fixes this issue. So I guess it was a kernel thing
afterall. :D
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New = Fix Released
--
Xorg fails with NVIDIA(0): Failed to allocate primary buffer: out of memory.
https://bugs.launchpad.net/bugs/607490
You received
I was too fast on fast. On most boots it fails, but on some it doesn't.
When booting with 2.6.35-10 that was the case. Anyway, this nevertheless
not fixed.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Fix Released = New
--
Xorg fails with NVIDIA(0): Failed to allocate primary
Apparently disabling boot splash by removing splash from the kernel
commandline is also a workaround for this issue. So I to not thnik it is
a kernel-issue anymore. So I changed it to nvidia-current because both
linux-image and nvidia-current had been was upgraded prior.
** Package changed: linux
Hi pc contains this.
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS,
943/940GML Express Integrated Graphics Controller (rev 03)
Xv works fine here, even with the current 2.9-driver
BUT whenre running a dual-screen configuration is does not work with any
driver. Is that a
I have Xv running fine here. But only in a single monitor configuration.
As soon as I add a second monitor Xv stops working. It works again when
going back to a single monitor though. My lspci looks like this.
00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and
945GT
agree
--
The key repeat delay for the down-arrow, left-arrow, and End keys is
longer than the other keys
https://bugs.launchpad.net/bugs/278078
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in ubuntu.
Apparently it can still happen. I'm running AJuty with 2.6.30 and newest
intel-drivers from X-swat PPA
--
Xorg driver locks up and screen goes blank (black) -
i915_gem_retire_work_handler+0x2a/0x70
https://bugs.launchpad.net/bugs/384960
You received this bug notification because you are a
65 matches
Mail list logo
