[Touch-packages] [Bug 1320394] Re: apparmor denies open /etc/dconf/profile/gdm

[Launchpad Bug Tracker]

[Expired for telepathy-mission-control-5 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: telepathy-mission-control-5 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  apparmor denies open /etc/dconf/profile/gdm

Status in “telepathy-mission-control-5” package in Ubuntu:
  Expired

Bug description:
  I am not sure if this is a bug, but apparmor notification pops up
  everytime I log in to gnome-shell about apparmor errors.

  from kern.log:

  type=1400 audit(1400277302.647:118): apparmor="DENIED"
  operation="mknod" profile="/usr/lib/telepathy/mission-control-5"
  name="/var/lib/gdm/.config/libaccounts-glib/accounts.db" pid=2519 comm
  ="mission-control" requested_mask="c" denied_mask="c" fsuid=114
  ouid=114

  type=1400 audit(1400277302.647:119): apparmor="DENIED"
  operation="open" profile="/usr/lib/telepathy/mission-control-5"
  name="/etc/dconf/profile/gdm" pid=2519 comm="mission-control"
  requested_mask="r" denied_mask="r" fsuid=114 ouid=0

  I am using Ubuntu 14.04 with default gnome 3.10

  telepathy-mission-control-5:
Installed: 1:5.16.1-1ubuntu3
Candidate: 1:5.16.1-1ubuntu3
Version table:
   *** 1:5.16.1-1ubuntu3 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1320394/+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 1326814] Re: Should be smarter about detecting X use

[Launchpad Bug Tracker]

[Expired for click-apparmor (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  Should be smarter about detecting X use

Status in “click-apparmor” package in Ubuntu:
  Expired

Bug description:
  click-apparmor has the following code:

  # Perhaps there is a better way to detect this, but for now, this works
  if [ -d "/tmp/.X11-unix" ]; then
  num_sockets=`ls -1 /tmp/.X11-unix | wc -l`
  if [ "$num_sockets" != "0" ] && [ "$use_insecure_x" != "yes" ]; then
  echo "Detected click app running under X! Aborting"
  exit 1
  fi
  fi

  But ofono-phonesim runs itself under xvfb.  Which puts a socket like
  :99 in /tmp/.X11-unix.  So you can't have both ofono-phonesim
  installed and use click apps.

  We could maybe detect X by checking $XAUTHORITY instead.  Or we could
  look for Mir instead by seeing if $MIR_SOCKET is non-empty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1326814/+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 1322879] Re: Wake from Suspend

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Wake from Suspend

Status in “xorg” package in Ubuntu:
  Expired

Bug description:
  After going into suspend, the machine doesn't respond. It 'wakes,' but
  doesn't turn on the display (not even the back light). Nothing I do
  brings the display back on, i.e. ctrl-alt-F1, ctrl-alt-del, ctrl-alt-
  bksp, etc.

  I just put xorg as the problem seems to be with the display not
  turning back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.1
  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: Sat May 24 09:45:26 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1252]
 Subsystem: ASUSTeK Computer Inc. Device [1043:1252]
  InstallationDate: Installed on 2014-04-24 (29 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: BUYMPC TransPort 1300e
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash pcie_aspm=force vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Z62FP
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 2.1
  dmi.chassis.asset.tag: Reserved
  dmi.chassis.type: 10
  dmi.chassis.vendor: BUYMPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr205:bd03/29/2007:svnBUYMPC:pnTransPort1300e:pvr1.0:rvnASUSTeKComputerInc.:rnZ62FP:rvr2.1:cvnBUYMPC:ct10:cvr:
  dmi.product.name: TransPort 1300e
  dmi.product.version: 1.0
  dmi.sys.vendor: BUYMPC
  version.compiz: compiz 1:0.9.11+14.04.20140423-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.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.1
  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
  xserver.bootTime: Sat May 24 09:35:24 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9028 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1322879/+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 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

[tagMacher]

On the Compaq V2414 laptop, the internal speakers have never worked;
sound is normal through headphones connected to jack.

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

Title:
  [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  I can get perfect sound through headphones, and the kernel recognizes
  the internal speaker, but nothing is ever played through it. I have
  personally tested a pair of earbuds to make sure that sound could play
  through the headphone port, and that isn't a problem. The sound driver
  just refuses to recognize the existence of the speaker, even though
  the kernel does.

  I wouldn't be surprised if the last upstream update had something to
  do with it.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu May 15 18:07:52 2014
  InstallationDate: Installed on 2014-01-29 (106 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isiah  7361 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago)
  dmi.bios.date: 03/23/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0M7CYJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 1470
  dmi.product.version: A05123
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+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 1354640] [NEW] rhythmbox not playing songs

[rajat]

Public bug reported:

i

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
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.3
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
Date: Sat Aug  9 09:08:19 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780MC [Mobility Radeon HD 3100] 
[1002:9613] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:ff6a]
InstallationDate: Installed on 2014-06-14 (55 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: TOSHIBA Satellite L300D
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=da71de44-8b8c-4dd9-a20a-1666aea4fba4 ro splash quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/01/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd09/01/2009:svnTOSHIBA:pnSatelliteL300D:pvrPSLC8C-1234567:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.name: Satellite L300D
dmi.product.version: PSLC8C-1234567
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
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.1
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
xserver.bootTime: Sat Aug  9 08:46:42 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


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

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

Title:
  rhythmbox not playing songs

Status in “xorg” package in Ubuntu:
  New

Bug description:
  i

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  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.3
  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
  Date: Sat Aug  9 09:08:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780MC [Mobility Radeon HD 3100] 
[1002:9613] (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:ff6a]
  InstallationDate: Installed on 2014-06-14 (55 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: TOSHIBA Satellite L300D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=da71de44-8b8c-4dd9-a20a-1666aea4fba4 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2009
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd09/01/2009:svnTOSHIBA:pnSatelliteL300D:pvrPSLC8C-1234567:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite L300D
  dmi.product.version: PSLC8C-1234567
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0

[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop

[Launchpad Bug Tracker]

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

** Changed in: gcc-4.8 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  krb5 database operations enter infinite loop

Status in The GNU Compiler Collection:
  Fix Released
Status in Network Authentication System:
  Unknown
Status in “gcc-4.8” package in Ubuntu:
  Fix Released
Status in “gcc-4.9” package in Ubuntu:
  Fix Released
Status in “krb5” package in Ubuntu:
  Fix Released
Status in “gcc-4.8” source package in Trusty:
  Confirmed
Status in “krb5” source package in Trusty:
  Triaged

Bug description:
  [Impact]

  On krb5 KDC databases with more than a few hundred principals,
  operations can enter an infinite loop in the database library.  This
  affects both read and write operations.  If operators are fortunate,
  they will encounter this bug while testing a migration.  If they are
  not so fortunate, they will encounter this bug in a production KDC
  when the number of principals crosses the threshold where this bug
  manifests, resulting in a service outage and possible database
  corruption.  Probably the only way to restore service in that
  situation is to install a patched KDC or to downgrade to an unaffected
  version.

  Both Trusty and Utopic amd64 have been verified to have this issue.

  One concrete reported example is an invocation of kdb5_util load (as
  part of a slave KDC propagation) spinning:

  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html

  Additional failure modes are likely

  A branch is linked including the upstream work around for this bug,
  along with two other patches to bugs already nominated for trusty
  applied to the krb5 in trusty.

  For utopic, the simplest fix is to rebuild krb5 with the compiler
  currently in utopic.  An alternative is to request that the Debian
  maintainers (both monitoring this bug for such a request) upload the
  upstream work around to Debian and sync that.  You could do an ubuntu-
  specific upload but it seems undesirable to introduce a change between
  Ubuntu and Debian when all the right parties are happy to avoid it.

  The upstream patch works around a compiler optimizer bug in the
  gcc-4.8 series, which incorrectly deduces that a strict aliasing
  violation has occurred and miscompiles part of the bundled libdb2
  library that the KDC database back end depends upon.  The
  miscompilation causes a data structure to contain an inappropriate
  cycle, which leads to an infinite loop when the structure is
  traversed.

  [Test Case]

  apt-get install krb5-kdc krb5-admin-server
  kdb5_util -W -r T create -s
  awk 'BEGIN{ for (i = 0; i < 1024; i++) { printf("ank -randkey a%06d\n", i) } 
}' /dev/null | kadmin.local -r T

  (Enter any password for the master key when requested.)

  On platforms with this issue, kadmin.local spins consuming 100% CPU
  after a few hundred principals have been created.  (This is "a000762"
  on two examples.)

  To clean up,

  rm /etc/krb5kdc/principal*

  or

  krb5kdc -r T destroy

  but the latter can possibly enter the same infinite loop.

  [Regression Potential]

  Negligible.

  It is theoretically possible that our upstream workaround, which
  involves using TAILQ macros instead of CIRCLEQ macros in the bundled
  libdb2 that backs the KDC database, will have some as-yet undiscovered
  bugs or compiler interactions with consequences worse than this
  current issue.  I think this is rather unlikely.

  The patched libdb2 passes both the extensive libdb2 test suite and the
  rest of the krb5 test suite.  Prior to patching, compiling krb5 with
  an affected gcc would cause the krb5 test suite to stall when it
  reached the libdb2 test suite.  (The test suite stall is how we became
  aware of the gcc optimizer bug.)

  The BSD TAILQ macros are generally considered to be safer than the
  CIRCLEQ macros, and the various open-source BSD derivatives have made
  the corresponding change to their libdb sources years ago, with no
  reported ill effects that I can see.

  Original report from Ben Kaduk:

  ==

  In some conditions, propagating a kerberos database to a slave KDC server can 
stall.
  This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros, 
apparently due to overzealous strict aliasing deductions.

  One case of this stall is reported at
  http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and
  the rest of the thread), and there is an entry in the upstream
  bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 .

  gcc 4.9 (as used in Debian unstable at present) is not believed to
  induce this problem.  Upstream has patched their code to use the TAILQ
  family of macros instead, as a workaround, but that workaround has not
  yet appeared in an upstream release:
  https

[Touch-packages] [Bug 1283551] Re: gjs-console crashed with signal 5

[Cristian Aravena Romero]

Hello, I'm working with utopic.

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

Title:
  gjs-console crashed with signal 5

Status in GNOME Spidermonkey Javascript binding:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in “gjs” package in Ubuntu:
  Fix Released
Status in “gobject-introspection” package in Ubuntu:
  Fix Released
Status in “gjs” source package in Trusty:
  Fix Committed
Status in “gobject-introspection” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  This is #1 crasher for gjs on errors.u.c, with thousands of hits per week.

  https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs-
  
console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas

  [Testcase]
  There is no specific testcase, this crash can be triggered by any function 
that frees its instance arguments.

  [Regression Potential]
  This adds a new attribute to g-i, for it to be effective however it requires 
typelibs to be rebuilt. See Comment #25 below

  === Original Bug Report ===

  Connect Bluethooth

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: gjs 1.39.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 22 17:44:13 2014
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2014-01-23 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 
5SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1283551/+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 1342127] Re: Video does not capture sound

[Launchpad Bug Tracker]

This bug was fixed in the package qtubuntu-camera -
0.3.3+14.10.20140807.1-0ubuntu1

---
qtubuntu-camera (0.3.3+14.10.20140807.1-0ubuntu1) utopic; urgency=low

  [ Jim Hodapp ]
  * Created a new AudioCapture class that is responsible for opening the
microphone channel from Pulseaudio and feeds the data to the Android
side of camera recording via a named pipe (LP: #1342127)

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Jim Hodapp ]
  * Created a new AudioCapture class that is responsible for opening the
microphone channel from Pulseaudio and feeds the data to the Android
side of camera recording via a named pipe (LP: #1342127)
 -- Ubuntu daily releaseThu, 07 Aug 2014 
21:29:32 +

** Changed in: qtubuntu-camera (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Video does not capture sound

Status in Camera App:
  Fix Committed
Status in “qtubuntu-camera” package in Ubuntu:
  Fix Released

Bug description:
  Mako Utopic #131

  Sound is not captured while recording a video

  Test Case:
  1. Start camera-app
  2. Switch to video mode
  3. Tap 'record'
  4. Record a video and make sure there is sound while you're recording
  5. Stop recording
  6. Play the video

  Actual Result
  The video has no sound

  Expected Result
  Video has sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1342127/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1

[Mathew Hodson]

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

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

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04,
  14.04.1

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1313129] Re: Duplicate results in Home Scope under Files & Folders

[Launchpad Bug Tracker]

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

** Changed in: unity-scope-home (Ubuntu)
   Status: New => Confirmed

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

Title:
  Duplicate results in Home Scope under Files & Folders

Status in “unity-scope-home” package in Ubuntu:
  Confirmed

Bug description:
  Some files appear twice in the Home Scope under Files & Folders. When
  I go the the Files & Folders Scope, these files appear under "Recently
  used" and under "Downloads". It is logical that in the Files & Folders
  Scope the same file appears under "Recently used" as well as under
  "Downloads", but in the Home Scope the same file should appear only
  once.

  For the attached screenshots, I first cleared all my usage data (via
  Security & Privacy - Files & Applications - Clear usage data), then
  opened 6 documents from the Downloads folder.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-home/+bug/1313129/+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 1317116] Re: libgtk2.0-dev is not multiarch-ready

[Stephen Maclagan]

I've fixed my problem, i've added trusty-updates to the sources.list in /etc/apt
the image i used didn't have it as standard.

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

Title:
  libgtk2.0-dev is not multiarch-ready

Status in “gtk+2.0” package in Ubuntu:
  Confirmed
Status in “gtk+2.0” package in Debian:
  New

