[Touch-packages] [Bug 1405086] [NEW] package url-dispatcher (not installed) failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2014-12-23 Thread slothy
Public bug reported:

Ungrade to ubuntu 14.10 from 14.04

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: url-dispatcher (not installed)
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Tue Dec 23 08:04:27 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
DuplicateSignature: package:url-dispatcher:(not installed):el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
InstallationDate: Installed on 2013-07-21 (519 days ago)
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
SourcePackage: url-dispatcher
Title: package url-dispatcher (not installed) failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
UpgradeStatus: Upgraded to utopic on 2014-12-23 (0 days ago)

** Affects: url-dispatcher (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade utopic

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

Title:
  package url-dispatcher (not installed) failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Ungrade to ubuntu 14.10 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: url-dispatcher (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec 23 08:04:27 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: package:url-dispatcher:(not installed):el subproceso 
script pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2013-07-21 (519 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: url-dispatcher
  Title: package url-dispatcher (not installed) failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to utopic on 2014-12-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1405086/+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 1405087] [NEW] package click-apparmor 0.2.11.2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2014-12-23 Thread slothy
Public bug reported:

Ungrade to ubuntu 14.10 from 14.04

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: click-apparmor 0.2.11.2
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Tue Dec 23 08:04:25 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
DuplicateSignature: package:click-apparmor:0.2.11.2:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
InstallationDate: Installed on 2013-07-21 (519 days ago)
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
SourcePackage: click-apparmor
Title: package click-apparmor 0.2.11.2 failed to install/upgrade: el subproceso 
script pre-removal nuevo devolvió el código de salida de error 1
UpgradeStatus: Upgraded to utopic on 2014-12-23 (0 days ago)

** Affects: click-apparmor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade utopic

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

Title:
  package click-apparmor 0.2.11.2 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  Ungrade to ubuntu 14.10 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: click-apparmor 0.2.11.2
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec 23 08:04:25 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: package:click-apparmor:0.2.11.2:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2013-07-21 (519 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.2.11.2 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to utopic on 2014-12-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1405087/+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 1405086] Re: package url-dispatcher (not installed) failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package url-dispatcher (not installed) failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in url-dispatcher package in Ubuntu:
  New

Bug description:
  Ungrade to ubuntu 14.10 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: url-dispatcher (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec 23 08:04:27 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: package:url-dispatcher:(not installed):el subproceso 
script pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2013-07-21 (519 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: url-dispatcher
  Title: package url-dispatcher (not installed) failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to utopic on 2014-12-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1405086/+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 1405087] Re: package click-apparmor 0.2.11.2 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package click-apparmor 0.2.11.2 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in click-apparmor package in Ubuntu:
  New

Bug description:
  Ungrade to ubuntu 14.10 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: click-apparmor 0.2.11.2
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec 23 08:04:25 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  DuplicateSignature: package:click-apparmor:0.2.11.2:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2013-07-21 (519 days ago)
  InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: click-apparmor
  Title: package click-apparmor 0.2.11.2 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: Upgraded to utopic on 2014-12-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1405087/+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 1405090] [NEW] Broken Cursor with Dual Screen setup ATI Radeon HD 5000/6000/7350 Series

2014-12-23 Thread tinman2501
Public bug reported:

This is very possible necromancy/a dublicate of Bug #360724.

Without any recognizeable pattern the cursor corrupts on the first of my
dual screen setup. Sometimes it is copped up vertically, sometimes the
cursor is reduced to a thin line. This is independent from the cursor
theme/style.

Taking screenshots is not possible, the mousecursor appears ok in the
pictures.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Dec 23 09:25:44 2014
InstallationDate: Installed on 2014-09-08 (105 days ago)
InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Broken Cursor with Dual Screen setup  ATI Radeon HD 5000/6000/7350
  Series

Status in xorg package in Ubuntu:
  New

Bug description:
  This is very possible necromancy/a dublicate of Bug #360724.

  Without any recognizeable pattern the cursor corrupts on the first of
  my dual screen setup. Sometimes it is copped up vertically, sometimes
  the cursor is reduced to a thin line. This is independent from the
  cursor theme/style.

  Taking screenshots is not possible, the mousecursor appears ok in the
  pictures.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Dec 23 09:25:44 2014
  InstallationDate: Installed on 2014-09-08 (105 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.1)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405090/+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 1405094] [NEW] Laptop screen stops working when DVI screen is connected at boot

2014-12-23 Thread Volodya
Public bug reported:

This problem is new with 14.10, did not exist with 14.04

What i do to reproduce:

Turn laptop off
Connect a screen via DVI
Turn computer on

What happens:

Laptop screen stops working as soon as the OS begins to boot
Once i login, it's clear that the OS thinks that the screen is working, since i 
can move my mouse into the area of that screen and move it around there. I can 
drag windows there and if i can grab them afterwards, i can move them back into 
the visible DVI screen.
Disconnecting DVI screen does *not* turn on the Laptop screen
The only way to get laptop screen to work is to boot and login without DVI and 
connect it only afterwards.

What i expect to happen:

When booting with two screens, both should work with the settings in
place.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 23 11:52:55 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1477]
   Subsystem: ASUSTeK Computer Inc. Device [1043:1477]
InstallationDate: Installed on 2014-12-22 (0 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: ASUSTeK COMPUTER INC. N76VB
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic 
root=UUID=c1b99000-5c86-4711-946a-ba820ac888d0 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N76VB.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N76VB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N76VB
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Mon Dec 22 21:31:52 2014
xserver.configfile: default
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8605 
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic

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

Title:
  Laptop screen stops working when DVI screen is connected at boot

Status in unity package in Ubuntu:
  New

Bug description:
  This problem is new with 14.10, did not exist with 14.04

  What i do to reproduce:

  Turn laptop off
  Connect a screen via DVI
  Turn computer on

  What happens:

  Laptop screen stops working as soon as the OS begins to boot
  Once i login, it's clear that the OS thinks that the screen is working, since 
i can move my mouse into the area of that screen and move it around there. I 
can drag windows there and if i can grab them afterwards, i can move them back 
into the visible DVI screen.
  Disconnecting DVI screen does *not* turn on the Laptop screen
  The only way to get laptop screen to work is to boot and login without DVI 
and connect it only afterwards.

  What i expect to happen:

  When booting with two screens, both should work with the settings in
  place.

  

[Touch-packages] [Bug 145399] Re: rhythmbox crashed with SIGSEGV in file_model_node_get_info()

2014-12-23 Thread Bug Watch Updater
** Changed in: gtk
   Status: New = Expired

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

Title:
  rhythmbox crashed with SIGSEGV in file_model_node_get_info()

Status in GTK+ GUI Toolkit:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: rhythmbox

  Listening to a music collection across the local network.

  ProblemType: Crash
  Architecture: i386
  Date: Wed Sep 26 15:33:28 2007
  DistroRelease: Ubuntu 7.10
  ExecutablePath: /usr/bin/rhythmbox
  NonfreeKernelModules: cdrom
  Package: rhythmbox 0.11.2-0ubuntu3
  PackageArchitecture: i386
  ProcCmdline: rhythmbox
  ProcCwd: /home/karl
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   ?? () from /usr/lib/libgtk-x11-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
   gtk_file_info_get_display_key ()
  Title: rhythmbox crashed with SIGSEGV in gtk_file_info_get_display_key()
  Uname: Linux novalingua 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 
i686 GNU/Linux
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev 
powerdev scanner video
  SegvAnalysis:
   Segfault happened at: 0xb77c00bf _fini+2099419:mov0xc(%eax),%eax
   PC (0xb77c00bf) ok
   source 0xc(%eax) (0x0025) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/145399/+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 1310335] Re: IPv6 renewal causes network-manager to disconnect reconnect

2014-12-23 Thread e633
The connection won't drop if i ignore the IPv6 part of the profile...
but i'm getting perfectly working global IPv6 addresses nonetheless!

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

Title:
  IPv6 renewal causes network-manager to disconnect  reconnect

Status in The Linux Mint Distribution:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  IPv6 renewal causes network manager to disconnect  reconnect

  Happens *roughly* every ten minutes.
  My network is running fully dual stack.
  The problematic option in the IPv6 part of the router's settings is
  IP Address Assignment
  - Use DHCP Server
  - Auto Config Problem presents itself only when using this one
  I have a Netgear DGND3700v2 router, firmware version V1.1.00.15_1.00.15 
(latest).

  There are 3 different PCs on WiFi and ethernet.
  Network manager settings are: one PC static IPv4, two DHCPv4 and all of them 
Automatic for IPv6.
  Linux Mint: 
  kernel 3.2.0-60 x86 network-manager version 0.9.4.0-0ubuntu4.3 (MATE)
  kernel 3.5.0-48 x64 network-manager version 0.9.6.0-0ubuntu7 (Cinnamon)
  kernel 3.11.0-12 x64 network-manager version 0.9.8.0-0ubuntu22 (MATE)

  Wifi disconnection log (repeated, ethernet reconnects seem to leave no trace 
and seem to happen slightly less frequently):
  http://pastebin.com/GUdWgRUp

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1310335/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

2014-12-23 Thread Hardkorova
Same thing on the HP's Chromebook 14 on Intel, on the latest kernels
(3.17-3.18). It happens after couple of hours of work or moments with
high CPU load. Bug brings slow redrawing in Opera (presto) and Chromium,
but Firefox refreshing stays smooth. Also, appears a high CPU
consumption by XOrg, when browsers are opened.

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

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics

  After upgrading from 14.04 to 14.10 there are a lot of places where
  the graphics are working much slower than they were before:

  - Gnome Shell Interface is very sluggish, visible chops (redrawing)
  when pressing the [Super] key.

  - Selecting text in Gedit takes a full second pr. line

  Experiences some subjective improvement when I booted kernel 3.13.0-37
  instead of 3.16.0-23, but that may be my imagination as the problem
  persists.

  I've searched google, forums, found a couple of relevant links that
  point to the issue being the Intel drivers.

  http://askubuntu.com/questions/53962...E2%86%92-14-10
  http://www.webupd8.org/2014/10/ubunt...ent-1652086424

  But the drivers currently in 14.10 should be newer than those supplied
  by Intel to 14.04 so that doesn't make sense to me. As one Intel
  developer wrote:

  I would like to point out that since what we do is bring more ecent
  versions of the software to the target distributions than they ship
  with, a 14.04 targeted installer is unlikely to bring much to a 14.10
  installation, which most likely has the same or more recent versions
  already anyway.

  Source: https://01.org/linuxgraphics/node/375

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Oct 28 15:24:30 2014
  DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-06-14 (135 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic 
root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Oct 28 13:44:57 2014
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4933
   vendor CMN
  xserver.version: 2:1.16.0-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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 1400205] Re: network-manager may start before libsystemd-logind

2014-12-23 Thread Mark
Is there an easy to apply this fix for a normal user, so that I don't
have to wait until Ubuntu does this?

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

Title:
  network-manager may start before libsystemd-logind

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When NetworkManager starts, it requests systemd login-monitor
  notifications through the libsystemd-login sd_login_monitor_new(3)
  API.

  This API will fail if the systemd-logind service has not been started,
  since it directly accesses directories in /run/systemd. As far as I
  can tell, systemd-logind in Utopic is started on-demand (through DBUS
  service activation). So, there's no guarantee that it has been started
  at the point during boot when NetworkMonitor is started. I attached a
  patch to upstart .conf file with one way to fix it -- it contacts the
  DBUS logind API within pre-start to ensure it has been started.

  NOTE: you will not see the error in syslog -- NetworkManager logs it
  to stderr which is /dev/null. If you enable --no-daemon on
  NetworkManager, the error (sd_login_monitor_new failed) should get
  logged to /var/log/upstart/network-manager.log. NOTE: even with this
  fix, I saw that sd_login_monitor_new failed -- I believe that's a bug
  in Utopic's systemd
  (https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203). I
  had to patch both to resolve a suspend/resume issue for me.

  Seen on:
  Ubuntu 14.10
  NetworkManager 0.9.8.8-0ubuntu28
  libsystemd-login0 208-8ubuntu8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1400205/+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 1400203] Re: libsystemd-login sd_login_monitor_new not working

2014-12-23 Thread Mark
Is there an easy to apply this fix for a normal user, so that I don't
have to wait until Ubuntu does this?

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

Title:
  libsystemd-login sd_login_monitor_new not working

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  There is a C API in libsystemd-login for receiving notifications, see
  sd_login_monitor_new(3). It is not working in the Utopic version of
  systemd, because it attempts to access /run/systemd/machines which
  does not exist on utopic.

  I see a patch to fix this in the older, Trusty Tahr version of systemd
  (http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-
  monitor-no-machine.patch). The patch isn't in the utopic systemd
  (208-8ubuntu8).

  I tracked down an issue in NetworkManager which I believe was due to
  this issue. Attached is a C program to demonstrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+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 1405116] [NEW] package libpam-systemd:amd64 204-5ubuntu20.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2014-12-23 Thread Bernd Laser
Public bug reported:

