[Bug 1957948] Re: 2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish function `fish_add_path` which requires fish 3.2 or later (Impish only packages fish 3.1)

2022-02-14 Thread Martin Vysny
This bug seems to also be causing
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960702

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1957948

Title:
  2.54.2+21.10 introduces a call in vendor_conf.d/snapd.fish to fish
  function `fish_add_path` which requires fish 3.2 or later (Impish only
  packages fish 3.1)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960702] Re: all snap apps gone after snap upgrade

2022-02-14 Thread Martin Vysny
Since using bash instead of fish fixes the issue, I think the problem
lies in the snapd+fish integration. Possible workarounds:

1. Revert to bash via chsh as stated above
2. Upgrade fish to 3.2.0 which contains the fish_add_path
3. Wait for newer snapd (which reportedly contains a compatibility fix to 
continue working with fish 3.1)

Also see https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1957948

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960702

Title:
  all snap apps gone after snap upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960702] Re: all snap apps gone after snap upgrade

2022-02-14 Thread Martin Vysny
Reverting back to bash and rebooting helped:

$ chsh -s /usr/bin/bash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960702

Title:
  all snap apps gone after snap upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960702] Re: all snap apps gone after snap upgrade

2022-02-14 Thread Martin Vysny
Tried to fix fish as suggested at
https://askubuntu.com/questions/1392178/where-should-i-find-the-fish-
add-path-command (by commenting out the line number 3 of
/usr/share/fish/vendor_conf.d/snapd.fish) indeed hides the fish error
but doesn't seem to help with the "missing apps" problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960702

Title:
  all snap apps gone after snap upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960702] Re: all snap apps gone after snap upgrade

2022-02-12 Thread Martin Vysny
The same thing happened just now on my other laptop after upgrading to
newest snapd, so this bug is not related to just one machine only.

This is critical - not for me since I can launch those apps from
terminal, but for less experienced users, since they will perceive this
as apps disappearing for no apparent reason.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960702

Title:
  all snap apps gone after snap upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1960702] Re: all snap apps gone after snap upgrade

2022-02-12 Thread Martin Vysny
** Attachment added: "missing icon"
   
https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1960702/+attachment/5560514/+files/Screenshot%20from%202022-02-12%2015-44-37.png

** Description changed:

  After snap has been upgraded yesterday to 2.54.2+21.10ubuntu1, all hell
  broke loose. All snap-installed apps are gone from gnome - snap firefox
  cannot be selected as the default browser, gnome says there's no app to
  handle https:// links when trying to report bugs via ubuntu-bug, firefox
  launch icon is missing from the dock launcher, even fish prints some
  kind of error to the console:
  
  ```
- /usr/share/fish/vendor_conf.d/snapd.fish (line 3): 
+ /usr/share/fish/vendor_conf.d/snapd.fish (line 3):
  fish_add_path -aP $snap_bin_path
  ^
  from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish
-   called on line 294 of file /usr/share/fish/config.fish
+  called on line 294 of file /usr/share/fish/config.fish
  from sourcing file /usr/share/fish/config.fish
-   called during startup
+  called during startup
  ```
  
  Firefox has no icon and is showing as the "grey cog wheel" icon, see
- screenshot for details.
- 
+ screenshot for details. Luckily, firefox and all snap apps can be
+ started from the terminal.
  
  > dpkg -s snapd
  Package: snapd
  Status: install ok installed
  Priority: optional
  Section: devel
  Installed-Size: 93766
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Version: 2.54.2+21.10ubuntu1
  Replaces: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), 
ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 
1.9)
  Depends: adduser, apparmor (>= 2.10.95-0ubuntu2.2), ca-certificates, 
openssh-client, squashfs-tools, systemd, udev, libc6 (>= 2.34), libfuse2 (>= 
2.6), liblzma5 (>= 5.1.1alpha+20110809), liblzo2-2 (>= 2.02), libudev1 (>= 
183), zlib1g (>= 1:1.1.4), default-dbus-session-bus | dbus-session-bus
  Recommends: gnupg
  Suggests: zenity | kdialog
  Breaks: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), 
ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 
1.9)
  Conflicts: snap (<< 2013-11-29-1ubuntu1)
  Conffiles:
-  /etc/apparmor.d/usr.lib.snapd.snap-confine.real 
b9b25a499a2aa93118180bfd799ff48a
-  /etc/apt/apt.conf.d/20snapd.conf e0e08d8267c66b9f81340dd6500cb67a
-  /etc/profile.d/apps-bin-path.sh cf10aed8bb987ded8b7f4ba4303c1e9b
-  /etc/xdg/autostart/snap-userd-autostart.desktop 
42fe36462a072a72e09cad553362
+  /etc/apparmor.d/usr.lib.snapd.snap-confine.real 
b9b25a499a2aa93118180bfd799ff48a
+  /etc/apt/apt.conf.d/20snapd.conf e0e08d8267c66b9f81340dd6500cb67a
+  /etc/profile.d/apps-bin-path.sh cf10aed8bb987ded8b7f4ba4303c1e9b
+  /etc/xdg/autostart/snap-userd-autostart.desktop 
42fe36462a072a72e09cad553362
  Description: Daemon and tooling that enable snap packages
-  Install, configure, refresh and remove snap packages. Snaps are
-  'universal' packages that work across many different Linux systems,
-  enabling secure distribution of the latest apps and utilities for
-  cloud, servers, desktops and the internet of things.
-  .
-  Start with 'snap list' to see installed snaps.
+  Install, configure, refresh and remove snap packages. Snaps are
+  'universal' packages that work across many different Linux systems,
+  enabling secure distribution of the latest apps and utilities for
+  cloud, servers, desktops and the internet of things.
+  .
+  Start with 'snap list' to see installed snaps.
  Built-Using: apparmor (= 3.0.3-0ubuntu1), libcap2 (= 1:2.44-1build1), 
libseccomp (= 2.5.1-1ubuntu1)
  Homepage: https://github.com/snapcore/snapd
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snap (not installed)
  ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
  Uname: Linux 5.13.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 12 15:39:43 2022
  InstallationDate: Installed on 2021-03-24 (324 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: snap
  UpgradeStatus: Upgraded to impish on 2021-10-13 (121 days ago)

** Description changed:

  After snap has been upgraded yesterday to 2.54.2+21.10ubuntu1, all hell
  broke loose. All snap-installed apps are gone from gnome - snap firefox
  cannot be selected as the default browser, gnome says there's no app to
  handle https:// links when trying to report bugs via ubuntu-bug, firefox
  launch icon is missing from the dock launcher, even fish prints some
  kind of error to the console:
  
  ```
  /usr/share/fish/vendor_conf.d/snapd.fish (line 3):
  fish_add_path -aP $snap_bin_path
  ^
  from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish
   called on line 294 of file /usr/share/fish/config.fish
  from sourcing file /usr/share/fish/config.fish
   called during startup
  ```
  
  Firefox has no icon and is showing as the "grey cog wheel" icon, see
  screenshot for 

[Bug 1960702] [NEW] all snap apps gone after snap upgrade

2022-02-12 Thread Martin Vysny
Public bug reported:

After snap has been upgraded yesterday to 2.54.2+21.10ubuntu1, all hell
broke loose. All snap-installed apps are gone from gnome - snap firefox
cannot be selected as the default browser, gnome says there's no app to
handle https:// links when trying to report bugs via ubuntu-bug, firefox
launch icon is missing from the dock launcher, even fish prints some
kind of error to the console:

```
/usr/share/fish/vendor_conf.d/snapd.fish (line 3):
fish_add_path -aP $snap_bin_path
^
from sourcing file /usr/share/fish/vendor_conf.d/snapd.fish
 called on line 294 of file /usr/share/fish/config.fish
from sourcing file /usr/share/fish/config.fish
 called during startup
```

Firefox has no icon and is showing as the "grey cog wheel" icon, see
screenshot for details. Luckily, firefox and all snap apps can be
started from the terminal.

snap chromium is not present in Gnome Applications list, but when
started from the terminal the icon in dock is correct for some reason.

None of the snap apps (firefox, chrome, intellij) can be "pinned" in
Ubuntu Dock.

> dpkg -s snapd
Package: snapd
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 93766
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 2.54.2+21.10ubuntu1
Replaces: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), 
ubuntu-core-launcher (<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 
1.9)
Depends: adduser, apparmor (>= 2.10.95-0ubuntu2.2), ca-certificates, 
openssh-client, squashfs-tools, systemd, udev, libc6 (>= 2.34), libfuse2 (>= 
2.6), liblzma5 (>= 5.1.1alpha+20110809), liblzo2-2 (>= 2.02), libudev1 (>= 
183), zlib1g (>= 1:1.1.4), default-dbus-session-bus | dbus-session-bus
Recommends: gnupg
Suggests: zenity | kdialog
Breaks: snap-confine (<< 2.23), snapd-xdg-open (<= 0.0.0), ubuntu-core-launcher 
(<< 2.22), ubuntu-snappy (<< 1.9), ubuntu-snappy-cli (<< 1.9)
Conflicts: snap (<< 2013-11-29-1ubuntu1)
Conffiles:
 /etc/apparmor.d/usr.lib.snapd.snap-confine.real 