Bug description:
  This means that if I want to compile a Gtk+ program for x86 on an
  amd64 machine, I need to install libgtk2.0-0:i386 and then manually
  symlink: libgtk-x11-2.0.so libgdk-x11-2.0.so libatk-1.0.so
  libgio-2.0.so libpangoft2-1.0.so libpangocairo-1.0.so libcairo.so
  libpango-1.0.so libgobject-2.0.so libglib-2.0.so in /usr/lib/i386
  -linux-gnu

  $ sudo apt-get install libgtk2.0-dev:i386
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgtk2.0-dev:i386 : Depends: gir1.2-gtk-2.0:i386 (= 2.24.23-0ubuntu1) but 
it is not going to be installed
Depends: libgdk-pixbuf2.0-dev:i386 (>= 2.21.0) but it 
is not going to be installed
Depends: libpango1.0-dev:i386 (>= 1.20) but it is not 
going to be installed
Depends: libatk1.0-dev:i386 (>= 1.29.2) but it is not 
going to be installed
Recommends: python:i386 (>= 2.4) but it is not going to 
be installed
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgtk2.0-dev 2.24.23-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May  7 16:17:56 2014
  InstallationDate: Installed on 2011-05-11 (1091 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  SourcePackage: gtk+2.0
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1317116/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1

[Mathew Hodson]

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

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04,
  14.04.1

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1354058] Re: Translations.cmake doesn't pick up cc/cxx/cpp files

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
13.10.0+14.10.20140808-0ubuntu1

---
indicator-datetime (13.10.0+14.10.20140808-0ubuntu1) utopic; urgency=low

  [ Charles Kerr ]
  * Add haptic feedback support for alarms. (LP: #1350017)
  * Have the shared Translations.cmake file look for .c, .cc, .cpp,
.cxx, and .vala files. (LP: #1354058)
 -- Ubuntu daily releaseFri, 08 Aug 2014 
20:52:54 +

** Changed in: indicator-datetime (Ubuntu)
   Status: New => Fix Released

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

Title:
  Translations.cmake doesn't pick up cc/cxx/cpp files

Status in The Date and Time Indicator:
  In Progress
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  potfile-building rules in cmake/Translations.cmake checks for .vala
  and .c files, but not C++ files, so they don't get passed to xgettext.

  Frankly I don't understand how this didn't get spotted earlier, surely
  this is throwing off our translations for indicator-datetime?

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1354058/+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 1350017] Re: [clock-app] There is no vibration when an alarm goes off

[Launchpad Bug Tracker]

This bug was fixed in the package indicator-datetime -
13.10.0+14.10.20140808-0ubuntu1

---
indicator-datetime (13.10.0+14.10.20140808-0ubuntu1) utopic; urgency=low

  [ Charles Kerr ]
  * Add haptic feedback support for alarms. (LP: #1350017)
  * Have the shared Translations.cmake file look for .c, .cc, .cpp,
.cxx, and .vala files. (LP: #1354058)
 -- Ubuntu daily releaseFri, 08 Aug 2014 
20:52:54 +

** Changed in: indicator-datetime (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [clock-app] There is no vibration when an alarm goes off

Status in Clock application for Ubuntu devices:
  In Progress
Status in Ubuntu UX bugs:
  Fix Committed
Status in “indicator-datetime” package in Ubuntu:
  Fix Released

Bug description:
  It'd be probably nice to also have vibration beside the sound alert
  when an alarm triggers.

  - Design Solution --
  Giorgio Venturi updated the design spec for the clock app at [1]. The 
vibration will be enabled by default for all alarms. The user however will be 
provided a global setting to disable that if required.

  [1]
  
https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-clock-app/+bug/1350017/+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 1287361] Re: add support for keyboard shortcuts

[Thibaut Brandscheid]

CTRL + SHIFT + T: reopen previously closed tab
ALT + 1-8: show first [tab number]
ALT + 9: show last tab

Plus one suggestion, for a new, unusual shortcut:
ALT + Enter: open settings

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

Title:
  add support for keyboard shortcuts

Status in Web Browser App:
  In Progress
Status in “webbrowser-app” package in Ubuntu:
  In Progress

Bug description:
  need to add commands similar to the other apps so it works well on the
  desktop:

  - fullscreen mode and toggle (via function key)
  - esc key to toggle out of fullscreen
  - ctrl-l to display the url bar and select all text in it
  - keyboard shortcuts for navigation (back, forward) - check what 
chrome/chromium/firefox does here
  - keyboard shortcut for reload a page
  - keyboard shortcut to display history
  - others???

To manage notifications about this bug go to:
https://bugs.launchpad.net/webbrowser-app/+bug/1287361/+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 999193] Re: "VPN service failed" since 11.04

[FAUGUSTO]

Very well, I am needing to configure VPN access to a host using PPTP and
everything goes well but does not connect as attached log and
configuration made ​​and reading all ASKUBUNTU not have a direct
solution to solve the prolema. Any idea?

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

Title:
  "VPN service failed" since 11.04

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  Having this problem since 11.04.
  Seems like this is long-term bug that haven't been fixed yet.

  When try to establish VPN connection on new Ubuntu 12.04 I am still
  coming up with the message 'VPN service failed.'

  Things, that I have already tried:
  1) Tick/Untick 'Available for all'
  2) Adding refuse-eap=yes in gconf-editor
  3) Various hints that popped up from Google.

  My syslog:

  May  6 13:43:57 head NetworkManager[958]:  Starting VPN service 
'pptp'...
  May  6 13:43:57 head NetworkManager[958]:  VPN service 'pptp' started 
(org.freedesktop.NetworkManager.pptp), PID 19702
  May  6 13:43:57 head NetworkManager[958]:  VPN service 'pptp' appeared; 
activating connections
  May  6 13:43:57 head NetworkManager[958]:  VPN plugin state changed: 
init (1)
  May  6 13:43:58 head NetworkManager[958]:  VPN plugin state changed: 
starting (3)
  May  6 13:43:58 head NetworkManager[958]:  VPN connection 'NIKS' 
(Connect) reply received.
  May  6 13:43:58 head pppd[19706]: Plugin 
/usr/lib/pppd/2.4.5/nm-pptp-pppd-plugin.so loaded.
  May  6 13:43:58 head pppd[19706]: pppd 2.4.5 started by root, uid 0
  May  6 13:43:58 head pppd[19706]: Using interface ppp0
  May  6 13:43:58 head pppd[19706]: Connect: ppp0 <--> /dev/pts/1
  May  6 13:43:58 head NetworkManager[958]:SCPlugin-Ifupdown: devices added 
(path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  May  6 13:43:58 head NetworkManager[958]:SCPlugin-Ifupdown: device added 
(path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration 
found.
  May  6 13:43:58 head pptp[19710]: nm-pptp-service-19702 log[main:pptp.c:314]: 
The synchronous pptp option is NOT activated
  May  6 13:43:58 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 1 
'Start-Control-Connection-Request'
  May  6 13:43:58 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_disp:pptp_ctrl.c:739]: Received Start Control Connection Reply
  May  6 13:43:58 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_disp:pptp_ctrl.c:773]: Client connection established.
  May  6 13:43:59 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 7 
'Outgoing-Call-Request'
  May  6 13:43:59 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_disp:pptp_ctrl.c:858]: Received Outgoing Call Reply.
  May  6 13:43:59 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_disp:pptp_ctrl.c:897]: Outgoing call established (call ID 0, peer's 
call ID 1284).
  May  6 13:44:01 head kernel: [54402.832108] wlan0: no IPv6 routers present
  May  6 13:44:03 head ntpdate[19681]: no server suitable for synchronization 
found
  May  6 13:44:10 head NetworkManager[958]:  (wlan0): IP6 addrconf timed 
out or failed.
  May  6 13:44:10 head NetworkManager[958]:  Activation (wlan0) Stage 4 
of 5 (IPv6 Configure Timeout) scheduled...
  May  6 13:44:10 head NetworkManager[958]:  Activation (wlan0) Stage 4 
of 5 (IPv6 Configure Timeout) started...
  May  6 13:44:10 head NetworkManager[958]:  Activation (wlan0) Stage 4 
of 5 (IPv6 Configure Timeout) complete.
  May  6 13:44:29 head pppd[19706]: LCP: timeout sending Config-Requests
  May  6 13:44:29 head pppd[19706]: Connection terminated.
  May  6 13:44:29 head NetworkManager[958]:  VPN plugin failed: 1
  May  6 13:44:29 head NetworkManager[958]:SCPlugin-Ifupdown: devices 
removed (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
  May  6 13:44:29 head pptp[19710]: nm-pptp-service-19702 
warn[decaps_hdlc:pptp_gre.c:204]: short read (-1): Input/output error
  May  6 13:44:29 head pppd[19706]: Modem hangup
  May  6 13:44:29 head pptp[19710]: nm-pptp-service-19702 
warn[decaps_hdlc:pptp_gre.c:216]: pppd may have shutdown, see pppd log
  May  6 13:44:29 head pptp[19717]: nm-pptp-service-19702 
log[callmgr_main:pptp_callmgr.c:234]: Closing connection (unhandled)
  May  6 13:44:29 head pptp[19717]: nm-pptp-service-19702 
log[ctrlp_rep:pptp_ctrl.c:251]: Sent control packet type is 12 
'Call-Clear-Request'
  May  6 13:44:29 head pptp[19717]: nm-pptp-service-19702 
log[call_callback:pptp_callmgr.c:79]: Closing connection (call state)
  May  6 13:44:29 head NetworkManager[958]:  VPN plugin failed: 1
  May  6 13:44:29 head pppd[19706]: Exit.
  May  6 13:44:29 head NetworkManager[958]:  VPN plugin failed: 1
  May  6 13:44:29 head NetworkManager[958]:  VPN plugin state changed: 
stopped (6)
  May  6 13:44:29 head NetworkManager[958]:  VPN plugi

[Touch-packages] [Bug 1283551] Re: gjs-console crashed with signal 5

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/gobject-introspection

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

Title:
  gjs-console crashed with signal 5

Status in GNOME Spidermonkey Javascript binding:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in “gjs” package in Ubuntu:
  Fix Released
Status in “gobject-introspection” package in Ubuntu:
  Fix Released
Status in “gjs” source package in Trusty:
  Fix Committed
Status in “gobject-introspection” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  This is #1 crasher for gjs on errors.u.c, with thousands of hits per week.

  https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs-
  
console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas

  [Testcase]
  There is no specific testcase, this crash can be triggered by any function 
that frees its instance arguments.

  [Regression Potential]
  This adds a new attribute to g-i, for it to be effective however it requires 
typelibs to be rebuilt. See Comment #25 below

  === Original Bug Report ===

  Connect Bluethooth

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: gjs 1.39.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 22 17:44:13 2014
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2014-01-23 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 
5SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1283551/+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 1315144] Re: Indicator icons don't reflect modem Offline state

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/indicator-network

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

Title:
  Indicator icons don't reflect modem Offline state

Status in Network Menu:
  New
Status in “indicator-network” package in Ubuntu:
  Fix Released

Bug description:
  While testing FlightMode on mako, I noticed that whenever the modem is
  offlined, the data tech indicator briefly changes from 3G to
  disconnected, and then re-displays 3G.  The cellular signal strength
  icon never changes.  When the modem is offline, both should indicate
  that the modem is offline ( ie. no signal, and no data connection ).

  Tested on mako running image #u4.

  Note, I tested with the following packages and setup changes ( upstart
  jobs are attached to this bug ):

  Package Versions:
   - urfkill: 0.5.0+20140429.092522.b3b9563-0ubuntu1~mtrudel4 ( 
ppa:mathieu-tl/nv-build )
   - network-manager: 0.9.8.8-0ubuntu9~mtrudel1 ( ppa:mathieu-tl/nv-build )
   - ofono: 1.12.bzr6858+14.10.20140501-0ubuntu1 ( 
lp:~ci-train-ppa-service/+archive/landing-008/ )
   - telepathy-ofono: 0.2+14.04.20140407-0ubuntu1~awe1 ( ppa:awe/ppa )

  Other Setup:
   - /etc/system-image/writable-paths needs an entry for /var/lib/urfkill
   - rild.conf and ofono.override need to be manually uploaded to /etc/init

  Steps to Test:

  1. Follow setup from above and reboot after packages are installed.
  2. Use the attached script rfkill-flight-mode to query the state of 
flight-mode ( it should be off initially )
  3. Run '/usr/share/ofono/scripts/list-modems | grep Online' to check the 
state of the modem
  4. Run 'rfkill-flight-mode 1'

  Notice that the 3G icon briefly shows disconnected, but then comes
  back up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1315144/+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 1354596] [NEW] Internal Server Error accessing localhost:631/admin

[Cliff Carson]

Public bug reported:

This is one of two problems I'm seeing on the Gnome version of 14.10.
Since there is a boot problem using the normal process (the first
problem) I've boot systemd with init=/lib/systemd/systemd rather than
using normal upstart boot.  The system comes up but trying to open the
localhost:631/admin to configure cups I get an Internal Server Error.
Trying to stop or start the cupsd I get this message

cliff@cliffsyx:~$ sudo start cupsd
[sudo] password for cliff: 
start: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: cups 1.7.4-4
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-0ubuntu3
Architecture: amd64
CupsErrorLog:
 E [08/Aug/2014:09:02:00 -0400] [CGI] Unable to connect to cupsd: Bad file 
descriptor
 E [08/Aug/2014:18:12:46 -0400] [CGI] Unable to connect to cupsd: Bad file 
