[Ubuntu-x-swat] [Bug 1784099] [NEW] Touchpad very unreliable. Freezes up constantly on use.

[Thomas Holmes]

Public bug reported:

Related to
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1746740

I would like to see this fix shipped in 18.04.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libinput10 1.10.4-1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 28 01:20:18 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:058b]
InstallationDate: Installed on 2018-07-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. XPS L322X
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: libinput
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PJHXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: XPS L322X
dmi.sys.vendor: Dell Inc.
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: libinput (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

-- 
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/1784099

Title:
  Touchpad very unreliable. Freezes up constantly on use.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1784099/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1773015] Re: appli Notes

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

-- 
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/1773015

Title:
  appli Notes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1773015/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783850] Re: Cannot find display configuration

[Tony Pursell]

It seems I spoke too soon.

When I started the machine back up again today using 4.4.0-130, the bug
was back again.

It seems that when I restart, sometimes it will start without the error
message, then it will be back again if I restart again.  Its quite
random.

Another thing I have noticed is that if I get the xorg error message, I
also lose the WiFi.

** Changed in: xorg-server (Ubuntu)
   Status: Fix Released => New

-- 
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/1783850

Title:
  Cannot find display configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1783850/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

[Bug Watch Updater]

Launchpad has imported 15 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=97024.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2016-07-21T15:10:30+00:00 Frdsktp wrote:

I'm using the keyboard layout de-neo (German Neo2). When starting a x11
graphical application in a xwayland session, I see this error message
printed to console or syslog:


The XKEYBOARD keymap compiler (xkbcomp) reports:
> Error:Key  added to map for multiple modifiers
>   Using Lock, ignoring Shift.
Errors from xkbcomp are not fatal to the X server


When starting wayland graphical applications (using Gtk+ 3.20) I get this 
message:


xkbcommon: ERROR: Key "" added to modifier map for multiple modifiers; 
Using Lock, ignoring Shift


When starting a x11 session I get this message:


The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:  Multiple interpretations of "Caps_Lock+AnyOfOrNone(all)"
>   Using last definition for duplicate fields
> Warning:  Multiple interpretations of "Shift_L+AnyOfOrNone(all)"
>   Using last definition for duplicate fields
> Error:Key  added to map for multiple modifiers
>   Using Mod2, ignoring Mod4.
> Error:Key  added to map for multiple modifiers
>   Using Mod3, ignoring Mod5.
Errors from xkbcomp are not fatal to the X server


So it looks like this layout is broken. I have no idea what. Can you please 
give me a hint on the reason why this happens?


Upstream is at https://wiki.neo-layout.org/browser#linux/X/rules, but they 
don't seem to fix these warnings/errors: https://wiki.neo-layout.org/ticket/408

I'm running Fedora 24 with
xkeyboard-config-2.17-2.fc24.noarch
libxkbcommon-0.6.1-1.fc24.x86_64

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/1783987/comments/0


On 2016-07-21T17:27:51+00:00 Ran Benita wrote:

I can help debug the wayland error message.

What desktop environment are you using?

Assuming you are using gnome shell, which layouts did you choose
exactly, and in what order? (You can see in the "Region & Language"
settings).

Did you change any settings in the "Tweak Tool" under "Typing"?

In X11 session, can you show the output of `setxkbmap -print`?

BTW, the keymap usually works fine even with such errors, so it is not
necessarily broken. Does it actually not work for you?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/1783987/comments/1


On 2016-07-21T18:45:39+00:00 Wettstae wrote:

> Warning:  Multiple interpretations of "Caps_Lock+AnyOfOrNone(all)"
>   Using last definition for duplicate fields

> Warning:  Multiple interpretations of "Shift_L+AnyOfOrNone(all)"
>   Using last definition for duplicate fields

The latter comes from "assign_shift_left_action" in compat/misc, see the
comment there why it is required.

I think the proper way to get rid of this warning would be to specify
the action associated to a keysym directly, not involving any "Any"
patters in the compat, that is, instead of

