[Ubuntu-x-swat] [Bug 1809110] [NEW] Intel drivers

2018-12-19 Thread Mustafa Jeja
Public bug reported:

i wanna see if it helps with setting up vagrant

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
Date: Wed Dec 19 14:33:31 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
   Subsystem: Dell 4 Series Chipset Integrated Graphics Controller [1028:027f]
InstallationDate: Installed on 2018-01-28 (324 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. OptiPlex 760
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=7dde6342-329e-4620-8e17-2e953c29f852 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0M858N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd02/18/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic 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/1809110

Title:
  Intel drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1809110/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

2018-12-19 Thread Gert van de Kraats
Mesa-bug:
https://bugs.freedesktop.org/show_bug.cgi?id=109102


** Bug watch added: freedesktop.org Bugzilla #109102
   https://bugs.freedesktop.org/show_bug.cgi?id=109102

-- 
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/1797882

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797882/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1727933] Re: as

2018-12-19 Thread Juhani Numminen
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

-- 
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/1727933

Title:
  as

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727933/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799875] Re: Kernel Crash - consisten when shutting down the system

2018-12-19 Thread Stephen Smith
** Changed in: nvidia-graphics-drivers (Ubuntu)
   Status: New => Fix Released

** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

-- 
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/1799875

Title:
  Kernel Crash  - consisten when shutting down the system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799875/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 313514]

2018-12-19 Thread Ajax-a
https://gitlab.freedesktop.org/xorg/xserver/issues/260

-- 
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/313514

Title:
  MASTER: evdev driver ignores keycodes > 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/313514/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1307701]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/569.

-- 
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/1307701

Title:
  xserver mouse pointer emulation from touch breaks with QML app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1171342]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/566.

-- 
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/1171342

Title:
  mouse scroll wheel not working in gedit & System Monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1171342/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Adam Goode
I am interested in doing a libinput-based wheel acceleration.

Peter: are you opposed to libinput mouse wheel acceleration in general,
or are you open to patches there? I think it could fit in cleanly.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Main-haarp
(In reply to Peter Hutterer from comment #20)
> (In reply to main.haarp from comment #17)
> If the document is long enough
> that scrolling acceleration is needed, the application (or toolkit) should
> honor that and provide the appropriate methods - that may include
> acceleration.
> libinput sits too low to have the semantic awareness here. For example,
> scrolling events during alt-tab switch between applications but libinput
> doesn't know that, it merely forwards the hardware events.

You have a point there, libinput will always lack the semantic awareness
and thus not provide an ideal solution.

But I'll have to disagree. In an ideal world, you can offload
acceleration to the app/toolkit. But since we have tons of legacy
applications or developers unaware or unwilling to implement
acceleration, they'll never receive the benefits. And even if they
implement it, you get lots of duplicated efforts and functionality
between apps.

If  acceleration depends on the toolkit/application, I fear it'll remain
a toy for select applications on modern distros only.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Peter Hutterer
Adam: I'm really hesitant to put it into libinput because I'm not sure
the problem scope is well understood (at least by me) and what the
actual point of it is. So far it's been a "would be nice" but - at least
these days :) - we require a bit more information about use-cases and
precise behaviours.

libinput provides two values for wheels: physical degrees and concrete
steps, so for most events on most mice you get a (15°, 1 step) tuple.
There is no room for acceleration there, if anything the acceleration
would have to be in the xf86-input-libinput driver. There we recently
added a patch to adjust the scroll distance based on the angle (see Bug
92772) so a wheel can now produce smooth scrolling for XI2 clients.

But as for any actual acceleration, someone (you? :) would have to come
up with a good plan of what the actual use-case is to solve and how to
solve it. Not necessarily with code at first but at least to get a good
idea of what's happening. And of course we'll need buy-in from the
bigger desktop environments.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Abdurrahim
I am surprised how much ignorant one can get. When I saw won't fix I see
why linux wont making any progress. Now I see why there are so much
forks on Linux no one can stand this much ignorance.

Let me correct one thing here:

"Win/MacOS have less toolkits to worry about *and* they control almost
the whole stack :)"

