Public bug reported:
I got a crash report prompt during installation of 17.10 from USB stick.
I have no idea what was going on when it crashed.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
Sebastien, thanks for the quick response. I found an existing upstream
bug (https://bugzilla.gnome.org/show_bug.cgi?id=788097) which, while
lacking detail, seemed to match. I linked it to this issue.
** Bug watch added: GNOME Bug Tracker #788097
Public bug reported:
I have installed Ubuntu Server 17.10. At request from a colleague I
then tried to install ubuntu-desktop and enable screen sharing.
However, this did not work as expected. When trying to enable screen
sharing (same goes for file sharing), the enable button just jumps
I can confirm this. I am *not* using focus follows mouse. Steps to
reproduce (not 100%, it seems to come and go):
* Start Firefox on desktop 1, make sure unity launcher is visible
* Ctrl+alt+right to desktop 2
* Start Qt Creator
* Maximize window or move it so that it makes the launcher auto-hide
Workaround: xinput set-prop device id 257 1. Device id can be
obtained with xinput list.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771716
Title:
middle click emulation not working
--
This should be configurable in gnome-mouse-properties I guess -
emulation is required to get usable copy/paste with a two-button mouse,
so having to hack config files is not really acceptable. Can this bug be
moved to that package or should a new one be created? Or are there other
options to get
This also affects me, using a Logitech Trackman Marble, attaching the
output of xinput list
** Attachment added: xinput-list.txt
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/771716/+attachment/2092514/+files/xinput-list.txt
--
You received this bug notification
@Mike: 9.04 worked during the install for me, but then I got random
graphics freezes during normal usage (might not be related to this bug).
Another workaround that works for me is to use an external display (with
10.04).
--
[i915] blank screen on Latitude E6410
I can also report success with linux-image-2.6.35-20-generic-pae
2.6.35-20.29~lucid1 (from kernel-ppa) on E5410, i3. Screen lights up
during boot, suspend/resume works and no crash when
connecting/disconnecting external monitor.
--
[i915] blank screen on Latitude E6410
I can't even verify the fix - on my E5410 core i3, the screen doesn't
even turn on during boot using 2.6.32-25.42 (however, the boot seems to
go fine otherwise). I, like dragilla, use the PAE kernel, I also tried
the normal one, but then there was some trouble detecting my hard drive
and I
@Carlos: that kernel is a pre-proposed one, and as far as I can tell not
the one referred to in #106. Thus, I still have the same question as
Paulo.
--
[arrandale] Resume doesn't work on a Latitude E6410
https://bugs.launchpad.net/bugs/578673
You received this bug notification because you are a
I have this issue, but on E5410 (core i3+arrandale). Resume works apart
from the screen being blank, i.e. I can ssh into the box and reboot it.
However, the backported kernel in #103 does not work for me. I think
there is some improvement, because now the backlight turns on, but still
no image.
Update: When the display backlight is shut down by power management,
after a failed resume, everything goes back to normal again (i.e.
pressing any key turns on the screen and shows the screen lock prompt).
--
[arrandale] Resume doesn't work on a Latitude E6410
13 matches
Mail list logo