Failure on login. Failure on update. Please fix this.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libpam-systemd:amd64 204-5ubuntu20.9
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Sat Dec  6 09:59:22 2014
DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.9:subprocess 
installed post-installation script returned error exit status 255
ErrorMessage: subprocess installed post-installation script returned error exit 
status 255
InstallationDate: Installed on 2013-10-02 (446 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
SourcePackage: systemd
Title: package libpam-systemd:amd64 204-5ubuntu20.9 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
UpgradeStatus: Upgraded to trusty on 2014-03-29 (269 days ago)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package libpam-systemd:amd64 204-5ubuntu20.9 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 255

Status in systemd package in Ubuntu:
  New

Bug description:
  Failure on login. Failure on update. Please fix this.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpam-systemd:amd64 204-5ubuntu20.9
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Dec  6 09:59:22 2014
  DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.9:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-10-02 (446 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 204-5ubuntu20.9 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 255
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (269 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1405116/+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 1405115] [NEW] package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2014-12-23 Thread Bernd Laser
Public bug reported:

Failure on login. Failure on update. Please fix this.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apparmor 2.8.95~2430-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Sat Dec  6 09:59:23 2014
DuplicateSignature: package:apparmor:2.8.95~2430-0ubuntu5.1:subprocess 
installed post-installation script returned error exit status 255
ErrorMessage: subprocess installed post-installation script returned error exit 
status 255
InstallationDate: Installed on 2013-10-02 (446 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1440d080-bfd3-4290-876c-4350ed113d7d ro quiet splash
SourcePackage: apparmor
Syslog: Dec 23 10:56:02 link dbus[507]: [system] AppArmor D-Bus mediation is 
enabled
Title: package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
UpgradeStatus: Upgraded to trusty on 2014-03-29 (269 days ago)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in apparmor package in Ubuntu:
  New

Bug description:
  Failure on login. Failure on update. Please fix this.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Dec  6 09:59:23 2014
  DuplicateSignature: package:apparmor:2.8.95~2430-0ubuntu5.1:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-10-02 (446 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1440d080-bfd3-4290-876c-4350ed113d7d ro quiet splash
  SourcePackage: apparmor
  Syslog: Dec 23 10:56:02 link dbus[507]: [system] AppArmor D-Bus mediation is 
enabled
  Title: package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (269 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1405115/+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 1405117] [NEW] package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64 2.15-0ubuntu10.9 cannot be configured because libc6

2014-12-23 Thread Andrew Ryan
Public bug reported:

Power failure in the middle of an update using update manager:

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libc6 2.15-0ubuntu10.9
ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
Uname: Linux 3.2.0-70-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.8
Architecture: amd64
Date: Tue Dec 23 13:10:08 2014
DuplicateSignature: package:libc6:2.15-0ubuntu10.9:libc6:amd64 2.15-0ubuntu10.9 
cannot be configured because libc6
ErrorMessage: libc6:amd64 2.15-0ubuntu10.9 cannot be configured because libc6
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
MarkForUpload: True
SourcePackage: eglibc
Title: package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64 
2.15-0ubuntu10.9 cannot be configured because libc6
UpgradeStatus: Upgraded to precise on 2012-12-09 (744 days ago)

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


** Tags: amd64 apport-package precise

** Attachment added: Console output when following package troubleshooting 
guide
   https://bugs.launchpad.net/bugs/1405117/+attachment/4286275/+files/typescript

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

Title:
  package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64
  2.15-0ubuntu10.9 cannot be configured because libc6

Status in eglibc package in Ubuntu:
  New

Bug description:
  Power failure in the middle of an update using update manager:

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libc6 2.15-0ubuntu10.9
  ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
  Uname: Linux 3.2.0-70-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Tue Dec 23 13:10:08 2014
  DuplicateSignature: package:libc6:2.15-0ubuntu10.9:libc6:amd64 
2.15-0ubuntu10.9 cannot be configured because libc6
  ErrorMessage: libc6:amd64 2.15-0ubuntu10.9 cannot be configured because libc6
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64 
2.15-0ubuntu10.9 cannot be configured because libc6
  UpgradeStatus: Upgraded to precise on 2012-12-09 (744 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1405117/+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 1405117] Re: package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64 2.15-0ubuntu10.9 cannot be configured because libc6

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64
  2.15-0ubuntu10.9 cannot be configured because libc6

Status in eglibc package in Ubuntu:
  New

Bug description:
  Power failure in the middle of an update using update manager:

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libc6 2.15-0ubuntu10.9
  ProcVersionSignature: Ubuntu 3.2.0-70.105-generic 3.2.63
  Uname: Linux 3.2.0-70-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: amd64
  Date: Tue Dec 23 13:10:08 2014
  DuplicateSignature: package:libc6:2.15-0ubuntu10.9:libc6:amd64 
2.15-0ubuntu10.9 cannot be configured because libc6
  ErrorMessage: libc6:amd64 2.15-0ubuntu10.9 cannot be configured because libc6
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  MarkForUpload: True
  SourcePackage: eglibc
  Title: package libc6 2.15-0ubuntu10.9 failed to install/upgrade: libc6:amd64 
2.15-0ubuntu10.9 cannot be configured because libc6
  UpgradeStatus: Upgraded to precise on 2012-12-09 (744 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1405117/+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 1405118] [NEW] Keyboard layout changes randomly for no reason

2014-12-23 Thread Nikita Yerenkov-Scott
Public bug reported:

This problem has occurred ever since I installed Ubuntu on this machine,
I installed 14.04, and even though I have upgraded to 14.10, the problem
still persists. Even though I have gone into the Text entry settings,
and deleted English (US) from their. It will still at random times
change from what I want it to be English (UK), to English (US)
keyboard layout. And when this has happened I have looked in the
settings to see which of the keyboard layouts is selected, and even
though it is clear that it has somehow changed to English (US), it
still says it is English (UK).

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 23 10:02:57 2014
DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:5002]
InstallationDate: Installed on 2014-12-06 (16 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: LENOVO 62742SG
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to utopic on 2014-12-13 (9 days ago)
dmi.bios.date: 11/15/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: H5ET69WW (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 62742SG
dmi.board.vendor: LENOVO
dmi.board.version: Win8 Pro DPK IPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 62742SG
dmi.product.version: Lenovo B590
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Dec 23 10:01:21 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 827 
 vendor LGD
xserver.version: 2:1.16.0-1ubuntu1.2

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic

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

Title:
  Keyboard layout changes randomly for no reason

Status in xorg package in Ubuntu:
  New

Bug description:
  This problem has occurred ever since I installed Ubuntu on this
  machine, I installed 14.04, and even though I have upgraded to 14.10,
  the problem still persists. Even though I have gone into the Text
  entry settings, and deleted English (US) from their. It will still
  at random times change from what I want it to be English (UK), to
  English (US) keyboard layout. And when this has happened I have
  looked in the settings to see which of the keyboard layouts is
  selected, and even though it is clear that it has somehow changed to
  English (US), it still says it is English (UK).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 23 10:02:57 2014
  DistUpgraded: 2014-12-13 16:39:34,851 

[Touch-packages] [Bug 1405115] Re: package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 255

Status in apparmor package in Ubuntu:
  New

Bug description:
  Failure on login. Failure on update. Please fix this.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Dec  6 09:59:23 2014
  DuplicateSignature: package:apparmor:2.8.95~2430-0ubuntu5.1:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-10-02 (446 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=1440d080-bfd3-4290-876c-4350ed113d7d ro quiet splash
  SourcePackage: apparmor
  Syslog: Dec 23 10:56:02 link dbus[507]: [system] AppArmor D-Bus mediation is 
enabled
  Title: package apparmor 2.8.95~2430-0ubuntu5.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (269 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1405115/+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 1405116] Re: package libpam-systemd:amd64 204-5ubuntu20.9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libpam-systemd:amd64 204-5ubuntu20.9 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 255

Status in systemd package in Ubuntu:
  New

Bug description:
  Failure on login. Failure on update. Please fix this.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libpam-systemd:amd64 204-5ubuntu20.9
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Sat Dec  6 09:59:22 2014
  DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.9:subprocess 
installed post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2013-10-02 (446 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1)
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 204-5ubuntu20.9 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 255
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (269 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1405116/+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 1405094] Re: Laptop screen stops working when HDMI screen is connected at boot

2014-12-23 Thread Volodya
** Summary changed:

- Laptop screen stops working when DVI screen is connected at boot
+ Laptop screen stops working when HDMI screen is connected at boot

** Description changed:

  This problem is new with 14.10, did not exist with 14.04
  
  What i do to reproduce:
  
  Turn laptop off
- Connect a screen via DVI
+ Connect a screen via HDMI
  Turn computer on
  
  What happens:
  
  Laptop screen stops working as soon as the OS begins to boot
- Once i login, it's clear that the OS thinks that the screen is working, since 
i can move my mouse into the area of that screen and move it around there. I 
can drag windows there and if i can grab them afterwards, i can move them back 
into the visible DVI screen.
- Disconnecting DVI screen does *not* turn on the Laptop screen
- The only way to get laptop screen to work is to boot and login without DVI 
and connect it only afterwards.
+ Once i login, it's clear that the OS thinks that the screen is working, since 
i can move my mouse into the area of that screen and move it around there. I 
can drag windows there and if i can grab them afterwards, i can move them back 
into the visible HDMI screen.
+ Disconnecting HDMI screen does *not* turn on the Laptop screen
+ The only way to get laptop screen to work is to boot and login without HDMI 
and connect it only afterwards.
  
  What i expect to happen:
  
  When booting with two screens, both should work with the settings in
  place.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 23 11:52:55 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:1477]
-Subsystem: ASUSTeK Computer Inc. Device [1043:1477]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:1477]
+    Subsystem: ASUSTeK Computer Inc. Device [1043:1477]
  InstallationDate: Installed on 2014-12-22 (0 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: ASUSTeK COMPUTER INC. N76VB
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-29-generic 
root=UUID=c1b99000-5c86-4711-946a-ba820ac888d0 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N76VB.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N76VB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN76VB.205:bd05/24/2013:svnASUSTeKCOMPUTERINC.:pnN76VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN76VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N76VB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Dec 22 21:31:52 2014
  xserver.configfile: default
  xserver.errors:
-  Failed to load module nvidia (module does not exist, 0)
-  Failed to load module nvidia (module does not exist, 0)
-  NOUVEAU(G0): [XvMC] Failed to initialize extension.
+  Failed to load module nvidia (module does not exist, 0)
+  Failed to load module nvidia (module does not exist, 0)
+  NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id8605 
-  vendor AUO
+  product id8605
+  vendor   

[Touch-packages] [Bug 1400203] Re: libsystemd-login sd_login_monitor_new not working

2014-12-23 Thread Martin Pitt
Added an utopic task for SRUing this. Fix:

http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?h=experimentalid=c8b099c992

** Also affects: systemd (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu Utopic)
   Status: New = Triaged

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

Title:
  libsystemd-login sd_login_monitor_new not working

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Utopic:
  Triaged

Bug description:
  There is a C API in libsystemd-login for receiving notifications, see
  sd_login_monitor_new(3). It is not working in the Utopic version of
  systemd, because it attempts to access /run/systemd/machines which
  does not exist on utopic.

  I see a patch to fix this in the older, Trusty Tahr version of systemd
  (http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-
  monitor-no-machine.patch). The patch isn't in the utopic systemd
  (208-8ubuntu8).

  I tracked down an issue in NetworkManager which I believe was due to
  this issue. Attached is a C program to demonstrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+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 1405141] [NEW] package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2014-12-23 Thread Past
Public bug reported:

Just apt-get  dist-upgrade

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: dbus 1.8.8-1ubuntu2.1
ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
Uname: Linux 3.11.0-17-generic x86_64
NonfreeKernelModules: zfs nvidia zunicode zavl zcommon znvpair
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Tue Dec  2 11:37:41 2014
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2014-02-12 (313 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
SourcePackage: dbus
Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: Upgraded to utopic on 2014-10-24 (60 days ago)

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


** Tags: amd64 apport-package utopic

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

Title:
  package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: подпроцесс
  установлен сценарий post-installation возвратил код ошибки 1

Status in dbus package in Ubuntu:
  New

Bug description:
  Just apt-get  dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: dbus 1.8.8-1ubuntu2.1
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: zfs nvidia zunicode zavl zcommon znvpair
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Tue Dec  2 11:37:41 2014
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2014-02-12 (313 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: dbus
  Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (60 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1405141/+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 1405140] [NEW] e4defrag doesn't notice if a device is mounted multiple times

2014-12-23 Thread Sworddragon
Public bug reported:

I'm using Ubuntu 15.04 dev with e2fsprogs 1.42.12-1ubuntu1 and if a
device is mounted multiple times e4defrag doesn't notice this and will
check/defragment the files multiple times. Here is an example:

root@ubuntu:~# e4defrag -c /dev/sda1 | grep extents
 Total/best extents 176021/174899
root@ubuntu:~# mount /dev/sda1 /mnt
root@ubuntu:~# e4defrag -c /dev/sda1 | grep extents
 Total/best extents 352050/349805

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

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

Title:
  e4defrag doesn't notice if a device is mounted multiple times

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 15.04 dev with e2fsprogs 1.42.12-1ubuntu1 and if a
  device is mounted multiple times e4defrag doesn't notice this and will
  check/defragment the files multiple times. Here is an example:

  root@ubuntu:~# e4defrag -c /dev/sda1 | grep extents
   Total/best extents   176021/174899
  root@ubuntu:~# mount /dev/sda1 /mnt
  root@ubuntu:~# e4defrag -c /dev/sda1 | grep extents
   Total/best extents   352050/349805

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1405140/+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 1400730] Re: libxext fills up .xsession-errors log files

2014-12-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libxext (Ubuntu Utopic)
   Status: New = Confirmed

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

Title:
  libxext fills up .xsession-errors log files

Status in libxext package in Ubuntu:
  Fix Released
Status in libxext source package in Utopic:
  Confirmed
Status in libxext source package in Vivid:
  Fix Released

Bug description:
  libxext can write debug output, and it can write so much of it that it
  fills up .xsession-errors t be several GB and fill up the hard disk
  (or the equivalent file with lightdm).

  error is _xgeWireToEvent: Unknown extension 148, this should never
  happen

  [TEST CASE]
  Install Plasma 5 on utopic
  Use it for a while
  Notice that ~/.xsession-errors is filling up saying _xgeWireToEvent: Unknown 
extension 148, this should never happen

  with the new packages this will not happen

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1400730/+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 1405154] [NEW] firefox windows move with workspace change

2014-12-23 Thread Stephen Davis
Public bug reported:

When changing workspaces the firefox web browser window moves with the
workspace change (always staying on the current workspace). This happens
both when using the keyboard shortcut and the gui applet. I cannot
designate different workspaces with different browser windows because of
this. This is very frusterating.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.3+14.04.20140826-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Tue Dec 23 04:54:06 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:029b]
   Subsystem: Acer Incorporated [ALI] Device [1025:029b]
InstallationDate: Installed on 2014-12-20 (3 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: Acer Aspire 1410
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=59ff4d47-8eb9-4ee8-8876-0128499dc5af ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/31/2010
dmi.bios.vendor: INSYDE
dmi.bios.version: v1.3314
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JM11-MS
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1410:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Aspire 1410
dmi.product.version: v1.3314
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Dec 20 15:52:55 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id9411 
 vendor ACI
xserver.version: 2:1.15.1-0ubuntu2.6

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


** Tags: amd64 apport-bug trusty ubuntu

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

Title:
  firefox windows move with workspace change

Status in unity package in Ubuntu:
  New

Bug description:
  When changing workspaces the firefox web browser window moves with the
  workspace change (always staying on the current workspace). This
  happens both when using the keyboard shortcut and the gui applet. I
  cannot designate different workspaces with different browser windows
  because of this. This is very frusterating.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Dec 23 04:54:06 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:029b]
 Subsystem: Acer Incorporated [ALI] Device [1025:029b]
  InstallationDate: Installed on 2014-12-20 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Acer Aspire 1410
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 1400874] Re: package rsyslog 7.4.4-1ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10

2014-12-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: rsyslog (Ubuntu)
   Status: New = Confirmed

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

Title:
  package rsyslog 7.4.4-1ubuntu2.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 10

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  !

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.3
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Tue Dec  9 21:54:45 2014
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.3:subprocess installed 
post-installation script returned error exit status 10
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 10
  InstallationDate: Installed on 2014-05-16 (207 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2)
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu2.3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1400874/+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 1310335] Re: IPv6 renewal causes network-manager to disconnect reconnect

2014-12-23 Thread e633
Looks like i was wrong: the connection gets dropped anyway. I've just tested 
this slowly downloading a large file (this is what happens):
http://pastebin.com/4Xida2qu
So i guess it's not (just) a network manager issue.

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

Title:
  IPv6 renewal causes network-manager to disconnect  reconnect

Status in The Linux Mint Distribution:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  IPv6 renewal causes network manager to disconnect  reconnect

  Happens *roughly* every ten minutes.
  My network is running fully dual stack.
  The problematic option in the IPv6 part of the router's settings is
  IP Address Assignment
  - Use DHCP Server
  - Auto Config Problem presents itself only when using this one
  I have a Netgear DGND3700v2 router, firmware version V1.1.00.15_1.00.15 
(latest).

  There are 3 different PCs on WiFi and ethernet.
  Network manager settings are: one PC static IPv4, two DHCPv4 and all of them 
Automatic for IPv6.
  Linux Mint: 
  kernel 3.2.0-60 x86 network-manager version 0.9.4.0-0ubuntu4.3 (MATE)
  kernel 3.5.0-48 x64 network-manager version 0.9.6.0-0ubuntu7 (Cinnamon)
  kernel 3.11.0-12 x64 network-manager version 0.9.8.0-0ubuntu22 (MATE)

  Wifi disconnection log (repeated, ethernet reconnects seem to leave no trace 
and seem to happen slightly less frequently):
  http://pastebin.com/GUdWgRUp

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1310335/+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 1405154] Re: firefox windows move with workspace change