Totally wrong. This shows how big ignorant you are getting. Just check
how real-world works:
http://www.neuber.com/taskmanager/process/ipoint.exe.html

Just thinking about explain of Unix philosophy to "Linux" developer
especially who works on X11 what I admired most says this blown my mind
away so I registered and wanted to make records for history so maybe
someone in next gen would understand that all were not ignorant.

Ok let me give you one of the best rules about Unix philosophy maybe it
may cleanse your ignorance: Rule of modularity. If you cannot maintain
all you simply modularize it. If you cant handle mouse driver
accelaration leave it modularized. If you still don't have idea or don't
understand with example I gave on Windows and best rule about Unix don't
try to understand either

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1184159]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/566.

-- 
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/1184159

Title:
  [saucy] scrolling with a touchpad is jerky with bindings  set in
  compiz for Desktop-based Viewport Switching

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1184159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread clel
To explain my understanding of acceleration:

The mouse wheel has a certain amount of lines that are scrolled with
each scroll. This is often called "scroll speed"

An acceleration would increase/decrease the scroll speed dynamically
based on how often the wheel scrolls in a certain amount of time. So if
I rotate the wheel fast also the speed is increased meaning one also
needs to rotate the wheel as often as one would need to if scrolling
slower. I think this is the usecase - accuracy or speed in scrolling can
be delivered as needed.

I am not sure, whether there is also something like scroll speed
implemented. At least KDE offers a setting for it.