descriptor
CurrentDesktop: GNOME
Date: Fri Aug  8 18:17:45 2014
InstallationDate: Installed on 2014-08-04 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140803)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Si G41M-P33
Papersize: letter
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=7500159c-733b-4b4c-a78b-0e5704204f40 ro init=/lib/systemd/systemd
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V7.7
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: G41M-P33 (MS-7592)
dmi.board.vendor: MSI
dmi.board.version: 3.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 3.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV7.7:bd01/05/2010:svnSi:pnG41M-P33:pvr3.0:rvnMSI:rnG41M-P33(MS-7592):rvr3.0:cvnMSI:ct3:cvr3.0:
dmi.product.name: G41M-P33
dmi.product.version: 3.0
dmi.sys.vendor: Si

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


** Tags: amd64 apparmor apport-bug utopic

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

Title:
  Internal Server Error accessing localhost:631/admin

Status in “cups” package in Ubuntu:
  New

Bug description:
  This is one of two problems I'm seeing on the Gnome version of 14.10.
  Since there is a boot problem using the normal process (the first
  problem) I've boot systemd with init=/lib/systemd/systemd rather than
  using normal upstart boot.  The system comes up but trying to open the
  localhost:631/admin to configure cups I get an Internal Server Error.
  Trying to stop or start the cupsd I get this message

  cliff@cliffsyx:~$ sudo start cupsd
  [sudo] password for cliff: 
  start: Unable to connect to Upstart: Failed to connect to socket 
/com/ubuntu/upstart: Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.4-4
  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-0ubuntu3
  Architecture: amd64
  CupsErrorLog:
   E [08/Aug/2014:09:02:00 -0400] [CGI] Unable to connect to cupsd: Bad file 
descriptor
   E [08/Aug/2014:18:12:46 -0400] [CGI] Unable to connect to cupsd: Bad file 
descriptor
  CurrentDesktop: GNOME
  Date: Fri Aug  8 18:17:45 2014
  InstallationDate: Installed on 2014-08-04 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140803)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Si G41M-P33
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic 
root=UUID=7500159c-733b-4b4c-a78b-0e5704204f40 ro init=/lib/systemd/systemd
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V7.7
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: G41M-P33 (MS-7592)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV7.7:bd01/05/2010:svnSi:pnG41M-P33:pvr3.0:rvnMSI:rnG41M-P33(MS-7592):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.name: G41M-P33
  dmi.product.version: 3.0
  dmi.sys.vendor: Si

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1354596/+subscriptio

[Touch-packages] [Bug 1354582] Re: Keyboard shortcuts like Ctrl-C do not work in non-english keyboard layout

[Oleg]

Please, close the ticket, it was solved with the latest updated

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

Title:
  Keyboard shortcuts like Ctrl-C do not work in non-english keyboard
  layout

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When my keyboard layout is different from English (I use Russian quite 
often), keyboard shortcuts do not work in any applications. For example, Ctrl-C 
and Ctrl-V do not work. They work only in English keyboard layout.
  This has never happened in previous distros before 14.04. I doubt it very 
much that it is related to my hardware or nondefault settings, because a friend 
of mine suffered from the same problem and decided to switch to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  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: Fri Aug  8 23:37:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
  InstallationDate: Installed on 2014-05-01 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ASUSTeK COMPUTER INC. K75VM
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 232
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K75VM
  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.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K75VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 22:51:48 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 721 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354582/+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 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder

[Brian Murray]

Hello edibueno, or anyone else affected,

Accepted evolution-data-server into trusty-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/evolution-data-server/3.10.4-0ubuntu1.2 in a few hours, and then in the
-proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Changed in: evolution-data-server (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: evolution (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  Fix Committed
Status in “evolution-data-server” source package in Trusty:
  Fix Committed

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before & not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
   PC (0x7f88ad21b520) ok
   source "0x18(%r14)" (0x0468) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1293144/+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 1293144] Please test proposed package

[Brian Murray]

Hello edibueno, or anyone else affected,

Accepted evolution into trusty-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/evolution/3.10.4-0ubuntu2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  Fix Committed
Status in “evolution-data-server” source package in Trusty:
  Fix Committed

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before & not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
   PC (0x7f88ad21b520) ok
   source "0x18(%r14)" (0x0468) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1293144/+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 1354580] Re: Keyboard layout cannot be changed with keyboard shortcut when entering a password at unlock screen

[Oleg]

Please close the bug, it was solved with the latest update

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

Title:
  Keyboard layout cannot be changed with keyboard shortcut when entering
  a password at unlock screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  If my keyboard layout was different from English (Russian, for example), and 
the screen locks, then it stays in this nondefault layout and it may be changed 
to English only with mouse. That is very unconvinient.
  This behaviour appeared only in Ubuntu 14.04
  I use the default desktop manager (I believe it is Unity) and the default 
login manager (I believe it is LightDM).
  It is not related only to my computer. A friend of mine also suffered from 
this new behaviour since 14.04, and that was one of the reasons why he switched 
to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  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: Fri Aug  8 23:27:01 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
  InstallationDate: Installed on 2014-05-01 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ASUSTeK COMPUTER INC. K75VM
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 232
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K75VM
  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.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K75VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 22:51:48 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 721 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354580/+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 1349958] Re: Gallery app does not load translations

[Arthur Mello]

** Changed in: gallery-app
   Status: Triaged => In Progress

** Changed in: gallery-app (Ubuntu)
   Status: Triaged => In Progress

** Branch linked: lp:~artmello/gallery-app/gallery-app-load_translations

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

Title:
  Gallery app does not load translations

Status in Gallery App:
  In Progress
Status in Ubuntu Translations:
  Triaged
Status in “gallery-app” package in Ubuntu:
  In Progress

Bug description:
  I noticed that Gallery no longer loads translations and appears in
  English only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gallery-app/+bug/1349958/+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 1283551] Please test proposed package

[Brian Murray]

Hello Cristian, or anyone else affected,

Accepted gjs into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/gjs/1.40.1-0ubuntu0.3
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

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

Title:
  gjs-console crashed with signal 5

Status in GNOME Spidermonkey Javascript binding:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in “gjs” package in Ubuntu:
  Fix Released
Status in “gobject-introspection” package in Ubuntu:
  Fix Released
Status in “gjs” source package in Trusty:
  Fix Committed
Status in “gobject-introspection” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  This is #1 crasher for gjs on errors.u.c, with thousands of hits per week.

  https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs-
  
console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas

  [Testcase]
  There is no specific testcase, this crash can be triggered by any function 
that frees its instance arguments.

  [Regression Potential]
  This adds a new attribute to g-i, for it to be effective however it requires 
typelibs to be rebuilt. See Comment #25 below

  === Original Bug Report ===

  Connect Bluethooth

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: gjs 1.39.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 22 17:44:13 2014
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2014-01-23 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 
5SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1283551/+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 1283551] Re: gjs-console crashed with signal 5

[Brian Murray]

Hello Cristian, or anyone else affected,

Accepted gobject-introspection into trusty-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/gobject-introspection/1.40.0-1ubuntu0.2 in a few hours, and then in the
-proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

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

** Changed in: gobject-introspection (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

** Changed in: gjs (Ubuntu Trusty)
   Status: In Progress => Fix Committed

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

Title:
  gjs-console crashed with signal 5

Status in GNOME Spidermonkey Javascript binding:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in “gjs” package in Ubuntu:
  Fix Released
Status in “gobject-introspection” package in Ubuntu:
  Fix Released
Status in “gjs” source package in Trusty:
  Fix Committed
Status in “gobject-introspection” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  This is #1 crasher for gjs on errors.u.c, with thousands of hits per week.

  https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs-
  
console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas

  [Testcase]
  There is no specific testcase, this crash can be triggered by any function 
that frees its instance arguments.

  [Regression Potential]
  This adds a new attribute to g-i, for it to be effective however it requires 
typelibs to be rebuilt. See Comment #25 below

  === Original Bug Report ===

  Connect Bluethooth

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: gjs 1.39.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 22 17:44:13 2014
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2014-01-23 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 
5SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1283551/+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 1283551] Re: gjs-console crashed with signal 5

[Brian Murray]

** Description changed:

  [Impact]
  This is #1 crasher for gjs on errors.u.c, with thousands of hits per week.
+ 
+ https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs-
+ 
console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas
  
  [Testcase]
  There is no specific testcase, this crash can be triggered by any function 
that frees its instance arguments.
  
  [Regression Potential]
  This adds a new attribute to g-i, for it to be effective however it requires 
typelibs to be rebuilt. See Comment #25 below
  
  === Original Bug Report ===
  
  Connect Bluethooth
  
  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: gjs 1.39.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 22 17:44:13 2014
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2014-01-23 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
- ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-window
- Signal: 5SourcePackage: gjs
+ ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 
5SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

Title:
  gjs-console crashed with signal 5

Status in GNOME Spidermonkey Javascript binding:
  Fix Released
Status in The "G" Library - GLib:
  Fix Released
Status in Ubuntu GNOME:
  Triaged
Status in “gjs” package in Ubuntu:
  Fix Released
Status in “gobject-introspection” package in Ubuntu:
  Fix Released
Status in “gjs” source package in Trusty:
  In Progress
Status in “gobject-introspection” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  This is #1 crasher for gjs on errors.u.c, with thousands of hits per week.

  https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs-
  
console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas

  [Testcase]
  There is no specific testcase, this crash can be triggered by any function 
that frees its instance arguments.

  [Regression Potential]
  This adds a new attribute to g-i, for it to be effective however it requires 
typelibs to be rebuilt. See Comment #25 below

  === Original Bug Report ===

  Connect Bluethooth

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: gjs 1.39.90-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Feb 22 17:44:13 2014
  ExecutablePath: /usr/bin/gjs-console
  InstallationDate: Installed on 2014-01-23 (30 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122)
  ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ 
Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 
5SourcePackage: gjs
  StacktraceTop:
   ?? () from /usr/lib/libgjs.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0
  Title: gjs-console crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gjs/+bug/1283551/+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 1351097] Re: [emulator] bottom edge swipe broken

[Łukasz Zemczak]

** Tags added: lt-whitelisted

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

Title:
  [emulator] bottom edge swipe broken

Status in “android” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 166
  device name: generic_x86
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-07-31 17:40:46
  version version: 166
  version ubuntu: 20140731.1
  version device: 20140728.1

  Can't use the bottom edge swipe anymore.

  Just open the browser and try using the bottom edge part of the
  screen. Same happens with dialler and messaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1351097/+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 1354582] [NEW] Keyboard shortcuts like Ctrl-C do not work in non-english keyboard layout

[Oleg]

Public bug reported:

When my keyboard layout is different from English (I use Russian quite often), 
keyboard shortcuts do not work in any applications. For example, Ctrl-C and 
Ctrl-V do not work. They work only in English keyboard layout.
This has never happened in previous distros before 14.04. I doubt it very much 
that it is related to my hardware or nondefault settings, because a friend of 
mine suffered from the same problem and decided to switch to another distro.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
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: Fri Aug  8 23:37:19 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
InstallationDate: Installed on 2014-05-01 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: ASUSTeK COMPUTER INC. K75VM
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 232
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K75VM
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.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K75VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Aug  8 22:51:48 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 721 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  Keyboard shortcuts like Ctrl-C do not work in non-english keyboard
  layout

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When my keyboard layout is different from English (I use Russian quite 
often), keyboard shortcuts do not work in any applications. For example, Ctrl-C 
and Ctrl-V do not work. They work only in English keyboard layout.
  This has never happened in previous distros before 14.04. I doubt it very 
much that it is related to my hardware or nondefault settings, because a friend 
of mine suffered from the same problem and decided to switch to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nv

[Touch-packages] [Bug 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder

[Daniel Wainwright]

Might be doing this wrong I think. I commented against each of the
'trusty' tasks Iain Lane had uploaded patches for, wanting to mark each
"ubuntu-sru approved and reviewed". How my comments appear, it isn't
clear that that is what I did. Any advice?

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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  In Progress
Status in “evolution-data-server” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before & not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
   PC (0x7f88ad21b520) ok
   source "0x18(%r14)" (0x0468) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1293144/+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 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder

[Daniel Wainwright]

Having read https://wiki.ubuntu.com/StableReleaseUpdates and
https://wiki.ubuntu.com/StableReleaseUpdates#Reviewing_procedure_and_tools
and having followed said guidelines I have reviewed this change and it
appears to meet the requirements; hence:-

ubuntu-sru approved and reviewed

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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  In Progress
Status in “evolution-data-server” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before & not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
   PC (0x7f88ad21b520) ok
   source "0x18(%r14)" (0x0468) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1293144/+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 1354580] [NEW] Keyboard layout cannot be changed with keyboard shortcut when entering a password at unlock screen

[Oleg]

Public bug reported:

If my keyboard layout was different from English (Russian, for example), and 
the screen locks, then it stays in this nondefault layout and it may be changed 
to English only with mouse. That is very unconvinient.
This behaviour appeared only in Ubuntu 14.04
I use the default desktop manager (I believe it is Unity) and the default login 
manager (I believe it is LightDM).
It is not related only to my computer. A friend of mine also suffered from this 
new behaviour since 14.04, and that was one of the reasons why he switched to 
another distro.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
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: Fri Aug  8 23:27:01 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
InstallationDate: Installed on 2014-05-01 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: ASUSTeK COMPUTER INC. K75VM
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 232
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K75VM
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.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K75VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Aug  8 22:51:48 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 721 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  Keyboard layout cannot be changed with keyboard shortcut when entering
  a password at unlock screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  If my keyboard layout was different from English (Russian, for example), and 
the screen locks, then it stays in this nondefault layout and it may be changed 
to English only with mouse. That is very unconvinient.
  This behaviour appeared only in Ubuntu 14.04
  I use the default desktop manager (I believe it is Unity) and the default 