2014-12-23 Thread Stephen M. Webb
The behaviour you are describing is exactly what I would expect if the
Compiz sticky window matching rule included class=firefox.

Please install the compizconfig-settings-manager package and run the
ccsm program.  Under the Window Management category, make sure the
Window Rules plugin is unchecked.

I'm marking this bug report as 'incomplete' until you have confirmed the
state of that Compiz plugin.

** Changed in: unity (Ubuntu)
   Status: New = Incomplete

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

Title:
  firefox windows move with workspace change

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When changing workspaces the firefox web browser window moves with the
  workspace change (always staying on the current workspace). This
  happens both when using the keyboard shortcut and the gui applet. I
  cannot designate different workspaces with different browser windows
  because of this. This is very frusterating.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Dec 23 04:54:06 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:029b]
 Subsystem: Acer Incorporated [ALI] Device [1025:029b]
  InstallationDate: Installed on 2014-12-20 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Acer Aspire 1410
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=59ff4d47-8eb9-4ee8-8876-0128499dc5af ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1410:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1410
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Dec 20 15:52:55 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9411 
   vendor ACI
  xserver.version: 2:1.15.1-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1405154/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

2014-12-23 Thread brayan bautista
hello,.

I can confirm I'm using sssd

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

Title:
  Unity Lockscreen in 14.04 can't unlock when using LDAP account

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  My setup is:

  Ubuntu 14.04 LTS,
  ldap accounts,
  krb5 authentication,
  Lightdm,
  Unity session

  ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent 
passwd and getent shadow works fine.
  I am able to login in console without any problems.
  I was able to login in lightdm.
  Then I used the lock screen.
  I could not disable the lock screen using my password.
  I rebooted my computer.

  Now:
  After logging in through lightdm, the unity lockscreen locks the screen 
immediately and I can not disable it using my password.

  From my short inspection of auth.log and unix_chkpwd sources it seems,
  that unix_chkpwd works fine when called from lightdm and fails to get
  user info when called from unity lockscreen.


  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  apt-cache policy unity lightdm libpam-modules
  unity:
Installed: 7.2.0+14.04.20140416-0ubuntu1
Candidate: 7.2.0+14.04.20140416-0ubuntu1
Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
   *** 1.1.8-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Contents of /var/log/auth.log:

  Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user
  Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost=  user=user
  Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optionalpam_gnome_keyring.so auto_start
  session requiredpam_env.so readenv=1
  session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1314095/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account

2014-12-23 Thread brayan bautista
caused Error by lighdm ???

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

Title:
  Unity Lockscreen in 14.04 can't unlock when using LDAP account

Status in Unity:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  My setup is:

  Ubuntu 14.04 LTS,
  ldap accounts,
  krb5 authentication,
  Lightdm,
  Unity session

  ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent 
passwd and getent shadow works fine.
  I am able to login in console without any problems.
  I was able to login in lightdm.
  Then I used the lock screen.
  I could not disable the lock screen using my password.
  I rebooted my computer.

  Now:
  After logging in through lightdm, the unity lockscreen locks the screen 
immediately and I can not disable it using my password.

  From my short inspection of auth.log and unix_chkpwd sources it seems,
  that unix_chkpwd works fine when called from lightdm and fails to get
  user info when called from unity lockscreen.


  lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  apt-cache policy unity lightdm libpam-modules
  unity:
Installed: 7.2.0+14.04.20140416-0ubuntu1
Candidate: 7.2.0+14.04.20140416-0ubuntu1
Version table:
   *** 7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
   *** 1.10.0-0ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status
  libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
   *** 1.1.8-1ubuntu2 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Contents of /var/log/auth.log:

  Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user
  Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication 
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost=  user=user
  Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): 
session closed for user lightdm
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
  Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user 
(user)
  Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication 
failure; logname= uid=1001 euid=1001 tty= ruser= rhost=  user=user
  Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user 
authenticated as user@NETWORK
  Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info 
(user)
  Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement 
user ingroup nopasswdlogin not met by user user

  cat /etc/pam.d/common-auth 
  account requiredpam_unix.so
  authrequiredpam_group.so
  auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
  auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
  authrequisite   pam_deny.so
  authrequiredpam_permit.so

  authoptionalpam_afs_session.so minimum_uid=200
  authoptionalpam_ecryptfs.so unwrap
  authoptionalpam_cap.so

  cat /etc/pam.d/common-account 
  account requiredpam_unix.so

  cat /etc/pam.d/lightdm
  authrequisite   pam_nologin.so
  authsufficient  pam_succeed_if.so user ingroup nopasswdlogin
  @include common-auth
  authoptionalpam_gnome_keyring.so
  @include common-account
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so close
  authoptionalpam_group.so
  session requiredpam_limits.so
  @include common-session
  session [success=ok ignore=ignore module_unknown=ignore default=bad] 
pam_selinux.so open
  session optionalpam_gnome_keyring.so auto_start
  session requiredpam_env.so readenv=1
  session requiredpam_env.so readenv=1 user_readenv=1 
envfile=/etc/default/locale
  @include common-password

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1314095/+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 1405188] [NEW] package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi

2014-12-23 Thread klomiz
Public bug reported:

It happend when updating

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: ncurses-term 5.9+20140118-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Tue Dec 23 15:20:48 2014
Dependencies:
 
DuplicateSignature: package:ncurses-term:5.9+20140118-1ubuntu1:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2014-05-08 (228 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: ncurses
Title: package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check trusty

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

Title:
  package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in ncurses package in Ubuntu:
  New

Bug description:
  It happend when updating

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ncurses-term 5.9+20140118-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec 23 15:20:48 2014
  Dependencies:
   
  DuplicateSignature: package:ncurses-term:5.9+20140118-1ubuntu1:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-05-08 (228 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ncurses
  Title: package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1405188/+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 1405188] Re: package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in ncurses package in Ubuntu:
  New

Bug description:
  It happend when updating

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: ncurses-term 5.9+20140118-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Tue Dec 23 15:20:48 2014
  Dependencies:
   
  DuplicateSignature: package:ncurses-term:5.9+20140118-1ubuntu1:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2014-05-08 (228 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: ncurses
  Title: package ncurses-term 5.9+20140118-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1405188/+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 1004792] Re: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

2014-12-23 Thread LAZA
Got this on 2 Internet-Cafe machines , one did the update.

Xubuntu 14.04.1

** Changed in: unattended-upgrades (Ubuntu)
   Status: Expired = New

** Tags added: trusty

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

Title:
  unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Always happens as i logon

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unattended-upgrades 0.76
  Uname: Linux 3.4.0-030400-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri May 25 01:09:56 2012
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/sh
  PythonArgs: ['/usr/bin/unattended-upgrade']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor
  Traceback: IOError: [Errno 9] Bad file descriptor
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792/+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 1400203] Re: libsystemd-login sd_login_monitor_new not working

2014-12-23 Thread Martin Pitt
Can you please add a proper impact description that justifies that SRU,
and would you be willing to test the update in -proposed?

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

Title:
  libsystemd-login sd_login_monitor_new not working

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Utopic:
  Triaged

Bug description:
  There is a C API in libsystemd-login for receiving notifications, see
  sd_login_monitor_new(3). It is not working in the Utopic version of
  systemd, because it attempts to access /run/systemd/machines which
  does not exist on utopic.

  I see a patch to fix this in the older, Trusty Tahr version of systemd
  (http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-
  monitor-no-machine.patch). The patch isn't in the utopic systemd
  (208-8ubuntu8).

  I tracked down an issue in NetworkManager which I believe was due to
  this issue. Attached is a C program to demonstrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+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 1004792] Re: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

2014-12-23 Thread LAZA
** Attachment added: _usr_bin_unattended-upgrade.0.crash
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792/+attachment/4286443/+files/_usr_bin_unattended-upgrade.0.crash

** Tags removed: trusty

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

Title:
  unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Always happens as i logon

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: unattended-upgrades 0.76
  Uname: Linux 3.4.0-030400-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: i386
  CrashCounter: 1
  Date: Fri May 25 01:09:56 2012
  ExecutablePath: /usr/bin/unattended-upgrade
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/sh
  PythonArgs: ['/usr/bin/unattended-upgrade']
  SourcePackage: unattended-upgrades
  Title: unattended-upgrade crashed with IOError: [Errno 9] Bad file descriptor
  Traceback: IOError: [Errno 9] Bad file descriptor
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792/+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 1405192] [NEW] package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2014-12-23 Thread LAZA
Public bug reported:

Got this crash:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792

than the crash about failed ntp installation.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.2
ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64
Uname: Linux 3.2.0-74-generic i686
ApportVersion: 2.0.1-0ubuntu17.8
AptOrdering:
 python-lazr.restfulclient: Install
 ntp: Configure
 python-lazr.restfulclient: Configure
Architecture: i386
Date: Tue Dec 23 15:28:51 2014
DuplicateSignature: package:ntp:1:4.2.6.p3+dfsg-1ubuntu3.2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
MarkForUpload: True
NtpStatus: ntpq: read: Connection refused
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-74-generic 
root=UUID=7fffcbef-13cb-47ff-979b-b36510db6940 ro quiet splash vt.handoff=7
SourcePackage: ntp
Title: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.ntp.conf: [modified]
mtime.conffile..etc.ntp.conf: 2012-10-02T10:47:49

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


** Tags: apparmor apport-package i386 precise

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

Title:
  package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in ntp package in Ubuntu:
  New

Bug description:
  Got this crash:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792

  than the crash about failed ntp installation.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64
  Uname: Linux 3.2.0-74-generic i686
  ApportVersion: 2.0.1-0ubuntu17.8
  AptOrdering:
   python-lazr.restfulclient: Install
   ntp: Configure
   python-lazr.restfulclient: Configure
  Architecture: i386
  Date: Tue Dec 23 15:28:51 2014
  DuplicateSignature: package:ntp:1:4.2.6.p3+dfsg-1ubuntu3.2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  MarkForUpload: True
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-74-generic 
root=UUID=7fffcbef-13cb-47ff-979b-b36510db6940 ro quiet splash vt.handoff=7
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2012-10-02T10:47:49

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1405192/+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 1405192] Re: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2014-12-23 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in ntp package in Ubuntu:
  New

Bug description:
  Got this crash:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792

  than the crash about failed ntp installation.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64
  Uname: Linux 3.2.0-74-generic i686
  ApportVersion: 2.0.1-0ubuntu17.8
  AptOrdering:
   python-lazr.restfulclient: Install
   ntp: Configure
   python-lazr.restfulclient: Configure
  Architecture: i386
  Date: Tue Dec 23 15:28:51 2014
  DuplicateSignature: package:ntp:1:4.2.6.p3+dfsg-1ubuntu3.2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  MarkForUpload: True
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-74-generic 
root=UUID=7fffcbef-13cb-47ff-979b-b36510db6940 ro quiet splash vt.handoff=7
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2012-10-02T10:47:49

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1405192/+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 1405192] Re: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2014-12-23 Thread LAZA
Update even fails if i open up a new bash as root:

root@icafe-a:~# apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut   
Statusinformationen werden eingelesen... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
1 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt.
Möchten Sie fortfahren [J/n]? 
ntp (1:4.2.6.p3+dfsg-1ubuntu3.2) wird eingerichtet ...
chown: ungültige Gruppe: »ntp:ntp“
dpkg: Fehler beim Bearbeiten von ntp (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Fehler traten auf beim Bearbeiten von:
 ntp
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in ntp package in Ubuntu:
  New

Bug description:
  Got this crash:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792

  than the crash about failed ntp installation.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64
  Uname: Linux 3.2.0-74-generic i686
  ApportVersion: 2.0.1-0ubuntu17.8
  AptOrdering:
   python-lazr.restfulclient: Install
   ntp: Configure
   python-lazr.restfulclient: Configure
  Architecture: i386
  Date: Tue Dec 23 15:28:51 2014
  DuplicateSignature: package:ntp:1:4.2.6.p3+dfsg-1ubuntu3.2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  MarkForUpload: True
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-74-generic 
root=UUID=7fffcbef-13cb-47ff-979b-b36510db6940 ro quiet splash vt.handoff=7
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2012-10-02T10:47:49

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1405192/+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 1405192] Re: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2014-12-23 Thread LAZA
Solved!

Group 'ntp' was deleted...

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

Title:
  package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in ntp package in Ubuntu:
  New

Bug description:
  Got this crash:
  https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1004792

  than the crash about failed ntp installation.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: ntp 1:4.2.6.p3+dfsg-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.2.0-74.109-generic 3.2.64
  Uname: Linux 3.2.0-74-generic i686
  ApportVersion: 2.0.1-0ubuntu17.8
  AptOrdering:
   python-lazr.restfulclient: Install
   ntp: Configure
   python-lazr.restfulclient: Configure
  Architecture: i386
  Date: Tue Dec 23 15:28:51 2014
  DuplicateSignature: package:ntp:1:4.2.6.p3+dfsg-1ubuntu3.2:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release i386 
(20120817.3)
  MarkForUpload: True
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-74-generic 
root=UUID=7fffcbef-13cb-47ff-979b-b36510db6940 ro quiet splash vt.handoff=7
  SourcePackage: ntp
  Title: package ntp 1:4.2.6.p3+dfsg-1ubuntu3.2 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.ntp.conf: 2012-10-02T10:47:49

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1405192/+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 886605] Re: Desktop, Launcher and menu bar still visible when screen locked

2014-12-23 Thread Kenan Gutić
It happend to me just now, using Ubuntu 14.04LTS.
I left my PC for 10 minutes, and when I got back screen was black. I moved my 
mouse and screen become active and it displayed Ubuntu lock screen with my 
laucnher, panel and desktop showing also.
Same thing is when I lock PC myself.

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

Title:
  Desktop, Launcher and menu bar still visible when screen locked

Status in Compiz:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  1. Lock your screen
 - Confirm that the whole screen goes black

  [Regression Potential]
  Visual regressions, shell drawing problems. Part of a big change, many 