So if speed is implemented one can implement "acceleration" as something
that changes the speed. Also I'd suggest a changeable value how strong
the acceleration will be.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Main-haarp
(In reply to Peter Hutterer from comment #16)
> Adam: I'm really hesitant to put it into libinput because I'm not sure the
> problem scope is well understood (at least by me) and what the actual point
> of it is. So far it's been a "would be nice" but - at least these days :) -
> we require a bit more information about use-cases and precise behaviours.
> 

At least from my corner of mouse usage, the problem is that X has no
scroll distance multiplier like Windows does. Scrolling is slow.

Some applications have their own mechanisms to deal with that, like
Firefox's hidden about:config preferences, or extensions for Chrome. Or
you can also try to hack something together with imwheel.

If it's a touchpad, you can reduce the distance needed to send one
"scroll event". This makes scrolling faster, but also less accurate and
more error-prone.

Obviously none of these solutions are very good.

The future is going towards smooth scrolling, which is an incredible
experience. But while it's buttery smooth, it still doesn't solve the
problem of configurable scroll speed/distance.

Configurable acceleration on the input device driver level would solve
this nicely. You could have fast scrolling when you need it, and even
still retain slow but precise scrolling when you don't.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403] Re: [KDE] no option for mouse wheel acceleration

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

** Bug watch added: bugs.webkit.org/ #24813
   https://bugs.webkit.org/show_bug.cgi?id=24813

** Bug watch added: bugs.webkit.org/ #45155
   https://bugs.webkit.org/show_bug.cgi?id=45155

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Albzey
(In reply to Peter Hutterer from comment #16)
> Adam: I'm really hesitant to put it into libinput because I'm not sure the
> problem scope is well understood (at least by me) and what the actual point
> of it is. So far it's been a "would be nice" but - at least these days :) -
> we require a bit more information about use-cases and precise behaviours.

I'm not exactly sure why the point is not clear.

You can make the same argument for normal mouse cursor movement, where
mouse cursor acceleration is a pretty standard thing. And I think it
makes even more sense for mouse wheel scrolling than it does for mouse
cursor movement.

In all cases, you want to be able to make precise movements, as precise
as what the application allows (pixel based or line based but e.g. for
scrolling a list, I think a nicer experience is pixel based in all
cases). So this requires that the minimum possible scroll/movement speed
greater zero is as low as possible (e.g. 1 pixel).

Also, you would want to make the movement/scrolling as fast as possible.
For mouse cursor movement, this might be less of a problem because the
screen is usually of finite size and usually not so big anyway. That is
why I think it is even more important for scrolling than for cursor
movement. The scroll area can usually be much larger (e.g. a whole book)
or even be infinite and you might want to skip over huge parts at once.

By acceleration, you solve this nicely as this dynamically adapts the
speed. It will be slow if you move slowly but it can be as fast as you
want.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread clel
Alright. It is a bit sad though that apparently no developer seems to be
interested in making Linux competitive with the two other big operating
systems in this case.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Peter Hutterer
i guess the only update is a WONTFIX, given that this has been
languishing for 6 years now. input stuff like this is moving to libinput
anyway, and I don't think I'll implement mouse wheel acceleration there
either.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Peter Hutterer
(In reply to main.haarp from comment #17)
> Configurable acceleration on the input device driver level would solve this
> nicely. You could have fast scrolling when you need it, and even still
> retain slow but precise scrolling when you don't.

I feel this is solving the wrong problem. If the document is long enough that 
scrolling acceleration is needed, the application (or toolkit) should honor 
that and provide the appropriate methods - that may include acceleration.
libinput sits too low to have the semantic awareness here. For example, 
scrolling events during alt-tab switch between applications but libinput 
doesn't know that, it merely forwards the hardware events.

This is also the reason why libinput doesn't do kinetic scrolling, it
merely forwards enough information that a caller can implement it
accurately.


(In reply to Albert Zeyer from comment #19)
> You can make the same argument for normal mouse cursor movement, where mouse
> cursor acceleration is a pretty standard thing. And I think it makes even
> more sense for mouse wheel scrolling than it does for mouse cursor movement.

yes, but we've had multiple decades of pointer acceleration being a
thing. mouse wheel acceleration is less ubiquitous, which is why we
should review the reasons for doing it.

> Also, you would want to make the movement/scrolling as fast as possible. For
> mouse cursor movement, this might be less of a problem because the screen is
> usually of finite size and usually not so big anyway. That is why I think it
> is even more important for scrolling than for cursor movement. The scroll
> area can usually be much larger (e.g. a whole book) or even be infinite and
> you might want to skip over huge parts at once.

judging by the general push towards touch-sensitive interfaces in the
industry and the interfaces feeding back into old-style interfaces, it
seems a better solution here would be to have kinetic scrolling on the
scroll wheel. Which I think enlightenment already does.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread clel
So if handling this in libinput causes problems, maybe there is a different 
central place where to implement it.
How do Windows or MacOS handle this, as it is probably working without issues 
there?

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Peter Hutterer
(In reply to main.haarp from comment #21)
> If  acceleration depends on the toolkit/application, I fear it'll remain a
> toy for select applications on modern distros only.

it's a thin line between adding these features for legacy applications
and screwing things up for new applications that could do it better
themselves. the worst mistake we made along these lines was kinetic
scrolling in the synaptics driver, in addition to the various bugs it
also made it impossible for clients to implement it properly themselves.
something like wheel acceleration would be the same, it is transparent
to the point that it makes smart acceleration in a client virtually
impossible.


(In reply to Claudius Ellsel from comment #22)
> So if handling this in libinput causes problems, maybe there is a different
> central place where to implement it.
> How do Windows or MacOS handle this, as it is probably working without
> issues there?

Win/MacOS have less toolkits to worry about *and* they control almost the whole 
stack :)
it'd be possible to add it as additional data in libinput but then you still 
require the compositor to pass the data on. Which requires a) updates to the 
software and b) a wayland protocol to send that data on which again requires 
a), so legacy applications are still out in the void.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread clel
Any updates on this?

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 313514] Re: MASTER: evdev driver ignores keycodes > 255

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/313514

Title:
  MASTER: evdev driver ignores keycodes > 255

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/313514/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Albzey
As there are no objections against reopening this (actually no response
at all), I'm reopening now.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/405.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread evgom
I would like see this fixed. I don't know why the people don't see it
this like a problem.

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Adam Goode
(In reply to Peter Hutterer from comment #16)
> Adam: I'm really hesitant to put it into libinput because I'm not sure the
> problem scope is well understood (at least by me) and what the actual point
> of it is. So far it's been a "would be nice" but - at least these days :) -
> we require a bit more information about use-cases and precise behaviours.
> 
> libinput provides two values for wheels: physical degrees and concrete
> steps, so for most events on most mice you get a (15°, 1 step) tuple. There
> is no room for acceleration there, if anything the acceleration would have
> to be in the xf86-input-libinput driver. There we recently added a patch to
> adjust the scroll distance based on the angle (see Bug 92772) so a wheel can
> now produce smooth scrolling for XI2 clients.
> 
> But as for any actual acceleration, someone (you? :) would have to come up
> with a good plan of what the actual use-case is to solve and how to solve
> it. Not necessarily with code at first but at least to get a good idea of
> what's happening. And of course we'll need buy-in from the bigger desktop
> environments.

I've been thinking a bit about this. Let me start with this proposal (I
can open a new bug if we want to continue this).

Use case:
- Scrolling through a long document is slow with a mouse wheel

Prior work showing benefits of wheel acceleration:
- macOS
- Chrome OS

Requirements:
- Don't break anything
- Require minimum changes from clients

Proposal:
- Mouse wheel acceleration at the libinput level, only for mouse wheels
- Do no acceleration on values returned from 
libinput_event_pointer_get_axis_value_discrete, this keeps the promise in the 
API of reporting "physical mouse wheel clicks" and keeps us from needing to 
implement a new "get unaccelerated" API
- Ensure that legacy X wheel events (pre-XI2.1) are not accelerated

Open questions:
- Does this cover enough clients without breaking things? Chrome and Firefox 
support XI2.1, so this would accelerate those programs.
- Under X or XWayland, is it possible to accelerate XI2.1 events but not the 
legacy events? Or are the legacy events generated automatically?
- Or is it ok to accelerate legacy X wheel events? emacs has scroll 
acceleration already, and other clients may as well.


Again, I can open another bug if this seems reasonable. I don't want this to 
continue in a WONTFIX bug :)

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Abdurrahim
I am surprised how much ignorant one can get. When I saw won't fix I see
why linux wont making any progress. Now I see why there are so much
forks on Linux no one can stand this much ignorance.

