[Ubuntu-x-swat] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution

2021-01-21 Thread Dale Sch.
Same issue with my Ultrawide. Workaround: xrandr --newmode "2560x999_60.00" 211.75 2560 2720 2984 3408 999 1002 1012 1037 -hsync +vsync xrandr --addmode Virtual1 2560x999_60.00 xrandr --output Virtual1 --mode 2560x999_60.00 -- You received this bug notification because you are a member of Ubu

[Ubuntu-x-swat] [Bug 1396361] Re: Double Mouse Cursor

2015-01-27 Thread Dale
Is this bug a result of a particular brand or model of mouse? I am using a logitech m215 external usb mouse. -- 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/1396361 Title: Double Mouse Cursor

[Ubuntu-x-swat] [Bug 1396361] [NEW] Double Mouse Cursor

2014-11-25 Thread Dale
Public bug reported: When dragging with the mouse cursor often it creates a double cursor side by side about 10 cm apart on the screen. Only one cursor works. Using print screen does not show the cursor in the resulting image. Rebooting corrects the problem. This is similar to the double mouse c

[Ubuntu-x-swat] [Bug 1388411] [NEW] numlockx

2014-11-01 Thread Dale
Public bug reported: After installing the package numlockx to lock the number pad on the laptop the entry numlockx has placed in init area for startup appears to be ignored. numlockx on ** Affects: xinput (Ubuntu) Importance: Undecided Status: New -- You received this bug notific

[Ubuntu-x-swat] [Bug 1388409] [NEW] Lubuntu forgets xinput commands upon sleep mode

2014-11-01 Thread Dale
Public bug reported: Unable to find a way to permenately turn off synaptics touchpad I've learned to open a terminal upon logon and issue the command xinput set-prop 00 "Device Enabled" 0 When the computer drops into sleep mode, and upon returning the settings are lost and must be re-entered upo

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-05 Thread Dale Hamel
@page p make sure that you're modules match your kernel version. Don't mean to be condescending, but that's a common error. -- 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/1248

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
I should probably mention I'm not using ubuntu at all, I'm using gentoo, so it's a lot easier for me to switch around my kernel... -- 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/bu

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
I can confirm 3.8-rc6 resolves this problem. So, if rolling back your kernel is an option I would suggest trying that. Otherwise, keep an eye on the upstream ticket. Hope all this helps guys! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xser

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Another possible (but hilarious fix) is to comment out a line as suggested here: https://bugs.freedesktop.org/show_bug.cgi?id=76732#c22 Haven't tried that one yet, but 3.8-rc6 should be clean as it is before 0a0afd282fd715dd63d64b243299a64da14f8e8d, which is the first bad commit. -- You receive

[Ubuntu-x-swat] [Bug 1020221] Re: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen

2014-04-04 Thread Dale Hamel
This should be closed as a duplicate of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1248256 -- 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/10202

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
The main thing I've been able to gleam is that the bug first appeared in 3.9, so I'm going to try rolling back to 3.8.13 (and earlier) to see if that resolves the issue. It would be awesome to be able to bisect the exact point when this issue was introduced. -- You received this bug notification

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
They pointed to this bug: https://bugs.freedesktop.org/show_bug.cgi?id=76732 ** Bug watch added: freedesktop.org Bugzilla #76732 https://bugs.freedesktop.org/show_bug.cgi?id=76732 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Oohh!! Found something very interesting in this log: https://bugs.freedesktop.org/attachment.cgi?id=96925 drm:drm_helper_hpd_irq_event is being fired a lot, which is likely the cause of the kernel workers? -- You received this bug notification because you are a member of Ubuntu-X, which is subs

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
I've created this issue against nouveau kernel driver: https://bugs.freedesktop.org/show_bug.cgi?id=77073 ** Bug watch added: freedesktop.org Bugzilla #77073 https://bugs.freedesktop.org/show_bug.cgi?id=77073 -- You received this bug notification because you are a member of Ubuntu-X, which i

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
My (assumed) kernel trace: http://lxr.free- electrons.com/source/drivers/gpu/drm/nouveau/nv50_display.c#L2201 - attempts to create the display here: http://lxr.free-electrons.com/ident?i=nouveau_connector_create Later on in the function there is some display port related code... wonder if it has

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Though it's just a wrapper for: http://lxr.free- electrons.com/source/drivers/gpu/drm/drm_crtc_helper.c#L884 Theory: For some reason, it is constantly toggling between DRM_MODE_DPMS_ON for some reason. Maybe we should report this bug against nouveau and probably the intel drivers as they will l

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
The code in question appears to be: http://lxr.free- electrons.com/source/drivers/gpu/drm/nouveau/nouveau_connector.c#L915 -- 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/1248

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Note: kworker/0:1 was found to have extremely CPU usage through ps -auxf: root 15854 50.0 0.0 0 0 ?R17:35 2:09 \_ [kworker/0:1] There are a number of other threads with similar output: kworker/0:3-1128 [000] d.s2 1973.688813: workqueue_queue_work: work struct

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Progress: kworker/0:1-15854 [000] d.h4 1821.296727: workqueue_queue_work: work struct=819b1920 function=console_callback workqueue=88046d17ba00 req_cpu=32 cpu=0 kworker/0:1-15854 [000] d.h2 1821.302144: workqueue_queue_work: work struct=819b85e0 function=push_to_

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
Well I'd much prefer to use just a normal HDMI monitor, but i work at a Mac shop and i'm stuck with a cinema display... I guess the price of the cinema display might be inhibitive? How many people really buy macs to run linux on them? My guess is that this is why this bug is rated so low here.

[Ubuntu-x-swat] [Bug 1020221] Re: [Lenovo ThinkPad T510] Connecting an external Monitor over DisplayPort freezes the screen

2014-04-04 Thread Dale Hamel
This does not appear to be exclusive to the nouveau or xorg. I've been able to reproduce it at the console by plugging in display port without X11 running. I open htop, everything looks fine. Then I plug in the display port cable and the CPU immediately shoots up to 100%. I've also loaded the int

[Ubuntu-x-swat] [Bug 1248256] Re: [MacBookPro10, 1] Plugging in displayport monitor causes kworker to take 100% CPU

2014-04-04 Thread Dale Hamel
This does not appear to be exclusive to the nouveau or xorg. I've been able to reproduce it at the console by plugging in display port without X11 running. I open htop, everything looks fine. Then I plug in the display port cable and the CPU immediately shoots up to 100%. I've also loaded the int

[Ubuntu-x-swat] [Bug 1285309] [NEW] Xorg crashed with SIGSEGV in miCreateScreenResources()

2014-02-26 Thread Dale Beaudoin
Public bug reported: Swapped SATA 1.5TB hdd from Intel based Core2 Duo to Asus P5QL Pro Core 2 Quad on ATi/AMD Graphics HD5450 silent IGBDDR3. Then: Update/Upgrade and hence .. xorg bug report ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersion

[Ubuntu-x-swat] [Bug 1132231] Re: Screen gets distorted with LibreOffice

2013-04-01 Thread Dale Maris
Thanks, Avery, your screen shot is close to what mine looks like. Mine might have been a little more distorted, but very close. I have switched computers to get around this issue. I will help out whatever I can as I still have the old computer sitting beside my desk. -- You received this bug n

[Ubuntu-x-swat] [Bug 1132231] Re: Screen gets distorted with LibreOffice

2013-03-14 Thread Dale Maris
et me know if I can provide any more information. Dale -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1132231 Title: Screen gets distorted with LibreOffice To manage not

[Ubuntu-x-swat] [Bug 1132231] Re: Screen gets distorted with LibreOffice

2013-03-09 Thread Dale Maris
This really hampring my use of my computer. I have now set up a duel boot to have access to Windows with Word to be able touse a word processor. Please keep me informed of any updated status. Thanks for everyone effort. Dale -- You received this bug notification because you are a member of