interpret Any+Lock {
action= LockMods(modifiers=Lock);
};

interpret Any + Any {
action= SetMods(modifiers=modMapMods);
};

(in compat/basic), use

interpret Caps_Lock {
action= LockMods(modifiers=Lock);
};

interpret Shift_L {
action= SetMods(modifiers=Shift);
};
interpret Shift_R {
action= SetMods(modifiers=Shift);
};

This might break some xmodmap setups of those very conservative user
still using xmodmap...

> Error:Key  added to map for multiple modifiers
>   Using Mod2, ignoring Mod4.
> Error:Key  added to map for multiple modifiers
>   Using Mod3, ignoring Mod5.

The former comes from "modifier_mapping" in symbols/level5, the latter
from "lock" in the same file, or something similar.  The purpose is
associate the virtual modifiers LevelFive and NumLock to a real
modifier, and this is done using keycodes HYPR and MDSW which are known
not to be produced by hardware.

A proper fix would be not to use virtual modifiers LevelFive and NumLock
(and LevelThree and AltGr) at all, and use real modifiers directly.
This would avoid the need of such hacks as the one in symbols/level5,
without any disadvantage.

However, the error messages state that the the modifiers are set up as
desired.  From the practical perspective, therefore, there is no
pressing need for a change.

Reply at: 