Let me correct one thing here:

"Win/MacOS have less toolkits to worry about *and* they control almost
the whole stack :)"

Totally wrong. This shows how big ignorant you are getting. Just check
how real-world works:
http://www.neuber.com/taskmanager/process/ipoint.exe.html

Just thinking about explain of Unix philosophy to "Linux" developer
especially who works on X11 what I admired most says this blown my mind
away so I registered and wanted to make records for history so maybe
someone in next gen would understand that all were not ignorant.

Ok let me give you one of the best rules about Unix philosophy maybe it
may cleanse your ignorance: Rule of modularity. If you cannot maintain
all you simply modularize it. If you cant handle mouse driver
accelaration leave it modularized. If you still don't have idea or don't
understand with example I gave on Windows and best rule about Unix don't
try to understand either

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 619403]

2018-12-19 Thread Albzey
First thing, I would reopen this bug report (remove the WONTFIX) - it
really doesn't matter if it's not clear yet where to implement this.

On the topic at where to implement this:

Conceptually, mouse scroll wheel acceleration is really the same thing
as mouse cursor movement acceleration. That's why I think it would make
most sense to implement at the same place, like I did in my initial
implementation.

Note that while I'm not sure if my initial implementation was the most
optimal way to implement this, it actually worked great, in all
applications. The only thing which optionally could have made it even
better would be if the applications all would do pixel-based scrolling
and not more, but even if the applications behave just like they do,
line-based scrolling or whatever other scrolling behavior, they don't
need to know and they should not need to know about any underlying mouse
scroll wheel acceleration. Just like they also should not need to know
about mouse cursor move acceleration.