login manager (I believe it is LightDM).
  It is not related only to my computer. A friend of mine also suffered from 
this new behaviour since 14.04, and that was one of the reasons why he switched 
to anot

[Touch-packages] [Bug 1353041] Re: Logging out of the Unity8 desktop preview session hangs

[Michał Sawicz]

unity8-dash job only exits on unity8 stopping, the desktop session used
a different job until now, there's branches fixing this now:

lp:~bregma/unity8/merge-desktop-upstart-job
lp:~bregma/unity8-desktop-session/merge-upstart-jobs

** Branch linked: lp:~bregma/unity8/merge-desktop-upstart-job

** Branch linked: lp:~bregma/unity8-desktop-session/merge-upstart-jobs

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

** Changed in: unity8-desktop-session (Ubuntu)
   Status: New => Incomplete

** Changed in: unity8-desktop-session (Ubuntu)
   Status: Incomplete => In Progress

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

Title:
  Logging out of the Unity8 desktop preview session hangs

Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8-desktop-session” package in Ubuntu:
  In Progress

Bug description:
  When logging out of a Unity8 desktop preview session, it hangs and
  keeps displaying the Logout dialogue but nothing else happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1353041/+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 1354564] Re: Keyboard no longer works in Unity8 desktop session

[Michał Sawicz]

It's rather the other way around, can you check ~/.cache/upstart/maliit-
server.log? The socket above is only there as a side channel for OSK to
tell the shell its dimensions, so it's maliit that creates that socket,
it must be unable to start for some reason.

** Also affects: maliit-framework (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: unity8 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Keyboard no longer works in Unity8 desktop session

Status in “maliit-framework” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Incomplete
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  The keyboard no longer works in the Unity 8 desktop session.  Looking
  at the ~/.cache/upstart/unity8.log, it looks as though the socket
  Unity 8 is trying to connect to does not exist.  I see some of the
  following messages:

  UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer:
  Invalid name"

  then the last message says:

  Failed to connect to "/run/user/1001/ubuntu-keyboard-info" after 10
  failed attempts

  I looked in /run/user/1001 and did not see any file by that name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1354564/+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 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Martin Pitt (pitti)

** Tags added: utopic

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  New

Bug description:
  I was trying to investigate a failed retrace on armhf and received the
  following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1354571/+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 1293144] Re: evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when creating new folder

[Daniel Wainwright]

Having read https://wiki.ubuntu.com/StableReleaseUpdates and
https://wiki.ubuntu.com/StableReleaseUpdates#Reviewing_procedure_and_tools
and having followed said guidelines I have reviewed  this change and it
appears to meet the requirements; hence:-

ubuntu-sru approved and reviewed

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

Title:
  evolution crashes with SIGSEGV in folder_tree_maybe_expand_row() when
  creating new folder

Status in The Evolution Mail & Calendaring Tool:
  Fix Released
Status in “evolution” package in Ubuntu:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “evolution” source package in Trusty:
  In Progress
Status in “evolution-data-server” source package in Trusty:
  In Progress

Bug description:
  [ Description ]

  (from upstream bug report, might not happen for everyone)

  - Open evolution
  - Go to mail view
  - Try to create a new folder

  Check evo crashes before & not after.

  I've also cherry-picked some related patches to make the created
  folder be displayed correctly. Check it doesn't have an expander.

  [ Development fix ]

  Same patches (disconnect the signals)

  [ Regression potential ]

  Check that folders are created and displayed properly, including cases
  that previously worked.

  [ Original description ]

  When I creates a new folder in Gmail the app closes.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: evolution 3.10.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Sun Mar 16 12:21:08 2014
  ExecutablePath: /usr/bin/evolution
  InstallationDate: Installed on 2014-03-13 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  ProcCmdline: evolution
  SegvAnalysis:
   Segfault happened at: 0x7f88ad21b520:mov0x18(%r14),%rdi
   PC (0x7f88ad21b520) ok
   source "0x18(%r14)" (0x0468) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evolution
  StacktraceTop:
   ?? () from /usr/lib/evolution/3.10/libevolution-mail.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kismet lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution/+bug/1293144/+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 1354571] [NEW] apport-retrace ignores warnings from gdb

[Brian Murray]

Public bug reported:

I was trying to investigate a failed retrace on armhf and received the
following when running apport-retrace with -g.

Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
-utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' --ex 
'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
helper"' --ex 'core-file /tmp/apport_core_36z3Va'
GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word".
The target architecture is assumed to be arm
Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
done.
BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size >= 
19316736, found: 9502720.
[New LWP 15327]
[New LWP 15530]
[New LWP 15321]
Cannot access memory at address 0xb6fa7948
Cannot access memory at address 0xb6fa7944

When running apport-retrace with -o, a new crash file is created with a
broken Stacktrace.  This makes sense given that the core file is
corrupt.

However, I think apport-retrace should do something different here, as
you have no idea why the retraced report is bad. Maybe it should write a
RetraceFailure key to the report, not write the report at all, or just
exit with an error regarding the core file size difference.

** Affects: apport (Ubuntu)
 Importance: Undecided
 Assignee: Martin Pitt (pitti)
 Status: New


** Tags: utopic

** Description changed:

  I was trying to investigate a failed retrace on armhf and received the
  following when running apport-retrace with -g.
  
  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944
  
  When running apport-retrace with -o, a new crash file is created with a
  broken Stacktrace.  This makes sense given that the core file is
- corrupt.  I think apport-retrace should do something different here,
- maybe write a RetraceFailure key to the report, not write the report at
- all, or just exit with an error regarding the core file size difference.
+ corrupt.
+ 
+ However, I think apport-retrace should do something different here, as
+ you have no idea why the retraced report is bad. Maybe it should write a
+ RetraceFailure key to the report, not write the report at all, or just
+ exit with an error regarding the core file size difference.

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  New

Bug description:
  I was trying to invest

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

Here is the log file from the Error Tracker retracer trying to retrace
the crash:

e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:21:45,422:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Processing.
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:21:45,447:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:swift
 token: de4d505d664547f086a4ee328ba87631
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:21:45,575:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Decompressing
 to /tmp/tmpxKHbHR-swift.f158f61e-1eec-11e4-9491-fa163e75317b.oopsid.core
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:21:45,887:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Retracing
 f158f61e-1eec-11e4-9491-fa163e75317b:swift
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:02,312:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Writing
 back to Cassandra
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:02,344:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Apport
 did not return a crash_signature.
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:02,345:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:StacktraceTop:
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:02,345:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:??
 ()
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:02,345:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:??
 ()
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:02,346:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Could
 not retrace.
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:03,108:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:Done
 processing /tmp/tmpxKHbHR-swift.f158f61e-1eec-11e4-9491-fa163e75317b.oopsid
e-t-retracer-app-5bb3de66-d6c1-412d-b8fc-fc855569978d/production-logs/retracer-armhf.log:2014-08-08
 
11:22:03,108:2852:140155919730432:INFO:root:f158f61e-1eec-11e4-9491-fa163e75317b:swift:swift
 token: de4d505d664547f086a4ee328ba87631

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  New

Bug description:
  I was trying to investigate a failed retrace on armhf and received the
  following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I th

[Touch-packages] [Bug 1354571] Re: apport-retrace ignores warnings from gdb

[Brian Murray]

This problem exists in apport/report.py:

part_re = re.compile('^\$\d+\s*=\s*-99$', re.MULTILINE)
parts = part_re.split(out)
# drop the gdb startup text prior to first separator
parts.pop(0)
for part in parts:
self[value_keys.pop(0)] = part.replace('\n\n', '\n.\n').strip()

Using the relevant core file we see the warning in parts[0].

ipdb> parts[0]
u'The target architecture is assumed to be arm\nBFD: Warning: 
/tmp/apport_core_U3847R is truncated: expected core file size >= 19316736, 
found: 9502720.\n[New LWP 15327]\n[New LWP 15530]\n[New LWP 15321]\nCannot 
access memory at address 0xb6fa7948\nCannot access memory at address 
0xb6fa7944\n'

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

Title:
  apport-retrace ignores warnings from gdb

Status in “apport” package in Ubuntu:
  New

Bug description:
  I was trying to investigate a failed retrace on armhf and received the
  following when running apport-retrace with -g.

  Calling gdb command: gdb-multiarch --ex 'set architecture arm' --ex 'set 
gnutarget elf32-littlearm' --ex 'set debug-file-directory /tmp/apport
  -utopic/usr/lib/debug' --ex 'set solib-absolute-prefix /tmp/apport-utopic' 
--ex 'file "/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-
  helper"' --ex 'core-file /tmp/apport_core_36z3Va'
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word".
  The target architecture is assumed to be arm
  Reading symbols from 
/tmp/apport-utopic//usr/lib/ubuntu-push-client/signing-helper...Reading symbols 
from /tmp/apport-utopic/usr/lib/debug/.bu
  ild-id/0d/28e75c6b9149132f8940077618a904989a75ed.debug...done.
  done.
  BFD: Warning: /tmp/apport_core_36z3Va is truncated: expected core file size 
>= 19316736, found: 9502720.
  [New LWP 15327]
  [New LWP 15530]
  [New LWP 15321]
  Cannot access memory at address 0xb6fa7948
  Cannot access memory at address 0xb6fa7944

  When running apport-retrace with -o, a new crash file is created with
  a broken Stacktrace.  This makes sense given that the core file is
  corrupt.

  However, I think apport-retrace should do something different here, as
  you have no idea why the retraced report is bad. Maybe it should write
  a RetraceFailure key to the report, not write the report at all, or
  just exit with an error regarding the core file size difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1354571/+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 1323418] Re: network-manager loses connection randomly

[Earendil02]

It happens to me too, randomly it disconnects and it isn't able to reconnect 
until I run this custom script:
sudo rmmod iwldvm ; sleep 3 ; sudo modprobe iwldvm
Then it automatically reconnects.
I have a dell XPS13 native ubuntu, running Ubuntu 14.04 LTS

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

Title:
  network-manager loses connection randomly

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  It started a few weeks ago when network-manager started to lose connection 
randomly. Before these few weeks it sometimes happened after wake-up from 
suspend, but now I don't even have to suspend to experience this issue. It just 
suddenly seem to lose the signal of my home wi-fi network and I can only 
reconnect it after restarting network manager. I'm almost sure about not having 
problem with the router because after losing signal I can still see my 
printer's hotspot, and if I connect it after a few minutes that connection 
breaks too.
  In the first weeks of my fresh ubuntu 14.04 install this issue didn't happen 
(only a few times after wakeup as I've mentioned, but).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 26 22:49:56 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-20 (36 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.1.100 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   CC:8C:E3:37:E8:6C bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1323418/+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 1351097] Re: [emulator] bottom edge swipe broken

[Robert Carr]

Applying http://pastebin.ubuntu.com/7991531/ as a patch against the
android device tree fixes things for me. It looks like the emulator
never supported resizing EGLWindowSurfaces. The WindowSurfaceon the host
side will still be the wrong size...the effects of this are hard to
predict. With 5-10 minute sof playing around with the emulator image
things seem to work fine...probably because we only resize
bigger->smaller atm...things could get broken as we support more.

Now that I am familiar with the codebase and have a workflow for
iterating on the device tree I think I will be able to provide a proper
fix earyl next week, not sure if people want to take this one in the
mean time.

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

Title:
  [emulator] bottom edge swipe broken

Status in “android” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  root@ubuntu-phablet:~# system-image-cli -i
  current build number: 166
  device name: generic_x86
  channel: ubuntu-touch/utopic-proposed
  last update: 2014-07-31 17:40:46
  version version: 166
  version ubuntu: 20140731.1
  version device: 20140728.1

  Can't use the bottom edge swipe anymore.

  Just open the browser and try using the bottom edge part of the
  screen. Same happens with dialler and messaging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android/+bug/1351097/+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 1354565] Re: Display problem

[Hitesh Rohilla]

sorry for messaging again and again but i notices another thing that
icons are there but not appearing. when i tried to click by guessing on
my screen where home folder icon could be present; it let open a
blackout window which means icons are there but not appearing.

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

Title:
  Display problem

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I installed QT-Creator via synaptic package installer it also
  installed two dependencies via unauthenticated source. Everything was
  going fine but after i reboot it start creating display problems icons
  from desktop are not appearing many software when i run are running
  either invisibly or turned application area black on screen. I am able
  to drag moving these applications normally by picking them from task
  bar via mouse and click dragging also able to close them but not able
  to see what's on application its total black area.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug  9 01:01:02 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0558]
  InstallationDate: Installed on 2014-07-31 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
  MachineType: Dell Inc. Vostro 2520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=2b48de70-6842-4e1d-a866-aa1c0b1d1cc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0WCP0C
  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:bd02/24/2014:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0WCP0C:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 2520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
  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.1
  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
  xserver.bootTime: Sat Aug  9 00:48:46 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 827 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354565/+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 1323418] Re: network-manager loses connection randomly

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => 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/1323418

Title:
  network-manager loses connection randomly

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  It started a few weeks ago when network-manager started to lose connection 
randomly. Before these few weeks it sometimes happened after wake-up from 
suspend, but now I don't even have to suspend to experience this issue. It just 
suddenly seem to lose the signal of my home wi-fi network and I can only 
reconnect it after restarting network manager. I'm almost sure about not having 
problem with the router because after losing signal I can still see my 
printer's hotspot, and if I connect it after a few minutes that connection 
breaks too.
  In the first weeks of my fresh ubuntu 14.04 install this issue didn't happen 
