touchpad dimensions are 66x38
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1526633
Title:
edge scrolling not working correctly on latitude e6410
To manage notifications
the range changes slightly between tries, got that on another one
Touchpad sends: x [70..1862], y [106..1308]
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1526633
Title:
Public bug reported:
This happened when i upgraded from 15.04 to 15.10
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: fglrx (not installed)
ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
Uname: Linux 4.2.0-21-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
it's not supported to install stock packages on top of lts backports
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
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/1514278
if it's a vbox bug why is this (and 1525735) filed against the xserver?
--
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/1525451
Title:
Ubuntu GNOME 16.04 daily wont boot in virtualbox
To
usr_lib_chromium-browser_chromium-browser.1000.crash
** Attachment added: "usr_lib_chromium-browser_chromium-browser.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535454/+files/_usr_lib_chromium-browser_chromium-browser.1000.crash
--
You received this b
also other crash-files are to be found:
** Attachment added: "usr_bin_gnome-panel crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535450/+files/_usr_bin_gnome-panel.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Here is my metacity crush log, i experience this bug since upgrading
from 14.04 to 15.10!
** Attachment added: "metacity crash file"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535449/+files/_usr_bin_metacity.1000.crash
--
You received this bug notification becau
_usr_bin_pidgin.1000.crash
** Attachment added: "_usr_bin_pidgin.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535451/+files/_usr_bin_pidgin.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xo
_usr_bin_vlc.1000.crash
** Attachment added: "_usr_bin_vlc.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535452/+files/_usr_bin_vlc.1000.crash
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubu
Public bug reported:
The output from touchpad-edge-detector
Touchpad AlpsPS/2 ALPS DualPoint TouchPad on /dev/input/event7
Move one finger around the touchpad to detect the actual edges
Kernel says:x [0..2000], y [0..1400]
Touchpad sends: x [92..1837], y [113..1308] \^C
Touchpad has no resol
** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-intel
(Ubuntu)
--
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/1522727
Title:
X.org crashes intermittently, rand
** Tags removed: need-duplicate-check
--
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/1503426
Title:
package libgl1-mesa-glx 10.1.3-0ubuntu0.5 failed to install/upgrade:
73.3516:subprocess inst
Fix committed into lp:mir at revision 3198, scheduled for release in
mir, milestone 0.19.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/
Fix committed to lp:mir/0.18 at revision 3182, scheduled for release in
Mir 0.18.0
** Changed in: mir/0.18
Status: Triaged => Fix Committed
** Changed in: mir/0.18
Assignee: (unassigned) => Mir development team (mir-team)
--
You received this bug notification because you are a membe
** Changed in: mir
Status: Incomplete => In Progress
** Changed in: mir
Assignee: (unassigned) => Mir development team (mir-team)
** Changed in: mir/0.18
Status: Incomplete => Triaged
** Changed in: mir (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug n
*** This bug is a duplicate of bug 1512527 ***
https://bugs.launchpad.net/bugs/1512527
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1512527, so it is being marked as such. Please look
stijn, let an apples-to-apples comparison be made. Hence, could you
please attach one document that had the kerning issue in Trusty?
Then, if you boot into the daily environment does it still have the
kerning issue?
--
You received this bug notification because you are a member of Ubuntu-X,
whic
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1526564/+attachment/4535354/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs
Public bug reported:
Xubuntu 16.04 Xenial
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
$ apt-cache policy nvidia-current
nvidia-current:
Installed: 304.131-0ubuntu2
Candidate: 304.131-0ubuntu2
Version table:
*** 304.131-0ubuntu2 500
500 http://us.
Almost identical to this bug, that had a fix release for ubuntu 14.10:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1363675
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.la
duflu, could you also try
1. with the '--vt' option ?
2. on another machine with a different GPU?
--
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/1526209
Title:
[regression] Clients of nested Mir
it's probably just a small change in usbtouchscreen module so that 15C2:3480
device is catched and configured..
unfortunately i have no idea of driver development..
this guy managed to add something to the usbtouchscreen module to get another
version of the fingervue touchscreen working.
his s
** Branch linked: lp:~mir-team/mir/revert-3098
--
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/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
To manage
Haven't been able to confirm this specific scenario today, but another
issue (not a crash, rather incorrect platform loading) was noticed
related to rev 3098. Seems best to back out that rev for lp:mir and
lp:mir/0.18 release.
--
You received this bug notification because you are a member of Ubu
Has anyone managed to solve the problem?
It's been quite a while (well, 3 years!) since the problem exists. I've
discovered it about a week ago with my new Acer Aspire V17 Nitro which has a
Synaptic touchpad (and has this exactly problem)
--
You received this bug notification because you are a
** Tags removed: need-duplicate-check
--
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/1518269
Title:
fglrx-core 2:15.200-0ubuntu4.2: fglrx-core kernel module failed to
build [error:
hmm, and now after doing a reinstall and upgrade of all packages (on
xenial), I can no longer reproduce the issue.
--
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/1526209
Title:
[regression] Clie
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1517562
Title:
package fglrx-updates-core (not installed) failed to install/upgrade:
att
Yes i can also remember seeing that stacktrace when toying around with
our reload hack, to get mesa to find our symbols during egl display
detection. But I dont get that anymore on xenial with lp:mir or
lp:mir/0.18
--
You received this bug notification because you are a member of Ubuntu-X,
which
** Tags removed: need-duplicate-check
--
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/1518242
Title:
package fglrx 2:15.200-0ubuntu0.6 failed to install/upgrade:
subprocess installed
** Tags removed: need-duplicate-check
--
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/1519009
Title:
package fglrx-core (not installed) failed to install/upgrade: forsøger
at overskr
This bug seems related to
https://bugs.freedesktop.org/show_bug.cgi?id=88012
As I can reproduce it after setting the parameters to save energy using
powertop.
** Bug watch added: freedesktop.org Bugzilla #88012
https://bugs.freedesktop.org/show_bug.cgi?id=88012
--
You received this bug notif
So my problem noted in #8 was just a mis-match of packages on my system.
Cannot reproduce with xenial + silo 021, nor with on-system builds of
lp:mir, lp:mir/0.18, or lp:mir/0.17.
After standup today, it seems like we weren't able to reproduce the
problem, provided that we had updated systems, and
I've been installing from the main repositories, but had previously tried using
the wily-proposed instances without success. However, I've tried again, using
the following steps (based on reply #123):
1) Checked /etc/apt/sources.list, and it already includes the line "deb
http://gb.archive.com/u
I could not reproduce on xenial. Both mir-on-x and mesa worked for me.
Note that there is a known issue with the nested server not being able
to detect the platform (lp:1515558) so a '--vt' switch is needed on the
server for correct behaviour.
--
You received this bug notification because you are
I make the mistake regularly of writing a non-breaking space instead of
a regular space, when writing shell scripts. It produces errors that are
very difficult to detect.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bug
Missing information to aid reproducing:
1. Are you running from a terminal, a VT or a ssh session?
1.1. AFAICS the commands as given in the instructions can only work from a
terminal session, but Mir-on-X doesn't *need* "sudo", so what happens without
"sudo"?
2. Are you running a local build?
** Tags removed: need-duplicate-check
--
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/1514278
Title:
package xserver-common 2:1.11.4-0ubuntu10.17 failed to
install/upgrade: trying to ove
** Tags removed: need-duplicate-check
--
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/1516342
Title:
package libgbm1 10.1.3-0ubuntu0.4 failed to install/upgrade: unable to
install (supposed) ne
** Tags removed: need-duplicate-check
--
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/1519401
Title:
package fglrx-amdcccle 2:15.201-0ubuntu2~15.10.2 failed to
install/upgrade: packa
** Tags removed: need-duplicate-check
--
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/1524059
Title:
fglrx-14.501.1003 installed ok, but it breaks dependencies Ubuntu
14.04
To manag
@philip-gemmell-r what version of fglrx-updates did you install? (the
package version) I don't think the fix is actually released in the main
repositories. They are still showing (2:15.201-0ubuntu1)
If you want to get the fixed version you need to enable wily-proposed
long enough to install fglrx-
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1519853
Title:
package fglrx-updates-core (not installed) failed to install/upgrade:
try
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1519686
Title:
package nvidia-304-updates 304.131-0ubuntu0.14.04.1 failed to
I'm still having the same problem - booting to blank screen unless I purge
fglrx*, lightdm and xorg to get to a command line interface. If I only try
removing fglrx*, I get a window telling me that I have to set-up my graphics
card, etc., but I can't progress beyond that. I've edited /etc/defaul
[Continuation of previous post, I can't seem to edit]
Two things:
1. The graphical output of LO was nearly faultless. Errors I normally
have in displayed properties like bold / italic / font were not there.
However I did experience a full loss of display of some characters at a
certain high zoom
Chris, I have tried using the LiveCD. I do not really know what to
conclude from the results though
** Attachment added: "CharactersLostAtHighZoomImpress_Wrong.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1448937/+attachment/4535112/+files/CharactersLostAtHighZoomImpress_Wrong.png
Please clarify how to reproduce:
If run from a terminal window we don't need any of the "sudo's" as we
simply load up the Mir-on-X stack and connect via $DISPLAY. In any case,
sudo should only be require for the host mir server when using kms
(--arw-file will make the endpoint accessible to all).
Kai Mast, would you mind testing with drm-intel-nightly? This is
typically requested by upstream for intel driver driven issues to see if
fixes have already been developed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://b
I also can see the nested server crash scenario when connecting
mir_demo_client_egltriangle. I haven't seen the client crash yet
--
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/1526209
Title:
[re
Can't reproduce on wily
--
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/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
To manage notifications about th
Public bug reported:
Log, and are working, often the screen is disturbed. When I click with the
mouse, usually it returns to the original. However, also when it does not
return.
When I upgrade my system from 15.4 to 15.10, but there was one error, it might
be it. Contents I forgot. That compila
seems to be mesa-specific
--
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/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
instantly
To manage notifications about
I swear I've also seen Mir 0.17.1 fail similarly (Unity8 on xenial
desktop). I might be imagining things, or I might have been seeing some
side-effect of bug 1506707 that perhaps also led to similar problems?...
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Bisected. The problem originated in:
revno: 3098 [merge]
author: Cemil Azizoglu
committer: Tarmac
branch nick: development-branch
timestamp: Tue 2015-11-10 23:10:22 +
message:
Tighten probing rules. Fixes: https://bugs.launchpad.n
Confirmed, reverting r3098 fixes the problem.
** Tags added: nested
--
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/1526209
Title:
[regression] Clients of nested Mir servers silently crash/exit
just updated to kernel 4.4.0-rc4-next-20151211-1.g34634ae-vanilla from
opensuse kernel next repo, and the warnings seem to be gone. if i get
some time later i will have to test with kde too if the graphic bugs and
crashes are gone too.
--
You received this bug notification because you are a membe
** Changed in: compiz
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-gtest in Ubuntu.
https://bugs.launchpad.net/bugs/1521366
Title:
Compiz fails to build tests with recent pkg-config and xorg-
Annoyingly bisection is going to be slow, because of a separate
regression - bug 1526225.
--
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/1526209
Title:
[regression] Clients of nested Mir servers
Public bug reported:
dpkg-reconfigure fglrx-updates-core
Removing all DKMS Modules
Done.
Loading new fglrx-updates-core-15.200 DKMS files...
Building only for 4.2.0-19-generic
Building for architecture amd64
Building initial module for 4.2.0-19-generic
ERROR: Cannot create report: [Errno 17] File
Connecting a software client to the affected nested server actually made
the nested server crash:
ERROR: /home/dan/bzr/mir/fixmirout/src/gl/recently_used_cache.cpp(44): Throw in
function virtual std::shared_ptr
mir::gl::RecentlyUsedCache::load(const mir::graphics::Renderable&)
Dynamic exception
Public bug reported:
Clients of nested Mir servers silently crash/exit instantly...
This happens in Mir trunk lp:mir and lp:mir/0.18, but not in lp:mir/0.17
sudo bin/mir_demo_server_minimal -f /tmp/outside &
sudo bin/mir_proving_server -f /tmp/inside --host-socket=/tmp/outside &
sudo bin/m
Public bug reported:
I have 3 screens including the laptop screen. The one connected to the
displayport is going in to power save mode and back in random
intervalls. The other screens don't care if the displayport one is
going back and forth to power save mode like it does when you unplug the
dis
65 matches
Mail list logo