Maybe 3D games are an exception, which would want to disable mouse
cursor move acceleration because they use the mouse cursor movement in a
different way. The same argument might be true for mouse scroll wheel
acceleration. This is again an argument that mouse scroll wheel
acceleration should be handled in the same way as mouse cursor move
acceleration.

I don't exactly understand why we are not looking at MacOSX how and at what 
level it is implemented there. It is a solved problem on MacOSX and works 
great. So about any question like at what level to implement it, why not do it 
like it's done on MacOSX?
So, I did some research on this, and here are some links, or keywords to look 
at and search for:
https://gist.github.com/svoisen/5215826
kCGScrollWheelEventIsContinuous
https://chromium.googlesource.com/chromium/src/+/68ac3a05284cd246589a38843f2ba5b20ed5db72%5E!/
https://codereview.chromium.org/42607
https://bugs.webkit.org/show_bug.cgi?id=24813
https://github.com/adobe/webkit/blob/master/Source/WebCore/platform/mac/WebCoreSystemInterface.mm
https://bugs.webkit.org/show_bug.cgi?id=45155
http://trac.webkit.org/changeset/66812/webkit
https://github.com/aosm/IOHIDFamily/blob/d36f126e5b8d3183a037c453df7feedaba874553/IOHIDSystem/IOKit/hidsystem/IOHIPointing.h
https://github.com/aosm/IOHIDFamily/blob/d36f126e5b8d3183a037c453df7feedaba874553/IOHIDSystem/IOHIPointing.cpp
https://stackoverflow.com/questions/44196338/where-is-mouse-cursor-movement

So, I guess the implementation of the main logic of the scroll acceleration can 
be found in that file IOHIPointing.cpp.
You even find that the pointer (mouse cursor) and (scroll) wheel share the same 
structure to handle the acceleration:

struct IOHIPointing::ExpansionData
{
UInt32  scrollType;

ScrollAccelInfo * scrollWheelInfo;
ScrollAccelInfo * scrollPointerInfo;
...
}

-- 
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/619403

Title:
  [KDE] no option for mouse wheel acceleration

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/619403/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/1307701

Title:
  xserver mouse pointer emulation from touch breaks with QML app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1184159] Re: [saucy] scrolling with a touchpad is jerky with bindings set in compiz for Desktop-based Viewport Switching

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/1184159

Title:
  [saucy] scrolling with a touchpad is jerky with bindings  set in
  compiz for Desktop-based Viewport Switching

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1184159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1440891] Re: xbacklight doesn'twork with modesetting driver

2018-12-19 Thread Bug Watch Updater
Launchpad has imported 23 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=96572.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-06-18T06:42:44+00:00 Vincent Bernat wrote:

Created attachment 124584
xorg.log

Hey!

After switching from intel to modesetting, xbacklight doesn't work
anymore:

$ xbacklight = 20
No outputs have backlight property

However, a backlight control is present in sysfs:

/sys/class/backlight/intel_backlight

In Debian:
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824987

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/4


On 2016-06-24T09:38:09+00:00 Peter B. Jørgensen wrote:

I have the same problem running Arch linux.
xbacklight works with the xf86-video-intel driver, but not without it, even 
though /sys/class/backlight/intel_backlight is still present.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/5


On 2016-07-07T15:20:07+00:00 Timabraldes wrote:

I'm not sure what the etiquette is about "me too" comments in this
Bugzilla instance, but I see the same behavior on a Lenovo Thinkpad
T440s: /sys/class/backlight/intel_backlight is present but xbacklight
simply says "No outputs have backlight property" when I try to run it. I
have not installed the intel driver so I'm using modesetting by default.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/6