regression potentials.

  Original description:

  When I lock my screen, instead of the monitor going, black, the
  desktop background goes black, but the Unity launcher and the main bar
  stay visible.  When I press a key or move my mouse the unlock
  dialog, asking me for my password pops up, centered on the black
  desktop background.

  I think the main issue here is gnome-screensaver failing to
  fullscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-screensaver 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov  5 13:05:04 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/886605/+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 886605] Re: Desktop, Launcher and menu bar still visible when screen locked

2014-12-23 Thread Kenan Gutić
After a bit looking I found out that the lock screen would work OK if I werent 
downloading anything with firefox.
When I download bigger file with firefox and left my PC to locks, then the 
launcher and panel shows up on lock screen.

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

Title:
  Desktop, Launcher and menu bar still visible when screen locked

Status in Compiz:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Precise:
  Fix Released

Bug description:
  [Test Case]
  1. Lock your screen
 - Confirm that the whole screen goes black

  [Regression Potential]
  Visual regressions, shell drawing problems. Part of a big change, many 
regression potentials.

  Original description:

  When I lock my screen, instead of the monitor going, black, the
  desktop background goes black, but the Unity launcher and the main bar
  stay visible.  When I press a key or move my mouse the unlock
  dialog, asking me for my password pops up, centered on the black
  desktop background.

  I think the main issue here is gnome-screensaver failing to
  fullscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-screensaver 3.2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Nov  5 13:05:04 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/886605/+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 1405207] [NEW] [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound at all

2014-12-23 Thread dennis
Public bug reported:

speakers on dell inspiron are working, but headphone jack does not , at
all, ever.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dutch  1387 F pulseaudio
 /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
CurrentDesktop: Unity
Date: Tue Dec 23 10:25:18 2014
InstallationDate: Installed on 2014-12-22 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dutch  1387 F pulseaudio
 /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/03/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron N5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 trusty

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

Title:
  [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  speakers on dell inspiron are working, but headphone jack does not ,
  at all, ever.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Tue Dec 23 10:25:18 2014
  InstallationDate: Installed on 2014-12-22 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dutch  1387 F pulseaudio
   /dev/snd/pcmC0D0p:   dutch  1387 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron N5110, IDT 92HD87B1/3, Black Headphone Out, Right] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1405207/+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 1405213] [NEW] + , instead of @

2014-12-23 Thread Gerhard Beck
*** This bug is a duplicate of bug 943104 ***
https://bugs.launchpad.net/bugs/943104

Public bug reported:

When I want to write an email address in the to field of evolution, I
can't get an @. With pressing Q and AltGr (German Layout) I get   +
, instead of @.

This Bug also has been filed with #1ß59107 and #943104

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 23 16:58:31 2014
DistUpgraded: 2014-10-25 00:44:05,240 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation ION VGA [10de:087d] (rev b1) (prog-if 00 [VGA controller])
   Subsystem: Foxconn International, Inc. Device [105b:0d52]
InstallationDate: Installed on 2013-10-23 (426 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: Foxconn nT-330i
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=6e1a06f8-261a-478b-b6e6-281d84414af5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to utopic on 2014-10-24 (59 days ago)
dmi.bios.date: 12/15/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
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.:bvr080015:bd12/15/2009:svnFoxconn:pnnT-330i:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: nT-330i
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Foxconn
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Dec 23 16:00:00 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
 NOUVEAU(0): [COPY] failed to allocate class.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2
xserver.video_driver: nouveau

** Affects: evolution
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic

** This bug has been marked a duplicate of bug 943104
   recipient address: comma inserted when pressing AltGr

** Also affects: evolution
   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/1405213

Title:
+ , instead of @

Status in The Evolution Mail  Calendaring Tool:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  When I want to write an email address in the to field of evolution,
  I can't get an @. With pressing Q and AltGr (German Layout) I get 
   + , instead of @.

  This Bug also has been filed with #1ß59107 and #943104

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: 

[Touch-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity

2014-12-23 Thread Andreas E.
I was able to install compiz-core-dbgsym=1:0.9.12+14.10.20140918-0ubuntu1 and 
have been trying to do
sudo gdb `pidof compiz`
but it gives me (2380 is the pid of compiz):
2380: File or directory not found
(gdb) bt full
No stack.

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

Title:
  Lock screen after idle time freezes unity

Status in Unity:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I recently upgrade to 14.04. My system uses fglrx provided by 14.04.

  When I lock manually the screen, I get no problem. I can even sleep the 
system without problem. However,
  when the screen is locked by idle time, I cannot unlock it.

  At this point, I can see the screen but with some kind of translucent
  panel over it. Mouse also works. I tried to type blink the password
  but I had no luck. I only get a working system by going text mode
  (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to
  indicate any error. The only strange log was in .xsession-errors.old:

  init: processos unity-settings-daemon main (2495) terminados com status 1
  init: processos gnome-session (Unity) main (2539) terminados com status 1
  init: processos unity-panel-service main (2572) terminados com status 1
  init: processos hud main (2536) terminados com status 1
  init: processo indicator-powermain (2740) morto pelo sinal TERM
  init: processo indicator-datetimemain (2741) morto pelo sinal TERM
  init: processo indicator-soundmain (2747) morto pelo sinal TERM
  init: processo indicator-printersmain (2748) morto pelo sinal TERM
  init: processo indicator-sessionmain (2768) morto pelo sinal TERM
  init: processo indicator-syncmain (2795) morto pelo sinal TERM
  init: processo update-notifier-crash 
(/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM
  init: processos unity-panel-service-lockscreen main (7447) terminados com 
status 1
  init: Disconnected from notified D-Bus bus
  init: processos at-spi2-registryd main (2538) terminados com status 1

  But as it has no time info, I cannot tell when they happened.

  At least another user faces the same problem:
  http://ubuntuforums.org/showthread.php?t=2214421

  And this seems to be different from bug 1283938 as pm sleep/wake works
  as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140328.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Apr  2 00:01:05 2014
  DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed
   fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed
   vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed
   vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] 
[1002:6758] (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0012]
  InstallationDate: Installed on 2012-10-19 (529 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  JockeyStatus:
   kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está 
em uso) [auto-install]
   kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, 
Desativado, Não está em uso)
   kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso)
  MachineType: Dell Inc. XPS 8300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic 
root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0Y2MRG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: XPS 8300
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  

[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2014-12-23 Thread Jonathan Kamens
This is still happening for me in 14.10.

I can't figure out how to nominate it for 14.10 in the settings at the
top of the bug.

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

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1003950/+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 1354924] Re: Networkmanager does not autoconnect to wireless network

2014-12-23 Thread tobiasBora
I can confirm I've the same (very annoying) bug. I don't have the file
that Paul L. is talking about, but when I do sudo service network-
manager restart it works (but it's dirty, even in the /etc/rc.local
folder).

I don't know if it can be useful but here are some logs (I aslept and awoke my 
laptop) :
$ cat /var/log/syslog | grep -i network
Dec 23 17:13:36 tblinux NetworkManager[1003]: info sleep requested (sleeping: 
no  enabled: yes)
Dec 23 17:13:36 tblinux NetworkManager[1003]: info sleeping or disabling...
Dec 23 17:13:36 tblinux NetworkManager[1003]: info (eth0): device state 
change: unavailable - unmanaged (reason 'sleeping') [20 10 37]
Dec 23 17:13:36 tblinux NetworkManager[1003]: info (eth0): cleaning up...
Dec 23 17:13:36 tblinux NetworkManager[1003]: info (eth0): taking down device.
Dec 23 17:13:37 tblinux NetworkManager[1003]: info NetworkManager state is 
now ASLEEP
Dec 23 17:13:37 tblinux NetworkManager[1003]: info (wlan0): device state 
change: activated - unmanaged (reason 'sleeping') [100 10 37]
Dec 23 17:13:37 tblinux NetworkManager[1003]: info (wlan0): deactivating 
device (reason 'sleeping') [37]
Dec 23 17:13:37 tblinux NetworkManager[1003]: info (wlan0): canceled DHCP 
transaction, DHCP client pid 5018
Dec 23 17:13:37 tblinux NetworkManager[1003]: warn DNS: plugin dnsmasq update 
failed
Dec 23 17:13:37 tblinux NetworkManager[1003]: info Removing DNS information 
from /sbin/resolvconf
Dec 23 17:13:38 tblinux NetworkManager[1003]: info (wlan0): cleaning up...
Dec 23 17:13:38 tblinux NetworkManager[1003]: info (wlan0): taking down 
device.
Dec 23 17:13:38 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): 
device state change: disconnected - unmanaged (reason 'sleeping') [30 10 37]
Dec 23 17:13:38 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): 
cleaning up...
Dec 23 17:13:38 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): 
taking down device.
Dec 23 17:13:45 tblinux NetworkManager[1003]: info BT device 
D0:C1:B1:5F:55:D9 removed
Dec 23 17:13:46 tblinux NetworkManager[1003]: info wake requested (sleeping: 
yes  enabled: yes)
Dec 23 17:13:46 tblinux NetworkManager[1003]: info waking up and 
re-enabling...
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): bringing up device.
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): preparing device.
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (eth0): deactivating 
device (reason 'managed') [2]
Dec 23 17:13:46 tblinux NetworkManager[1003]: info Unmanaged Device found; 
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 23 17:13:46 tblinux NetworkManager[1003]: info Unmanaged Device found; 
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 23 17:13:46 tblinux NetworkManager[1003]: info NetworkManager state is 
now CONNECTED_GLOBAL
Dec 23 17:13:46 tblinux NetworkManager[1003]: info Unmanaged Device found; 
state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): bringing up 
device.
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): preparing device.
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): deactivating 
device (reason 'managed') [2]
Dec 23 17:13:46 tblinux NetworkManager[1003]: info NetworkManager state is 
now DISCONNECTED
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0) supports 4 scan 
SSIDs
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): supplicant 
interface state: starting - ready
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): device state 
change: unavailable - disconnected (reason 'supplicant-available') [20 30 42]
Dec 23 17:13:46 tblinux NetworkManager[1003]: warn Trying to remove a 
non-existant call id.
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0): supplicant 
interface state: ready - disconnected
Dec 23 17:13:46 tblinux NetworkManager[1003]: info (wlan0) supports 4 scan 
SSIDs
Dec 23 17:13:47 tblinux NetworkManager[1003]: info (wlan0): supplicant 
interface state: disconnected - inactive
Dec 23 17:13:47 tblinux NetworkManager[1003]: info BT device tobias 
(D0:C1:B1:5F:55:D9) added (NAP)
Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): new 
Bluetooth device (driver: 'bluez' ifindex: 0)
Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): 
exported as /org/freedesktop/NetworkManager/Devices/5
Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): 
device state change: unmanaged - unavailable (reason 'managed') [10 20 2]
Dec 23 17:13:47 tblinux NetworkManager[1003]: info (D0:C1:B1:5F:55:D9): 
deactivating device (reason 'managed') [2]
Dec 23 17:13:47 tblinux NetworkManager[1003]: 

[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

2014-12-23 Thread tobiasBora
Is it possible that the wifi is loaded after network-manager, so that
network-manager cannot reconnect ?

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/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 disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1393843] Re: Log in prompt appears twice or three times after suspend

2014-12-23 Thread Burko
Push.

Is there nobody interested in solving the issue?

I mean, a fresh installation would probably solve the problem. However,
this is more of a workaround than of a fix.

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

Title:
  Log in prompt appears twice or three times after suspend

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  since my update to 14.04.1 LTS I experience difficulties with
  unlocking my screen after waking up my maschine. After logging the
  desktio is shown only for a short moment, following another screen
  lock. I have to unlock the screen again then. This happens after every
  suspend, sometimes even three times.

  I am happy to provide additional data.

  cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:03:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393843/+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 1405232] [NEW] ping reports wrong IP responding under certain conditions

2014-12-23 Thread Elliot Dronebarger
Public bug reported:

Description:Ubuntu 14.04.1 LTS
Release:14.04
iputils-ping:
Installed: 3:20121221-4ubuntu1.1
Candidate: 3:20121221-4ubuntu1.1

ping will report the incorrect reply IP address under certain, specific
conditions, and is repeatable. This is how to re-create the issue:

1. Start pinging an IP where you get an ICMP error message from some
other device (RFC792 lists errors). For instance: Destination IP is
offline and the last-hop router reports message type Destination
Unreachable. I assume this would work for any ICMP error, though.

2. When the device comes back online, ping reports replies from the
other device, when it should report replies from the device that is
sending the Echo Reply messages.

3. If the ping is stopped and restarted after the device is up, it
reports the correct IP address again. Other ping utilities do not
exhibit this behavior.

Example output (Destination that was pinged was 172.21.56.50, last hop router 
was 172.21.25.103):
circle@circle:~$ /bin/ping 172.21.56.50
PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data.
From 172.21.25.103 icmp_seq=1 Destination Host Unreachable
From 172.21.25.103 icmp_seq=2 Destination Host Unreachable
From 172.21.25.103 icmp_seq=3 Destination Host Unreachable
From 172.21.25.103 icmp_seq=4 Destination Host Unreachable
From 172.21.25.103 icmp_seq=5 Destination Host Unreachable
From 172.21.25.103 icmp_seq=6 Destination Host Unreachable
64 bytes from 172.21.25.103: icmp_seq=7 ttl=63 time=0.689 ms
64 bytes from 172.21.25.103: icmp_seq=8 ttl=63 time=0.635 ms
64 bytes from 172.21.25.103: icmp_seq=9 ttl=63 time=0.656 ms
64 bytes from 172.21.25.103: icmp_seq=10 ttl=63 time=0.822 ms
64 bytes from 172.21.25.103: icmp_seq=11 ttl=63 time=0.785 ms
^C
--- 172.21.56.50 ping statistics ---
11 packets transmitted, 5 received, +6 errors, 54% packet loss, time 10023ms
rtt min/avg/max/mdev = 0.635/0.717/0.822/0.077 ms, pipe 3
circle@circle:~$ /bin/ping 172.21.56.50
PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data.
64 bytes from 172.21.56.50: icmp_seq=1 ttl=63 time=0.737 ms
64 bytes from 172.21.56.50: icmp_seq=2 ttl=63 time=0.646 ms
64 bytes from 172.21.56.50: icmp_seq=3 ttl=63 time=0.626 ms
^C
--- 172.21.56.50 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.626/0.669/0.737/0.056 ms

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: iputils-ping 3:20121221-4ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Dec 23 10:50:35 2014
InstallationDate: Installed on 2014-10-08 (76 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723)
SourcePackage: iputils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  ping reports wrong IP responding under certain conditions