(only a few times after wakeup as I've mentioned, but).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 26 22:49:56 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-20 (36 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IpRoute:
   default via 192.168.1.100 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.105  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   CC:8C:E3:37:E8:6C bluetooth disconnected  
/org/freedesktop/NetworkManager/Devices/2  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

[Hitesh Rohilla]

I noticed that the blackout area application is only the file explorer
and everything else is working fine except desktop icons which are not
there any more on gnome desktop.

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

Title:
  Display problem

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I installed QT-Creator via synaptic package installer it also
  installed two dependencies via unauthenticated source. Everything was
  going fine but after i reboot it start creating display problems icons
  from desktop are not appearing many software when i run are running
  either invisibly or turned application area black on screen. I am able
  to drag moving these applications normally by picking them from task
  bar via mouse and click dragging also able to close them but not able
  to see what's on application its total black area.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug  9 01:01:02 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0558]
  InstallationDate: Installed on 2014-07-31 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
  MachineType: Dell Inc. Vostro 2520
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=2b48de70-6842-4e1d-a866-aa1c0b1d1cc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0WCP0C
  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:bd02/24/2014:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0WCP0C:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Vostro 2520
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
  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.1
  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
  xserver.bootTime: Sat Aug  9 00:48:46 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 827 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354565/+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 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1

[Mathew Hodson]

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

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

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04,
  14.04.1

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in MonoDevelop:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters->keyboard->hotkeys->windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+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 1354565] [NEW] Display problem

[Hitesh Rohilla]

Public bug reported:

I installed QT-Creator via synaptic package installer it also installed
two dependencies via unauthenticated source. Everything was going fine
but after i reboot it start creating display problems icons from desktop
are not appearing many software when i run are running either invisibly
or turned application area black on screen. I am able to drag moving
these applications normally by picking them from task bar via mouse and
click dragging also able to close them but not able to see what's on
application its total black area.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Aug  9 01:01:02 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, i686: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0558]
InstallationDate: Installed on 2014-07-31 (8 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release i386 
(20140416.2)
MachineType: Dell Inc. Vostro 2520
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=2b48de70-6842-4e1d-a866-aa1c0b1d1cc2 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0WCP0C
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:bd02/24/2014:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0WCP0C:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Vostro 2520
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1
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.1
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
xserver.bootTime: Sat Aug  9 00:48:46 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 827 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  Display problem

Status in “xorg” package in Ubuntu:
  New

Bug description:
  I installed QT-Creator via synaptic package installer it also
  installed two dependencies via unauthenticated source. Everything was
  going fine but after i reboot it start creating display problems icons
  from desktop are not appearing many software when i run are running
  either invisibly or turned application area black on screen. I am able
  to drag moving these applications normally by picking them from task
  bar via mouse and click dragging also able to close them but not able
  to see what's on application its total black area.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug  9 01:01:02 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, i686: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0558]
  InstallationDate: Installed on 2014-07-31 (8 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LT

[Touch-packages] [Bug 1353832] Re: arm CPUs get "FATAL: cannot locate cpu MHz in /proc/cpuinfo"

[Launchpad Bug Tracker]

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

** Changed in: jackd2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  arm CPUs get "FATAL: cannot locate cpu MHz in /proc/cpuinfo"

Status in “jackd2” package in Ubuntu:
  Confirmed

Bug description:
  Trying to run the Supercollider http://supercollider.github.io/ sound
  synthesis program on an ARM-based NVIDIA Jetson TK1, I received this
  error.  I also received this when I tried jack_simple_client

  FATAL: cannot locate cpu MHz in /proc/cpuinfo

  This is from the Jack Library.  
  $ apt-cache policy libjack-jackd2-0:armhf
  libjack-jackd2-0:
Installed: 1.9.9.5+20130622git7de15e7a-1ubuntu1
Candidate: 1.9.9.5+20130622git7de15e7a-1ubuntu1
Version table:
   *** 1.9.9.5+20130622git7de15e7a-1ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ trusty/main armhf Packages
  100 /var/lib/dpkg/status
  (updated in 2013)

  The issue is fixed in the latest source by this checkin: (from March, 2014)
  
https://github.com/jackaudio/jack2/commit/d425d8035b761b4a362c538c41eca874ff4995f0

  I have found this latest source works for me if I compile and install
  jack by hand.  So, I think updating the libjack-jackd2-0:armhf library
  would be desirable.  Until then, all ARM-based systems can't use jack.

  Also see
  https://bugs.launchpad.net/ubuntu/+source/audacity/+bug/1347914 for a
  similar report for the program Audacity.

  Additional details

  $ lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  $ uname -a
  Linux muggy 3.10.24-gf455cd4-dirty #3 SMP PREEMPT Tue Jul 22 12:20:38 PDT 
2014 armv7l armv7l armv7l GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1353832/+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 1354564] [NEW] Keyboard no longer works in Unity8 desktop session

[Christopher Townsend]

Public bug reported:

The keyboard no longer works in the Unity 8 desktop session.  Looking at
the ~/.cache/upstart/unity8.log, it looks as though the socket Unity 8
is trying to connect to does not exist.  I see some of the following
messages:

UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer:
Invalid name"

then the last message says:

Failed to connect to "/run/user/1001/ubuntu-keyboard-info" after 10
failed attempts

I looked in /run/user/1001 and did not see any file by that name.

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

** Affects: unity8-desktop-session (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: unity8-desktop-session (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Keyboard no longer works in Unity8 desktop session

Status in “unity8” package in Ubuntu:
  New
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  The keyboard no longer works in the Unity 8 desktop session.  Looking
  at the ~/.cache/upstart/unity8.log, it looks as though the socket
  Unity 8 is trying to connect to does not exist.  I see some of the
  following messages:

  UbuntuKeyboardInfo - socket error: "QLocalSocket::connectToServer:
  Invalid name"

  then the last message says:

  Failed to connect to "/run/user/1001/ubuntu-keyboard-info" after 10
  failed attempts

  I looked in /run/user/1001 and did not see any file by that name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1354564/+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 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

[Seth Forshee]

Okay - bug #1354560.

Just one note though - bug #1333135 talks specifically about landscape
orientation, but I was using the phone in portrait orientation.

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1202806/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: "actiongroup.txt"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173013/+files/actiongroup.txt

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the "connected" icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: "indicator-2.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173010/+files/indicator-2.png

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the "connected" icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: "nmcli_d_wifi_list.txt"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173015/+files/nmcli_d_wifi_list.txt

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the "connected" icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: "indicator-3.png"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173011/+files/indicator-3.png

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the "connected" icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] Re: Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

** Attachment added: "menumodel.txt"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+attachment/4173014/+files/menumodel.txt

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the "connected" icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 1354560] [NEW] Indicator doesn't show connected status when associated with hidden network

[Seth Forshee]

Public bug reported:

After connecting to a hidden wifi network the indicator does not
correctly show the connection status. Instead of the "connected" icon in
the top bar there's just a blank space, the hidden network shows up in
the indicator's network list twice, and there's no check mark next to
either of the entries in the network list. The phone is associated with
the wireless network however and has a functioning network connection.

I'm attaching screenshots of the indicator when this is happening as
well as other data requested in bug #1202806.

** Affects: indicator-network (Ubuntu)
 Importance: Undecided
 Assignee: Antti Kaijanmäki (kaijanmaki)
 Status: New

** Attachment added: "indicator-1.png"
   
https://bugs.launchpad.net/bugs/1354560/+attachment/4173009/+files/indicator-1.png

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

Title:
  Indicator doesn't show connected status when associated with hidden
  network

Status in “indicator-network” package in Ubuntu:
  New

Bug description:
  After connecting to a hidden wifi network the indicator does not
  correctly show the connection status. Instead of the "connected" icon
  in the top bar there's just a blank space, the hidden network shows up
  in the indicator's network list twice, and there's no check mark next
  to either of the entries in the network list. The phone is associated
  with the wireless network however and has a functioning network
  connection.

  I'm attaching screenshots of the indicator when this is happening as
  well as other data requested in bug #1202806.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+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 618587] Re: eclipse does not work with appmenu

[Mathew Hodson]

** Project changed: audacity => unity-gtk-module

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

Title:
  eclipse does not work with appmenu

Status in Application menu module for GTK+:
  Invalid
Status in Eclipse:
  Unknown
Status in The Application Menu:
  Invalid
Status in DBus Menu:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in Unity GTK+ module:
  Invalid
Status in “libdbusmenu” package in Ubuntu:
  Fix Released
Status in “libdbusmenu” source package in Natty:
  Won't Fix

Bug description:
  Binary package hint: indicator-appmenu

  eclipse do not work

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: indicator-appmenu 0.0.9-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
  Uname: Linux 2.6.35-15-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Mon Aug 16 13:06:20 2010
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-appmenu

To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-gtk/+bug/618587/+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 1029289] Re: Need to authorize my google account each time I boot the computer

[BlackDalek]

This bug is reproducible on mine as wel by either rebooting or by
turning my google account off then on again.

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

Title:
  Need to authorize my google account each time I boot the computer

Status in Online Accounts: Account plugins:
  In Progress
Status in Online Accounts: OAuth2 plug-in:
  Unknown
Status in Online Accounts: Sign-on UI:
  Fix Released
Status in “account-plugins” package in Ubuntu:
  Fix Released
Status in “signon-plugin-oauth2” package in Ubuntu:
  Fix Released
Status in “account-plugins” source package in Quantal:
  Fix Released
Status in “signon-plugin-oauth2” source package in Quantal:
  Fix Released

Bug description:
  [Test Case] Sometimes after one day, sometimes after one week, the
  system indicator will turn red and the Google account will be marked
  as needing reauthentication. Time can vary, but any period shorter
  than one month is a symptom of the bug.

  [Regression Potential] Minimal: the change to the Google plugin (in
  account-plugins) simply changes the authentication method, in a way
  that is well-documented. The change in signon-plugin-oauth2 affects
  only those accounts/providers which use the OAuth refresh tokens --
  which is only Google, at the moment -- and in a way that can't
  possibly break any existing functionality; if the new code had some
  mistake, the refresh token would be unusable and the system would
  automatically fall back to requesting a new access token (which is
  exactly what happens now, with this bug).

  I'll try to find why the account-plugins package was not uploaded;
  indeed, both are required in order to fix this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1353041] Re: Logging out of the Unity8 desktop preview session hangs

[Christopher Townsend]

Here is the relevant snippet from ~/.cache/upstart/unity8.conf:

qtmir.applications: ApplicationManager::stopApplication - appId= "unity8-dash"
qtmir.applications: ApplicationManager::remove - appId= "unity8-dash"
qtmir.applications: ApplicationManager::focusApplication - appId= "unity8-dash"
No such running application with appId= "unity8-dash"
qtmir.applications: TaskController::stop - appId= "unity8-dash"
ApplicationController::stopApplication FAILED to stop appId= "unity8-dash"
qtmir.applications: TaskController::stopApplication - FAILED to stop appId= 
"unity8-dash"
FAILED to ask Upstart to stop application with appId "unity8-dash" Sending 
SIGTERM to process: 3264
qtmir.applications: Application::~Application
qtmir.applications: Application::removeSurface  "Unity Dash"  from  "Unity 8 
Dash"
qtmir.applications: Application::setSurface - appId= "unity8-dash" surface= 
QQuickItem(0)
qtmir.applications: Application::setFullscreen - appId= "unity8-dash" 
fullscreen= false
qtmir.surfaces: MirSurfaceItem::~MirSurfaceItem - this= qtmir::MirSurfaceItem 
(this = 0x3106b20 , name= "" , parent = 0x2a51df0 , geometry = QRectF(0,24 
1280x776) , z = 1 )
qtmir.applications: DesktopFileReader::~DesktopFileReader
QtCompositor::setAllWindowsExposed false
qtmir.applications: ApplicationManager::~ApplicationManager
qtmir.surfaces: MirSurfaceManager::~MirSurfaceManager - this= 
qtmir::MirSurfaceManager(0x1f01e70, name = "qtmir::SurfaceManager")

If I try killing unity8-dash manually, it respawns immediately.  I'm
wondering if something is a little out of sync in the upstart scripts...

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

Title:
  Logging out of the Unity8 desktop preview session hangs

Status in “unity8” package in Ubuntu:
  New
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  When logging out of a Unity8 desktop preview session, it hangs and
  keeps displaying the Logout dialogue but nothing else happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1353041/+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 1350449] Re: Add opt-in ability to factory reset phone after some failed logins

[Pat McGowan]

I assume this is added here to provide an opt in toggle under security
and privacy, do we have language for that toggle?

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Add opt-in ability to factory reset phone after some failed logins

Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  Per design:
  
https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#heading=h.6zhf6wqejmh6
  (search for "passcode incorrect")

  They want us to factory-reset the phone after 10 failed attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1350449/+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 1318812] Re: [osk] no way to remove user added dictionary words

[Pat McGowan]

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  [osk] no way to remove user added dictionary words

Status in Ubuntu Keyboard:
  Confirmed
Status in Ubuntu UX bugs:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  Confirmed
Status in “ubuntu-system-settings” package in Ubuntu:
  Confirmed

Bug description:
  when spell checking is enabled, any word the user types that is not 
recognized gets added to the user dictionary (I think).
  The problem is once a word gets added there is no way to delete it and it 
always shows up on the word ribbon, whether you want it or not.

  We should be more selective when adding words (i.e. if you type
  asdafadfadsfadsfadsfadsf that gets added). We can address that in
  another bug. For this bug, I think we need to provide the user with a
  way to remove words they added to the dictionary.

  One idea: press and hold the word on the word ribbon would produce an
  "x" button which when pressed would remove the word from the
  dictionary. This would be consistent with how users close apps, delete
  bookmarks, etc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1318812/+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 1268848] Re: Unity in 13.10 unstable with Radeon 7950