On 2016-07-29T07:17:30+00:00 rubik wrote:

Experiencing the same problem. For me it's a real problem because the intel 
driver freezes constantly, so my only option is modesetting.
Is there something I can do to help?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/9


On 2016-08-03T16:09:21+00:00 Martin-peres-n wrote:

Thanks for the bug report, I will be looking it starting from today.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/10


On 2016-08-04T06:27:05+00:00 Jani-nikula wrote:

IIUC xf86-video-intel provides the backlight property itself; such a
property is not supplied by the kernel.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/11


On 2016-08-04T14:46:03+00:00 Martin-peres-n wrote:

(In reply to Jani Nikula from comment #5)
> IIUC xf86-video-intel provides the backlight property itself; such a
> property is not supplied by the kernel.

Indeed. Here is a relevant thread:
https://lists.freedesktop.org/archives/dri-
devel/2014-September/thread.html#67984

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/12


On 2016-08-23T10:38:51+00:00 Timo Aaltonen wrote:

so is that set of patches going to be revived soon?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/13


On 2016-09-10T19:42:26+00:00 Nico-freedesktop-org wrote:

I wonder if anyone of the developers is reading here at all?

The only reason not to use the modesetting driver is the missing
backlight capability - as it is faster and more reliable than the intel
driver (for intel hardware!).

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1440891/comments/14


On 2016-09-12T15:20:26+00:00 Eero-t-tamminen wrote:

(In reply to nico-freedesktop.org from comment #8)
> I wonder if anyone of the developers is reading here at all?

Martin's soon back from vacation.

I don't see Jani on the CC, but if this needs new API from kernel, bug
about that should be linked here. Is there one?


> The only reason not to use the modesetting driver is the missing backlight
> capability - as it is faster and more reliable than the intel driver (for
> intel hardware!).

You didn't mention in which use-case, on which distro and with which
exact HW you've compared modesetting and Intel DDX performance, but in
our tests Intel DDX has been somewhat faster on average.  As to
reliability, there have been issues with DRI3, but those have been fixed
in X libraries, Mesa, Intel DDX etc.  Mainly you need to use new enough
(full) stack.

Reply at: http

[Ubuntu-x-swat] [Bug 1171342] Re: mouse scroll wheel not working in gedit & System Monitor

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/1171342

Title:
  mouse scroll wheel not working in gedit & System Monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1171342/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

2018-12-19 Thread Daniel van Vugt
** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=109102
   Importance: Unknown
   Status: Unknown

-- 
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/1797882

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1797882/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1808806] Re: ????

2018-12-19 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
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/1808806

Title:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1808806/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1809110] Re: Intel drivers

2018-12-19 Thread Daniel van Vugt
Ubuntu already comes with all "Intel drivers" pre-installed.

What is the problem you're trying to solve?

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

-- 
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/1809110

Title:
  Intel drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1809110/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485]

2018-12-19 Thread Tfa7
FWIW we've patched xorg-server in the distribution.
Shame on those breaking base functionality instead of fixing their crap!

-- 
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/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485]

2018-12-19 Thread Alan Coopersmith
*** Bug 102424 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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1240957]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/566.

-- 
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/1240957

Title:
  Scrolling behaviour and window focus has changed and is inconsistent

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1240957/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/253.

-- 
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/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1200829]

2018-12-19 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/566.

-- 
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/1200829

Title:
  Regression: Enabling typical bindings in  "Desktop-based Viewport
  Switching" breaks scrollwheel scrolling in some windows with a usb
  mouse on a laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1200829/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485]

