[Touch-packages] [Bug 2060326] Re: unnattended upgrades stuck burning 100% cpu

[Alexey Kharlamov]

Same here, `unattended-upgrade` hogging CPU for 10hours straight
already.

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

Title:
  unnattended upgrades stuck burning 100% cpu

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  For the last hour or so, unattended upgrades has been stuck burning
  100% of a cpu.

  series: noble
  version: 2.9.1+nmu4ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+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 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04

[Alexey Gavrilov]

I suggest a temporary solution for cron . wrap apt update in timeout -k
60 1200 or add to systemd unit add JobTimeoutSec=1200

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

Title:
  occasional hanging 'apt-get update' from daily cronjob since Jammy
  22.04

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  Yesterday I spotted several machines of ours where a period `apt-get
  update` was stalled. The `http` children were hanging in `WaitFd`
  (waiting for parent instructions/queue). The parent was looping in
  `AcquireUpdate` every 500ms.

  
  We have a cronjob that runs every few hours which calls `apt-get update` and 
does some post-processing. We noticed that several of them had stalled at some 
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.

  Example:
  ```
  # apt-get update
  Reading package lists... Done
  E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026 
(apt-get)
  N: Be aware that removing the lock file is not a solution and may break your 
system.
  E: Unable to lock directory /var/lib/apt/lists/
  ```

  Task listing:
  ```
  root  153929  \_ /usr/sbin/CRON -f -P
  root  153942  \_ /bin/sh -c  [ -x /etc/zabbix/scripts/dpkg.updates ] 
&& /etc/zabbix/scripts/dpkg.updates --cron
  root  153943  \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
  root  154026  \_ apt-get update
  _apt  154029  \_ /usr/lib/apt/methods/http
  _apt  154030  \_ /usr/lib/apt/methods/http
  _apt  154031  \_ /usr/lib/apt/methods/http
  _apt  154033  \_ /usr/lib/apt/methods/gpgv
  ```
  Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
  ```
  # netstat -apn | grep -E '154026|154029|154030|154031|154033'
  tcp  1  0  10.x.x.x:60868  217.x.x.x:80  CLOSE_WAIT  154030/http 
  tcp  1  0  10.x.x.x:40756  178.x.x.x:80  CLOSE_WAIT  154029/http 
  tcp  1  0  10.x.x.x:56818  185.x.x.x:80  CLOSE_WAIT  154031/http 
  ```
  All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL, 