[madbiologist]

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

** Package changed: unity (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Fix Released

** Changed in: unity
   Status: Incomplete => Invalid

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

Title:
  Unity in 13.10 unstable with Radeon 7950

Status in Unity:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  About a month ago I installed a fresh Ubuntu 13.10 64bit on a i5
  machine, 8GB RAM, with Radeon 7950 graphic card. Before this, I was
  running 12.04 64bit without any graphic driver related problems.

  I tried both Catalyst versions from official repository, latest 13.12
  drivers from AMD site and open source drivers (radeon), and I can't
  tell which one was more unstable. After a few hours of use, I could
  not play any videos with any of the drivers (tried mplayer and VLC,
  both crashed with various errors), OpenGL isn't working anymore (even
  glxgears was crashing) and I had various artifacts on screen (like
  parts of window rendered on the wrong place on screen). Putting
  machine to sleep and waking it up later produced even more errors. I
  also tried to turn off various things in CCSM, without any positive
  results. Steam client had terrible flickering almost all the time, it
  was practically unusable; also about 8 of 10 times it was crashing on
  startup.

  After about two weeks of trying to make it usable, I gave up and
  installed MATE desktop. Not a single graphic error since then. Steam
  works flawlessly, 3D games also, Wine games, playing videos,
  everything.

  I kind of like how Unity works, I was using it for the last two years
  as my main desktop (on the same machine), but this behaviour is
  unexpected and utterly undesireable.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.2+13.10.20131014.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Jan 14 07:26:14 2014
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx, 13.251, 3.11.0-14-generic, x86_64: installed
   fglrx, 13.251, 3.11.0-15-generic, x86_64: installed
   vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed
   vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950] 
[1002:679a] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:0424]
  InstallationDate: Installed on 2013-12-06 (38 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  JockeyStatus:
   kmod:fglrx - ATI Fire GL (Proprietary, Enabled, In use)
   kmod:fglrx_updates - Video driver for the AMD graphics accelerators 
(Proprietary, Disabled, Not in use)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic 
root=UUID=eab5c9d7-0979-4fae-9ed5-a26a530694de ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/08/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: Z68 Extreme4 Gen3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ68Extreme4Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.boot

[Touch-packages] [Bug 1353041] Re: Logging out of the Unity8 desktop preview session hangs

[Christopher Townsend]

I watched dbus when I tried logging out of the Unity 8 desktop session
and to my untrained eye, it looks like unity8-dash is not getting killed
as it should which then holds up the rest of the logout.

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

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

Title:
  Logging out of the Unity8 desktop preview session hangs

Status in “unity8” package in Ubuntu:
  New
Status in “unity8-desktop-session” package in Ubuntu:
  New

Bug description:
  When logging out of a Unity8 desktop preview session, it hangs and
  keeps displaying the Logout dialogue but nothing else happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1353041/+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 1284308] getfacl.txt

[Alistair Buxton]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4173004/+files/getfacl.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device

[Alistair Buxton]

That didn't really attach anything useful, oh well. Here's the log
snippet from ~/.cache/upstart/dbus/ showing the error happening:

** (zeitgeist-fts:2146): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-S9DAKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-S9DAKX (retval 2)
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-NM4FKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-NM4FKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-9X2MKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-9X2MKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-XTK5JX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-XTK5JX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-3LWGKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-3LWGKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-GYMKKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-GYMKKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-W77BKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-W77BKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: ChangeCurrentFolderToRoot failed

** (zeitgeist-fts:2146): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-RFE9JX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-RFE9JX (retval 2)
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-284GKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-284GKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-UP0AKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-UP0AKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled

** (zeitgeist-fts:2146): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-F3C5JX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-F3C5JX (retval 2)
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-LVIFKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-LVIFKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer got cancelled

** (zeitgeist-fts:2146): WARNING **: Unable to get info on 
application://nautilus-autostart.desktop
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-OQULKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-OQULKX (retval 2)
** Message: ChangeCurrentFolderToRoot failed
** Message: ChangeCurrentFolderToRoot failed
** Message: transfer of Image010.jpg to /tmp/gvfsobexftp-tmp-VWUIKX started
** Message: filename: /Memory card/Images/Image010.jpg (Image010.jpg) copying 
to /tmp/gvfsobexftp-tmp-VWUIKX (retval 2)


The "ChangeCurrentFolderToRoot failed" appears to be harmless, for example when 
opening in eog this message is printed but the image still loads.

"transfer got cancelled" appears to be the message which is ultimately
printed when a transfer actually fails.

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferr

[Touch-packages] [Bug 1284308] UdevLog.txt

[Alistair Buxton]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4173003/+files/UdevLog.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] ProcCpuinfo.txt

[Alistair Buxton]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4172998/+files/ProcCpuinfo.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] ProcInterrupts.txt

[Alistair Buxton]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4173000/+files/ProcInterrupts.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] UdevDb.txt

[Alistair Buxton]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1284308/+attachment/4173002/+files/UdevDb.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] ProcModules.txt

[Alistair Buxton]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4173001/+files/ProcModules.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Lsusb.txt

[Alistair Buxton]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1284308/+attachment/4172997/+files/Lsusb.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Lspci.txt

[Alistair Buxton]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1284308/+attachment/4172996/+files/Lspci.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] BootDmesg.txt

[Alistair Buxton]

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4172993/+files/BootDmesg.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] CurrentDmesg.txt

[Alistair Buxton]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1284308/+attachment/4172994/+files/CurrentDmesg.txt

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Dependencies.txt

[Alistair Buxton]

apport information

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

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device

[Alistair Buxton]

ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2013-12-22 (228 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterestingModules: btusb rfcomm bnep bluetooth
MachineType: ASUS All Series
Package: obex-data-server
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=e1e7d1a7-19e8-4203-ad6a-86a144db61bc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Tags:  trusty
Uname: Linux 3.13.0-32-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-06-20 (49 days ago)
UserGroups:
 
_MarkForUpload: True
dmi.bios.date: 04/10/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0401:bd04/10/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
hciconfig:
 hci0:  Type: BR/EDR  Bus: USB
BD Address: 00:0A:3A:56:79:E3  ACL MTU: 192:8  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:7596474 acl:34665 sco:0 events:3541 errors:0
TX bytes:195498 acl:3728 sco:0 commands:44 errors:0
rfkill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
syslog:
 Aug  8 17:10:10 stuart-desktop bluetoothd[667]: Adapter /org/bluez/667/hci0 
has been disabled
 Aug  8 17:27:48 stuart-desktop bluetoothd[667]: Adapter /org/bluez/667/hci0 
has been enabled


** Tags added: apport-collected trusty

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  

[Touch-packages] [Bug 1354543] Re: mediascanner fails to watch removable devices if /media/$USER doesn't exist when starting

[Sergio Schvezov]

This log is from when /media/$USER exists:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1354543/+attachment/4172992/+files/upstart.mediascanner-2.0.log.txt

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

Title:
  mediascanner fails to watch removable devices if /media/$USER doesn't
  exist when starting

Status in “mediascanner2” package in Ubuntu:
  Confirmed

Bug description:
  If the system has never mounted a removable device then /media/$USER
  does not exist which causes mediascanner to fail it's watch with this
  error:

  Mount directory does not exist

  if something is mounted after this, then it just doesn't notice it.

  starting mediascanner after /media/$USER is created allows everything
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mediascanner2.0 0.102+14.10.20140805-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Fri Aug  8 14:39:22 2014
  InstallationDate: Installed on 2014-08-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140808-020205)
  SourcePackage: mediascanner2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1354543/+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 1351113] Re: password input box after suspend/resume was not focused but looked like it was; keyboard input was being intercepted by another window

[teo1978]

After restarting (several times) I've never observed the issue again, so
I guess it was fixed by the update mentioned above.

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

Title:
  password input box after suspend/resume was not focused but looked
  like it was; keyboard input was being intercepted by another window

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

Bug description:
  This is a HUGE SECURITY ISSUE.

  I suspended, then I resumed.

  Upon resume, I was presented the usual screen where you have to insert
  the password to unlock the screen.

  The password input box had a blinking cursor, as expected.
  I tried to type the password but it appeared to be not responding to 
keystrokes (from an external usb keyboard), meaning the usual dots would not 
appear at every keystroke.

  I thought the external usb keyboard was not working (due to another
  known bug) so I plugged it to another port, with no luck.

  So I tried to use the builtin keyboard of the laptop, but it wouldn't
  (apparently) respond to keystrokes either.

  So I clicked with the mouse on the language selection indicator in the
  upper right corner of the screen, and selected the (unique and already
  selected) language: spanish. A posteriori I think this was irrelevant.
  What I guess was relevant is that I gave focus to anything other than
  the password input box and then clicked on the password input box
  again.

  So now it worked and I could type my password and unlock the screen.

  AND HERE'S THE TERRIFYING THING: after inserting the password and
  unlocking the screen, Google Chrome was the active window (because it
  had been prior to suspending), and in the active tab there was
  facebook open. In the status-update textarea there were all the keys
  that I had been hitting when trying to input the password.

  Do you realize the enormous security hazard here? If I had typed the
  whole password quickly without looking at the screen and hit Enter
  before realizing the keystrokes were not being intercepted by the
  password input box, I could have posted my password on facebook
  without seeing it. Perhaps even twice. Fortunately, I saw the
  keystrokes were not being registered from the very beginning, and
  reacted by repeating the first few characters several times, and then
  hitting random keys, so I only typed a nonsense sequence of characters
  that doesn't even remotely resemble my password and I never got to hit
  the Enter key anyway.

  
  So, to sum up the issue:
  - after resume, the password input box wasn't focused and it should have been
  - worse: it completely looked like it was focused, with a blinking cursor 
inside, so everything looked like keyboard was not working at all
  - worst of all: keystrokes were actually being intercepted by an active 
application (which was not visible because the screen was locked). NOTHING that 
is "behind" the locked screen should be able to intercept keystrokes or mouse 
interaction, under any circumstance. If you are not seing something, that 
something must be non-existent to keyboard and mouse interaction.

  
  This is far from systematically reproducible. This is the first time I have 
observed this, ever, and have no idea what triggered this. I suspend and resume 
very often on a daily basis so this must be something pretty rare. Yet it is 
hugely dangerous.
  My very real-life case could have led to posting my password on facebook.
  Imagine if the active window was a terminal and if you happen to have a funny 
password such as "sudo rm -f /*"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Aug  1 02:40:29 2014
  InstallationDate: Installed on 2013-10-11 (293 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1351113/+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 1354543] Re: mediascanner fails to watch removable devices if /media/$USER doesn't exist when starting

[Pat McGowan]

Jussi can you take a look? this is to make SD cards work properly for
media playback

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

Title:
  mediascanner fails to watch removable devices if /media/$USER doesn't
  exist when starting

Status in “mediascanner2” package in Ubuntu:
  Confirmed

Bug description:
  If the system has never mounted a removable device then /media/$USER
  does not exist which causes mediascanner to fail it's watch with this
  error:

  Mount directory does not exist

  if something is mounted after this, then it just doesn't notice it.

  starting mediascanner after /media/$USER is created allows everything
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mediascanner2.0 0.102+14.10.20140805-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Fri Aug  8 14:39:22 2014
  InstallationDate: Installed on 2014-08-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140808-020205)
  SourcePackage: mediascanner2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1354543/+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 1354543] Re: mediascanner fails to watch removable devices if /media/$USER doesn't exist when starting

[Pat McGowan]

Jussi can you take a look? this is to make SD cards work properly for
media playback

** Changed in: mediascanner2 (Ubuntu)
   Status: New => Confirmed

** Changed in: mediascanner2 (Ubuntu)
   Importance: Undecided => Critical

** Changed in: mediascanner2 (Ubuntu)
 Assignee: (unassigned) => Jussi Pakkanen (jpakkane)

** Tags added: rtm14

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

Title:
  mediascanner fails to watch removable devices if /media/$USER doesn't
  exist when starting

Status in “mediascanner2” package in Ubuntu:
  Confirmed

Bug description:
  If the system has never mounted a removable device then /media/$USER
  does not exist which causes mediascanner to fail it's watch with this
  error:

  Mount directory does not exist

  if something is mounted after this, then it just doesn't notice it.

  starting mediascanner after /media/$USER is created allows everything
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mediascanner2.0 0.102+14.10.20140805-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Fri Aug  8 14:39:22 2014
  InstallationDate: Installed on 2014-08-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140808-020205)
  SourcePackage: mediascanner2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1354543/+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 49579] Re: screen doesn't lock when some menu is open

[Launchpad Bug Tracker]

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

** Changed in: unity (Ubuntu Precise)
   Status: New => Confirmed

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

Title:
  screen doesn't lock when some menu is open

Status in GNOME Screensaver:
  Confirmed
Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in Unity:
  Triaged
Status in Unity 7.2 series:
  Triaged
Status in X.Org X server:
  Confirmed
Status in “gnome-screensaver” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Confirmed
Status in “gnome-screensaver” source package in Precise:
  Confirmed
Status in “unity” source package in Precise:
  Confirmed
Status in “xorg-server” package in Debian:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  I'm running a fresh install of Dapper with screensaver set to 'blank
  screen', and 'lock screen when screensaver is active' enabled.

  If a panel menu (e.g. Applications) is open and the machine is left
  idle, the screen fails to lock. It fades out after the time period as
  expected, but the desktop reappears after a few seconds.

  Ben (comments / criticism welcome, this is my first bug report)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+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 1354543] [NEW] mediascanner fails to watch removable devices if /media/$USER doesn't exist when starting

