Re: [Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-11-19 Thread Raul Dias
Yes Em sex, 16 de nov de 2018 07:25, Daniel van Vugt < daniel.van.v...@canonical.com escreveu: > Is this bug still a problem in the latest updates to 18.04? > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Also affects: gnome-shell (Ubuntu) >Importance: Undecided >Statu

[Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-08-14 Thread Raul Dias
I created inside /etc/x11/xorg.conf.d/ -- 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/1761773 Title: Touch Screen stop working on 18.04 beta1 To manage notifications about this bug go to: https

[Ubuntu-x-swat] [Bug 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream

2018-05-08 Thread Raul Dias
I have a lot of computers in my office that needs this drive to work. Neither Nouveau or VESA works with them. If this decision persists I will have to move to another distribution (which I hope to avoid). -- You received this bug notification because you are a member of Ubuntu-X, which is subsc

[Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-10 Thread Raul Dias
The simplest solution was to add the configuration: Section "InputClass" Identifier "NextWindows 1900 HID Touchscreen" MatchUSBID "1926:0003" Driver "evdev" EndSection -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg

[Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-10 Thread Raul Dias
Removing xserver-xorg-input-libinput did the tricky. Now it uses evdev. However, that shouldn't need be necessary. -- 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/1761773 Title: Touch Screen sto

[Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-10 Thread Raul Dias
The problem might also involve udev, as by these lines: [ 800.429] (II) event5 - NextWindow Touchscreen: is tagged by udev as: Tablet [ 800.429] (EE) event5 - NextWindow Touchscreen: libinput bug: missing tablet capabilities: btn-stylus resolution.Ignoring this device. [ 800.429] (II) eve

[Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-09 Thread Raul Dias
Upgraded to beta 2 and the same issue continues. -- 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/1761773 Title: Touch Screen stop working on 18.04 beta1 To manage notifications about this bug go

[Ubuntu-x-swat] [Bug 1761773] [NEW] Touch Screen stop working on 18.04 beta1

2018-04-06 Thread Raul Dias
Public bug reported: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. Probl

[Ubuntu-x-swat] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1

2018-04-06 Thread Raul Dias
** Attachment added: "X.org logs from 16.04 (Install Media Try Ubuntu option) where it works" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+attachment/5104182/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to x

[Ubuntu-x-swat] [Bug 1247528] Re: Build and distribute intel-virtual-output

2014-02-08 Thread Raul Dias
This tool is very important and it is already built, but not packaged: http://askubuntu.com/questions/380844/intel-virtual-output-command-for-saucy-13-10-with-dual-monitor-setup-and-hybrid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-x

[Ubuntu-x-swat] [Bug 894115] Re: Xorg Segfaults

2011-11-23 Thread Raul Dias
-- 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/894115 Title: Xorg Segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/894115/+subscription

[Ubuntu-x-swat] [Bug 894115] [NEW] Xorg Segfaults

2011-11-23 Thread Raul Dias
Public bug reported: Xorg segfaults randomly. I bet it is some other libraries fault, but I am not sure how to diagnose this. The system is up to date and the memories were exhaustly checked (memtest over many hours). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 Pro

[Ubuntu-x-swat] [Bug 881602] Re: 2nd head does not start automatically

2011-10-25 Thread Raul Dias
-- 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/881602 Title: 2nd head does not start automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+b

[Ubuntu-x-swat] [Bug 881602] [NEW] 2nd head does not start automatically

2011-10-25 Thread Raul Dias
Public bug reported: During boot, the 2nd head is shown as a clone of the console. This is what is expected. When xorg kicks in the 2nd head is turned off. after my session starts [kx]randr can be used to shown the 2nd head just fine, but it is a manual process. ProblemType: Bug DistroRelease:

[Ubuntu-x-swat] [Bug 761065] Re: [Sandybridge] Spurious "*ERROR* Hangcheck timer elapsed... blt ring idle" messages in dmesg when using compiz

2011-05-20 Thread Raul Dias
doing what Felix proposed at #16 didn't work on natty (2.6.38-8-generic): # echo 1 > /sys/module/i915/parameters/semaphores -bash: echo: write error: Invalid argument However, doing what proposed on #18 solved the problem. XPS L502X with optimus/bumblebee working -- You received this