NULL, NULL).

  The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
  NULL, {tv_sec=0, tv_nsec=5}, NULL).

  The http sockets in the children were at fd=3.

  Parent lsof:
  ```
  # lsof -p 154026 +E
  ...
  apt-get   154026 root4uW  REG8,10  262281 
/var/lib/apt/lists/lock
  apt-get   154026 root5r  FIFO   0,13  0t0 4015176 pipe 154029,http,1w
  apt-get   154026 root6r  FIFO   0,13  0t0 4012448 pipe 154030,http,1w
  apt-get   154026 root7r  FIFO   0,13  0t0 4015192 pipe 154031,http,1w
  apt-get   154026 root8w  FIFO   0,13  0t0 4015177 pipe 154029,http,0r
  apt-get   154026 root9r  FIFO   0,13  0t0 4015233 pipe 154033,gpgv,1w
  apt-get   154026 root   10w  FIFO   0,13  0t0 4012449 pipe 154030,http,0r
  apt-get   154026 root   12w  FIFO   0,13  0t0 4015193 pipe 154031,http,0r
  apt-get   154026 root   14w  FIFO   0,13  0t0 4015234 pipe 154033,gpgv,0r
  http  154029 _apt0r  FIFO   0,13  0t0 4015177 pipe 
154026,apt-get,8w
  http  154029 _apt1w  FIFO   0,13  0t0 4015176 pipe 
154026,apt-get,5r
  http  154030 _apt0r  FIFO   0,13  0t0 4012449 pipe 
154026,apt-get,10w
  http  154030 _apt1w  FIFO   0,13  0t0 4012448 pipe 
154026,apt-get,6r
  http  154031 _apt0r  FIFO   0,13  0t0 4015193 pipe 
154026,apt-get,12w
  http  154031 _apt1w  FIFO   0,13  0t0 4015192 pipe 
154026,apt-get,7r
  gpgv  154033 _apt0r  FIFO   0,13  0t0 4015234 pipe 
154026,apt-get,14w
  gpgv  154033 _apt1w  FIFO   0,13  0t0 4015233 pipe 
154026,apt-get,9r
  ```
  So:
  - apt-get is waiting for any data written by any of its four children (at fd 
5/6/7/9)
  - http and gpgv are waiting for any data written by their parent (at their 
respective fd 0)

  Parent backtrace:
  ```
  #0  0x7f420116a74d in select ()
 from /lib/x86_64-linux-gnu/libc.so.6
  #1  0x7f420153fb5d in pkgAcquire::Run(int) ()
 from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
  #2  0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) ()
 from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
  #3  0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int) 
()
 from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
  #4  0x7f42016d127b in DoUpdate (CmdL=...)
  at ./apt-private/private-update.cc:73
  #5  0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch 
const*, bool) ()
 from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
  #6  0x7f420169fa97 in DispatchCommandLine (CmdL=..., 
  Cmds=std::vector of length 27, capacity 32 = {...})
  at ./apt-private/private-cmndline.cc:588
  #7  

[Touch-packages] [Bug 2007355] [NEW] current curl and libcurl 7.81 in Ubuntu 22.04.1 LTS contain annoying bug

[Alexey Dmitriev]

Public bug reported:

Hi team,
Current curl and libcurl 7.81.0 in Ubuntu 22.04 contain annoying bug:
"cURL error 35: error:0A00010B:SSL routines::wrong version number"
It is described in curl repo there https://github.com/curl/curl/issues/9931 and 
fixed in curl and libcurl 7.87
Could you kindly update curl and libcurl packages for Ubuntu 22.04.

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


** Tags: upgrade-software-version

** Package changed: apport (Ubuntu) => curl (Ubuntu)

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

Title:
  current curl and libcurl 7.81 in Ubuntu 22.04.1 LTS contain annoying
  bug

Status in curl package in Ubuntu:
  New

Bug description:
  Hi team,
  Current curl and libcurl 7.81.0 in Ubuntu 22.04 contain annoying bug:
  "cURL error 35: error:0A00010B:SSL routines::wrong version number"
  It is described in curl repo there https://github.com/curl/curl/issues/9931 
and fixed in curl and libcurl 7.87
  Could you kindly update curl and libcurl packages for Ubuntu 22.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2007355/+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 1977545] [NEW] xrandr: Failed to get size of gamma for output default

[Alexey V. Galkin]

Public bug reported:

spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
   1920x1080  77.0*

Display setup

GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
org.gnome.SettingsDaemon was not provided by any .service files

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
Uname: Linux 4.4.0-148-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jun  3 17:50:08 2022
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:09b4]
InstallationDate: Installed on 2022-05-27 (7 days ago)
InstallationMedia: VMI 14.04 - Release amd64
MachineType: Dell Inc. Vostro 3681
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed 
root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet 
i915.alpha_support=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/13/2022
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.8.2
dmi.board.name: 0X9X1W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.2:bd01/13/2022:svnDellInc.:pnVostro3681:pvr:rvnDellInc.:rn0X9X1W:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 3681
dmi.sys.vendor: Dell Inc.
drirc:
 
 
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Jun  3 17:29:43 2022
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.11

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


** Tags: amd64 apport-bug third-party-packages trusty ubuntu

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

Title:
  xrandr: Failed to get size of gamma for output default

Status in xorg package in Ubuntu:
  New

Bug description:
  spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  77.0*

  Display setup

  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SettingsDaemon was not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jun  3 17:50:08 2022
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:09b4]
  InstallationDate: Installed on 2022-05-27 (7 days ago)
  InstallationMedia: VMI 14.04 - Release amd64
  MachineType: Dell Inc. Vostro 3681
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed 
root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet 
i915.alpha_support=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.2
  dmi.board.name: 0X9X1W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  

[Touch-packages] [Bug 1888598] Re: Pulseaudio breaks HDMI audio on sleep/wake

[Alexey Gusev]

the same problem on 21.10 
pulseaudio package 1:15.0+dfsg1-1ubuntu2

default output is reset in random order after resume from sleep.
Sometimes it stays as it was before suspend, but more often it just
changes to HDMI or dock output.

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

Title:
  Pulseaudio breaks HDMI audio on sleep/wake

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  on a fresh Ubuntu 20.04 x64 install, I've noticed some troubling bugs
  with pulseaudio after putting my system to sleep and then waking it
  up. these bugs aren't present on a fresh boot, only after resuming
  from sleep:

  - it forgets which sound output device it's set to, and always reverse to the 
motherboard's S/PDIF output.
  - I have two devices connected to my video card, one is a displayport 
monitor, and one is a home theater receiver via HDMI. it confuses the two, and 
randomly switches which device it thinks is capable of surround sound.
  - it sometimes refuses to switch to the correct audio device, and just resets 
any choice back to the internal S/PDIF, until the system is rebooted.

  as you can imagine, this a pretty frustrating state of affairs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.4
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa  3387 F pulseaudio
   /dev/snd/pcmC1D7p:   tessa  3387 F...m pulseaudio
   /dev/snd/controlC2:  tessa  3387 F pulseaudio
   /dev/snd/controlC0:  tessa  3387 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 22 18:38:42 2020
  InstallationDate: Installed on 2020-07-15 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3503
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: GRYPHON Z97
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1888598/+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 1465183] Re: ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-routes

[Alexey Lyashkov]

In fact, RedHat, Windows, MacOS don't ignore an default routes with 
classless-static_route option.
What about to add an some tunable to have same behavior in Ubuntu? It should be 
not a hard

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

Title:
  ubuntu 15.04 dhcp: option routers and option rfc3442-classless-static-
  routes

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Hi.
  Sorry for my bad english.
  Iam using  option rfc3442-classless-static-routes in my dhcp-server.

  # cat /var/lib/dhcp/dhclient.eth0.leases 
  lease {
interface "eth0";
fixed-address 192.168.120.170;
option subnet-mask 255.255.255.0;
option routers 192.168.120.1;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.120.1;
option dhcp-server-identifier 192.168.120.1;
option ntp-servers 192.168.120.1;
option rfc3442-classless-static-routes 24,10,125,0,192,168,120,110;
option broadcast-address 192.168.120.255;
option domain-name "home.xmu";
renew 1 2015/06/15 05:45:48;
rebind 1 2015/06/15 17:04:48;
expire 1 2015/06/15 20:04:48;
  }

  In other operation system:
  # route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.120.1   0.0.0.0 UG0  00 eth0
  10.125.0.0  192.168.120.110 255.255.255.0   UG0  00 eth0
  192.168.120.0   0.0.0.0 255.255.255.0   U 0  00 eth0

  In ubuntu 15.04:
  # route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  10.125.0.0  192.168.120.110 255.255.255.0   UG0  00 eth0
  192.168.120.0   0.0.0.0 255.255.255.0   U 0  00 eth0

  No default gateway!!!

  # cat /var/lib/dhcp/dhclient.leases
  lease {
interface "eth0";
fixed-address 192.168.120.169;
option subnet-mask 255.255.255.0;
option routers 192.168.120.1;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.120.1;
option dhcp-server-identifier 192.168.120.1;
option ntp-servers 192.168.120.1;
option rfc3442-classless-static-routes 24,10,125,0,192,168,120,110;
option broadcast-address 192.168.120.255;
option domain-name "home.xmu";
renew 1 2015/06/15 07:41:11;
rebind 1 2015/06/15 16:57:38;
expire 1 2015/06/15 19:57:38;
  }

  If i comment option rfc3442-classless-static-routes in my dhcp-server.
  Default gateway works fine:
  # route -n
  Kernel IP routing table
  Destination Gateway Genmask Flags Metric RefUse Iface
  0.0.0.0 192.168.120.1   0.0.0.0 UG0  00 eth0
  192.168.120.0   0.0.0.0 255.255.255.0   U 0  00 eth0

  # cat /etc/issue
  Ubuntu 15.04 \n \l

  # uname -a
  Linux wp01 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

  # aptitude show isc-dhcp-client
  Package: isc-dhcp-client 
  State: installed
  Automatically installed: no
  Version: 4.3.1-5ubuntu2.2
  Priority: important
  Section: net
  Maintainer: Ubuntu Developers 
  Architecture: amd64
  Uncompressed Size: 698 k
  Depends: libc6 (>= 2.15), libdns-export100, libirs-export91, libisc-export95, 
debianutils (>= 2.8.2), isc-dhcp-common (= 4.3.1-5ubuntu2.2), iproute2
  Suggests: resolvconf, avahi-autoipd, apparmor
  Provides: dhcp-client

  # aptitude show isc-dhcp-common
  Package: isc-dhcp-common 
  State: installed
  Automatically installed: no
  Version: 4.3.1-5ubuntu2.2
  Priority: important
  Section: net
  Maintainer: Ubuntu Developers 
  Architecture: amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1465183/+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 1873476] [NEW] incorrect status intel 8265 / 8275

[Alexey Kuznetsov]

Public bug reported:

software-properties reporting I have not working Intel 8265 / 8275
device it offer options: This device not working. grayed 1) using
iwlwifi 2) continue using manually installed drivers. grayed 3) Do not
use device

But device working fine without any manually installed drivers. I'm
using original Ubuntu 19.10 installation.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: software-properties-gtk 0.98.5
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 17 17:52:46 2020
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  incorrect status intel 8265 / 8275

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties reporting I have not working Intel 8265 / 8275
  device it offer options: This device not working. grayed 1) using
  iwlwifi 2) continue using manually installed drivers. grayed 3) Do not
  use device

  But device working fine without any manually installed drivers. I'm
  using original Ubuntu 19.10 installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 17 17:52:46 2020
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1873476/+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 1851385] Re: ubuntu 19.10 / print bug : requires authentication

[Alexey Nikitin]

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

I have the same issue on two PCs with HP LaserJet 1020 printer connected
to the Wi-Fi router on Ubuntu 19.10.

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

Title:
  ubuntu 19.10 / print bug : requires authentication

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I have 2 computers(one laptop and one desktop) which have a dual boot
  Windows / Ubuntu. My printer (Xerox WorkCentre 6015B) is plugged on a
  USB port from my modem on which my computers are connected using Wi-
  Fi.

  Since the upgrade of Ubuntu to version 19.10, I cannot print. On both
  computers I get the same message : [The printer] requires
  authentication / credentials required in order to print.

  With Ubuntu 19.04, I had absolutely no problem. I tried with a live
  USB with Ubuntu 19.04, there is no problem, the printer works. With a
  Ubuntu live 19.10, it doesn't work.

  If I plug the printer directly on a USB port on my computer, I get the
  same error message : [The printer] requires authentication /
  credentials required in order to print.

  It's the same behaviour on both computers, no I guess it must be a
  bug. Anyway I don't know which authentication I could do, with which
  ID and password ?

  Thank you very much

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov  5 15:12:07 2019
  Lpstat: device for Xerox_WorkCentre_6015B_Wi-Fi: 
smb://FREEBOX_SERVER/Xerox%20WorkCentre%206015B
  MachineType: Acer Aspire V5-571
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/Xerox_WorkCentre_6015B_Wi-Fi.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=fb8ccf3e-9970-4066-bae2-26fe4387c122 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.15
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire V5-571
  dmi.board.vendor: Acer
  dmi.board.version: V2.15
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.15
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd12/21/2012:svnAcer:pnAspireV5-571:pvrV2.15:rvnAcer:rnAspireV5-571:rvrV2.15:cvnAcer:ct9:cvrV2.15:
  dmi.product.family: Aspire V5-571
  dmi.product.name: Aspire V5-571
  dmi.product.sku: Aspire V5-571_072A_2.15
  dmi.product.version: V2.15
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1851385/+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 1370953] Re: layout switch is delayed

[Alexey Gusev]

I confirm this bug is still present in ubuntu 19.10.

My comment in gnome bug tracker: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1154#note_696130

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

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1370953] Re: layout switch is delayed

[Alexey]

Hello!

The problem is still here. In 17.10, 18.04, 18.10, 19.04 releases...

I found out that all standard layout switches are with that stupid delay. 
But somehow the alternative switching on LShift+RShift works instantly!

I spent few hours to find the place where this action is stored to move
it to standard keybindings like Shfit+Alt, but failed.

May be someone can suggest the way how to find action on key binding in
Ubuntu to do this?

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Alexey Morozov]

I've tried to boot up the recently upgraded Ubuntu Disco system in the
text mode and found, that the delay happens after the script:

1. fails to connect to lvmetad
2. falls back to device scanning
3. probes for btrfs.

I DO NOT have any btrfs volumes in the system so I would like to simply
avoid this step. I'd like to keep the ability to hibernate/resume
though, that's why I'd prefer to keep all configuration options needed
for RESUME.

I will continue to experiment and probably will take a look into the
booting script, but maybe the information gathered so far will be useful
for someone.

Installed packages [probably related to the problem]:

initramfs-tools_0.131ubuntu19
initramfs-tools-bin_0.131ubuntu19
initramfs-tools-core_0.131ubuntu19
lvm2_2.02.176-4.1ubuntu4
udisks2-lvm2_2.8.2-1
systemd_240-6ubuntu5
btrfs-progs_4.20.2-1

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.

[Alexey]

18.04 and mint 19 x64 newly installed
5 notebooks with ssd have. 

alex@NOUT:~$ systemd-analyze time
Startup finished in 10.388s (kernel) + 8.148s (userspace) = 18.536s
graphical.target reached after 8.134s in userspace

REAL STARTUP TIME  5 MINUTES!
it's really annoy mint 18 n ubuntu 16 work normal.(without systemd?)

systemd-analyze blame
6.416s NetworkManager-wait-online.service
3.319s dev-sda1.device
1.700s vboxdrv.service

[x]alex@NOUT:~$ /etc/initramfs-tools/conf.d/resume 
bash: /etc/initramfs-tools/conf.d/resume: Нет такого файла или каталога создал
no file resume, 
i create it,update initramfs, but it not helped me
[x]systemctl disable fstrim.timer  -this too not helped me
[x]install new kernel  - not helped
alex@NOUT:~$ uname -a
Linux NOUT 5.0.0-05rc1-generic #201901062130 SMP Mon Jan 
7 02:32:47 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
alex@NOUT:~$

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

Title:
  Long time booting : Failed to connect to lvmetad. Falling back to
  device scanning.

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in ubiquity source package in Bionic:
  Fix Released

Bug description:
  [SRU Justification]
  A regression in initramfs-tools causes it to autogenerate config in the 
initramfs saying to resume from any available swap devices, but references the 
swap device by UUID, which is not a canonical form for referring to LVM volumes 
(because of snapshotting, they are not unique).  Ubiquity also generates a file 
in /etc at install time which references the swap partition in the same way.  
Since the lvm2 initramfs hooks also only activate precisely those LVs that are 
detected as needed at boot, this adds an inappropriate 30-second boot delay to 
any system with swap on LVM, which includes any desktop system that was 
configured with LVM (but not full-disk encryption) at install time.

  [Test case]
  1. Install using the "Use LVM" option in the desktop installer.
  4. Reboot.
  5. Verify that dmesg shows a 30-second delay before mounting the root 
filesystem.
  6. Install initramfs-tools from bionic-proposed.
  7. Reboot.
  8. Verify that dmesg no longer shows a 30-second delay before mounting the 
root filesystem.
  9. Install using the bionic daily image that contains the ubiquity from 
bionic-proposed.
  10. Reboot.
  11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that 
there is no delay before mounting the root filesystem.

  [Regression potential]
  This makes changes to shell scripts, and shell is a perilous language. An 
unnoticed bug could cause all initramfs generation, and thus all kernel 
installation, to fail for some users. A regression could also cause a user to 
lose hiberation support that they currently have.

  [Original description]
  After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu 
installation", the
  system is very slow to reboot.

  It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to 
device scanning.",
  then waits 32 seconds, then continues as it should.

  I think this is a ubiquity bug, since the d-i based installer is not affected.
   - ubuntu-18.04-desktop-amd64.iso 
(a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected
   - xubuntu-18.04-desktop-amd64.iso 
(7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected
   - ubuntu-18.04-server-amd64.iso 
(a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not 
affected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1763611] Re: Lubuntu bionic boots slower than the other Ubuntu flavours with some SSDs

[Alexey]

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

18.04 and mint 19 x64 hve problem
no file resume

alex@NOUT:~$ /etc/initramfs-tools/conf.d/resume bash: /etc/initramfs-
tools/conf.d/resume: Нет такого файла или каталога создал

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

Title:
  Lubuntu bionic boots slower than the other Ubuntu flavours with some
  SSDs

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  See this thread at the Ubuntu Forums:

  https://ubuntuforums.org/showthread.php?t=2388799

  How come the ultra light Lubuntu Bionic needs 40 seconds from the grub
  menu to the log in screen, while the corresponding Kubuntu and Xubuntu
  Bionic can do it in 10 seconds in my Toshiba laptop?

  All the operating systems were installed from the Bionic Beta-2
  desktop 64-bit iso files and made up to date today (and reside in a
  new SSD connected via the internal SATA bay).

  -o-

  and to summarize the conclusion

  
https://ubuntuforums.org/showthread.php?t=2388799=2=13756324#post13756324

  This supports the assumption, that there are problems for Lubuntu to
  manage SSDs with 4096 byte size physical sectors. But the other
  flavours of Ubuntu can manage it.

  Let us hope that this can help the Lubuntu developer to find and
  squash the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lubuntu-desktop 0.93
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Apr 13 09:59:42 2018
  InstallationDate: Installed on 2018-04-06 (7 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405)
  SourcePackage: lubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1763611/+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

[Alexey Sys]

Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install
and applying nvidia-390

-- 
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 1795407] Re: python-apt frontend locking

[Alexey Shchukin]

Got it. Thanks for the info.

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

Title:
  python-apt frontend locking

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Add support to python-apt for frontend locking. This is a bit more 
complicated, and also requires some other restructuring:

  (1) The archives lock was only taken for a short time, when it should
  have been kept for the duration of an installation, as otherwise debs
  could disappear from archives/ while the install is running.

  (2) There was no lock handling at all. Tools essentially acquire the
  lock, and then release it before commit().

  The fix is based on the apt fix, which makes apt_pkg.SystemLock()
  manage both the frontend and the normal lock, and allows code to call
  apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
  around dpkg invocations to release the inner lock.

  Cache.commit() takes care of locking itself now. It releases the inner
  lock as needed for dpkg invocations. It also now requires
  apt_pkg.SystemLock to be hold - if it is not, it will acquire it
  itself.

  [Test case]
  1. Mark a package in the cache for install/removal and commit() - FE lock 
should be taken while dpkg is running.
  2. Mark a package in the cache for install/removal and commit() while holding 
the lock. Releasing the lock afterwards should still work correctly, and the FE 
lock should never be released
  3. Observe that the archive lock is not released until the last dpkg run

  The locking behavior can be observed via strace.

  [Regression potential]
  The dpkg lock changed the most: Some lock counting might go wrong and 
programs might fail as a result. Any problems will be isolated, though - dpkg 
still acquires its locks, and if a lock miscount happens, apt would not tell 
dpkg to skip acquiring the frontend lock, so even if we were losing the lock 
anywhere, dpkg would still try to acquire it and not run unlocked.

  The archive lock done by commit()/fetch_archives() in apt.Cache() is
  now hold as long as the fetcher object exists though (as it uses the
  fetcher's get_lock method), which might cause unexpected behavior in
  apps not expecting that.

  The lists/ lock is unaffected by the changes, so there should not be
  any regressions when it comes to updating index files.

  [Other info (1)]
  CI changes: There were some improvements to type hints for mypy needed to 
make type checks pass, and changes to the CI's Dockerfile to pull a new apt 
from the apt stable PPA (as a new enough apt is only in unapproved atm). 
Neither of those files are used anywhere outside of the package, so they should 
not cause any problems.

  [Other info (2)]
  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

  - This SRU depends on the apt SRU above, and breaks unattended-
  upgrades in bionic without its SRU due to a bug in the u-u code in
  handling the new API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1795407] Re: python-apt frontend locking

[Alexey Shchukin]

Hello! Is there any change this fix will be backported to ubuntu/trusty?

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

Title:
  python-apt frontend locking

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Committed
Status in python-apt source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Add support to python-apt for frontend locking. This is a bit more 
complicated, and also requires some other restructuring:

  (1) The archives lock was only taken for a short time, when it should
  have been kept for the duration of an installation, as otherwise debs
  could disappear from archives/ while the install is running.

  (2) There was no lock handling at all. Tools essentially acquire the
  lock, and then release it before commit().

  The fix is based on the apt fix, which makes apt_pkg.SystemLock()
  manage both the frontend and the normal lock, and allows code to call
  apt_pkg.pkgsystem_unlock_inner() and apt_pkg.pkgsystem_lock_inner()
  around dpkg invocations to release the inner lock.

  Cache.commit() takes care of locking itself now. It releases the inner
  lock as needed for dpkg invocations. It also now requires
  apt_pkg.SystemLock to be hold - if it is not, it will acquire it
  itself.

  [Test case]
  1. Mark a package in the cache for install/removal and commit() - FE lock 
should be taken while dpkg is running.
  2. Mark a package in the cache for install/removal and commit() while holding 
the lock. Releasing the lock afterwards should still work correctly, and the FE 
lock should never be released
  3. Observe that the archive lock is not released until the last dpkg run

  The locking behavior can be observed via strace.

  [Regression potential]
  The dpkg lock changed the most: Some lock counting might go wrong and 
programs might fail as a result. Any problems will be isolated, though - dpkg 
still acquires its locks, and if a lock miscount happens, apt would not tell 
dpkg to skip acquiring the frontend lock, so even if we were losing the lock 
anywhere, dpkg would still try to acquire it and not run unlocked.

  The archive lock done by commit()/fetch_archives() in apt.Cache() is
  now hold as long as the fetcher object exists though (as it uses the
  fetcher's get_lock method), which might cause unexpected behavior in
  apps not expecting that.

  The lists/ lock is unaffected by the changes, so there should not be
  any regressions when it comes to updating index files.

  [Other info (1)]
  CI changes: There were some improvements to type hints for mypy needed to 
make type checks pass, and changes to the CI's Dockerfile to pull a new apt 
from the apt stable PPA (as a new enough apt is only in unapproved atm). 
Neither of those files are used anywhere outside of the package, so they should 
not cause any problems.

  [Other info (2)]
  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

  - This SRU depends on the apt SRU above, and breaks unattended-
  upgrades in bionic without its SRU due to a bug in the u-u code in
  handling the new API.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1795407/+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 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)

[Alexey Zagarin]

I have a similar issue. I'm trying to get the mic working on Beats X
headset. These series of patches helped me to solve the issue:

https://patchwork.freedesktop.org/patch/178198/
https://patchwork.freedesktop.org/patch/178199/
https://patchwork.freedesktop.org/patch/178200/
https://patchwork.freedesktop.org/patch/178201/

Can we get them upstream?
I'm on Ubuntu 18.04.

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

Title:
  Bluetooth audio stuck in A2DP profile ([pulseaudio] module-
  bluez5-device.c: Refused to switch profile to headset_head_unit: Not
  connected)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I've got a pair of Parot Zik bluetooth headphones, with inbuilt
  microphones and such.

  The Sound control panel offers a “Profile” dropdown, with choice of
  A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add
  an input source to the “Inputs” tab, and (b) doesn't stop the
  headphones playing stereo sound, indicating that it hasn't actually
  been switched to HSP profile (which is, AFAIK, mono).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  chris  7755 F pulseaudio
   /dev/snd/controlC1:  chris  7755 F pulseaudio
   /dev/snd/pcmC0D0c:   chris  7755 F...m pulseaudio
   /dev/snd/controlC0:  chris  7755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Jul 14 16:27:09 2017
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA1 02/20/2017
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+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 1759644] [NEW] [18.04] Regression: wired network does not work upon resume from suspend

[Alexey Balmashnov]

Public bug reported:

After upgrade to 18.04 (bionic) I've encountered the following
regression: wired network connection does not work, when system is
resumed from suspend.

Reloading the kernel driver module seems to help:
sudo modprobe -r r8169
sudo modprobe r8169

Could this be fixed structurally?

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 28 20:08:20 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-01-06 (811 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
 169.254.0.0/16 dev enp5s0 scope link metric 1000 
 192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  ethernet  1522260260 
 wo 28 mrt 2018 20:04:20 CEST  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/3  yes enp5s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
 dzente  a899e56b-4048-43a8-bc38-9212d0af383b  wifi  1493769143 
 wo 03 mei 2017 01:52:23 CEST  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp5s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/4  
Wired connection 1  7fa0c3a2-6ef0-37fd-9f9e-9029777aaf23  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp4s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  [18.04] Regression: wired network does not work upon resume  from
  suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade to 18.04 (bionic) I've encountered the following
  regression: wired network connection does not work, when system is
  resumed from suspend.

  Reloading the kernel driver module seems to help:
  sudo modprobe -r r8169
  sudo modprobe r8169

  Could this be fixed structurally?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 28 20:08:20 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-01-06 (811 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IpRoute:
   default via 192.168.0.1 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev enp5s0 scope link metric 1000 
   192.168.0.0/24 dev enp5s0 proto kernel scope link src 192.168.0.107 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-03-21 (6 days ago)
 

[Touch-packages] [Bug 1732876] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Evgraphov Alexey]

I found a solution. There was the printer driver earlier installed that
I downloaded from the supplier's website. Printer model Xerox wc3210.
After uninstalling the driver all work properly.

** Description changed:

  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:
  
  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)
  
  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
-  600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
-  640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
+  600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
+  640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.2
-  apt  1.2.24
+  dpkg 1.18.4ubuntu1.2
+  apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:

  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732876/+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 1732876] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Evgraphov Alexey]

I found a solution. There was the printer driver earlier installed that
I downloaded from the supplier's website. Printer model Xerox wc3210.
After uninstalling the driver all work properly.

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:

  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732876/+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 1732876] [NEW] package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Evgraphov Alexey]

Public bug reported:

I just see message box in time of start ubuntu.
Yesterday I've installed packages:

git (1:2.7.4-0ubuntu1.3)
git-man (1:2.7.4-0ubuntu1.3)
liberror-perl (0.17-1.2)

libncurses5-dev (6.0+20160213-1ubuntu1)
libtinfo-dev (6.0+20160213-1ubuntu1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.12
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
CrashReports:
 600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
 640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
Date: Fri Nov 17 11:58:02 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-11-10 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732876/+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 1370953] Re: layout switch is delayed

[Alexey Nezhdanov]

The worst thing one can do it so maintain his position instead of apologising 
after being rude and being called out on that.
At least one workaround was proposed even in this very thread.

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10

[Alexey Balmashnov]

Another possible duplicate:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262

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

Title:
  No network connectivity after upgrade from 16.04 to 16.10

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Released
Status in network-manager source package in Zesty:
  In Progress

Bug description:
  Impact
  --
  When upgrading from Xenial (with all updates installed) to Yakkety you will 
boot to a system without networking - sad!

  Test Case
  -
  1) Boot a xenial desktop system
  2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed
  3) Upgrade to yakkety
  4) Reboot
  5) Observe you have no network

  If you install the version of network-manager from yakkety-proposed
  before rebooting you should have a network connection after you
  reboot.

  1) Boot a xenial desktop system.
  2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is 
installed.
  3) Install netplan, configure to set up static network on an ethernet device 
using netplan.
  4) Upgrade to yakkety
  5) Reboot
  6) Observe that your system is still being managed by networkd rather than 
NetworkManager.

  
  Regression Potential
  

  Any failure to manage ethernet or wireless devices after upgrade, or
  issues with the use of netplan in conjunction with NetworkManager
  should be investigated as potential regressions. For example, if after
  upgrading, ethernet devices are no longer managed, or if devices that
  should be explicitly ignored by NetworkManager due to existing user
  configuration are now managed, these would indicate a possible
  regression caused by this update.

  Original Description
  

  nplan was installed during the upgrade process but I had no network
  connectivity after upgrading. Apparently, no package wanted to manage
  my ethernet connection.

  ProblemType: BugDistroRelease: Ubuntu 16.10
  Package: ubuntu-release-upgrader-core 1:16.10.10
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Mar 27 11:34:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-16 (1531 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago)
  VarLogDistupgradeTermlog:

  modified.conffile..etc.update-manager.meta-release: [modified]
  mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1370953] Re: layout switch is delayed

[Alexey Nezhdanov]

Alex, how much did you pay for your copy of Ubuntu?

The problem is frustrating, but:
1) these people don't owe you anything
2) this is FOSS - go and do it yourself
3) solutions do exist.

Drop that tone!

Am 29.08.2017 9:55 nachm. schrieb "Alex" :

> what the f*cking bullshit 21st century and you can't solve this
> annoying bug during several years??? F*ck your bloody UNITY and solve this
> simplest and most important problem!!!
> how to use the system if not possible to switch layout normally???
> shit! shit! shit!
>
> Ubuntu 17.04
>
> uname -a
> Linux 4.10.0-33-generic #37-Ubuntu SMP Fri Aug 11 10:53:59 UTC 2017 i686
> i686 i686 GNU/Linux
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1370953
>
> Title:
>   layout switch is delayed
>
> Status in console-setup package in Ubuntu:
>   Confirmed
> Status in gconf package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I have two layouts configured En and Ru with Ctrl-Shift as layout
>   switch combo.
>
>   When I start typing in wrong layout I notice it, hit Ctrl-Shift and type
> again, but more often than not it is wrong layout again.
>   I repeat the action, but there is no luck. On the third attemt it
> usually either works OR the first letter is still in wrong layout, but the
> second is in correct one - i.e. layout switches as I type.
>
>   The explanation for this is that layout switch takes very unreasonable
>   time - much longer than it is needed to move your fingers from  one
>   key to the other. Each time I encounter the error I retry slower so on
>   the third attempt it is slow enough to actually recognize that layout
>   switch is happening, but with a delay.
>
>   This is extremely annoying and unacceptable. If someone knows how to
>   work around it - please post your suggestions here. It would be nice
>   to have a solution for 3+ layouts setup as well.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/console-setup/+
> bug/1370953/+subscriptions
>

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1688433] [NEW] qBittorrent or any qt 5 applications still crashing on ubuntu 16.10

[Alexey Ivanov]

Public bug reported:


https://bugs.launchpad.net/ubuntu/+source/qbittorrent/+bug/1630848

https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765

Meanwhile it still not fixed in Ubuntu 16.10 Yakkety. Since 2016-10-21
"patch" was backported from qt 5.8. All Qt5 applications with plugin
architecture creahing on exit.

Like typical strace from qbittorrent:

#0  0x77eba5df in QNetworkConfiguration::~QNetworkConfiguration() () 
from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#1  0x75eda019 in QHashData::free_helper(void (*)(QHashData::Node*)) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x77ecd06f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
#3  0x75e77ed3 in QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x76050a2c in QCoreApplicationPrivate::cleanupThreadData() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7639a84b in QGuiApplicationPrivate::~QGuiApplicationPrivate() () 
from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#6  0x77524869 in QApplicationPrivate::~QApplicationPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#7  0x760862c7 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x76052ec6 in QCoreApplication::~QCoreApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x77526331 in QApplication::~QApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

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

Title:
  qBittorrent or any qt 5 applications still crashing on ubuntu 16.10

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

Bug description:
  
  https://bugs.launchpad.net/ubuntu/+source/qbittorrent/+bug/1630848

  https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630765

  Meanwhile it still not fixed in Ubuntu 16.10 Yakkety. Since 2016-10-21
  "patch" was backported from qt 5.8. All Qt5 applications with plugin
  architecture creahing on exit.

  Like typical strace from qbittorrent:

  #0  0x77eba5df in QNetworkConfiguration::~QNetworkConfiguration() () 
from /usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #1  0x75eda019 in QHashData::free_helper(void (*)(QHashData::Node*)) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #2  0x77ecd06f in ?? () from 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5
  #3  0x75e77ed3 in QThreadStorageData::finish(void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #4  0x76050a2c in QCoreApplicationPrivate::cleanupThreadData() () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #5  0x7639a84b in QGuiApplicationPrivate::~QGuiApplicationPrivate() 
() from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
  #6  0x77524869 in QApplicationPrivate::~QApplicationPrivate() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
  #7  0x760862c7 in QObject::~QObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #8  0x76052ec6 in QCoreApplication::~QCoreApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #9  0x77526331 in QApplication::~QApplication() () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1688433/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alexey]

This is the exact discription of who my trackpoint works on Ubuntu now:

 I am unable to achieve acceptable results with all the different knobs
that are available. If I tune down acceleration, I am able to do
detailed pointing, but the stick is generally so slow, that it takes
ages to cross the screen. On the other hand, if I increase the
acceleration, even the slightest movement of the stick makes it jump
significantly on the screen so that I am unable to do detailed
selections.

https://bugs.freedesktop.org/show_bug.cgi?id=99860
here is the thread.
I'm not sure 

Seems like acceleration is now working corretly. How can I find more
info about how this works?

** Bug watch added: freedesktop.org Bugzilla #99860
   https://bugs.freedesktop.org/show_bug.cgi?id=99860

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1370953] Re: layout switch is delayed

[Alexey Kachalov]

I have this bug on Ubuntu 16.04 x64 too.
Some people say switching to setxkbmap helps: https://toster.ru/q/72254

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

[Alexey]

Unchecking "Auto power-on" in Blueman PowerManager plugin configuration
solved this issue for me.

Additionally (or alternatively) consider unchecking "Blueman Applet" in
"Startup Applications Preferences".

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1675934] Re: Screen corruption after resuming system from suspend

[Alexey Balmashnov]

** Attachment added: "bug_2017-03-24_22-22-32.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+attachment/4845050/+files/bug_2017-03-24_22-22-32.png

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

Title:
  Screen corruption after resuming system from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Upon resuming system from suspend I observe graphical artefacts.

  This is a regression, since I've noticed this behaviour only after
  latest updates.

  Rebooting system resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar 24 22:20:38 2017
  DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed
   nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4]
  InstallationDate: Installed on 2016-01-06 (442 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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.2
  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: Thu Mar 23 19:44:08 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+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 1675934] [NEW] Screen corruption after resuming system from suspend

[Alexey Balmashnov]

Public bug reported:

Upon resuming system from suspend I observe graphical artefacts.

This is a regression, since I've noticed this behaviour only after
latest updates.

Rebooting system resolves the issue.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
Uname: Linux 4.4.0-67-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Mar 24 22:20:38 2017
DistUpgraded: 2016-02-24 21:53:29,420 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-66-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-67-generic, x86_64: installed
 nvidia-375, 375.39, 4.4.0-67-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASRock Incorporation GF108M [GeForce GT 540M] [1849:0df4]
InstallationDate: Installed on 2016-01-06 (442 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-67-generic.efi.signed 
root=UUID=d4f27b9e-0cff-49e1-8392-a41aa520bd85 ro noprompt persistent quiet 
splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-02-24 (394 days ago)
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: HM65-MXM
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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.2
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: Thu Mar 23 19:44:08 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial

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

Title:
  Screen corruption after resuming system from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Upon resuming system from suspend I observe graphical artefacts.

  This is a regression, since I've noticed this behaviour only after
  latest updates.

  Rebooting system resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-67.88-generic 4.4.49
  Uname: Linux 4.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  

[Touch-packages] [Bug 1652253] ProcEnviron.txt

[Alexey Bazhin]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1652253/+attachment/4808955/+files/ProcEnviron.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1652253/+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 1652253] Re: Xorg crash

[Alexey Bazhin]

apport information

** Tags added: apport-collected

** Description changed:

  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-11-18 (68 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: xorg 1:7.7+13ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
+ Tags:  yakkety
+ Uname: Linux 4.8.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1652253/+attachment/4808953/+files/Dependencies.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 

[Touch-packages] [Bug 1652253] JournalErrors.txt

[Alexey Bazhin]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1652253/+attachment/4808954/+files/JournalErrors.txt

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1652253/+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 1652253] [NEW] Xorg crash

[Alexey Bazhin]

Public bug reported:

[  3122.921] (EE) 
[  3122.921] (EE) Backtrace:
[  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
[  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
[  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
[  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
[  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
[  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
[  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
[  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
[  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
[  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
[  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
[  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
[  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf1) 
[0x7fcac3f703f1]
[  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
[  3122.922] (EE) 
[  3122.922] (EE) Bus error at address 0x7fcaa65ab400
[  3122.922] (EE) 
Fatal server error:
[  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
[  3122.922] (EE) 
[  3122.922] (EE)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Dec 23 11:53:30 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-11-18 (34 days ago)
InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug crash yakkety

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1652253/+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 1617637] Re: wget crashing in libc if using screen output

[Alexey]

I've got the same problem. -nv solved it, thanks

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

Title:
  wget crashing in libc if using screen output

Status in wget package in Ubuntu:
  New

Bug description:
  I got wget crashing repeatetly in libc if verbose or progress is enable.
  If use "-nv" flag it does not crash.

  This is dmesg:

  [44755.426609] wget[14324]: segfault at 564d49cc7000 ip 7f95b0686328 sp 
7ffd8d1066c8 error 6 in libc-2.23.so[7f95b0514000+1c]
  [44760.175689] wget[14336]: segfault at 56409e4cd000 ip 7f12bb66e328 sp 
7fff63a84d68 error 6 in libc-2.23.so[7f12bb4fc000+1c]
  [44827.776604] wget[16986]: segfault at 55b4cd4e5000 ip 7f7917462328 sp 
7fff996f6a48 error 6 in libc-2.23.so[7f79172f+1c]
  [44831.555214] wget[17010]: segfault at 56549efa1000 ip 7f62d4acb328 sp 
7ffc9f4039a8 error 6 in libc-2.23.so[7f62d4959000+1c]

  
  This is a strace of the command:

  write(2, "Berserk_.mp4   "..., 189Berserkmp4 
2%[+>   
 ]   9,72M   395KB/s   ) = 189
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 949998})
  read(3, 
"\214\22\366SA\276\312\344L\"\274:oD[\210\246\222,N\362w\253\310\\2A\360|\306\333;"...,
 8192) = 8192
  write(4, 
"\214\22\366SA\276\312\344L\"\274:oD[\210\246\222,N\362w\253\310\\2A\360|\306\333;"...,
 4096) = 4096
  write(4, 
"j\312\177l\367o\264\2220C\330\364\326Fc\375\200\303\213wa\356\237y,\236\212\315CI?\352"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"\364\264\2640:6q\245v\265\367\230\204\30\302\236\265\335\267\242\322\\\240\364L\374\274\260\3307[\r"...,
 8192) = 8192
  write(4, 
"\364\264\2640:6q\245v\265\367\230\204\30\302\236\265\335\267\242\322\\\240\364L\374\274\260\3307[\r"...,
 4096) = 4096
  write(4, 
"Og\0233\354\324v\251\211\332\274\377\322\347\214HdD(\0028\227\337v\311\334\25s\206|\2143"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"\2454\237\236\372;\357\270\276\212Kkd\2\302\272\343x\344Y*\201q\35\"\255h\225\203\17]\240"...,
 8192) = 8192
  write(4, 
"\2454\237\236\372;\357\270\276\212Kkd\2\302\272\343x\344Y*\201q\35\"\255h\225\203\17]\240"...,
 4096) = 4096
  write(4, 
"\316\263\213y\342\306\253\251x&\355\377m\367}\215\217Y\363\356\330}!]\326\326R\334\25!\306\236"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"\302h\211\244\325\32\275\326'D6E\325Y/f\200w\n\25\277n]\26\362\16~b\265.\222\322"...,
 8192) = 8192
  write(4, 
"\302h\211\244\325\32\275\326'D6E\325Y/f\200w\n\25\277n]\26\362\16~b\265.\222\322"...,
 4096) = 4096
  write(4, 
"\327t\20\275}j\377(\201\336GF\372!i\31\3604o\377\\\273\361\347\277\326\376\3425~\313O"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"\371+*\22663e0ip\30\0017w;\376\372\243\312\235\222\212Oj\225\267\315\352t\27\372\266"...,
 8192) = 8192
  write(4, 
"\371+*\22663e0ip\30\0017w;\376\372\243\312\235\222\212Oj\225\267\315\352t\27\372\266"...,
 4096) = 4096
  write(4, 
"[3\276(\205\244\3144\236\216\\\220\215\267\"Q\22\262\261P\364\332\204\344n1\fP\320\235\16s"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"\377\371\257\274\257\244\266/C$\257\341EpU\352\3410\325F\265r\221\271\331\227w\344\v\376\34\5"...,
 8192) = 8192
  write(4, 
"\377\371\257\274\257\244\266/C$\257\341EpU\352\3410\325F\265r\221\271\331\227w\344\v\376\34\5"...,
 4096) = 4096
  write(4, 
"\23P\272\345\211E\324Jo\367T*\v\366D\362\211~\10u\34\253\10Gh\265&\206\20\321{\f"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"(\315\265\366\307\224\32\30\245v\376\256\204\210d\311\250\315,|8\227#o\317\234\5L\21Zr\224"...,
 8192) = 8192
  write(4, 
"(\315\265\366\307\224\32\30\245v\376\256\204\210d\311\250\315,|8\227#o\317\234\5L\21Zr\224"...,
 4096) = 4096
  write(4, 
"\373\206\30\205\3\177Z\270\f\3rI\236s\244\340\377\3259\204\300\274\220W\330\7E\231\nU\301\257"...,
 4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"_\3117_?M\362ae\263\267\177HtS\206\24\260\364\341\374\217\213\351I\342\345q\372\r\36\350"...,
 8192) = 8192
  write(4, 
"_\3117_?M\362ae\263\267\177HtS\206\24\260\364\341\374\217\213\351I\342\345q\372\r\36\350"...,
 4096) = 4096
  write(4, 
"\27&\311\263\362\f\33AgYC\224R\224l\245!1\251\353\366'#jd\35tA\202T4\301"..., 
4096) = 4096
  select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94})
  read(3, 
"\262\351A\237\267f\377\365N\335\326rm\360\277\313D\364gC\2001\10\216\0\0\2c\1\237-D"...,
 8192) = 8192
  write(4, 

[Touch-packages] [Bug 1604733] [NEW] package libc6 2.19-0ubuntu6.9 failed to install/upgrade: пакет с именем «libc6» не установлен, настройка невозможна

[Alexey]

Public bug reported:

I was try to install libXp-1.0.0-8.1.el5 RPM for i386 from
http://rpmfind.net/linux/RPM/centos/5.11/i386/CentOS/libXp-1.0.0-8.1.el5.i386.html

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libc6 2.19-0ubuntu6.9
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Wed Jul 20 15:26:03 2016
Dependencies:
 gcc-4.9-base 4.9.3-0ubuntu4
 libc6 2.19-0ubuntu6.9
 libgcc1 1:4.9.3-0ubuntu4
 multiarch-support 2.19-0ubuntu6.7
ErrorMessage: пакет с именем «libc6» не установлен, настройка невозможна
InstallationDate: Installed on 2015-03-02 (505 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.11
SourcePackage: eglibc
Title: package libc6 2.19-0ubuntu6.9 failed to install/upgrade: пакет с именем 
«libc6» не установлен, настройка невозможна
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package libc6 2.19-0ubuntu6.9 failed to install/upgrade: пакет с
  именем «libc6» не установлен, настройка невозможна

Status in eglibc package in Ubuntu:
  New

Bug description:
  I was try to install libXp-1.0.0-8.1.el5 RPM for i386 from
  
http://rpmfind.net/linux/RPM/centos/5.11/i386/CentOS/libXp-1.0.0-8.1.el5.i386.html

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6 2.19-0ubuntu6.9
  ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
  Uname: Linux 3.13.0-79-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Jul 20 15:26:03 2016
  Dependencies:
   gcc-4.9-base 4.9.3-0ubuntu4
   libc6 2.19-0ubuntu6.9
   libgcc1 1:4.9.3-0ubuntu4
   multiarch-support 2.19-0ubuntu6.7
  ErrorMessage: пакет с именем «libc6» не установлен, настройка невозможна
  InstallationDate: Installed on 2015-03-02 (505 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.11
  SourcePackage: eglibc
  Title: package libc6 2.19-0ubuntu6.9 failed to install/upgrade: пакет с 
именем «libc6» не установлен, настройка невозможна
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1604733/+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 1546733] Re: Update of today screen messes up scopes layout.

[Alexey Balmashnov]

+1

On Fri, Jun 3, 2016 at 3:26 AM, Anupam <1546...@bugs.launchpad.net>
wrote:

> just experienced once again, even after updating to OTA-11
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
>   Update of today screen messes up scopes layout.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions
>

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1570040] [NEW] [Feature request] In dual-SIM configurations show SIM-card used in call list

[Alexey Balmashnov]

Public bug reported:

In dual-SIM configurations, when phone receives a call, SIM-card in use
is being indicated. The list of calls does not show this information,
however. It is only available in the call details.

Providing this information in a list of calls will help user to phone
back using appropriate SIM-card/phone number. Moreover, it would be
logical to select the SIM card used to receive the call for placing an
outgoing call.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [Feature request] In dual-SIM configurations show SIM-card used in
  call list

Status in dialer-app package in Ubuntu:
  New

Bug description:
  In dual-SIM configurations, when phone receives a call, SIM-card in
  use is being indicated. The list of calls does not show this
  information, however. It is only available in the call details.

  Providing this information in a list of calls will help user to phone
  back using appropriate SIM-card/phone number. Moreover, it would be
  logical to select the SIM card used to receive the call for placing an
  outgoing call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1570040/+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 1551976] Re: Headphones not activated after unplugging/plugging-in

[Alexey Balmashnov]

Puzzled...
Was this instruction for me to do something???

On Wed, Mar 2, 2016 at 12:51 AM, Raymond <1551...@bugs.launchpad.net>
wrote:

> ports: analog-input-front-mic: Front Microphone (priority 8500, latency
> offset 0 usec, available: no) properties: device.icon_name = "audio-
> input-microphone" analog-input-rear-mic: Rear Microphone (priority 8200,
> latency offset 0 usec, available: no) properties: device.icon_name =
> "audio-input-microphone" analog-input-linein: Line In (priority 8100,
> latency offset 0 usec, available: no) properties: analog-output-lineout:
> Line Out (priority 9900, latency offset 0 usec, available: no)
> properties: analog-output-headphones: Headphones (priority 9000, latency
> offset 0 usec, available: yes) properties: device.icon_name = "audio-
> headphones" iec958-stereo-output: Digital Output (S/PDIF) (priority 0,
> latency offset 0 usec, available: unknown) properties:
>
> Seem no line out plugged, do pulseaudio switch to digial after headphone
> is unplugged
>
> ** Changed in: alsa-driver (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1551976
>
> Title:
>   Headphones not activated after unplugging/plugging-in
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+subscriptions
>

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

Title:
  Headphones not activated after unplugging/plugging-in

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  Expected behavior:
  Sound is played-back via headphones, when they are plugged-in.

  Observed behavior:
  Unplugging/plugging-in headphones disables headphones sound.

  To restore sound, user needs to go to sound settings, and switch
  "Output" to "Headphones"

  This is a regression from 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1692 F pulseaudio
   /dev/snd/controlC0:  alexei 1692 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  1 22:43:40 2016
  InstallationDate: Installed on 2016-01-06 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+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 1551976] [NEW] Headphones not activated after unplugging/plugging-in

[Alexey Balmashnov]

Public bug reported:

Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

Expected behavior:
Sound is played-back via headphones, when they are plugged-in.

Observed behavior:
Unplugging/plugging-in headphones disables headphones sound.

To restore sound, user needs to go to sound settings, and switch
"Output" to "Headphones"

This is a regression from 15.10.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
Uname: Linux 4.4.0-8-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alexei 1692 F pulseaudio
 /dev/snd/controlC0:  alexei 1692 F pulseaudio
CurrentDesktop: Unity
Date: Tue Mar  1 22:43:40 2016
InstallationDate: Installed on 2016-01-06 (54 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
Playback problem
UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago)
dmi.bios.date: 09/16/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: HM65-MXM
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Headphones not activated after unplugging/plugging-in

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  Expected behavior:
  Sound is played-back via headphones, when they are plugged-in.

  Observed behavior:
  Unplugging/plugging-in headphones disables headphones sound.

  To restore sound, user needs to go to sound settings, and switch
  "Output" to "Headphones"

  This is a regression from 15.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alexei 1692 F pulseaudio
   /dev/snd/controlC0:  alexei 1692 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  1 22:43:40 2016
  InstallationDate: Installed on 2016-01-06 (54 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [To Be Filled By O.E.M., Realtek ALC892, Green Headphone Out, Front] 
Playback problem
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (6 days ago)
  dmi.bios.date: 09/16/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: HM65-MXM
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd09/16/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnHM65-MXM:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1551976/+subscriptions

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

Re: [Touch-packages] [Bug 1546733] Re: Update of today screen messes up scopes layout.

[Alexey Balmashnov]

Interesting...

Pawel: Could you please provide a couple of words, why change of status to
invalid?

P.S. Maybe a good idea to always provide a short rationale for change of
status?

On Thu, Feb 18, 2016 at 1:06 PM, Pawel Stolowski <1546...@bugs.launchpad.net
> wrote:

> ** Changed in: unity-scopes-shell (Ubuntu)
>Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
>   Update of today screen messes up scopes layout.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions
>

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] [NEW] Update of today screen messes up scopes layout.

[Alexey Balmashnov]

Albert: No, after reboot refresh works OK.

On Thursday, February 18, 2016, Albert Astals Cid <
albert.ast...@canonical.com> wrote:
> Alexey: If you reboot can you get
> https://launchpadlibrarian.net/240240439/step01.png just by pulling down
> the today scope to refresh?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1546733
>
> Title:
>   Update of today screen messes up scopes layout.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/today-scope/+bug/1546733/+subscriptions
>

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.

[Alexey Balmashnov]

Nope, no sign of .crash files.

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.

[Alexey Balmashnov]

** Attachment added: "scope-registry.log"
   
https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573922/+files/scope-registry.log

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.

[Alexey Balmashnov]

** Attachment added: "unity8.log"
   
https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573921/+files/unity8.log

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1546733] Re: Update of today screen messes up scopes layout.

[Alexey Balmashnov]

** Attachment added: "unity8-dash.log"
   
https://bugs.launchpad.net/today-scope/+bug/1546733/+attachment/4573920/+files/unity8-dash.log

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

Title:
  Update of today screen messes up scopes layout.

Status in Today Scope:
  New
Status in unity-scopes-shell package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  BQ4.5, OTA9, official channel.

  Observed the following:
  * Upon updating today screen (swipe-down) get partially updated info, see 
attached step01.png
  * Activating side bar/pressing on Ubuntu icon shows that the rest of scopes 
were updated, but they somehow ended up above today screen controls, see 
attached step02.png
  * Activating side bar again makes it look like on attached step03.png
  * Finally, pressing on Ubuntu icon once more results in empty today screen, 
step04.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/today-scope/+bug/1546733/+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 1446865]

[Alexey Chernov]

I'm actually aware of the problem with session management since last
summer, now I've upgraded my stuff to have more KF5-based applications
and suprisingly found it still just doesn't work. So I've dived deeper
into it this time, reading all the discussion here and last part of bug
#341930, both Andreas's change proposals and the thread in the mailing-
list.

I likely agree with comment #18 of Andreas and in my point of view it is
the following:

1. As a whole it's a massive regression since KDE4 which affects all Qt5
applications, most of which behave correctly as a session clients. Even
server parts of both KWin and KSMServer now behave correctly, thanks to
Thomas's fixes, I think. But as a whole it just doesn't work at all.

2. This problem is caused by some bug in processing session management
messages in Qt, which earlier wasn't a big pain and could be avoided,
but due to significant changes in the whole interaction process, in the
API etc. now it can't be avoided and lead to (1).

3. There's initial change (https://codereview.qt-
project.org/#/c/142232/) by Andreas, which perfectly fixes the problem
with any observable problems. It also fixes a fault in the session
management protocol implementation for at least two OSs, which is good
for Qt itself.

4. There could be potentially affected client applications which: a)
were already been ported to/written for Qt5; b) process some valuable
data which shouldn't be lost; c) would like to use session management to
prevent loss of unsaved data; d) still don't care to follow session
management protocol correctly and just exploit old hacks and errors in
its implementation, which exist historically, but now is moved to a new
place. Unfortunately, this term is a little objectless since it wasn't
mentioned any real-life application like this.

5. I completely don't like the proposed way to preserve the
compatibility with (4) and make the use case of broken session
management client implementation legal and default, but also try to
allow proper-written apps to still survive somehow, adding some strange
workarounds to Qt as closing all the windows, but not too much, or API
properties to enable proper processing of SM messages.

To sum it all up, I've applied the patch (3) and have all the session
management things back again without any other changes to KDE or
whatever, it's already released versions (KF-5.18.0, Plasma-5.5.3,
applications-15.12.1). I'll also test Windows behaviour with some toy
application. Unless any problems arise, I see no reason why this tiny
and simple (and right) fix isn't applied and merged.

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

Title:
  KDE5/Qt5 does not support session restoration

Status in KDE Base Workspace:
  Confirmed
Status in Qt:
  New
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  KDE5/Qt5 does not support proper session restoration.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+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 1446865]

[Alexey Chernov]

(In reply to Thomas Lübking from comment #26)
> (In reply to Alexey Chernov from comment #25)
> 
> > According to what?
> According to "This is not fixed in years and each and every session
> management code was ported as "#if 0""
> If there was some relevant interest, it would be fixed long time, since it's
> really not that hard.

Rather interesting indicator. Why don't you apply it to Qt5 or KF5 then?
What a selective vision :)

> > > Loosing your data is however relevant for everyone. And the latter is the 
> > > by
> > > far more severe issue. Restarting applications is merely an annoyance,
> > > loosing your work is truely expensive.
> 
> > Hey, how could session management be "apparently relevant for only a
> > minority of users", but fixes in its behaviour be crucial for a lot of them?
> [...]
> > Fully agree here, but we should confirm that nobody said in the beggining
> > that upstream changes were about to break session management for KF5
> > applications. It was just broken.
> 
> Errr... what?
> Session management (in terms of "please restore the desktop as I left it")
> doesn't seem very important, but if you click "logout" and *booom*, gone is
> your work of the last two hours because the application had no chance (or,
> well, listened to the wrong events) to ask you to save it, that's pretty
> important...

Hmmm... so session management "doesn't seem very important", but
there're applications which expect a) to be closed gently, and also b)
to have an opportunity to interact to the user the very special way, so
that the rest of the world is waiting for them and doesn't logout, but
it's surely not session management. Nice. Following this way we have, I
think, thousands of apps which don't use X, kernel etc. and other not so
important stuff.

> We're apparently talking past each other.
> There're two steps:
> a) logout, clients ask to save your stuff. That works (because of the close
> event)
> b) login, clients should restart. That's broken (because the close event is
> not just an event, but the window "illegally" being withdrawn during logout)
> 
> You propse to fix (b) by breaking (a) and I'm trying to convince you that
> this is a really bad idea.

The matter is just that if you like the fruitful results of some service
or protocol, you need to follow the rules of it. If you violate them and
currently it just works, it's natural that anyone can change something
internally and you are going to fail. Rather atomic thing.

My proposal is just to have library code of Qt following the proper
interaction process, which is expected by anyone who haven't read this
discussion and just wants to support session management in the
application. Nothing against any workarounds in KSMServer, KF wrappers
or anywhere else downstream.

> > bugs which should be fixed either in library and its clients. It's better to
> > fix them when no one really relies on the stability too much. It looks like
> > this time is now for KF5-based application and environment.
> Yes, we should fix KMainWindow now (if faking close events is finally not
> considered a permanent behavior despite the majority of clients will
> probably do that in return to the data commit request - with a fair share
> actually just calling close() ...) but that has absolutely no implications
> on whether it's ok to easily break away from established (even though maybe
> wrong) behavior.

There's no one accepted fix of Qt to fix anything against.
There's a way to fix applications to interact with session manager properly 
though and add some fixes and workarounds to make it work somehow, at least 
with any local Qt patch. According to the comments of 
https://codereview.qt-project.org/#/c/146566/, that's something what Andreas is 
doing.

> > No, that's just postponing and messing up the whole problem. If, as you
> > stated, almost no one implemented easy and pretty simple interaction
> > appeared in Qt5, even less would care of possible bugs and corner cases of
> > the workaround, more complex protocol with close event you propose. There
> > would be just another argument that it's just too messy, not to mention
> > already existing argument that no one uses session management.
> 
> Sorry, but I really cannot read any sense into this paragraph.
> Please try to rephrase it. The above isn't English grammar at all.

Again. Please try to reread it: https://www.kde.org/code-of-conduct/.
Hopefully, it's English would impress you more.

> > It won't be fixed until it's broken
> So you demand to jeopardize userdata because otherwise code won't be fixed.
> Sorry, but there's no way you're ever gonna convince me in this.
> Any solution that b

[Touch-packages] [Bug 1446865]

[Alexey Chernov]

(In reply to Thomas Lübking from comment #22)
> > 5. I completely don't like the proposed way to preserve the compatibility 
> > with (4) and make
> > the use case of broken session management client implementation legal and 
> > default, but
> > also try to allow proper-written apps to still survive somehow, adding some 
> > strange
> > workarounds to Qt as closing all the windows, but not too much, or API 
> > properties to enable
> > proper processing of SM messages.
>
> No ofense, but what you "like" is completely irrelevant.

Comments like this clearly don't help the discussion or solving the
problem, especially when you start your reply with them. I won't answer
you the same style, but given that it's not the first one from you, my
earnest request to you is to please respect each other and avoid such
comments in future. In case of any questions feel free to consult
https://www.kde.org/code-of-conduct/. Thank you.

> You propose to intentionally break clients by library changes in some minor
> update

Never mentioned minor update or particular version. Please don't
distort.

> to teach developers to do right

No intention to do it, but any specs probably means something like that.

> but while you might aim their face, you're gonna hit the users (and
probably yours)

Users were already hit when the significant part of functionality
important for someone's every day use case is broken. I just can't get
why it's OK to break everything for one part of users and ultimately
save broken implementation to preserve some ephemeral compatibility for
another. That's probably the biggest question for me in this thread.
Maybe I'm wrong and those who use sessions are somewhat less important
than users that sometimes save their data on quitting? It's worth
mentioning then, and I'll immediately give up.

> We had that (I kindly remind of the qDeleteAll fix ...) and it cooked up
> hell.

Still better than a couple of API methods like
"enableSpecifiedBehaviour()" or deleting and trying to catch SIGSEGV,
right?)

> commitDataRequest hardly shows up in lxr.kde.org, what means it's probably
> not used at all and aboutToQuit (which isn't used but could come to rescue)
> isn't used too much either.
>
> The BY FAR! omnipresent pattern is to listen to queryClose() which is
> called/emitted on -guess what- close events from KMainWindow.
> And that's for pretty much sure why the (wrong) behavior in QSessionManager
> exists.

If it wasn't done before for some reason, it's better to just fix the
applications, especially given that you don't need any changes in Qt to
have just the same functionality with the new approach. If it's still
too much to change while porting to Qt5/KF5, I really wonder what
porting is.

Once again: we all could already apply the fix of Andreas and be busy
fixing the necessary applications rather than keep discussing here.

> Is this behavior correct? No.
> Does this matter? NO!
>
> It's ok to spam a #warning that this behavior is shit and deprecate and kill
> it for Qt6

On the Qt6 release you would say that everyone already rely on the
workaround there was in Qt5 etc. etc. That's an endless story. By the
way, do you really think it's so much major change that it can't be
changed before Qt6? Seriously, with no API change and with just removing
unexpected actions?

> and we might even bail out (aka "fix") KMainWindow applications
> NOW by invoking queryClose() on QGuiApplicationPrivate::commitData() but
> regardless, we MUST assume this to be a global default pattern that
> applications (also beyond KDE) rely on (also because it's absolutely natural
> to intercept closing to save data and not think of closing on session end
> could be something entirely different - actually the illegal behavior
> happens to be the most sane one...)

I just kindly remind your description of current Plasma 5 and it's
application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30. It
was written months ago, but nothing changed too dramatically from then.

Even if the proper fix could break some apps, they all are *already in*
transition process, Wayland is just around the corner with another
transition process, so now it's the perfect time to fix something to
make it finally working properly rather than make life easier for now
and have this pain for years again and again.

>
> Now, *actually* closing windows to test interaction on session end is of
> course just as wrong - if the user cancels the logout by such incident, we
> should not have closed random other windows before (letting alone that it
> causes this but) - therefore I frankly do not understand what's so
> complicated about just faking a close event to serve the present "save your
> stuff" pattern in a majority in clients without causing the destructive
> close itself which may not only be a bit premature, but also triggers this
> bug.
>
> It's the least invasive solution that does not require everyone to signal
> "yes, i can sessionmanagement" (what's not 

[Touch-packages] [Bug 1446865]

[Alexey Chernov]

(In reply to Andreas Hartmetz from comment #29)
> We cannot change Qt in a way that breaks existing applications. Qt5 has not
> exactly just been released, and commercial customers value stability very
> much. Some of them even pay for Qt licenses, which is good for all Qt users,
> so really, we should not make things worse for them.

The same way commercial customers or applications would be affected with
API changes. I think, this issue (and fix) more concerns the environment
than the application itself.

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

Title:
  KDE5/Qt5 does not support session restoration

Status in KDE Base Workspace:
  Confirmed
Status in Qt:
  New
Status in plasma-workspace package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  KDE5/Qt5 does not support proper session restoration.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+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 1446865]

[Alexey Chernov]

(In reply to Thomas Lübking from comment #24)
> (In reply to Alexey Chernov from comment #23)
> 
> > Comments like this clearly don't help
> Seriously, you asked for breaking clients because that's what you'd "like"
> to do - what did you expect to hear? That's simply not an acceptable stance.

No one here presents any absolutely true point, otherwise there were no
discussion. I just wrote my point of view and emphasized that it's just
mine and not some ultimate truth.

> > Never mentioned minor update or particular version. Please don't distort.
> So you meant to schedule this for Qt6?

No. I just stated that I didn't mention any particular version, no other
implications. As to your question, I'd prefer properly test the patch,
including success scenario for the default not-aware-of-session-
management application, and release it as soon as possible.

> > Users were already hit when the significant part of functionality important
> > for someone's every day use case is broken.
> Let's be honest: session restorage is apparently relevant for only a
> minority of users.

According to what? Your assumption? It's not too evident for me, sorry.

> Loosing your data is however relevant for everyone. And the latter is the by
> far more severe issue. Restarting applications is merely an annoyance,
> loosing your work is truely expensive.

Hey, how could session management be "apparently relevant for only a
minority of users", but fixes in its behaviour be crucial for a lot of
them? Don't you contradict with yourself in these two points?

Anyway, it's very subjective and I wouldn't argue on what's more
important. I agree that data loss is the worst thing which could happen.
I just think it doesn't mean it should result in some messy API or
library code when someone's relying on the undocumented side-effects.
Just because it will surely lead to more bugs and more data loss in the
future. It's just the bugs which should be fixed either in library and
its clients. It's better to fix them when no one really relies on the
stability too much. It looks like this time is now for KF5-based
application and environment.

> Also there's absolutely NO reason why we should not care about both - except
> that you'd "like" to break client code and risk data loss for some reason
> that completely escapes me.

No, that's just postponing and messing up the whole problem. If, as you
stated, almost no one implemented easy and pretty simple interaction
appeared in Qt5, even less would care of possible bugs and corner cases
of the workaround, more complex protocol with close event you propose.
There would be just another argument that it's just too messy, not to
mention already existing argument that no one uses session management.

> > Still better than a couple of API methods like "enableSpecifiedBehaviour()"
> 
> I fully agree on that proposal to be of little help - it will be mostly
> ignored or used w/o accounting the implications.

Ok.

> > Once again: we all could already apply the fix of Andreas and be busy fixing
> > the necessary applications rather than keep discussing here.
> 
> It does NOT only affect KDE applications, there're hundreds of Qt
> applications which might have adopted this pattern - or simply don't care
> about session management itfp.
> Also the proper order is to fix and roll out clients, *then* remove the
> deprecated upstream code. That's why "=> Qt6" for this approach.

Fully agree here, but we should confirm that nobody said in the
beggining that upstream changes were about to break session management
for KF5 applications. It was just broken. Since we have what we have,
there's no other way than to start fixing it on both sides. I think
nobody is against if it would be synchronized.

> > On the Qt6 release you would say that everyone already rely on the
> > workaround there was in Qt5 etc. etc.
> 
> No. Because you would tell people during Qt5 don't do this and don't rely on
> it because it's not gonna work with Qt6, so that when things are ported to
> Qt6, client code has to be fixed.

Oh, you're too optimistic here. Why it's still not fixed during porting
on Qt5? Only because it just works. It won't be fixed until it's broken
or would be planned to fix as we discussed above.

> Breaking it now and depending client behavior on whether it's linked against
> Qt 5.6 or Qt 5.7 is plain wrong and begging for trouble.

That's again due to your assumption that session management is of lower
priority. I'm pretty sure there would be packages that would require
just most recent Qt version, and it would be acceptable. What's wrong in
relying on changes in recent Qt release and informing the maintainer of
it with more strict requirement? There're backports if someone is
interested in special cases.

> > I just kindly re

[Touch-packages] [Bug 1533631] [NEW] Failed to renew DHCPv6 lease after suspend

[Alexey Zagarin]

Public bug reported:

After fixing IPv6 address assignment (#1469346), IPv6 works fine until
sleep. On wake up ubuntu fails to renew its IPv6 lease:

Jan 13 10:47:47 ubuntu dhclient: PRC: Renewing lease on wlp3s0.
Jan 13 10:47:47 ubuntu dhclient: PRC: Rebinding lease on wlp3s0.
Jan 13 10:47:47 ubuntu dhclient: XMT: Rebind on wlp3s0, interval 9890ms.
Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): DHCPv6 state 
changed bound -> unknown
Jan 13 10:47:47 ubuntu dhclient: PRC: Address 2a02:::::b44 
depreferred.
Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): DHCPv6 state 
changed unknown -> expire
Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): canceled DHCP 
transaction, DHCP client pid 1170
Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): DHCPv6 state 
changed expire -> done

I'm not sure that it's solely NetworkManager issue (dhclient could also
be affected).

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Failed to renew DHCPv6 lease after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  After fixing IPv6 address assignment (#1469346), IPv6 works fine until
  sleep. On wake up ubuntu fails to renew its IPv6 lease:

  Jan 13 10:47:47 ubuntu dhclient: PRC: Renewing lease on wlp3s0.
  Jan 13 10:47:47 ubuntu dhclient: PRC: Rebinding lease on wlp3s0.
  Jan 13 10:47:47 ubuntu dhclient: XMT: Rebind on wlp3s0, interval 9890ms.
  Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): DHCPv6 state 
changed bound -> unknown
  Jan 13 10:47:47 ubuntu dhclient: PRC: Address 2a02:::::b44 
depreferred.
  Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): DHCPv6 state 
changed unknown -> expire
  Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): canceled DHCP 
transaction, DHCP client pid 1170
  Jan 13 10:47:47 ubuntu NetworkManager[796]:   (wlp3s0): DHCPv6 state 
changed expire -> done

  I'm not sure that it's solely NetworkManager issue (dhclient could
  also be affected).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1533631/+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 1469346] Re: DHCPv6 responses with multiple addresses applied incorrectly to interface

[Alexey Zagarin]

There is a patch exists that fixes this problem, but against more recent 
version of NetworkManager: https://bugzilla.gnome.org/show_bug.cgi?id=681764#c20
I tried to adapt it to 1.0.4 currently present in Ubuntu (and it works for me). 
However, further testing needed.

** Bug watch added: GNOME Bug Tracker #681764
   https://bugzilla.gnome.org/show_bug.cgi?id=681764

** Patch added: "nm.patch"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1469346/+attachment/4541727/+files/nm.patch

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

Title:
  DHCPv6 responses with multiple addresses applied incorrectly to
  interface

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  A DHCPv6 server may respond with multiple addresses, and is not an
  unusual case as you may wish to provide both a ULA and a global prefix
  to a common suffix. Recent versions of OpenWRT behave in this manner
  for DHCPv6.

  Network Manager is handling this *almost* correctly. Both addresses
  get applied, just not simultaneously as would be expected.

  The dhclient process is seeing both addresses, and both get processed
  by the handler, but is handled as though there were two seperate
  requests, applies the first address, promptly removes it, and replaces
  it with the second address, resulting in only the latter address
  persisting after interface setup.

  After adding the following to the upstart config for network manager,
  you can easily follow the mishandling of the response:

  --log-level=debug --log-domains=DEVICE,IP6,DHCP6

  The following are key lines from the debug logging:

  Jun 20 23:21:16 pinky-linux NetworkManager[6244]:  [1434856876.790352] 
[nm-system.c:280] sync_addresses(): (wlan0): adding address 
'2607:::ad10::61/128'
  ...

  Jun 20 23:21:17 pinky-linux NetworkManager[6244]:  [1434856877.837130] 
[nm-system.c:247] sync_addresses(): (wlan0): removing address 
'2607:::ad10::61/128'
  Jun 20 23:21:17 pinky-linux NetworkManager[6244]:  [1434856877.837526] 
[nm-system.c:280] sync_addresses(): (wlan0): adding address 
'fd5b:::10::61/128'

  In this case the global prefixed address was applied, then immediately
  replaced by the ULA prefixed one.

  So it's correctly parsing both addresses of the response as supplied
  by dhclient, but the end result is not what is expected for the given
  configuration sent from the server.

  The correct behaviour is to add/replace all addresses in the response
  as a set.

  This negates much of the usefulness of supporting DHCPv6, and is an
  impediment to integration with IPv6 networks requiring it's use.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 26 22:19:20 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-05-21 (36 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  IpRoute:
   default via 192.168.169.1 dev wlan0  proto static 
   192.168.169.0/24 dev wlan0  proto kernel  scope link  src 192.168.169.61  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-06-17T17:39:57.347300
  mtime.conffile..etc.init.network.manager.conf: 2015-06-20T23:20:39.172713
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   somewhere 1bc6a70d-cf1a-4109-8a21-71656d34685c   
802-11-wireless   1435371500   Fri 26 Jun 2015 10:18:20 PM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about 

[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS

[Alexey Balmashnov]

Wanted to apply patches from #12 and #13, but files are read-only. Looks
like I miss some knowledge. Any pointers are welcome.

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

Title:
  Shell not responsive after an incoming SMS

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1491566] Re: Greeter and edges not responsive after an incoming SMS

[Alexey Balmashnov]

Actually, I tried buttons, there was no visible reaction on the presses:
* volume buttons (even attempted to get a screenshot, but it is not present
on the phone, so it did not work)
* power button. could not even reboot the phone (or maybe have not waited
long enough? pressed on it for about a minute), had to do reboot via shell

The only part that still was updating on the screen - notification area.
Noticed, because charging was indicated upon connection of the phone to the
PC.


On Fri, Sep 4, 2015 at 10:59 AM, Launchpad Bug Tracker <
1491...@bugs.launchpad.net> wrote:

> Status changed to 'Confirmed' because the bug affects multiple users.
>
> ** Changed in: unity-system-compositor (Ubuntu)
>Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1491566
>
> Title:
>   Greeter and edges not responsive after an incoming SMS
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions
>

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

Title:
  Greeter and edges not responsive after an incoming SMS

Status in Canonical System Image:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1491566] Re: Greeter and edges not responsive after an incoming SMS

[Alexey Balmashnov]

Attaching unity8.log as advised by Pat McGowan.

** Attachment added: "unity8.log.1.gz"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1491566/+attachment/4456964/+files/unity8.log.1.gz

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

Title:
  Greeter and edges not responsive after an incoming SMS

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1491566] Re: Greeter and edges not responsive after an incoming SMS

[Alexey Balmashnov]

Observed similar issue on BQ E4.5., r25 (after OTA6 update).

Dialer locked UI.

Happened after dialing back via activation of dialer from missed call
notification (without unlocking the phone). Dialer remains on the
foreground and phone UI seems to be stuck. At the same time, icons in
the notification area are being updated (clock, battery, network
status), but there seem to be no way to access notification area or
unlock the phone.

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

Title:
  Greeter and edges not responsive after an incoming SMS

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  RC proposed MX4 r100

  This happened twice in the last two days
  Receive an incoming text
  Screen turns on and notification is shown
  notification goes away
  try to interact with the phone and nothing works
  another text message is received and the notification is displayed

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+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 1465051] Re: Lock screen does not react on input/swipes

[Alexey Balmashnov]

Once device unlocked, all functionality seems to be OK: yes, I can switch
between apps/start apps using launcher, also can switch between apps/kill
apps using swipe from right.

On Mon, Jun 15, 2015 at 10:25 AM, Michael Zanetti 
michael.zane...@canonical.com wrote:

 Once the device is unlocked, do the edges work again? I.e. Can you
 switch apps using the right edge or pull in the launcher?

 ** Changed in: unity8 (Ubuntu)
Status: Confirmed = Incomplete

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1465051

 Title:
   Lock screen does not react on input/swipes

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465051/+subscriptions


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

Title:
  Lock screen does not react on input/swipes

Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Can't get to unlock: when I try to swipe away lock screen nothing
  happens.

  Can get beyond the screen using active icons in the notification area,
  e.g. if I select battery indicator and then options, input secret code
  screen gets activated and I can access the device.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Sun Jun 14 21:42:48 2015
  InstallationDate: Installed on 2015-05-08 (37 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150508-031218)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465051/+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 1465051] [NEW] Lock screen does not react on input/swipes

[Alexey Balmashnov]

Public bug reported:

Can't get to unlock: when I try to swipe away lock screen nothing
happens.

Can get beyond the screen using active icons in the notification area,
e.g. if I select battery indicator and then options, input secret code
screen gets activated and I can access the device.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Sun Jun 14 21:42:48 2015
InstallationDate: Installed on 2015-05-08 (37 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150508-031218)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug armhf utopic

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

Title:
  Lock screen does not react on input/swipes

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Can't get to unlock: when I try to swipe away lock screen nothing
  happens.

  Can get beyond the screen using active icons in the notification area,
  e.g. if I select battery indicator and then options, input secret code
  screen gets activated and I can access the device.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.02+15.04.20150406~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Sun Jun 14 21:42:48 2015
  InstallationDate: Installed on 2015-05-08 (37 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150508-031218)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1465051/+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 1392699] Re: Can't change locale settings (e.g. language, 12/24-hour time, date format) independently

[Alexey Dokuchaev]

By reading ubuntu-system-settings/trunk/plugins/language/language-
plugin.cpp source code, it appears that this rather common problem
(preferred en_US locale and 24-hour military clock) happens because
selected language (translated to locale) is assigned *both* to the
Language and FormatsLocale of the org.freedesktop.Accounts.User
properties.

It can be fixed (until you change it with ubuntu-system-settings again)
by changing FormatsLocale after you've set your desired language, and
restarting device:

$ dbus-send --print-reply --system --dest=org.freedesktop.Accounts
/org/freedesktop/Accounts/User$UID
org.freedesktop.Accounts.User.SetFormatsLocale string:'ru_RU.UTF-8'

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

Title:
  Can't change locale settings (e.g. language, 12/24-hour time, date
  format) independently

Status in libc package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  A. Try to use US English, but with all apps using 24-hour instead of 12-hour 
time. Or:
  B. Try to use UK English, but with all apps using -MM-DD date format.

  What happens: You can't.
  What should happen: You can.

  Since Ubuntu has existed, it has used the GNU locale system. This
  system assumes that every single person using a particular locale
  wants exactly the same settings for time display, date display,
  currency display, alphabetizing, and number formatting.
  http://www.gnu.org/software/libc/manual/html_node/Effects-of-
  Locale.html

  Windows, Mac OS, and (to a lesser extent) iOS have always been more
  flexible: setting a locale sets appropriate defaults for these
  settings, but you can also change them individually. Ubuntu should do
  the same.

  This might involve changing the locale system itself, or it might
  involve changing all relevant toolkits so that they ignore the locale
  system when appropriate.

  It would also involve adding settings in System Settings to customize
  the individual locale details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libc/+bug/1392699/+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 1459451] Re: freeze after suspend

[Alexey]

I post workaround at askubuntu: 
http://askubuntu.com/questions/605563/ubuntu-14-10-issue-with-suspend?lq=1
So, problem is in nvidia driver

** Also affects: nvidia-graphics-drivers-340-updates (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  freeze after suspend

Status in nvidia-graphics-drivers-340-updates package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1) suspend
  2) try to wake up

  Frequency:
  Always

  I cannot switch between TTYs and i don't know whats wrong. I have only black 
screen with 2 prints:
  [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR*
  uncleared fifo underrun on pipe A
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU
  pipe A FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.76  Thu Jan 22 12:11:08 
PST 2015
   GCC version:  gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13)
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 28 01:13:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.19.0-18-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-18-generic, x86_64: installed
   nvidia-340, 340.76, 3.19.0-18-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-18-generic, x86_64: installed
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0866]
 Subsystem: Acer Incorporated [ALI] GeForce 820M [1025:0868]
  InstallationDate: Installed on 2015-05-25 (2 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Acer Aspire E5-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=91d68de4-e180-4852-b16f-74026d53a17e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/16/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.15
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.15:bd09/16/2014:svnAcer:pnAspireE5-571G:pvrV1.15:rvnAcer:rnEA50_HB:rvrV1.15:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.15
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Wed May 27 20:42:33 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16876 
   vendor AUO
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340-updates/+bug/1459451/+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 1404475] [NEW] Multi-Arch support

[Alexey]

Public bug reported:

libopus0 package lacks multi-arch support as for ubuntu 14.10
Running 'sudo apt-get install libopus0 libopus0:i386' fails because of this
And there is not signs of Multi-Arch: same when running 'apt-cache show 
libopus0' also

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

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

Title:
  Multi-Arch support

Status in opus package in Ubuntu:
  New

Bug description:
  libopus0 package lacks multi-arch support as for ubuntu 14.10
  Running 'sudo apt-get install libopus0 libopus0:i386' fails because of this
  And there is not signs of Multi-Arch: same when running 'apt-cache show 
libopus0' also

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1404475/+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 1360342] Re: Add Multi-arch support in libxi-dev

[Alexey]

Is it going to be ever fixed?

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

Title:
  Add Multi-arch support in libxi-dev

Status in libxi package in Ubuntu:
  New

Bug description:
  Please add Multi-arch support in libxi-dev. Would really help in
  crosscompiling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/1360342/+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 1360342] Re: Add Multi-arch support in libxi-dev

[Alexey]

It would be really nice to hear some kind of response.

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

Title:
  Add Multi-arch support in libxi-dev

Status in libxi package in Ubuntu:
  New

Bug description:
  Please add Multi-arch support in libxi-dev. Would really help in
  crosscompiling.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxi/+bug/1360342/+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 1273907] Re: multiple cups daemons running

[Alexey Zagarin]

Also had this issue.

The problem here is that one or some of the configuration utilities
(could be hplip tools also) restarts cups at some point by calling
/etc/init.d/cups restart. Since cups startup scripts were converted to
upstart jobs, at the moment of restart upstart will notice that there is
no more daemon running and will start it. So does old Sys V script. You
could easy reproduce the problem by issuing /etc/init.d/cups restart
from command line. The result will be two instances of cupsd running.

The solution is simple: get rid of old init scripts and create symlinks
to /lib/init/upstart-job in init.d.

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

Title:
  multiple cups daemons running

Status in “cups” package in Ubuntu:
  Expired

Bug description:
  On 13.10, after using system-config-printer, there will be multiple
  cups daemons running:

  root 10159 1  0 17:06 ?00:00:00 /usr/sbin/cupsd -C 
/etc/cups/cupsd.conf
  root 10163 1  0 17:06 ?00:00:01 /usr/sbin/cupsd -F

  Upstart only knows about the one with -F:

  # service cups stop
  cups stop/waiting
  root@terra:~# ps -ef | grep cups
  root 10159 1  0 17:06 ?00:00:00 /usr/sbin/cupsd -C 
/etc/cups/cupsd.conf

  This seems to cause all kinds of problems, mostly with them fighting
  over the printers.conf file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1273907/+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 1370953] Re: layout switch is delayed

[Alexey Nezhdanov]

A very bad (but still better than what we have now) workaround would be
to lock keyboard immidiately after layout switch combo is pressed and
unlock it once the layout actually switched.

This way user won't have wrong letters typed. He won't have right
letters typed either, but that will make him retry typing, not retry
switching layouts (thus extending the pain).

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

Title:
  layout switch is delayed

Status in “console-setup” package in Ubuntu:
  New

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+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 1364312] [NEW] Multiarch support

[Alexey]

Public bug reported:

Please add Multi-arch support to this package

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

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

Title:
  Multiarch support

Status in “wayland” package in Ubuntu:
  New

Bug description:
  Please add Multi-arch support to this package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1364312/+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 1360285] [NEW] multi arch support for libpng12-dev package

[Alexey]

Public bug reported:

Any chance to see multi-arch support for libpng12-dev package? That will
be very useful for crosscompiling

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

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

Title:
  multi arch support for libpng12-dev package

Status in “libpng” package in Ubuntu:
  New

Bug description:
  Any chance to see multi-arch support for libpng12-dev package? That
  will be very useful for crosscompiling

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