2018-12-19 Thread Main-haarp
(In reply to Michael Shigorin from comment #32)
> (In reply to main.haarp from comment #31)
> > Do you happen to have a more recent patch?
> 
> 1.19.3:
> http://git.altlinux.org/gears/x/xorg-server.git?p=xorg-server.git;
> a=commitdiff;h=c5b77a90d7e0d6a1874fcb545969f355d1ed0293

Applies well. Thanks!

-- 
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/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485]

2018-12-19 Thread Tfa7
(In reply to main.haarp from comment #31)
> Do you happen to have a more recent patch?

1.19.3: http://git.altlinux.org/gears/x/xorg-server.git?p=xorg-
server.git;a=commitdiff;h=c5b77a90d7e0d6a1874fcb545969f355d1ed0293

-- 
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/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485]

2018-12-19 Thread Main-haarp
(In reply to Michael Shigorin from comment #30)
> FWIW we've patched xorg-server in the distribution.
> Shame on those breaking base functionality instead of fixing their crap!

Do you happen to have a more recent patch? The ones posted here are very
outdated.

-- 
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/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1200829] Re: Regression: Enabling typical bindings in "Desktop-based Viewport Switching" breaks scrollwheel scrolling in some windows with a usb mouse on a laptop

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/1200829

Title:
  Regression: Enabling typical bindings in  "Desktop-based Viewport
  Switching" breaks scrollwheel scrolling in some windows with a usb
  mouse on a laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1200829/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/1240957

Title:
  Scrolling behaviour and window focus has changed and is inconsistent

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1240957/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 589485] Re: Ignores physical display size and calculates based on 96DPI

2018-12-19 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

-- 
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/589485

Title:
  Ignores physical display size and calculates based on 96DPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/589485/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1809217] [NEW] ???

2018-12-19 Thread duffaud
Public bug reported:

Sorry, but I'm a french guy and my english isn't fluent enough for telling you 
what is happenning to me . So I must follow in french.
Quand j'enregistre des photos ou des pages sur le net (Pinterest, FB, Tumblr, 
etc...) sur mon disque dur, normalement celles-ci apparaissent telles quelles 
dans le dossier que j'ai sélectionné, je n'ai pas besoin de les ouvrir avec le 
visionneur d'images. Mais là, depuis environ trois semaines, quand je 
télécharge un document celui-ci apparait sous la forme d'un petit rectangle 
noir sur lequel est écrit JPG ou PNG. Ce petit rectangle noir que je peux 
ouvrir en double-cliquant ou en me servant d'un visionneur d'image, mais qui 
apparait à nouveau à la place de l'image ou du document une fois que j'ai cessé 
de le visionner. 
Ce malencontreux phénomène s'étend maintenant  à des documents antérieurement 
enregistrés, ce qui rend mes dossiers illisibles. 
Si je n'excelle pas en anglais, je ne suis pas meilleur en informatique. Donc 
si vous pensez pouvoir m'aider, faites le de la manière la plus claire qui 
soit. Please !!!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Dec 20 07:33:36 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation NV44 [GeForce 6200 LE] [10de:0163] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd NV44 [GeForce 6200 LE] [1458:3400]
InstallationDate: Installed on 2015-12-26 (1089 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
MachineType: Dell Inc. OptiPlex 360
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=eb14491b-f949-4add-b1ee-9395094ec859 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/12/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0T656F
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd08/12/2008:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 360
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Dec 20 08:31:42 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 input  USB Keyboard   KEYBOARD, id 8
 input  USB Keyboard   KEYBOARD, id 9
 inputMicrosoft  Microsoft Basic Optical Mouse v2.0  MOUSE, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386 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/1809217

Title:
  ???

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1809217/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1809217] Re: Image icons appear as black rectangles instead of previews

2018-12-19 Thread Daniel van Vugt
This might be related to your kernel starting in recovery mode with
"nomodeset":

[36.451] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=eb14491b-f949-4add-
b1ee-9395094ec859 ro recovery nomodeset

Please try rebooting and as soon as the purple screen appears, hit Esc.
Now in the menus select a standard kernel that is not recovery mode.

** Summary changed:

- ???
+ Image icons appear as black rectangles instead of previews

** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu)

** Tags added: nouveau

-- 
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/1809217

Title:
  Image icons appear as black rectangles instead of previews

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1809217/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp