date:20181025

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-10-25 Thread ccdisle

I just tested this. It worked for me as well. Thanks, Nebojša.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-10-25 Thread ccdisle

Uncommenting "WaylandEnable=false " worked.

Removing gdm3 did not work, I just got redirected to a tty3 login shell.

Thanks again

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7

2018-10-25 Thread Łukasz Zemczak

Hello Matthias, or anyone else affected,

Accepted python3-defaults into cosmic-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/python3-defaults/3.6.7-1~18.10 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: python3-defaults (Ubuntu Cosmic)
   Status: New => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1799206

Title:
  SRU: update python3.6 to the new minor release 3.6.7

Status in python3-defaults package in Ubuntu:
  Fix Committed
Status in python3.6 package in Ubuntu:
  Fix Committed
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in python3.6 source package in Bionic:
  Fix Committed
Status in python3-defaults source package in Cosmic:
  Fix Committed
Status in python3.6 source package in Cosmic:
  Fix Committed

Bug description:
  SRU: update python3.6 to the new minor release 3.6.7

  See LP: #1792143 for the rationale, going one minor release ahead (and
  planning to do 3.6.8 in January, the last source release from the 3.6
  branch).

  [Impact]
  Provide the branch updates for the stable 3.6 branch in the LTS release.

  [Regression Potential]
  There is regression potential, but this version is in use in 18.10, which 
didn't show regressions.

  [Test Case]
  No regressions in the Python 3.6 test suite, no regressions in the autopkg 
tests

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-10-25 Thread Kyle Weber

I didn’t need to remove GDM3, but installing LightDM (and switching to
it) fixed it for me. Well, I should say it was a workaround, anyway...

> On Oct 24, 2018, at 11:56 PM, ccdisle  wrote:
> 
> Uncommenting "WaylandEnable=false " worked.
> 
> Removing gdm3 did not work, I just got redirected to a tty3 login shell.
> 
> Thanks again
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1752053
> 
> Title:
>  nvidia-390 fails to boot graphical display
> 
> Status in mesa package in Ubuntu:
>  Fix Released
> Status in nvidia-graphics-drivers-390 package in Ubuntu:
>  Fix Released
> Status in xserver-xorg-video-nouveau package in Ubuntu:
>  Invalid
> 
> Bug description:
>  I'm using Bionic with the new 4.15 kernel. I've been using the
>  nvidia-384 driver with no problem for a while.  Today I issued "sudo
>  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
>  the nvidia-390.  After installing the driver and rebooting, I was only
>  able to boot in to the tty terminal.  The graphical display failed to
>  boot.  I have had similar problems with nvidia driver version 390 with
>  Arch Linux and with Open Suse Tumbleweed.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

2018-10-25 Thread Sebastien Bacher

** Description changed:

+ * Impact
+ keyboard backlight control keys don't work in cosmic
+ 
+ *  Test case
+ On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level
+ 
+ * Regression potential
+ The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working
+ 
+ ---
+ 
  https://gitlab.freedesktop.org/upower/upower/issues/73
  
  ---
  
  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit keyboard
  is displayed but no progress bar and no actual effect to the backlight.
  Almost as if the shell only understands laptops with a single key for
  controlling the keyboard backlight...
  
  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air
  
  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly.
  This seems to be a problem with Gnome Shell only.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1796550

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Committed

Bug description:
  * Impact
  keyboard backlight control keys don't work in cosmic

  *  Test case
  On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level

  * Regression potential
  The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working

  ---

  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=

2018-10-25 Thread Alex Murray

** Attachment added: "PoC using libpcre (ie without libglib)"
   
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1798725/+attachment/5205348/+files/PoC.c

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcre3 in Ubuntu.
https://bugs.launchpad.net/bugs/1798725

Title:
  Content "n\xff=" can crash libpcre when an application is matching the
  pattern \s*=

Status in pcre3 package in Ubuntu:
  Confirmed

Bug description:
  Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 -
  libpcre3 can be made to crash when matching the pattern \s*= when the
  context is n\xff=

  Able to reproduce on current Bionic using the PoC attached (which is
  copied directly from the upstream bug report) - in a fresh Bionic VM:

  $ sudo apt install build-essential libgtk2.0-dev
  $ cd PCRE_PoC
  $ ./compilePoC.sh
  $ ./PoC 
  Content:
  ---
  n�=
  ---
  Pattern:
  ---
  \s*=
  -
  Segmentation fault (core dumped)

  Haven't yet tested the second PoC via an external disk autorun.inf and
  gvfs-udisks2-volume-monitor.

  Also haven't tested in Cosmic / older releases

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace

2018-10-25 Thread Sebastien Bacher

Change uploaded to bionic and cosmic

** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config
(Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => Fix Committed

** Description changed:

+ * Impact
+ the airplane mode key doesn't work in GNOME
+ 
+ * Test case
+ Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used
+ 
+ * Regression potential
+ The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working
+ 
+ -
+ 
  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:
  
  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces
  the RFKill key: https://lists.freedesktop.org/archives/wayland-
  devel/2017-August/034721.html
  
  - x11-proto needs a new release. This commit added RFKill, but it is not
  in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf
  
  - Likely other X11 packages need to be rebuilt.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1740894

Title:
  KEY_RFKILL is not passed to userspace

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Committed
Status in xorgproto package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1799913] [NEW] Unhandled lockdown error (-2) - iphone ios 12

2018-10-25 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Hi!

On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on 
the Documents in the file manager, I got this error: Unhandled lockdown error 
(-2). 
I attached a screenshot about this error.

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


** Tags: bot-comment
-- 
Unhandled lockdown error (-2) - iphone ios 12
https://bugs.launchpad.net/bugs/1799913
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libimobiledevice in Ubuntu.

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1795614] Update Released

2018-10-25 Thread Łukasz Zemczak

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1795614

Title:
  packagekit frontend locking

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Fix Committed
Status in packagekit source package in Bionic:
  Fix Released
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [SRU Notes]

  [rbasak] Requires apt 1.2.28 (Xenial) and 1.6.5 (Bionic), both of
  which are currently in proposed. Do not release to updates without
  releasing the newer apt first.

  [Impact]
  PackageKit needs an adjustment for frontend locking, so it does not release 
the frontend lock during dpkg invocations, but only the normal dpkg lock.

  Frontend locking prevents race conditions between multiple dpkg
  frontends, which can cause other frontends to be interrupted while
  they are installing stuff - the frontend loses the dpkg lock between
  dpkg runs and the system ends up in a partially configured state.

  See bug 1781169 for more details on frontend locking.

  [Test case]
  1. Install a package
  2. Modify prerm to sleep
  3. Remove package via pkcon and check that packagekitd process holds 
lock-frontend and dpkg holds lock (we release lock by closing the lock files, 
so just check if the files are open).

  [Regression potential]
  Changing the code to call UnLockInner() vs UnLock() makes it do less steps 
and only release "lock" as before, and not "lock-frontend". That should not be 
causing any regressions.

  The patch also adds a call to LockInner() after the dpkg execution to
  make it reacquire "lock", this could fail. It should not have much
  impact however, as it only affects a single transaction AFAICT. It
  does reduce the risk of some frontend not implementing frontend
  locking from racing while we still hold the frontend lock, though.

  [Other info]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy

2018-10-25 Thread Launchpad Bug Tracker

This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.3

---
packagekit (1.1.9-1ubuntu2.18.04.3) bionic; urgency=medium

  * Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit
restarting while upgrading under PackageKit (LP: #1790613)

packagekit (1.1.9-1ubuntu2.18.04.2) bionic; urgency=medium

  * debian/patches/frontend-locking.diff:
Implement frontend locking in a simple way. Will need some more
work to upstream, and possibly some error checking. (LP: #1795614)
  * Bump libapt-pkg-dev build-dep to >= 1.6.5~ for frontend locking
  * debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch,
aptcc-removing-duplicate-delete-call.patch:
Fix invalid dereference and delete wrong (duplicate) "delete"
statement in providesCodec (LP: #1790671)

 -- Julian Andres Klode   Mon, 15 Oct 2018 15:46:47
+0200

** Changed in: packagekit (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790671

Title:
  
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  pkcon what-provides and other tools querying codecs do not work, they crash 
(unless you happen to be lucky with your apt cache). Also, cancalled 
transactions crash as well, even if you're lucky with your apt cache, as the 
"matcher" object is deleted twice.

  There are two reasons: A duplicate delete statement in providesCodec
  entered when cancelling the lookup, and a invalid pointer dereference
  in there.

  [Test case]
  The daemon should not crash as below, but should print a useful message.

  $ lxc launch -e ubuntu:bionic bbb
  $ lxc exec bbb apt update
  $ lxc exec bbb -- apt  -y  install packagekit
  $ lxc exec bbb pkcon what-provides  "gstreamer1.0(decoder-audio/ac3)"
  [...] The daemon crashed mid-transaction!

  (empty lxd container seems to be able to reproduce easily)

  This only tests the pointer dereference, I don't have a test for the
  duplicate. But the code is obviously correct:

   for ... [
 if (m_cancel) {
   // here used to be "delete matcher" - that's deleted
   break;
 }
   }
   delete matcher;

  That is, matcher is always deleted once now, and was always deleted
  twice when cancelling before.

  [Regression potential]
  I don't think it's possible to have a regression here, given the nature of 
the fix, but if there were one, we'd see different behavior in codec lookup.

  For the duplicate delete on cancelled transactions, you'd be looking
  at memory leaks if there were a regression.

  [Other info]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.1.10-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1795614] Re: packagekit frontend locking

2018-10-25 Thread Launchpad Bug Tracker

This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.3

---
packagekit (1.1.9-1ubuntu2.18.04.3) bionic; urgency=medium

  * Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit
restarting while upgrading under PackageKit (LP: #1790613)

packagekit (1.1.9-1ubuntu2.18.04.2) bionic; urgency=medium

  * debian/patches/frontend-locking.diff:
Implement frontend locking in a simple way. Will need some more
work to upstream, and possibly some error checking. (LP: #1795614)
  * Bump libapt-pkg-dev build-dep to >= 1.6.5~ for frontend locking
  * debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch,
aptcc-removing-duplicate-delete-call.patch:
Fix invalid dereference and delete wrong (duplicate) "delete"
statement in providesCodec (LP: #1790671)

 -- Julian Andres Klode   Mon, 15 Oct 2018 15:46:47
+0200

** Changed in: packagekit (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1795614

Title:
  packagekit frontend locking

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Fix Committed
Status in packagekit source package in Bionic:
  Fix Released
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [SRU Notes]

  [rbasak] Requires apt 1.2.28 (Xenial) and 1.6.5 (Bionic), both of
  which are currently in proposed. Do not release to updates without
  releasing the newer apt first.

  [Impact]
  PackageKit needs an adjustment for frontend locking, so it does not release 
the frontend lock during dpkg invocations, but only the normal dpkg lock.

  Frontend locking prevents race conditions between multiple dpkg
  frontends, which can cause other frontends to be interrupted while
  they are installing stuff - the frontend loses the dpkg lock between
  dpkg runs and the system ends up in a partially configured state.

  See bug 1781169 for more details on frontend locking.

  [Test case]
  1. Install a package
  2. Modify prerm to sleep
  3. Remove package via pkcon and check that packagekitd process holds 
lock-frontend and dpkg holds lock (we release lock by closing the lock files, 
so just check if the files are open).

  [Regression potential]
  Changing the code to call UnLockInner() vs UnLock() makes it do less steps 
and only release "lock" as before, and not "lock-frontend". That should not be 
causing any regressions.

  The patch also adds a call to LockInner() after the dpkg execution to
  make it reacquire "lock", this could fail. It should not have much
  impact however, as it only affects a single transaction AFAICT. It
  does reduce the risk of some frontend not implementing frontend
  locking from racing while we still hold the frontend lock, though.

  [Other info]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1799978] [NEW] Ubuntu 18.10 problem after lid close

2018-10-25 Thread exactt

Public bug reported:

Hi, I recently upgraded my Dell 9360 to Ubuntu 18.10. Ever since I
cannot login after I close the lid and reopen it. The screen is mostly
black. See attached photos. There are also some graphical errors in the
still working menues. My work around: Manually suspend the notebook and
wake it up via power button. Then I get the regular login screen.

This happens both on X and Wayland sessions.

How can I debug further? Any help much appreciated.

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

** Attachment added: "after wakup"

https://bugs.launchpad.net/bugs/1799978/+attachment/5205451/+files/IMG_20181025_165633.jpg

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1799978

Title:
Ubuntu 18.10 problem after lid close

Status in systemd package in Ubuntu:
New

Bug description:
Hi, I recently upgraded my Dell 9360 to Ubuntu 18.10. Ever since I
cannot login after I close the lid and reopen it. The screen is mostly
black. See attached photos. There are also some graphical errors in
the still working menues. My work around: Manually suspend the
notebook and wake it up via power button. Then I get the regular login
screen.

This happens both on X and Wayland sessions.

How can I debug further? Any help much appreciated.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

1 2 3 >

1 - 100 of 209 matches

Mail list logo