date:20190609

[Expired for QEMU because there has been no activity for 60 days.]

** Changed in: qemu
   Status: Incomplete => Expired

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

Title:
  qemu runas and sandbox option incompatible, process will hang in futex
  after setgid

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

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

[Bug 1176569] Re: Poor Scanning Performance (Speed)

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

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

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

Title:
  Poor Scanning Performance (Speed)

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

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

[Bug 1525676] Re: qemu runas and sandbox option incompatible, process will hang in futex after setgid

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

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

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

Title:
  qemu runas and sandbox option incompatible, process will hang in futex
  after setgid

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

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

[Bug 1821597] Re: USB suspend / resume with docking station and laptop lid closed

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

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

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

Title:
  USB suspend / resume with docking station and laptop lid closed

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

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

[Bug 1821034] Re: release-upgrade-motd can't update message

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

** Changed in: update-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  release-upgrade-motd can't update message

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1821034/+subscriptions

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

[Bug 1824006] Re: package winbind 2:4.3.11+dfsg-0ubuntu0.16.04.19 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

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

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

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

Title:
  package winbind 2:4.3.11+dfsg-0ubuntu0.16.04.19 failed to
  install/upgrade: проблемы зависимостей — оставляем не настроенным

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

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

[Bug 1824007] Re: package samba 2:4.3.11+dfsg-0ubuntu0.16.04.19 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

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

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

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

Title:
  package samba 2:4.3.11+dfsg-0ubuntu0.16.04.19 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  возвратил код ошибки 1

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

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

[Bug 1823455] Re: package libisccc140 1:9.10.3.dfsg.P4-8ubuntu1.12 failed to install/upgrade: too-long line or missing newline in '/var/lib/dpkg/info/libisccc140:armhf.triggers'

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

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

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

Title:
  package libisccc140 1:9.10.3.dfsg.P4-8ubuntu1.12 failed to
  install/upgrade: too-long line or missing newline in
  '/var/lib/dpkg/info/libisccc140:armhf.triggers'

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

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

[Bug 1824072] Re: Intel XL710 series NIC can't receive any packet on 18.04 & 18.10 Ubuntu-arm64-server

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

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

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

Title:
  Intel XL710 series NIC can't receive any packet on 18.04 & 18.10
  Ubuntu-arm64-server

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

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

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2019-06-09 Thread Nicolas_Raoul

Original poster here.

I switched to 19.04 (disco) in April, and I have never seen this bug
again since (default window manager and everything).

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

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

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

[Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C KVM

2019-06-09 Thread Po-Hsu Lin

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** Also affects: linux-kvm (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Summary changed:

- test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C 
KVM
+ test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on 
B/C/D KVM

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on B/C/D KVM

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions

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

[Bug 1832137] Re: The default shell theme is titled Default instead of its real name 'Yaru' or 'Adwaita'

Sorry, I was convinced it was possible to select Adwaita. But it seems
my memory was confused with either selecting the Applications theme or
because I build gnome-shell from source every day and see the Adwaita
shell theme every day there.


** Summary changed:

- The default shell theme is titled Default instead of its real name 'Yaru' or 
'Adwaita'
+ Can't switch between Yaru and Adwaita shell themes, even when User Themes is 
enabled

** Changed in: yaru-theme (Ubuntu)
   Importance: Wishlist => Medium

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

Title:
  Can't switch between Yaru and Adwaita shell themes, even when User
  Themes is enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => New

** Changed in: mutter (Ubuntu)
   Status: Incomplete => New

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832137] Re: The default shell theme is titled Default instead of its real name 'Yaru' or 'Adwaita'

Just to make it crystal clear. I now enter my Ubuntu session, go to
Tweaks and get this shell themes list:

(1)
Default
Materia
Materia-compact
Materia-dark
Materia-dark-compact
Materia-light
Materia-light-compact

Nevertheless, Adwaita shell theme IS installed in my computer. Hence I
would like to see:

(2)
Default
Adwaita  <---
Materia
Materia-compact
Materia-dark
Materia-dark-compact
Materia-light
Materia-light-compact

If, instead, I enter my vanilla Gnome session I again get (1) above but
I would like to see:

(3)
Default
Materia
Materia-compact
Materia-dark
Materia-dark-compact
Materia-light
Materia-light-compact
Yaru  <-

Now, creating the symlinks I proposed, I won't get (2) and (3) but the
quite similar (4):

(4)
Default
Adwaita  <
Materia
Materia-compact
Materia-dark
Materia-dark-compact
Materia-light
Materia-light-compact
Yaru  <---

Under both types of session there would be redundancy, since sometimes
Default means Adwaita and sometimes it means Yaru, but I see that as a
lesser problem than being unable to select "the other" theme.

Finally, a minimal proposal is to create just one of the symlinks to get
Yaru into the list but not Adwaita, so only yaru-theme has to be
patched.

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

Title:
  The default shell theme is titled Default instead of its real name
  'Yaru' or 'Adwaita'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832159] [NEW] nfs-ganesha-config.service fails to start due to bad path

2019-06-09 Thread Jason Alavaliant

Public bug reported:

The nfs-ganesha package installs the systemd unit file
/lib/systemd/system/nfs-ganesha-config.service

which specifies
ExecStart=/usr/lib/ganesha/nfs-ganesha-config.sh

but no such file is provided by the package so the service fails to
start.

The package does install a /usr/lib/nfs-ganesha-config.sh so I'd presume
either the file is being installed to the wrong location when the
package is being built or the nfs-ganesha-config.service needs it's
ExecStart= value corrected.

I'm using bionic/18.04,   I've not tested for if the bug is present in
other package versions.

** Affects: nfs-ganesha (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  nfs-ganesha-config.service fails to start due to bad path

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/1832159/+subscriptions

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

[Bug 1832137] Re: The default shell theme is titled Default instead of its real name 'Yaru' or 'Adwaita'

Oh, I now see why I was not following you. I don't think the "Default"
name to be a problem, quite to the contrary. What I don't like is the
inability to select the other (the non-default) theme. Even if you
renamed Default to Yaru, that won't make Adwaita appear. And if in a
vanilla session you renamed Default to Adwaita, that won't make Yaru
appear either. The only way for a shell theme to appear in Tweaks with a
name that is not "Default" is to be listed under
/usr/share/themes//gnome-shell (OTOH, to be "Default" it has to
live under /usr/share/gnome-shell/theme).

What I did point out is that by linking "the other theme" from
/usr/share/themes you would get two entries for the same theme, the
Default one and the Yaru/Adwaita one. Now, if you wanted to remove
Default and at the same time introduce Yaru and Adwaita, I think that
would be more difficult to achieve that my simple fix. But, in any case,
now the description is not accurate to me :)

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

Title:
  The default shell theme is titled Default instead of its real name
  'Yaru' or 'Adwaita'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1769545]

2019-06-09 Thread gkapoor

Issue mentioned in
https://bugzilla.redhat.com/show_bug.cgi?id=1540924#c18 happens when
there are certificates not available.During HSM installation especially
migrations , client machines needs to sync correctly.This can be done
using :

ON CS 8:
===

 /opt/nfast/bin/rfs-sync --setup --no-authenticate 
 /opt/nfast/bin/rfs-setup --gang-client --write-noauth 
 /opt/nfast/bin/rfs-sync --commit


on RHEL 7 (CS 9) machine do :

/opt/nfast/bin/rfs-sync --update


After doing this NPE which occurred at at 
com.netscape.cms.servlet.csadmin.ConfigurationUtils.createPKCS7(ConfigurationUtils.java:3374)
 should not come.

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

Title:
  DerInput.getLength(): lengthTag=9, too big.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1769545/+subscriptions

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-09 Thread Pat

Hi Daniel,

It doesn't appear anything has actually crashed when this scenario happens.
/var/crash is empty

The contents of my /var/lib/whoopsie/whoopsie-id is;
d0d31e5e858096f38cba06e106ab0375a0e96fd9fda7031d320fa3966f0064bba364acdc53d42bce08a29148a49314d352455fe8b6cb716c20dbf804d8711876

There is nothing
at;https://errors.ubuntu.com/user/d0d31e5e858096f38cba06e106ab0375a0e96fd9fda7031d320fa3966f0064bba364acdc53d42bce08a29148a49314d352455fe8b6cb716c20dbf804d8711876

When the system boots up, I briefly see the splash screen then the
splash goes away and all I see is a completely blank purple-ish page.
No login page.  No indications at all that anything has gone wrong
perse.  And no log files.

If I ssh into the system,

Here is output of 'sudo systemctl status gdm'

- snip -
● gdm.service - GNOME Display Manager
   Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: 
enabled)
   Active: active (running) since Sun 2019-06-09 21:12:34 MDT; 2min 59s ago
  Process: 1095 ExecStartPre=/usr/share/gdm/generate-config (code=exited, 
status=0/SUCCESS)
 Main PID: 1098 (gdm3)
Tasks: 3 (limit: 4651)
   CGroup: /system.slice/gdm.service
   └─1098 /usr/sbin/gdm3

Jun 09 21:12:34 ubuntuvm1 systemd[1]: Starting GNOME Display Manager...
Jun 09 21:12:34 ubuntuvm1 systemd[1]: Started GNOME Display Manager.
Jun 09 21:12:34 ubuntuvm1 gdm-launch-environment][1112]: 
pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0)
- snip -

Here is output of 'sudo systemctl status session-c1.scope';

- snip -
● session-c1.scope - Session c1 of user gdm
   Loaded: loaded (/run/systemd/transient/session-c1.scope; transient)
Transient: yes
   Active: active (running) since Sun 2019-06-09 21:12:34 MDT; 12min ago
Tasks: 102
   CGroup: /user.slice/user-120.slice/session-c1.scope
   ├─1112 gdm-session-worker [pam/gdm-launch-environment]
   ├─1274 /usr/lib/gdm3/gdm-wayland-session gnome-session --autostart 
/usr/share/gdm/greeter/autostart
   ├─1285 /usr/lib/gnome-session/gnome-session-binary --autostart 
/usr/share/gdm/greeter/autostart
   ├─1383 /usr/bin/gnome-shell
   ├─1461 /usr/bin/Xwayland :1024 -rootless -terminate -accessx -core 
-listen 4 -listen 5 -displayfd 6
   ├─1528 ibus-daemon --xim --panel disable
   ├─1531 /usr/lib/ibus/ibus-dconf
   ├─1534 /usr/lib/ibus/ibus-x11 --kill-daemon
   ├─1550 /usr/lib/gnome-settings-daemon/gsd-xsettings
   ├─1554 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
   ├─1556 /usr/lib/gnome-settings-daemon/gsd-clipboard
   ├─1558 /usr/lib/gnome-settings-daemon/gsd-color
   ├─1560 /usr/lib/gnome-settings-daemon/gsd-datetime
   ├─1561 /usr/lib/gnome-settings-daemon/gsd-housekeeping
   ├─1562 /usr/lib/gnome-settings-daemon/gsd-keyboard
   ├─1563 /usr/lib/gnome-settings-daemon/gsd-media-keys
   ├─1568 /usr/lib/gnome-settings-daemon/gsd-mouse
   ├─1570 /usr/lib/gnome-settings-daemon/gsd-power
   ├─1573 /usr/lib/gnome-settings-daemon/gsd-print-notifications
   ├─1578 /usr/lib/gnome-settings-daemon/gsd-rfkill
   ├─1579 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
   ├─1581 /usr/lib/gnome-settings-daemon/gsd-sharing
   ├─1587 /usr/lib/gnome-settings-daemon/gsd-smartcard
   ├─1592 /usr/lib/gnome-settings-daemon/gsd-sound
   ├─1595 /usr/lib/gnome-settings-daemon/gsd-wacom
   └─1605 /usr/lib/ibus/ibus-engine-simple

Jun 09 21:12:34 ubuntuvm1 systemd[1]: Started Session c1 of user gdm.
Jun 09 21:12:35 ubuntuvm1 org.gnome.Shell.desktop[1383]: glamor: EGL version 
1.4 (DRI2):
Jun 09 21:12:36 ubuntuvm1 spice-vdagent[1596]: Cannot access vdagent virtio 
channel /dev/virtio-ports/com.redhat.spice.0
Jun 09 21:12:36 ubuntuvm1 gnome-session[1285]: gnome-session-binary[1285]: 
WARNING: App 'spice-vdagent.desktop' exited with code 1
Jun 09 21:12:36 ubuntuvm1 gnome-session-binary[1285]: WARNING: App 
'spice-vdagent.desktop' exited with code 1
Jun 09 21:12:36 ubuntuvm1 gnome-shell[1383]: Error looking up permission: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.impl.portal.PermissionStore was not provided by any .service 
files
Jun 09 21:12:37 ubuntuvm1 gnome-shell[1383]: JS WARNING: 
[resource:///org/gnome/shell/ui/windowManager.js 1477]: reference to undefined 
property "MetaWindowXwayland"
Jun 09 21:12:37 ubuntuvm1 gnome-session-binary[1285]: Entering running state
Jun 09 21:12:37 ubuntuvm1 gsd-color[1558]: failed to get edid: unable to get 
EDID for output
Jun 09 21:12:37 ubuntuvm1 gsd-color[1558]: unable to get EDID for 
xrandr-Virtual-1: unable to get EDID for output
- snip -

Here is output of 'sudo systemctl status user-120.slice';

- snip -
● user-120.slice - User Slice of gdm
   Loaded: loaded (/run/systemd/transient/user-120.slice; transient)
Transient: yes
   Active:

[Bug 1832137] Re: The default shell theme is titled Default instead of its real name 'Yaru' or 'Adwaita'

** Summary changed:

- Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions
+ The default shell theme is titled Default instead of its real name 'Yaru' or 
'Adwaita'

** Changed in: yaru-theme (Ubuntu)
   Status: New => Triaged

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

Title:
  The default shell theme is titled Default instead of its real name
  'Yaru' or 'Adwaita'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

Thanks. That log is shorter than I expected.

Maybe something crashed in the startup process. Can you please try these
instructions?

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832137] Re: Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

Thanks for you careful considerations, Daniel.

> Because you say "there is no way to pick the other shell theme" which
is simply untrue.

I'm not quite following you here, what I mean is that when you are in
Yaru shell theme you can't pick Adwaita shell theme (that is, the other
theme in the "Adwaita/Yaru" pair mentioned in the subject) and
viceversa. Please feel free to reword it in the way you believe will
cause less confusion because I'm sincerely not understanding.

> It's less confusing for them to refer to the default theme as just
"Default".

Don't forget that there still would be a Default entry. Under Ubuntu you
would get:

Default (meaning Yaru)
...
Adwaita

Yaru


Under vanilla:

Default (meaning Adwaita)
...
Adwaita

Yaru


Although my minimal proposal was to implement only the second case, because:

1) Users opting for vanilla desktop are probably less prone to confusion
here.

2) They will be unable to use Yaru, which I consider worse than Ubuntu
session users unable to use Adwaita. In fact, I want to use a vanilla
session but I like Yaru and would like to achieve widget/shell
consistency. It's a bit ridiculous being unable to use Yaru in Ubuntu :)

3) You only have to patch a package. Better, the less "upstreamy" one,
yaru-theme.

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832144] Missing required logs.

2019-06-09 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1832144

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

** Tags added: disco

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

Title:
  Ubuntu 19.04 suspend freeze on Dell inspiron 7373

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

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

[Bug 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373

2019-06-09 Thread Carlos Cesar Caballero Diaz

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

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

Title:
  Ubuntu 19.04 suspend freeze on Dell inspiron 7373

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

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

[Bug 1832137] Re: Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

OK. Future readers of this bug might be confused though. Because you say
"there is no way to pick the other shell theme" which is simply untrue.
Please reword those statements to avoid confusing other people in
future.

While I agree with your concern here, we also need to be mindful that
upstream Gnome Shell has their own reasons for disallowing shell theming
by default.

>From the perspective of less advanced users than yourself, I think the
current design is actually going to be less confusing. Because normal
people don't know to call the current theme "Yaru" or "Adwaita". It's
less confusing for them to refer to the default theme as just "Default".

So yes I agree with your concern and I would like it resolved too, but
at the same time I can see it being beneficial for many people that this
doesn't get fixed.



** Changed in: yaru-theme (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

2019-06-09 Thread Pat

Hi Daniel,
Here is the hungboot.txt file you requested.

** Attachment added: "hungboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832138/+attachment/5269842/+files/hungboot.txt

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832153] [NEW] game-data-packager fails to download wolf3d data

2019-06-09 Thread Josh Holland

Public bug reported:

As reported upstream at https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=911788, game-data-packager version 58 attempts to
download data for Wolfenstein 3D from http://pkg-games.alioth.debian.org
/game-data/1wolf14.zip, which is no longer available since Alioth was
shut down.

This is (presumably) a regression, since when Ubuntu 18.04 was released,
Alioth was still online.

$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy game-data-packager
game-data-packager:
  Installed: 58
  Candidate: 58
  Version table:
 *** 58 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: game-data-packager 58
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: i3
Date: Mon Jun 10 03:23:57 2019
InstallationDate: Installed on 2018-08-13 (300 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: game-data-packager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: game-data-packager (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: game-data-packager (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug bionic

** Bug watch added: Debian Bug tracker #911788
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911788

** Also affects: game-data-packager (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911788
   Importance: Unknown
   Status: Unknown

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

Title:
  game-data-packager fails to download wolf3d data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/game-data-packager/+bug/1832153/+subscriptions

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

[Bug 1830662] Re: Monitor does not wake up on input after DPMS turns it off, pressing the monitor power button wakes it up

2019-06-09 Thread Douglas Silva

Tested kernel 5.2-rc2. The issue is still reproducible.

To clarify it a bit more, let me explain that this happens when the
screen turns off by inactivity (screen locks) and also when you suspend
to RAM and then resume. The monitor will not turn back on when you press
any key.

I can continue pressing keys and mouse buttons, but it will remain dark.
I turn on the monitor manually, and I see the screen locker there
showing in the password input box that I've been pressing keys while the
monitor was dark.

However, when the computer hibernates or is shut down, and you turn it
on again, the monitor will go from standby to the powered on state, as
it should.

** Description changed:

After the screen turns off (for inactivity, screen lock, etc.), mouse or
keyboard input won't bring it back. When I come back to the computer to
resume my work, I have to wake the system up, and press the power button
on the monitor. If I don't manually bring the monitor back on, the
system will resume and the screen will remain off.

I believe this is a regression, because this cannot be reproduced in
distributions as old as Debian Stretch 9. Any distribution newer than
- Debian causes this problem. This is also not reproducible on Windows 10.
+ Debian causes this problem, no matter what Desktop Environment, what
+ Display Manager or Screen Locker I choose. This is also not reproducible
+ on Windows 10.

It's worth mentioning that this desktop runs the RX 560 AMD graphics card.
Also, this is my monitor: https://www.lg.com/in/monitors/lg-22MP58VQ

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: dsilva 1883 F pulseaudio
- /dev/snd/controlC1: dsilva 1883 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: dsilva 1883 F pulseaudio
+ /dev/snd/controlC1: dsilva 1883 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon May 27 22:45:13 2019
InstallationDate: Installed on 2019-05-26 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
- enp2s0no wireless extensions.
-
- lono wireless extensions.
+ enp2s0no wireless extensions.
+
+ lono wireless extensions.
Lsusb:
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 003: ID 0951:16bc Kingston Technology
- Bus 001 Device 002: ID 0951:16d2 Kingston Technology
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 003: ID 0951:16bc Kingston Technology
+ Bus 001 Device 002: ID 0951:16d2 Kingston Technology
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B360M GAMING HD
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
- linux-restricted-modules-5.0.0-15-generic N/A
- linux-backports-modules-5.0.0-15-generic N/A
- linux-firmware1.178.1
+ linux-restricted-modules-5.0.0-15-generic N/A
+ linux-backports-modules-5.0.0-15-generic N/A
+ linux-firmware1.178.1
RfKill:
-
+
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12
dmi.board.asset.tag: Default string
dmi.board.name: B360M GAMING HD
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnB360MGAMINGHD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB360MGAMINGHD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B360M GAMING HD
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Title:
Monitor does not wake up on input after DPMS turns it off, pressing
the monitor power button wakes it up

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

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

[Bug 1832000] Re: NVidia fails everytime a new kernel update is released : nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build

I don't quite understand why this is failing to build:

  ld -r -m elf_x86_64  -z max-page-size=0x20 -T ./scripts/module-common.lds 
--build-id  -o /var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia-uvm.ko 
/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia-uvm.o 
/var/lib/dkms/nvidia-340/340.107/build/uvm/nvidia-uvm.mod.o
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-150-generic'
NVIDIA: left KBUILD.
 nvidia-uvm.ko failed to build!
Makefile:216: recipe for target 'nvidia-uvm.ko' failed
make: *** [nvidia-uvm.ko] Error 1
make: Leaving directory '/var/lib/dkms/nvidia/340-340.107/build/uvm'

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

Title:
  NVidia fails everytime a new kernel update is released : nvidia-340
  340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build

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

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

[Bug 1779817] Re: r8169 no internet after suspending

2019-06-09 Thread AceLan Kao

** Changed in: linux-oem (Ubuntu)
   Status: New => Invalid

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

Title:
  r8169 no internet after suspending

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

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

[Bug 1832137] Re: Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

I know that Daniel, that is not what I meant. The problem is that
Adwaita is not listed for an Ubuntu session and, conversely, Yaru is not
listed for a vanilla session, because both are "Default" and the meaning
of default is contextual to the session and neither of them are listed
under /usr/share/themes.

** Changed in: yaru-theme (Ubuntu)
   Status: Invalid => New

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832141] Re: Panel applets crashing on start

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

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

Title:
  Panel applets crashing on start

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

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

In order to debug this problem we would need you to reintroduce it. That
means:

1. Comment out again:

  WaylandEnable=false

2. Reboot and ensure you don't see the login screen.

3. Log in via SSH while the problem is happening and run:

   journalctl -b0 > hungboot.txt

   and send us the resulting file 'hungboot.txt'.



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

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

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1832137] Re: Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

The ability to change the shell theme is hidden behind the User Themes
extension. To do it you need to:

1. sudo apt install gnome-shell-extensions

2. In gnome-tweaks enable Extensions > User themes

3. Restart gnome-tweaks

4. gnome-tweaks > Appearance > Themes > Shell ... is now selectable.


** Changed in: yaru-theme (Ubuntu)
   Status: New => Invalid

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832138] Re: Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

** Summary changed:

- Login freeze during boot after upgrade
+ Login screen never appears on vmwgfx but setting WaylandEnable=false fixes it

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

** Also affects: gdm3 (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: vmware

** Changed in: gdm3 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Login screen never appears on vmwgfx but setting WaylandEnable=false
  fixes it

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

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

[Bug 1774002] Re: Dynamic inventory errors in 2.5.1

** Changed in: ansible
   Status: Unknown => Fix Released

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

Title:
  Dynamic inventory errors in 2.5.1

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

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

[Bug 1825096] Re: ansible: set_fact in with_items append loop only keeps last item

** Changed in: ansible
   Status: Unknown => Fix Released

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

Title:
  ansible: set_fact in with_items append loop only keeps last item

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

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

[Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04

The only hint of a problem I can see is this from the kernel log:

[ 6402.282272] usb 5-2: USB disconnect, device number 2
[ 6405.688387] usb 5-2: new low-speed USB device number 3 using xhci_hcd
[ 6405.863785] usb 5-2: New USB device found, idVendor=1241, idProduct=
[ 6405.863792] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 6405.884749] input: HID 1241: as 
/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.0/0003:1241:.0003/input/input19
[ 6405.885322] hid-generic 0003:1241:.0003: input,hidraw1: USB HID v1.00 
Mouse [HID 1241:] on usb-:00:10.0-2/input0

which is concurred by the Xorg log:

[  6402.353] (II) config/udev: removing device HID 1241:
[  6402.353] (**) Option "fd" "29"
[  6402.353] (II) event11 - HID 1241:: device removed
[  6402.361] (II) UnloadModule: "libinput"
[  6402.361] (II) systemd-logind: releasing fd for 13:75
[  6405.965] (II) config/udev: Adding input device HID 1241: 
(/dev/input/mouse2)
[  6405.965] (II) No input driver specified, ignoring this device.
[  6405.965] (II) This device may have been added with another device file.

That suggests the mouse got disconnected and reconnected after 1h46m.

Please reproduce the problem again and as soon as it happens run:

  dmesg > dmesg.txt

and send us the file 'dmesg.txt'.

Please also try a different mouse to see if that avoids the problem.

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

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

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

Title:
  Mouse unresponsive on Ubuntu 18.04

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

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

[Bug 1832106] Re: Some packages could not be installed

Can you please send us a screenshot or photo of the problem you are
experiencing?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Some packages could not be installed

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

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

[Bug 1832078] Re: two start need

It sounds like you are saying the first start fails and the second start
succeeds. If that is correct then on the second start please run:

  journalctl -b-1 > prevboot.txt

and send us the file 'prevboot.txt'.

** Tags added: radeon

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  two start need

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

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

[Bug 1832004] Re: [amdgpu] display hanging after laptop opens lid

Please:

1. Reproduce the hang again.

2. Reboot and then immediately run:

   journalctl -b-1 > prevboot.txt

   and send us the file 'prevboot.txt'.


** Summary changed:

- display hanging after laptop opens lid
+ [amdgpu] display hanging after laptop opens lid

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Tags added: amdgpu

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Incomplete

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

Title:
  [amdgpu] display hanging after laptop opens lid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1832004/+subscriptions

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

[Bug 1832151] Missing required logs.

2019-06-09 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1832151

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Unexpected CFS throttling

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

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

[Bug 1832060] Re: Backport "add an option that allows rewinds to be disabled"

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Backport "add an option that allows rewinds to be disabled"

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

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

[Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

You kernel log is showing a problem at the kernel level:

[  349.209981] iwlwifi :05:00.0: Microcode SW error detected.  Restarting 
0x200.
[  349.210223] iwlwifi :05:00.0: Start IWL Error Log Dump:
[  349.210228] iwlwifi :05:00.0: Status: 0x0100, count: 6
[  349.210231] iwlwifi :05:00.0: Loaded firmware version: 29.1044073957.0
...

Please try this:

  sudo apt update
  sudo apt install --reinstall linux-firmware gnome-bluetooth

Then reboot.

If the problem still persists then please:

1. Run:

   dpkg -l > allpackages.txt

   and send us the file 'allpackages.txt'.

2. Reproduce the problem again and then run:
   
   journalctl -b0 > curjournal.txt

   and send us the file 'curjournal.txt'.

** Changed in: bluez (Ubuntu)
   Status: New => Incomplete

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-firmware (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

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

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

[Bug 1831995] Re: Bluetooth earphone is connected but disconnected immediately.

** Tags added: a2dp

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Bluetooth earphone is connected but disconnected immediately.
+ Bluetooth earphone is connected but disconnected immediately. [Intel 3165]

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

Title:
  Bluetooth earphone is connected but disconnected immediately. [Intel
  3165]

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

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

[Bug 1831959] Re: [nouveau] The screen froze

If you can't reproduce the original problem then this bug should
expire/close. Later, if you are able to reproduce the original problem
again then please follow the steps in comment #3.

Otherwise, if you would like to discuss any other problem then please
open a new bug for that.

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

Title:
  [nouveau] The screen froze

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

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

[Bug 1831037] Re: not working list

Please ensure you only report one problem per bug report.

Which problem would you like this bug to be about?

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

Title:
  not working list

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

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

[Bug 1832151] [NEW] Unexpected CFS throttling

2019-06-09 Thread Khaled El Mously

Public bug reported:

Basically, this issue:

https://bugzilla.kernel.org/show_bug.cgi?id=198197


..is affecting a cloud provider on a 4.15 kernel.

Customer testing with a kernel that is patched with the fix (upstream:
512ac999d2755d2b7109e996a76b6fb8b888631d ) confirms that it resolves the
issue.

More details in:  https://canonical.my.salesforce.com/5003z1yUmC1

This bug is for SRU patch-tracking only.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Khaled El Mously (kmously)
 Status: New

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

Title:
  Unexpected CFS throttling

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

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

[Bug 1831514] Re: Ubuntu 19.04 system update causes boot failure

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

Eli,

Please open new bugs for the problems you are experiencing. Your
comments are confusing people.

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

Title:
  Ubuntu 19.04 system update causes boot failure

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

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

[Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)

Eli,

That's a different bug. Please open a new bug for that problem.

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

Title:
  Ubuntu login screen never appears when using the Nvidia driver (and
  setting WaylandEnable=false fixes it)

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

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

[Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

This bug is closed so if you experience any problem at all then please
open a new one.

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

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

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

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

** Tags removed: wily zesty
** Tags added: bionic

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

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

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

[Bug 1526093] Re: /usr/bin/totem:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect

Unfortunately the above link does show the crash is still happening.
Mostly in 16.04 but also in 18.04.

** Changed in: totem (Ubuntu)
   Status: Fix Released => Confirmed

** Tags removed: trusty utopic vivid
** Tags added: bionic cosmic xenial

** Tags removed: wily

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

Title:
  
/usr/bin/totem:5:doGetScreenResources:XRRGetScreenResources:update_outputs:_cogl_xlib_renderer_connect:_cogl_winsys_renderer_connect

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

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

[Bug 1832150] [NEW] Eu estou tendo problemas na instalaçâo, provavelmente eu apaguei alguma coisa quando limpei meu HD. Por favor, me ajudem.

2019-06-09 Thread David Teixeira Locks

Public bug reported:

Não sei o que posso fazer, sou um usuário leigo.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  9 22:26:54 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=pt_BR.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu

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

Title:
  Eu estou tendo problemas na instalaçâo, provavelmente eu apaguei
  alguma coisa quando limpei meu HD. Por favor, me ajudem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1832150/+subscriptions

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

[Bug 1780278] Re: ansible 2.5.1 need upgrade to 2.5.2 or 2.5.3 (bug with set_facts)

The append to list bug is also reported in 1825096, but this bug report
can focus on the upstream issue
https://github.com/ansible/ansible/issues/54618 that's from 2.5.3.


** Also affects: ansible via
   https://github.com/ansible/ansible/issues/54618
   Importance: Unknown
   Status: Unknown

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

Title:
  ansible 2.5.1 need upgrade to 2.5.2 or 2.5.3 (bug with set_facts)

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

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

[Bug 1774002] Re: Dynamic inventory errors in 2.5.1

** Bug watch added: github.com/ansible/ansible/issues #39007
   https://github.com/ansible/ansible/issues/39007

** Also affects: ansible via
   https://github.com/ansible/ansible/issues/39007
   Importance: Unknown
   Status: Unknown

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

Title:
  Dynamic inventory errors in 2.5.1

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

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

[Bug 1757280] Re: Night Light only works on one Monitor

2019-06-09 Thread kinghat

have this issue with 18.04.2 with my 3 identical monitors.

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

Title:
  Night Light only works on one Monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1757280/+subscriptions

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

[Bug 1825096] Re: ansible: set_fact in with_items append loop only keeps last item

** Bug watch added: github.com/ansible/ansible/issues #38991
   https://github.com/ansible/ansible/issues/38991

** Also affects: ansible via
   https://github.com/ansible/ansible/issues/38991
   Importance: Unknown
   Status: Unknown

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

Title:
  ansible: set_fact in with_items append loop only keeps last item

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

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

[Bug 1818920] Re: Snap without icons use old asset

This bug was fixed in the package gnome-software - 3.30.6-2ubuntu6

---
gnome-software (3.30.6-2ubuntu6) eoan; urgency=medium

  * debian/patches/0016-snap-Use-default-icon-if-none-provided.patch:
- Update default snap icon (LP: #1818920)

 -- Robert Ancell   Mon, 10 Jun 2019
12:02:12 +1200

** Changed in: gnome-software (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Snap without icons use old asset

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

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

[Bug 1832149] [NEW] USB Installer

2019-06-09 Thread Kristopher Ali

Public bug reported:

I am installing Ubuntu onto a USB (PNY 32GB - no partitions, until the
installer changed it) from another USB (Sandisk 32GB) that contains the
ISO extracted with Rufus.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
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
CasperVersion: 1.405
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  9 20:53:35 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu

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

Title:
  USB Installer

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

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

[Bug 1661745] Re: ssh-keyscan does not exit with non-zero return code on error

** Changed in: openssh (Debian)
   Status: Confirmed => Fix Released

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

Title:
  ssh-keyscan does not exit with non-zero return code on error

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

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

[Bug 1832145] Re: X.org freeze after selecting nvidia profile

2019-06-09 Thread Luca Mastromatteo

To be more clear, it looks like what actually freezes is the plasma panel 
itself, you could always use the alt+tab hotkey to switch programs
You could also restart plasmashell. It happens right when the Nvidia module got 
loaded before logging off

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

Title:
  X.org freeze after selecting nvidia profile

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

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

[Bug 1523212] Re: unhelpful error message "giblib error: Saving to file [file] failed"

2019-06-09 Thread Eriberto

Fixed at https://github.com/resurrecting-open-source-
projects/scrot/commit/18803a68f6c1af61912bb02f0acb3c1a37475d85

** Changed in: scrot (Ubuntu)
   Status: New => Fix Committed

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

Title:
  unhelpful error message "giblib error: Saving to file [file] failed"

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

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

[Bug 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373

2019-06-09 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1832144/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

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

Title:
  Ubuntu 19.04 suspend freeze on Dell inspiron 7373

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

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

[Bug 1698375] Re: Capture mouse pointer ?

2019-06-09 Thread Eriberto

Fixed in https://github.com/resurrecting-open-source-
projects/scrot/commit/755f29de94c09721f953635151de6bd5fa53c06b

** Changed in: scrot (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Capture mouse pointer ?

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

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

[Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

2019-06-09 Thread VanVan

A new BIOS version (304) was released for the UX433FN that fix the
problem !

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

Title:
  Linux 5.0 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

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

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

[Bug 1824632] Re: Linux 5 regression causes no video out on some laptops in 19.04 beta

2019-06-09 Thread VanVan

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

A new BIOS version (304) was released for the UX433FN that fix the
problem

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

Title:
  Linux 5 regression causes no video out on some laptops in 19.04 beta

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

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

[Bug 1831341] Re: package libreoffice-common 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: unable to stat './usr/share/icons/locolor/32x32/mimetypes/libreoffice-oasis-drawing.png' (which I w

2019-06-09 Thread Tilmann Rückauer

Hi Marcus,

please excuse the latency of my response. Had to work.

In the meanwhile, I changed the partition size of the root and home
partitions, allocating more space to root, since there was not enough
free space left for the download of system updates. In that process,
qparted checked the fs. The partitions are named differently
(mmcblk0p2=sdf2), since I took the micro-SD card out of the BanananPi
and plugged it into my PC in order to work on the unmounted partitions.
Here is the report:

GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2

Dateisystem (ext4) auf /dev/sdf2 überprüfen und reparieren  00:00:12( 
ERFOLG )

/dev/sdf2 kalibrieren  00:00:01( ERFOLG )

Pfad: /dev/sdf2 (Partition)
Anfang: 729088
Ende: 23656447
Größe: 22927360 (10.93 GiB)
Dateisystem auf /dev/sdf2 auf Fehler überprüfen und (falls möglich) diese 
beheben  00:00:11( ERFOLG )

e2fsck -f -y -v -C 0 '/dev/sdf2'  00:00:11( ERFOLG )

Durchgang 1: Inodes, Blöcke und Größen werden geprüft
Durchgang 2: Verzeichnisstruktur wird geprüft 
Durchgang 3: Verzeichnisverknüpfungen werden geprüft 
Durchgang 4: Referenzzähler werden überprüft
Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft

225176 Inodes sind in Benutzung (31.48% von 715264)
275 nicht zusammenhängende Dateien (0.1%)
241 nicht zusammenhängende Verzeichnisse (0.1%)
# von Inodes mit ind/dind/tind Blöcken: 0/0/0
Histogramm der Tiefe von Erweiterungen: 178544/89
1335296 Blöcke werden benutzt (46.59% von 2865920)
0 defekte Blöcke
1 große Datei

157743 reguläre Dateien
19071 Verzeichnisse
54 zeichenorientierte Gerätedateien
25 Blockgerätedateien
0 Fifos
32 Verknüpfungen
48273 symbolische Verknüpfungen (46454 schnelle symbolische Verknüpfungen)
1 Socket

225199 Dateien
e2fsck 1.44.1 (24-Mar-2018)
Dateisystem bis zum Auffüllen der Partition vergrößern  00:00:00( ERFOLG )

resize2fs -p '/dev/sdf2'  00:00:00( ERFOLG )

resize2fs 1.44.1 (24-Mar-2018)
Das Dateisystem ist bereits 2865920 (4k) Blöcke lang. Nichts zu tun!


After this was done, I tried to run the command you suggested. Again, I worked 
on my PC with the micro-SD card plugged in: 

ty@tilmann-yvonne-Rechenknecht:~$ mount
[...]
/dev/sdf1 on /media/ty/BPI-BOOT type vfat 
(rw,nosuid,nodev,relatime,uid=1000,gid=1000,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,flush,errors=remount-ro,uhelper=udisks2)
/dev/sdf2 on /media/ty/BPI-ROOT type ext4 
(rw,nosuid,nodev,relatime,block_validity,delalloc,barrier,user_xattr,acl,stripe=1024,uhelper=udisks2)
/dev/sdf3 on /media/ty/c54307ab-fcbe-4450-af13-a75bf85ede49 type ext2 
(rw,nosuid,nodev,relatime,block_validity,barrier,user_xattr,acl,uhelper=udisks2)
ty@tilmann-yvonne-Rechenknecht:~$ sudo umount /dev/sdf1
ty@tilmann-yvonne-Rechenknecht:~$ sudo umount /dev/sdf2
ty@tilmann-yvonne-Rechenknecht:~$ sudo umount /dev/sdf3
ty@tilmann-yvonne-Rechenknecht:~$ sudo fsck.ext4 /dev/sdf2
e2fsck 1.44.1 (24-Mar-2018)
BPI-ROOT: sauber, 224654/715264 Dateien, 1334265/2865920 Blöcke
ty@tilmann-yvonne-Rechenknecht:~$ sudo fsck.ext4 /dev/sdf3
e2fsck 1.44.1 (24-Mar-2018)
/dev/sdf3: sauber, 2831/1204224 Dateien, 432951/4809472 Blöcke
ty@tilmann-yvonne-Rechenknecht:~$ sudo fsck.vfat /dev/sdf1
fsck.fat 4.1 (2017-01-24)
/dev/sdf1: 261 files, 53297/65467 clusters
ty@tilmann-yvonne-Rechenknecht:~$ sudo fsck.ext4 -f /dev/sdf2
[sudo] Passwort für ty: 
e2fsck 1.44.1 (24-Mar-2018)
Durchgang 1: Inodes, Blöcke und Größen werden geprüft
Durchgang 2: Verzeichnisstruktur wird geprüft
Durchgang 3: Verzeichnisverknüpfungen werden geprüft
Durchgang 4: Referenzzähler werden überprüft
Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft
BPI-ROOT: 224654/715264 Dateien (0.2% nicht zusammenhängend), 1334265/2865920 
Blöcke
ty@tilmann-yvonne-Rechenknecht:~$ sudo fsck.ext4 -f /dev/sdf3
e2fsck 1.44.1 (24-Mar-2018)
Durchgang 1: Inodes, Blöcke und Größen werden geprüft
Durchgang 2: Verzeichnisstruktur wird geprüft
Durchgang 3: Verzeichnisverknüpfungen werden geprüft
Durchgang 4: Referenzzähler werden überprüft
Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft
/dev/sdf3: 2831/1204224 Dateien (20.6% nicht zusammenhängend), 432951/4809472 
Blöcke

Then I realized, that sdf3 was not ext4 but ext2. So I repeated the last
command with the correct file system:

ty@tilmann-yvonne-Rechenknecht:~$ sudo fsck.ext2 -f /dev/sdf3
e2fsck 1.44.1 (24-Mar-2018)
Durchgang 1: Inodes, Blöcke und Größen werden geprüft
Durchgang 2: Verzeichnisstruktur wird geprüft
Durchgang 3: Verzeichnisverknüpfungen werden geprüft
Durchgang 4: Referenzzähler werden überprüft
Durchgang 5: Zusammengefasste Gruppeninformation wird geprüft
/dev/sdf3: 2831/1204224 Dateien (20.6% nicht zusammenhängend), 432951/4809472 
Blöcke


So, this didn't change anything (I had done no damage when using the wrong file 
system). There were no corrupt parts to repair, maybe qparted had already taken 
care of this.

[Bug 314147] Re: [Upstream] Calc can't load a *.wb3 file

2019-06-09 Thread Christopher M. Penalver

Resolved in as early as:
Version: 6.2.4.2 (x64)
Build ID: 2412653d852ce75f65fbfa83fb7e7b669a126d64

** Changed in: libreoffice (Ubuntu)
   Status: Won't Fix => Fix Released

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

Title:
  [Upstream] Calc can't load a *.wb3 file

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/314147/+subscriptions

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

[Bug 1820130] Re: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1

2019-06-09 Thread Jan

Hi Timo, is this package the same that was in Graham PPA
https://launchpad.net/~ginggs/+archive/ubuntu/sru? I've already tested
it and it fixes the bug.

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

Title:
  [SRU] modem-manager-gui fails to start after modemmanager is upgraded
  to 1.10.0-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions

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

[Bug 1832138] Re: Login freeze during boot after upgrade

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
   Status: New => Confirmed

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

Title:
  Login freeze during boot after upgrade

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

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

[Bug 1828613] Re: [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver engaged

2019-06-09 Thread grn

Facing the same.

My sound module is a VIA VT1708S on an Asus mobo(M5A78L-M/USB3)
Facing the same.

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

Title:
  [Realtek ALC889, Green Line Out, Rear] Popping sound when audio driver
  engaged

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

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

[Bug 1832145] [NEW] X.org freeze after selecting nvidia profile

2019-06-09 Thread Luca Mastromatteo

Public bug reported:

- Using ubuntu 18.04.2 LTS.
- Tried driver NVIDIA 390 + 430 from the repo, same result
- KDE Plasma desktop

Reproducibility: 75%

Steps required:
- Installing nvidia drivers on an optimus laptop
- Rebooting
- Select NVIDIA GPU with prime from Intel
- Waiting some seconds

Bug observed: 
- Before the nvidia module gets loaded (I could type lsmod | grep nvidia fine 
and no module is loaded after the first 3 seconds) 
- When (presumably) the nvidia driver is loaded, the X.org session locks up. 
The mouse cursor can move things, but cannot click anything, everything else on 
the screen is frozen up

Workaround: Killing the X.org session gives an usable graphical system

Notes: If the session ends (doing a logout so SDDM) there is no lockup
at all, but once the nvidia driver is loaded, it looks like it's when
the issue appears.

I recently moved from 19.04 to 18.04.2 LTS, and I don't remember this
issue happening at all, is that some fix that needs to be backported?

** Affects: nvidia-prime (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  X.org freeze after selecting nvidia profile

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

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

[Bug 1832144] [NEW] Ubuntu 19.04 suspend freeze on Dell inspiron 7373

2019-06-09 Thread Carlos Cesar Caballero Diaz

Public bug reported:

I have installed Ubuntu 19.04 in my Dell Inspiron 7373 and I am getting
issues with suspend. When I lock the case or write the "systemctl
suspend" command, the screen turn off, the system freeze and the laptop
keeps turned on. I need to force the laptop turn off and on again. There
are some cases when it suspends without issues, but most of the time it
freezes.

There are some workarounds for issues like this one but they are mostly
for laptops using nvidia graphics.

I am not sure how to provide debug information about this issue, but I
can give it if someone tells me how to do it.

"lsb_release -rd" output:
Description:Ubuntu 19.04
Release:19.04

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 19.04 suspend freeze on Dell inspiron 7373

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

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

[Bug 218741] Re: scp cuts UTF8 filenames by bytes instead of characters

2019-06-09 Thread Colin Watson

I did some experimentation today with different "stty cols" settings,
and I'm pretty sure this is fixed.  I believe that the commit that fixed
it was probably
https://anongit.mindrot.org/openssh.git/commit/?id=0e059cdf5fd86297546c63fa8607c24059118832
(note in particular "take character display widths into account for the
progressmeter", in which case this has been fixed since OpenSSH 7.3p1,
so since Ubuntu 16.10.

** Changed in: openssh (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  scp cuts UTF8 filenames by bytes instead of characters

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

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

[Bug 1706630] Re: aarch64: MSI is not supported by interrupt controller

2019-06-09 Thread RussianNeuroMancer

Getting same issue with both of libvirt 4.0.0/qemu 2.11 (18.04.2) and
libvirt 5.0.0/qemu 3.1 (19.04) on attempt to run AArch64 guest on
AArch64 host. Virtual machine setting is default generated by virt-
manager wizard, so there is no big changes to default devices, I just
filled iso, hdd and network bridge.

Is there something I missing?

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

Title:
  aarch64: MSI is not supported by interrupt controller

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

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

[Bug 1706630] Re: aarch64: MSI is not supported by interrupt controller

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libvirt (Ubuntu)
   Status: New => Confirmed

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

Title:
  aarch64: MSI is not supported by interrupt controller

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

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

[Bug 1804542] Re: [SRU] Multiple intermittent socket failures during name resolutions

** Tags added: server-next

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

Title:
  [SRU] Multiple intermittent socket failures during name resolutions

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

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

[Bug 1784757] Re: rabbitmq-server does not properly shutdown

Alex, thanks for looking up the Debian upstream situation, this is
looking a lot more actionable so am re-adding it to server-next.

Sounds like if we just picked the two changes to the service file from
the debian commits, those would solve the problem?  If so, that should
be straightforward to SRU.


** Tags added: server-next

** Changed in: rabbitmq-server (Ubuntu)
   Status: Incomplete => Triaged

** Also affects: rabbitmq-server (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: rabbitmq-server (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Description changed:

- When I run `systemctl restart rabbitmq-server` it waits for 90 seconds
- then systemd sends SIGKILL to it.
+ [Impact]
+ TBD
+ 
+ [Test Case]
+ TBD
+ 
+ [Regression Potential]
+ TBD
+ 
+ [Fix]
+ TBD
+ 
+ The fix is available upstream in Debian as of 3.7.6, so would need
+ backported for bionic and cosmic:
+ 
+  rabbitmq-server | 3.5.7-1| xenial  | source, all
+  rabbitmq-server | 3.6.10-1   | bionic  | source, all
+  rabbitmq-server | 3.6.10-1   | cosmic  | source, all
+  rabbitmq-server | 3.7.8-4ubuntu2 | disco   | source, all
+  rabbitmq-server | 3.7.8-4ubuntu2 | eoan| source, all
+ 
+ [Discussion]
+ TBD
+ 
+ [Original Report]
+ When I run `systemctl restart rabbitmq-server` it waits for 90 seconds then 
systemd sends SIGKILL to it.
  
  Presumably the `epmd` process does not receive SIGTERM, since if I run
  `kill 1493` (or whatever pid it currently is) then restart happens
  straight after that successfully
  
  ● rabbitmq-server.service - RabbitMQ Messaging Server
-Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; 
vendor preset: enabled)
-Active: deactivating (final-sigterm) since Wed 2018-08-01 01:17:04 UTC; 7s 
ago
-   Process: 1183 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, 
status=0/SUCCESS)
-   Process: 178 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait 
(code=exited, status=0/SUCCESS)
-   Process: 177 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
-  Main PID: 177 (code=killed, signal=TERM)
- Tasks: 1 (limit: 4915)
-CGroup: /system.slice/rabbitmq-server.service
-└─1493 /usr/lib/erlang/erts-9.2/bin/epmd -daemon
+    Loaded: loaded (/lib/systemd/system/rabbitmq-server.service; enabled; 
vendor preset: enabled)
+    Active: deactivating (final-sigterm) since Wed 2018-08-01 01:17:04 UTC; 7s 
ago
+   Process: 1183 ExecStop=/usr/sbin/rabbitmqctl stop (code=exited, 
status=0/SUCCESS)
+   Process: 178 ExecStartPost=/usr/lib/rabbitmq/bin/rabbitmq-server-wait 
(code=exited, status=0/SUCCESS)
+   Process: 177 ExecStart=/usr/sbin/rabbitmq-server (code=killed, signal=TERM)
+  Main PID: 177 (code=killed, signal=TERM)
+ Tasks: 1 (limit: 4915)
+    CGroup: /system.slice/rabbitmq-server.service
+    └─1493 /usr/lib/erlang/erts-9.2/bin/epmd -daemon
  
  Aug 01 01:11:20 rmq-1 systemd[1]: rabbitmq-server.service: Failed to reset 
devices.list: Operation not permitted
  Aug 01 01:11:20 rmq-1 systemd[1]: Starting RabbitMQ Messaging Server...
  Aug 01 01:11:25 rmq-1 rabbitmq[178]: Waiting for 'rabbit@rmq-1'
  Aug 01 01:11:25 rmq-1 rabbitmq[178]: pid is 204
  Aug 01 01:11:30 rmq-1 systemd[1]: Started RabbitMQ Messaging Server.
  Aug 01 01:17:04 rmq-1 systemd[1]: Stopping RabbitMQ Messaging Server...
  Aug 01 01:17:06 rmq-1 rabbitmq[1183]: Stopping and halting node 'rabbit@rmq-1'

** Changed in: rabbitmq-server (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: rabbitmq-server (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: rabbitmq-server (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: rabbitmq-server (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: rabbitmq-server (Ubuntu)
   Status: Triaged => Fix Released

** Summary changed:

- rabbitmq-server does not properly shutdown
+ [SRU] rabbitmq-server does not properly shutdown

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

Title:
  [SRU] rabbitmq-server does not properly shutdown

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

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

[Bug 1798167] Re: Does not evaluate defined variables

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: wxmaxima (Ubuntu)
   Status: New => Confirmed

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

Title:
  Does not evaluate defined variables

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

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

[Bug 1832137] Re: Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

One additional consideration. Maybe one answer to my request could be:
Ubuntu desktop is opinionated, provide a few extensions and restricted
customization options, you're not supposed to change the gtk widget
theme, let alone the shell theme for mere consistency with widgets, and
if you want to do that, well you have already found a workaround. And I
would agree. But then there is this other aspect: not allowing vanilla
Gnome users to set Yaru, of all themes, as their shell theme, would be
perplexing given the status of Yaru as emblematic of Ubuntu. So, short
of having it both ways, I would still propose to let vanilla sessions
set Yaru as the shell theme, that is:

ln -s /usr/share/gnome-shell/theme/Yaru /usr/share/themes/Yaru
/gnome-shell

This also has the advantage that only the yaru-theme package has to be
modified.

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0

2019-06-09 Thread Eric-Pierre Fabre

Hi all,
I have the same issue with a dell laptop Inspiron 15.
Step to reproduce:
Plug HDMI cable 4k ready, of course connected to 4k screen.

Actual result:
Purpul screen (default color of my background) on both screen...
To have any things displayed I need to use CTRL + ALT + F1.

Expected result:
Desktop extended to 4k screen.

Setup:
4.18.0-20-generic #21~18.04.1-Ubuntu SMP Wed May 8 08:43:37 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

If more information are needed, ask please.
BR
Eric

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

Title:
  spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-
  ports/com.redhat.spice.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions

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

[Bug 1810239] Re: amd_iommu conflict with Marvell 88SE9230 SATA Controller

2019-06-09 Thread Christopher M. Penalver

Johannes (piktogrammdd+ubuntu), it will help immensely if you use Ubuntu with 
the computer the problem is reproducible with and file a new report via a 
terminal to provide necessary debugging logs:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: latest-bios-f2
** Tags added: bios-outdated-f.40

** Tags added: needs-upstream-testing

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

Title:
  amd_iommu conflict with  Marvell 88SE9230 SATA Controller

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

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

[Bug 1832141] [NEW] Panel applets crashing on start

2019-06-09 Thread holiday

Public bug reported:

 
SEveral panel applets on both top and right panels. Workspace switcher and text 
output applets raise error dialog on GUI session start. MATE.

This does not happen to all text output applets and not always the same
ones. But the workspace switcher (set to 3x3 table) has become
consistent in the last few days.

The journal has the following error


The program 'wnck-applet' received an X Window System error.
This probably reflects a bug in the 
program.
The error was 'RenderBadPicture 
(invalid Picture parameter)'.
  (Details: serial 4910 error_code 143 
request_code 139 (RENDER) minor_code 7)
  (Note to programmers: normally, X 
errors are reported asynchronously;
   that is, you will receive the error 
a while after causing it.
   To debug your program, run it with 
the GDK_SYNCHRONIZE environment
   variable to change this behavior. 
You can then get a meaningful
   backtrace from your debugger if you 
break on the gdk_x_error() function.)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Jun  9 12:39:06 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 5.0.0-16-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed
 virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1080]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
InstallationDate: Installed on 2019-04-25 (45 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUSTeK COMPUTER INC. N501VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic 
root=UUID=7a6ead44-b94a-4058-8c40-fda725ccedba ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N501VW.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N501VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.304:bd11/28/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N501VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  Panel applets crashing on start

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

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

[Bug 1832048] Re: hinic: fix oops due to race in set_rx_mode

2019-06-09 Thread dann frazier

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

Title:
  hinic: fix oops due to race in set_rx_mode

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

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

[Bug 1790979] Re: Unable to change disk decryption passphrase

2019-06-09 Thread Jonathan Baldwin

** Also affects: gnome-disk-utility (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  Unable to change disk decryption passphrase

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

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

[Bug 1815475] Re: libevent-rpc-perl FTBFS in bionic, expired test certs

** Changed in: libevent-rpc-perl (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  libevent-rpc-perl FTBFS in bionic, expired test certs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libevent-rpc-perl/+bug/1815475/+subscriptions

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

[Bug 1826065] Re: Can't boot from usb live system to install disco dingo 19.04

2019-06-09 Thread VanVan

The new BIOS version works for me also !

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

Title:
  Can't boot from usb live system to install disco dingo 19.04

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

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

[Bug 1832138] [NEW] Login freeze during boot after upgrade

2019-06-09 Thread Pat

Public bug reported:

I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare
Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook
Pro.

I've been running this Ubuntu 18.04.2 VM without problem for many months 
without problem.
Yesterday, I did 'sudo apt update; sudo apt upgrade'.  Upon rebooting, the 
system hangs immediately after displaying the splash screen.  I never see a 
login screen.  And I can't use Ctrl+Alt+F2 to navigate to a console/tty login.

I can SSH into the system however.

I've found that I can work around the hang/freeze if I uncomment the following 
line in /etc/gdm3/custom.conf;
#WaylandEnable=false

After uncommenting the WaylandEnable=false line and rebooting, then I
see the login prompt as expected and I can then log in and use the
system normally again.

After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as
shown in this 'uname -a' output;

Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a output;

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompositorRunning: None
Date: Sun Jun  9 12:38:37 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2018-05-06 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: VMware, Inc. VMware Virtual Platform
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Login freeze during boot after upgrade

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

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

[Bug 1832137] Re: Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

** Description changed:

  In an ubuntu session the default shell theme is Yaru. In a vanilla gnome
  session the default shell theme is Adwaita. In both cases, there is no
  way to pick the other shell theme. Of course, I agree with the defaults,
  but arguably one might be interested in using Yaru in a vanilla gnome
  session and viceversa. Plus, the ability to change the gtk theme to
  Adwaita in an ubuntu session is crippled by the inability to also change
  the shell theme in a consistent way (and viceversa).
  
  The problem is that these themes get installed under /usr/share/gnome-
  shell/theme and not under /usr/share/themes//gnome-shell as is
  usually the case with every other third party theme. But it's simple to
  fix this in order to allow for selecting the alternative theme: symlink
  from /usr/share/themes/. For example:
  
- ln -s /usr/share/gnome-shell/theme/Yaru /usr/share/themes/Yaru
+ ln -s /usr/share/gnome-shell/theme/Yaru /usr/share/themes/Yaru
  /gnome-shell
  
+ ln -s /usr/share/gnome-shell/theme /usr/share/themes/Adwaita/gnome-
+ shell
  
- The only downside I see is that you will have Yaru as an alias to Default 
under an ubuntu session and Adwaita as an alias to Default under a vanilla 
session. That is, two options in the dropdown will refer to the same underlying 
theme. But this seems quite innocuous to me, specially for a user that has 
already made his/her way into Tweaks and theme customization. And arguably 
having an explicitly named option and a default option may even be desirable.
+ The only downside I see is that you will have Yaru as an alias to
+ Default under an ubuntu session and Adwaita as an alias to Default under
+ a vanilla session. That is, two options in the dropdown will refer to
+ the same underlying theme. But this seems quite innocuous to me,
+ specially for a user that has already made his/her way into Tweaks and
+ theme customization. And arguably having an explicitly named option and
+ a default option may even be desirable.

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1832137] [NEW] Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

Public bug reported:

In an ubuntu session the default shell theme is Yaru. In a vanilla gnome
session the default shell theme is Adwaita. In both cases, there is no
way to pick the other shell theme. Of course, I agree with the defaults,
but arguably one might be interested in using Yaru in a vanilla gnome
session and viceversa. Plus, the ability to change the gtk theme to
Adwaita in an ubuntu session is crippled by the inability to also change
the shell theme in a consistent way (and viceversa).

The problem is that these themes get installed under /usr/share/gnome-
shell/theme and not under /usr/share/themes//gnome-shell as is
usually the case with every other third party theme. But it's simple to
fix this in order to allow for selecting the alternative theme: symlink
from /usr/share/themes/. For example:

ln -s /usr/share/gnome-shell/theme/Yaru /usr/share/themes/Yaru
/gnome-shell

ln -s /usr/share/gnome-shell/theme /usr/share/themes/Adwaita/gnome-
shell

The only downside I see is that you will have Yaru as an alias to
Default under an ubuntu session and Adwaita as an alias to Default under
a vanilla session. That is, two options in the dropdown will refer to
the same underlying theme. But this seems quite innocuous to me,
specially for a user that has already made his/her way into Tweaks and
theme customization. And arguably having an explicitly named option and
a default option may even be desirable.

** Affects: yaru-theme (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Switch Adwaita/Yaru shell themes under vanilla/ubuntu gnome sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1832137/+subscriptions

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

[Bug 1829671] Re: alt tab + shift alt tab does something interesting

2019-06-09 Thread klfyt

Might be this instead:
https://bugzilla.redhat.com/show_bug.cgi?id=1693960#c44

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

Title:
  alt tab + shift alt tab does something interesting

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

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

[Bug 1764461] Re: dkopp crashed with SIGABRT in beroot()

2019-06-09 Thread Caleb McKay

Seeing the same errors. This app was updated by the developer and source
posted on his/her website. See
https://kornelix.net/downloads/downloads.html. Everything about this
package is out of date, including the link to the developer's website. I
download the source and built my own .deb and installed. Can confirm the
updated version works fine on Ubuntu 19.04.

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

Title:
  dkopp crashed with SIGABRT in beroot()

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

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

[Bug 1764461] Re: dkopp crashed with SIGABRT in beroot()