Status in iputils package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  iputils-ping:
  Installed: 3:20121221-4ubuntu1.1
  Candidate: 3:20121221-4ubuntu1.1

  ping will report the incorrect reply IP address under certain,
  specific conditions, and is repeatable. This is how to re-create the
  issue:

  1. Start pinging an IP where you get an ICMP error message from some
  other device (RFC792 lists errors). For instance: Destination IP is
  offline and the last-hop router reports message type Destination
  Unreachable. I assume this would work for any ICMP error, though.

  2. When the device comes back online, ping reports replies from the
  other device, when it should report replies from the device that is
  sending the Echo Reply messages.

  3. If the ping is stopped and restarted after the device is up, it
  reports the correct IP address again. Other ping utilities do not
  exhibit this behavior.

  Example output (Destination that was pinged was 172.21.56.50, last hop router 
was 172.21.25.103):
  circle@circle:~$ /bin/ping 172.21.56.50
  PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data.
  From 172.21.25.103 icmp_seq=1 Destination Host Unreachable
  From 172.21.25.103 icmp_seq=2 Destination Host Unreachable
  From 172.21.25.103 icmp_seq=3 Destination Host Unreachable
  From 172.21.25.103 icmp_seq=4 Destination Host Unreachable
  From 172.21.25.103 icmp_seq=5 Destination Host Unreachable
  From 172.21.25.103 icmp_seq=6 Destination Host Unreachable
  64 bytes from 172.21.25.103: icmp_seq=7 ttl=63 time=0.689 ms
  64 bytes from 172.21.25.103: icmp_seq=8 ttl=63 time=0.635 ms
  64 bytes from 172.21.25.103: icmp_seq=9 ttl=63 time=0.656 ms
  64 bytes from 172.21.25.103: icmp_seq=10 

[Touch-packages] [Bug 1393843] Re: Log in prompt appears twice or three times after suspend

2014-12-23 Thread Burko
** Also affects: unity-greeter
   Importance: Undecided
   Status: New

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

Title:
  Log in prompt appears twice or three times after suspend

Status in Unity Greeter:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  since my update to 14.04.1 LTS I experience difficulties with
  unlocking my screen after waking up my maschine. After logging the
  desktio is shown only for a short moment, following another screen
  lock. I have to unlock the screen again then. This happens after every
  suspend, sometimes even three times.

  I am happy to provide additional data.

  cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic i686
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Tue Nov 18 17:03:00 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-13 (673 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2)
  LightdmConfig:
   [SeatDefaults]
   user-session=ubuntu
   greeter-session=unity-greeter
   allow-guest=true
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-greeter/+bug/1393843/+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 1326810] Re: ping forgets to whom it's talking

2014-12-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: iputils (Ubuntu)
   Status: New = Confirmed

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

Title:
  ping forgets to whom it's talking

Status in iputils package in Ubuntu:
  Confirmed

Bug description:
  Distro: ubuntu 14.04 x64
  Package: iputils-ping 3:20121221-4ubuntu1.1

  The ping command accidentally uses the information for the last ICMP
  UNREACHABLE response instead of the host from which the *actual*
  response came. See the output below:

  michael@challenger:~
  ○ → ping 10gb-sw1
  PING 10gb-sw1.office.netdirect.ca (192.168.0.33) 56(84) bytes of data.
  From challenger.netdirect.ca (192.168.0.135) icmp_seq=1 Destination Host 
Unreachable
  From challenger.netdirect.ca (192.168.0.135) icmp_seq=2 Destination Host 
Unreachable
  …
  From challenger.netdirect.ca (192.168.0.135) icmp_seq=82 Destination Host 
Unreachable
  From challenger.netdirect.ca (192.168.0.135) icmp_seq=86 Destination Host 
Unreachable
  64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=88 ttl=255 
time=3.25 ms
  64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=89 ttl=255 
time=0.737 ms
  64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=90 ttl=255 
time=1.68 ms
  …
  64 bytes from challenger.netdirect.ca (192.168.0.135): icmp_seq=96 ttl=255 
time=2.83 ms
  ^C
  --- 10gb-sw1.office.netdirect.ca ping statistics ---
  96 packets transmitted, 9 received, +56 errors, 90% packet loss, time 95015ms
  rtt min/avg/max/mdev = 0.737/2.427/3.966/1.156 ms, pipe 4

  michael@challenger:~
  ○ → ping 10gb-sw1
  PING 10gb-sw1.office.netdirect.ca (192.168.0.33) 56(84) bytes of data.
  64 bytes from 10gb-sw1.netdirect.ca (192.168.0.33): icmp_seq=1 ttl=255 
time=4.34 ms
  64 bytes from 10gb-sw1.netdirect.ca (192.168.0.33): icmp_seq=2 ttl=255 
time=2.97 ms
  64 bytes from 10gb-sw1.netdirect.ca (192.168.0.33): icmp_seq=3 ttl=255 
time=2.14 ms
  ^C
  --- 10gb-sw1.office.netdirect.ca ping statistics ---
  3 packets transmitted, 3 received, 0% packet loss, time 2002ms
  rtt min/avg/max/mdev = 2.146/3.156/4.344/0.907 ms

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: iputils-ping 3:20121221-4ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun  5 09:50:13 2014
  InstallationDate: Installed on 2013-09-09 (268 days ago)
  InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 
(20130423.1)
  SourcePackage: iputils
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (48 days ago)

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

2014-12-23 Thread Michael Kuhn
Created attachment 93
Respect fontconfig's hintstyle

I am currently using the attached minimal patch to make cairo respect
fontconfig's hintstyle; it will probably need to be adapted for the
other parameters.

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

Title:
  some ~/.fonts.conf settings do no override desktop-wide gnome settings
  (hinting style)

Status in Cairo Graphics Library:
  Confirmed
Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  I didn't fill out the package field, since this seems to be an
  interaction between multiple packages (gnome-setting-daemon, libgtk,
  libcairo, pango/cairo).

  In the 'Appearance' control app, under the font settings, I like to
  use 'Subpixel' and 'Full' hinting by default, since this looks good
  for most bundled fonts.

  However, there is occasionally a font (especially in the msttcorefonts
  package) that doesn't look good with these settings. So I want to
  override their rendering settings using .fonts.conf. My main tactic is
  to usually turn on the autohinter in 'hintslight' mode for certain
  fonts. Lets take Times new Roman as an example.. the .fonts.conf
  incantation to do this would be:

   match target=font
   test name=family qual=any 
   stringTimes New Roman/string
   /test
  edit name=autohint booltrue/bool/edit
  edit name=hinting booltrue/bool/edit
  edit name=hintstyle  consthintslight/const /edit
   /match

  The odd thing about this is that the 'autohint' and 'hinting' edits
  seem to work, but the 'hintstyle' edit is always overridden by the
  control applet's settings. I can verify this by launching gedit each
  time after tweaking these settings.

  fc-match -v 'Times New Roman' does return the right settings, so its
  something in the chain of gtk libraries that is messing it up.

  Interstingly, it's not all possible edit settings that are ignored. It
  seems to only be hintstyle. For example if I were to say:

  
   match target=font
   test name=family qual=any 
   stringTimes New Roman/string
   /test
  edit name=antialias bool false /bool /edit
   /match

  Then this works correctly. Only Times New Roman will be non-antialiased even 
in gedit. Even setting hinting to false works.. its only the hintstyle 
setting that doesn't work.
  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX 
Host bridge [8086:7190] (rev 01)
Subsystem: VMware Inc Device [15ad:1976]
  00:0f.0 VGA compatible controller [0300]: VMware Inc Abstract SVGA II Adapter 
[15ad:0405]
Subsystem: VMware Inc Abstract SVGA II Adapter [15ad:0405]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/161058/+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 1400203] Re: libsystemd-login sd_login_monitor_new not working

2014-12-23 Thread Martin Pitt
I uploaded the fix to the SRU review queue.

** Changed in: systemd (Ubuntu Utopic)
   Status: Triaged = In Progress

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

Title:
  libsystemd-login sd_login_monitor_new not working

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Utopic:
  In Progress

Bug description:
  There is a C API in libsystemd-login for receiving notifications, see
  sd_login_monitor_new(3). It is not working in the Utopic version of
  systemd, because it attempts to access /run/systemd/machines which
  does not exist on utopic.

  I see a patch to fix this in the older, Trusty Tahr version of systemd
  (http://bazaar.launchpad.net/~ubuntu-
  branches/ubuntu/trusty/systemd/trusty/view/head:/debian/patches/login-
  monitor-no-machine.patch). The patch isn't in the utopic systemd
  (208-8ubuntu8).

  I tracked down an issue in NetworkManager which I believe was due to
  this issue. Attached is a C program to demonstrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400203/+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 1366332] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg

2014-12-23 Thread David Margrave
*** This bug is a duplicate of bug 1263540 ***
https://bugs.launchpad.net/bugs/1263540

come on you guys.  get it together

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 14.04
  apt 1.0.1ubuntu2.1

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://extras.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 16126D3A3E5C1192
  W: GPG error: http://archive.canonical.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://qgis.org trusty InRelease: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
030561BEDD45F6C3
  W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
  W: GPG error: http://dl.google.com stable Release: The following signatures 
couldn't be verified because the public key is not available: NO_PUBKEY 
A040830F7FAC5991
  W: GPG error: http://archive.ubuntu.com trusty Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://archive.ubuntu.com trusty-updates Release: The following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
  W: GPG error: http://archive.ubuntu.com trusty-security Release: The 
following signatures couldn't be verified because the public key is not 
available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  sudo apt-key clean didn't help

  The only ultimate solution was to remove all the keys from
  /etc/apt/trusted.gpg.d and run

  sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys KEY

  for each key that was missing.


  Here is a reference bug for 13.10 
  https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1263540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1366332/+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 1263540] Re: Apt-get reports NO_PUBKEY gpg error for keys that are present in trusted.gpg.

2014-12-23 Thread David Margrave
yes empting /etc/apt/trusted.gpg.d directory worked for me as well.

very annoying how it silently choked on contents of that directory.

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

Title:
  Apt-get reports NO_PUBKEY gpg error for keys that are present in
  trusted.gpg.

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  apt  0.9.9.1~ubuntu3

  'apt-get update' has started showing several warnings like the
  following, even though the keys are present:

  W: GPG error: http://us.archive.ubuntu.com saucy Release: The
  following signatures couldn't be verified because the public key is
  not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32

  'apt-key list' shows the keys in question in its output...

  pub   1024D/437D05B5 2004-09-12
  uid  Ubuntu Archive Automatic Signing Key 
ftpmas...@ubuntu.com
  sub   2048g/79164387 2004-09-12

  pub   4096R/C0B21F32 2012-05-11
  uid  Ubuntu Archive Automatic Signing Key (2012) 
ftpmas...@ubuntu.com

  ...and its output begins with the following:

  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-y-ppa-
  manager.gpg': resource limit

  I see the same gpg message when I manually update/remove/add the keys
  in question. E.g.:

  $ sudo apt-key update
  gpg: keyblock resource `/etc/apt/trusted.gpg.d//webupd8team-java.gpg': 
resource limit
  gpg: keyblock resource 
`/etc/apt/trusted.gpg.d//webupd8team-y-ppa-manager.gpg': resource limit
  gpg: key 437D05B5: Ubuntu Archive Automatic Signing Key 
ftpmas...@ubuntu.com not changed
  gpg: key FBB75451: Ubuntu CD Image Automatic Signing Key 
cdim...@ubuntu.com not changed
  gpg: key C0B21F32: Ubuntu Archive Automatic Signing Key (2012) 
ftpmas...@ubuntu.com not changed
  gpg: key EFE21092: Ubuntu CD Image Automatic Signing Key (2012) 
cdim...@ubuntu.com not changed
  gpg: Total number processed: 4
  gpg:  unchanged: 4

  I asked about the resource limit message on the gnupg-users mailing list...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23300.html
  Based on Werner Koch's (the dev) answer...
  http://www.mail-archive.com/gnupg-users@gnupg.org/msg23302.html
  ...the secure apt related programs might be making gpg use more than the 
maximum number of keyrings that it can handle.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1263540/+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 1385624] Re: wrapper-2.0 crashed with SIGSEGV in strrchr()

2014-12-23 Thread Alistair Buxton
Did you attempt to add the indicator-menu (global menu indicator)?
Because that does not work, will crash like this, and is unsupported.

** Also affects: xfce4-indicator-plugin (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  wrapper-2.0 crashed with SIGSEGV in strrchr()

Status in gtk+3.0 package in Ubuntu:
  New
Status in xfce4-indicator-plugin package in Ubuntu:
  New
Status in xfce4-panel package in Ubuntu:
  Confirmed

Bug description:
  It just crashed.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: xfce4-panel 4.11.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-23.31-lowlatency 3.16.4
  Uname: Linux 3.16.0-23-lowlatency x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 25 12:26:05 2014
  ExecutablePath: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0
  InstallationDate: Installed on 2011-11-13 (1076 days ago)
  InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcCmdline: /usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-2.0 
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libindicator-plugin.so 5 18874401 
indicator Indicator\ Plugin Provides\ a\ panel\ area\ for\ Unity\ indicators.\ 
Indicators\ allow\ applications\ and\ system\ services\ to\ display\ their\ 
status\ and\ interact\ with\ the\ user.
  SegvAnalysis:
   Segfault happened at: 0x7f6d654461f5 strrchr+37:   movdqu (%rdi),%xmm0
   PC (0x7f6d654461f5) ok
   source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
   destination %xmm0 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: xfce4-panel
  StacktraceTop:
   strrchr () at ../sysdeps/x86_64/strrchr.S:32
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
  Title: wrapper-2.0 crashed with SIGSEGV in strrchr()
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (0 days ago)
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin 
mythtv netdev plugdev sambashare scanner tape vboxusers video wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1385624/+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 1405154] Re: firefox windows move with workspace change

2014-12-23 Thread Stephen Davis
Thank you for the support. I just tried that and it did not solve the
issue. However, I noticed that the issue only happens if the application
are setting on my 2nd external monitor. If i leave them in the primary
monitor then the described behavior does not happen.

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

Title:
  firefox windows move with workspace change

Status in unity package in Ubuntu:
  Incomplete

Bug description:
  When changing workspaces the firefox web browser window moves with the
  workspace change (always staying on the current workspace). This
  happens both when using the keyboard shortcut and the gui applet. I
  cannot designate different workspaces with different browser windows
  because of this. This is very frusterating.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.3+14.04.20140826-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Dec 23 04:54:06 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:029b]
 Subsystem: Acer Incorporated [ALI] Device [1025:029b]
  InstallationDate: Installed on 2014-12-20 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Acer Aspire 1410
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=59ff4d47-8eb9-4ee8-8876-0128499dc5af ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1410:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1410
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Dec 20 15:52:55 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9411 
   vendor ACI
  xserver.version: 2:1.15.1-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1405154/+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 1315369] Re: Log in not available after lock screen with multi-monitor

2014-12-23 Thread Stephen Rasku
I had this problem when I came back from lunch today.  I am running a
desktop with two DisplayPort monitors.  I was able to move the cursor
from monitor to monitor but no prompt appeared to allow me to enter my
password.  I had to go into a text console to reboot.  I had a VM
running which got aborted so this is very annoying.

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

Title:
  Log in not available after lock screen with multi-monitor

Status in Unity:
  Invalid
Status in X.org xf86-video-intel:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed
Status in unity source package in Trusty:
  Confirmed

Bug description:
  After the screen locks I am unable to log back in because the screen
  with the login prompt is black, and the screen on my laptop just shows
  the Ubuntu logo.

  Furthermore, if I then unplug the external monitor (in an attempt to
  force the log in option to be displayed on the laptop)  the laptop
  screen then goes black and I can't do anything at all.

  I can't reproduce this if I select lock screen from the UI, but it
  happens reliably if it locks due to inactivity.

  Other info:
  - I am running a fresh install of 14.04
  - I have it set to lock after 5 min of inactivity, and require login after 
lock
  - I have an external monitor, configured to be on the left side of the laptop 
screen
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jane   2184 F pulseaudio
   /dev/snd/controlC0:  jane   2184 F pulseaudio
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=61f52096-031e-4e3d-b1ae-e504b3b3edec
  InstallationDate: Installed on 2014-05-01 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: Dell Inc. Dell System XPS L321X
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  PackageArchitecture: i386
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro persistent quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  Tags:  trusty trusty
  Uname: Linux 3.13.0-24-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 085X6F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd04/09/2012:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn085X6F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L321X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1315369/+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 1405213] [NEW] + , instead of @

2014-12-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I want to write an email address in the to field of evolution, I
can't get an @. With pressing Q and AltGr (German Layout) I get   +
, instead of @.

This Bug also has been filed with #1ß59107 and #943104

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: xorg 1:7.7+7ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Dec 23 16:58:31 2014
DistUpgraded: 2014-10-25 00:44:05,240 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation ION VGA [10de:087d] (rev b1) (prog-if 00 [VGA controller])
   Subsystem: Foxconn International, Inc. Device [105b:0d52]
InstallationDate: Installed on 2013-10-23 (426 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: Foxconn nT-330i
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=6e1a06f8-261a-478b-b6e6-281d84414af5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to utopic on 2014-10-24 (59 days ago)
dmi.bios.date: 12/15/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
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.:bvr080015:bd12/15/2009:svnFoxconn:pnnT-330i:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: nT-330i
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: Foxconn
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Tue Dec 23 16:00:00 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputLogitech USB Receiver KEYBOARD, id 8
 inputLogitech USB Receiver KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
 NOUVEAU(0): [COPY] failed to allocate class.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic
-- 
  + , instead of @
https://bugs.launchpad.net/bugs/1405213
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 943104] [NEW] recipient address: comma inserted when pressing AltGr

2014-12-23 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I want to send a message using evolution. When I type the recipient address 
pippo.pa...@pluto.com I notice a comma followed by a blank character before the 
@ character, and these two spare characters are inserted every time I press  
AltGr in my keyboard (italian localisation), I experience this behaviour  just 
in A:(TO:)  CC: and CCN: (BCC): fields.
See the attached screen shot

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: evolution 3.2.3-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CasperVersion: 1.304
Date: Wed Feb 29 07:23:44 2012
LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Beta i386 (20120228.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: apport-bug i386 iso-testing needs-ac precise
-- 
recipient address: comma inserted when pressing AltGr
https://bugs.launchpad.net/bugs/943104
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1405213] Re: + , instead of @

2014-12-23 Thread Christopher M. Penalver
Gerhard Beck, thank you for reporting this and helping make Ubuntu
better. Please answer all of the following questions:

+ Did this problem not occur in a release prior to 14.10?

+ Does this problem occur in other programs or just Evolution?

** This bug is no longer a duplicate of bug 943104
   recipient address: comma inserted when pressing AltGr

** No longer affects: xorg (Ubuntu)

** Project changed: evolution = xorg (Ubuntu)

** Changed in: xorg (Ubuntu)
   Status: New = Incomplete

** Description changed:

  When I want to write an email address in the to field of evolution, I
  can't get an @. With pressing Q and AltGr (German Layout) I get   +
  , instead of @.
- 
- This Bug also has been filed with #1ß59107 and #943104
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Dec 23 16:58:31 2014
  DistUpgraded: 2014-10-25 00:44:05,240 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  NVIDIA Corporation ION VGA [10de:087d] (rev b1) (prog-if 00 [VGA controller])
-Subsystem: Foxconn International, Inc. Device [105b:0d52]
+  NVIDIA Corporation ION VGA [10de:087d] (rev b1) (prog-if 00 [VGA controller])
+    Subsystem: Foxconn International, Inc. Device [105b:0d52]
  InstallationDate: Installed on 2013-10-23 (426 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Foxconn nT-330i
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=6e1a06f8-261a-478b-b6e6-281d84414af5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (59 days ago)
  dmi.bios.date: 12/15/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  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.:bvr080015:bd12/15/2009:svnFoxconn:pnnT-330i:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: nT-330i
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: Foxconn
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  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.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Dec 23 16:00:00 2014
  xserver.configfile: default
  xserver.devices:
-  inputPower Button KEYBOARD, id 6
-  inputPower Button KEYBOARD, id 7
-  inputLogitech USB Receiver KEYBOARD, id 8
-  inputLogitech USB Receiver KEYBOARD, id 9
-  inputAT Translated Set 2 keyboard KEYBOARD, id 10
+  inputPower Button KEYBOARD, id 6
+  inputPower Button KEYBOARD, id 7
+  inputLogitech USB Receiver KEYBOARD, id 8
+  inputLogitech USB Receiver KEYBOARD, id 9
+  inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
-  Failed to load module nvidia (module does not exist, 0)
-  Failed to load module nvidia (module does not exist, 0)
-  NOUVEAU(0): [COPY] failed to allocate class.
+  Failed to load module nvidia (module does not exist, 0)
+  Failed to load module nvidia (module does not exist, 0)
+  NOUVEAU(0): [COPY] failed to allocate class.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1.2
  xserver.video_driver: nouveau

** Changed in: xorg (Ubuntu)
   Importance: Undecided = Low

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

Title:
+ , 

[Touch-packages] [Bug 943104] Re: recipient address: comma inserted when pressing AltGr

2014-12-23 Thread Christopher M. Penalver
Berenyi Peter, thank you for your comment. So your problem and hardware may be 
tracked, could you please file a new report by executing the following in a 
terminal:
ubuntu-bug xorg

Please ensure you have xdiagnose installed, and that you click the Yes
button for attaching additional debugging information.

For more on this, please see the official Ubuntu documentation:
Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: 
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Community: 
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report will delay your problem being
addressed as quickly as possible.

As well, please do not announce in this report you created a new bug
report.

Thank you for your understanding.

** Changed in: xserver-xorg-input-evdev (Ubuntu)
   Status: Confirmed = Incomplete

** Tags added: needs-ac

** Package changed: xserver-xorg-input-evdev (Ubuntu) = xorg (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/943104

Title:
  recipient address: comma inserted when pressing AltGr

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to send a message using evolution. When I type the recipient address 
pippo.pa...@pluto.com I notice a comma followed by a blank character before the 
@ character, and these two spare characters are inserted every time I press  
AltGr in my keyboard (italian localisation), I experience this behaviour  just 
in A:(TO:)  CC: and CCN: (BCC): fields.
  See the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: evolution 3.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  CasperVersion: 1.304
  Date: Wed Feb 29 07:23:44 2012
  LiveMediaBuild: Edubuntu 12.04 Precise Pangolin - Beta i386 (20120228.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/943104/+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 1405277] [NEW] screen flicker in ubuntu 14.04.1 and derivatives

2014-12-23 Thread hansie
Public bug reported:

1. my screen flickers on all ubuntu 14.04.1 distro versions, linux mint
17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

2. it flickers on the mint 17.1 'cinamon' installation disk - but it is
stable on mint 17.0 'mate' installed

3. i can cure it by accesing the 'recovery section' of the 'multi-boot'
system: but it is NOT 'persistent'

4. how can i fix this, using the 'cli': to make the fix 'permanent'

the laptop is an older 'toshiba - amd - athlon x2'

** Affects: xorg (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/1405277

Title:
  screen flicker in ubuntu 14.04.1 and derivatives

Status in xorg package in Ubuntu:
  New

Bug description:
  1. my screen flickers on all ubuntu 14.04.1 distro versions, linux
  mint 17.1 'cinamon', lxle 64 bit, guadalinex v9 32 bit, etc.

  2. it flickers on the mint 17.1 'cinamon' installation disk - but it
  is stable on mint 17.0 'mate' installed

  3. i can cure it by accesing the 'recovery section' of the 'multi-
  boot' system: but it is NOT 'persistent'

  4. how can i fix this, using the 'cli': to make the fix 'permanent'

  the laptop is an older 'toshiba - amd - athlon x2'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1405277/+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 1404779] Re: Hp Designjet 130 prints part of page then freezes

2014-12-23 Thread Rod Boudreaux
correction:replace msdos with windows xp.

rod

** Also affects: cups (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Hp Designjet 130 prints part of page then freezes

Status in Apport crash detection/reporting:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  Cups

  Printer works under msdos. Have not been able to get full page printed under 
ubuntu. Prints A few lines to 1/3 page then freezes. must remove power to reset 
and remove paper. All controls freeze.
  Tried on several computers and ver of O/s. Currently 14.04. See attached 
Printer cmd report. Per lunchpad direction.

  
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ lsmod | grep usb
  usblp  18277  0 
  usbhid 47070  0 
  hid87604  2 hid_generic,usbhid
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ tail -f /var/log/syslog
  Dec 21 21:45:39 rod-HP-Compaq-dc7900-Convertible-Minitower python: 
io/hpmud/musb.c 2105: ignoring hp:/usb/hp_designjet_130?serial=MY6AID80CM 
support=0
  Dec 21 21:45:39 rod-HP-Compaq-dc7900-Convertible-Minitower python: 
io/hpmud/pp.c 627: unable to read device-id ret=-1
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.816339] type=1400 audit(1419216354.023:68): apparmor=DENIED 
operation=signal profile=/usr/sbin/cupsd pid=2520 comm=cups-deviced 
requested_mask=send denied_mask=send signal=term peer=unconfined
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.818276] type=1400 audit(1419216354.023:69): apparmor=DENIED 
operation=signal profile=/usr/sbin/cupsd pid=2150 comm=cupsd 
requested_mask=send denied_mask=send signal=term peer=unconfined
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.820058] parport0: lp tried to release parport when not owner
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.820072] parport0: ppdev0 forgot to release port
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2294.664108] usb 3-2: USB disconnect, device number 4
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2294.664280] usblp0: removed
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: remove /devices/pci:00/:00:1a.0/usb3/3-2
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower colord: device 
removed: sysfs-Hewlett-Packard-hp_designjet_130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.104036] usb 3-2: new full-speed USB device number 5 using uhci_hcd
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303075] usb 3-2: New USB device found, idVendor=03f0, idProduct=0314
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303080] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303083] usb 3-2: Product: hp designjet 130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303085] usb 3-2: Manufacturer: Hewlett-Packard
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303088] usb 3-2: SerialNumber: MY6AID80CM
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.334166] usblp 3-2:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 
proto 2 vid 0x03F0 pid 0x0314
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower logger: loading HP 
Device 003 005
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower colord: Device 
added: sysfs-Hewlett-Packard-hp_designjet_130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: add /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: device devpath is 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: Device already handled
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower 
hp-config_usb_printer: hp-config_usb_printer[2617]: error: This is not a valid 
device
  ^C
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ lsusb
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 

[Touch-packages] [Bug 1405289] [NEW] network-manager reports usb link as disconnected

2014-12-23 Thread Gilles Pietri
Public bug reported:

When I plug my Motorola XT910 (Razr Max) as USB, with connection sharing
on USB enabled on the phone, network-manager sees it, but reports it as
disconnected. If I activate the usb0 interface manually (ifconfig /
dhclient), it works, flawlessly.

I set network manager to log debug info, this is what I get, once the device is 
plugged in (MAC  S/N removed) :
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.827268] usb 1-2: new high-speed USB 
device number 10 using xhci_hcd
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.278667] 
[nm-netlink-monitor.c:164] link_msg_handler(): netlink link message: iface idx 
5 flags 0x1002
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.955942] usb 1-2: New USB device 
found, idVendor=22b8, idProduct=431c
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.955945] usb 1-2: New USB device 
strings: Mfr=2, Product=3, SerialNumber=4
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.955947] usb 1-2: Product: XT910
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.955949] usb 1-2: Manufacturer: 
Motorola
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.955950] usb 1-2: SerialNumber: X
Dec 23 20:15:00 gilles-M3800 kernel: [ 3959.957736] rndis_host 1-2:1.0 usb0: 
register 'rndis_host' at usb-:00:14.0-2, RNDIS device, xx:xx:xx:xx:xx:xx
Dec 23 20:15:00 gilles-M3800 mtp-probe: checking bus 1, device 10: 
/sys/devices/pci:00/:00:14.0/usb1/1-2
Dec 23 20:15:00 gilles-M3800 mtp-probe: bus: 1, device: 10 was not an MTP device
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/net/usb0, iface: usb0)
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]:SCPlugin-Ifupdown: device 
added (path: /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/net/usb0, 
iface: usb0): no ifupdown configuration found.
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.301139] 
[nm-udev-manager.c:563] handle_uevent(): UDEV event: action 'add' subsys 'net' 
device 'usb0'
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: warn failed to allocate 
link cache: (-26) Protocol mismatch
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.301528] 
[nm-device-ethernet.c:1624] supports_ethtool_carrier_detect(): ethtool is 
supported
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.301609] 
[nm-device-wired.c:313] constructor(): (usb0): kernel ifindex 5
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): carrier is OFF
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.301765] 
[nm-device-ethernet.c:261] constructor(): (usb0): kernel ifindex 5
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.302205] 
[nm-device-ethernet.c:485] update_initial_hw_address(): (usb0): read initial 
MAC address 62:A4:06:B5:C8:73
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): new Ethernet 
device (driver: 'rndis_host' ifindex: 5)
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): exported as 
/org/freedesktop/NetworkManager/Devices/3
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.302928] 
[nm-device.c:5333] nm_device_set_managed(): (usb0): now managed
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): device state 
change: unmanaged - unavailable (reason 'managed') [10 20 2]
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): bringing up 
device.
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): carrier now 
ON (device state 20)
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303239] 
[nm-device.c:5272] nm_device_queue_state(): (usb0): queued state change to 
disconnected (id 657)
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): preparing 
device.
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: info (usb0): deactivating 
device (reason 'managed') [2]
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303338] 
[nm-device.c:5295] nm_device_queued_state_clear(): (usb0): clearing queued 
state transition (id 657)
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303355] 
[NetworkManagerUtils.c:637] nm_utils_do_sysctl(): sysctl: setting 
'/proc/sys/net/ipv6/conf/usb0/accept_ra' to '0'
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303371] 
[NetworkManagerUtils.c:637] nm_utils_do_sysctl(): sysctl: setting 
'/proc/sys/net/ipv6/conf/usb0/use_tempaddr' to '0'
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303380] 
[nm-device-ethernet.c:384] _set_hw_addr(): (usb0): no MAC address change needed
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303416] 
[nm-system.c:1404] nm_system_iface_flush_routes(): (usb0): flushing routes 
ifindex 5 family INET (2)
Dec 23 20:15:00 gilles-M3800 NetworkManager[1284]: debug [1419362100.303468] 
[nm-netlink-utils.c:356] dump_route():   route idx 1 family INET (2) addr 

[Touch-packages] [Bug 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites

2014-12-23 Thread navidR
same here

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [GeForce 610M] 
(rev a1)

this is very serious bug and made me really crazy .

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

Title:
  Ubuntu 14.04 random screen freeze while Normal OS activites

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  same symptom described in https://bugs.launchpad.net/ubuntu/+source
  /xorg-server/+bug/1184451

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia wl
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May  1 09:21:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:044d]
   NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:044d]
  InstallationDate: Installed on 2014-04-27 (3 days ago)
  InstallationMedia: Ubuntu-Kylin 14.04 LTS Trusty Tahr - Release amd64 
(20140417.1)
  MachineType: Dell Inc. Vostro 3400
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RXV7H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A10
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Vostro 3400
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2

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

2014-12-23 Thread Jakub-gcc
GCC 4.8.4 has been released.

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

Title:
  [4.8 Regression] unable to find a register to spill in class 'LO_REGS'

Status in The GNU Compiler Collection:
  New
Status in Linaro GCC:
  Triaged
Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  seen with the 4.8 branch on arm-linux-gnueabihf, configured with
  --with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb 

  omitting the -fno-tree-dce works around the issue.  not seen with the
  4.7 branch and trunk 20140306.

  $ g++ -std=c++11 -fPIC -fno-tree-dce -fno-exceptions -fno-omit-frame-pointer 
-c -g -O2 JITArithmetic32_64.ii
  ../Source/JavaScriptCore/jit/JITArithmetic32_64.cpp: In member function 'void 
JSC::JIT::emit_op_add(JSC::Instruction*)':
  ../Source/JavaScriptCore/jit/JITArithmetic32_64.cpp:526:1: error: unable to 
find a register to spill in class 'LO_REGS'
  ../Source/JavaScriptCore/jit/JITArithmetic32_64.cpp:526:1: error: this is the 
