Public bug reported:
I have several computers running 20.04 and a couple running 22.04. VNC
was great on 20.04. I could connect using remina or real vnc no problem.
on the 22.04 machines though, I cannot connect reliably at all. If the
server montitor is in sleep, the server rejects the
Public bug reported:
On my tablet PC, the screen rotates automatically by 90° as soon as I
disconnect the physical keyboard (that came with the tablet)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
--
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/2020604
Title:
After mesa upgrades, Chrome won't show graphics
To manage notifications about this bug go to:
Public bug reported:
After each brightness-step change (via using Fn+arrow up-/arrow-down
keys), system freezes for ~500ms. With my notebook's 10 brightness-
levels, this often results in total delay from 10x 500ms, = 5 entire
seconds for the notebook finishing a multi-step brightness-change in
** Attachment added: "brightness.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2016281/+attachment/5663971/+files/brightness.png
** Description changed:
After each brightness-step change (via using Fn+arrow up-/arrow-down
keys), system freezes for ~500ms. With my notebook's 10
The corruption occurs as soon as "try ubuntu" is clicked and seems to be
caused by the "automatic" color-profile being applied ("Automatic -
C24F390", Samsung monitor C24F390). It can temporarily be fixed by
removing the automatic profile and activating "Colorspace sRGB" profile.
A permanent patch
** Description changed:
using the "try ubuntu" feature, this is what the entire experience looks
- like (see the 2nd attached screenshot in comment #2).
+ like (see the 2nd attached image in comment #2).
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
Thanks for the report, Mike.
Indeed testing the Flutterstaller ISO in a VM is a bit crashy right now.
I've changed the package since this particular crash doesn't seem
Subiquity related.
** Also affects: xserver-xorg-video-qxl (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
** Changed in: trusty-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libwacom in Ubuntu.
https://bugs.launchpad.net/bugs/1532052
Title:
"no tablet detected" message in system settings for
** Changed in: xenial-backports
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1003950
Title:
launcher does not show minimized update
@cpaelzer the build and/or autopkgtest requirement for MIR possibly
should be expanded to allow for hardware-specific code like this, where
'normal' testing isn't easy and/or possible. In such cases, IMO at
least, it seems like an exception would be reasonable, but only if the
subscribing team
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1864781
Title:
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1812356
Title:
AlpsPS/2 ALPS
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1825499
Title:
Touchpad vertical
** Changed in: systemd (Ubuntu)
Status: New => Won't Fix
--
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/1554662
Title:
First client to invoke Xorg via systemd socket activation
> Kernel says: x [1266..5678], y [1162..4694]
> Touchpad sends: x [1266..5678], y [1161..4694] -^C
unless I'm reading that wrong, the kernel reports exactly the same range
as the touchpad sends, so there should be no need for the hwdb to carry
x/y values overridding the kernel-reported ranges
In
Yes - "after login" means after I have successfully entered my password.
Also, I have not been able to locate the 'Ubuntu on Wayland' selection.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Attached prevboot.txt as instructed. Thanks for your assistance.
** Attachment added: "Output of 'journalctl -b-1 > prevboot.txt'"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901342/+attachment/5427638/+files/prevboot.txt
--
You received this bug notification because you are
Public bug reported:
Description:Ubuntu 20.10
Release:20.10
5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64
x86_64 GNU/Linux
After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu splash
screen after login. Workaround: Press CTRL+ALT+DEL then
I saw this on an ubuntu 20.04 alpha system when I did 'ubuntu-drivers install'
to
get drivers for my gtx 1080. Reinstalling ubuntu 20.04 final made the problem
vanish
(whew).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Screen shots of the corruption do not work as the screen shot tool
appears to overwrite the corruption. Video capture does work.
** Attachment added: "Video capture of screen corruption"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+attachment/5273854/+files/screen-speckles.ogv
Public bug reported:
Regularly the screen displays corruptions that change depending on disk
i/o, keyboard/mouse and other system activity. The screen corruptions do
not appear on each session and can be removed by selecting an
alternative resolution and then changing back (or reverting without
Removing the nomodeset kernel parameter makes GDM snappier, but it then
hangs on login (relevant portion of syslog attached).
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1830029/+attachment/5265713/+files/syslog
--
You received this bug notification
Public bug reported:
I am trying to use the nouveau drivers on a recent (today) install of
18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at
all.
What I am finding is that the sluggishness of the display is comparable
to the case when nouveau drivers are disabled. The only
Public bug reported:
Installing the nvidia-driver-390 package and disabling (or not) the
nouveau drivers results in a system that superficially appears to busy
hang before reaching the login screen, leaving only the fsck
"/dev/sda1: clean,..." message on the screen.
The machine is alive, and
Public bug reported:
I've been testing as follows:
- install chromium (or chrome, or chrome beta)
- open http://fishgl.com
- crank up number of fish to 325 (or as high as it'll go and sustain 60 fps)
- after fish are happily swimming, watch them swim for 60 seconds, and count
number of times the
Public bug reported:
I've been testing Ubuntu 18.04.1 with Hades Canyon using the recipe
https://mzwiki.oblong.com/wiki/Hades_Canyon
My smoke test is:
- install chromium (or chrome, or chrome beta)
- open http://fishgl.com
- crank up number of fish to 325 (or as high as it'll go and sustain 60
@Alberto:
Sorry for the lateness of my reply, apparently Launchpad doesn't
automatically subscribe me just because I commented...
Anyway, I am attaching both gpu-manager.log and gpu-manager-switch.log
for when both the Nvidia profile and Intel profiles are selected.
FWIW, I discovered that once
I noticed off a clean boot on Intel gpu-manager.log was different from
when I just logged out and logged back in so I'm attaching that file
now.
No change as far as power consumption goes though.
** Attachment added: "gpu-manager.log"
I'm still experiencing high power consumption with GDM3 on Cosmic with
0.8.10 of nvidia-prime. Can provide logs/hardware info if it's helpful,
just let me know what you need. Nouveau or manually disabling the DGPU
in the BIOS behaves as expected.
--
You received this bug notification because you
I'm still experiencing high power consumption with GDM3 on Cosmic with
0.8.10 of nvidia-prime. Can provide logs/hardware info if it's helpful,
just let me know what you need. Nouveau or manually disabling the DGPU
in the BIOS behaves as expected.
--
You received this bug notification because you
Actually my issue is much closer to bug 1791427 (comment #62).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1696929
Title:
Touchpads are unresponsive and laggy for small finger movements
I see a much worse version of this problem on my brand new ThinkPad X1
Carbon 6th gen: the mouse cursor moves/clicks only about 5% of the time
I use the touchpad. The Trackpoint doesn't work at all. Installing
Ubuntu was a keyboard-only affair, and I hoped that some updates would
fix this
Same problem, no external monitor via HDMI detected:
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 309mm x 173mm
1920x1080 60.03*+ 60.0159.9759.9659.9348.03
I should have mentioned, my Hades has 32GB of RAM.
With 8GB or less of RAM, the problem might persist (if I understand the mailing
list posts).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
This just changed for me... but the hardware may matter, as I'm on Hades
Canyon, using the amd gpu, not HD graphics.
A few days ago I updated to the then-latest 4.19-rc2
(and wrote https://ubuntuforums.org/showthread.php?t=2400400 documenting
exactly what I did).
Using plain old X (no desktop) on
This just hit me as well, on a kosher 18.04 system.
I recently upgraded to a newer nvidia card, so that must have mangled it
somehow.
Looks like three of its symlinks got nuked:
ls: cannot access '/usr/lib/x86_64-linux-gnu/libEGL.so': No such file or
directory
ls: cannot access
Public bug reported:
When I use an audio/video receiver, if I change inputs or turn off my
TV, my windows will change positions.
I think maybe this is because my receiver is capable of 4096x2160 and my
TV has a native resolution of 3,840x2,160 and it's resizing everything
to match the 9:5 aspect
> now our toughbook CF-19 touchscreens can't be calibrated
I also use toughbooks, CF-29s and CF-30s, which I think use the same
resistive touchscreen as the CF-19s, that requires software calibration.
Unfortunately all the cool new tiny (and very delicate) touchscreen
tablets and laptops use
Thanks... sounds like it's a hardware limitation, and the fix involves noticing
when the limit's being violated, and doing extra work in that case.
I wonder what the framerate impact of that extra work will be.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Thanks, I'll try weston-launch when I get a chance, and I'll try it on
ubuntu 18.04 with intel graphics.
In the meantime, I checked the maximum size a few systems report, and it
does seem to be a property of the graphics hardware and/or driver.
See also
Sorry, that Intel URL should have been
https://www.intel.com/content/www/us/en/support/articles/05571/mini-
pcs.html
--
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/1776260
Title:
Public bug reported:
https://www.intel.com/content/www/us.../mini-pcs.html
claims that the Skull Canyon ( NUC6i7KYK ) can handle three 4k displays, so
I'm experimenting with a Skull Canyon running a fresh minimal Ubuntu 18.04.
It works great when plugged into one 4k monitor (via any of the three
Still in ubuntu 17.10 with nvidia card.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1655709
Title:
Spurious crash report dialog on every login
To manage notifications about this bug go to:
** Attachment added: "20180222_133958.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751120/+attachment/5060610/+files/20180222_133958.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
My mouse cursor would still move, but I couldn't do anything.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
The attached photo displays what I end up stuck with.
** Attachment added: "20180207_165829.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748029/+attachment/5050935/+files/20180207_165829.jpg
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug
Public bug reported:
I have an external monitor in portrait mode, which means that the top of
my external monitor is substantially above my laptop monitor (which has
the top bar). If I move a window by holding Meta and dragging it from
the bottom, and accidentally let go with the window
Now what? will you send me an email, what do I expect now?
--
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/1734014
Title:
updates won't load
To manage notifications about this bug go to:
I need some one to tell me what to do in plain English. Dumbfounded.
--
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/1734014
Title:
updates won't load
To manage notifications about this bug go
This seems like the same kind of problem I have been having for a while.
This is kind of the same problem I was having when my vista program
died.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
that a new OS
system was available and I thought I would install it but I found later
on it was not finished and that it was not a long term system any way
opps I think that is where I stubed my tow. Any way I have a mess. I am
tempted to just reinstall this system. Dan Purdy
ProblemType: Bug
Public bug reported:
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Table at 0x000E.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: 1.5.8
Release Date: 08/07/2017
Address: 0xF
Runtime Size: 64
As a reference, here is one posted workaround:
https://wiki.archlinux.org/index.php/Talk:Calibrating_Touchscreen#Libinput_breaks_xinput_calibrator
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
with the libinput xorg driver. This
results in a mis/un-calibrated touchscreen, and no way to calibrate it.
** Affects: xserver-xorg-input-libinput (Ubuntu)
Importance: Low
Assignee: Dan Streetman (ddstreet)
Status: New
** Changed in: xserver-xorg-input-libinput (Ubuntu)
I'm also seeing this issue with Wayland/GNOME on artful; any chance it
might be addressed before artful releases?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1705402
Title:
Touchpad
Public bug reported:
#BASIC SETUP
-server side: ext4 / lubuntu 14.04.5 / 4.4.0-72-generic #93~14.04.1-Ubuntu SMP
.. i686 / samba 4.3.11
-client side: ext4 / lubuntu 14.04.5 / 4.4.0-75-generic #96~14.04.1-Ubuntu SMP
x86_64 / mount.cifs 6.0
-both server and client are up-to-date
-mount line:
can confirm this on my pc
Host bridge: 915GM/PM/GMS/910GML / pentium M 1.7 lubuntu 14.04.5 i386
ive with tested the following kernels
3.19.0-80 is ok
4.2.0-22 is ok
4.2.0-42 is ok
4.4.0-21 many errors
4.4.0-22 errors
4.4.0-72 errors
4.4.0-75 errors
--
You received this bug notification because
can confirm this on my pc
Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML
pentium M 1.8
lubuntu 14.04.5 i376
ive tested the following kernels
3.19.0-80 is ok
4.2.0-22 is ok
4.2.0-42 is ok
4.4.0-21 many errors
4.4.0-22 errors
4.4.0-72 errors
4.4.0-75 errors
--
You received this bug
Public bug reported:
moving from windows 10 and I'd like to help outthis made my old
laptop scream thanks
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
I have no clue why I am getting this ms.
--
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/1658466
Title:
info not down loaded
To manage notifications about this bug go to:
Public bug reported:
extra information not down loaded.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.5
Public bug reported:
For the last few years, on nearly all my computers, ubuntu has
rewarded my logging in with a crash dialog. Nothing's actually
wrong; xorg probably trips over its shoelaces every time it
shuts down, but so late in the process that it doesn't matter.
Today I went through the
Not sure which package this should be against; since it might be DRM,
maybe it should be against the linux kernel?
--
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/1639640
I booted with drm.debug=14 and looked at the output of dmesg. It had lines like
[0.717202] [drm:i915_dump_device_info] i915 device info: gen=7,
pciid=0x0412 rev=0x06
flags=need_gfx_hws,is_haswell,has_fbc,has_hotplug,has_llc,has_ddi,has_fpga_dbg,
...
[0.938640]
Seems to have gotten worse with the next batch of updates
(linux-image-4.4.0-47-generic:amd64); now it won't show a screen at all, even
when booting to multiuser, after the kernel sets the
graphics mode. Works fine if I give nomodeset, but then I can't use
accelerated graphics.
--
You
Public bug reported:
After a recent update (early Nov 2016), my 16.04 system (an HP Pavillion
500-321, i.e. a generic i5-4570 system with integrated graphics) started
showing a black screen on boot (after the grub menu finished).
A fresh 16.10 live USB image also has the same problem on this
It's unbelievable that this bug hasn't been fixed in more than a year
and a half.
How difficult is it to add a "Primary monitor" setting?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
When I started looking at this problem, the machine would not boot
without nomodeset. This is no longer the case - and removing that fixes
the problem.
Thank you for looking at this, Timo. Please mark as invalid.
--
You received this bug notification because you are a member of Ubuntu-X,
which
OK, `gdb64 /usr/lib/xorg/Xorg 2>&1 | tee gdb-Xorg.txt' works. The
instructions for backtracing at
https://wiki.ubuntu.com/X/Backtracing#Backtrace_with_gdb obviously need
some love.
With all the complaints from gdb out of the way it seems that the issue
shows up as the corrupted shared library
I have sorted out the syscall-template.S issue by getting the libc6
source.
I have found places saying that the cause of gdb not liking the binary
is because of arch incompatibility (32 v 64). I tried this with no
change.
~# gdb /usr/bin/Xorg 2>&1 | tee gdb-Xorg.txt
GNU gdb (Ubuntu
Yoo hoo! Is anyone home?
Some triage love would be greatly appreciated here.
--
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/1591472
Title:
Xorg crashes immediately on login returning to
Yes. I worked around the problem by installing the latest nvidia
proprietary driver from nvidia's download site.
--
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/1572587
Title:
mouse cursor
Public bug reported:
~ $ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
~ $ apt-cache policy nvidia-361 xorg
nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
*** 361.42-0ubuntu2 500
500
and a nastier one:
[13882.769753] [drm:drm_edid_block_valid [drm]] *ERROR* EDID checksum is
invalid, remainder is 155
[13882.769759] Raw EDID:
[13882.769763] 00 ff ff ff ff ff ff 00 04 72 3a 01 5f 15 00 35
[13882.769765] 32 17 01 03 80 33 1d 78 2a e5 95 a6 56 52 9d 27
Go the same error several times on Linux ubuntu 4.4.0-22-generic
#39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 x86_64
GNU/Linux, running on ASROCK N3700 ITX motherboard.
[ 4521.775619] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update
failure on pipe A (start=45955 end=45956)
Public bug reported:
Using a second monitor with my lenovo laptop.
The mouse cursor forms a trail only on the second monitor and slowly disappears
after a few seconds or a right mouse click .
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature:
Public bug reported:
https://forums.linuxmint.com/viewtopic.php?t=219807=1152439#p1152439
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-32-generic i686
ApportVersion:
** Bug watch added: freedesktop.org Bugzilla #89055
https://bugs.freedesktop.org/show_bug.cgi?id=89055
** Also affects: xorg-server via
https://bugs.freedesktop.org/show_bug.cgi?id=89055
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
I always get an warning and stacktrace (and it seems to hang a little
bit). This occurs after reboot as well as when I move with the cursor
between my hdmi monitor and my laptop. (This only occurs when HDMI is
connected)
Default Kubuntu install version 15.10 with kernel
Also with kernel 4.3 the problem persists.
[ cut here ]
[Sam Dez 5 23:23:25 2015] WARNING: CPU: 2 PID: 880 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3668
skl_update_other_pipe_wm+0x1de/0x1f0 [i915]()
[Sam Dez 5 23:23:25 2015] WARN_ON(!wm_changed)
[Sam
Public bug reported:
A library which is being developed against the nvidia libGL.so fails to link
against mesa's libGL.so.
The linker complains:
foo: undefined reference to `glProgramUniform1fv'
foo: undefined reference to `glProgramUniform1i'
foo: undefined reference to `glProgramUniform2fv'
I still seem to be having issues here. Did a fresh install of 14.04.3,
allowed updates during the install. Kernel is 3.19.0-26-generic and I
have fglrx 2:15.200-0ubuntu0.5. Still get flickering and erratic video
behaviour when I use chrome. Doesn't seem to do it when I open the dash
or am using
Workaround: at boot, press F2 to get into BIOS, then set trackpad to Basic
instead of Advanced.
This even lets you scroll with a two-fingered gesture, and changes the output
of
cat /proc/bus/input/devices to:
I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
N: Name=SynPS/2 Synaptics
Public bug reported:
Live booting Ubuntu 15.04 via USB key worked, but touchpad and wifi
didn't work, had to plug in a mouse and ethernet. This report is about
the touchpad.
cat /proc/bus/input/devices says
I: Bus=0018 Vendor=06cb Product=2970 Version=0100
N: Name=SYN1B81:01 06CB:2970 UNKNOWN
** Description changed:
I'm using xubuntu 14.04 clean install with updates. Whenever I wake
from suspend, my mouse cursor is invisible, although still functional.
Sometimes suspending and resuming again fixes the problem but not
always.
+
+ I've also noticed that if I use lightlocker to
Public bug reported:
I'm using xubuntu 14.04 clean install with updates. Whenever I wake
from suspend, my mouse cursor is invisible, although still functional.
Sometimes suspending and resuming again fixes the problem but not
always.
I've also noticed that if I use lightlocker to lock the
I have added your patch with quilt, but repackaging with the following:
debuild -us -uc
gave me the following error:
...
/bin/sh: -c: line 2: unexpected sintax error near `done'
/bin/sh: -c: line 2: `done'
debian/rules:268: recipe for target 'pre-binary-arch' failed
make: *** [pre-binary-arch]
Solved - solution based on many pages like:
http://cs-people.bu.edu/doucette/xia/guides/debian-patch.txt
https://wiki.debian.org/UsingQuilt
(and many more I forgot ... sorry)
So, I will try to write some quick steps so you can build your own
fglrx-installer-updates package until properly
Can verify that this isn't fixed...total mess when using external
monitor on my T450s.
--
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/1432194
Title:
Graphics unstable on
However, the suggested temporary fix in #36 has seems to have helped for
now.
--
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/1432194
Title:
Graphics unstable on Ubuntu 14.04
Spoke too soon; nothing has changed.
--
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/1432194
Title:
Graphics unstable on Ubuntu 14.04 and 14.10 using Intel HD Graphics
5500
syslog shows colord: Device added: xrandr-Fujitsu Siemens Computers
GmbH-C17-3-YEAW191036
Physical markings show it is Fujitsu Siemens scaleoview c17-3 s26361-k941-v200
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I tested with http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc2-vivid/
and the issue persists.
Added tags kernel-bug-exists-upstream kernel-bug-exists-upstream-4.1-rc2
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.1-rc2
--
You received this bug notification
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1404332/+attachment/4390233/+files/Lsusb.txt
--
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/1404332
Title:
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1404332/+attachment/4390244/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1404332/+attachment/4390238/+files/UdevDb.txt
--
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/1404332
Title:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1404332/+attachment/4390226/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: JournalErrors.txt
https://bugs.launchpad.net/bugs/1404332/+attachment/4390229/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1404332/+attachment/4390232/+files/Lspci.txt
--
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/1404332
Title:
1 - 100 of 300 matches
Mail list logo
