[Desktop-packages] [Bug 1969250] [NEW] gdm disables wayland for all(?) non-nvidia cards since 42.0-1ubuntu4
Public bug reported:
I was happily using wayland so far on an Intel Tiger Lake laptop. Then I
did an upgrade, including upgrading gdm3 42.0-1ubuntu2 to 42.0-1ubuntu4,
rebooted, and got logged into an Xorg session.
Investigating, it seems this was caused by this patch, reverting in
manually locally fixes things: https://salsa.debian.org/gnome-
team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on-
nvidia-if-suspend-is-broken.patch
Looking at the patch, it seems that the checks introduced by it are
nvidia-specific, but are applied to *all* other cards as well. There
used to be an nvidia-only check wrapping these checeks, but that was
reverted as part of 42.0-1ubuntu4 here: https://salsa.debian.org/gnome-
team/gdm/-/commit/e2f0cca51dd9638c5b2a74a9739539ef4fd427bd
I think this is a pretty urgent and issue. I haven't tested on multiple
machines, but AFAICS this will be unintentionally be disabling wayland
for a lot of people...
I can provide more hardware details, but I think the bug will be obvious
if you look at the resulting 61-gdm.rules file (here's an excerpt,
including some context around the nvidia checks to see they are
unguarded):
LABEL="gdm_pci_device_end"
# disable Wayland if modesetting is disabled
KERNEL!="card[0-9]*", GOTO="gdm_nomodeset_end"
SUBSYSTEM!="drm", GOTO="gdm_nomodeset_end"
IMPORT{parent}="GDM_MACHINE_HAS_VIRTUAL_GPU"
ENV{GDM_MACHINE_HAS_VIRTUAL_GPU}!="1", RUN+="/usr/bin/touch
/run/udev/gdm-machine-has-hardware-gpu"
# but keep it enabled for simple framebuffer drivers
DRIVERS=="simple-framebuffer", GOTO="gdm_nomodeset_end"
IMPORT{cmdline}="nomodeset", GOTO="gdm_disable_wayland"
LABEL="gdm_nomodeset_end"
# Check if suspend/resume services necessary for working wayland support is
available
TEST{0711}!="/usr/bin/nvidia-sleep.sh", GOTO="gdm_disable_wayland"
TEST{0711}!="/usr/lib/systemd/system-sleep/nvidia", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c \"sed -e 's/: /=/g' -e
's/\([^[:upper:]]\)\([[:upper:]]\)/\1_\2/g' -e 's/[[:lower:]]/\U&/g' -e
's/^/NVIDIA_/' /proc/driver/nvidia/params\""
ENV{NVIDIA_PRESERVE_VIDEO_MEMORY_ALLOCATIONS}!="1", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_HIBERNATE=`systemctl is-enabled
nvidia-hibernate`'"
ENV{NVIDIA_HIBERNATE}!="enabled", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_RESUME=`systemctl is-enabled
nvidia-resume`'"
ENV{NVIDIA_RESUME}!="enabled", GOTO="gdm_disable_wayland"
IMPORT{program}="/bin/sh -c 'echo NVIDIA_SUSPEND=`systemctl is-enabled
nvidia-suspend`'"
ENV{NVIDIA_SUSPEND}!="enabled", GOTO="gdm_disable_wayland"
#
# Disable wayland when nvidia modeset is disabled or when drivers are a lower
# version than 470,
# For versions above 470 but lower than 510 prefer Xorg,
# Above 510, prefer Wayland.
KERNEL!="nvidia_drm", GOTO="gdm_nvidia_drm_end"
SUBSYSTEM!="module", GOTO="gdm_nvidia_drm_end"
ACTION!="add", GOTO="gdm_nvidia_drm_end"
# disable wayland if nvidia-drm modeset is not enabled
ATTR{parameters/modeset}!="Y", GOTO="gdm_disable_wayland"
# disable wayland for nvidia drivers versions lower than 470
ATTR{version}=="4[0-6][0-9].*|[0-3][0-9][0-9].*|[0-9][0-9].*|[0-9].*",
GOTO="gdm_disable_wayland"
# For nvidia drivers versions Above 510, keep Wayland by default
ATTR{version}=="[5-9][1-9][0-9].*", GOTO="gdm_end"
# For nvidia drivers versions 470-495, prefer Xorg by default
GOTO="gdm_prefer_xorg"
LABEL="gdm_nvidia_drm_end"
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1969250
Title:
gdm disables wayland for all(?) non-nvidia cards since 42.0-1ubuntu4
Status in gdm3 package in Ubuntu:
New
Bug description:
I was happily using wayland so far on an Intel Tiger Lake laptop. Then
I did an upgrade, including upgrading gdm3 42.0-1ubuntu2 to
42.0-1ubuntu4, rebooted, and got logged into an Xorg session.
Investigating, it seems this was caused by this patch, reverting in
manually locally fixes things: https://salsa.debian.org/gnome-
team/gdm/-/blob/ubuntu/master/debian/patches/data-Disable-wayland-on-
nvidia-if-suspend-is-broken.patch
Looking at the patch, it seems that the checks introduced by it are
nvidia-specific, but are applied to *all* other cards as well. There
used to be an nvidia-only check wrapping these checeks, but that was
reverted as part of 42.0-1ubuntu4 here:
https://salsa.debian.org/gnome-
team/gdm/-/commit/e2f0cca51dd9638c5b2a74a9739539ef4fd427bd
I think this is a pretty urgent and issue. I haven't tested on
multiple machines, but AFAICS this will be unintentionally be
disabling wayland for a lot of people...
I can provide more hardware details, but I think the bug will be
obvious if you look at the resulting 61-gdm.rules file (here's an
excerpt, including some context around the nvidia checks to see they
are
[Desktop-packages] [Bug 1955850] [NEW] /etc/X11/Xresources no longer loaded, error in patch
Public bug reported: After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory no longer loads on login. Looking at the sources, I think this can be traced to: - Switching from a custom Xsession file to the upstream Xsession file in 3.38.0-1ubuntu1, combined with - An oversight in `debian/patches/ubuntu/xresources_is_a_dir.patch` Looking at [that patch](https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/debian/patches/ubuntu/xresources_is_a_dir.patch), it has: ```diff --- a/data/Xsession.in +++ b/data/Xsession.in @@ -122,6 +122,13 @@ fi if [ -f "$sysresources" ]; then xrdb -nocpp -merge "$sysresources" +elif [ -d "$sysresources" ]; then +# directory of Xresources files on Debian/Ubuntu +for i in `ls "$sysresources"` ; do +if [ -r "$sysresources/$i" -a -f "$sysresources/$i" ] && expr "$i" : '^[[:alnum:]_-]\+$' > /dev/null; then +xrdb -nocpp -merge "$sysresources/$i" +fi +done fi if [ -f "$userresources" ]; then ``` However, looking a few lines further up in [the original Xsession.in file](https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/data/Xsession.in#L97), I see: ```sh if [ -f /etc/X11/Xresources ]; then sysresources=/etc/X11/Xresources else sysresources=/usr/etc/X11/Xresources fi ``` In other words, if `/etc/X11/Xresources` is a directory, the `sysresources` variable is never set correctly, so the patch should also modify this part of the script. I have observed this broken behavior on version 41~rc-0ubuntu2, but looking at the ubuntu/master branch (as linked above), it still seems broken there. I'm currently testing this patch: ```diff --- Xsession.orig 2021-12-27 22:05:09.038863375 +0100 +++ Xsession2021-12-27 22:05:33.143057433 +0100 @@ -111,7 +111,7 @@ usermodmap="$HOME/.Xmodmap" userxkbmap="$HOME/.Xkbmap" -if [ -f /etc/X11/Xresources ]; then +if [ -e /etc/X11/Xresources ]; then sysresources=/etc/X11/Xresources else sysresources=/usr/etc/X11/Xresources ``` I don't know if it works yet, since I need to log out for that, and close my browser, so need to submit this report first ;-) ``` $ lsb_release -rd Description:Ubuntu 21.10 Release:21.10 $ apt-cache policy gdm3 gdm3: Installed: 41~rc-0ubuntu2 Candidate: 41~rc-0ubuntu2 Version table: *** 41~rc-0ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status ``` ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1955850 Title: /etc/X11/Xresources no longer loaded, error in patch Status in gdm3 package in Ubuntu: New Bug description: After upgrading from 21.04 to 21.10, my /etc/X11/Xresources/ directory no longer loads on login. Looking at the sources, I think this can be traced to: - Switching from a custom Xsession file to the upstream Xsession file in 3.38.0-1ubuntu1, combined with - An oversight in `debian/patches/ubuntu/xresources_is_a_dir.patch` Looking at [that patch](https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/debian/patches/ubuntu/xresources_is_a_dir.patch), it has: ```diff --- a/data/Xsession.in +++ b/data/Xsession.in @@ -122,6 +122,13 @@ fi if [ -f "$sysresources" ]; then xrdb -nocpp -merge "$sysresources" +elif [ -d "$sysresources" ]; then +# directory of Xresources files on Debian/Ubuntu +for i in `ls "$sysresources"` ; do +if [ -r "$sysresources/$i" -a -f "$sysresources/$i" ] && expr "$i" : '^[[:alnum:]_-]\+$' > /dev/null; then +xrdb -nocpp -merge "$sysresources/$i" +fi +done fi if [ -f "$userresources" ]; then ``` However, looking a few lines further up in [the original Xsession.in file](https://salsa.debian.org/gnome- team/gdm/-/blob/ubuntu/master/data/Xsession.in#L97), I see: ```sh if [ -f /etc/X11/Xresources ]; then sysresources=/etc/X11/Xresources else sysresources=/usr/etc/X11/Xresources fi ``` In other words, if `/etc/X11/Xresources` is a directory, the `sysresources` variable is never set correctly, so the patch should also modify this part of the script. I have observed this broken behavior on version 41~rc-0ubuntu2, but looking at the ubuntu/master branch (as linked above), it still seems broken there. I'm currently testing this patch: ```diff --- Xsession.orig 2021-12-27 22:05:09.038863375 +0100 +++ Xsession2021-12-27 22:05:33.143057433 +0100 @@ -111,7 +111,7 @@ usermodmap="$HOME/.Xmodmap" userxkbmap="$HOME/.Xkbmap" -if [ -f /etc/X11/Xresources ]; then +if [ -e /etc/X11/Xresources ]; then sysresources=/etc/X11/Xresources else sysresources=/usr/etc/X11/Xresources ``` I don't know if it works yet, since
[Desktop-packages] [Bug 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend
I'm also running into this bug (or at least something that looks like it). Typically what happens for me is that I resume from suspend, get an unlock prompt (the system is locked on suspend) and when I log in, the unlock prompt stays visible (the password dots disappear, but I cannot type anything or click any buttons). When I then kill X to recover (ctrl-alt-backspace), I get a new login prompt. Sometimes, logging in again no longer works then, seeing such messages in the console: jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024" jun 21 17:01:50 grubby at-spi-bus-launcher[30649]: after 21 requests (21 known processed) with 0 events remaining. jun 21 17:01:50 grubby gsd-power[30703]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-keyboard[30715]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-xsettings[30696]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-media-keys[30731]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby systemd-logind[1100]: Session c9 logged out. Waiting for processes to exit. jun 21 17:01:50 grubby gsd-clipboard[30695]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gsd-color[30713]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. jun 21 17:01:50 grubby gnome-shell[30633]: Connection to xwayland lost >From the messages, I suspect this might be the same problem as the original >poster. However, I'm not entirely sure if at-spi-bus-launcher is actually the culprit here. Could it be that that the xserver or xwayland (I'm not sure which - I'm using the GNOME xorg session since the wayland session doesn't work for me, but the log does talk about xwayland) crashes and that at-spi-bus-launcher is just the first process to find out (because it does so many requests maybe?). I've also seen some instances where at-spi-bus-launcher is not the first one in the log, and I've tried disabling at-spi-bus-launcher by masking it in systemd (not entirely sure if that really worked), but then I also think I saw a crash where at-spi-bus-launcher would not show up in the log at all. One additional observation: At some point during testing, while login would not work, I found a logged in session in some virtual terminal. After logging out that session, logins would work again as normal. I'm not entirely sure if there's a causal relationship there, nor where that logged in session came from (but I was testing with two different users to see if there was something in my homedir that triggered it, so perhaps it came from one of those tests...). Vague, but I wanted to mention this just in case it triggers an idea somewhere :-) As for reporting an upstream issue, that is probably a good idea, though I'm not entirely sure where the cause is. It's probably safe to say it is something in gnome, though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1775392 Title: at-spi-bus-launcher makes Xorg crash when resuming from suspend Status in at-spi2-core package in Ubuntu: Confirmed Bug description: If at-spi2-core is installed, when resuming from suspend messages like these are logged in systemd journal: at-spi-bus-launcher[31720]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" at-spi-bus-launcher[31720]: after 8065 requests (8065 known processed) with 0 events remaining. The number of requests vary, it can reach more than 15000. Depending on the number of requests, the Xorg server crashes with SIGBUS. Depending on the exact moment Xorg crashes, when lightdm manages to recover, it shows a login greeter, or worst case scenario, it can't recover, a black screen is shown and the desptop session doesn't start. It took me a long time to discover the cause. The visible symptom was: once in a while when resuming from suspend, I got a login greeter instead of an unlock greeter, or a black screen which forced me to power down. Investigating, I found out that whenever that happened, there was a Xorg core left behind. Looking at the journal messages before the crash, there was always that flood of at-spi2-core requests. So I uninstalled at-spi2-core and Xorg never crashed anymore. This is a quite severe bug, which makes it impossible to use at- spi2-core. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: at-spi2-core (not installed) ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1
[Desktop-packages] [Bug 1796607] Re: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_dis
Seems upstream diagnosed and fixed this bug in their master branch two weeks ago, and the fix indeed got included in 3.32 (first in 3.31.92, though it seems to have been omitted from their changelog/NEWS file). Any chance of getting this fix backported into the Ubuntu cosmic package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796607 Title: gnome-shell crashed with SIGSEGV in meta_compositor_switch_workspace(compositor=NULL) → meta_workspace_activate_with_focus → meta_workspace_activate → meta_x11_display_new → meta_display_open Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell package in Fedora: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/853 https://gitlab.gnome.org/GNOME/mutter/issues/479 --- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/a7a2ba87e4d962b215ce37aaf80089f085e1db97 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
I also ran the i2c_hid module with debug enabled (`modprobe i2c_hid
debug=1`), which gives a bit of insight in what commands are sent to the
touch screen. On a suspend, it seems to send a sleep command. On a
resume, it sends a power on command, followed by a reset command (which
is properly acknowledge through an empty interrupt, as suggested by the
kernel sources). After that, no further activity happens for the touch
screen (its interrupt also does not trigger according to
/proc/interrupts).
I wonder if this device perhaps needs another power on command, or needs
to be reconfigured (setting report descriptors?) after a reset? I can't
quite find how to do this manually, so I might need to modify the kernel
module for that. Or perhaps try to sniff the windows driver to see how
that handles resume?
Since this device is autodetected through ACPI, I dumped and decompiled the
system's ACPI tables. The part about this device is here:
Scope (_SB.PCI0.I2C1)
{
Device (TPL4)
{
Name (_HID, "SYNA7508") // _HID: Hardware ID
Name (_CID, "PNP0C50" /* HID Protocol Device (I2C bus) */) //
_CID: Compatible ID
Name (_UID, One) // _UID: Unique ID
Name (_S0W, 0x04) // _S0W: S0 Device Wake State
Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
If ((Arg0 == ToUUID ("3cdff6f7-4267-4555-ad05-b30a3d8938de") /*
HID I2C Device */))
{
If ((Arg2 == Zero))
{
If ((Arg1 == One))
{
Return (Buffer (One)
{
0x03
// .
})
}
Else
{
Return (Buffer (One)
{
0x00
// .
})
}
}
If ((Arg2 == One))
{
Return (0x20)
}
}
Else
{
Return (Buffer (One)
{
0x00 // .
})
}
}
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (((SDS1 & 0x0200) == 0x0200))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
{
Name (SBFI, ResourceTemplate ()
{
I2cSerialBusV2 (0x0020, ControllerInitiated, 0x00061A80,
AddressingMode7Bit, "\\_SB.PCI0.I2C1",
0x00, ResourceConsumer, , Exclusive,
)
Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive,
,, )
{
0x0022,
}
GpioIo (Exclusive, PullDefault, 0x, 0x,
IoRestrictionInputOnly,
"\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0026
}
})
Return (SBFI) /* \_SB_.PCI0.I2C1.TPL4._CRS.SBFI */
}
}
}
In the last block, it describes the I2c address and interrupt that is
being used (also shown in /proc/interrupts). However, it also describes
some GPIO being relevant, but AFAICS the i2c_hid driver does not handle
any GPIOs, so this GPIO might be ignored (or might be handled by an
upper layer of ACPI). I wonder if this pin might be the subject of a
problem similar to the one fixed by https://marc.info/?l=linux-
gpio=147610677825233=2 (but that fixes the intel pinctrl driver, but
I think there are no pinctrl drivers involved here). I couldn't figure
out how to get the state of a GPIO pin, though (other than exporting it
to sysfs, which did not work, probably because the pin is in use?).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinput in Ubuntu.
https://bugs.launchpad.net/bugs/1796580
Title:
Touchscreen breaks after suspend on Acer Aspire Switch 11
Status in xinput package in Ubuntu:
New
Bug description:
I'm not entirely sure this bug belongs in package xinput, but I'm
following the lead of
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which
describes the same symptoms (but on other hardware, so likely a
[Desktop-packages] [Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
I dug around a bit, and found that the touchscreen can also be fixed by reloading the ic2_hid module. It also works to reinitialize just the hid driver for the touchscreen (rather than reloading the entire module) by running: echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/unbind echo 0018:06CB:77B2.000C > /sys/bus/hid/drivers/hid-multitouch/bind Disabling and re-enabling the device with xinput does *not* work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 Status in xinput package in Ubuntu: New Bug description: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11
** Description changed: I'm not entirely sure this bug belongs in package xinput, but I'm - following the lead of #1275416, which describes the same symptoms (but - on other hardware, so likely a different underlying problem). + following the lead of + https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which + describes the same symptoms (but on other hardware, so likely a + different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: - Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Device [1025:0930] + Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 Status in xinput package in Ubuntu: New Bug description: I'm not entirely sure this bug belongs in package xinput, but I'm following
[Desktop-packages] [Bug 1796580] [NEW] Touchscreen breaks after suspend on Acer Aspire Switch 11
Public bug reported: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of #1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and resume again, the touch screen no longer works. Kernel and Xorg logs show no indication of any problem, xinput still lists the touchscreen, but it just no longer works. The touchscreen can be made to work again by reloading the hid_multitouch module (that works by unloading and reloading after a resume, or by unloading the module before suspend and reloading it after resume). I tried updating the bios from v1.03 to the latest v1.04 (no changelog available), but that did not change the problem. I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected. In this dmesg log, I've shown a full boot, a suspend (breaking the touchscreen), a module reload (fixing the touchscreen), then a module unload, suspend and module reload, after which the touchscreen also works (I've added annotations to the log to indicate what happens when). The log also shows some USB-related errors after suspend, but that seems to be about the bluetooth adapter (looking at the usb ids), so I think these are unrelated. The touchscreen in question seems to be connected through I2c, according to dmesg: [4.561527] input: SYNA7508:00 06CB:77B2 Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8 [4.561741] input: SYNA7508:00 06CB:77B2 as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9 [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00 I realize that this is not enough information to diagnose and fix the problem, but I'd gladly receive some suggestions on debug strategies to dig into this issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xinput 1.6.2-1build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 19:40:05 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0930] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Acer Aspire SW5-171P ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/7/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Longchamp_S dmi.board.vendor: Acer dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Haswell-Y System dmi.product.name: Aspire SW5-171P dmi.product.version: V1.04 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/bugs/1796580/+attachment/5198396/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1796580 Title: Touchscreen breaks after suspend on Acer Aspire Switch 11 Status in xinput package in Ubuntu: New Bug description: I'm not entirely sure this bug belongs in package xinput, but I'm following the lead of #1275416, which describes the same symptoms (but on other hardware, so likely a different underlying problem). On this notebook, the touchscreen works well out of the box. But as soon as I suspend (by pressing the power button or closing the lid) and
[Desktop-packages] [Bug 910736] Re: Add ignore rule for Arduino to udev blacklist
An ignore should probably be added for Arduino.org devices too (there's
two competing Arduino companies now, don't ask):
ATTRS{idVendor}==2a03, ENV{ID_MM_DEVICE_IGNORE}=1
And, while we are here, perhaps also ignore the Pinoccio Scout (arduino-
like device):
ATTRS{idVendor}==1d50, ATTRS{idProduct}==6051,
ENV{ID_MM_DEVICE_IGNORE}=1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/910736
Title:
Add ignore rule for Arduino to udev blacklist
Status in modemmanager package in Ubuntu:
Fix Released
Bug description:
When connecting an Arduino or any Arduino-based device (like monome)
modemmanager immediately starts exchanging data with the device,
causing problems for software that works with these devices, namely
serialosc and the Arduino IDE.
Blacklisting the affected devices currently seems the best way to
solve the problem, as found by doing a search for simular bugs, e.g.
bug 842702, bug 807889 and bug 490194.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/910736/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 892706] Re: after gdm login, keyboard doesn't send KeyPress events
In case any one else comes across this problem: I had exactly the same symptoms and found out they were caused by xbindkeys that was started in the background. Removing my .xbindkeysrc solved the problem for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/892706 Title: after gdm login, keyboard doesn't send KeyPress events Status in “xserver-xorg-input-evdev” package in Ubuntu: New Bug description: I can type fine at the gdm prompt, and the mouse works after login too. fvwm catches my bound function keys for window manipulation, but regular keypresses into windows don't work. I ran xev and typed into it. Usually each keypress makes 3 events: FocusOut event, serial 23, synthetic NO, window 0xc1, mode NotifyGrab, detail NotifyPointer FocusIn event, serial 23, synthetic NO, window 0xc1, mode NotifyGrab, detail NotifyPointer KeymapNotify event, serial 23, synthetic NO, window 0x0, keys: 2 0 0 0 0 4 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ..and the keyrelease makes 3 more: FocusOut event, serial 23, synthetic NO, window 0xc1, mode NotifyUngrab, detail NotifyPointer FocusIn event, serial 23, synthetic NO, window 0xc1, mode NotifyUngrab, detail NotifyPointer KeymapNotify event, serial 23, synthetic NO, window 0x0, keys: 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 but I noticed that if I press a few keys and overlap the time they're down, I can get occasional correct-looking KeyRelease events with the right keysyms and everything. I haven't found any way to get a KeyPress. Here are some related-looking pages: http://e-mats.org/2009/05/keyboard-not-working-after-booting-ubuntu/ blames dbus and hal for a very similar bug. I have tried restarting dbus but nothing seems to change. https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/59616/comments/18 but running gconftool-2 -s /apps/gnome-settings-daemon/plugins/a11y-keyboard/active -t bool false had no effect This damage happened upon my upgrade from 11.04 to 11.10. One other thing I changed today was that I used to have Module Load xtrap in my xorg.conf but took it out when I got warnings from the new X version. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 19 19:00:32 2011 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to oneiric on 2011-11-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/892706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