insn:
  (insn 335 334 336 20 (parallel [
  (set (reg:SI 3 r3)
  (ior:SI (eq:SI (reg/v:SI 112 [ op ])
  (reg/v:SI 110 [ dst ]))
  (eq:SI (reg/v:SI 111 [ op ])
  (reg/v:SI 110 [ dst ]
  (clobber (reg:CC 100 cc))
  ]) ../Source/JavaScriptCore/jit/JITArithmetic32_64.cpp:514 295 
{*ior_scc_scc}
   (expr_list:REG_UNUSED (reg:CC 100 cc)
  (nil)))
  ../Source/JavaScriptCore/jit/JITArithmetic32_64.cpp:526: confused by earlier 
errors, bailing out
  Preprocessed source stored into /tmp/ccb0Osgc.out file, please attach this to 
your bugreport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1295738/+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 1396250] Re: Continually am prompted for Google credentials. First time pwd is always wrong, 2nd input takes. This happened on Debian Jessie awhile ago too.

2014-12-23 Thread Alberto Salvia Novella
** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Continually am prompted for Google credentials. First time pwd is
  always wrong, 2nd input takes. This happened on Debian Jessie awhile
  ago too.

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  It happens at intermittent times, there is no logic to it in terms of
  I do this and it happens. Always the 1st attempt is wrong, regardless
  if the pwd is correct or not. Very irritating.

  Not absolutely sure if this should be filed against Gnome proper or
  GOA. So, feel free to change to the appropriate package if this is
  wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gnome-online-accounts 3.12.4-1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Nov 25 11:57:53 2014
  InstallationDate: Installed on 2014-11-23 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 
(20141022.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1396250/+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 1393090] Re: Apparmor errors on login

2014-12-23 Thread Alberto Salvia Novella
** Changed in: cups (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  Apparmor errors on login

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to utopic (from trusty), I keep getting these AppArmor 
errors when I log in:
  Nov 15 22:40:41 nibbler kernel: [   34.872860] audit: type=1400 
audit(1416087641.731:66): apparmor=STATUS operation=profile_replace 
profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=3381 
comm=apparmor_parser
  Nov 15 22:40:41 nibbler kernel: [   34.872872] audit: type=1400 
audit(1416087641.731:67): apparmor=STATUS operation=profile_replace 
profile=unconfined name=/usr/sbin/cupsd pid=3381 comm=apparmor_parser
  Nov 15 22:40:41 nibbler kernel: [   34.879454] audit: type=1400 
audit(1416087641.739:68): apparmor=STATUS operation=profile_replace 
profile=unconfined name=third_party pid=3381 comm=apparmor_parser

  I've been searching for information about this but finding anything
  useful is quite challenging as many people have these messages in
  their log when reporting completely different problems (and just
  providing a full syslog).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Sat Nov 15 23:24:33 2014
  InstallationDate: Installed on 2012-04-26 (933 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=BR893FF10S052D
   device for Deskjet_F4200: hp:/usb/Deskjet_F4200_series?serial=BR893FF10S052D
  MachineType: TOSHIBA SATELLITE Z830
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_F4200.ppd', '/etc/cups/ppd/Deskjet-F4200-series.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Deskjet_F4200.ppd: Permission 
denied
   grep: /etc/cups/ppd/Deskjet-F4200-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=36929bf3-a158-44d9-a80d-3adac2840fa8 ro quiet splash 
acpi_backlight=vendor pcie_aspm=force i915.enable_rc6=7 i915.enable_fbc=1 
i915.lvds_downclock=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-11-08 (7 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.80
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00300GGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: SATELLITE Z830
  dmi.product.version: PT22LE-00300GGR
  dmi.sys.vendor: TOSHIBA
  mtime.conffile..etc.cups.cupsd.conf: 2013-05-30T23:09:49.798492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1393090/+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 1399924] Re: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

2014-12-23 Thread Alberto Salvia Novella
** Changed in: sudo (Ubuntu)
   Importance: Undecided = High

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

Title:
  package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  nothing happens just a window at every startup appears about fixing
  the problem

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: sudo 1.8.9p5-1ubuntu2
  Uname: Linux 3.14.1-031401-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Fri Dec  5 01:47:59 2014
  DuplicateSignature: package:sudo:1.8.9p5-1ubuntu2:subprocess installed 
pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2014-06-23 (165 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: sudo
  Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (39 days ago)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1399924/+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 1365186] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@148:collect_info:process_report

2014-12-23 Thread Alberto Salvia Novella
It renders essential functionality of the package (or a dependent one)
broken.

** Changed in: apport (Ubuntu)
   Importance: Undecided = High

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@148:collect_info:process_report

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/6dcf56089700281d1f9a22242799e14f4c7c60ab
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1365186/+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 1404188] Re: QNetworkSession::isOpen() always returns false

2014-12-23 Thread Lorn Potter
[05:34:57] lpotter QDBusConnection: error: could not send message to service 
org.freedesktop.NetworkManager path  interface 
org.freedesktop.DBus.Introspectable member Introspect: 
[05:35:01] lpotter hmm
[05:35:24] mzanetti oh, you're still working. I hope it's not just for this
[05:35:34] lpotter morning time :)
[05:35:44] lpotter just thought I'd look at it
[05:35:50] mzanetti ok :)
[05:35:58] mzanetti that looks like apparmor
[05:36:05] lpotter there's also some other odd output
[05:36:15] lpotter yes, my thought too
[05:36:56] mzanetti not sure if we can convince jamie to allow apps calling 
Introspect on that interface
[05:40:09] lpotter there was another bug mentioning that abstract dbus 
interface does not introspect, whereas QDBusInterface does
[05:40:41] mzanetti ah, that might well be true
[05:40:56] lpotter I use QDBusInterface all over in those classes
[05:41:40] mzanetti hmm, I guess if that would solve the issue it would be 
way to go... I think it's also in upstream's interest to allow more fine 
grained control on Qt's permissions
[05:49:05] lpotter wish I could remember what bug was that. it was only 
yesterday I looked at it
[05:50:33] lpotter ahh 1403508
[05:54:05] lpotter I even thought about changing those to use 
QDBusAbstractInterface when I was updating it

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

Title:
  QNetworkSession::isOpen() always returns false

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

Bug description:
  Using QNetworkSession::isOpen() in confined apps on a phone running
  vivid always returns false. This might be an apparmor thing, however,
  I couldn't find any REJECTED entries in log files.

  The test app in lp:~mzanetti/+junk/nmsessiontest can reproduce the
  issue. Open this project in ubuntu-sdk's qtcreator and run it on a
  vivid device. Press the button and watch the debug prints.

  On a vivid-desktop or a RTM based phone it will print all is well.
  On a vivid phone however, it'll print network session not open...

  This used to work fine at least back in utopic images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1404188/+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 1393090] Re: Apparmor errors on login

2014-12-23 Thread Till Kamppeter
pitti, Jamie, are these really eror messages? Or are these messages of
the startup of AppArmor which are normal?

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

Title:
  Apparmor errors on login

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to utopic (from trusty), I keep getting these AppArmor 
errors when I log in:
  Nov 15 22:40:41 nibbler kernel: [   34.872860] audit: type=1400 
audit(1416087641.731:66): apparmor=STATUS operation=profile_replace 
profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=3381 
comm=apparmor_parser
  Nov 15 22:40:41 nibbler kernel: [   34.872872] audit: type=1400 
audit(1416087641.731:67): apparmor=STATUS operation=profile_replace 
profile=unconfined name=/usr/sbin/cupsd pid=3381 comm=apparmor_parser
  Nov 15 22:40:41 nibbler kernel: [   34.879454] audit: type=1400 
audit(1416087641.739:68): apparmor=STATUS operation=profile_replace 
profile=unconfined name=third_party pid=3381 comm=apparmor_parser

  I've been searching for information about this but finding anything
  useful is quite challenging as many people have these messages in
  their log when reporting completely different problems (and just
  providing a full syslog).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Sat Nov 15 23:24:33 2014
  InstallationDate: Installed on 2012-04-26 (933 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=BR893FF10S052D
   device for Deskjet_F4200: hp:/usb/Deskjet_F4200_series?serial=BR893FF10S052D
  MachineType: TOSHIBA SATELLITE Z830
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_F4200.ppd', '/etc/cups/ppd/Deskjet-F4200-series.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Deskjet_F4200.ppd: Permission 
denied
   grep: /etc/cups/ppd/Deskjet-F4200-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=36929bf3-a158-44d9-a80d-3adac2840fa8 ro quiet splash 
acpi_backlight=vendor pcie_aspm=force i915.enable_rc6=7 i915.enable_fbc=1 
i915.lvds_downclock=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-11-08 (7 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.80
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00300GGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: SATELLITE Z830
  dmi.product.version: PT22LE-00300GGR
  dmi.sys.vendor: TOSHIBA
  mtime.conffile..etc.cups.cupsd.conf: 2013-05-30T23:09:49.798492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1393090/+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 1393090] Re: Apparmor errors on login

2014-12-23 Thread Jamie Strandboge
Thank you for using Ubuntu and reporting a bug. These are not errors but
instead normal messages saying that the profiles are being loaded.

** Changed in: cups (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  Apparmor errors on login

Status in cups package in Ubuntu:
  Invalid

Bug description:
  Since I upgraded to utopic (from trusty), I keep getting these AppArmor 
errors when I log in:
  Nov 15 22:40:41 nibbler kernel: [   34.872860] audit: type=1400 
audit(1416087641.731:66): apparmor=STATUS operation=profile_replace 
profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=3381 
comm=apparmor_parser
  Nov 15 22:40:41 nibbler kernel: [   34.872872] audit: type=1400 
audit(1416087641.731:67): apparmor=STATUS operation=profile_replace 
profile=unconfined name=/usr/sbin/cupsd pid=3381 comm=apparmor_parser
  Nov 15 22:40:41 nibbler kernel: [   34.879454] audit: type=1400 
audit(1416087641.739:68): apparmor=STATUS operation=profile_replace 
profile=unconfined name=third_party pid=3381 comm=apparmor_parser

  I've been searching for information about this but finding anything
  useful is quite challenging as many people have these messages in
  their log when reporting completely different problems (and just
  providing a full syslog).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Sat Nov 15 23:24:33 2014
  InstallationDate: Installed on 2012-04-26 (933 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  Lpstat:
   device for Deskjet-F4200-series: 
hp:/usb/Deskjet_F4200_series?serial=BR893FF10S052D
   device for Deskjet_F4200: hp:/usb/Deskjet_F4200_series?serial=BR893FF10S052D
  MachineType: TOSHIBA SATELLITE Z830
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet_F4200.ppd', '/etc/cups/ppd/Deskjet-F4200-series.ppd'] 
failed with exit code 2: grep: /etc/cups/ppd/Deskjet_F4200.ppd: Permission 
denied
   grep: /etc/cups/ppd/Deskjet-F4200-series.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=36929bf3-a158-44d9-a80d-3adac2840fa8 ro quiet splash 
acpi_backlight=vendor pcie_aspm=force i915.enable_rc6=7 i915.enable_fbc=1 
i915.lvds_downclock=1 vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to utopic on 2014-11-08 (7 days ago)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.80
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnSATELLITEZ830:pvrPT22LE-00300GGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: SATELLITE Z830
  dmi.product.version: PT22LE-00300GGR
  dmi.sys.vendor: TOSHIBA
  mtime.conffile..etc.cups.cupsd.conf: 2013-05-30T23:09:49.798492

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1393090/+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 1405327] [NEW] My computer has an Intel i3 processor and no other inbuilt GPU. However, the nvidia-* latest got installed on the computer during an update process. I used sudo ap

2014-12-23 Thread Suddhasheel Ghosh
Public bug reported:

My computer has an Intel i3 processor and no other inbuilt GPU. However,
the nvidia-* latest got installed on the computer during an update
process.

I used sudo apt-get remove nvidia-* to remove all the nvidia related
contents.

Post this event, the unity-desktop has stopped working (in its full
functionality i.e. the sidebar does not appear) and I am now only able
to see the desktop (with the shortcut icons and wallpaper) but not able
to interact with it, nor am I being able to open any applications on it.

What should be done to restore lightdm to its original functionality?

PS: I have already tried the sudo apt-get install --reinstall lightdm

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Dec 24 07:50:26 2014
DistUpgraded: 2014-10-29 07:06:16,700 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:2ac5]
InstallationDate: Installed on 2012-08-09 (866 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
MachineType: Hewlett-Packard 120-1109il
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic 
root=UUID=e10366ce-1bdb-4001-9bd4-db0e1cbd84e6 ro splash quiet
SourcePackage: unity
UpgradeStatus: Upgraded to utopic on 2014-10-29 (56 days ago)
dmi.bios.date: 11/17/2011
dmi.bios.vendor: AMI
dmi.bios.version: LEO_707
dmi.board.name: 2AC5
dmi.board.vendor: Quanta
dmi.board.version: 101
dmi.chassis.asset.tag: 4CS2230G4S
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAMI:bvrLEO_707:bd11/17/2011:svnHewlett-Packard:pn120-1109il:pvr:rvnQuanta:rn2AC5:rvr101:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: 120-1109il
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs 20090808ubuntu36
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
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.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Wed Dec 24 07:27:01 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   16921 
 vendor HWP
xserver.version: 2:1.16.0-1ubuntu1.2

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


** Tags: amd64 apport-bug ubuntu utopic

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

Title:
  My computer has an Intel i3 processor and no other inbuilt GPU.
  However, the nvidia-* latest got installed on the computer during an
  update process.  I used sudo apt-get remove nvidia-* to remove all the
  nvidia related contents.  Post this event, the unity-desktop has
  stopped working (in its full functionality i.e. the sidebar does not
  appear) and I am now only able to see the desktop (with the shortcut
  icons and wallpaper) but not able to interact with it, nor am I being
  able to open any applications on it.  What should be done to restore
  lightdm to its original functionality?  PS: I have already tried the
  sudo apt-get install --reinstall lightdm

Status in unity package in Ubuntu:
  New

Bug description:
  My computer has an Intel i3 processor and no other inbuilt GPU.
  However, the nvidia-* latest got installed on the computer during an
  update process.

  I used sudo apt-get remove nvidia-* to remove all the nvidia related
  contents.

  Post this event, the unity-desktop has stopped working (in its full
  functionality i.e. the sidebar does not appear) and I am now only able
  to see the desktop (with the shortcut icons and wallpaper) but not
  able to interact with it, nor am I being able to open any applications
  on it.

  What should be done to restore lightdm to its 

[Touch-packages] [Bug 1376604] Re: Could not printing from LPT port with Ubuntu

2014-12-23 Thread ubuntuers_medan
/usr/lib/cups/backend/parallel

direct parallel:/dev/lp0 EPSON LQ-300+ EPSON LQ-300+ LPT #1
MFG:EPSON;CMD:ESCPL2,PRPXL24,BDC,D4;MDL:LQ-300+;CLS:PRINTER;DES:EPSON
LQ-300+; 

sudo /usr/lib/cups/backend/parallel
direct parallel:/dev/lp0 EPSON LQ-300+ EPSON LQ-300+ LPT #1 
MFG:EPSON;CMD:ESCPL2,PRPXL24,BDC,D4;MDL:LQ-300+;CLS:PRINTER;DES:EPSON 
LQ-300+; 

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

Title:
  Could not printing from LPT port with Ubuntu

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have lenovo PC edge 73z, this PC has an LPT port. I've tried to
  install Windows in this PC, and it's printing well from LPT, but whe I
  reinstall it with ubuntu 12.04, 13.04, and 14.04, it would not work.

  When I try to add print, it's detecting my printing such as LQ310 and
  LQ2180, but in Printing Tes steps, it can't printing.

  I've also tried to print with the same print and with the same OS but
  at this time via USB, it working well.

  Please, any one have the solution for me?
  ---
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-05-16 (209 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: LENOVO 10AS005HIA
  Package: cups 1.7.2-0ubuntu1.3
  PackageArchitecture: i386
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=444b6b19-2130-4de3-ba34-a24b9f65fb00 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=444b6b19-2130-4de3-ba34-a24b9f65fb00 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Tags: third-party-packages trusty package-from-proposed
  Uname: Linux 3.13.0-35-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/16/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: FCKT46AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: NOK
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrFCKT46AUS:bd12/16/2013:svnLENOVO:pn10AS005HIA:pvrThinkCentreE73:rvnLENOVO:rn:rvrNOK:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10AS005HIA
  dmi.product.version: ThinkCentre E73
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1376604/+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 1200934] Re: evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup()

2014-12-23 Thread Mike Davis
** Changed in: ubuntu-gnome
   Status: Expired = Fix Released

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

Title:
  evolution-source-registry crashed with SIGSEGV in
  g_hash_table_lookup()

Status in Ubuntu GNOME:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  Ass soon I started my machine (with gome 3 with auto login), this
  error raised.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.04
  Package: evolution-data-server 3.8.3-0ubuntu5~ubuntu13.04.2 [origin: 
LP-PPA-gnome3-team-gnome3]
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CrashCounter: 1
  Date: Sat Jul 13 10:28:19 2013
  ExecutablePath: /usr/lib/evolution/evolution-source-registry
  InstallationDate: Installed on 2012-11-01 (253 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/evolution/evolution-source-registry
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=set
   PATH=(custom, no user)
   LANGUAGE=es_AR:zh_CN:en
   LANG=es_AR.UTF-8
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ag_auth_data_get_login_parameters () from 
/usr/lib/x86_64-linux-gnu/libaccounts-glib.so.0
   ?? () from 
/usr/lib/evolution-data-server/registry-modules/module-ubuntu-online-accounts.so
   g_simple_async_result_complete () from 
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: evolution-source-registry crashed with SIGSEGV in g_hash_table_lookup()
  UpgradeStatus: Upgraded to raring on 2013-05-08 (66 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lp lpadmin plugdev sambashare 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1200934/+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 1377519] Re: package util-linux 2.25.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2014-12-23 Thread Launchpad Bug Tracker
[Expired for util-linux (Ubuntu) because there has been no activity for
60 days.]

** Changed in: util-linux (Ubuntu)
   Status: Incomplete = Expired

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

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

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  Instalation error, when upgrade to ubuntu 14.10

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: util-linux 2.25.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Sat Oct  4 22:03:59 2014
  DuplicateSignature: package:util-linux:2.25.1-1ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-04-19 (168 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  SourcePackage: util-linux
  Title: package util-linux 2.25.1-1ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-09-20 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1377519/+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 1324608] Re: when aa-logprof processed file access rules with mask of c the resulting profile doesn't work

2014-12-23 Thread Launchpad Bug Tracker
[Expired for AppArmor because there has been no activity for 60 days.]

** Changed in: apparmor
   Status: Incomplete = Expired

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

Title:
  when aa-logprof processed file access rules with mask of c the
  resulting profile doesn't work

Status in AppArmor Linux application security framework:
  Expired
Status in apparmor package in Ubuntu:
  Expired

Bug description:
  To set the scene

  /usr/local/bin/test2.sh++
  #!/bin/bash

  echo hello world
  cat /etc/passwd
  echo 'echo I am a pink bunny!'  ~/.profile
  ++

  /etc/apparmor.d/usr.local.bin.test2.sh++
  # Last Modified: Thu May 29 11:34:54 2014
  #include tunables/global

  /usr/local/bin/test2.sh {
#include abstractions/base
#include abstractions/bash

/bin/bash ix,
/bin/cat rix,
/dev/tty rw,
/usr/local/bin/test2.sh r,

  }
  ++

  So I run test2.sh and the 
 ~/.profile
  is denied as expected. When I go to run aa-logprof it picks up on the logline

 apparmor=DENIED operation=open
  profile=/usr/local/bin/test2.sh name=/root/.profile pid=30693
  comm=test2.sh requested_mask=c denied_mask=c fsuid=0 ouid=0

  It as me about adding an append mode which makes sense so I add and
  allow. Now my profile looks like so

  /etc/apparmor.d/usr.local.bin.test2.sh++
  # Last Modified: Thu May 29 12:32:31 2014
  #include tunables/global

  /usr/local/bin/test2.sh {
#include abstractions/base
#include abstractions/bash

/bin/bash ix,
/bin/cat rix,
/dev/tty rw,
/root/.profile a,
/usr/local/bin/test2.sh r,

  }
  ++

  The problem is when I run test2.sh again the append rule is still
  denied. I think this likely because although the request_mask of c
  is converted to a by logparser.py in the runtime code (kernel?,
  apparmor_parse?) c is not converted to a nor is a subset of a.
  It is in fact a subset of w which works. Here is the workaround in
  diff format.

  
  --- /usr/lib/python3/dist-packages/apparmor/logparser.py  2014-05-29 
12:39:23.844284290 -0400
  +++ /usr/lib/python3/dist-packages/apparmor/logparser.py.new  2014-05-29 
12:39:11.444283996 -0400
  @@ -126,12 +126,12 @@
   LibAppArmor.free_record(event)
   # Map c (create) to a and d (delete) to w, logprof doesn't support c 
and d
   if rmask:
  -rmask = rmask.replace('c', 'a')
  +rmask = rmask.replace('c', 'w')
   rmask = rmask.replace('d', 'w')
   if not validate_log_mode(hide_log_mode(rmask)):
   raise AppArmorException(_('Log contains unknown mode %s') % 
rmask)
   if dmask:
  -dmask = dmask.replace('c', 'a')
  +dmask = dmask.replace('c', 'w')
   dmask = dmask.replace('d', 'w')
   if not validate_log_mode(hide_log_mode(dmask)):
   raise AppArmorException(_('Log contains unknown mode %s') % 
dmask)

  
  Right now I don't have time to identify where this bug is exactly but if I do 
I will update this ticket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1324608/+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 1324608] Re: when aa-logprof processed file access rules with mask of c the resulting profile doesn't work

2014-12-23 Thread Launchpad Bug Tracker
[Expired for apparmor (Ubuntu) because there has been no activity for 60
days.]

** Changed in: apparmor (Ubuntu)
   Status: Incomplete = Expired

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

Title:
  when aa-logprof processed file access rules with mask of c the
  resulting profile doesn't work

Status in AppArmor Linux application security framework:
  Expired
Status in apparmor package in Ubuntu:
  Expired

Bug description:
  To set the scene

  /usr/local/bin/test2.sh++
  #!/bin/bash

  echo hello world
  cat /etc/passwd
  echo 'echo I am a pink bunny!'  ~/.profile
  ++

  /etc/apparmor.d/usr.local.bin.test2.sh++
  # Last Modified: Thu May 29 11:34:54 2014
  #include tunables/global

  /usr/local/bin/test2.sh {
#include abstractions/base
#include abstractions/bash

/bin/bash ix,
/bin/cat rix,
/dev/tty rw,
/usr/local/bin/test2.sh r,

  }
  ++

  So I run test2.sh and the 
 ~/.profile
  is denied as expected. When I go to run aa-logprof it picks up on the logline

 apparmor=DENIED operation=open
  profile=/usr/local/bin/test2.sh name=/root/.profile pid=30693
  comm=test2.sh requested_mask=c denied_mask=c fsuid=0 ouid=0

  It as me about adding an append mode which makes sense so I add and
  allow. Now my profile looks like so

  /etc/apparmor.d/usr.local.bin.test2.sh++
  # Last Modified: Thu May 29 12:32:31 2014
  #include tunables/global

  /usr/local/bin/test2.sh {
#include abstractions/base
#include abstractions/bash

/bin/bash ix,
/bin/cat rix,
/dev/tty rw,
/root/.profile a,
/usr/local/bin/test2.sh r,

  }
  ++

  The problem is when I run test2.sh again the append rule is still
  denied. I think this likely because although the request_mask of c
  is converted to a by logparser.py in the runtime code (kernel?,
  apparmor_parse?) c is not converted to a nor is a subset of a.
  It is in fact a subset of w which works. Here is the workaround in
  diff format.

  
  --- /usr/lib/python3/dist-packages/apparmor/logparser.py  2014-05-29 
12:39:23.844284290 -0400
  +++ /usr/lib/python3/dist-packages/apparmor/logparser.py.new  2014-05-29 
12:39:11.444283996 -0400
  @@ -126,12 +126,12 @@
   LibAppArmor.free_record(event)
   # Map c (create) to a and d (delete) to w, logprof doesn't support c 
and d
   if rmask:
  -rmask = rmask.replace('c', 'a')
  +rmask = rmask.replace('c', 'w')
   rmask = rmask.replace('d', 'w')
   if not validate_log_mode(hide_log_mode(rmask)):
   raise AppArmorException(_('Log contains unknown mode %s') % 
rmask)
   if dmask:
  -dmask = dmask.replace('c', 'a')
  +dmask = dmask.replace('c', 'w')
   dmask = dmask.replace('d', 'w')
   if not validate_log_mode(hide_log_mode(dmask)):
   raise AppArmorException(_('Log contains unknown mode %s') % 
dmask)

  
  Right now I don't have time to identify where this bug is exactly but if I do 
I will update this ticket.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1324608/+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 1002454] Re: IPv4 DNS preferred over IPv6 ones

2014-12-23 Thread Kevin Otte
NetworkManager is still handing the information to resolvconf in the
wrong order.

root@daedalus:~# lsb_release -d
Description:Ubuntu 14.04.1 LTS

root@daedalus:~# cat /run/resolvconf/interface/NetworkManager 
domain home.nivex.net
search nivex.lan. home.nivex.net home.nivex.net.
nameserver 172.31.3.4
nameserver 2001:470:8:64f::4
nameserver 2606:a000:aa20:2200::4


** Changed in: network-manager (Ubuntu)
   Status: Expired = Confirmed

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

Title:
  IPv4 DNS preferred over IPv6 ones

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The Network Manager always prefers IPv4 DNS over IPv6 ones. The issue
  occurs both when DNSs are statically configured and when they're
  acquired via DHCPv4/DHCPv6.

  Network Manager puts IPv4 DNSs before IPv6 ones in the /var/run/nm-
  dns-dnsmasq.conf so Dnsmasq resolves names using IPv4 DNSs before
  using IPv6 ones.

  If I disable Dnsmasq, DNS servers are put in the wrong way in
  /etc/resolv.conf file.

  The system shoud prefer IPv6 DNSs in any case.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager-gnome 0.9.4.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Mon May 21 21:05:59 2012
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  IpRoute:
   default via 192.168.0.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.0.0/24 dev eth0  proto kernel  scope link  src 192.168.0.217  metric 
1 
   192.168.36.0/24 dev vmnet1  proto kernel  scope link  src 192.168.36.1 
   192.168.70.0/24 dev vmnet8  proto kernel  scope link  src 192.168.70.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to precise on 2012-05-02 (18 days ago)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   eth0-Static   0bcb2b9f-a2c0-46f9-a6b1-59f66e383264   
802-3-ethernet1337627018   lun 21 mag 2012 21:03:38 CEST  yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.4.0connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1002454/+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 1182007] Re: Failed to SUID root

2014-12-23 Thread Asher Diamond
I am still getting this error in 14.10. Is anyone going to fix this?
Looks like some kind of permission problem. Is 'Online Accounts' run as root?

if (getuid() != 0) {
BLAME()  Failed to SUID root. Secure storage will not be available.;
}

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

Title:
  Failed to SUID root

Status in signon package in Ubuntu:
  Confirmed

Bug description:
  signond[7451]: ../../../../src/signond/signondaemon.cpp 360 init
  Failed to SUID root. Secure storage will not be available.

  This report appears in syslog each time Empathy tries and fails to
  connect to Google Talk using the google-talkplugin interface.

  It is not clear whether this SUID report is related to the Empathy
  failure.

  See bug #1168582 Google talk Requires Authorization after
  suspend/resume

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1182007/+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 1354924] Re: Networkmanager does not autoconnect to wireless network

2014-12-23 Thread Nick B.
I've got this same problem too. After doing a fresh boot and logging in,
the wireless will not connect but it is listed in the plasma-nm
connection list. I've found that if I delete it and re-add the
connection it will automatically reconnect after suspend/hibernate until
the next reboot or login. Then it breaks again.

Is anyone else using a hidden network? I'm wondering if that's related.

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/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 disabled

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