[Ubuntu-x-swat] [Bug 1132231] Re: Scrren get distorted with LibreOffice

2013-02-23 Thread Dale Maris
I am running Ubuntu on a Dell Inspiorn 531 with an Nvidia graphic card. -- 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/1132231 Title: Scrren get distorted with LibreOffice To manage notificatio

[Ubuntu-x-swat] [Bug 1132231] [NEW] Scrren get distorted with LibreOffice

2013-02-23 Thread Dale Maris
Public bug reported: Its not consistent, but when using LibreOffice, at some point my screen distorts and I cannot read anything or even view icons and other graphics. I can still tell that the windows are there, but nothing is readable. I do manage to re-boot my maching that seems to reset my s

[Ubuntu-x-swat] [Bug 1045197] Re: Xorg crashed with SIGABRT in raise()

2012-09-03 Thread Dale Beaudoin
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1045197 Title: Xorg crashed with SIGABRT in raise() To manage notifications about this bug go

[Ubuntu-x-swat] [Bug 1034680] Re: Xorg crashed with SIGABRT

2012-08-08 Thread Dale Beaudoin
** Visibility changed to: Public -- 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/1034680 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launch

[Ubuntu-x-swat] [Bug 995997] Re: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-07 Thread Dale Beaudoin
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/995997 Title: nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build To manage notifications about this

[Ubuntu-x-swat] [Bug 995997] [NEW] nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to build

2012-05-07 Thread Dale Beaudoin
Public bug reported: trying to update nvidia drivers. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: nvidia-current 295.49-0ubuntu1 ProcVersionSignature: Ubuntu 3.4.0-1.3-generic-pae 3.4.0-rc5 Uname: Linux 3.4.0-1-generic-pae i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Compiz

[Ubuntu-x-swat] [Bug 995970] [NEW] nvidia-current-updates 295.49-0ubuntu1: nvidia-current-updates kernel module failed to build

2012-05-07 Thread Dale Beaudoin
Public bug reported: Will not load nvidia drivers on reboot. Cannot adjust screen resolution. 800x600 only. 3rd time this happened on second install os same system . This bug was preceeded by another bug report #995962. whcih is fglrx2:8.960-0ubuntu1:fglrx kernel module failed. ProblemType: Pack

[Ubuntu-x-swat] [Bug 995970] Re: nvidia-current-updates 295.49-0ubuntu1: nvidia-current-updates kernel module failed to build

2012-05-07 Thread Dale Beaudoin
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/995970 Title: nvidia-current-updates 295.49-0ubuntu1: nvidia-current-updates kernel module failed to build To manage n

[Ubuntu-x-swat] [Bug 995962] Re: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build

2012-05-07 Thread Dale Beaudoin
-- 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/995962 Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.lau

[Ubuntu-x-swat] [Bug 995962] [NEW] fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build

2012-05-07 Thread Dale Beaudoin
Public bug reported: This occured while installing the 3.4.n-n kernel on Quantal Quetzal . ProblemType: Package DistroRelease: Ubuntu 12.10 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia .proc

