I'm not skilled at all with hwdb & libinput syntax : didn't you forget
the "pn" substring before *XPSL322X* ?
Le 15/04/2018 à 05:02, seanlano a écrit :
> I've updated my patch to libinput, in
> https://bugs.freedesktop.org/show_bug.cgi?id=104990#c25
>
> Hopefully the devs there will shortly be abl
*** This bug is a duplicate of bug 1750138 ***
https://bugs.launchpad.net/bugs/1750138
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1750138, so is being marked as such.
Public bug reported:
Description:Ubuntu 16.04.4 LTS
Release:16.04
Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
#43~16.04.1-Ubuntu SMP
Hi Marc.
I apologize for not mentioning a release type. It's Xubuntu 16.04 LTS.
For now, I have no access to my other computer with Ubuntu 16.04 LTS so
I can not verify this issue. Sorry.
Is it a problem, that incorrect permission - in this case - are in
Xubuntu and not in Ubuntu? Will it be fixe
** Changed in: xkeyboard-config
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/62587
Title:
Ligatures problem in Arabic keyboard layout
To manag
On my machine, the complete string is
dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1
- so the *XPSL322X* seems to still match. I'm not sure on the syntax
either really, but it seemed to work for me at least - did it work f
Public bug reported:
Touchpad worked perfectly in Ubuntu 17.10 when using one and two fingers
clicks, two finger scrolling, and tapping. (I don't know if multitouch
worked, but IIRC it did in the past with Unity)
After upgrading to Bionic Beaver it frequently becomes unresponsive,
during which I
** Attachment added: "xinput"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116384/+files/xinput
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https:
** Attachment added: "xev.log"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116386/+files/xev.log
** Summary changed:
- 'Apple touchpad bcm5974' stops being reponsive until finger is lifted after
moving cursor a bit in 'Apple MacBookPro5,4
** Attachment added: "evtest"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116385/+files/evtest
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https:
*** This bug is a duplicate of bug 1546541 ***
https://bugs.launchpad.net/bugs/1546541
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1546541, so is being marked as such.
** Description changed:
+ Report created by following
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.
+ Let me know if anything is wrong or if I can give more info
+
Touchpad worked perfectly in Ubuntu 17.10 whe
It does.
You see, I believe bvr in the string surely stands for BIOS Vendor
Release. You are @A08, and I @A10. This may be the reason for a
different "pn" returned string for the exactly same computer.
Silly Vendor
Thank you Sean
Le 15/04/2018 à 12:24, seanlano a écrit :
> On my machine, the compl
I have the same issue.
$ uname -a
Linux mh-lt-asus 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -r
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubunt
I upgraded to Bionic using a GeForce 950 and got a blank screen when
lightdm should have been visible. The only way I have been able to get
it working has been to delete /etc/X11/xorg.conf which was being used
before since my card was overclocked. If nvidia-xconfig is used later
and creates xorg.co
All things as mentioned above are garbage
--
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/1752053
Title:
nvidia-390 fails to boot graphical display
To manage notifications about
** Attachment added: "Full kern.log from April 1 crash"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.lau
Public bug reported:
Unfortunately, I had to create a second bug report because apport-
collect will not accept a different set of Launchpad user credentials
from those I used to create the original bug report (#1763273). My
apologies, but I had to use a different Launchpad account to run apport-
When I get home I'll copy these attachments and data into the original
bug report under my personal Launchpad account.
--
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/1764211
Title:
apport bug de
Further details from apport-bug are in #1764211; I'll copy them into
this account using my "cdarroch" personal Launchpad account in a few
hours, when I get home.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchp
Thanks for the bug report. It's been a known issue for a while:
https://bugzilla.gnome.org/show_bug.cgi?id=781296
** Bug watch added: GNOME Bug Tracker #781296
https://bugzilla.gnome.org/show_bug.cgi?id=781296
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Also affects: mutter via
Incomplete per upstream bug:
https://bugs.freedesktop.org/show_bug.cgi?id=105753
** Changed in: libinput (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bug
@update. Started occurring even when bypassing the Avocent.
--
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/1763975
Title:
DP1.2 daisy-chain flickering
To manage notifications about this bug go
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+files/Xorg.0.log
--
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/1763273
Title
Further debugging today while I'm on-site with the kiosks. The system
froze, as usual, after normal idle screen blanking. I was able to login
via ssh and retrieve some details.
First, it appears that the basic screen blanking problem is somehow
related to the Radeon driver. I will attach the Xo
** Attachment added: "gdb-Xorg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.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/1763273
T
** Attachment added: "rom.vga.bin"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin
--
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/1763273
Tit
While logged in via ssh to the machine with the "hung" Xorg (screen
blank, no way to recover except Alt-SysRq-k), I dumped the output of
Alt-SysRq-t into the syslog -- see attached file. Not sure this is much
use, however. Just trying to be complete while I'm on-site with a hung
machine.
** Atta
Public bug reported:
Hello,
kubuntu 18.04 beta 1
I often use :
X-KDE-SubstituteUID=true
X-KDE-Username=root
in the file ".desktop" for applications who may have root id.
Example, luckybackup, system-config-samba
No bug in a plasma session.
With wayland, using the same desktop, the appli
** Description changed:
Hello,
kubuntu 18.04 beta 1
I often use :
X-KDE-SubstituteUID=true
X-KDE-Username=root
in the file ".desktop" for applications who may have root id.
Example, luckybackup, system-config-samba
No bug in a plasma session.
With wayland
** Package changed: wayland (Ubuntu) => kwin (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1764252
Title:
X-KDE-SubstituteUID=true / root can't be used in wayland
To manage notific
Here are the details from apport-bug, as promised (copied from #1764211
because I had to use a different Launchpad account):
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
.
32 matches
Mail list logo