[Sergio Schvezov]

Public bug reported:

If the system has never mounted a removable device then /media/$USER
does not exist which causes mediascanner to fail it's watch with this
error:

Mount directory does not exist

if something is mounted after this, then it just doesn't notice it.

starting mediascanner after /media/$USER is created allows everything to
work.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: mediascanner2.0 0.102+14.10.20140805-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.5-0ubuntu3
Architecture: armhf
Date: Fri Aug  8 14:39:22 2014
InstallationDate: Installed on 2014-08-08 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140808-020205)
SourcePackage: mediascanner2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mediascanner2 (Ubuntu)
 Importance: Critical
 Assignee: Jussi Pakkanen (jpakkane)
 Status: Confirmed


** Tags: apport-bug armhf rtm14 utopic

** Summary changed:

- mediascanner fails to what removable devices if /media/$USER doesn't exist
+ mediascanner fails to watch removable devices if /media/$USER doesn't exist 
when starting

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

Title:
  mediascanner fails to watch removable devices if /media/$USER doesn't
  exist when starting

Status in “mediascanner2” package in Ubuntu:
  Confirmed

Bug description:
  If the system has never mounted a removable device then /media/$USER
  does not exist which causes mediascanner to fail it's watch with this
  error:

  Mount directory does not exist

  if something is mounted after this, then it just doesn't notice it.

  starting mediascanner after /media/$USER is created allows everything
  to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: mediascanner2.0 0.102+14.10.20140805-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: armhf
  Date: Fri Aug  8 14:39:22 2014
  InstallationDate: Installed on 2014-08-08 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140808-020205)
  SourcePackage: mediascanner2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1354543/+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 1351180] Re: Python security issue #16039, #16041 and #16042 looks not be fixed on Python 2.7.6 (smtplib/imaplib/poplib of python has a vulnerability due to unlimited readline()

[Jamie Strandboge]

This is CVE-2013-1752 which is rated as having a 'Low' priority. It
should be fixed in a future python update.

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-1752

** Changed in: python2.7 (Ubuntu)
   Status: New => Triaged

** Changed in: python2.7 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Python security issue #16039, #16041 and #16042 looks not be fixed on
  Python 2.7.6 (smtplib/imaplib/poplib of python has a vulnerability due
  to unlimited readline() from connection)

Status in “python2.7” package in Ubuntu:
  Triaged

Bug description:
  I found that below Python security issues may not be yet fixed on
  Python 2.7.6 bundled with 14.04LTS. It looks those patches are already
  applied to Python 3.4 on 14.04LTS. It looks those patches are not
  included in upstream souce codes on both 2.7.6 and latest 2.7 version
  (2.7.8).

  http://bugs.python.org/issue16039
  http://bugs.python.org/issue16041
  http://bugs.python.org/issue16042

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1351180/+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 1351224] Re: Python security issue #14621 (Hash function is not randomized properly)

[Jamie Strandboge]

Thank you for using Ubuntu and reporting a bug. We will not be issuing a
security update for this issue. Please see http://people.canonical.com
/~ubuntu-security/cve/2013/CVE-2013-7040.html for details.

** Information type changed from Private Security to Public Security

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2013-7040

** Changed in: python2.7 (Ubuntu)
   Importance: Undecided => Low

** Changed in: python2.7 (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Python security issue #14621 (Hash function is not randomized
  properly)

Status in “python2.7” package in Ubuntu:
  Won't Fix

Bug description:
  Due to an incomplete fix for CVE-2012-1150, other CVE-2012-1150 [1] is 
reported. The following [2] is corresponding bug report in Python upstream.
  I'm not 100% sure, but this vulnerability may affect to both Python 2.7 and 
3.3 bundled with Ubuntu 14.04LTS.

  [1] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-7040
  [2] http://bugs.python.org/issue14621

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1351224/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device

[Alistair Buxton]

Subsribed additional packages to try to get some eyes on this.

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1086058] Re: my unity laucher and environment disappeared when i changed certain permission in dpkg file while installing hadoop.

[Jamie Strandboge]

Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

** Changed in: unity
   Status: New => Invalid

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

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

Title:
  my unity laucher and environment disappeared when i changed certain
  permission in dpkg file while installing hadoop.

Status in Unity:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  my settings for flashdrive is not working.
  users and groups are disabled. error: configuration cannot be loaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1086058/+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 1284308] Re: Bogus "another operation in progress" error. Can't copy files from a bluetooth device

[Alistair Buxton]

Today my workaround didn't work. This suggests the problem is in gvfsd
or obex-data-server.

** Also affects: obex-data-server (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: gvfs (Ubuntu)
   Status: New => Confirmed

** Changed in: obex-data-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bogus "another operation in progress" error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose "bluetooth settings"
  3 - select the phone among the listed devices
  4 - click on "Browse files"
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  => I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is "another
  operation in progress". Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then "ejected" the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error "This location could not be displayed. Another 
operation in progress", so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when "ejecting" 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO MTU: 183:5
    UP RUNNING PSCAN ISCAN
    RX bytes:44318 acl:198 sco:0 events:355 errors:0
    TX bytes:6132 acl:178 sco:0 commands:82 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+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 1351113] Re: password input box after suspend/resume was not focused but looked like it was; keyboard input was being intercepted by another window

[Jamie Strandboge]

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

** Changed in: unity
   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/1351113

Title:
  password input box after suspend/resume was not focused but looked
  like it was; keyboard input was being intercepted by another window

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

Bug description:
  This is a HUGE SECURITY ISSUE.

  I suspended, then I resumed.

  Upon resume, I was presented the usual screen where you have to insert
  the password to unlock the screen.

  The password input box had a blinking cursor, as expected.
  I tried to type the password but it appeared to be not responding to 
keystrokes (from an external usb keyboard), meaning the usual dots would not 
appear at every keystroke.

  I thought the external usb keyboard was not working (due to another
  known bug) so I plugged it to another port, with no luck.

  So I tried to use the builtin keyboard of the laptop, but it wouldn't
  (apparently) respond to keystrokes either.

  So I clicked with the mouse on the language selection indicator in the
  upper right corner of the screen, and selected the (unique and already
  selected) language: spanish. A posteriori I think this was irrelevant.
  What I guess was relevant is that I gave focus to anything other than
  the password input box and then clicked on the password input box
  again.

  So now it worked and I could type my password and unlock the screen.

  AND HERE'S THE TERRIFYING THING: after inserting the password and
  unlocking the screen, Google Chrome was the active window (because it
  had been prior to suspending), and in the active tab there was
  facebook open. In the status-update textarea there were all the keys
  that I had been hitting when trying to input the password.

  Do you realize the enormous security hazard here? If I had typed the
  whole password quickly without looking at the screen and hit Enter
  before realizing the keystrokes were not being intercepted by the
  password input box, I could have posted my password on facebook
  without seeing it. Perhaps even twice. Fortunately, I saw the
  keystrokes were not being registered from the very beginning, and
  reacted by repeating the first few characters several times, and then
  hitting random keys, so I only typed a nonsense sequence of characters
  that doesn't even remotely resemble my password and I never got to hit
  the Enter key anyway.

  
  So, to sum up the issue:
  - after resume, the password input box wasn't focused and it should have been
  - worse: it completely looked like it was focused, with a blinking cursor 
inside, so everything looked like keyboard was not working at all
  - worst of all: keystrokes were actually being intercepted by an active 
application (which was not visible because the screen was locked). NOTHING that 
is "behind" the locked screen should be able to intercept keystrokes or mouse 
interaction, under any circumstance. If you are not seing something, that 
something must be non-existent to keyboard and mouse interaction.

  
  This is far from systematically reproducible. This is the first time I have 
observed this, ever, and have no idea what triggered this. I suspend and resume 
very often on a daily basis so this must be something pretty rare. Yet it is 
hugely dangerous.
  My very real-life case could have led to posting my password on facebook.
  Imagine if the active window was a terminal and if you happen to have a funny 
password such as "sudo rm -f /*"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Aug  1 02:40:29 2014
  InstallationDate: Installed on 2013-10-11 (293 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-24 (68 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1351113/+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 1342127] Re: Video does not capture sound

[Jim Hodapp]

** Changed in: qtubuntu-camera (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: qtubuntu-camera (Ubuntu)
 Assignee: (unassigned) => Jim Hodapp (jhodapp)

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

Title:
  Video does not capture sound

Status in Camera App:
  Fix Committed
Status in “qtubuntu-camera” package in Ubuntu:
  Fix Committed

Bug description:
  Mako Utopic #131

  Sound is not captured while recording a video

  Test Case:
  1. Start camera-app
  2. Switch to video mode
  3. Tap 'record'
  4. Record a video and make sure there is sound while you're recording
  5. Stop recording
  6. Play the video

  Actual Result
  The video has no sound

  Expected Result
  Video has sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1342127/+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 1354540] [NEW] Missing path in init command prevents Desktop session

[Hadmut Danisch]

Public bug reported:

Hi,

/etc/X11/Xsession.d/99upstart

contains the line

STARTUP="init --user"


which can prevent the user from logging in. 

Usually, and conforming to Unix standards,  /sbin and /usr/sbin contain
system related programs to be used by root. non-root users usually do
and can not use programs found here, and therefore should not have /sbin
/usr/sbin /usr/local/sbin in their PATH variable.

But if they have a PATH variable without /sbin (which is perfectly
correct for non-root users), the STARTUP value defined above will not
work, since the should does not find init.

Therefore, and to be independent from PATH variables, this should be
/sbin/init instead of init.

regards

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Aug  8 19:31:32 2014
SourcePackage: upstart
UpgradeStatus: Upgraded to trusty on 2014-04-19 (111 days ago)
UpstartBugCategory: Session
UpstartRunningSessionCount: 2
UpstartRunningSessionVersion: init (upstart 1.12.1)
UpstartRunningSystemVersion: init (upstart 1.12.1)
upstart.logrotate.log: /proc/self/fd/9: 27: /proc/self/fd/9: logrotate: not 
found

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


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

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

Title:
  Missing path in init command prevents Desktop session

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Hi,

  /etc/X11/Xsession.d/99upstart

  contains the line

  STARTUP="init --user"

  
  which can prevent the user from logging in. 

  Usually, and conforming to Unix standards,  /sbin and /usr/sbin
  contain system related programs to be used by root. non-root users
  usually do and can not use programs found here, and therefore should
  not have /sbin /usr/sbin /usr/local/sbin in their PATH variable.

  But if they have a PATH variable without /sbin (which is perfectly
  correct for non-root users), the STARTUP value defined above will not
  work, since the should does not find init.

  Therefore, and to be independent from PATH variables, this should be
  /sbin/init instead of init.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Aug  8 19:31:32 2014
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (111 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 2
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  upstart.logrotate.log: /proc/self/fd/9: 27: /proc/self/fd/9: logrotate: not 
found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1354540/+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 1354540] Re: Missing path in init command prevents Desktop session

[Hadmut Danisch]

BTW, if that problem occurs, the session immediately aborts right after
logging in.

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

Title:
  Missing path in init command prevents Desktop session

Status in “upstart” package in Ubuntu:
  New

Bug description:
  Hi,

  /etc/X11/Xsession.d/99upstart

  contains the line

  STARTUP="init --user"

  
  which can prevent the user from logging in. 

  Usually, and conforming to Unix standards,  /sbin and /usr/sbin
  contain system related programs to be used by root. non-root users
  usually do and can not use programs found here, and therefore should
  not have /sbin /usr/sbin /usr/local/sbin in their PATH variable.

  But if they have a PATH variable without /sbin (which is perfectly
  correct for non-root users), the STARTUP value defined above will not
  work, since the should does not find init.

  Therefore, and to be independent from PATH variables, this should be
  /sbin/init instead of init.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Aug  8 19:31:32 2014
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (111 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 2
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  upstart.logrotate.log: /proc/self/fd/9: 27: /proc/self/fd/9: logrotate: not 
found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1354540/+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 1347053] Re: Clients are crashing with a fatal exception in MirSocketRpcChannel::send_message()

[Launchpad Bug Tracker]

** Branch linked: lp:mir/0.6

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

Title:
  Clients are crashing with a fatal exception in
  MirSocketRpcChannel::send_message()

Status in Mir:
  Fix Committed
Status in Mir 0.5 series:
  Won't Fix
Status in Mir 0.6 series:
  Triaged
Status in “mir” package in Ubuntu:
  Triaged
Status in “unity-system-compositor” package in Ubuntu:
  Invalid

Bug description:
  Starting unity8 when u-s-c is running results in them fighting over
  the hardware (not for the socket due to the default XDG_RUNTIME_DIR)
  and u-s-c crashing.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-system-compositor 0.0.4+14.10.20140718-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: armhf
  Date: Tue Jul 22 16:26:40 2014
  ExecutablePath: /usr/bin/unity-system-compositor-spinner
  GraphicsCard:
   
  InstallationDate: Installed on 2014-07-22 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140722-095505)
  LocalLibraries: /android/system/lib/liblog.so 