[Ubuntu-x-swat] [Bug 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

2012-04-04 Thread Dale Beaudoin
Started GNOME classic to check for a crash bug in Gnome Classic and got Nautilus error. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/905686 Title: nautilus assert failure: nautilus: ../../sr

[Ubuntu-x-swat] [Bug 555957] Re: package fglrx (not installed) failed to install/upgrade: make returns error: mixed implicit and normal rules

2012-02-17 Thread Dale Bowley
Using Catalyst 12-1 on Ubuntu 11.04 x86_64; Radeon HD 5450 When I did: # sudo aticonfig --initial -f (amdconfig cmd not found) Output: # Uninitialized file found, configuring # Fail to link to fglrx-libglx.so, please check whether driver is installed correctly # Using /etc/X11/xorg.conf # Savi

[Ubuntu-x-swat] [Bug 909742] Re: GNOME bottom bar in Unity 3d ??

2011-12-29 Thread Dale B
Please belay this bug report. This is a non-bug. I had erroneously made this report while assuming I was working out of the Unity 3D DE, when, in actuality, I was in GNOME CLASSIC.DE. Thank you . Kind regrads, Ventrical. -- You received this bug notification because you are a member of Ubuntu-X

[Ubuntu-x-swat] [Bug 909742] Re: GNOME bottom bar in Unity 3d ??

2011-12-29 Thread Dale B
-- 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/909742 Title: GNOME bottom bar in Unity 3d ?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/909

[Ubuntu-x-swat] [Bug 909742] [NEW] GNOME bottom bar in Unity 3d ??

2011-12-29 Thread Dale B
Public bug reported: A strange phenomenon has occured while beta testing Unity 3D on Precise. The GNOME 2.(n) bottom bar has showed up out of nowhere and has enabled a previously set function in Compiz (Wallpaper(cycle)). I chose xorg as the possible culprit but it may be a Unity/Compiz problem. I

[Ubuntu-x-swat] [Bug 751378] Re: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7d8e0001)

2011-04-05 Thread Dale B
*** This bug is a duplicate of bug 727594 *** https://bugs.launchpad.net/bugs/727594 same probs as with alpha?? ** Attachment added: "Screenshot.png" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/751378/+attachment/1982637/+files/Screenshot.png -- You received

[Ubuntu-x-swat] [Bug 751378] Re: [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7d8e0001)

2011-04-05 Thread Dale B
*** This bug is a duplicate of bug 727594 *** https://bugs.launchpad.net/bugs/727594 -- 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/751378 Title: [i915gm] GPU lockup (ESR

[Ubuntu-x-swat] [Bug 751378] [NEW] [i915gm] GPU lockup (ESR: 0x00000001 IPEHR: 0x7d8e0001)

2011-04-05 Thread Dale B
*** This bug is a duplicate of bug 727594 *** https://bugs.launchpad.net/bugs/727594 Public bug reported: Binary package hint: xserver-xorg-video-intel apport-gpu-error-intel.py closed unexpectedly just after startup , while accessing main file menu at top left corner with Ubuntu Classic De

[Ubuntu-x-swat] [Bug 665233] Re: Ubuntu Maverick with ATI RADEON screen corruption

2011-03-09 Thread Dale Crawford
THANKS MILTON!! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in ubuntu. https://bugs.launchpad.net/bugs/665233 Title: Ubuntu Maverick with ATI RADEON screen corruption

[Ubuntu-x-swat] [Bug 665233] Re: Ubuntu Maverick with ATI RADEON screen corruption

2011-03-09 Thread Dale Crawford
I just wanted to say!!! POST #7 and #8 from Milton COMPLETELY FIXED MY FLICKERING PROBLEM!!! I am running a fresh install of Ubuntu 10.10 on a ATI Radeon X1300 512MB AGP Graphics card, 1.2Gb RAM, and a 2.0GHZ Sempron +2800 Processor. I have had this flickering problem ever since I FRESH installed U

[Ubuntu-x-swat] [Bug 549727] Re: [10.04] Touchpad stops working after login

2010-04-28 Thread Dale Russell
I have a T500 and it was working on 10.04 for a month until I did an update this morning. The workaround works but the bug still exists. -- [10.04] Touchpad stops working after login https://bugs.launchpad.net/bugs/549727 You received this bug notification because you are a member of Ubuntu-X, wh

[Ubuntu-x-swat] [Bug 489524] Re: resolution will not go 1440x900

2009-11-28 Thread Dale
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/36196487/BootDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/36196488/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/36196489/Lspci.txt ** Attachment adde

[Ubuntu-x-swat] [Bug 489524] [NEW] resolution will not go 1440x900

2009-11-28 Thread Dale
Public bug reported: Binary package hint: xorg it didnt find any nvidia driver from hard drive I already installed and didnt configure as well ProblemType: Bug Architecture: i386 CheckboxCommand: resolution_test CheckboxDescription: This display is using the following resolution: $output