[Bug 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]

2019-04-30 Thread Treviño
** Changed in: gnome-shell (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  [regression] gnome-shell crashes if booted with the monitor off ["JS
  ERROR: TypeError: monitor is null" from
  _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]

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

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

[Bug 1719213] Re: Please update percona-xtradb-cluster to version 5.7

2019-04-30 Thread Trent Lloyd
Setting Invalid for Xenial, as by policy Ubuntu updates do not generally
update software from one major version to another.

Bug was originally for OpenStack, on Bionic we now have PXC 5.7

** Changed in: percona-xtradb-cluster-5.6 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Please update percona-xtradb-cluster to version 5.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-percona-cluster/+bug/1719213/+subscriptions

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

[Bug 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]

2019-04-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/38

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

Title:
  [regression] gnome-shell crashes if booted with the monitor off ["JS
  ERROR: TypeError: monitor is null" from
  _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]

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

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

[Bug 1826797] Re: [regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]

2019-04-30 Thread Treviño
** Also affects: gnome-shell (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu Disco)
   Status: New => In Progress

** Changed in: gnome-shell (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: gnome-shell (Ubuntu Disco)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Description changed:

+ [ Impact ]
+ 
  gnome-shell crashes if booted with the monitor off. This leaves me with
  just a black screen and flashing cursor when I turn the monitor on.
+ 
+ [ Test Case ]
+ 
+ Boot ubuntu with the monitor off, turn on the monitor.
+ GNOME-Shell should run properly with no errors
+ 
+ [ Regression potential ]
+ 
+ Mouse cursor isn't scaled properly when using the a11y magnifier
+ 
+ 
  
  Apr 29 09:31:02 kab gnome-shell[995]: JS ERROR: TypeError: monitor is null
    
_updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9
    
Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9
    
_initializeUI@resource:///org/gnome/shell/ui/main.js:170:17
    
start@resource:///org/gnome/shell/ui/main.js:127:5
    @:1:31
  Apr 29 09:31:02 kab gnome-shell[995]: Execution of main.js threw exception: 
Script  threw an exception
  Apr 29 09:31:02 kab org.gnome.Shell.desktop[995]: (EE) failed to read Wayland 
events: Connection reset by peer
  Apr 29 09:31:03 kab gnome-shell[1076]: JS ERROR: TypeError: monitor is null
     
_updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9
     
Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9
     
_initializeUI@resource:///org/gnome/shell/ui/main.js:170:17
     
start@resource:///org/gnome/shell/ui/main.js:127:5
     @:1:31
  Apr 29 09:31:03 kab gnome-shell[1076]: Execution of main.js threw exception: 
Script  threw an exception
  Apr 29 09:31:03 kab gnome-shell[1094]: JS ERROR: TypeError: monitor is null
     
_updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9
     
Magnifier@resource:///org/gnome/shell/ui/magnifier.js:160:9
     
_initializeUI@resource:///org/gnome/shell/ui/main.js:170:17
     
start@resource:///org/gnome/shell/ui/main.js:127:5
     @:1:31
  Apr 29 09:31:03 kab gnome-shell[1094]: Execution of main.js threw exception: 
Script  threw an exception
  
- ProblemType: Bug
- DistroRelease: Ubuntu 19.04
+ ProblemType: BugDistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-14.15-generic 5.0.6
  Uname: Linux 5.0.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Mon Apr 29 09:33:16 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-04 (145 days ago)
- InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203)
- SourcePackage: gnome-shell
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 
(20181203)SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [regression] gnome-shell crashes if booted with the monitor off ["JS
  ERROR: TypeError: monitor is null" from
  _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]

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

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

[Bug 1826201] Re: Green vertical bars when using gstreamer-vaapi in Totem under Xorg

2019-04-30 Thread Daniel van Vugt
OK, I can reproduce the bug now. Only in Xorg sessions and not Wayland.

Although performance isn't great even when it is working so I strongly
recommend using 'mpv' to play your videos instead. mpv will give you
smoother playback with lower CPU.

** Summary changed:

- Green vertical bars when using gstreamer-vaapi in Totem
+ Green vertical bars when using gstreamer-vaapi in Totem under Xorg

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

Title:
  Green vertical bars when using gstreamer-vaapi in Totem under Xorg

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

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

[Bug 1826506] Re: Test

2019-04-30 Thread Daniel van Vugt
Thanks!

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

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

Title:
  Test

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

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

[Bug 1826201] Re: Green vertical bars when using gstreamer-vaapi in Totem under Xorg

2019-04-30 Thread Daniel van Vugt
Also gst-play-1.0 seems to work fine, and that does use gstreamer-vaapi.

So maybe the bug here is more Totem-specific in package
'gstreamer1.0-clutter-3.0'?

** Also affects: clutter-gst-3.0 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: clutter-gst-3.0 (Ubuntu)
   Status: New => Triaged

** Changed in: clutter-gst-3.0 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Green vertical bars when using gstreamer-vaapi in Totem under Xorg

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

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

[Bug 1827174] Missing required logs.

2019-04-30 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 1827174

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

Title:
  Sound: ASoC: sof: support Internal DMIC which directly connects to PCH

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827174/+subscriptions

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

[Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide

2019-04-30 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1696788.

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


On 2019-04-05T16:04:51+00:00 mkrajnak wrote:

Description of problem:
I am getting those messages while running yelp in 7.7, I am not seeing them on 
RHEL-8 with X session

Version-Release number of selected component (if applicable):
yelp-libs-3.28.1-1.el7.x86_64
yelp-xsl-3.28.0-1.el7.noarch
yelp-3.28.1-1.el7.x86_64
yelp-tools-3.28.0-1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1.Run yelp from terminal
2.Click on getting started with Gnome

Actual results:
[test@localhost ~]$ yelp
failed to create drawable
Xlib: sequence lost (0x100cd > 0xcf) in reply type 0x0!
Xlib: sequence lost (0x100cb > 0xcf) in reply type 0x0!
Xlib: sequence lost (0x100d2 > 0xd6) in reply type 0x0!
Xlib: sequence lost (0x100d9 > 0xdd) in reply type 0x0!
Xlib: sequence lost (0x100e0 > 0xe4) in reply type 0x0!
Xlib: sequence lost (0x100e7 > 0xeb) in reply type 0x0!
Xlib: sequence lost (0x100ee > 0xf2) in reply type 0x0!
Xlib: sequence lost (0x100f5 > 0xf7) in reply type 0x0!
Xlib: sequence lost (0x100fa > 0xfc) in reply type 0x0!


Expected results:
no err messages

Additional info:

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-
started-docs/+bug/1804786/comments/9


On 2019-04-05T16:10:09+00:00 mkrajnak wrote:

Also something like this, not sure if those indicating some errors as well
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating bg color
Recursion depth exceeded calculating fg color
Recursion depth exceeded calculating bg color

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-
started-docs/+bug/1804786/comments/10


** Changed in: yelp
   Status: Unknown => Confirmed

** Changed in: yelp
   Importance: Unknown => Medium

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

Title:
  Garbage occurred when Playing the video in the Ubuntu Desktop Guide

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

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

[Bug 1827174] Re: Sound: ASoC: sof: support Internal DMIC which directly connects to PCH

2019-04-30 Thread Hui Wang
** Tags added: dell originate-from-1821270 originate-from-1826181

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

Title:
  Sound: ASoC: sof: support Internal DMIC which directly connects to PCH

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827174/+subscriptions

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

[Bug 1827175] [NEW] armv8l-unknown-linux-gnueabihf triplet from clang -dumpmachine on ARMv7l

2019-04-30 Thread Jeffrey Walton
Public bug reported:

I'm working on a Tritium ARMv7 dev board
(https://www.amazon.com/gp/product/B07D4L7GXZ). It has a Cortex-A7
(https://libre.computer/products/boards/all-h3-cc/).

I'm testing native build of a package using Clang.

GCC provides the following triplet:

$ gcc -dumpmachine
arm-linux-gnueabihf

Clang provides the following triplet:

$ clang -dumpmachine
armv8l-unknown-linux-gnueabihf

The Clang triplet is very unusual. I've never seen a compiler claim
armv8l. ARM does not even have a hit for ARMv8l on their site
(https://www.google.com/search?q="armv8l"+site%3Aarm.com). According to
https://github.com/tsandmann/armv8l-toolchain-linux, it is an ARM A-53
toolchain. It looks like the mis-identification is causing some folks
trouble, including me (https://stackoverflow.com/q/27121199/608639).

Perhaps it would be a good idea if Clang reported something closer to
the board it is running on.



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

$ apt-cache policy clang
clang:
  Installed: 1:6.0-41~exp5~ubuntu1
  Candidate: 1:6.0-41~exp5~ubuntu1
  Version table:
 *** 1:6.0-41~exp5~ubuntu1 500
500 http://ports.ubuntu.com bionic-updates/universe armhf Packages
100 /var/lib/dpkg/status
 1:6.0-41~exp4 500
500 http://ports.ubuntu.com bionic/universe armhf Packages

** Affects: clang (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/1827175

Title:
  armv8l-unknown-linux-gnueabihf triplet from clang -dumpmachine on
  ARMv7l

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

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

[Bug 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object

2019-04-30 Thread Treviño
** Changed in: gnome-shell (Ubuntu Disco)
   Status: New => In Progress

** Changed in: mutter (Ubuntu Disco)
   Status: New => In Progress

** Description changed:

+ [ Impact ]
+ 
+ GNOME Shell crashes on restart or when ending the session
+ 
+ [ Test Case ]
+ 
+ Under X11, try to reload the shell multiple times using
+  - Alt+F2: write 'r', press 'enter'.
+  - Or quit it writing in the run dialog 'debugexit'.
+ 
+ Repeat multiple times, no crash caused by x11 calls should happen.
+ 
+ [ Regression potential ]
+ 
+ Nothing known, window actors might not be painted on reload.
+ 
+ ---
+ 
+ 
  Tracked upstream in https://gitlab.gnome.org/GNOME/mutter/issues/576
  
  Proposed fix: https://gitlab.gnome.org/GNOME/mutter/merge_requests/557
  
- 
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.2-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/a27089759201dfe884a9070c2d62c50680fb2de4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

** Changed in: mutter (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: gnome-shell (Ubuntu Disco)
   Importance: Undecided => High

** Changed in: gnome-shell (Ubuntu Disco)
   Importance: High => Medium

** Changed in: gnome-shell (Ubuntu Eoan)
   Importance: High => Medium

** Changed in: mutter (Ubuntu Disco)
   Importance: High => Medium

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

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay →
  detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref →
  ObjectInstance → → release_native_object

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

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

[Bug 1827174] [NEW] Sound: ASoC: sof: support Internal DMIC which directly connects to PCH

2019-04-30 Thread Hui Wang
Public bug reported:

- Need to port Intel's 5.0 kernel branch to (Disco) oem-kernel for DMIC
(digital MIC) support in some OEM platforms

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: New


** Tags: dell originate-from-1821270 originate-from-1826181

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- Sound: ASoC: sof: support Internal DMIC which directly connects to PHC
+ Sound: ASoC: sof: support Internal DMIC which directly connects to PCH

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

Title:
  Sound: ASoC: sof: support Internal DMIC which directly connects to PCH

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1827174/+subscriptions

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

[Bug 1827172] Re: update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-04-30 Thread Matthew Ruffell
** Description changed:

  [Impact]
  
-  * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.
+  * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.
  
-  * update-rc.d incorrectly modifies symlinks when enabling or disabling 
services
-which are started on the "S" runlevel.
+  * update-rc.d incorrectly modifies symlinks when enabling or disabling  
+services which are started on the "S" runlevel.
  
-  * This can lead to services being changed from S runlevel from where they 
would
-be started on boot, to "0" runlevel, and are run on halt, which is 
incorrect.
+  * This can lead to services being changed from S runlevel from where they 
+would be started on boot, to "0" runlevel, and are run on halt, which is 
+incorrect.
  
-  * The bug is caused by trying to use the runlevel to index into an integer
-array of runlevels. When the runlevel in question is "S", an error is 
printed
-
-Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 
232.
+  * The bug is caused by trying to use the runlevel to index into an integer
+    array of runlevels. When the runlevel in question is "S", an error is 
+printed
  
-Perl then sets the index to default to 0, which changes the runlevel.
+Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 
+232.
  
-  * The fix is to check if the runlevel is "S", and if it is, set the index to 
99
-which conforms with other expected usages for the "S" runlevel in the 
script.
-See the "startstop" and "makelinks" subroutines.
+    Perl then sets the index to default to 0, which changes the runlevel.
+ 
+  * The fix is to check if the runlevel is "S", and if it is, set the index to 
 
+99 which conforms with other expected usages for the "S" runlevel in the 
+script. See the "startstop" and "makelinks" subroutines.
  
  [Test Case]
  
- * You can reproduce this with any service that is started on the "S" runlevel.
-   We will use open-iscsi for an example.
+ * You can reproduce this with any service that is started on the "S" 
+   runlevel. We will use open-iscsi for an example.
  
  1) Install open-iscsi
  
  $ sudo apt install open-iscsi
  
  2) Check to see symlinks for init.d scripts are set to defaults:
  
  root@trusty-openiscsi:/etc# ls -l /etc/rc[0123456S].d/*iscsi*
- lrwxrwxrwx 1 root root 24 Apr 29 20:56 /etc/rc0.d/K80umountiscsi.sh -> 
../init.d/umountiscsi.sh
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rc0.d/K81open-iscsi -> 
../init.d/open-iscsi
- lrwxrwxrwx 1 root root 24 Apr 29 20:56 /etc/rc1.d/K80umountiscsi.sh -> 
../init.d/umountiscsi.sh
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rc1.d/K81open-iscsi -> 
../init.d/open-iscsi
- lrwxrwxrwx 1 root root 24 Apr 29 20:56 /etc/rc6.d/K80umountiscsi.sh -> 
../init.d/umountiscsi.sh
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rc6.d/K81open-iscsi -> 
../init.d/open-iscsi
- lrwxrwxrwx 1 root root 20 Apr 29 20:56 /etc/rcS.d/S45open-iscsi -> 
../init.d/open-iscsi
+ /etc/rc0.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
+ /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
+ /etc/rc1.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
+ /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
+ /etc/rc6.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
+ /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
+ /etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi
  
  3) Use update-rc.d to enable open-iscsi service
  
  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
  Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 232.
  Enabling system startup links for /etc/init.d/open-iscsi ...
  Removing any system startup links for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi
  /etc/rc1.d/K81open-iscsi
  /etc/rc6.d/K81open-iscsi
  /etc/rcS.d/S45open-iscsi
  Adding system startup for /etc/init.d/open-iscsi ...
  /etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
  /etc/rc0.d/S45open-iscsi -> ../init.d/open-iscsi
  
- * The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly 
changed to
-   "/etc/rc0.d/S45open-iscsi".
+ * The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly 
+   changed to "/etc/rc0.d/S45open-iscsi".
  
- * Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/
- intact:
+ * Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/ 
+   intact:
  
  root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
  update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
  update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values 

Re: [Bug 1826506] Re: Test

2019-04-30 Thread kai kessler
Hallo, und guten Tag

Vielen Dank für die Hilfe.

Problem war das Update von 16.04. auf 18.04. Vermutlich lief dann der 
KORG Kalender fehlerhaft.

Habe jetzt 18.04. runtergeladen, und neu installiert. Jetzt ist alles
ok.

    Schöne Grüße. Kai

Am 26.04.19 um 09:42 schrieb Daniel van Vugt:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
>  ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
>
> ** 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/1826506

Title:
  Test

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

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

[Bug 1813716] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object

2019-04-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/mutter/+git/mutter/+merge/36

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

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay →
  detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref →
  ObjectInstance → → release_native_object

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

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

[Bug 1826181] Re: To add DMIC support to oem-kernel

2019-04-30 Thread Hui Wang
** Description changed:

  - Need to port Intel's 5.0 kernel branch to (Disco) oem-kernel for DMIC
  (digital MIC) support in some OEM platforms
+ 
+ X-HWE-Bug: Bug #1827174

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

Title:
  To add DMIC support to oem-kernel

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

2019-04-30 Thread Daniel van Vugt
Great!

By the way, one possible reason why you were unable to follow comment #2
is that gdm is designed to catch mutter/gnome-shell crashes in the
Wayland backend (which it tries first). If such a crash occurs then it
is meant to automatically fall back to Xorg.

Regardless of whether the automatic fallback was working for you, that
crash handling done by gdm would possibly prevent any crash in mutter
/gnome-shell Wayland start-up from being saved and sent to Ubuntu :(

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

2019-04-30 Thread Gregory Stewart
I didn't know how to log into "Ubuntu" instead of "Ubuntu on Wayland"
since I only got a blinking cursor and no logon prompt. I edited
/etc/gdm3/custom.conf and rebooted.

Successfully got a GUI logon prompt and was able to log in to the
desktop.

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1827172] [NEW] update-rc.d: enabling or disabling S runlevel services incorrectly modifies runlevel

2019-04-30 Thread Matthew Ruffell
Public bug reported:

[Impact]

 * update-rc.d, in sysv-rc-2.88dsf-41ubuntu6.3 is broken in trusty.

 * update-rc.d incorrectly modifies symlinks when enabling or disabling  
   services which are started on the "S" runlevel.

 * This can lead to services being changed from S runlevel from where they 
   would be started on boot, to "0" runlevel, and are run on halt, which is 
   incorrect.

 * The bug is caused by trying to use the runlevel to index into an integer
   array of runlevels. When the runlevel in question is "S", an error is 
   printed

   Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 
   232.

   Perl then sets the index to default to 0, which changes the runlevel.

 * The fix is to check if the runlevel is "S", and if it is, set the index to  
   99 which conforms with other expected usages for the "S" runlevel in the 
   script. See the "startstop" and "makelinks" subroutines.

[Test Case]

* You can reproduce this with any service that is started on the "S" 
  runlevel. We will use open-iscsi for an example.

1) Install open-iscsi

$ sudo apt install open-iscsi

2) Check to see symlinks for init.d scripts are set to defaults:

root@trusty-openiscsi:/etc# ls -l /etc/rc[0123456S].d/*iscsi*
/etc/rc0.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
/etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc1.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
/etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc6.d/K80umountiscsi.sh -> ../init.d/umountiscsi.sh
/etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

3) Use update-rc.d to enable open-iscsi service

root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
Argument "S" isn't numeric in array element at /usr/sbin/update-rc.d line 232.
Enabling system startup links for /etc/init.d/open-iscsi ...
Removing any system startup links for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi
/etc/rc1.d/K81open-iscsi
/etc/rc6.d/K81open-iscsi
/etc/rcS.d/S45open-iscsi
Adding system startup for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc0.d/S45open-iscsi -> ../init.d/open-iscsi

* The problem is the "/etc/rcS.d/S45open-iscsi" symlink is incorrectly 
  changed to "/etc/rc0.d/S45open-iscsi".

* Instead, the correct behaviour is to keep the symlink in /etc/rcS.d/ 
  intact:

root@trusty-openiscsi:/etc# update-rc.d open-iscsi enable
update-rc.d: warning: start runlevel arguments (none) do not match open-iscsi 
Default-Start values (S)
update-rc.d: warning: stop runlevel arguments (none) do not match open-iscsi 
Default-Stop values (0 1 6)
Enabling system startup links for /etc/init.d/open-iscsi ...
Removing any system startup links for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi
/etc/rc1.d/K81open-iscsi
/etc/rc6.d/K81open-iscsi
/etc/rcS.d/S45open-iscsi
Adding system startup for /etc/init.d/open-iscsi ...
/etc/rc0.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc1.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rc6.d/K81open-iscsi -> ../init.d/open-iscsi
/etc/rcS.d/S45open-iscsi -> ../init.d/open-iscsi

[Regression Potential]

 * There is only one file modified, which is the update-rc.d perl script. 
   Worst case scenario is that users cannot enable or disable their services, 
   or a symlink is changed such that a service is started / stopped on an 
   incorrect runlevel.

 * If a regression happens, any damage should be easily spotted by a 
   sysadmin and can be manually repaired by making manual symlinks with 
   "ln -s".

[Other Info]

 * trusty is the last Ubuntu release to use sysvinit, and this bug is not 
   present in newer versions since they use systemd, and the code in question 
   is removed from update-rc.d.

 * The bug exists in debian squeeze, which is now unsupported, and the code 
   in question is not in any newer versions.

 * The bug was introduced in 2009-06-29 and somehow evaded anyone noticing 
   it.

** Affects: sysvinit (Ubuntu)
 Importance: Medium
 Assignee: Matthew Ruffell (mruffell)
 Status: New

** Affects: sysvinit (Ubuntu Trusty)
 Importance: Medium
 Assignee: Matthew Ruffell (mruffell)
 Status: New


** Tags: sts

** Also affects: sysvinit (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: sysvinit (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: sysvinit (Ubuntu Trusty)
 Assignee: (unassigned) => Matthew Ruffell (mruffell)

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

Title:
  update-rc.d: enabling or disabling S 

[Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function

2019-04-30 Thread RA
I can also confirm that this is still happening with Ubuntu 16.04 LTS

duplicity-backup.sh v1.6.0
duplicity 0.7.19

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Codename:   xenial

---[ Program versions ]---
duplicity-backup.sh v1.6.0
duplicity 0.7.19
--

LFTP version is 4.6.3a
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1581, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1567, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1419, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1441, in do_backup
action).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 684, 
in set_values
backend_filename_list = self.backend.list()
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 301: 
ordinal not in range(128)

[ Duplicity Cleanup ]
LFTP version is 4.6.3a
Traceback (innermost last):
  File "/usr/bin/duplicity", line 1581, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1567, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1419, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1441, in do_backup
action).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 684, 
in set_values
backend_filename_list = self.backend.list()
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 301: 
ordinal not in range(128)

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

Title:
  Duplicity fails with UnicodeDecodeError in uexc function

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

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

[Bug 1762205] Re: GNOME boxes fails to start virtual os

2019-04-30 Thread Dennis Etheridge
*** This bug is a duplicate of bug 1767302 ***
https://bugs.launchpad.net/bugs/1767302

Tried what John Tanner did not work.
So I tried Stephen Matin's also did not work.

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

Title:
  GNOME boxes fails to start virtual os

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

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

[Bug 1804786] Re: Garbage occurred when Playing the video in the Ubuntu Desktop Guide

2019-04-30 Thread Gunnar Hjalmarsson
The problem seems not to be Ubuntu specific.

https://bugzilla.redhat.com/show_bug.cgi?id=1696788

(I get those "Recursion depth exceeded calculating {bg,fg} color"
messages too on eoan and disco.

** Bug watch added: Red Hat Bugzilla #1696788
   https://bugzilla.redhat.com/show_bug.cgi?id=1696788

** Also affects: yelp via
   https://bugzilla.redhat.com/show_bug.cgi?id=1696788
   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/1804786

Title:
  Garbage occurred when Playing the video in the Ubuntu Desktop Guide

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

2019-04-30 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1827037] Re: [Comm] IBM JDK 8.0.5.35 integration into Ubuntu

2019-04-30 Thread Steve Langasek
ibm-java80/8.0.5.35-0ubuntu1 has been accepted into xenial-proposed for
building/testing.

** Changed in: ibm-java71 (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/1827037

Title:
  [Comm] IBM JDK 8.0.5.35 integration into Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1827037/+subscriptions

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

[Bug 1818059] Re: packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()

2019-04-30 Thread Launchpad Bug Tracker
[Expired for packagekit (Ubuntu) because there has been no activity for
60 days.]

** Changed in: packagekit (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/1818059

Title:
  packagekitd crashed with SIGSEGV in __strncasecmp_l_avx()

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

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

[Bug 1817998] Re: KVM Guest - DHCP lease lost (Ubuntu 18.04)

2019-04-30 Thread Launchpad Bug Tracker
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (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/1817998

Title:
  KVM Guest - DHCP lease lost (Ubuntu 18.04)

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

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

[Bug 1818271] Re: package unattended-upgrades 1.5ubuntu3.18.10.2 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess was killed by signal (Broken pipe)

2019-04-30 Thread Launchpad Bug Tracker
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: unattended-upgrades (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/1818271

Title:
  package unattended-upgrades 1.5ubuntu3.18.10.2 failed to
  install/upgrade: installed unattended-upgrades package post-
  installation script subprocess was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1818271/+subscriptions

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

[Bug 1818238] Re: fib_tests.sh net selftest is flaky when running carrier tests

2019-04-30 Thread Launchpad Bug Tracker
[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/1818238

Title:
  fib_tests.sh net selftest is flaky when running carrier tests

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

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

[Bug 1827169] Re: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1827169/+subscriptions

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

[Bug 1827170] [NEW] la laptop se me bloquea a cada momento

2019-04-30 Thread donovan
Public bug reported:

cuando me encuentro trabajando en la pc se me bloquea a cada rato y ya
desactive el bloqueo automático y aun lo sigue asiendo también desactive
la opción de apagar pantalla automáticamente

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-release-upgrader-core 1:18.10.11.5
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CrashDB: ubuntu
Date: Tue Apr 30 21:33:50 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-07-04 (301 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=es_GT:es
 PATH=(custom, no user)
 LANG=es_GT.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to cosmic on 2019-05-01 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2019-04-30 21:30:06.719191
 Log time: 2019-04-30 21:31:07.428968
 Log time: 2019-04-30 21:33:17.873388
 Log time: 2019-04-30 21:33:51.012144
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2019-02-19T13:51:09.127922

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic dist-upgrade

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

Title:
  la laptop se me bloquea a cada momento

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1827170/+subscriptions

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

[Bug 1827169] [NEW] package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-30 Thread Michael Charleston
Public bug reported:

Attempting to install lyx from command-line with sudo apt install.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: desktop-file-utils 0.22-1ubuntu5.2
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed May  1 13:14:35 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2019-03-19 (43 days ago)
InstallationMedia: Ubuntu-Server 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190226)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.31
SourcePackage: desktop-file-utils
Title: package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: desktop-file-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package desktop-file-utils 0.22-1ubuntu5.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1827169/+subscriptions

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

[Bug 1827168] [NEW] install error

2019-04-30 Thread Jason W.
Public bug reported:

unsure of the issue

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CasperVersion: 1.405
Date: Tue Apr 30 22:30:45 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash nomodeset ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (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/1827168

Title:
  install error

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

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

[Bug 1827073] Re: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build

2019-04-30 Thread Daniel van Vugt
The attached build log appears to be truncated and incomplete. Do you
have any other build logs?

** Changed in: nvidia-graphics-drivers-384 (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/1827073

Title:
  nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed
  to build

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

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

[Bug 1827134] Re: Software Updater has bad URL for gfortran package

2019-04-30 Thread JPSman
** Package changed: ubuntu => gcc-defaults (Ubuntu)

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

Title:
  Software Updater has bad URL for gfortran package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1827134/+subscriptions

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

[Bug 1538902] Re: package openvpn 2.3.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-04-30 Thread sathesh
** Description changed:

- error
- 
- ProblemType: Package
- DistroRelease: Ubuntu 15.10
- Package: openvpn 2.3.7-1ubuntu1
- ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
- Uname: Linux 4.2.0-25-generic x86_64
- ApportVersion: 2.19.1-0ubuntu5
- Architecture: amd64
- Date: Thu Jan 28 11:26:25 2016
- DuplicateSignature: package:openvpn:2.3.7-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
- ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
- InstallationDate: Installed on 2016-01-20 (7 days ago)
- InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
- RelatedPackageVersions:
-  dpkg 1.18.2ubuntu5.1
-  apt  1.0.10.2ubuntu1
- SourcePackage: openvpn
- Title: package openvpn 2.3.7-1ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
- UpgradeStatus: No upgrade log present (probably fresh install)
+ ..

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

Title:
  package openvpn 2.3.7-1ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

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

[Bug 1827059] Re: Gnome-shell won't lock screen anymore

2019-04-30 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Gnome-shell won't lock screen anymore

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

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

[Bug 1827118] Re: Boot black screen

2019-04-30 Thread Daniel van Vugt
I can't see any problem in the files attached so far. We need a log file
covering the period of time when the problem actually happened. To get
that please:

1. Reproduce the problem.

2. Reboot and then immediately run:

   journalctl -b-1 > prevboot.txt

   and then attach the file 'prevboot.txt' to this bug.


** 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/1827118

Title:
  Boot black screen

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

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

[Bug 1805077] Re: [ASUS X555YI] the audio pause and repeat for a very short of time randomly

2019-04-30 Thread widon1104
This bug appear a few time today after I upgrade my system to ubuntu19.04.
This is definitely a bug.

widon@widon-X555YI:~$ uname -a
Linux widon-X555YI 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [ASUS X555YI] the audio pause and repeat for a very short of time
  randomly

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

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

[Bug 1827049] Re: Constant cpu load after scaling change from 200 to 300

2019-04-30 Thread Daniel van Vugt
If you are using Xorg with fractional scaling then this issue is
expected [1]. And I assume you are using Xorg if you have the Nvidia
driver installed.

However, mutter should be smart enough to detect when you are using
integer scaling factors and avoid the inefficiency of fractional
scaling. So maybe this is a different bottleneck...

[1] https://discourse.ubuntu.com/t/x11-hidpi-scaling-available-for-
testing-on-disco/10293/16

** Tags added: x11-scaling

** Tags added: hidpi

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

Title:
  Constant cpu load after scaling change from 200 to 300

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1827049/+subscriptions

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: Function not implemented" on Matrox graphics card)

2019-04-30 Thread Daniel van Vugt
Also, to avoid Wayland fully, please edit /etc/gdm3/custom.conf and
uncomment:

  #WaylandEnable=false

then reboot.

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1393403] Re: dovecot unable to create files in /var/mail

2019-04-30 Thread Bug Watch Updater
** Changed in: dovecot (Debian)
   Status: Unknown => New

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

Title:
  dovecot unable to create files in /var/mail

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

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

[Bug 1827031] Re: Desktop wallpaper and lock screen wallpaper corrupted after waking up the system

2019-04-30 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1809407, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1809407
   [nvidia] Corrupted wallpaper after resuming from suspend

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

Title:
  Desktop wallpaper and lock screen wallpaper corrupted after waking up
  the system

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

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

[Bug 1826201] Re: Green vertical bars when using gstreamer-vaapi in Totem

2019-04-30 Thread Daniel van Vugt
** Summary changed:

- MP4 Video playback is broken in Ubuntu 19.04
+ Green vertical bars when using gstreamer-vaapi in Totem

** Tags added: regression-release

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

Title:
  Green vertical bars when using gstreamer-vaapi in Totem

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

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

[Bug 1826944] Re: Green bars in ubuntu videos when using gstreamer1.0-vaapi

2019-04-30 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1826201 ***
https://bugs.launchpad.net/bugs/1826201

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1826201, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- green bars in ubuntu videos
+ Green bars in ubuntu videos when using gstreamer1.0-vaapi

** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu)

** Changed in: gstreamer-vaapi (Ubuntu)
   Status: Incomplete => New

** This bug has been marked a duplicate of bug 1826201
   Green vertical bars when using gstreamer-vaapi in Totem

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

Title:
  Green bars in ubuntu videos when using gstreamer1.0-vaapi

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1826944/+subscriptions

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Daniel van Vugt
** No longer affects: linux (Ubuntu)

** Summary changed:

- gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer: 
Function not implemented" on Matrox graphics card)

** Changed in: mesa (Ubuntu)
   Importance: High => Low

** Changed in: mutter (Ubuntu)
   Importance: High => Low

** Changed in: mesa (Ubuntu)
   Status: New => Triaged

** Changed in: mutter (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/1826025

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826201] Re: MP4 Video playback is broken in Ubuntu 19.04

2019-04-30 Thread Daniel van Vugt
We haven't established for certain that this is a gstreamer-vaapi bug
yet. Though it sounds likely.

Please follow the instructions in comment #10.

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

Title:
  MP4 Video playback is broken in Ubuntu 19.04

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

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

[Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot

2019-04-30 Thread Theron Muller
Dear Sebastian,
Thanks for your response. I've raised the bug upstream here: 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166

I'll try to keep this bug stream and that one coordinated.

** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues 
#166
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166

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

Title:
  Ethernet won't connect when cable is plugged in at boot

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

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

[Bug 854206] Re: no desktop login, just console. xorg Matrox MGA driver fails to initialize

2019-04-30 Thread Daniel van Vugt
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

** Changed in: xserver-xorg-video-mga (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  no desktop login, just console. xorg Matrox MGA driver fails to
  initialize

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Daniel van Vugt
** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Daniel van Vugt
Tracking upstream (I think) in
https://gitlab.gnome.org/GNOME/mutter/issues/57

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

** Summary changed:

- gnome-shell trap int3 no desktop (MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #57
   https://gitlab.gnome.org/GNOME/mutter/issues/57

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/issues/57
   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/1826025

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop

2019-04-30 Thread Daniel van Vugt
It appears this message keeps happening with the gnome-shell crash:

  "Impossible to lock surface front buffer: Function not implemented"

that's from mutter's "native" (Wayland) backend:

  next_bo = gbm_surface_lock_front_buffer (gbm_surface);

  if (!next_bo)
{
  g_error ("Impossible to lock surface front buffer: %m");
  return FALSE;
}

so it means your kernel graphics driver (mgag200) does not fully support
Wayland sessions.

Please just use Xorg sessions instead (log into "Ubuntu" instead of
"Ubuntu on Wayland").

** Summary changed:

- gnome-shell trap int3 no desktop
+ gnome-shell trap int3 no desktop (MGA G200eW fails when calling 
gbm_surface_lock_front_buffer)

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux (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/1826025

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mesa (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/1826025

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Status changed to Confirmed

2019-04-30 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (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/1826025

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mutter (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/1826025

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1826025] Re: gnome-shell trap int3 no desktop (MGA G200eW fails when calling gbm_surface_lock_front_buffer)

2019-04-30 Thread Daniel van Vugt
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)

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

Title:
  gnome-shell trap int3 no desktop ("Impossible to lock surface front
  buffer: Function not implemented" on Matrox graphics card)

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

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

[Bug 1827167] [NEW] New version, current ver is badly outdated

2019-04-30 Thread Kevin Williams
Public bug reported:

Current upstream version is 4.1.3, released in July 2018.  Please
update.

** Affects: angband (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/1827167

Title:
  New version, current ver is badly outdated

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

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

[Bug 1822392] Re: gsd-media-keys fails to adjust the screen brightness after unlocking

2019-04-30 Thread DooMMasteR
that does never work for me
`sudo /usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 93
fish: “sudo /usr/lib/gnome-settings-da…” terminated by signal SIGSEGV (Address 
boundary error)
`
gsd-backlight-h[19085]: segfault at 0 ip 7f7235fe25ee sp 7fff88c62278 
error 4 in libc-2.29.so[7f7235e86000+173000]
[499265.506514] Code: 0f 84 f9 fe ff ff e9 51 89 f3 ff 90 89 f8 31 d2 c5 c5 ef 
ff 09 f0 25 ff 0f 00 00 3d 80 0f 00 00 0f 8f 56 03 00 00 c5 fe 6f 0f  f5 74 
06 c5 fd da c1 c5 fd 74 c7 c5 fd d7 c8 85 c9 74 7e f3 0f

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

Title:
  gsd-media-keys fails to adjust the screen brightness after unlocking

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

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

[Bug 1817620] Re: High cpu usage on alt-tab-ing

2019-04-30 Thread Daniel van Vugt
Please try:

(1) Updating your system, since the fix mentioned in comment #1 should
now be included in 18.04 updates. Maybe this bug has been fixed.

(2) If you do restart gnome-shell and find that improves performance,
then wait another 30 seconds or more and retest. Does it get slower
again after 30 seconds?

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

** Changed in: mutter (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/1817620

Title:
  High cpu usage on alt-tab-ing

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

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

[Bug 1816231] Re: There is regular screen flickering/flashing (when the mouse isn't moving)

2019-04-30 Thread Daniel van Vugt
The file 'journal.txt' is created in the current directory when you run:

  journalctl -b0 > journal.txt

But if you have successfully removed 'xserver-xorg-video-intel' then you
may not need to do anything more. Did that fix it?

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

Title:
  There is regular screen flickering/flashing (when the mouse isn't
  moving)

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

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

[Bug 1818614] Re: [SRU] Various L3HA functional tests fails often

2019-04-30 Thread Launchpad Bug Tracker
This bug was fixed in the package neutron - 2:13.0.2-0ubuntu3.1

---
neutron (2:13.0.2-0ubuntu3.1) cosmic; urgency=medium

  * d/p/bug1823038.patch: Cherry pick fix to ensure that None is not
passed as an argument when spawning the neutron-keepalived-state-change
agent (LP: #1823038).

neutron (2:13.0.2-0ubuntu3) cosmic; urgency=medium

  * d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream
to prevent neutron ovs agent from crashing due to creation of two
security groups that both use the same remote security group, where
the first group's port range is a subset of the second (LP: #1813007).
  * d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch:
Cherry-picked from upstream stable/rocky branch to ensure proper
detection of MASTER HA router by neutron-keepalived-state-change
(LP: #1818614).

 -- James Page   Tue, 09 Apr 2019 11:37:29 +0100

** Changed in: neutron (Ubuntu Cosmic)
   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/1818614

Title:
  [SRU] Various L3HA functional tests fails often

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1818614/+subscriptions

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

[Bug 1813007] Re: [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes when having broken security group rules (CVE-2019-10876)

2019-04-30 Thread Launchpad Bug Tracker
This bug was fixed in the package neutron - 2:13.0.2-0ubuntu3.1

---
neutron (2:13.0.2-0ubuntu3.1) cosmic; urgency=medium

  * d/p/bug1823038.patch: Cherry pick fix to ensure that None is not
passed as an argument when spawning the neutron-keepalived-state-change
agent (LP: #1823038).

neutron (2:13.0.2-0ubuntu3) cosmic; urgency=medium

  * d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream
to prevent neutron ovs agent from crashing due to creation of two
security groups that both use the same remote security group, where
the first group's port range is a subset of the second (LP: #1813007).
  * d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch:
Cherry-picked from upstream stable/rocky branch to ensure proper
detection of MASTER HA router by neutron-keepalived-state-change
(LP: #1818614).

 -- James Page   Tue, 09 Apr 2019 11:37:29 +0100

** Changed in: neutron (Ubuntu Cosmic)
   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/1813007

Title:
  [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes
  when having broken security group rules (CVE-2019-10876)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

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

[Bug 1823038] Re: Neutron-keepalived-state-change fails to check initial router state

2019-04-30 Thread Launchpad Bug Tracker
This bug was fixed in the package neutron - 2:13.0.2-0ubuntu3.1

---
neutron (2:13.0.2-0ubuntu3.1) cosmic; urgency=medium

  * d/p/bug1823038.patch: Cherry pick fix to ensure that None is not
passed as an argument when spawning the neutron-keepalived-state-change
agent (LP: #1823038).

neutron (2:13.0.2-0ubuntu3) cosmic; urgency=medium

  * d/p/fix-KeyError-in-OVS-firewall.patch: Cherry-picked from upstream
to prevent neutron ovs agent from crashing due to creation of two
security groups that both use the same remote security group, where
the first group's port range is a subset of the second (LP: #1813007).
  * d/p/set-initial-ha-router-state-in-neutron-keepalived-st.patch:
Cherry-picked from upstream stable/rocky branch to ensure proper
detection of MASTER HA router by neutron-keepalived-state-change
(LP: #1818614).

 -- James Page   Tue, 09 Apr 2019 11:37:29 +0100

** Changed in: neutron (Ubuntu Cosmic)
   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/1823038

Title:
  Neutron-keepalived-state-change fails to check initial router state

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1823038/+subscriptions

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

[Bug 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()

2019-04-30 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  gnome-control-center crashed with SIGSEGV in
  _gdk_event_queue_handle_motion_compression()

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

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

[Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...

2019-04-30 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: Unknown => New

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

Title:
  Shell dialog messages are truncated and ellipsized...

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

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

[Bug 1827162] Missing required logs.

2019-04-30 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 1827162

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

Title:
  "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

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

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

[Bug 1824738] Re: gvfsd-admin crashed with signal 5

2019-04-30 Thread Bug Watch Updater
** Changed in: gvfs
   Status: New => 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/1824738

Title:
  gvfsd-admin crashed with signal 5

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

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

[Bug 1823038] Update Released

2019-04-30 Thread Chris Halse Rogers
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Neutron-keepalived-state-change fails to check initial router state

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1823038/+subscriptions

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

[Bug 1766201] Re: CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg error Checking for all LINUX clients for devops4p10

2019-04-30 Thread Khaled El Mously
There appears to be more than one problem being described in this bug
report. Since they are separate issues they should be tracked as
separate bugs (this helps keeping tracking of the fixes).

We'll use this bug to track the original issue described in the bug
description (downgrading the x509 errors to warnings) which @Andrea has
already taken care of.

The other issue described here ("vio: failed to send synthetic uevent")
will be tracked under
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827162

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

Title:
  CTAUTO:DevOps:860.50:devops4fp1:Error occurred during LINUX Dmesg
  error Checking for all LINUX clients for devops4p10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1766201/+subscriptions

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

[Bug 1818614] Update Released

2019-04-30 Thread Chris Halse Rogers
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] Various L3HA functional tests fails often

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1818614/+subscriptions

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

[Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...

2019-04-30 Thread Daniel van Vugt
I can't see any history of a fix. But it's only reported in 3.28 here
and 3.30 upstream...?

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

Title:
  Shell dialog messages are truncated and ellipsized...

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

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

[Bug 1813007] Update Released

2019-04-30 Thread Chris Halse Rogers
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes
  when having broken security group rules (CVE-2019-10876)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

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

[Bug 1809788] Re: bionic - TBT authentication message will be cut from the dialog box

2019-04-30 Thread Daniel van Vugt
Tracking upstream in https://gitlab.gnome.org/GNOME/gnome-
shell/issues/922

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #922
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/922

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/issues/922
   Importance: Unknown
   Status: Unknown

** Summary changed:

- bionic - TBT authentication message will be cut from the dialog box
+ Shell dialog messages are truncated and ellipsized...

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

Title:
  Shell dialog messages are truncated and ellipsized...

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

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

[Bug 1783085] Re: open-vm-tools-dkms 2:10.0.7-3227872-5ubuntu1~16.04.2: open-vm-tools kernel module failed to build [error: implicit declaration of function ‘init_timer_deferrable’]

2019-04-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: open-vm-tools (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/1783085

Title:
  open-vm-tools-dkms 2:10.0.7-3227872-5ubuntu1~16.04.2: open-vm-tools
  kernel module failed to build [error: implicit declaration of function
  ‘init_timer_deferrable’]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1783085/+subscriptions

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

[Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...

2019-04-30 Thread Daniel van Vugt
I would say remove Yaru here. The theme can't directly control whether
the dialog is too small and needs wrapping. Although it can control the
dialog size indirectly with some tweaks, but doing that would be a hack.

I think this is a pure Gnome Shell bug.

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

Title:
  Shell dialog messages are truncated and ellipsized...

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

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

[Bug 1826688] Re: GNOME Shell icon grid fade in/out is sometimes missing at the top/bottom of the screen

2019-04-30 Thread PJ O
I added the newest journalctl to the post above, and here's the entire
thing.

** Description changed:

  After installing an update for Ubuntu 18.04 LTS, GNOME's App Launcher
  screen faces graphical issues when scrolling. To reproduce this, simply
  open the Application menu and scroll in the paginated list. If the bug
  is present, the screen will fail to update completly; the animation wil
  play through, but the icons will remain in place or "chopped off," it
  seems the frame isn't completly refreshed? It's fixed after a few
  seconds or by moving the mouse.
  
  I'm using GNOME 3.28.2 on Ubuntu 18.04 LTS
  
  I'm also using an Nvidia card for graphics (with drivers installed)
  
  I attached a picture (Sorry that it isn't a screenshot!)
+ 
+ EDIT 4/30/19: Here's `journalctl` (I ran the command, performed the
+ action. If this doesn't cut it, I attached the entire journalctl
+ below.):
+ 
+ ```
+ Apr 30 21:24:15 pj-desktop anacron[14623]: Updated timestamp for job 
`cron.daily' to 2019-04-30
+ Apr 30 21:24:15 pj-desktop cracklib[14653]: no dictionary update necessary.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopping Make remote CUPS printers 
available locally...
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopped Make remote CUPS printers 
available locally.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopping CUPS Scheduler...
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopped CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop gsd-color[2010]: failed to connect to device: 
Failed to connect to missing device 
/org/freedesktop/ColorManager/devices/cups_Canon_MF720C_Series
+ Apr 30 21:24:16 pj-desktop gsd-color[1624]: failed to connect to device: 
Failed to connect to missing device 
/org/freedesktop/ColorManager/devices/cups_Canon_MF720C_Series
+ Apr 30 21:24:16 pj-desktop systemd[1]: Closed CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopping CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Listening on CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopped CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Stopping CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Started CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Started CUPS Scheduler.
+ Apr 30 21:24:16 pj-desktop systemd[1]: Started Make remote CUPS printers 
available locally.
+ Apr 30 21:24:16 pj-desktop colord[1115]: failed to get session [pid 14745]: 
No data available
+ Apr 30 21:24:16 pj-desktop rsyslogd[1038]:  [origin software="rsyslogd" 
swVersion="8.32.0" x-pid="1038" x-info="http://www.rsyslog.com;] rsyslogd was 
HUPed
+ Apr 30 21:24:17 pj-desktop colord[1115]: failed to get session [pid 14745]: 
No data available
+ Apr 30 21:24:18 pj-desktop pkexec[14767]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
+ Apr 30 21:24:18 pj-desktop pkexec[14767]: pj: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/pj] 
[COMMAND=/usr/lib/update-notifier/package-system-locked]
+ Apr 30 21:24:30 pj-desktop anacron[10055]: Job `cron.daily' terminated
+ Apr 30 21:24:30 pj-desktop anacron[10055]: Normal exit (1 job run)
+ 
+ ```
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sat Apr 27 20:51:07 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-12-25 (123 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Attachment added: "gnomelog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826688/+attachment/5260439/+files/gnomelog.txt

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

Title:
  GNOME Shell icon grid fade in/out is sometimes missing at the
  top/bottom of the screen

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

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

[Bug 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000

2019-04-30 Thread tdotreppe
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  mac80211_hwsim unable to handle kernel NULL pointer dereference
  at

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

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

[Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

2019-04-30 Thread Chris Halse Rogers
Marking as verification-failed as per the last couple of comments.

It looks like that might want to be split out into a new bug,
particularly as it also affects cosmic (and disco?)

** Tags removed: verification-done
** Tags added: regression-proposed verification-failed

** Tags removed: verification-done-bionic
** Tags added: verification-failed-bionic

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1819615/+subscriptions

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

[Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

2019-04-30 Thread Daniel van Vugt
** 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/1796606

Title:
  gnome-shell crashed with SIGSEGV in st_widget_get_theme_node →
  ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

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

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

[Bug 1827162] [NEW] "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

2019-04-30 Thread Khaled El Mously
Public bug reported:

This bug is created from bug LP #1766201 which reported multiple errors
in the kernel log on ppc64el. This bug is for tracking the issue of the
error message "vio vio: uevent: failed to send synthetic uevent" (see
the original bug, and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766201/comments/12
for more info)

** Affects: linux (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/1827162

Title:
  "vio vio: uevent: failed to send synthetic uevent" errors on ppc64el

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

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

[Bug 1827154] Re: gnome-control-center crashed with SIGSEGV in _gdk_event_queue_handle_motion_compression()

2019-04-30 Thread El jinete sin cabeza
** Also affects: gtk+3.0 (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/1827154

Title:
  gnome-control-center crashed with SIGSEGV in
  _gdk_event_queue_handle_motion_compression()

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

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

[Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()

2019-04-30 Thread Daniel van Vugt
Yeah, we seem to only be getting crash reports from 3.28 (bionic) now...
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

** Also affects: gnome-session (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: gnome-session (Ubuntu Eoan)
   Importance: Medium
   Status: Confirmed

** Also affects: gnome-session (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: gnome-session (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: gnome-session (Ubuntu Eoan)
   Status: Confirmed => Fix Released

** Changed in: gnome-session (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: gnome-session (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: gnome-session (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: gnome-session (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: gnome-session (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: gnome-session (Ubuntu Disco)
   Importance: Undecided => Medium

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

Title:
  gnome-session-check-accelerated crashed with SIGSEGV in
  g_hash_table_lookup_node() from g_hash_table_lookup() from
  lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()

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

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

[Bug 1393403] Re: dovecot unable to create files in /var/mail

2019-04-30 Thread Bryce Harrington
** Bug watch added: Debian Bug tracker #885001
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885001

** Also affects: dovecot (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885001
   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/1393403

Title:
  dovecot unable to create files in /var/mail

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

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

[Bug 1735363] Re: inkscape: Port to Python 3

2019-04-30 Thread Qantas94Heavy
** Changed in: inkscape
Milestone: None => 0.92.5

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

Title:
  inkscape: Port to Python 3

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

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

[Bug 1827160] [NEW] gnome night light works on only one monitor

2019-04-30 Thread Bickhaus
Public bug reported:

I am running Ubuntu 19.04 with an AMD RX570, using the open source
driver, and I have two Dell U2415 monitors connected via DisplayPort
(not daisy-chained).  Gnome Night Light only changes the color on the
monitor dubbed "Monitor 1" in display settings (though the monitor I
have set to primary is Monitor 2).  I found a multiple posts where it
was stated that using `killall gsd-color` fixed the issue.  This
workaround was successful for me also.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 20:05:24 2019
InstallationDate: Installed on 2019-03-19 (42 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: meta-gnome3
UpgradeStatus: Upgraded to disco on 2019-04-19 (12 days ago)

** Affects: meta-gnome3 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  gnome night light works on only one monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1827160/+subscriptions

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

[Bug 923676] Re: /usr/lib/dovecot/deliver: invalid option -- 'n'

2019-04-30 Thread Bryce Harrington
Closing bug as obsolete, since the distro upgrade it involves is over 7
years old now.

** Changed in: dovecot (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  /usr/lib/dovecot/deliver: invalid option -- 'n'

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

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

[Bug 1827159] Re: check_all_disks includes squashfs /snap/* which are 100%

2019-04-30 Thread Xav Paice
** Merge proposal linked:
   
https://code.launchpad.net/~xavpaice/nagios-charm/+git/nagios-charm/+merge/366740

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

Title:
  check_all_disks includes squashfs /snap/* which are 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1827159/+subscriptions

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

[Bug 1827159] [NEW] check_all_disks includes squashfs /snap/* which are 100%

2019-04-30 Thread Xav Paice
Public bug reported:

When using nagios to monitor the Nagios host itself, if the host is not
a container, the template for checking the disk space on the Nagios host
does not exclude any snap filesystems.  This means we get a Critical
report if any snap is installed.

This can be changed by adding to the check_all_disks command a '-X
squashfs', but that command is defined in the nagios plugins package.

** Affects: nagios-charm
 Importance: Undecided
 Status: New

** Affects: monitoring-plugins (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: canonical-bootstack

** Also affects: monitoring-plugins (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/1827159

Title:
  check_all_disks includes squashfs /snap/* which are 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1827159/+subscriptions

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

[Bug 640121] Re: package dovecot-imapd 1:1.2.9-1ubuntu6.1 failed to install/upgrade: `hostname` not defined

2019-04-30 Thread Bryce Harrington
** Summary changed:

- package dovecot-imapd 1:1.2.9-1ubuntu6.1 failed to install/upgrade: 
dependency problems - leaving unconfigured
+ package dovecot-imapd 1:1.2.9-1ubuntu6.1 failed to install/upgrade: 
`hostname` not defined

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

Title:
  package dovecot-imapd 1:1.2.9-1ubuntu6.1 failed to install/upgrade:
  `hostname` not defined

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

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

[Bug 1822871] Re: enabling ftrace on Hi1620 CS causes an Oops

2019-04-30 Thread dann frazier
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  enabling ftrace on Hi1620 CS causes an Oops

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

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

[Bug 1826739] Re: Adobe flash player does not work correctly on Ubuntu 19.04 Disk

2019-04-30 Thread Edson José dos Santos
Hello Cliff (enkiduonthenet)

We know that these flash players are about to disappear forever, but
while that does not happen officially should not work normally? This
problem is recurrent in the majority of Linux distros, where after
upgrades, either distro or browsers something happens in adobe flash
player plugins or in the famous Opera ffmpeg. For ffmpeg I found a
definitive solution for some distros that insist on not working, but for
the flash player not yet.

Note: In an attempt to find out why Opera Browser, using the adobe flash
player plugin does not work, I ended up finding the command to run Opera
via sandbox and thus, using it through the terminal, the adobe flash
returns to normal operation.

[edson @ edson-pc6540br ~] $ opera with --no-sandbox
[18933: 18933: 0429 / 233016.386156: ERROR: sandbox_linux.cc (364)] 
InitializeSandbox () called with multiple threads in process gpu-process.
[18908: 18908: 1829 / 233018.493575: ERROR: CONSOLE (0)] "Unchecked 
runtime.lastError while running operaTouchPrivate.getLocalName: Can not obtain 
local name
at chrome-extension: //ebongfbmlegepmkkdjlnlmdcmckedlal/touch_communication.js: 
246: 35 ", source: chrome-extension: 
//ebongfbmlegepmkkdjlnlmdcmckedlal/page.html (0)
[18908: 18908: 18908: 0429 / 233018.577888: ERROR: CONSOLE (0)] "Uncaught (in 
promise) #", source: chrome-extension: 
//obhaigpnhcioanniiaepcgkdilopflbb/background_worker.html (0)

Closing connection 0
NOT SANDBOXED


For Google Chrome also only works the adobe flash player plugins in sandbox


[edson @ edson-pc6540br ~] $ / opt / google / chrome / chrome with --no-sandbox
[27942: 27942: 272942/325039.994321: ERROR: sandbox_linux.cc (368)] 
InitializeSandbox () called with multiple threads in process gpu-process.
NOT SANDBOXED
[27918: 27918: 0429 / 235104.908528: ERROR: textfield.cc (1773)] Textfield :: 
ShouldDoLearning ()
[27918: 27918: 0429 / 235118.411465: ERROR: prefix_selector.cc (168)] 
PrefixSelector :: ShouldDoLearning ()


What may have caused such discomfort?
In some distros Linux as in the case of MX Linux is working normally, in others 
also only work in sandbox as is the case in Ubuntu 19.04.

As in Manjaro it is easy to review the adobe flash player's
dependencies, I saw that there is a file called glibc 2.29 that was
updated in this package yesterday, and it is precisely in distros that
their browsers do not work. Already for the distros that work the adobe
plugins are with this file glibc previous to 2.29. I do not know if this
is the real problem, but I think it should be investigated for this
inconvenience that adobe plugins only work in sandbox in some cases.

The problem seems to be really related to glibc version 2.29.
So the next version of chromium should solve this problem that has been 
dragging on for years.

https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/chromium=6dbfc1d185e673ad82f2539083b0e625c746dfa6


Thank You

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

Title:
  Adobe flash player does not work correctly on Ubuntu 19.04 Disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adobe-flashplugin/+bug/1826739/+subscriptions

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

[Bug 1404879] Re: package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: Unknown setting: managesieve_max_line_length

2019-04-30 Thread Bryce Harrington
** Summary changed:

- package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 255
+ package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade: Unknown 
setting: managesieve_max_line_length

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

Title:
  package dovecot-core 1:2.2.9-1ubuntu5 failed to install/upgrade:
  Unknown setting: managesieve_max_line_length

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

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

[Bug 1411962] Re: package dovecot-pop3d 1:2.2.9-1ubuntu5 failed to install/upgrade: cp: cannot create regular file ‘/etc/dovecot/conf.d/20-imap.conf’: No such file or directory

2019-04-30 Thread Bryce Harrington
** Summary changed:

- package dovecot-pop3d 1:2.2.9-1ubuntu5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
+ package dovecot-pop3d 1:2.2.9-1ubuntu5 failed to install/upgrade: cp: cannot 
create regular file ‘/etc/dovecot/conf.d/20-imap.conf’: No such file or 
directory

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

Title:
  package dovecot-pop3d 1:2.2.9-1ubuntu5 failed to install/upgrade: cp:
  cannot create regular file ‘/etc/dovecot/conf.d/20-imap.conf’: No such
  file or directory

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

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

[Bug 1817665] Re: Please SRU the pymacaroons stack to Trusty

2019-04-30 Thread Chris Halse Rogers
As we still don't have an ubuntu-advantage-tools package ready to use
these, and it is still my understanding that we don't want to release
these until there's an ubuntu-advantage-tools SRU using them, I'm re-
marking these as Incomplete to move them off the SRU team report until
they *are* ready to release.

These are still verification-done, so as soon as an SRU of ubuntu-
advantage-tools using this is ready to go we can release them all.

If my understanding is faulty, please reset to ‘fix committed’ and add a
comment making it clear what the next step is expected to be. Thanks!

** Changed in: libsodium (Ubuntu Trusty)
   Status: Fix Committed => Incomplete

** Changed in: pymacaroons (Ubuntu Trusty)
   Status: Fix Committed => Incomplete

** Changed in: python-libnacl (Ubuntu Trusty)
   Status: Fix Committed => Incomplete

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

Title:
  Please SRU the pymacaroons stack to Trusty

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

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

[Bug 1827158] [NEW] nautilus 1:3.26.4-0~ubuntu18.04.4 crash

2019-04-30 Thread widon1104
Public bug reported:

widon@widon-X555YI:/var/log$ dpkg -l | grep nautilus
ii  nautilus  1:3.26.4-0~ubuntu18.04.4  
 amd64file manager and graphical shell for GNOME

I don't how to reproduce it, it happens when I copy some picture from
Desktop to Pictures folder.

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

** Attachment added: "It happens in 22:34, you can search "crash" in syslog"
   https://bugs.launchpad.net/bugs/1827158/+attachment/5260435/+files/syslog

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

Title:
  nautilus 1:3.26.4-0~ubuntu18.04.4 crash

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

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

[Bug 1827158] Re: nautilus 1:3.26.4-0~ubuntu18.04.4 crash

2019-04-30 Thread widon1104
** Attachment added: "_usr_bin_nautilus.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827158/+attachment/5260436/+files/_usr_bin_nautilus.1000.crash

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

Title:
  nautilus 1:3.26.4-0~ubuntu18.04.4 crash

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

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

[Bug 1826958] Re: lubuntu 19.04 - USB pendrive storage

2019-04-30 Thread Walter Lapchynski
Again, pictures could be helpful.

Also, I would suggest providing *clear* and *simple* instructions that
anyone could follow to reproduce the exact same issue. What commands did
you use? What applications did you use? What was every single step?

The more we can make the description and problem generic, the easier
this will be.

That said, one thing that's not clear is whether or not your USB
pendrive has persistence. If it doesn't, you most certainly will have
problems.

Also, what makes you think that the files are invisible? How are you
trying to look for them?

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

Title:
  lubuntu 19.04 - USB pendrive storage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm-qt/+bug/1826958/+subscriptions

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

[Bug 1827134] Re: Software Updater has bad URL for gfortran package

2019-04-30 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/1827134/+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/1827134

Title:
  Software Updater has bad URL for gfortran package

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

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

[Bug 1827140] Re: Ubuntu 18.04-2 installer crash if "search domains" are specified in IPv4 configuration

2019-04-30 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/1827140/+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/1827140

Title:
  Ubuntu 18.04-2 installer crash if "search domains" are specified in
  IPv4 configuration

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

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

  1   2   3   4   5   6   7   >