/android/system/lib/libhardware.so /android/system/lib/libstdc++.so 
/android/system/lib/libcutils.so /android/system/lib/libcorkscrew.so 
/android/system/lib/libsync.so /android/system/lib/libc.so 
/android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libm.so 
/android/system/lib/libGLESv1_CM.so /android/system/lib/libmemalloc.so 
/android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libz.so 
/android/system/lib/libgccdemangle.so /android/system/lib/libui.so 
/android/system/lib/libadreno_utils.so /android/system/lib/egl/libEGL_adreno.so 
/android/system/lib/libstlport.so /android/system/lib/egl/eglsubAndroid.so 
/android/system/lib/libutils.so /android/system/lib/libgsl.so 
/android/system/lib/libdsyscalls.so /android/system/lib/egl/libGLESv2_adreno.so 
/android/system/lib/libsc-a3xx.so /android/system/lib/libGLESv2.so 
/android/system/lib/libGLES_trace.so /android/system/lib/libEGL.so 
/android/system/lib/libqdutils.so
  ProcCmdline: /usr/bin/unity-system-compositor-spinner
  ProcEnviron:
   
  Signal: 6
  SourcePackage: unity-system-compositor
  StacktraceTop:
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
   ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  Title: unity-system-compositor-spinner crashed with SIGABRT in 
__gnu_cxx::__verbose_terminate_handler()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.54-1
  version.lightdm: lightdm 1.11.4-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1347053/+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 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

[Antti Kaijanmäki]

OK, but you _can connect_  to the hidden network, so this bug is Fix
Released.

the keyboard issue: bug #1333135


Could you file a new bug about the indicator visual problem and attach the 
following information to it:

=== with phablet-shell from the device ===
$ dbus-send --session --print-reply --dest=com.canonical.indicator.network 
/com/canonical/indicator/network/phone org.gtk.Menus.Start array:uint32:1,0 > 
menumodel.txt

$ nmcli d wifi list > nmcli_d_wifi_list.txt

$ dbus-send --print-reply --dest=com.canonical.indicator.network 
/com/canonical/indicator/network org.gtk.Actions.DescribeAll > actiongroup.txt
==

=== on the host computer with the device attached via USB ===
1. open the network indicator and take a screenshot of it's wrong contents:

$ phablet-screenshot indicator.png
==

Download the files from the device with adb:
$ adb pull /home/phablet/

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1202806/+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 1350193] Re: maliit-server consuming large amounts of memory

[Michael Sheldon]

** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/reduce-memory-
usage

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

Title:
  maliit-server consuming large amounts of memory

Status in Ubuntu Keyboard:
  In Progress
Status in “ubuntu-keyboard” package in Ubuntu:
  In Progress

Bug description:
  using ~40mb after starting. This needs to be reduced significantly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1350193/+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 1202806] Re: [mako] Cannot connect to hidden wifi network (touch|android)

[Seth Forshee]

All right, it turns out I didn't run ubuntu-device-flash the right way
and ended up with an old image. I tested with devel-proposed, and I'd
say that it's mostly fixed.

The UI is there, and I can use it to connect to a hidden network, but I
did have a few of problems. First, when the keyboard was present on the
screen to setup up the network it resulted in the test field for
entering the passphrase getting covered by buttons, making it impossible
to select the field until I dismissed the keyboard. Second, once
connected I didn't have the little "wifi connected" icon in the top bar
that I get when connected to a non-hidden network, just a blank space
where it should have been. Finally, after I connected to the hidden
network the list of available networks showed that network twice, once
with a check mark and high signal indication and again unchecked with
the graphic showing no signal. When I tapped the network with no signal
it just disappeared.

Oh, one more thing. The hidden network always appears at the bottom of
the list of available network, regardless of relative signal strength,
and even when I'm connected to that network.

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

Title:
  [mako] Cannot connect to hidden wifi network (touch|android)

Status in “indicator-network” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Incomplete

Bug description:
  There's no UI for this right now that I can find, but if I try to
  connect to a hidden wireless network on mako by manually creating the
  wpa_supplicant.conf file and launching wpa_supplicant by hand,
  authentication with the network fails. The same operation works fine
  on maguro, so odds are this is a driver bug. The network in question
  has WPA2-PSK security.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1202806/+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 1354375] Re: lxc-snapshot destroys container

[Serge Hallyn]

The safety workaround (refusing lxc-snapshot of lvm-backed containers)
is committed in git.

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Fix Committed

** Also affects: lxc (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: lxc (Ubuntu Trusty)
   Status: New => Confirmed

** Changed in: lxc (Ubuntu Trusty)
   Importance: Undecided => High

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

Title:
  lxc-snapshot destroys container

Status in “lxc” package in Ubuntu:
  Fix Committed
Status in “lxc” source package in Trusty:
  Confirmed

Bug description:
  Was following instructions for lxc-snapshots at:

https://help.ubuntu.com/lts/serverguide/lxc.html

  The problem I am reporting is that when I create a snapshot with:

lxc-snapshot -n c1

  which creates snap0 (snap1...snapN, etc.), after I try restore the
  snapshot with:

lxc-snapshot -r snap0 -n c1

  lxc seems to happily remove snap0 and c1, thus destroying the entire
  container. I would paste the output, but it was via a vbox vm and
  wasn't easy to copy/paste the text, so I have attached a screenshot
  instead.

  The release was 14.0.4.1 LTS with lxc 1.0.5-0ubuntu0.1. What I
  expected was for the snapshot to first remove c1 and then rename snap0
  to c1. Seeing as how the c1 container was a LVM snapshot I can see
  that removing c1 (the origin of snap0) might be the reason for it
  killing snap0 and c1, but it seems a little unpexted, especially if
  this had been more than a test.

  Is this a real bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Fri Aug  8 05:58:41 2014
  InstallationDate: Installed on 2014-08-07 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1354375/+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 1346804] Re: [dialer-app] Don't display 'SIM1' if only one SIM is available

[Timo Jyrinki]

** Tags removed: rmt14
** Tags added: rtm14

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

Title:
  [dialer-app] Don't display 'SIM1' if only one SIM is available

Status in Dialer app for Ubuntu Touch:
  Confirmed
Status in Messaging App:
  Confirmed
Status in Ubuntu UX bugs:
  Fix Committed
Status in “dialer-app” package in Ubuntu:
  Fix Released
Status in “messaging-app” package in Ubuntu:
  Fix Released

Bug description:
  The dialer shouldn't display SIM1 (in red) when the phone uses only 1
  SIM. (cf screenshot)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1346804/+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 1312707] Re: [Dash] Dash should not reset when unfocused

[Michał Sawicz]

** Tags added: rtm14

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

Title:
  [Dash] Dash should not reset when unfocused

Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  1. Open Scopes scope
  2. Select scope
  3. Open result from surfacing or from search, such that Preview will contain 
a button launching a browser
  4. Press the button in the Preview
  5. Browser launches
  6. Swipe the browser away to right.

  What happens:
  Dash 'Apps' section is shown.

  What I expect to happen:
  Dash should show the scope result preview I was viewing. Otherwise I need to 
navigate back, search again, and possibly loose bandwidth and patience.

  --
  Desired resolution:

  See https://sites.google.com/a/canonical.com/unity8dash/navigating-
  the-dash

  Once the Dash is released as an app, the user can return to the
  previous state of the Dash using the right edge interactions. They can
  also tap on the Home button. A long left swipe will take them back to
  the 'Home scope' ie apps scope.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1312707/+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 1352591] Re: apport-retrace does not update libraries in a sandbox

[Brian Murray]

There is also not a check to see whether or not the path in
InterpreterPath or ExecutablePath is current. From sandboxutils.py:

   # package hooks might reassign Package:, check that we have the originally
# crashing binary
for path in ('InterpreterPath', 'ExecutablePath'):
if path in report and not os.path.exists(sandbox_dir + report[path]):

So we only check for the existence not whether or not it is recent.
Subsequently, a retrace with a old executable can fail like so.

Reading symbols from 
/tmp/apport-utopic//usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service...Reading
 symbols from /tmp/ap
port-utopic/usr/lib/debug/.build-id/5a/851287dfe6af740803822fa635ea6fa5fa5f19.debug...done.
done.
warning: core file may not match specified executable file.

** Summary changed:

- apport-retrace does not update libraries in a sandbox
+ apport-retrace does not update libraries or executable in a sandbox

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

Title:
  apport-retrace does not update libraries or executable in a sandbox

Status in Apport crash detection/reporting:
  New
Status in “apport” package in Ubuntu:
  New

Bug description:
  I was trying to retrace a crash that failed with the retracers in the
  Ubuntu Error Tracker.  I'm using gdb-multiarch from the following PPA
  (https://launchpad.net/~daisy-pluckers/+archive/ubuntu/daisy-seeds)
  and apport from bzr revision number 2818. The command follows:

  PYTHONPATH=$PYTHONPATH:/srv/daisy.staging.ubuntu.com/prod
  uction/apport python 
/srv/daisy.staging.ubuntu.com/production/apport/bin/apport-retrace 
~/4d9d6984-1883-11e4-84c3-fa163e22e467.crash -S /srv/da
  isy.staging.ubuntu.com/production/daisy/retracer/config --sandbox-dir 
/srv/daisy.staging.ubuntu.com/production/cache/Ubuntu\ 
14.10/cache-DhmXbj/sandbox -C 
/srv/daisy.staging.ubuntu.com/production/cache/Ubuntu\ 14.10/cache-DhmXbj/cache 
-v -g

  With that bt full would return:

  Thread 1 (LWP 2270):
  #0  __libc_do_syscall () at 
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
  No locals.
  #1  0xb6a3805e in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
  _a1 = 0
  _a3tmp = 6
  _a1tmp = 0
  _a3 = 6
  _nametmp = 268
  _a2tmp = 2270
  _a2 = 2270
  _name = 268
  _sys_result = 
  pd = 0xb680e000
  pid = 0
  selftid = 2270
  #2  0xb6a38d4e in __GI_abort () at abort.c:89
  save_stage = 2
  act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, 
sa_mask = {__val = {1, 3064945215, 3064945144, 3064575611, 
3064342309, 3069180536, 3061899264, 3069180712, 3061899264, 
3065241600, 729240, 0, 1, 3199521020, 0, 3069123061, 3069180712, 
1, 5, 0, 3199521440, 3064036264, 1, 3064946200, 1, 10212828, 
3199521044, 3069005824, 3199521440, 3069141488, 10212360, 
3061900488}}, sa_flags = 2, sa_restorer = 0x0}
  sigs = {__val = {32, 0 }}
  #3  0xb6b892c4 in ?? ()
 from /srv/daisy.staging.ubuntu.com/production/cache/Ubuntu 
14.10/cache-DhmXbj/sandbox-corrupt/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  No symbol table info available.
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

  However, using apport-retrace without the sandbox-dir command creates
  a more complete backtrace like in http://paste.ubuntu.com/7929061/.

  I've tracked this down to the following from needed_runtime_packages
  in apport/sandboxutils.py:

  # grab as much as we can
  for l in libs:
  if os.path.exists(sandbox + l):
  continue

  There is no check to see if the sandbox version of the library is
  current or not, subsequently the library may be out of date which was
  causing the retrace to fail.

  I've verified this by checking the ctime of the file before and after
  commenting out the "if os.path.exists()" check.

  ls -lch /srv/daisy.staging.ubuntu.com/production/cache/Ubuntu\ 
14.10/cache-DhmXbj/sandbox-old/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  lrwxrwxrwx 1 root root 19 Jul 11 02:19 
/srv/daisy.staging.ubuntu.com/production/cache/Ubuntu 
14.10/cache-DhmXbj/sandbox-old/usr/lib/arm-linux-gnueabihf/libstdc++.so.6 -> 
libstdc++.so.6.0.20

  ls -lch /srv/daisy.staging.ubuntu.com/production/cache/Ubuntu\ 
14.10/cache-DhmXbj/sandbox-corrupt/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  lrwxrwxrwx 1 root root 19 Aug  4 22:27 
/srv/daisy.staging.ubuntu.com/production/cache/Ubuntu 
14.10/cache-DhmXbj/sandbox-old/usr/lib/arm-linux-gnueabihf/libstdc++.so.6 -> 
libstdc++.so.6.0.20

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

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

[Touch-packages] [Bug 1312707] Re: [Dash] Dash should not reset when unfocused

[Launchpad Bug Tracker]

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

** Changed in: unity8 (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Dash] Dash should not reset when unfocused

Status in Ubuntu UX bugs:
  Fix Committed
Status in The Unity 8 shell:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  1. Open Scopes scope
  2. Select scope
  3. Open result from surfacing or from search, such that Preview will contain 
a button launching a browser
  4. Press the button in the Preview
  5. Browser launches
  6. Swipe the browser away to right.

  What happens:
  Dash 'Apps' section is shown.

  What I expect to happen:
  Dash should show the scope result preview I was viewing. Otherwise I need to 
navigate back, search again, and possibly loose bandwidth and patience.

  --
  Desired resolution:

  See https://sites.google.com/a/canonical.com/unity8dash/navigating-
  the-dash

  Once the Dash is released as an app, the user can return to the
  previous state of the Dash using the right edge interactions. They can
  also tap on the Home button. A long left swipe will take them back to
  the 'Home scope' ie apps scope.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1312707/+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 1313289] Re: Low Graphics Mode with AMD R9 270X

[madbiologist]

Which version of Ubuntu are you using?  Can you please paste the output
of uname -srm?

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

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

Title:
  Low Graphics Mode with AMD R9 270X

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  I have an AMD R9 270X graphics card and Ubuntu will occasionally go
  into "low-graphics mode" when starting up. At that point I cannot do
  anything apart from drop into the terminal.

  It happens sporadically, about 3/4 of the time. Often a reboot will
  fix it however because it happens so often, it's very annoying.

  I've tried installing fglrx and fglrx-updates along with the latest
  proprietary AMD drivers including 14.4 stable and 14.3 beta. However
  it still occurs.

  I've also tried using failsafeX settings among other things without
  success.

  Attached are the Xorg and Xorg.failsafe log files.

  There's a segmentation fault at the bottom of the failsafe log files
  which may have something to do with it?

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