b9b25a499a2aa93118180bfd799ff48a
 /etc/apt/apt.conf.d/20snapd.conf e0e08d8267c66b9f81340dd6500cb67a
 /etc/profile.d/apps-bin-path.sh cf10aed8bb987ded8b7f4ba4303c1e9b
 /etc/xdg/autostart/snap-userd-autostart.desktop 
42fe36462a072a72e09cad553362
Description: Daemon and tooling that enable snap packages
 Install, configure, refresh and remove snap packages. Snaps are
 'universal' packages that work across many different Linux systems,
 enabling secure distribution of the latest apps and utilities for
 cloud, servers, desktops and the internet of things.
 .
 Start with 'snap list' to see installed snaps.
Built-Using: apparmor (= 3.0.3-0ubuntu1), libcap2 (= 1:2.44-1build1), 
libseccomp (= 2.5.1-1ubuntu1)
Homepage: https://github.com/snapcore/snapd

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: snap (not installed)
ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 12 15:39:43 2022
InstallationDate: Installed on 2021-03-24 (324 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
SourcePackage: snap
UpgradeStatus: Upgraded to impish on 2021-10-13 (121 days ago)

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


** Tags: amd64 apport-bug impish wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960702

Title:
  all snap apps gone after snap upgrade

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1729016] Re: Drop hard dependency on lynx | www-browser

2022-01-14 Thread Martin Vysny
Hi, I'm on Ubuntu 21.10 and dpkg says that the "fish" package depends on
lynx or www-browser:


$ dpkg -s fish
Package: fish
Status: install ok installed
Priority: optional
Section: shells
Installed-Size: 5300
Maintainer: Ubuntu Developers 
Architecture: amd64
Version: 3.1.2-3ubuntu1
Depends: bc, fish-common (= 3.1.2-3ubuntu1), lynx | www-browser, man-db, 
python3, python3-distutils, libc6 (>= 2.32), libpcre2-32-0 (>= 10.22), 
libstdc++6 (>= 5.2), libtinfo6 (>= 6)
Pre-Depends: dpkg (>= 1.17.14)
...

Perhaps the web-based configuration could be removed from the fish
package?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729016

Title:
  Drop hard dependency on lynx | www-browser

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938683] Re: Thunderbird still running after being closed

2021-08-02 Thread Martin Vysny
** Attachment added: "Screenshot from 2021-08-02 15-19-19.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1938683/+attachment/5515270/+files/Screenshot%20from%202021-08-02%2015-19-19.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938683

Title:
  Thunderbird still running after being closed

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938683] Re: Thunderbird still running after being closed

2021-08-02 Thread Martin Vysny
I was able to reproduce the issue - please see the screenshot for more
details. Unfortunately I don't have concrete steps to reproduce - I was
simply writing a long e-mail and after I sent it, I realized the
thunderbird/dash issue reproduced.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938683

Title:
  Thunderbird still running after being closed

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938683] Re: Thunderbird still running after being closed

2021-08-02 Thread Martin Vysny
Thank you for getting back to me. I'm convinced that Thunderbird is
actually not running, since `killall thunderbird` said that there's no
such process, and `ps -ef|grep -i thunderbird` has shown no thunderbird
process running.

However, after a reboot, I am not able to reproduce this issue easily.
I'll try to find a more solid steps to reproduce, then I'll post more
information.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938683

Title:
  Thunderbird still running after being closed

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938683] Re: dash number-of-windows indicator not cleared for thunderbird

2021-08-02 Thread Martin Vysny
** Attachment added: "Screenshot from 2021-08-02 11-46-16.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938683/+attachment/5515238/+files/Screenshot%20from%202021-08-02%2011-46-16.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938683

Title:
  dash number-of-windows indicator not cleared for thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938683/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1938683] [NEW] dash number-of-windows indicator not cleared for thunderbird

2021-08-02 Thread Martin Vysny
Public bug reported:

The "number of windows" indicator in the Ubuntu Dash (the orange dots to
the left of the app icon) is not cleared for Thunderbird, when a new
e-mail is written in a new window. Ultimately, the indicators stay
visible even after Thunderbird is closed completely, and it's no longer
possible to launch thunderbird by left-clicking of the dash icon
(middle-click works okay).

Steps to reproduce:
1. Launch Thunderbird. There is one orange dot to the left of the thunderbird 
icon.
2. Write an e-mail and close the e-mail window
3. Observe that there are now two orange dots to the left of the thunderbird 
icon.

Please see the screenshot for more details.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu3~21.04.1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug  2 11:41:47 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-03-24 (130 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to hirsute on 2021-04-23 (101 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938683

Title:
  dash number-of-windows indicator not cleared for thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938683/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-05-18 Thread Martin Vysny
I confirm that the situation improved a lot, I'm not getting the error
anymore.

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-05-17 Thread Martin Vysny
I've successfully upgraded to 5.11.0-18-generic and removed all
usbcore.quirks kernel parameters; so far everything is working. I'll
test more and I'll update the tags tomorrow appropriately.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-05-02 Thread Martin Vysny
It did not help, I'm still getting

[  299.648322] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  300.672037] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  301.695990] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

on kernel 5.11.0-16-generic. As if the USB_QUIRK_NO_LPM quirk is no
longer taken into effect... Or maybe there was an update to the docking
station's firmware (via the Lenovo Windows app) and that's when the
problem reappeared? Or was it that the problem reappeared because of
kernel v bump? Hard to say.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-05-01 Thread Martin Vysny
> So, the k option, while improving the situation, doesn't seem to solve
it fully.

Or maybe the new kernel enabled link power management for the "Lenovo
USB3.1 Hub" devices?

The devices in question (excerpt from `lsusb`):

Bus 005 Device 003: ID 17ef:a393 Lenovo USB3.1 Hub
Bus 005 Device 004: ID 17ef:a387 Lenovo USB-C Dock Ethernet
Bus 005 Device 002: ID 17ef:a391 Lenovo USB3.1 Hub

I've therefore started using
usbcore.quirks=17ef:a387:k,17ef:a393:k,17ef:a391:k , I'll test and post
more.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-28 Thread Martin Vysny
Maybe the Lenovo USB3.1 Hub device would benefit from having the 'k'
parameter? I'll try.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-28 Thread Martin Vysny
Hold on please, it looks like the bug is back - upon a boot I'm randomly
getting

[  271.935097] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  272.959356] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  273.983324] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

even though I have the kernel parameter usbcore.quirks=17ef:a387:k . Now
I'm running Ubuntu 21.04 using kernel 5.11.0-16-generic. lsusb now
identifies the device correctly:

Bus 005 Device 003: ID 17ef:a387 Lenovo USB-C Dock Ethernet

So, the k option, while improving the situation, doesn't seem to solve
it fully.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849478] Re: [snap] (experimental) pipewire support not available

2021-04-22 Thread Martin Vysny
[continuing]

This is bad, since Ubuntu 21.04 switches from Xorg to Wayland by default
which effectively disables screen sharing on Chromium. User needs to go
back to Xorg to enable screen sharing on Chromium, which is a bit of a
pity since pipewire is already in place and ready to be used.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849478

Title:
  [snap] (experimental) pipewire support not available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1849478] Re: [snap] (experimental) pipewire support not available

2021-04-22 Thread Martin Vysny
Starting from Ubuntu 21.04 the pipewire libs are bundled in Ubuntu
itself, to allow screen sharing over webrtc. This allows Firefox to cast
screen properly, which is great :)

However, since the Chromium snap is missing the pipewire support
(currently 90.0.4430.85), it's not possible to set the flag
chrome://flags/#enable-webrtc-pipewire-capturer to true, which
effectively disables screen sharing on Chromium.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849478

Title:
  [snap] (experimental) pipewire support not available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-12 Thread Martin Vysny
Oh, I misunderstood you then. Awesome work with the patch, it would be
great to have that directly in the kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-12 Thread Martin Vysny
I placed the parameter into /etc/default/grub as follows:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.quirks=17ef:a387:k"

I'm not sure how to create a patch from that.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-07 Thread Martin Vysny
The "usbcore.quirks=17ef:a387:k" kernel parameter workaround seems to be
working excellent so far!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-07 Thread Martin Vysny
Indeed: the PCI device is controlled by a different kernel driver
(r8169) as shown via lspci -k:

02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0e)
Subsystem: Lenovo RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
Kernel driver in use: r8169
Kernel modules: r8169


Therefore, we can safely ignore this PCI device and focus on the USB device 
17ef:a387 controlled by the r8152 driver.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-07 Thread Martin Vysny
Okay the network seems to be working so far, this is encouraging, I'll
observe and let you know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-07 Thread Martin Vysny
I've seen comments regarding using usbcore.quirks; I'll try
usbcore.quirks=17ef:a387:k in order to disable the link power
management.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-07 Thread Martin Vysny
BUT the Network Manager says "USB Ethernet" for the docking station
ethernet port, so perhaps the PCI device refers to the ethernet "dongle"
which can be attached to the computer? Yes: Network Manager says "PCI
Ethernet Connected" when I plug the cable into the dongle.