[Ubuntu-x-swat] [Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

[DJ]

The same problem here.
Upgrage from 16 to 18
Dell XPS

-- 
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/1768976

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

[Gunnar Hjalmarsson]

I jumped at conclusions; sorry for that.

I too see the issue you mention. However, I found an upstream bug
report, and one of the ideas mentioned there was to disable NumLock.
Once I had done so, the "German (Neo 2)" layout seemed to behave as
expected.

Can you please make sure that NumLock is turned off when switching to
Neo 2 and let us know if that helps.

** Changed in: xkeyboard-config (Ubuntu)
   Status: Invalid => Incomplete

** Bug watch added: freedesktop.org Bugzilla #97024
   https://bugs.freedesktop.org/show_bug.cgi?id=97024

** Also affects: xkeyboard-config via
   https://bugs.freedesktop.org/show_bug.cgi?id=97024
   Importance: Unknown
   Status: Unknown

-- 
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/1783987

Title:
  German Neo2 Problem with Xubuntu 18.04 (try out mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1783987/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1731261] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...")

[Apport retracing service]

** Tags added: cosmic

-- 
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/1731261

Title:
  Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
  FatalError() from xwl_log_handler(msg="Error sending request: Broken
  pipe\n...")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731261/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1784064] Re: Xwayland crashed with SIGABRT in OsAbort()

[Apport retracing service]

*** This bug is a duplicate of bug 1731261 ***
https://bugs.launchpad.net/bugs/1731261

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 #1731261, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168715/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168718/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168727/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168729/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168730/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168731/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1784064/+attachment/5168732/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1731261
   Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from 
FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...")

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
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/1784064

Title:
  Xwayland crashed with SIGABRT in OsAbort()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1784064/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic

[beta-tester]

my Logitech K400 still does not react to double tap on ubuntu 18.04.1

so ubuntu 18.04.1 still got no update of libinput to version >=1.10.5

-- 
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/1762536

Title:
  double tap on touchpad isn't recognized as double click on ubuntu
  18.04 bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/libinput/+bug/1762536/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

[Krino Hoogestraat]

Thanks Gunnar :-)

I don't think my report was invalid. I've been using Neo 2 for many
years, so I know what it looks like when it works. So here's what
happens in some more detail:

1. I insert a USB Stick with xubuntu-18.04-desktop-amd64.iso into my computer.
2. I start the computer and, by pressing F10, use the USB as my booting device 
(live system).
3. I select Language Deutsch.
4. I select »Ubuntu ausprobieren« (try Ubuntu).
5. In the keyboard menu, I change from »Deutsch qwertz« to »Deutsch Neo 2«.
>From here, the keyboard should respond in the Neo manner, meaning that asdf 
>yields uiae, jklö yields nrtd, etc. At least that's what it does when using 
>16.04.
6. I start Mousepad to test the keyboard layout. So jklö should yield nrtd, but 
in actual fact what I get is ›456,‹. Which is Neo 2 to be sure, however it's 
not Mod1, but Mod4.

-- 
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/1783987

Title:
  German Neo2 Problem with Xubuntu 18.04 (try out mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1783987/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)

[Gunnar Hjalmarsson]

I think Neo 2 is it, but it's a complex keyboard layout. There are some
hints in the file

/usr/share/X11/xkb/symbols/de

If you need help to understand how it's supposed to be used, please use
one of the support resources, e.g. .

There does not seem to be a bug here, so closing.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Invalid

-- 
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/1783987

Title:
  German Neo2 Problem with Xubuntu 18.04 (try out mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1783987/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

[Jim Kyle]

s/metter/better/!!!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2 [error: implicit declaration of function
  ‘init_timer’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]

[Jim Kyle]

I've encountered this bug on the past TWO kernel updates of my Xubuntu
16.04.4 (now .5) system that uses an Nvidia card. Initially I found that
falling back to the previous kernel was a satisfactory workaround. This
morning, I tried using the "Additional drivers" system setting to change
from the Nvidia driver to the noveau driver -- and that has worked
perfectly so far. This might be a possible recommended solution. I had
originally switched from noveau to the proprietary driver because noveau
didn't work properly, but that was several years ago and it has
obviously gotten much metter!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750

Title:
  nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with
  linux 4.15.0-1.2 [error: implicit declaration of function
  ‘init_timer’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Andreas Ntaflos]

Using Kubuntu 16.04 on a Thinkpad X240 with Intel graphics this problem
also causes Yakuake ("Quake-style terminal emulator based on KDE Konsole
technology") to remain invisible when activated. It still accepts input
and the window is in focus, it just is not visible.

Switching the compositor rendering backend from OpenGL to XRender works
around the problem but the XRender backend seems to cause massive screen
tearing when scrolling or watching videos so this workaround is
suboptimal.

Installing xserver-common and xserver-xorg-core from
ppa:canonical-x/testing fixes the issue!

-- 
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/1780664

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780664/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783987] [NEW] German Neo2 Problem with Xubuntu 18.04 (try out mode)

[Krino Hoogestraat]

Public bug reported:

When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered
the Neo2 Keyboard Layout, but it does not work. What I get is apparently
Neo2 Mod4, but not Mod 1, as it should be.

I wonder if Neo2 does work if I install 18.04 properly?

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1783987

Title:
  German Neo2 Problem with Xubuntu 18.04 (try out mode)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1783987/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1782882] Re: Xorg crashed (logged out when suspend or turn off the screen) with signal 7 in do_lookup_x()

[Marc Deslauriers]

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 privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Public Security to Public

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1782882

Title:
  Xorg crashed (logged out when suspend or turn off the screen) with
  signal 7 in do_lookup_x()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1782882/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence

[Daniel van Vugt]

Sounds like a kernel regression so reassigning there.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

-- 
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/1783957

Title:
  Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
  login screen in a normal sequence

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783954] Re: [NVIDIA] GPU lockup (screen freeze) after resume from hibernation / suspend

[YS1]

typo

** Package changed: grub2 (Ubuntu) => xorg (Ubuntu)

-- 
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/1783954

Title:
  [NVIDIA] GPU lockup (screen freeze) after resume from hibernation /
  suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1783954/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783954] Re: [NVIDIA] GPU lockup (screen freeze) after resume from hibernation / suspend

[Daniel van Vugt]

It appears you're using NVIDIA 396.45, which isn't supported. Did you
find the same bug with the official driver 390.48?

To install that you would need to remove the PPA and then:  sudo apt
install nvidia-driver-390

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Tags added: nvidia

-- 
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/1783954

Title:
  [NVIDIA] GPU lockup (screen freeze) after resume from hibernation /
  suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1783954/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783957] [NEW] Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence

[Anquietas]

Public bug reported:

I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS)
with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and
natural install, no funky custom kernel or drivers or anything...

Everything worked fine (with the 4.13.* kernel) until I've upgraded all
my packages (which included the "wonderful" 4.15.0-29 kernel, which
broke my system).

Now, everytime I try to boot normally, it asks me for my disk password (I have 
an encrypted LVM) and after that, guess what ?: blank screen. The login screen 
does not appear.
I can switch the Terminals with Ctrl+Alt+Fx, however.

However, the same kernel, if I boot it in recovery mode and then I
select "Resume", the login screen appears, but it lags a little bit...

Needless to say, if I boot the older kernel (4.13), everything works
perfectly.

I dug up some logs and found something like "sddm-greeter" segmentation
fault in nouveau_dri.so or something like this.

So, it looks like the new kernel doesn't quite seem to look eye-to-eye
with nouveau drivers...

And no, I don't want the NVidia proprietary drivers because I get along
just perfectly with Nouveau on other machines, and I don't want to
reinstall nvidia drivers everytime I'm upgrading the kernel.

And yes, I already have "haveged" installed, to provide sufficient
entropy (I saw that the possible lack of entropy might be a problem in
some cases)...

If I boot in recovery mode and then select "resume", everything works.

So, what is going on ?

Any help would be appreciated...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Jul 27 10:40:31 2018
InstallationDate: Installed on 2018-07-04 (22 days ago)
InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
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/1783957

Title:
  Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no
  login screen in a normal sequence

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1783957/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-x-swat] [Bug 1783954] [NEW] [NVIDIA] GPU lockup (screen freeze) after resume from hibernation / suspend

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

 This bug is reported against xorg as per
. It is also reported
to NVIDIA under
.

I have been experiencing GPU lockups after resuming from hibernation on
KUbuntu 18.04.

When this happens, the display freezes except for the mouse cursor. It
is possible to ssh into the computer but killing X does not update the
display either.

These lockups seem to happen at a random time after hibernation. Sometimes the 
computer works correctly for hours after resuming, sometimes the lockup happen 
a few seconds after resuming. Actions that are prone to trigger the lockup are :
 - hovering over some task in KDE/Plasma panel and causing the miniature of the 
application window to be displayed (when a lockup happens, it is often when I 
do this, but doing this does not systematically incur a lockup) ;
 - with Spectacle (screenshot utility), start selecting a rectangular region 
(this has systematically caused a lockup when tried after resuming from 
hibernation/suspend).

Following  I tried
with the latest graphics drivers from the graphics-drivers PPA, the
latest version of Xorg in the xorg-edgers PPA and the latest available
kernel (4.17.0-996-generic).

Attached are some logs, including a partial log produced by nvidia-bug-report. 
Indeed, the script could not complete. Inspection of the running processes with 
a second ssh connection while the script was hanging up shows that the blocking 
point is [code]cat /proc/driver/nvidia/./gpus/:01:00.0/information[/code]. 
Indeed, trying to manually read that file in the ssh console also caused it to 
hang. Of course doing this in normal operation works and gives
[code]Model:   Quadro K620
IRQ: 127
GPU UUID:GPU-ea026ffc-2c0d-1301-c365-b1cceeb45601
Video BIOS:  82.07.7a.00.1a
Bus Type:PCIe
DMA Size:40 bits
DMA Mask:0xff
Bus Location::01:00.0
Device Minor:0[/code]

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New

-- 
[NVIDIA] GPU lockup (screen freeze) after resume from hibernation / suspend
https://bugs.launchpad.net/bugs/1783954
You received this bug notification because you are a member of Ubuntu-X, which 
is subscribed to xorg in Ubuntu.

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp