This should fix it:
https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1766728
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766851
Title:
Missing `linux-update-symlinks` causes Linux
I can confirm this fixes 4.17-rc2 from mainline ppa for xenial. Thank
you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766728
Title:
update linux-base on xenial
To manage notifications about
Sorry for the spamming, turns out in gnome session with Ubuntu Dock it's
the same under X11, in Wayland it seems better/nearly perfect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725384
Title:
Now it gets weird. I installed gnome-session and it seems that here,
both Caribou seems less intrusive and the "multiple touch events" issue
does not occur even when activating the Ubuntu Dock extension.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I observe the same on a Dell Venue 7140. At least disabling Caribou
using the Block Caribou extension does not solve the issue.
I would like to point out the severity of this issue, as this makes the
dock virtually unusable for touchscreens and even can lock up the
activities button at the top
Just another confirmation, using an Acer T230H on 12.04. Practically
makes the touchscreen unusable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002788
Title:
Using the touchscreen breaks normal
I can confirm this on a laptop with an intel graphics chip and a clean
ubuntu precise install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024276
Title:
lightdm doesn't start if weston is
Changing /etc/init/network-manager.conf as mentioned here did not fully solve
the problem for me.
Instead, it led to network-manager complaining about a missing messaging bus
(DBus?) during shutdown (which was still too long ;) ).
The workaround mentioned in Bug 903825, however, seems to work
I can confirm this problem for Ubuntu 11.10.
The posted fix works fine.
Can this fix still be included in Oneiric? Apparently, this problem would make
vpnc useless in Oneiric if not fixed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Well, so we need someone to valac as a dependency to the anjuta package.
Valac appears not to be too big, so that should not be a big memory
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807670
Okay, so is this the right place for this bug, or should I report it
somewhere else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/807670
Title:
anjuta crashes when opening .vala file without
Public bug reported:
System: Ubuntu Oneiric Ocelot 11.10 Alpha 2 64bit
Anjuta Version: 3.1.3
Compiling and running an existing project without opening its source
files works perfectly. However, if the package valac is not installed,
trying to open a .vala file results in anjuta to crash.
Same here with an Acer T230H touch screen.
Tried all kinds of configuration, there is but no reaction at all. However,
uTouch + Touchegg works fine.
Maybe this is uTouch-related?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
well, there is still one question: now that the screen appears to work
correctly, should there be any multitouch functionality? I tried unity,
but did not get any reactions on gestures. as i posted above, ginn is
not really satisfying on my system (yet).
--
Pressing buttons on quanta hardware is
well, there is still one question: now that the screen appears to work
correctly, should there be any multitouch functionality? I tried unity,
but did not get any reactions on gestures. as i posted above, ginn is
not really satisfying on my system (yet).
--
Pressing buttons on quanta hardware is
Using the proposed sources (as described in the other bug) solves the problems,
now the touchscreen works perfectly, thanks a lot!
Ginn still does not work correctly, but I think, this is not related to the
touchscreen.
--
Pressing buttons on quanta hardware is very hard and imprecise
@Felix: Is your problem that ginn does not compile correctly? I remember I had
to install a dependency to make it work (can't remember the name, but the
compile output should reveal which one).
However, after compiling ginn, I can't use most of its functions without
problems, as I posted
@Felix: Is your problem that ginn does not compile correctly? I remember I had
to install a dependency to make it work (can't remember the name, but the
compile output should reveal which one).
However, after compiling ginn, I can't use most of its functions without
problems, as I posted
Hi,
sorry for my absence for the last weeks, exams are approaching ;)
I did not have problems with the maverick upgrade, so I guess this is not a
general problem. Have you tried reconfiguring your Xorg.conf?
On my system, sometimes the touchscreen does not react after booting, a reboot
usually
Hi,
sorry for my absence for the last weeks, exams are approaching ;)
I did not have problems with the maverick upgrade, so I guess this is not a
general problem. Have you tried reconfiguring your Xorg.conf?
On my system, sometimes the touchscreen does not react after booting, a reboot
usually
Hi,
sorry for my absence for the last weeks, exams are approaching ;)
I did not have problems with the maverick upgrade, so I guess this is not a
general problem. Have you tried reconfiguring your Xorg.conf?
On my system, sometimes the touchscreen does not react after booting, a reboot
usually
Using this driver, mouse up is missing again (like test2).
It still mixes up the fingers sometimes. I think it only happens when one
finger passes below the other, so I guess, this movement simply puzzles the
optical recognition.
However, all kinds of two-finger gestures I could imagine worked
Using this driver, mouse up is missing again (like test2).
It still mixes up the fingers sometimes. I think it only happens when one
finger passes below the other, so I guess, this movement simply puzzles the
optical recognition.
However, all kinds of two-finger gestures I could imagine worked
I now have installed the newest test driver and evemu. At the moment, the
touchscreen behaves as Felix described, my system is up-to-date.
In the attachment, I put the output of evemu-describe and three evemu-record
outputs (for 1 short tap, 3 short taps at different positions and 2 swipes (~5
On my system, this problem is not limited to the onscreen keyboard, so it is
probably still a driver issue.
Swipes work perfectly. However, when tapping, the mouse position is not always
updated and then, the click is performed at the position of the last tap that
was recognized correctly.
I
On my system, this problem is not limited to the onscreen keyboard, so it is
probably still a driver issue.
Swipes work perfectly. However, when tapping, the mouse position is not always
updated and then, the click is performed at the position of the last tap that
was recognized correctly.
I
Good news ;)
In mtview, tapping and dragging works well both with one and two fingers! (Only
when dragging two fingers in strange curves, it sometimes mixes up the fingers,
but it looks like that is because of the optical recognition by the screen)
Now that the driver itself works perfectly,
Good news ;)
In mtview, tapping and dragging works well both with one and two fingers! (Only
when dragging two fingers in strange curves, it sometimes mixes up the fingers,
but it looks like that is because of the optical recognition by the screen)
Now that the driver itself works perfectly,
Good news ;)
In mtview, tapping and dragging works well both with one and two fingers! (Only
when dragging two fingers in strange curves, it sometimes mixes up the fingers,
but it looks like that is because of the optical recognition by the screen)
Now that the driver itself works perfectly,
Indeed, this sweeping was the first problem for me. I have not tried the
newest test driver yet, but before using any drivers posted here, I
noticed that clicking the mouse once made one simple click with the
touchscreen possible (without sweeping). After this single click,
sweeping was necessary
Indeed, this sweeping was the first problem for me. I have not tried the
newest test driver yet, but before using any drivers posted here, I
noticed that clicking the mouse once made one simple click with the
touchscreen possible (without sweeping). After this single click,
sweeping was necessary
Indeed, this sweeping was the first problem for me. I have not tried the
newest test driver yet, but before using any drivers posted here, I
noticed that clicking the mouse once made one simple click with the
touchscreen possible (without sweeping). After this single click,
sweeping was necessary
I tried the test2 driver. This seems to return the problem to the beginning :(
Apparently, mouse up is not recognized by the driver (the screen behaves as if
it was pressed continuously). Pressing the regular mouse buttons does not
change that, so after touching the screen once, no click is
I tried the test2 driver. This seems to return the problem to the beginning :(
Apparently, mouse up is not recognized by the driver (the screen behaves as if
it was pressed continuously). Pressing the regular mouse buttons does not
change that, so after touching the screen once, no click is
I tried the test2 driver. This seems to return the problem to the beginning :(
Apparently, mouse up is not recognized by the driver (the screen behaves as if
it was pressed continuously). Pressing the regular mouse buttons does not
change that, so after touching the screen once, no click is
I can confirm this behaviour. Left clicks are neither accepted from the
touchscreen nor from the mouse. Moving the cursor works with both devices.
This problem is not related to easystroke as I have not installed it on this
maverick install yet.
--
Pressing buttons on quanta hardware is very
I can confirm this behaviour. Left clicks are neither accepted from the
touchscreen nor from the mouse. Moving the cursor works with both devices.
This problem is not related to easystroke as I have not installed it on this
maverick install yet.
--
Pressing buttons on quanta hardware is very
I can confirm this behaviour. Left clicks are neither accepted from the
touchscreen nor from the mouse. Moving the cursor works with both devices.
This problem is not related to easystroke as I have not installed it on this
maverick install yet.
--
Pressing buttons on quanta hardware is very
38 matches
Mail list logo