Found it:

~> lsusb -t|grep r8
|__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=r8152, 
5000M


It's this guy (even though lsusb says "USB3.1 Hub"):
Bus 005 Device 003: ID 17ef:a387 Lenovo USB3.1 Hub

Indeed this page confirms this finding: https://linux-
hardware.org/index.php?id=usb:17ef-a387 : Lenovo USB-C Dock Ethernet

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-07 Thread Martin Vysny
Interestingly, the card does not seem to act as an USB device, but
rather as a PCI device. That's weird, since the card is located on a
docking station which is connected to the computer via USB. I guess this
is because Thunderbolt-over-USB or similar?

~> lspci|grep -i eth
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 0e)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-06 Thread Martin Vysny
I need to correct myself: the card stopped working out of the blue and
started to print Tx status -71 to dmesg. So the statement "network works
perfectly while the computer is turned on" is not true.

Excerpt from the dmesg:

[11284.014421] audit: type=1400 audit(1617704946.490:148): apparmor="DENIED" 
operation="capable" profile="/snap/snapd/11588/usr/lib/snapd/snap-confine" 
pid=24752 comm="snap-confine" capability=4  capname="fsetid"
[11292.590915] audit: type=1400 audit(1617704955.062:149): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c510:0" 
pid=24752 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[11292.590920] audit: type=1400 audit(1617704955.062:150): apparmor="DENIED" 
operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c510:1" 
pid=24752 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=0
[11328.103406] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.111513] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.119627] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.127759] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.135889] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.144009] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.152141] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.160250] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.168395] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11328.176506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11333.085154] retire_capture_urb: 2492 callbacks suppressed
[11333.110654] net_ratelimit: 596 callbacks suppressed
[11333.110660] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11333.118785] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[11333.126913] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-06 Thread Martin Vysny
Finally, powering the notebook off (which seemingly also powered the
docking station off) then on after a couple of seconds seem to be
working as a workaround - the network works perfectly while the computer
is turned on.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] [NEW] r8152 tx status -71

2021-04-06 Thread Martin Vysny
Public bug reported:

I've bought ThinkPad T14s with a USB-based docking station. Everything
is working marvelously, but from time to time the ethernet port on the
docking station won't connect. I've discovered the following messages in
my dmesg:

[  400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[  594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

Rebooting the machine doesn't seem to work, turning the ethernet
connection off and on doesn't seem to work. I have a dualboot
Linux+Windows (one wants to play games from time to time :-p ) and it
could be that rebooting from Win to Lin causes this issue, but this
needs to be confirmed yet. I will try to power off the computer and/or
the docking station, to see whether that would help.

I've found numerous bug reports, but they are rather old or may not
apply to this situation, therefore I figured it's best to open a new bug
report.

Thank you so much for your hard work!

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-48-generic 5.8.0-48.54
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  6 10:00:29 2021
InstallationDate: Installed on 2021-03-24 (12 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: LENOVO 20UH001QMX
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic 
root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-48-generic N/A
 linux-backports-modules-5.8.0-48-generic  N/A
 linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET61W(1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001QMX
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.30
dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001QMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922651] Re: r8152 tx status -71

2021-04-06 Thread Martin Vysny
Trying rmmod r8169 && modprobe r8169 doesn't seem to work:


[ 1273.946335] r8169 :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[ 1273.964669] libphy: r8169: probed
[ 1273.965172] r8169 :02:00.0 eth0: RTL8168ep/8111ep, 8c:8c:aa:1d:93:ca, 
XID 502, IRQ 48
[ 1273.965178] r8169 :02:00.0 eth0: jumbo features [frames: 9194 bytes, tx 
checksumming: ko]
[ 1273.970331] r8169 :02:00.0 enp2s0f0: renamed from eth0
[ 1274.041619] Generic FE-GE Realtek PHY r8169-200:00: attached PHY driver 
[Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
[ 1274.157641] r8169 :02:00.0 enp2s0f0: Link is Down
[ 1304.326079] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1322.474202] wlp3s0: deauthenticating from b0:95:75:04:6f:ea by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 1337.865675] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1338.837702] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1339.896810] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1339.905573] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1340.469696] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1340.566179] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1341.494091] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1341.505622] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1341.803331] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1341.817618] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1342.998669] net_ratelimit: 5 callbacks suppressed
[ 1342.998713] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1343.979560] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1344.064021] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71
[ 1344.635990] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922651

Title:
  r8152 tx status -71

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912158] Re: undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1

2021-01-18 Thread Martin Vysny
Certainly, thank you :)


~> apt policy openjdk-11-jre openjdk-11-jre-dcevm
openjdk-11-jre:
  Installed: 11.0.9.1+1-0ubuntu1~20.10
  Candidate: 11.0.9.1+1-0ubuntu1~20.10
  Version table:
 *** 11.0.9.1+1-0ubuntu1~20.10 500
500 http://ftp.acc.umu.se/ubuntu groovy-updates/main amd64 Packages
500 http://ftp.acc.umu.se/ubuntu groovy-security/main amd64 Packages
100 /var/lib/dpkg/status
 11.0.9+10-0ubuntu1 500
500 http://ftp.acc.umu.se/ubuntu groovy/main amd64 Packages
openjdk-11-jre-dcevm:
  Installed: 11.0.7+1-1
  Candidate: 11.0.7+1-1
  Version table:
 *** 11.0.7+1-1 500
500 http://ftp.acc.umu.se/ubuntu groovy/universe amd64 Packages
100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912158

Title:
  undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-dcevm/+bug/1912158/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1912158] [NEW] undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1

2021-01-17 Thread Martin Vysny
Public bug reported:

Installing openjdk-11-jre-dcevm/groovy,now 11.0.7+1-1 amd64 makes java
fail to start:

~> java -dcevm
Error occurred during initialization of VM
Unable to load native library: 
/usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: undefined symbol: 
JVM_IsUseContainerSupport, version SUNWprivate_1.1

I can see the bug report
https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-
dcevm/+bug/1890482 however it applies to a different dcevm version,
therefore I thought to open a new bug report - hopefully that was the
correct thing to do.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: openjdk-11-jre-dcevm 11.0.7+1-1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 18 08:58:27 2021
InstallationDate: Installed on 2016-09-05 (1595 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: openjdk-11-jre-dcevm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openjdk-11-jre-dcevm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912158

Title:
  undefined symbol: JVM_IsUseContainerSupport, version SUNWprivate_1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-dcevm/+bug/1912158/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890482] Re: Unable to load native library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: undefined symbol: JVM_InitializeFromArchive, version SUNWprivate_1.1

2020-12-14 Thread Martin Vysny
Unfortunately, the issue persists even with openjdk-11-jre-
dcevm:11.0.7+1-1:

$ dpkg -s openjdk-11-jre-dcevm
Package: openjdk-11-jre-dcevm
Status: install ok installed
Priority: optional
Section: java
Installed-Size: 17989
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: same
Version: 11.0.7+1-1


$ java -dcevm
Error occurred during initialization of VM
Unable to load native library: 
/usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: undefined symbol: 
JVM_IsUseContainerSupport, version SUNWprivate_1.1

I have openjdk-11-jre:11.0.9.1+1-0ubuntu1~20.10

Should I open a new bug report, or reopen the current one please?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890482

Title:
  Unable to load native library: /usr/lib/jvm/java-11-openjdk-
  amd64/lib/libjava.so: undefined symbol: JVM_InitializeFromArchive,
  version SUNWprivate_1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-dcevm/+bug/1890482/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1848277] Re: Won't start, get "cannot open display: :0" message

2020-10-02 Thread Martin Vysny
Also does not work for me on Ubuntu 20.10 when running on Xorg.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848277

Title:
  Won't start, get "cannot open display: :0" message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1848277/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897690] [NEW] ping: socket: Address family not supported by protocol

2020-09-29 Thread Martin Vysny
Public bug reported:

The ping utility prints this curious error/warning message:

```
ping: socket: Address family not supported by protocol
```

Otherwise seems to be working just fine:

```
> ping 127.0.0.1
ping: socket: Address family not supported by protocol
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.048 ms
64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.050 ms
64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.043 ms
64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.046 ms
```

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: iputils-ping 3:20200821-2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 10:42:17 2020
InstallationDate: Installed on 2016-09-05 (1484 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897690

Title:
  ping: socket: Address family not supported by protocol

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897224] [NEW] chromium wayland won't start: Unable to open X display

2020-09-25 Thread Martin Vysny
Public bug reported:

I'm trying to run chromium installed via snap in Ubuntu 20.10 when
running Ubuntu Wayland session. Unfortunately, chromium wouldn't start:

> chromium 
[49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to 
open X display.

I am able to run Firefox just fine (assuming that Firefox still runs on
xwayland) and also Intellij snap works fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 25 09:45:16 2020
InstallationDate: Installed on 2016-09-05 (1480 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Snap: chromium 85.0.4183.121 (latest/stable)
SnapSource: ubuntu/+source/chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy snap wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897224

Title:
  chromium wayland won't start: Unable to open X display

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897224/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1895631] Re: systemd at 100% handling apport failures

2020-09-21 Thread Martin Vysny
This started to happen to me as well after experiencing a hard kernel
crash described at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896446

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895631

Title:
  systemd at 100% handling apport failures

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896453] [NEW] systemd at apport failures

2020-09-21 Thread Martin Vysny
Public bug reported:

After experiencing
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896446 systemd
suddenly started to eat 100% of CPU, logging lots of


```
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Start 
request repeated too quickly.
syys 21 11:45:58 mavi-vaadin systemd[1]: apport-autoreport.service: Failed with 
result 'start-limit-hit'.
syys 21 11:45:58 mavi-vaadin systemd[1]: Failed to start Process error reports 
when automatic reporting is enabled.

```

It looks like a duplicite of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895631, however
I was unable to persuade launchpad to add additional info to that very
bug, therefore I've opened a new one :)

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu45
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 21 11:49:06 2020
InstallationDate: Installed on 2016-09-05 (1476 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896453

Title:
  systemd at apport 

[Bug 1896446] Re: Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker hard-freezes the computer

2020-09-21 Thread Martin Vysny
Changed the status of the bug to 'Confirmed' as asked by the apport
program.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] Lsusb-t.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412874/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] ProcCpuinfoMinimal.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412877/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] ProcModules.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412880/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] Lsusb-v.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412875/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] ProcInterrupts.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412879/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] acpidump.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412885/+files/acpidump.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] CurrentDmesg.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412869/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] PulseList.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412881/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] IwConfig.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412870/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] ProcEnviron.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412878/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] RfKill.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1896446/+attachment/5412882/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] UdevDb.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1896446/+attachment/5412883/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] Lsusb.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1896446/+attachment/5412873/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] WifiSyslog.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412884/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] Lspci-vt.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412872/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] Re: Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker hard-freezes the computer

2020-09-21 Thread Martin Vysny
apport information

** Tags added: apport-collected

** Description changed:

  Running the following docker image on Ubuntu 20.10/kernel 5.8 will hard-
  freeze the computer:
  
  docker run --rm -ti -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=myPASSWD123" -p
  1433:1433 --name sqlserver mcr.microsoft.com/mssql/server:2017-latest-
  ubuntu
  
  I am unable to Alt+Sysrq+SUB to reboot the machine - the machine doesn't
  respond. I'm unable to see the crash since I'm in gnome-shell and
  everything just stops - music, mouse, keyboard, everything. The
  /var/log/kern.log doesn't seem to contain any information regarding the
  freeze/panic/crash.
  
  The bug seems to be 100% reproducible: 2 out of 2 times I tried, the
  machine froze reproducibly.
  
  When running on Ubuntu 20.04/kernel 5.4.x the image worked just fine.
  
  Thank you :)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-generic 5.8.0.18.22
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mavi   2344 F pulseaudio
   /dev/snd/pcmC2D0p:   mavi   2344 F...m pulseaudio
   /dev/snd/controlC0:  mavi   2344 F pulseaudio
   /dev/snd/controlC1:  mavi   2344 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep 21 11:14:52 2020
  HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
  InstallationDate: Installed on 2016-09-05 (1476 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN0005MS
  ProcFB:
   0 i915drmfb
   1 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2020
  dmi.bios.release: 1.62
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET89W (1.62 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN0005MS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET89W(1.62):bd06/18/2020:br1.62:efr1.18:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN0005MS
  dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu45
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  mavi   2380 F pulseaudio
+  /dev/snd/pcmC2D0p:   mavi   2380 F...m pulseaudio
+  /dev/snd/controlC0:  mavi   2380 F pulseaudio
+  /dev/snd/controlC1:  mavi   2380 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.10
+ HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
+ InstallationDate: Installed on 2016-09-05 (1476 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ MachineType: LENOVO 20EN0005MS
+ Package: linux (not installed)
+ ProcFB:
+  0 i915drmfb
+  1 nouveaudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
+ RelatedPackageVersions:
+  linux-restricted-modules-5.8.0-18-generic N/A
+  linux-backports-modules-5.8.0-18-generic  N/A
+  linux-firmware1.190
+ Tags:  wayland-session groovy
+ Uname: Linux 5.8.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 06/18/2020
+ dmi.bios.release: 1.62
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N1EET89W (1.62 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20EN0005MS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40705 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.18
+ dmi.modalias: 

[Bug 1896446] ProcCpuinfo.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1896446/+attachment/5412876/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] CRDA.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1896446/+attachment/5412868/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] Lspci.txt

2020-09-21 Thread Martin Vysny
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1896446/+attachment/5412871/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896446] [NEW] Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker hard-freezes the computer

2020-09-21 Thread Martin Vysny
Public bug reported:

Running the following docker image on Ubuntu 20.10/kernel 5.8 will hard-
freeze the computer:

docker run --rm -ti -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=myPASSWD123" -p
1433:1433 --name sqlserver mcr.microsoft.com/mssql/server:2017-latest-
ubuntu

I am unable to Alt+Sysrq+SUB to reboot the machine - the machine doesn't
respond. I'm unable to see the crash since I'm in gnome-shell and
everything just stops - music, mouse, keyboard, everything. The
/var/log/kern.log doesn't seem to contain any information regarding the
freeze/panic/crash.

The bug seems to be 100% reproducible: 2 out of 2 times I tried, the
machine froze reproducibly.

When running on Ubuntu 20.04/kernel 5.4.x the image worked just fine.

Thank you :)

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-generic 5.8.0.18.22
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  mavi   2344 F pulseaudio
 /dev/snd/pcmC2D0p:   mavi   2344 F...m pulseaudio
 /dev/snd/controlC0:  mavi   2344 F pulseaudio
 /dev/snd/controlC1:  mavi   2344 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Mon Sep 21 11:14:52 2020
HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
InstallationDate: Installed on 2016-09-05 (1476 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
MachineType: LENOVO 20EN0005MS
ProcFB:
 0 i915drmfb
 1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-18-generic N/A
 linux-backports-modules-5.8.0-18-generic  N/A
 linux-firmware1.190
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2020
dmi.bios.release: 1.62
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET89W (1.62 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EN0005MS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.18
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET89W(1.62):bd06/18/2020:br1.62:efr1.18:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EN0005MS
dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug groovy wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896446

Title:
  Running mcr.microsoft.com/mssql/server:2017-latest-ubuntu in docker
  hard-freezes the computer

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1890482] [NEW] Unable to load native library: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so: undefined symbol: JVM_InitializeFromArchive, version SUNWprivate_1.1

2020-08-05 Thread Martin Vysny
Public bug reported:

Hi, thank you so much for maintaining ubuntu and making it better for
everyone :)

The dcevm mode of java 11 doesn't work. Could you please look into it?

Steps to reproduce:
1. sudo apt install openjdk-11-jre-dcevm
2. java -dcevm

Unable to load native library: /usr/lib/jvm/java-11-openjdk-
amd64/lib/libjava.so: undefined symbol: JVM_InitializeFromArchive,
version SUNWprivate_1.1

Expected outcome: java should start properly

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openjdk-11-jre-dcevm 11.0.3+1-1
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.6
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug  5 21:39:16 2020
InstallationDate: Installed on 2015-11-19 (1721 days ago)
InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
SourcePackage: openjdk-11-jre-dcevm
UpgradeStatus: Upgraded to focal on 2020-04-11 (116 days ago)

** Affects: openjdk-11-jre-dcevm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890482

Title:
  Unable to load native library: /usr/lib/jvm/java-11-openjdk-
  amd64/lib/libjava.so: undefined symbol: JVM_InitializeFromArchive,
  version SUNWprivate_1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-11-jre-dcevm/+bug/1890482/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Lsusb-t.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377350/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Lspci-vt.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377348/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] PulseList.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377357/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] IwConfig.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377346/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] ProcInterrupts.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377355/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] CurrentDmesg.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377345/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Re: Kernel crash in nouveau with Wayland

2020-05-27 Thread Martin Vysny
apport information

** Tags added: apport-collected

