[Bug 1820185] Re: [MIR] django-haystack as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] django-haystack as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-haystack/+bug/1820185/+subscriptions

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

[Bug 1820179] Re: [MIR] coreapi as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] coreapi as dependency of mailman3

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

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

[Bug 1820182] Re: [MIR] django-filter as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] django-filter as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-filter/+bug/1820182/+subscriptions

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

[Bug 1820180] Re: [MIR] coreschema as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] coreschema as dependency of mailman3

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

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

[Bug 1820191] Re: [MIR] flufl.bounce as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: flufl.bounce (Ubuntu)
   Status: New => 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/1820191

Title:
  [MIR] flufl.bounce as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flufl.bounce/+bug/1820191/+subscriptions

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

[Bug 1820190] Re: [MIR] djangorestframework as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: djangorestframework (Ubuntu)
   Status: New => 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/1820190

Title:
  [MIR] djangorestframework as dependency of mailman3

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

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

[Bug 1820188] Re: [MIR] django-picklefield as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] django-picklefield as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-picklefield/+bug/1820188/+subscriptions

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

[Bug 1820189] Re: [MIR] django-q as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] django-q as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-q/+bug/1820189/+subscriptions

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

[Bug 1820192] Re: [MIR] flufl.i18n as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] flufl.i18n as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flufl.i18n/+bug/1820192/+subscriptions

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

[Bug 1820193] Re: [MIR] flufl.lock as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] flufl.lock as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flufl.lock/+bug/1820193/+subscriptions

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

[Bug 1820196] Re: [MIR] hyperkitty as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: hyperkitty (Ubuntu)
   Status: New => 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/1820196

Title:
  [MIR] hyperkitty as dependency of mailman3

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

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

[Bug 1820197] Re: [MIR] itypes as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] itypes as dependency of mailman3

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

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

[Bug 1820200] Re: [MIR] lazr.delegates as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] lazr.delegates as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lazr.delegates/+bug/1820200/+subscriptions

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

[Bug 1820223] Re: [MIR] python-uritemplate as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] python-uritemplate as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-uritemplate/+bug/1820223/+subscriptions

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

[Bug 1820221] Re: [MIR] python-requests-oauthlib as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python-requests-oauthlib (Ubuntu)
   Status: New => 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/1820221

Title:
  [MIR] python-requests-oauthlib as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-requests-oauthlib/+bug/1820221/+subscriptions

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

[Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)

2019-07-02 Thread Kai-Heng Feng
Does the latest HWE kernel solve the issue?

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

Title:
  Touchpad not working (Lenevo Ideapad 330 series)

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

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

[Bug 1820202] Re: [MIR] libmatheval as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: libmatheval (Ubuntu)
   Status: New => 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/1820202

Title:
  [MIR] libmatheval as dependency of mailman3

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

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

[Bug 1820203] Re: [MIR] libpgm as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: libpgm (Ubuntu)
   Status: New => 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/1820203

Title:
  [MIR] libpgm as dependency of mailman3

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

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

[Bug 1820199] Re: [MIR] lazr.config as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] lazr.config as dependency of mailman3

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

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

[Bug 1820211] Re: [MIR] python3-openid as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python3-openid (Ubuntu)
   Status: New => 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/1820211

Title:
  [MIR] python3-openid as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-openid/+bug/1820211/+subscriptions

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

[Bug 1820216] Re: [MIR] python-django-gravatar2 as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python-django-gravatar2 (Ubuntu)
   Status: New => 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/1820216

Title:
  [MIR] python-django-gravatar2 as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-django-gravatar2/+bug/1820216/+subscriptions

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

[Bug 1820234] Re: [MIR] zope.configuration as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: zope.configuration (Ubuntu)
   Status: New => 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/1820234

Title:
  [MIR] zope.configuration as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zope.configuration/+bug/1820234/+subscriptions

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

[Bug 1820229] Re: [MIR] wcwidth as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] wcwidth as dependency of mailman3

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

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

[Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

2019-07-02 Thread Kai-Heng Feng
Sorry for the late reply.

Have you tried latest latest Ubuntu ISO?
http://cdimages.ubuntu.com/daily-live/current/

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

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

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

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

[Bug 1820214] Re: [MIR] python-blessed as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] python-blessed as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-blessed/+bug/1820214/+subscriptions

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

[Bug 1820205] Re: [MIR] mailman-hyperkitty as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: mailman-hyperkitty (Ubuntu)
   Status: New => 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/1820205

Title:
  [MIR] mailman-hyperkitty as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman-hyperkitty/+bug/1820205/+subscriptions

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

[Bug 1820204] Re: [MIR] mailmanclient as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: mailmanclient (Ubuntu)
   Status: New => 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/1820204

Title:
  [MIR] mailmanclient as dependency of mailman3

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

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

[Bug 1820982] Re: [MIR] nose as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] nose as dependency of mailman3

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

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

[Bug 1820210] Re: [MIR] postorius as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: postorius (Ubuntu)
   Status: New => 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/1820210

Title:
  [MIR] postorius as dependency of mailman3

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

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

[Bug 1820220] Re: [MIR] python-public as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] python-public as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-public/+bug/1820220/+subscriptions

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

[Bug 1820206] Re: [MIR] mailman-suite as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] mailman-suite as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/1820206/+subscriptions

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

[Bug 1820225] Re: [MIR] robot-detection as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] robot-detection as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/robot-detection/+bug/1820225/+subscriptions

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

[Bug 1820212] Re: [MIR] python-aiosmtpd as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python-aiosmtpd (Ubuntu)
   Status: New => 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/1820212

Title:
  [MIR] python-aiosmtpd as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-aiosmtpd/+bug/1820212/+subscriptions

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

[Bug 1820217] Re: [MIR] python-falcon as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python-falcon (Ubuntu)
   Status: New => 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/1820217

Title:
  [MIR] python-falcon as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-falcon/+bug/1820217/+subscriptions

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

[Bug 1820213] Re: [MIR] python-arrow as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved - 
like this one - will stay that way, but we will make no seed change to pull 
things in for now. Yet if other needs come up for those they have a prepared 
MIR already.
Other bugs which are not yet completed in terms of review will be closed as 
Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

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

Title:
  [MIR] python-arrow as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-arrow/+bug/1820213/+subscriptions

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

[Bug 1820209] Re: [MIR] norm as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: norm (Ubuntu)
   Status: New => 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/1820209

Title:
  [MIR] norm as dependency of mailman3

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

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

[Bug 1820224] Re: [MIR] python-whoosh as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python-whoosh (Ubuntu)
   Status: New => 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/1820224

Title:
  [MIR] python-whoosh as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-whoosh/+bug/1820224/+subscriptions

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

[Bug 1820215] Re: [MIR] python-django-extensions as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: python-django-extensions (Ubuntu)
   Status: New => 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/1820215

Title:
  [MIR] python-django-extensions as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-django-extensions/+bug/1820215/+subscriptions

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

[Bug 1834936] Re: linux-gcp: 4.15.0-1037.39 -proposed tracker

2019-07-02 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1834935 (xenial/linux-gcp)
  derivatives: bug 1834931 (gcp-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Ready for Packaging
- phase-changed: Tuesday, 02. July 2019 18:37 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 03. July 2019 05:37 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux-gcp: 4.15.0-1037.39 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834936/+subscriptions

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

[Bug 1820237] Re: [MIR] zope.hookable as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: zope.hookable (Ubuntu)
   Status: New => 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/1820237

Title:
  [MIR] zope.hookable as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zope.hookable/+bug/1820237/+subscriptions

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

[Bug 1820238] Re: [MIR] zope.schema as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: zope.schema (Ubuntu)
   Status: New => 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/1820238

Title:
  [MIR] zope.schema as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zope.schema/+bug/1820238/+subscriptions

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

[Bug 1820227] Re: [MIR] uwsgi as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: uwsgi (Ubuntu)
   Status: New => 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/1820227

Title:
  [MIR] uwsgi as dependency of mailman3

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

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

[Bug 1820239] Re: [MIR] zope.i18nmessageid as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: zope.i18nmessageid (Ubuntu)
   Status: New => 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/1820239

Title:
  [MIR] zope.i18nmessageid as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zope.i18nmessageid/+bug/1820239/+subscriptions

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

[Bug 1820186] Re: [MIR] django-mailman3 as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: django-mailman3 (Ubuntu)
   Status: New => 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/1820186

Title:
  [MIR] django-mailman3 as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-mailman3/+bug/1820186/+subscriptions

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

[Bug 1820181] Re: [MIR] django-allauth as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: django-allauth (Ubuntu)
   Status: New => 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/1820181

Title:
  [MIR] django-allauth as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-allauth/+bug/1820181/+subscriptions

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

[Bug 1820236] Re: [MIR] zope.event as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: zope.event (Ubuntu)
   Status: New => 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/1820236

Title:
  [MIR] zope.event as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zope.event/+bug/1820236/+subscriptions

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

[Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker

2019-07-02 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1833987
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 02. July 2019 21:09 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 03. July 2019 05:33 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
+   promote-to-proposed: Pending -- ready for review
  variant: debs

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

Title:
  linux-fips: 4.15.0-1011.12 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+subscriptions

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

[Bug 1820183] Re: [MIR] django-guardian as dependency of mailman3

2019-07-02 Thread Christian Ehrhardt 
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it for support in main.

We have closed the primary LP bug already, the MIRs that are already approved 
will stay that way, but we will make no seed change to pull things in for now. 
Yet if other needs come up for those they have a prepared MIR already.
Other bugs - like this one - which are not yet completed in terms of review 
will be closed as Won't Fix.

Even thou it ended being aborted, I think that is a valid outcome of the
MIR evaluations. Never the less I want to thank everybody involved for
all the work spent in what was nearly a year working through these MIRs.

** Changed in: django-guardian (Ubuntu)
   Status: New => 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/1820183

Title:
  [MIR] django-guardian as dependency of mailman3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/django-guardian/+bug/1820183/+subscriptions

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

[Bug 40285] Re: libgcc_s.so.1 must be installed for pthread_cancel to work

2019-07-02 Thread WHK
Same problem using python3 and multithreading in Ubuntu 18.04 LTS.

libgcc_s.so.1 must be installed for pthread_cancel to work.

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

Title:
  libgcc_s.so.1 must be installed for pthread_cancel to work

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

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

[Bug 1835076] Re: No open button after installing .deb package

2019-07-02 Thread Olivier Tilloy
** Attachment added: "journalctlb0.log"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835076/+attachment/5274803/+files/journalctlb0.log

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

Title:
  No open button after installing .deb package

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

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

[Bug 1835076] Re: No open button after installing .deb package

2019-07-02 Thread Olivier Tilloy
I can observe the problem in a stock Ubuntu 19.10 VM, after installing the 
google-chrome-stable deb from chrome.com.
Attaching journalctl, the following lines look like they might be related to 
the problem:

jul 03 07:11:55 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/appdata/google-chrome.appdata.xml.dpkg-new file: cannot process file 
of type text/html
jul 03 07:11:55 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/google-chrome.desktop.dpkg-new file: cannot process 
file of type text/plain
jul 03 07:12:07 eoanvm gnome-software[2412]: failed to rescan: No valid root 
node specified
jul 03 07:12:07 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/google-chrome.desktop file: cannot process file of type 
application/x-desktop
jul 03 07:12:08 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/defaults.list file: cannot process file of type 
text/plain
jul 03 07:12:08 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/defaults.list file: cannot process file of type 
text/plain
jul 03 07:12:08 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/defaults.list file: cannot process file of type 
text/plain
jul 03 07:12:08 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/defaults.list file: cannot process file of type 
text/plain
jul 03 07:12:08 eoanvm gnome-software[2412]: failed to rescan: Failed to parse 
/usr/share/applications/defaults.list file: cannot process file of type 
text/plain

** Changed in: gnome-software (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  No open button after installing .deb package

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

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

[Bug 1835146] Re: download speed, internet connectivity is ruhl bad

2019-07-02 Thread Chris Guiver
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

** Changed in: bcmwl (Ubuntu)
   Status: New => Invalid

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

Title:
  download speed, internet connectivity is ruhl bad

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

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

[Bug 1834936] Re: linux-gcp: 4.15.0-1037.39 -proposed tracker

2019-07-02 Thread Khaled El Mously
** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1037.39 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-gcp: 4.15.0-1037.39 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834936/+subscriptions

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

[Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.63 -proposed tracker

2019-07-02 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  derivatives: bug 1834924 (dragonboard-kernel)
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Ready for Packaging
- phase-changed: Tuesday, 02. July 2019 18:36 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 03. July 2019 05:07 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux-snapdragon: 4.15.0-1058.63 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions

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

[Bug 1835073] Re: Put filename path of .deb package on a different line

2019-07-02 Thread Olivier Tilloy
** Changed in: gnome-software (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/1835073

Title:
  Put filename path of .deb package on a different line

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

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

[Bug 1834940] Re: linux-kvm: 4.15.0-1039.39 -proposed tracker

2019-07-02 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1834954
- phase: Ready for Packaging
- phase-changed: Tuesday, 02. July 2019 18:37 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 03. July 2019 05:07 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

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

Title:
  linux-kvm: 4.15.0-1039.39 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834940/+subscriptions

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

[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor

2019-07-02 Thread Hui Wang
This is the log of running uefi app.


** Attachment added: "591384548.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1822043/+attachment/5274802/+files/591384548.jpg

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

Title:
  as enrolling mok, the font is too small in hi-dpi monitor

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

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

[Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.63 -proposed tracker

2019-07-02 Thread Khaled El Mously
** Summary changed:

- linux-snapdragon:  -proposed tracker
+ linux-snapdragon: 4.15.0-1058.63 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-snapdragon: 4.15.0-1058.63 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions

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

[Bug 1835112] Re: linux-fips: 4.15.0-1011.12 -proposed tracker

2019-07-02 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
    https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1833987
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 21:09 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa meta:failed
+   promote-to-proposed: Ongoing -- builds not complete in ppa meta:building
  variant: debs

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

Title:
  linux-fips: 4.15.0-1011.12 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835112/+subscriptions

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

[Bug 1834940] Re: linux-kvm: 4.15.0-1039.39 -proposed tracker

2019-07-02 Thread Khaled El Mously
** Summary changed:

- linux-kvm:  -proposed tracker
+ linux-kvm: 4.15.0-1039.39 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  linux-kvm: 4.15.0-1039.39 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834940/+subscriptions

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

[Bug 1801780] Re: Unable to select Yaru sound theme in sound effects

2019-07-02 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1753070 ***
https://bugs.launchpad.net/bugs/1753070

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

** Changed in: gnome-control-center (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/1801780

Title:
  Unable to select Yaru sound theme in sound effects

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

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

[Bug 1448243] Re: package totem 3.14.0-0ubuntu1~utopic1 failed to install/upgrade: trying to overwrite '/usr/share/dbus-1/services/org.gnome.Totem.service', which is also in package totem-common 3.14.

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1448243

Title:
  package totem 3.14.0-0ubuntu1~utopic1 failed to install/upgrade:
  trying to overwrite
  '/usr/share/dbus-1/services/org.gnome.Totem.service', which is also in
  package totem-common 3.14.0-0ubuntu1~utopic1

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

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

[Bug 1132065] Re: totem crashed with SIGSEGV in g_data_set_internal()

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1132065

Title:
  totem crashed with SIGSEGV in g_data_set_internal()

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

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

[Bug 1232544] Re: totem-video-thumbnailer crashed with SIGABRT in alloc_table()

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1232544

Title:
  totem-video-thumbnailer crashed with SIGABRT in alloc_table()

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

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

[Bug 1219121] Re: Totem’s interface unable to launch.

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1219121

Title:
  Totem’s interface unable to launch.

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

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

[Bug 1015417] Re: Totem doesnt release memory when going to next file

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1015417

Title:
  Totem doesnt release memory when going to next file

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

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

[Bug 942873] Re: Totem causes logout when playing mp3/videos with dual monitor and fglrx Drivers

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/942873

Title:
  Totem causes logout when playing mp3/videos with dual monitor and
  fglrx Drivers

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

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

[Bug 1270435] Re: totem crashed with signal 5 in g_object_bind_property_full() when run with option --g-fatal-warnings

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1270435

Title:
  totem crashed with signal 5 in g_object_bind_property_full() when run
  with option --g-fatal-warnings

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

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

[Bug 1346188] Re: totem crashed with SIGSEGV in submit_packet() while playing vide

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1346188

Title:
  totem crashed with SIGSEGV in submit_packet() while playing vide

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

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

[Bug 1376468] Re: Totem crashes attempting to play wmv file

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1376468

Title:
  Totem crashes attempting to play wmv file

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

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

[Bug 1471944] Re: package totem-plugins 3.14.2-0ubuntu2 failed to install/upgrade: subprocesso novo script pre-removal retornou erro do status de saída 139

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1471944

Title:
  package totem-plugins 3.14.2-0ubuntu2 failed to install/upgrade:
  subprocesso novo script pre-removal retornou erro do status de saída
  139

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

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

[Bug 1491564] Re: package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1491564

Title:
  package totem 3.14.2-0ubuntu1 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 1

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

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

[Bug 1529153] Re: Totem crashes with segmentation fault

2019-07-02 Thread Launchpad Bug Tracker
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]

** Changed in: totem (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/1529153

Title:
  Totem crashes with segmentation fault

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

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

[Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

2019-07-02 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (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/1827417

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

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

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

[Bug 1792329] Re: Firefox freezes continuously on Ubuntu 16.04

2019-07-02 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (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/1792329

Title:
  Firefox freezes continuously on Ubuntu 16.04

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

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

[Bug 1827417] Re: Ubuntu 16.04 - EMU10K1 / CT4832 lost ability to listen stereo on headphones - there is upmixed surround only.

2019-07-02 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/1827417

Title:
  Ubuntu 16.04 -  EMU10K1 / CT4832 lost ability to listen stereo on
  headphones -  there is upmixed  surround only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827417/+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-07-02 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/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/linux/+bug/1816231/+subscriptions

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

[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

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

** Changed in: linux (Ubuntu Bionic)
   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/1827884

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

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

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

[Bug 1833018] Re: After Installing Updates, system fails to boot on first try

2019-07-02 Thread Kai-Heng Feng
*** This bug is a duplicate of bug 1827884 ***
https://bugs.launchpad.net/bugs/1827884

** This bug has been marked a duplicate of bug 1827884
   Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

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

Title:
  After Installing Updates, system fails to boot on first try

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

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

[Bug 1835154] [NEW] Cannot start tor browser - gpg hangs refreshing keys

2019-07-02 Thread Andrei Borzenkov
Public bug reported:

I am not able to start tor browser since a couple of days because gpg
loops refreshing keys. Killing gpg allows tor browser to start:

UIDPID  PPID  C STIME TTY  TIME CMD
bor  31474 31391 97 06:30 ?00:13:46 /usr/bin/gpg --status-fd 2 
--homedir /home/bor/.local/share/torbrowser/gnupg_homedir --keyserver 
hkps://hkps.pool.sks-keyservers.net --keyserver-options ca-cert-file 
/usr/share/torbrowser-launcher/sks-keyservers.netCA.pem include-revoked 
no-honor-keyserver-url no-honor-pka-record --refresh-keys

Yes, this is 18 *minutes*.

See https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f
for description of DoS on key servers which seems to be the reason.

Key server is hard coded in torbrowser-launcher. It needs to either be
changed or made configurable.

I also opened upstream issue:

https://github.com/micahflee/torbrowser-launcher/issues/401

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: torbrowser-launcher 0.2.9-2
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Wed Jul  3 06:46:16 2019
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2015-07-02 (1461 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
SourcePackage: torbrowser-launcher
UpgradeStatus: Upgraded to bionic on 2018-08-22 (314 days ago)

** Affects: torbrowser-launcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Cannot start tor browser - gpg hangs refreshing keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/torbrowser-launcher/+bug/1835154/+subscriptions

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

[Bug 1835150] Re: Sometimes touchpad detected as mouse(i2c designware fails to get adapter number)

2019-07-02 Thread AceLan Kao
** Changed in: linux (Ubuntu)
   Status: In Progress => Invalid

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

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

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: AceLan Kao (acelankao) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Changed in: linux-oem-osp1 (Ubuntu Disco)
 Assignee: (unassigned) => AceLan Kao (acelankao)

** Tags added: oem-priority originate-from-1834156 somerville

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

Title:
  Sometimes touchpad detected as mouse(i2c designware fails to get
  adapter number)

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

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

[Bug 1820227] Re: [MIR] uwsgi as dependency of mailman3

2019-07-02 Thread Seth Arnold
Here's the notes I took while reviewing this package:

About the source code:
uwsgi_calloc() re-introduces integer overflow bugs
cppcheck results are entirely false positives

About the debian packaging:
cdbs is unfortunate
gbp is difficult to work with
there's a huge number of binary packages
complex Depends, Suggests, Replaces, Conflicts, Provides
different binary packages have different supported architectures


I really liked the documentation, and it felt like there was a lot to recommend 
this service, but the huge amount of complexity and highly intricate memory 
management felt very likely to have security issues.

To be clear I didn't find any security issues: it's just that moving
memory chunks across consumers and producers as this program does is
notoriously difficult to keep correct under maintenance.

Thanks

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

Title:
  [MIR] uwsgi as dependency of mailman3

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

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

[Bug 1835150] [NEW] Sometimes touchpad detected as mouse(i2c designware fails to get adapter number)

2019-07-02 Thread AceLan Kao
Public bug reported:

[Impact]
I2C designware fails to get its adapter number, and this may lead to fail to 
access touchpad through I2C bus.
[ 6.476367] WARNING: CPU: 9 PID: 567 at 
/build/linux-oem-osp1-bkWHJC/linux-oem-osp1-5.0.0/drivers/i2c/i2c-core-base.c:1322
 i2c_add_numbered_adapter+0x81/0x90

[Fix]
The 2 commits from v5.1-rc1 fix this issue.
   cd86d1403bb4 i2c: i2c-designware-platdrv: Always use a dynamic adapter number
   77f3381a83c2 i2c: i2c-designware-platdrv: Cleanup setting of the adapter 
number

[Test]
Verified on Dell machine which had this issue.

[Regression Potential]
Low, the 2 commits make it always use dynamic adapter-numbers which does not 
make any difference in most cases and in the one case where it does make a 
difference the behavior change is desirable because the old behavior caused an 
oops.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: AceLan Kao (acelankao)
 Status: In Progress

** Affects: linux-oem-osp1 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: linux-oem-osp1 (Ubuntu Bionic)
 Importance: Undecided
 Status: New

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

** Affects: linux-oem-osp1 (Ubuntu Disco)
 Importance: Undecided
 Status: New

** Description changed:

  [Impact]
  I2C designware fails to get its adapter number, and this may lead to fail to 
access touchpad through I2C bus.
  [ 6.476367] WARNING: CPU: 9 PID: 567 at 
/build/linux-oem-osp1-bkWHJC/linux-oem-osp1-5.0.0/drivers/i2c/i2c-core-base.c:1322
 i2c_add_numbered_adapter+0x81/0x90
  
  [Fix]
- The 2 commits fix this issue.
-cd86d1403bb4 i2c: i2c-designware-platdrv: Always use a dynamic adapter 
number
-77f3381a83c2 i2c: i2c-designware-platdrv: Cleanup setting of the adapter 
number
+ The 2 commits from v5.1-rc1 fix this issue.
+    cd86d1403bb4 i2c: i2c-designware-platdrv: Always use a dynamic adapter 
number
+    77f3381a83c2 i2c: i2c-designware-platdrv: Cleanup setting of the adapter 
number
  
  [Test]
  Verified on Dell machine which had this issue.
  
  [Regression Potential]
  Low, the 2 commits make it always use dynamic adapter-numbers which does not 
make any difference in most cases and in the one case where it does make a 
difference the behavior change is desirable because the old behavior caused an 
oops.

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

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

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

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

** Also affects: linux-oem-osp1 (Ubuntu Bionic)
   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/1835150

Title:
  Sometimes touchpad detected as mouse(i2c designware fails to get
  adapter number)

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

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

[Bug 1835151] [NEW] auto crop

2019-07-02 Thread Gene Olson
Public bug reported:

Handbrake on ubuntu 18.04 no longer autocrops videos as it used to. I've
tried multiple videos, and while Handbrake on Windows crops them
perfectly, Hanbrake on Ubuntu 18.04 no longer does.

How to reproduce.

Find a long skinny bluray video, which is just about any movie released
in the last 10 years.  Scan it with handbrake.  You'll find that it
"auto crops" to 1920 x 1080 on Linux, while on Windows it crops more
liken 1920 x 800.

** Affects: handbrake (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/1835151

Title:
  auto crop

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

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

[Bug 1835068] Re: When I click to top indicators, I will see freezing animations

2019-07-02 Thread Daniel van Vugt
** Tags added: performance

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

Title:
  When I click to top indicators, I will see freezing animations

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

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

[Bug 1835118] Re: i don't know

2019-07-02 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!


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

Title:
  i don't know

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

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

[Bug 1835043] Re: Ubuntu Dock sticks if I will enter the text in the search line

2019-07-02 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1832317 ***
https://bugs.launchpad.net/bugs/1832317

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 1832317, 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.


** Tags added: performance

** This bug has been marked a duplicate of bug 1832317
   A quick type in the Gnome 3 search sticks

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

Title:
  Ubuntu Dock sticks if I will enter the text in the search line

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

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

[Bug 1832946] Re: Icon spring animation performs worse and skips frames if there are windows open

2019-07-02 Thread Daniel van Vugt
I agree I think this might be a problem unique to gnome-shell-extension-
ubuntu-dock but am yet to confirm...

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell-extension-ubuntu-dock (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/1832946

Title:
  Icon spring animation performs worse and skips frames if there are
  windows open

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

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

[Bug 1834967] Re: Activities overview doesn't fit the whole window in when shrinking

2019-07-02 Thread Daniel van Vugt
Please try attaching that file again with a simpler file name that web
browsers can handle :)

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

Title:
  Activities overview doesn't fit the whole window in when shrinking

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

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

[Bug 1814643] Re: keyboard switch indicator

2019-07-02 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1812266 ***
https://bugs.launchpad.net/bugs/1812266

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 1812266, 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 1812266
   Keyboard layout indicator does not indicate current layout (18.04 Bionic 
beaver)

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

Title:
  keyboard switch indicator

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

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

[Bug 1826918] Re: gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay() from detach_pixmap() from meta_surface_actor_x11_dispose() from g_object_unref() from g_object_unref()

2019-07-02 Thread Daniel van Vugt
** Tags removed: fixed-3.33.3
** Tags added: fixed-in-3.33.3

** Changed in: mutter (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay()
  from detach_pixmap() from meta_surface_actor_x11_dispose() from
  g_object_unref() from g_object_unref()

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

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

[Bug 1424201]

2019-07-02 Thread Robert Mader
Although this bug is only about decoding support, I'd like to leave a note 
about the rendering: AFAIK rendering without any slow copies requires DMABUF 
support, so processes can share resources on the GPU.
For the Wayland backend this about to land, see bug 1552590, quote:

> Wayland dmabuf surface are located in GPU and can be attached as
EGLImage or wl_buffer. It allows direct rendering to GPU and share the
HW buffer across processes.

Also see bug 1010527

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

Title:
  Web browsers lacking hardware-accelerated video decoding

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

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

[Bug 1835033] Re: gnome-shell frozen and spinning in g_type_check_instance_cast() from meta_window_x11_is_focusable() from get_default_focus_window()

2019-07-02 Thread Daniel van Vugt
I inserted the word spinning per comment #6 :)

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

Title:
  gnome-shell frozen and spinning in g_type_check_instance_cast() from
  meta_window_x11_is_focusable() from get_default_focus_window()

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

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

[Bug 1804207] Re: current session logout when eog open a big jpg

2019-07-02 Thread Daniel van Vugt
If the main problem is getting logged out then:

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.

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

Title:
  current session logout when eog open a big jpg

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

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

[Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour when user logged in.

2019-07-02 Thread Daniel van Vugt
Alexander, please see bug 1550779 for that.

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

Title:
  No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic
  behaviour when user logged in.

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

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

[Bug 1835146] [NEW] download speed, internet connectivity is ruhl bad

2019-07-02 Thread Senyo
Public bug reported:

[31493:31493:0702/222647.438796:ERROR:sandbox_linux.cc(368)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[31449:31473:0702/222647.632779:ERROR:browser_process_sub_thread.cc(221)] 
Waited 59 ms for network service
Opening in existing browser session.
dpkg-query: no packages found matching broadcom-sta-source

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: GNOME-Classic:GNOME
Date: Tue Jul  2 22:24:56 2019
InstallationDate: Installed on 2019-06-12 (20 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  download speed, internet connectivity is ruhl bad

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

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

[Bug 1835141] Re: /usr/lib/ibus-mozc/ibus-engine-mozc:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_logic_error

2019-07-02 Thread Gunnar Hjalmarsson
As far as I can tell, these crashes seem to be unrelated to the latest
change due to Reiwa.

@Nobuhiro: Is the existence of such crashes something you are aware of?
Is it possibly a reason to look at a newer upstream version?

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

Title:
  /usr/lib/ibus-mozc/ibus-engine-
  
mozc:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_logic_error

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

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

[Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker

2019-07-02 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe)
  derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 
1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 
(linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 
(linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 
1834943 (linux-oracle), bug 1834944 (linux-fips)
  
  -- swm properties --
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 02. July 2019 18:31 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
meta:failed,main:building
+   promote-to-proposed: Pending -- builds not complete in ppa meta:failed
  variant: debs

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

Title:
  linux: 4.15.0-55.60 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834954/+subscriptions

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

[Bug 1835144] [NEW] nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build

2019-07-02 Thread RiCK
Public bug reported:

fails to build after kernel update.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
DKMSKernelVersion: 4.4.0-154-generic
Date: Tue Jul  2 22:07:56 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GT216 [GeForce GT 220] 
[1462:1910]
InstallationDate: Installed on 2015-11-14 (1326 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: HP-Pavilion AY600AA-ABA HPE-127c
PackageVersion: 340.107-0ubuntu0.16.04.2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic 
root=UUID=55fcadff-651e-d101-002c-a5ff651ed101 ro quiet splash nomodeset 
usbcore.autosuspend=-1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.32
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.07
dmi.board.name: IONA
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.07:bd12/21/2009:svnHP-Pavilion:pnAY600AA-ABAHPE-127c:pvr:rvnMSI:rnIONA:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: AY600AA-ABA HPE-127c
dmi.sys.vendor: HP-Pavilion
modified.conffile..etc.modprobe.d.nvidia-340_hybrid.conf: [deleted]
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Jul  2 22:21:47 2019
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package possible-manual-nvidia-install 
third-party-packages ubuntu xenial

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

Title:
  nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to
  build

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

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

[Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-07-02 Thread Dima
I've tried. It's still happening.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827884/+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   8   9   >