from:"Trent Nelson"

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

2018-08-23 Thread Trent Nelson

Tested working! Thanks!

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Fix Committed

Bug description:
  SRU for bionic:

  Acceptance criteria: An encrypted partition can be decrypted using
  cryptroot-unlock.

  Regression potential: It's not the default method, so unused by the
  majority of people. Besides that the patched script runs fine in
  cosmic.

  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

2018-06-27 Thread Trent Nelson

Thanks Dimitri!

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

2018-06-18 Thread Trent Nelson

Thanks for the confirmation @Thorsten!

Now to get some maintainer eyes on it...

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Confirmed
Status in cryptsetup package in Ubuntu:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-06-17 Thread Trent Nelson

The upstream commit to fix this issues is this one:
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/advertising.c?id=1873096352f518d3247f8efb3c2e0aa8804e50ac

I've applied it to Ubuntu's bluez 5.48 and confirmed that it works, as
expected.

Please backport!

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  In Progress
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

2018-06-12 Thread Trent Nelson

I took a crack at patching this.  Works without complaints for
cryptroot-unlock as shipped with Ubuntu 18.04 Server.

Apply with:
$ cd /usr/share/cryptsetup/initramfs/bin/
$ sudo patch -bp1 < /path/to/cryptroot-unlock-neutered-busybox-progs.patch
$ sudo update-initramfs -uk all

Problems were:
1) Busybox `ps` takes no (useful) args.
2) Busybox `grep` does not accept -z (NULL terminated line handling).
3) Busybox has no `usleep`, it DOES have a `sleep` that accepts fractional 
seconds.

** Patch added: "Fix cryptroot-unlock for neutered Busybox env"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+attachment/5151893/+files/cryptroot-unlock-neutered-busybox-progs.patch

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Confirmed
Status in cryptsetup package in Ubuntu:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1719750] [NEW] QSystemTrayIcon creates an icon in the wrong place.

2017-09-26 Thread Trent Nelson

Public bug reported:

This is probably a long shot given the age, but any chance of getting
the following patches backported to the Trusty build from upstream?

https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=d8090022f66cc6cff6af5ed2ae702212fd172ff7
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=612953a626ec21b8518ee23a4f5268b566cf41e5
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=cec103897f5109c70f2fd69460d10d21fa4feded
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=38abd653774aa0b3c5cdfd9a8b78619605230726

Upstream issue: https://bugreports.qt.io/browse/QTBUG-31762

I am experiencing this with the Dash Core Wallet, built from their git
tag v0.12.1.5.  The tray icon is being rendered outside the tray area.
Always the top-left of the left-most monitor.

Ubuntu 14.04.5 (fully patched as of posting)
libqt5core5a is at 5.2.1+dfsg-1ubuntu14.3, which should have these patches 
already being as they were merged in the 5.2 upstream series.  I did not see 
them in the source tree here on launchpad, though.

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  QSystemTrayIcon creates an icon in the wrong place.

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  This is probably a long shot given the age, but any chance of getting
  the following patches backported to the Trusty build from upstream?

  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=d8090022f66cc6cff6af5ed2ae702212fd172ff7
  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=612953a626ec21b8518ee23a4f5268b566cf41e5
  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=cec103897f5109c70f2fd69460d10d21fa4feded
  
https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1=38abd653774aa0b3c5cdfd9a8b78619605230726

  Upstream issue: https://bugreports.qt.io/browse/QTBUG-31762

  I am experiencing this with the Dash Core Wallet, built from their git
  tag v0.12.1.5.  The tray icon is being rendered outside the tray area.
  Always the top-left of the left-most monitor.

  Ubuntu 14.04.5 (fully patched as of posting)
  libqt5core5a is at 5.2.1+dfsg-1ubuntu14.3, which should have these patches 
already being as they were merged in the 5.2 upstream series.  I did not see 
them in the source tree here on launchpad, though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1719750/+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 1589605] Re: evolution-calendar-factory uses lots of memory

2017-07-10 Thread Trent Nelson

TitanKing,

I'd posted a bit less intrusive workaround at
https://askubuntu.com/a/894387/653294.

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

Title:
  evolution-calendar-factory uses lots of memory

Status in evolution package in Ubuntu:
  Invalid
Status in evolution-data-server package in Ubuntu:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Expired

Bug description:
  As filed under bug #1342123 (under Canonical System Image, i.e. for mobile 
installs) by several users, including desktop installs, 
evolution-calendar-factory (previsouly in 14.04) then 
evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of 
megabytes of memory (~ 300 Mio in my case).
  This might have to do with having lots of linked calendars (Google Agenda or 
other). Another user on my system has much fewer Google Agendas than me and her 
memory usage of evolution-calendar-factory-subprocess is less, but still close 
to 100 Mio.
  There have been random crashes of the process, mostly directly upon login, 
always caused by addressing memory out of range.
  There used to be a workaround by invoking the process a second time, which 
caused it to exit more or less gracefully. This is not the case anymore in 
16.04.
  Unfortunately, searching Google leads to the bug #1342123 which concerns 
"Canonical System Image", and several users have replied even though it does 
not only concern mobile installs, which is not immediately self-evident when 
you are not aware what "Canonical System Image" stands for…

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+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 1545308] Re: Backport upstream fix for memleak

2016-03-25 Thread Trent Nelson

Hey Brian,

I was going to let this run longer, but I think we're safe.  I've
observed RSS of both xfce4-power-manager and NetworkManager grow by over
1.5MB from usage at start up and have now dropped back to more than 1MB
below usage at start up.  These observations were made with swap
disabled, so they should be accurate.  Without the patch, both would be
~50MB over start up usage by now.

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

Title:
  Backport upstream fix for memleak

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Wily:
  Fix Committed

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=758641

  Please consider taking this memleak fix from upstream.  I've built the
  package with it locally and confirmed that it fixes the leak in xfce4
  -power-manager, which is mentioned in the upstream report.  It also
  fixes a similarly sized (hundreds of MB after a few days up time) leak
  that I have observed in the NetworkManager service.

  [Impact]
  Hundreds of MB memory leak in certain dbus applications, including default 
services like xfce4-power-manager and NetworkManager with default 
configurations.

  [Test Case]
  Clean install of lubuntu 15.10 on a notebook with working battery.  Observe 
xfce4-power-manager and NetworkManager* in "top" over 48-72hrs of normal use 
(web browsing, text editing, shell, etc).  Both will be taking on several tens 
of MB per day of additional RES.

  *NetworkManager may require buggy wifi to reproduce. rtl8723be in my
  case.

  [Regression Potential]
  I'm no authority on the glib code base, but the upstream patch looks very 
safe to me.

  Let me know if you need any further details.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libglib2.0-0 2.46.1-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Feb 13 09:58:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-25 (49 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1545308/+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 1545308] Re: Backport upstream fix for memleak

2016-03-24 Thread Trent Nelson

I finally got around to enabling the package from proposed.  I'll report
back in a few days with results.

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

Title:
  Backport upstream fix for memleak

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Wily:
  Fix Committed

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=758641

  Please consider taking this memleak fix from upstream.  I've built the
  package with it locally and confirmed that it fixes the leak in xfce4
  -power-manager, which is mentioned in the upstream report.  It also
  fixes a similarly sized (hundreds of MB after a few days up time) leak
  that I have observed in the NetworkManager service.

  [Impact]
  Hundreds of MB memory leak in certain dbus applications, including default 
services like xfce4-power-manager and NetworkManager with default 
configurations.

  [Test Case]
  Clean install of lubuntu 15.10 on a notebook with working battery.  Observe 
xfce4-power-manager and NetworkManager* in "top" over 48-72hrs of normal use 
(web browsing, text editing, shell, etc).  Both will be taking on several tens 
of MB per day of additional RES.

  *NetworkManager may require buggy wifi to reproduce. rtl8723be in my
  case.

  [Regression Potential]
  I'm no authority on the glib code base, but the upstream patch looks very 
safe to me.

  Let me know if you need any further details.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libglib2.0-0 2.46.1-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Feb 13 09:58:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-25 (49 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1545308/+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 1545308] Re: Backport upstream fix for memleak

2016-03-03 Thread Trent Nelson

Sorry, I spaced this.  Description updated. :)

** Description changed:

  https://bugzilla.gnome.org/show_bug.cgi?id=758641
  
  Please consider taking this memleak fix from upstream.  I've built the
  package with it locally and confirmed that it fixes the leak in xfce4
  -power-manager, which is mentioned in the upstream report.  It also
  fixes a similarly sized (hundreds of MB after a few days up time) leak
  that I have observed in the NetworkManager service.
+ 
+ [Impact]
+ Hundreds of MB memory leak in certain dbus applications, including default 
services like xfce4-power-manager and NetworkManager with default 
configurations.
+ 
+ [Test Case]
+ Clean install of lubuntu 15.10 on a notebook with working battery.  Observe 
xfce4-power-manager and NetworkManager* in "top" over 48-72hrs of normal use 
(web browsing, text editing, shell, etc).  Both will be taking on several tens 
of MB per day of additional RES.
+ 
+ *NetworkManager may require buggy wifi to reproduce. rtl8723be in my
+ case.
+ 
+ [Regression Potential]
+ I'm no authority on the glib code base, but the upstream patch looks very 
safe to me.
  
  Let me know if you need any further details.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libglib2.0-0 2.46.1-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Feb 13 09:58:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-25 (49 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: glib2.0
  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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1545308

Title:
  Backport upstream fix for memleak

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Wily:
  In Progress

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=758641

  Please consider taking this memleak fix from upstream.  I've built the
  package with it locally and confirmed that it fixes the leak in xfce4
  -power-manager, which is mentioned in the upstream report.  It also
  fixes a similarly sized (hundreds of MB after a few days up time) leak
  that I have observed in the NetworkManager service.

  [Impact]
  Hundreds of MB memory leak in certain dbus applications, including default 
services like xfce4-power-manager and NetworkManager with default 
configurations.

  [Test Case]
  Clean install of lubuntu 15.10 on a notebook with working battery.  Observe 
xfce4-power-manager and NetworkManager* in "top" over 48-72hrs of normal use 
(web browsing, text editing, shell, etc).  Both will be taking on several tens 
of MB per day of additional RES.

  *NetworkManager may require buggy wifi to reproduce. rtl8723be in my
  case.

  [Regression Potential]
  I'm no authority on the glib code base, but the upstream patch looks very 
safe to me.

  Let me know if you need any further details.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libglib2.0-0 2.46.1-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Feb 13 09:58:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-25 (49 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1545308/+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 1545308] Re: Backport upstream fix for memleak

2016-03-01 Thread Trent Nelson

Thanks fellas!

Iain,

Was the SRU comment directed at me or Sebastien?  I would be happy to
update what I can later this evening, but some of the information
requested there seems like it would better come from someone more
familiar with the glib code base (potential regressions, etc).

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

Title:
  Backport upstream fix for memleak

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Wily:
  In Progress

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=758641

  Please consider taking this memleak fix from upstream.  I've built the
  package with it locally and confirmed that it fixes the leak in xfce4
  -power-manager, which is mentioned in the upstream report.  It also
  fixes a similarly sized (hundreds of MB after a few days up time) leak
  that I have observed in the NetworkManager service.

  Let me know if you need any further details.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libglib2.0-0 2.46.1-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Feb 13 09:58:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-25 (49 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1545308/+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 1545308] [NEW] Backport upstream fix for memleak

2016-02-13 Thread Trent Nelson

Public bug reported:

https://bugzilla.gnome.org/show_bug.cgi?id=758641

Please consider taking this memleak fix from upstream.  I've built the
package with it locally and confirmed that it fixes the leak in xfce4
-power-manager, which is mentioned in the upstream report.  It also
fixes a similarly sized (hundreds of MB after a few days up time) leak
that I have observed in the NetworkManager service.

Let me know if you need any further details.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: libglib2.0-0 2.46.1-1
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: LXDE
Date: Sat Feb 13 09:58:03 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-12-25 (49 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: glib2.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  Backport upstream fix for memleak

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  https://bugzilla.gnome.org/show_bug.cgi?id=758641

  Please consider taking this memleak fix from upstream.  I've built the
  package with it locally and confirmed that it fixes the leak in xfce4
  -power-manager, which is mentioned in the upstream report.  It also
  fixes a similarly sized (hundreds of MB after a few days up time) leak
  that I have observed in the NetworkManager service.

  Let me know if you need any further details.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libglib2.0-0 2.46.1-1
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Feb 13 09:58:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-12-25 (49 days ago)
  InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: glib2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1545308/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Touch-packages] [Bug 1719750] [NEW] QSystemTrayIcon creates an icon in the wrong place.

[Touch-packages] [Bug 1589605] Re: evolution-calendar-factory uses lots of memory

[Touch-packages] [Bug 1545308] Re: Backport upstream fix for memleak

[Touch-packages] [Bug 1545308] Re: Backport upstream fix for memleak

[Touch-packages] [Bug 1545308] Re: Backport upstream fix for memleak

[Touch-packages] [Bug 1545308] Re: Backport upstream fix for memleak

[Touch-packages] [Bug 1545308] [NEW] Backport upstream fix for memleak

12 matches

Site Navigation

Mail list logo

Footer information