** Description changed:

  The freeze causes the mouse cursor to stop moving and keyboard to stop
  responding and nothing moves on screen, not even the clock. Curiously
  the music continues to play (and e.g. sound from youtube video continues
  to be played even though the video itself freezes and no longer animates
  on-screen).
  
  It appears that the freeze happens quite randomly; I am not able to
  figure out what it's caused by. Sometimes it's caused by launching the
  Snap Chromium, or perhaps by a notification shown, but I do not know for
  sure. I also tried to hunt system logs and/or systemd gnome-shell logs,
  but I failed to discover some kind of crash dump.
  
  Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to
  believe that it's some kind of kernel+nouveau crash, but I can't seem to
  discover any kernel panic in the system logs.
  
  After the gnome-shell freezes, the numlock light still responds to
  numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm
  only able to reboot via Alt+Sysrq+s u b.
  
  Thank you :)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 12 11:20:36 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2016-09-05 (1344 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  mavi   2227 F pulseaudio
+  /dev/snd/controlC0:  mavi   2227 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ HibernationDevice: RESUME=/dev/mapper/vg0-lv0--swap
+ InstallationDate: Installed on 2016-09-05 (1360 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ MachineType: LENOVO 20EN0005MS
+ Package: linux (not installed)
+ ProcFB: 0 nouveaudrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic 
root=/dev/mapper/vg0-lv1--root ro splash ipv6.disable=1 nouveau.modeset=1 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-31-generic N/A
+  linux-backports-modules-5.4.0-31-generic  N/A
+  linux-firmware1.187
+ Tags:  wayland-session focal
+ Uname: Linux 5.4.0-31-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-03-20 (67 days ago)
+ UserGroups: adm cdrom dip docker kvm lpadmin lxd plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 12/06/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N1EET87W (1.60 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20EN0005MS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40705 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET87W(1.60):bd12/06/2019:svnLENOVO:pn20EN0005MS:pvrThinkPadP50:rvnLENOVO:rn20EN0005MS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad P50
+ dmi.product.name: 20EN0005MS
+ dmi.product.sku: LENOVO_MT_20EN_BU_Think_FM_ThinkPad P50
+ dmi.product.version: ThinkPad P50
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377343/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] ProcModules.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377356/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Lsusb.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1878166/+attachment/5377349/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] ProcCpuinfo.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377352/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] ProcCpuinfoMinimal.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377353/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Lsusb-v.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377351/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] RfKill.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1878166/+attachment/5377358/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] WifiSyslog.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377360/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Lspci.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1878166/+attachment/5377347/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] UdevDb.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1878166/+attachment/5377359/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] CRDA.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1878166/+attachment/5377344/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] ProcEnviron.txt

2020-05-27 Thread Martin Vysny
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1878166/+attachment/5377354/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  Kernel crash in nouveau with Wayland

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland

2020-05-27 Thread Martin Vysny
Daniel thank you so much for being so supportive, I really appreciate it
:)

I have ran the command `ubuntu-bug /var/crash/_usr_bin_gnome-
shell.1000.crash` which then opens a dialog; however when I press "Send"
there's no follow-up - no browser tab opens. The contents of
`_usr_bin_gnome-shell.1000.uploaded` says `93823806-9ff7-11ea-
9bb3-fa163e102db1` so maybe it's already there in your servers. From the
dialog I see the following title: gnome-shell crashed with SIGABRT in
__Gl___poll() (sorry copy-paste from the dialog doesn't work).

And there is no rush - the computer crashes once per day or so, so it's
definitely not that annoying; if it becomes an annoyance I'll install
the proprietary driver as a workaround.

Thanks again

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  gnome-shell freezes randomly on nouveau and wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland

2020-05-27 Thread Martin Vysny
Thank you kindly. I was able to ssh into the machine and prepare a crash
report from the gnome-shell process, I will upload that shortly, perhaps
as a separate bug report. However, the real culprit might be located in
the dmesg:


```
[12870.773176] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[12870.773196] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[12870.773220] nouveau :01:00.0: fifo: channel 6: killed
[12870.773229] nouveau :01:00.0: fifo: engine 5: scheduled for recovery
[12870.773234] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
[12870.773896] nouveau :01:00.0: systemd-logind[1312]: channel 6 killed!
[12907.524710] GpuWatchdog[5838]: segfault at 0 ip 560accf3e4c9 sp 
7f3ce9a516c0 error 6 in chrome[560ac8dd1000+7094000]
[12907.524716] Code: 00 79 09 48 8b 7d c0 e8 05 28 2b fc c7 45 c0 aa aa aa aa 
0f ae f0 41 8b 84 24 e0 00 00 00 89 45 c0 48 8d 7d c0 e8 e7 44 e9 fb  04 25 
00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e
[12922.616876] nouveau :01:00.0: Xwayland[2419]: failed to idle channel 4 
[Xwayland[2419]]
[12937.616723] nouveau :01:00.0: Xwayland[2419]: failed to idle channel 4 
[Xwayland[2419]]
[12937.616907] nouveau :01:00.0: fifo: fault 00 [READ] at 00013000 
engine 07 [HOST0] client 07 [HUB/HOST_CPU] reason 02 [PTE] on channel 4 
[007fa19000 Xwayland[2419]]
[12937.616915] nouveau :01:00.0: fifo: channel 4: killed
[12937.616917] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery
[12937.616923] nouveau :01:00.0: fifo: engine 0: scheduled for recovery
[12937.616941] nouveau :01:00.0: fifo: engine 5: scheduled for recovery
[12937.616945] nouveau :01:00.0: Xwayland[2419]: channel 4 killed!
[12937.735092] [ cut here ]
[12937.735142] WARNING: CPU: 3 PID: 26055 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6d/0x80 [nouveau]
[12937.735142] Modules linked in: rfcomm aufs cmac algif_hash algif_skcipher 
af_alg bnep overlay binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua intel_rapl_msr mei_hdcp snd_hda_codec_hdmi intel_rapl_common 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm intel_cstate 
intel_rapl_perf iwlmvm mac80211 libarc4 snd_usb_audio snd_hda_codec_realtek 
serio_raw intel_wmi_thunderbolt uvcvideo rmi_smbus snd_hda_codec_generic 
snd_usbmidi_lib rmi_core snd_seq_midi snd_seq_midi_event wmi_bmof 
videobuf2_vmalloc iwlwifi videobuf2_memops videobuf2_v4l2 snd_rawmidi 
snd_hda_intel videobuf2_common snd_intel_dspcfg rtsx_pci_ms thinkpad_acpi btusb 
snd_hda_codec nvram videodev btrtl btbcm snd_hda_core input_leds memstick 
ledtrig_audio mc snd_seq btintel joydev cfg80211 snd_hwdep bluetooth snd_pcm 
snd_seq_device mei_me ecdh_generic ecc snd_timer mei intel_pch_thermal snd 
soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport ip_tables 
x_tables autofs4 btrfs zstd_compress dm_crypt
[12937.735161]  raid10 raid456 async_raid6_recov async_memcpy async_pq 
async_xor async_tx xor hid_generic usbhid hid raid6_pq libcrc32c raid1 raid0 
multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel nouveau 
rtsx_pci_sdmmc mxm_wmi aesni_intel crypto_simd i2c_algo_bit ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt cryptd fb_sys_fops glue_helper drm e1000e 
psmouse ahci i2c_i801 rtsx_pci libahci wmi video
[12937.735173] CPU: 3 PID: 26055 Comm: chrome Not tainted 5.4.0-31-generic 
#35-Ubuntu
[12937.735174] Hardware name: LENOVO 20EN0005MS/20EN0005MS, BIOS N1EET87W (1.60 
) 12/06/2019
[12937.735194] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
[12937.735196] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 71 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ea f6 58 eb 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
[12937.735196] RSP: 0018:b807c5f5fbc8 EFLAGS: 00010282
[12937.735197] RAX: fffe RBX: b807c5f5fbf8 RCX: 
[12937.735198] RDX: 0010 RSI: b807c5f5fb38 RDI: b807c5f5fbd8
[12937.735198] RBP: b807c5f5fbe8 R08:  R09: 
[12937.735199] R10: 0030 R11: 9b7ac9c07e40 R12: b807c5f5fc30
[12937.735199] R13: 9b7ca4fff0b0 R14:  R15: 9b7ac9c07e38
[12937.735200] FS:  7f3cfaa1db00() GS:9b7cac2c() 
knlGS:
[12937.735201] CS:  0010 DS:  ES:  CR0: 80050033
[12937.735201] CR2: 560ad25fe010 CR3: 000842f0a004 CR4: 003606e0
[12937.735202] DR0:  DR1:  DR2: 
[12937.735202] DR3:  DR6: fffe0ff0 DR7: 0400
[12937.735203] Call Trace:
[12937.735265]  nouveau_vma_del+0x75/0xc0 [nouveau]
[12937.735316]  nouveau_gem_object_close+0x1f5/0x210 [nouveau]
[12937.735330]  drm_gem_object_release_handle+0x35/0xa0 [drm]
[12937.735337]  drm_gem_handle_delete+0x59/0xa0 [drm]
[12937.735344]  ? 

[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland

2020-05-27 Thread Martin Vysny
** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+attachment/5377303/+files/dmesg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  gnome-shell freezes randomly on nouveau and wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland

2020-05-24 Thread Martin Vysny
It was a different time, so maybe they're unrelated as you say.

Because the sound continues to play, I suspect that it's just the
graphics stack that freezes. To verify this assumption I've installed
openssh-server on the laptop; if the freeze occurs again, I'll ssh into
the machine and I may be able to gather useful debugging info.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  gnome-shell freezes randomly on nouveau and wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland

2020-05-24 Thread Martin Vysny
Thank you so much. I was not yet able to investigate the crash (it
usually happens during a video call and then I quickly need to reboot,
to continue chatting with the customer - no time to diagnose  :-D )

However, today I found out something in the log that might be connected
(even though in this case nothing crashed, the computer seems to be
continuing just fine):

[ 2090.256068] [ cut here ]
[ 2090.256153] WARNING: CPU: 5 PID: 6749 at 
drivers/gpu/drm/nouveau/nvif/vmm.c:68 nvif_vmm_put+0x6d/0x80 [nouveau]
[ 2090.256154] Modules linked in: ccm rfcomm aufs cmac algif_hash overlay 
algif_skcipher af_alg bnep binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc 
scsi_dh_alua snd_hda_codec_hdmi intel_rapl_msr mei_hdcp intel_rapl_common 
iwlmvm x86_pkg_temp_thermal intel_powerclamp coretemp mac80211 kvm_intel 
snd_hda_codec_realtek libarc4 snd_hda_codec_generic kvm rmi_smbus snd_usb_audio 
rmi_core uvcvideo snd_usbmidi_lib intel_cstate intel_rapl_perf 
videobuf2_vmalloc snd_hda_intel serio_raw btusb iwlwifi videobuf2_memops 
snd_intel_dspcfg videobuf2_v4l2 btrtl snd_seq_midi snd_hda_codec 
videobuf2_common snd_seq_midi_event snd_rawmidi btbcm snd_hda_core btintel 
intel_wmi_thunderbolt videodev input_leds joydev snd_hwdep wmi_bmof snd_seq 
thinkpad_acpi bluetooth rtsx_pci_ms mc snd_pcm memstick cfg80211 nvram 
ledtrig_audio mei_me ecdh_generic snd_seq_device ecc intel_pch_thermal mei 
snd_timer snd soundcore mac_hid sch_fq_codel cuse parport_pc ppdev lp parport 
ip_tables x_tables autofs4 btrfs zstd_compress
[ 2090.256181]  hid_generic usbhid hid dm_crypt raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel rtsx_pci_sdmmc nouveau aesni_intel crypto_simd mxm_wmi 
i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect cryptd sysimgblt 
glue_helper fb_sys_fops psmouse drm e1000e i2c_i801 rtsx_pci ahci libahci wmi 
video
[ 2090.256215] CPU: 5 PID: 6749 Comm: chrome Not tainted 5.4.0-31-generic 
#35-Ubuntu
[ 2090.256215] Hardware name: LENOVO 20EN0005MS/20EN0005MS, BIOS N1EET87W (1.60 
) 12/06/2019
[ 2090.256263] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau]
[ 2090.256283] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 
48 89 45 e8 e8 71 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb 
f2 e8 ea 26 7f ed 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44
[ 2090.256284] RSP: 0018:a8d503f27bc8 EFLAGS: 00010282
[ 2090.256286] RAX: fffe RBX: a8d503f27bf8 RCX: 
[ 2090.256287] RDX: 0010 RSI: a8d503f27b38 RDI: a8d503f27bd8
[ 2090.256287] RBP: a8d503f27be8 R08:  R09: 
[ 2090.256288] R10: 0030 R11: 927e7fc8f640 R12: a8d503f27c30
[ 2090.256289] R13: 927f64fee0b0 R14:  R15: 927e7fc8f638
[ 2090.256290] FS:  7f0fb553bb00() GS:927f6c34() 
knlGS:
[ 2090.256291] CS:  0010 DS:  ES:  CR0: 80050033
[ 2090.256291] CR2: 55bdb8317000 CR3: 00088824a003 CR4: 003606e0
[ 2090.256292] DR0:  DR1:  DR2: 
[ 2090.256306] DR3:  DR6: fffe0ff0 DR7: 0400
[ 2090.256306] Call Trace:
[ 2090.256362]  nouveau_vma_del+0x75/0xc0 [nouveau]
[ 2090.256402]  nouveau_gem_object_close+0x1f5/0x210 [nouveau]
[ 2090.256416]  drm_gem_object_release_handle+0x35/0xa0 [drm]
[ 2090.256427]  drm_gem_handle_delete+0x59/0xa0 [drm]
[ 2090.256449]  ? drm_gem_handle_create+0x40/0x40 [drm]
[ 2090.256478]  drm_gem_close_ioctl+0x24/0x30 [drm]
[ 2090.256488]  drm_ioctl_kernel+0xae/0xf0 [drm]
[ 2090.256511]  drm_ioctl+0x234/0x3d0 [drm]
[ 2090.256522]  ? drm_gem_handle_create+0x40/0x40 [drm]
[ 2090.256526]  ? evict+0x14c/0x1b0
[ 2090.256565]  nouveau_drm_ioctl+0x78/0xc0 [nouveau]
[ 2090.256567]  do_vfs_ioctl+0x407/0x670
[ 2090.256570]  ? __secure_computing+0x42/0xe0
[ 2090.256571]  ksys_ioctl+0x67/0x90
[ 2090.256573]  __x64_sys_ioctl+0x1a/0x20
[ 2090.256575]  do_syscall_64+0x57/0x190
[ 2090.256578]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 2090.256579] RIP: 0033:0x7f0fae1375d7
[ 2090.256581] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7 
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
[ 2090.256595] RSP: 002b:7ffcbdcc1068 EFLAGS: 0246 ORIG_RAX: 
0010
[ 2090.256596] RAX: ffda RBX: 55bdb82e3870 RCX: 7f0fae1375d7
[ 2090.256597] RDX: 7ffcbdcc10a0 RSI: 40086409 RDI: 0015
[ 2090.256597] RBP: 7ffcbdcc10a0 R08:  R09: 0002
[ 2090.256598] R10: 7f0fa1124070 R11: 0246 R12: 40086409
[ 2090.256599] R13: 0015 R14: 0001 R15: b82c7b00
[ 2090.256600] ---[ end trace 9a9c0a943b125b8f ]---
[ 

[Bug 1878919] [NEW] kworker/0:1+kacpid uses 100% of one CPU core

2020-05-15 Thread Martin Vysny
Public bug reported:

At some point, kworker/0:1+kacpid starts using 100% of one CPU's core;
this can be seen in the top command.

I captured some performance data via the following command:
$ perf record -g -a sleep 10

Then, perf report gives the following:


Samples: 75K of event 'cycles', Event count (approx.): 44710762967
  Children  Self  Command  Shared Object   
Symbol
+   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] ret_from_fork
+   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] kthread
+   65,46% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] worker_thread
+   65,44% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] process_one_work
+   65,44% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_os_execute_deferred
+   65,33% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ev_asynch_execute_gpe_method
+   65,32% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_evaluate
+   65,26% 0,00%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_execute_method
+   65,16% 0,06%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_parse_aml
+   61,00% 0,94%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_parse_loop
+   37,83% 0,75%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_exec_end_op
+   18,33% 0,04%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_evaluate_name_path
+   16,12% 0,23%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_lookup
+   15,79% 0,20%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_search_and_enter
+   15,23%14,99%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ns_search_one_scope
+   14,38% 0,00%  swapper  [kernel.kallsyms]   
[k] secondary_startup_64
+   14,38% 0,02%  swapper  [kernel.kallsyms]   
[k] cpu_startup_entry
+   14,31% 0,12%  swapper  [kernel.kallsyms]   
[k] do_idle
+   13,79% 0,00%  swapper  [kernel.kallsyms]   
[k] start_secondary
+   12,92% 0,03%  swapper  [kernel.kallsyms]   
[k] call_cpuidle
+   12,89% 0,00%  swapper  [kernel.kallsyms]   
[k] cpuidle_enter
+   12,85% 0,05%  swapper  [kernel.kallsyms]   
[k] cpuidle_enter_state
+   12,35% 2,15%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_update_object_reference
+   12,05% 0,28%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_resolve_to_value
+   10,40% 0,04%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_resolve_node_to_value
+9,90% 0,44%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_create_operand
+9,50% 0,05%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_read_data_from_field
+9,39% 0,06%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_field_datum_io
+9,26% 0,12%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_access_region
+9,23% 0,08%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_get_next_namepath
+9,15% 1,28%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_update_ref_count.part.0
+9,01% 0,08%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ev_address_space_dispatch
+8,96% 0,14%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_extract_from_field
+8,78% 7,70%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ex_system_memory_space_handler
+7,81% 0,22%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_remove_reference
+6,63% 6,43%  swapper  [kernel.kallsyms]   
[k] intel_idle
+5,31% 0,68%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_create_op
+5,12% 0,08%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_add_reference
+4,89% 0,07%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_delete_result_if_not_used
+4,71% 0,09%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_do_implicit_return
+4,61% 0,17%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ds_is_result_used
+3,91% 3,62%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ut_track_stack_ptr
+3,83% 0,31%  kworker/0:1+kac  [kernel.kallsyms]   
[k] acpi_ps_complete_op
+3,39% 

[Bug 1878166] Re: gnome-shell freezes randomly on nouveau and wayland

2020-05-12 Thread Martin Vysny
Thank you, I was exactly hoping for a guidance on how to debug this
issue further.

The crash happened today 10:55:00; please find the output of journalctl
-b-1 attached.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+attachment/5370267/+files/prevboot.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  gnome-shell freezes randomly on nouveau and wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878166] [NEW] gnome-shell freezes randomly on nouveau and wayland

2020-05-12 Thread Martin Vysny
Public bug reported:

The freeze causes the mouse cursor to stop moving and keyboard to stop
responding and nothing moves on screen, not even the clock. Curiously
the music continues to play (and e.g. sound from youtube video continues
to be played even though the video itself freezes and no longer animates
on-screen).

It appears that the freeze happens quite randomly; I am not able to
figure out what it's caused by. Sometimes it's caused by launching the
Snap Chromium, or perhaps by a notification shown, but I do not know for
sure. I also tried to hunt system logs and/or systemd gnome-shell logs,
but I failed to discover some kind of crash dump.

Curiously the Ctrl+Alt+F2 key combo stops working. That leads me to
believe that it's some kind of kernel+nouveau crash, but I can't seem to
discover any kernel panic in the system logs.

After the gnome-shell freezes, the numlock light still responds to
numlock key presses. However, mashing Ctrl+Alt+Del has no effect, so I'm
only able to reboot via Alt+Sysrq+s u b.

Thank you :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 11:20:36 2020
DisplayManager: gdm3
InstallationDate: Installed on 2016-09-05 (1344 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-03-20 (52 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878166

Title:
  gnome-shell freezes randomly on nouveau and wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1878166/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865342] Re: Extensions don't work on Gnome Shell 3.36

2020-04-19 Thread Martin Vysny
Thank you very much, I've updated my Ubuntu 20.04 and I confirm that the
System Monitor extension started working again. Thanks again :)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865342

Title:
  Extensions don't work on Gnome Shell 3.36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-system-monitor/+bug/1865342/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1868924] [NEW] a desktop launcher icon can not be activated by focusing and pressing enter

2020-03-25 Thread Martin Vysny
Public bug reported:

I have a desktop launcher icon which launches a shell script which auto-
starts apps that I use. I tend to click on the launcher icon with my
mouse, then press Enter to run the launcher. This worked well on Ubuntu
19.10 but stopped working on Ubuntu 20.04. Double-clicking on the
launcher icon correctly launches the launcher, and I'm happy with the
workaround. Yet, maybe something to look into. Thank you kindly :)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-desktop-icons 19.10.2+git20200223-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 25 08:14:30 2020
InstallationDate: Installed on 2016-09-05 (1296 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-desktop-icons
UpgradeStatus: Upgraded to focal on 2020-03-20 (4 days ago)

** Affects: gnome-shell-extension-desktop-icons (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1868924

Title:
  a desktop launcher icon can not be activated by focusing and pressing
  enter

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1868924/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866787] [NEW] java dcevm crashes immediately with Invalid layout of java.lang.StackFrameInfo field: bci type: S

2020-03-10 Thread Martin Vysny
Public bug reported:

I've installed openjdk-11-jdk, openjdk-11-source, openjdk-11-doc,
openjdk-11-jre-dcevm. Attempting to run java -dcevm fails immediately:

$ java -dcevm
[0.014s][error][class] Invalid layout of java.lang.StackFrameInfo field: bci 
type: S
Error occurred during initialization of VM
Invalid layout of preloaded class: use -Xlog:class+load=info to see the origin 
of the problem class


More verbose info:

$ java -dcevm -Xlog:class+load=info
[0.002s][info][class,load] opened: 
/usr/lib/jvm/java-11-openjdk-amd64/lib/modules
[0.006s][info][class,load] java.lang.Object source: jrt:/java.base
[0.006s][info][class,load] java.io.Serializable source: jrt:/java.base
[0.006s][info][class,load] java.lang.Comparable source: jrt:/java.base
[0.006s][info][class,load] java.lang.CharSequence source: jrt:/java.base
[0.006s][info][class,load] java.lang.String source: jrt:/java.base
[0.006s][info][class,load] java.lang.reflect.AnnotatedElement source: 
jrt:/java.base
[0.007s][info][class,load] java.lang.reflect.GenericDeclaration source: 
jrt:/java.base
[0.007s][info][class,load] java.lang.reflect.Type source: jrt:/java.base
[0.007s][info][class,load] java.lang.Class source: jrt:/java.base
[0.007s][info][class,load] java.lang.Cloneable source: jrt:/java.base
[0.007s][info][class,load] java.lang.ClassLoader source: jrt:/java.base
[0.007s][info][class,load] java.lang.System source: jrt:/java.base
[0.007s][info][class,load] java.lang.Throwable source: jrt:/java.base
[0.007s][info][class,load] java.lang.Error source: jrt:/java.base
[0.007s][info][class,load] java.lang.ThreadDeath source: jrt:/java.base
[0.007s][info][class,load] java.lang.Exception source: jrt:/java.base
[0.007s][info][class,load] java.lang.RuntimeException source: jrt:/java.base
[0.007s][info][class,load] java.lang.SecurityManager source: jrt:/java.base
[0.008s][info][class,load] java.security.ProtectionDomain source: jrt:/java.base
[0.008s][info][class,load] java.security.AccessControlContext source: 
jrt:/java.base
[0.008s][info][class,load] java.security.SecureClassLoader source: 
jrt:/java.base
[0.008s][info][class,load] java.lang.ReflectiveOperationException source: 
jrt:/java.base
[0.008s][info][class,load] java.lang.ClassNotFoundException source: 
jrt:/java.base
[0.008s][info][class,load] java.lang.LinkageError source: jrt:/java.base
[0.008s][info][class,load] java.lang.NoClassDefFoundError source: jrt:/java.base
[0.008s][info][class,load] java.lang.ClassCastException source: jrt:/java.base
[0.008s][info][class,load] java.lang.ArrayStoreException source: jrt:/java.base
[0.008s][info][class,load] java.lang.VirtualMachineError source: jrt:/java.base
[0.008s][info][class,load] java.lang.OutOfMemoryError source: jrt:/java.base
[0.008s][info][class,load] java.lang.StackOverflowError source: jrt:/java.base
[0.008s][info][class,load] java.lang.IllegalMonitorStateException source: 
jrt:/java.base
[0.008s][info][class,load] java.lang.ref.Reference source: jrt:/java.base
[0.008s][info][class,load] java.lang.ref.SoftReference source: jrt:/java.base
[0.008s][info][class,load] java.lang.ref.WeakReference source: jrt:/java.base
[0.008s][info][class,load] java.lang.ref.FinalReference source: jrt:/java.base
[0.008s][info][class,load] java.lang.ref.PhantomReference source: jrt:/java.base
[0.008s][info][class,load] java.lang.ref.Finalizer source: jrt:/java.base
[0.008s][info][class,load] java.lang.Runnable source: jrt:/java.base
[0.008s][info][class,load] java.lang.Thread source: jrt:/java.base
[0.008s][info][class,load] java.lang.Thread$UncaughtExceptionHandler source: 
jrt:/java.base
[0.008s][info][class,load] java.lang.ThreadGroup source: jrt:/java.base
[0.009s][info][class,load] java.util.Map source: jrt:/java.base
[0.009s][info][class,load] java.util.Dictionary source: jrt:/java.base
[0.009s][info][class,load] java.util.Hashtable source: jrt:/java.base
[0.009s][info][class,load] java.util.Properties source: jrt:/java.base
[0.009s][info][class,load] java.lang.Module source: jrt:/java.base
[0.009s][info][class,load] java.lang.reflect.AccessibleObject source: 
jrt:/java.base
[0.009s][info][class,load] java.lang.reflect.Member source: jrt:/java.base
[0.010s][info][class,load] java.lang.reflect.Field source: jrt:/java.base
[0.010s][info][class,load] java.lang.reflect.Parameter source: jrt:/java.base
[0.010s][info][class,load] java.lang.reflect.Executable source: jrt:/java.base
[0.010s][info][class,load] java.lang.reflect.Method source: jrt:/java.base
[0.010s][info][class,load] java.lang.reflect.Constructor source: jrt:/java.base
[0.010s][info][class,load] jdk.internal.reflect.MagicAccessorImpl source: 
jrt:/java.base
[0.010s][info][class,load] jdk.internal.reflect.MethodAccessor source: 
jrt:/java.base
[0.010s][info][class,load] jdk.internal.reflect.MethodAccessorImpl source: 
jrt:/java.base
[0.010s][info][class,load] jdk.internal.reflect.ConstructorAccessor source: 
jrt:/java.base
[0.010s][info][class,load] jdk.internal.reflect.ConstructorAccessorImpl 

[Bug 1865342] [NEW] Error: Tried to construct an object without a GType

2020-03-01 Thread Martin Vysny
Public bug reported:

The gnome-shell-extension-system-monitor won't start after login;
there's the following stacktrace in journalctl /usr/bin/gnome-shell:

```
maalis 01 14:58:11 sumomo2 gnome-shell[2564]: JS ERROR: Extension 
system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object 
without a GType; are you using GObject.registerClass() when inheriting from a 
GObject type?
SystemMonitor_TipItem@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9
tip_format@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27
SystemMonitor_Cpu@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:9
createCpus@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20
enable@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:149:13
loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:281:21
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:499:13
collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:474:9
_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:508:13
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:539:13
init@resource:///org/gnome/shell/ui/extensionSystem.js:49:9
_initializeUI@resource:///org/gnome/shell/ui/main.js:245:5
start@resource:///org/gnome/shell/ui/main.js:141:5
@:1:31
```

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell-extension-system-monitor 38-2
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar  1 15:07:54 2020
InstallationDate: Installed on 2018-06-25 (615 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: gnome-shell-extension-system-monitor
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)

** Affects: gnome-shell-extension-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal wayland-session

** Description changed:

  The gnome-shell-extension-system-monitor won't start after login;
  there's the following stacktrace in journalctl /usr/bin/gnome-shell:
  
  maalis 01 14:58:11 sumomo2 gnome-shell[2564]: JS ERROR: Extension 
system-moni...@paradoxxx.zero.gmail.com: Error: Tried to construct an object 
without a GType; are you using GObject.registerClass() when>
-   
SystemMonitor_TipItem@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9
-   
tip_format@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27
-   
SystemMonitor_Cpu@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1196:9
-   
createCpus@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:1363:20
-   
enable@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:2316:26
-   
_callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:149:13
-   
loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:281:21
-   
_loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:499:13
-   
collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:17
-   
_loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:474:9
-   
_enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:508:13
-   
_sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:539:13
-   
init@resource:///org/gnome/shell/ui/extensionSystem.js:49:9
-   
_initializeUI@resource:///org/gnome/shell/ui/main.js:245:5
-   
start@resource:///org/gnome/shell/ui/main.js:141:5
-   @:1:31
+ 
SystemMonitor_TipItem@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:640:9
+ 
tip_format@/usr/share/gnome-shell/extensions/system-moni...@paradoxxx.zero.gmail.com/extension.js:898:27
+ 

[Bug 1847184] [NEW] java Keyboard stops working after a dialog is shown

2019-10-07 Thread Martin Vysny
Public bug reported:

On Ubuntu 19.10 + Gnome + Wayland, after a dialog (any dialog) is shown,
the keyboard stops working in Intellij - the editor stops responding to
keystrokes, global shortcuts like Ctrl+N stops working etc, until you
alt-tab to another application and back to intellij.

The bug has been reported here to Intellij:
https://youtrack.jetbrains.com/issue/IDEA-222415

However, the bug was really present in
https://gitlab.gnome.org/GNOME/mutter/issues/819

The fix is already in git:
https://www.phoronix.com/scan.php?page=news_item=Java-Focus-GNOME-
Wayland

Could you please upgrade Mutter to include fix for this issue? Thank you
:) Have a nice day ;)

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: mutter 3.34.0-3ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  8 07:52:13 2019
InstallationDate: Installed on 2016-09-05 (1127 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: mutter
UpgradeStatus: Upgraded to eoan on 2019-09-26 (11 days ago)

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


** Tags: amd64 apport-bug eoan wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847184

Title:
  java Keyboard stops working after a dialog is shown

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838179] Re: gnome-system-monitor snap segfaults

2019-07-28 Thread Martin Vysny
ubuntu 19.04 x86-64 5.0.0-21-generic #22-Ubuntu SMP Tue Jul 2 13:27:33
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838179

Title:
  gnome-system-monitor snap segfaults

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1838179/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1838179] [NEW] gnome-system-monitor snap segfaults

2019-07-28 Thread Martin Vysny
Public bug reported:

I have gnome-system-monitor installed as a snap. It never starts for me
- it always segfaults.

$ snap info gnome-system-monitor 
name:  gnome-system-monitor
summary:   System Monitor
publisher: Canonical✓
contact:   
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bugs?field.tag=snap
license:   unset
description: |
  GNOME System Monitor is a GNOME process viewer and system monitor with
  an attractive, easy-to-use interface, It has features, such as a tree
  view for process dependencies, icons for processes, the ability to hide
  processes that you don't want to see, graphical time histories of
  CPU/memory/swap usage, the ability to kill/renice processes needing root
  access, as well as the standard features that you might expect from a
  process viewer.
commands:
  - gnome-system-monitor
snap-id:  9BTClmjz31r0UltmbJ5nnGe0Xm1AzfMp
tracking: stable/ubuntu-18.10
refresh-date: 18 days ago, at 23:46 EEST
channels:
  stable:3.32.1-3-g0ea89b4922 2019-07-09 (100) 3MB -
  candidate: 3.32.1-3-g0ea89b4922 2019-07-09 (100) 3MB -
  beta:  ↑ 
  edge:  ↑ 
installed:   3.32.1-3-g0ea89b4922(100) 3MB -


$ gnome-system-monitor 
mkdir: cannot create directory 
'/home/vyzivus/snap/gnome-system-monitor/100/.config': Permission denied
mkdir: cannot create directory 
'/home/vyzivus/snap/gnome-system-monitor/100/.local': Permission denied
/snap/gnome-system-monitor/100/bin/desktop-launch: line 246: 
/home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.dirs: No such 
file or directory
cp: cannot create regular file 
'/home/vyzivus/snap/gnome-system-monitor/100/.config': Permission denied
/snap/gnome-system-monitor/100/bin/desktop-launch: line 249: 
/home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.dirs.md5sum: No 
such file or directory
/snap/gnome-system-monitor/100/bin/desktop-launch: line 249: 
/home/vyzivus/snap/gnome-system-monitor/100/.config/user-dirs.locale.md5sum: No 
such file or directory
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Desktop
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Downloads
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Templates
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Public
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Documents
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Music
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Pictures
Can't create dir /home/vyzivus/snap/gnome-system-monitor/100/Videos
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
realpath: '': No such file or directory
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.config’: Permission denied
/snap/gnome-system-monitor/100/bin/desktop-launch: line 381: 
/home/vyzivus/snap/gnome-system-monitor/100/.config/fontconfig/fonts.conf: No 
such file or directory
ln: failed to create symbolic link 
'/home/vyzivus/snap/gnome-system-monitor/100/.local/share': No such file or 
directory
ln: failed to create symbolic link 
'/home/vyzivus/snap/gnome-system-monitor/100/.themes': Permission denied
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied
ln: target 
'/home/vyzivus/snap/gnome-system-monitor/100/.local/share/glib-2.0/schemas' is 
not a directory
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.config’: Permission denied
ln: failed to create symbolic link 
'/home/vyzivus/snap/gnome-system-monitor/100/.config/dconf': No such file or 
directory
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied
ln: target 
'/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/DMZ-Black' is 
not a directory
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied
ln: target 
'/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/DMZ-White' is 
not a directory
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied
ln: failed to create symbolic link 
'/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/Papirus-Adapta-Maia':
 No such file or directory
mkdir: cannot create directory 
‘/home/vyzivus/snap/gnome-system-monitor/100/.local’: Permission denied
ln: failed to create symbolic link 
'/home/vyzivus/snap/gnome-system-monitor/100/.local/share/icons/Papirus-Adapta-Nokto-Maia':
 No such file or directory
mkdir: cannot create directory 

[Bug 1826830] [NEW] newly launched apps start unfocused

2019-04-29 Thread Martin Vysny
Public bug reported:

For example, pressing the ENTER key on a .png image in Krusader will
start the Gnome Image Viewer (if Krusader is so configured), however the
focus returns back to the Krusader. Pressing DEL would then delete files
in the Krusader; pressing any keys controls the Krusader but since it's
obscured by the Image Viewer, it's hard to see what's going on. This is
highly confusing to me.

A better solution would be either to start the Image Viewer focused, or
to start the Image Viewer in the background, behind krusader (and
perhaps flashing the icon in the Unity dock).

I'm not sure whether the bug is in Krusader itself, or in Gnome-Shell
(being a window manager), I'm a bit guessing here :)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 29 08:55:02 2019
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.shell' b'enabled-extensions' 
b"['system-moni...@paradoxxx.zero.gmail.com', 'desktop-icons@csoriano', 
'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']"
 b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2016-09-05 (965 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-03-12 (47 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826830

Title:
  newly launched apps start unfocused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1826830] Re: newly launched apps start unfocused

2019-04-29 Thread Martin Vysny
Definitely Gnome Shell, since starting e.g. "Files" (Nautilus) from the
dock starts the Nautilus unfocused, sending any keystrokes to whatever
app was active before.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826830

Title:
  newly launched apps start unfocused

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824642] Re: nvidia card disabled after upgrading to 5.0.0-11-generic

2019-04-14 Thread Martin Vysny
You're right, thank you very much for pointing that out! Adding
nouveau.modeset=1 fixed things for me as well. This bug can be closed as
a duplicite of https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-
video-nouveau/+bug/1824677

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824642

Title:
  nvidia card disabled after upgrading to 5.0.0-11-generic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824642] Re: nvidia card disabled after upgrading to 5.0.0-11-generic

2019-04-13 Thread Martin Vysny
I have just upgraded to 5.0.0-11 on my other laptop also with hybrid
Intel+Nvidia GPU stack (a different Nvidia GPU though) - the same thing
happened, Linux+nouveau completely ignores the nvidia GPU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824642

Title:
  nvidia card disabled after upgrading to 5.0.0-11-generic

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   >