[Touch-packages] [Bug 491251]

2014-10-20 Thread Oibaf
No feedback after 4+ years, closing. Feel free to reopen if the problem
still happens with mesa 10.3.1 or later.

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

Title:
  [RV515] Switcher applet not displayed with OpenGL

Status in Cairo-Dock : Core:
  Invalid
Status in Mesa:
  Invalid
Status in “mesa” package in Ubuntu:
  Triaged

Bug description:
  Using 2.1.1-3-1ubuntu2~karmic from the stable ppa , and Kernel
  2.6.32-6 from the Lucid repos[since KMS and OpenGL works better with
  this kernel].

  When running cairo-dock in the openGL mode , the switcher applet is
  not displayed [attached screenshot]

  But the applet works fine the desktop numbers are displayed but the only 
problem is that the switcher is not displayed.
  When i use the non-OpenGL version , there is no such problem.

  
  [lspci]
  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon 
Mobility X1400 [1002:7145]
   Subsystem: Acer Incorporated [ALI] Device [1025:0094]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/491251/+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 491251] Re: [RV515] Switcher applet not displayed with OpenGL

2014-10-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: Confirmed = Invalid

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

Title:
  [RV515] Switcher applet not displayed with OpenGL

Status in Cairo-Dock : Core:
  Invalid
Status in Mesa:
  Invalid
Status in “mesa” package in Ubuntu:
  Triaged

Bug description:
  Using 2.1.1-3-1ubuntu2~karmic from the stable ppa , and Kernel
  2.6.32-6 from the Lucid repos[since KMS and OpenGL works better with
  this kernel].

  When running cairo-dock in the openGL mode , the switcher applet is
  not displayed [attached screenshot]

  But the applet works fine the desktop numbers are displayed but the only 
problem is that the switcher is not displayed.
  When i use the non-OpenGL version , there is no such problem.

  
  [lspci]
  01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon 
Mobility X1400 [1002:7145]
   Subsystem: Acer Incorporated [ALI] Device [1025:0094]

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/491251/+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 1330413] Re: 安装结束的时候提示按钮显示的是“继续测试”

2014-10-20 Thread shijing
** Changed in: ubuntukylin
   Status: Fix Committed = Fix Released

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

Title:
  安装结束的时候提示按钮显示的是“继续测试”

Status in Ubuntu Kylin:
  Fix Released
Status in “language-pack-zh-hans” package in Ubuntu:
  New

Bug description:
  系统:UK 14.10 dailybuild 32 位 6-15
  机器型号:vritualbox 
  现象: 在试用模式,安装结束的时候提示“您可以继续试用Ubuntu 
Kylin。。。”,下面的按钮显示的是“继续测试”,应该改成“继续试用”,如图finish.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1330413/+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 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-20 Thread David Henningsson
What happens is the following:

Gnome settings' UI shows device.description by default. This value is
taken from udev, key ID_MODEL_FROM_DATABASE. The firewire udev device
does not set this value, so it falls back looking for the parent device.
The parent device, the controller has an ID_MODEL_FROM_DATABASE set,
which in my case is Motherboard. So the firewire card ends up with the
name Motherboard.

The ID_MODEL_FROM_DATABASE is probably set (for the firewire controller)
by udev/systemd, see the hwdb directory of systemd sources.

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

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use help for usage information.
   4 sink(s) available.
  [...]
  index: 2
name: alsa_output.firewire-0x000aac0300592827.10-channels
driver: module-alsa-card.c
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 alsa_card.firewire-0x000aac0300592827
module: 8
properties:
alsa.resolution_bits = 16
device.api = alsa
device.class = sound
alsa.class = generic
alsa.subclass = generic-mix
alsa.name = PHASE 88 Rack FW PCM
alsa.id = BeBoB
alsa.subdevice = 0
alsa.subdevice_name = subdevice #0
alsa.device = 0
alsa.card = 0
alsa.card_name = PHASE 88 Rack FW
alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a
alsa.driver_name = snd_bebob
device.bus_path = pci-:01:09.0
sysfs.path = 
/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0
udev.id = firewire-0x000aac0300592827
device.bus = firewire
device.vendor.name = Texas Instruments
device.product.name = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]
device.string = hw:0
device.buffering.buffer_size = 163840
device.buffering.fragment_size = 81920
device.access_mode = mmap+timer
device.profile.name = 10-channels
device.profile.description = 10 Channels
device.description = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels
alsa.mixer_name = PHASE 88 Rack FW
module-udev-detect.discovered = 1
device.icon_name = audio-card-firewire

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+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 1330413] Re: 安装结束的时候提示按钮显示的是“继续测试”

2014-10-20 Thread Anthony Wong
** Changed in: language-pack-zh-hans (Ubuntu)
   Status: New = Fix Released

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

Title:
  安装结束的时候提示按钮显示的是“继续测试”

Status in Ubuntu Kylin:
  Fix Released
Status in “language-pack-zh-hans” package in Ubuntu:
  Fix Released

Bug description:
  系统:UK 14.10 dailybuild 32 位 6-15
  机器型号:vritualbox 
  现象: 在试用模式,安装结束的时候提示“您可以继续试用Ubuntu 
Kylin。。。”,下面的按钮显示的是“继续测试”,应该改成“继续试用”,如图finish.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1330413/+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 1382861] Re: Auto brightness toggle removed from power indicator

2014-10-20 Thread Niklas Wenzel
Screenshot.

** Attachment added: missing-toggle.png
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1382861/+attachment/4240406/+files/missing-toggle.png

** Summary changed:

- Auto brightness toggle removed from power indicator
+ Auto brightness toggle sometimes doesn't appear in power indicator

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

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in “indicator-power” package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1382861/+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 1382861] Re: Auto brightness toggle removed from power indicator

2014-10-20 Thread Niklas Wenzel
Ok, I confirmed this but modified the bug description according to the
discussion here: https://lists.launchpad.net/ubuntu-phone/msg10258.html

** Changed in: indicator-power (Ubuntu)
   Status: Incomplete = Confirmed

** Description changed:

- On RTM 5 with Mako, the auto brightness toggle switch has been removed
- from the power indicator. This was highly useful, and I don't understand
- why it has been removed. Please bring it back!!
+ On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
+ brightness toggle is sometimes missing in the power indicator. Sometimes
+ everything is fine and sometimes it's simply not there.

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

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in “indicator-power” package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1382861/+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 1382861] Re: Auto brightness toggle removed from power indicator

2014-10-20 Thread Niklas Wenzel
Hoping that it's of help to you, I'll attach my log file.

** Attachment added: indicator-power.log
   
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1382861/+attachment/4240405/+files/indicator-power.log

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

Title:
  Auto brightness toggle sometimes doesn't appear in power indicator

Status in “indicator-power” package in Ubuntu:
  Confirmed

Bug description:
  On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto
  brightness toggle is sometimes missing in the power indicator.
  Sometimes everything is fine and sometimes it's simply not there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1382861/+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 828538] Re: Europe/Moscow not updated

2014-10-20 Thread Йож
26.10 time will update in Moscow, but not in my ubuntu server... Can you
resolve it before 26.10.2014?

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

Title:
  Europe/Moscow not updated

Status in “tzdata” package in Ubuntu:
  Confirmed

Bug description:
  Please, update zone Russia (Europe/Moscow, etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/828538/+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 971018] Re: Auto-hide Unity Launcher will not reveal when mouse pushed to left side in VirtualBox or VMware

2014-10-20 Thread Michał Szwejkowski
Still present on Ubuntu 14.10 VBox 4.3.18

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

Title:
  Auto-hide Unity Launcher will not reveal when mouse pushed to left
  side in VirtualBox or VMware

Status in Unity:
  Incomplete
Status in “libxfixes” package in Ubuntu:
  Confirmed
Status in “unity” package in Ubuntu:
  Incomplete
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Precise 12.04 Beta 2 AMD64 DVD:
   
   
  I am running Ubuntu Precise 12.04 Beta 2 in a VirtualBox 4.1.8 session.  
VirtualBox Guest Additions have been installed via jockey-gtk from the Ubuntu 
Precise repository, and Unity is running in 3D mode with Compiz.
   
   
  When the Unity Launcher is set to autohide, the Launcher will never reveal 
when the mouse pointer is moved to the left edge of the screen.  It does not 
matter how much pressure is applied; the Launcher never appears.
   
   
  I have tried the following VirtualBox window form-factors, all with the 
same result (the Launcher never appears):
   
  -- VirtualBox session running in a non-maximized window
  -- VirtualBox session running in a maximized window
  -- VirtualBox session running full-screen
   
   
  I have attached a screen capture (OGV) with Ubuntu Precise running in a 
maximized VirtualBox window.
   
   
  Note:  This Bug may be related to the following other Bugs reported on 
LaunchPad:
   
  -- Bug 965643:  Unity 5.8: auto-hide using mouse reveals launcher 
inconsistently
  -- -- https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/965643

  -- Bug 923749:  New push mouse offscreen feature really difficult to get
  -- -- https://bugs.launchpad.net/unity/+bug/923749

  -- Bug 937792:  Left launcher does not revel when in autohide mode on 
multi-monitor setups
  -- -- https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/937792

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  ApportVersion: 2.0-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Sun Apr  1 14:46:23 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/971018/+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 1341548] Re: Online detection does not work with confined apps on Nexus 4

2014-10-20 Thread Dan Chapman
** Changed in: dekko
   Status: Fix Committed = Fix Released

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

Title:
  Online detection does not work with confined apps on Nexus 4

Status in dekko:
  Fix Released
Status in Network Menu:
  Fix Released
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
  Fix Released
Status in “connectivity-api” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Fix Released
Status in “connectivity-api” package in Ubuntu RTM:
  Fix Released
Status in “indicator-network” package in Ubuntu RTM:
  Fix Released

Bug description:
  Dekko is not detecting if Online correctly. If I look at the server
  logs, I don't see anything in the email server logs for dekko to
  connect. If I look in ~/.cache/upstart/application-click-
  com.ubuntu.developer.dpniel.dekko_dekko_0.2.2.log, I don't see
  anything about connecting. If I click the globe in dekko, I see that
  it is in offline mode and selecting one of the others seems to make no
  difference (I see nothing in the server logs and the upstart logs) and
  the setting doesn't stick (ie, it *always* says 'Offline mode').

  I thought this might be bug #1226844, but if I adjust
  /var/lib/apparmor/profiles/*dekko* to remove 'deny' from in front of
  the NetworkManager and ofono rules and run apparmor_parser -r
  /var/lib/apparmor/profiles/*dekko*, there are no denials but it still
  doesn't detect if I am online or not  when on 3G.

  If I get on wifi instead of 3G, dekko can detect if I am online if I
  apply the apparmor changes I mentioned above (though, there are still
  NetworkManager dbus denials).

  For dekko to work as a confined application (ie, shipped in the Ubuntu
  App Store) it is going to need to operate without these NetworkManager
  and ofono DBus APIs, because they are not allowed to app store apps.

  
  Previous description:
  In addidtion to TLS on port 143, it would be nice to support imaps on port 
993.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dekko/+bug/1341548/+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 244250] Re: Spurious reboot notifications caused by libssl upgrades.

2014-10-20 Thread Khaled Blah
On Ubuntu 14.04 this bug still persists. Is there any reason why libssl
would require different treatment than other libraries? I.e. why
wouldn't it suffice to restart services depending on libssl or
libcrypto?

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

Title:
  Spurious reboot notifications caused by libssl upgrades.

Status in “openssl” package in Ubuntu:
  Fix Released

Bug description:
  The postinst script for libssl0.9.8 currently has a bug where it sends
  a reboot notifcation whenever libssl is configured.  So reconfiguring
  libssl0.9.8 or even just installing libssl0.9.8 will result in a
  reboot notification.  Sending of the reboot notification should
  definitely be moved inside the upgrading guard.  The correct fix is
  likely to move it inside a version comparison guard for particular
  important updates like Colin suggests below -- this is what every
  other standard package using notify-reboot-required does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+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 828538] Re: Europe/Moscow not updated

2014-10-20 Thread Йож
Current version 2014e-0ubuntu0.12.04 doesn't contain information about
russian time zone changes. Debian have 2014h-0wheezy1, that doesn't
contain this problem.

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

Title:
  Europe/Moscow not updated

Status in “tzdata” package in Ubuntu:
  Confirmed

Bug description:
  Please, update zone Russia (Europe/Moscow, etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/828538/+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 1383174] [NEW] i am a new user

2014-10-20 Thread Debasis Chaudhuri
Public bug reported:

i dont know what to do?

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
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Oct 20 14:01:42 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:104c]
InstallationDate: Installed on 2014-08-24 (57 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
LightdmGreeterLog:
 ** (lightdm-gtk-greeter:9160): WARNING **: Failed to load user image: Failed 
to open file '/home/debasis/.face': No such file or directory
 g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1601): WARNING **: Failed to load 
user image: Failed to open file '/home/debasis/.face': No such file or directory
MachineType: ASUSTeK Computer Inc. K53U
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=479ef2c5-a812-47cc-a4cf-5a2f9f42be3d ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 221
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53U
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.:bvr221:bd03/12/2012:svnASUSTeKComputerInc.:pnK53U:pvr1.0:rvnASUSTeKComputerInc.:rnK53U:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K53U
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.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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct 20 13:45:05 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: radeon

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


** Tags: apport-bug 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/1383174

Title:
  i am a new user

Status in “xorg” package in Ubuntu:
  New

Bug description:
  i dont know what to do?

  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
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Oct 20 14:01:42 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:104c]
  InstallationDate: Installed on 2014-08-24 (57 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9160): WARNING **: Failed to load user image: Failed 
to open file '/home/debasis/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1601): WARNING **: Failed to 
load user image: Failed to open file '/home/debasis/.face': No such file or 
directory
  MachineType: ASUSTeK Computer Inc. K53U
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: 

[Touch-packages] [Bug 828538] Re: Europe/Moscow not updated

2014-10-20 Thread Andrey Bondarenko
Please see bug #1377813

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

Title:
  Europe/Moscow not updated

Status in “tzdata” package in Ubuntu:
  Confirmed

Bug description:
  Please, update zone Russia (Europe/Moscow, etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/828538/+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 1383202] [NEW] Left touch pad button not working on Ubuntu (Gnome) 14.10 and kernel above 3.16.0-20

2014-10-20 Thread George Karavasilev
Public bug reported:

So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for
some reason kernels:

3.16.0-23
3.16.0-22
3.16.0-21

Don't seem to recognise my left touchpad button, however it worked up to
kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed
just in case) and the touchpad is perfectly functional and the left
button works like a charm. I am willing to provide any info you guys
need. Oh and - left clicking works with a mouse. Also - xorg edgers PPA
and using 3.17 mainline kernel don't seem to fix this.

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

** Description changed:

  So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for
  some reason kernels:
  
  3.16.0-23
  3.16.0-22
  3.16.0-21
- Don't seem to recognise my left touchpad button, however it worked up to 
kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed just in 
case) and the touchpad is perfectly functional and the left button works like a 
charm. I am willing to provide any info you guys need. Oh and - left clicking 
works with a mouse. Also - xorg edgers PPA and using 3.17 mainline kernel don't 
seem to fix this.
+ 
+ Don't seem to recognise my left touchpad button, however it worked up to
+ kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have installed
+ just in case) and the touchpad is perfectly functional and the left
+ button works like a charm. I am willing to provide any info you guys
+ need. Oh and - left clicking works with a mouse. Also - xorg edgers PPA
+ and using 3.17 mainline kernel don't seem to fix this.

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

Title:
  Left touch pad button not working on Ubuntu (Gnome) 14.10 and kernel
  above 3.16.0-20

Status in “xorg” package in Ubuntu:
  New

Bug description:
  So, I've this Lenovo B50 laptop that runs Ubuntu Gnome 14.10 and for
  some reason kernels:

  3.16.0-23
  3.16.0-22
  3.16.0-21

  Don't seem to recognise my left touchpad button, however it worked up
  to kernel 3.16.0-20 and I've tested on Windows 8.1 (which I have
  installed just in case) and the touchpad is perfectly functional and
  the left button works like a charm. I am willing to provide any info
  you guys need. Oh and - left clicking works with a mouse. Also - xorg
  edgers PPA and using 3.17 mainline kernel don't seem to fix this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1383202/+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 1383208] [NEW] Manage Scopes does not display all scopes

2014-10-20 Thread Nathan Haines
Public bug reported:

On ubuntu-rtm/14.09 r4 and ubuntu-rtm/14.09-proposed r100, bringing up
the Manage Scopes view and tapping All does not display all installed
scopes after install.  Only after a search or a reboot are additional
scopes displayed as well.

This occurs in unity8 8.00+14.10.20141017-0ubuntu1

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Status: 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/1383208

Title:
  Manage Scopes does not display all scopes

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu-rtm/14.09 r4 and ubuntu-rtm/14.09-proposed r100, bringing up
  the Manage Scopes view and tapping All does not display all
  installed scopes after install.  Only after a search or a reboot are
  additional scopes displayed as well.

  This occurs in unity8 8.00+14.10.20141017-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383208/+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 1383207] [NEW] Different system settings show different sound cards and chosen sound card will only play on command line test.

2014-10-20 Thread Jamil V
Public bug reported:

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


Sound has been troublesome on my system.

I noticed this happened twice. I have two different system settings
programs (because of the first time this happened). In one program (KDE
system settings), my soundcard is listed, in the other (Ubuntu's default
system settings),  it is not listed. I cannot play sound out of it with
graphical desktop programs, but `aplay
/usr/share/sounds/alsa/Front_Center.wav` does play sound fine.

I followed these instructions:
https://help.ubuntu.com/community/SoundTroubleshooting

`pacmd` looked fine. My chosen sound card had an asterisk next to it.

`aplay /usr/share/sounds/alsa/Front_Center.wav` ran as user fine

`sudo aplay -l` lists it accurately

`find /lib/modules/`uname -r` | grep snd` gave an appropriate driver:
/lib/modules/3.13.0-37-generic/kernel/sound/pci/echoaudio/snd-layla24.ko

`lspci -v | grep -A7 -i audio` showed my sound card:
03:00.0 PCI bridge: Pericom Semiconductor PI7C9X111SL PCIe-to-PCI Reversible 
Bridge (rev 02) (prog-if 00 [Normal decode])
--
Subsystem: Echo Digital Audio Corporation Layla24
Flags: bus master, medium devsel, latency 192, IRQ 18
Memory at fa20 (32-bit, non-prefetchable) [size=1M]
Kernel driver in use: snd_layla24

I tried `modprobe snd_layla24` and `modprobe snd-layla24` with no
difference being made.


I tried adding it to /etc/modprobe.d/alsa-base.conf, but it still doesn't show 
up in the ubuntu system settings (gnome I think), which I think is the one that 
determines if it'll play through regular desktop applications or not (7th to 
last line snd_layla24):
--
# autoloader aliases
install sound-slot-0 /sbin/modprobe snd-card-0
install sound-slot-1 /sbin/modprobe snd-card-1
install sound-slot-2 /sbin/modprobe snd-card-2
install sound-slot-3 /sbin/modprobe snd-card-3
install sound-slot-4 /sbin/modprobe snd-card-4
install sound-slot-5 /sbin/modprobe snd-card-5
install sound-slot-6 /sbin/modprobe snd-card-6
install sound-slot-7 /sbin/modprobe snd-card-7

# Cause optional modules to be loaded above generic modules
install snd /sbin/modprobe --ignore-install snd $CMDLINE_OPTS  { 
/sbin/modprobe --quiet --use-blacklist snd-ioctl32 ; /sbin/modprobe --quiet 
--use-blacklist snd-seq ; }
#
# Workaround at bug #499695 (reverted in Ubuntu see LP #319505)
install snd-pcm /sbin/modprobe --ignore-install snd-pcm $CMDLINE_OPTS  { 
/sbin/modprobe --quiet --use-blacklist snd-pcm-oss ; : ; }
install snd-mixer /sbin/modprobe --ignore-install snd-mixer $CMDLINE_OPTS  { 
/sbin/modprobe --quiet --use-blacklist snd-mixer-oss ; : ; }
install snd-seq /sbin/modprobe --ignore-install snd-seq $CMDLINE_OPTS  { 
/sbin/modprobe --quiet --use-blacklist snd-seq-midi ; /sbin/modprobe --quiet 
--use-blacklist snd-seq-oss ; : ; }
#
install snd-rawmidi /sbin/modprobe --ignore-install snd-rawmidi $CMDLINE_OPTS 
 { /sbin/modprobe --quiet --use-blacklist snd-seq-midi ; : ; }
# Cause optional modules to be loaded above sound card driver modules
install snd-emu10k1 /sbin/modprobe --ignore-install snd-emu10k1 $CMDLINE_OPTS 
 { /sbin/modprobe --quiet --use-blacklist snd-emu10k1-synth ; }
install snd-via82xx /sbin/modprobe --ignore-install snd-via82xx $CMDLINE_OPTS 
 { /sbin/modprobe --quiet --use-blacklist snd-seq ; }

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 /sbin/modprobe --ignore-install saa7134 $CMDLINE_OPTS  { 
/sbin/modprobe --quiet --use-blacklist saa7134-alsa ; : ; }
# Prevent abnormal drivers from grabbing index 0
options bt87x index=-2
options cx88_alsa index=-2
options saa7134-alsa index=-2
options snd-atiixp-modem index=-2
options snd-intel8x0m index=-2
options snd-via82xx-modem index=-2
options snd-usb-audio index=-2
options snd-usb-caiaq index=-2
options snd-usb-ua101 index=-2
options snd-usb-us122l index=-2
options snd-usb-usx2y index=-2
options snd_layla24 index=0
# Ubuntu #62691, enable MPU for snd-cmipci
options snd-cmipci mpu_port=0x330 fm_port=0x388
# Keep snd-pcsp from being loaded as first soundcard
options snd-pcsp index=-2
# Keep snd-usb-audio from beeing loaded as first soundcard
options snd-usb-audio index=-2
--

I tried `sudo alsa reload`, `pulseaudio -k`, and `sudo pulseaudio -k`

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


** Tags: alsa audio pulseaudio sound sound-card

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

Title:
  Different system settings show different sound cards and chosen sound
  card will only play on command line test.

Status in “alsa-utils” package in Ubuntu:
  New

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

  Sound has been troublesome on my system.

  I noticed 

[Touch-packages] [Bug 1331813] Re: Support ipv6 mobile connections

2014-10-20 Thread richard mccormick
adb push is giving me permissions denied :/  ive tried everything
including the adb she manual setting of the apn and i still have no 3g
data, im only able to receive texts and make calls any idea on how to
circumvent this? i installed ubuntu touch through multi rom on the n5 if
that makes any difference

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

Title:
  Support ipv6 mobile connections

Status in “network-manager” package in Ubuntu:
  Confirmed
Status in “ofono” package in Ubuntu:
  Confirmed
Status in “ubuntu-download-manager” package in Ubuntu:
  Confirmed

Bug description:
  My new T-Mobile SIM only has Apn contexts using IPv6 so cellular data is not 
working
  Purchased the SIM a couple weeks ago.

  The output of the /usr/share/ofono/list-contexts is:

  [ /ril_0 ]
  [ /ril_0/context1 ]
  MessageProxy =
  Type = internet
  Password =
  Active = 1
  MessageCenter = http://mms.msg.eng.t-mobile.com/mms/wapenc
  Username =
  IPv6.Settings = { Interface=rmnet_usb0 }
  AccessPointName = fast.t-mobile.com
  Settings = { }
  Name = T-Mobile GPRS
  Protocol = ipv6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1331813/+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 1383208] Re: Manage Scopes does not display all scopes

2014-10-20 Thread Niklas Wenzel
** 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/1383208

Title:
  Manage Scopes does not display all scopes

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu-rtm/14.09 r4 and ubuntu-rtm/14.09-proposed r100, bringing up
  the Manage Scopes view and tapping All does not display all
  installed scopes after install.  Only after a search or a reboot are
  additional scopes displayed as well.

  This occurs in unity8 8.00+14.10.20141017-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383208/+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 327190] Re: User Crontab is outside of GUI session

2014-10-20 Thread Christian Kastner
cron jobs are started by the cron daemon which is completely unrelated
to your GUI session, or any other session that might be active for the
user.

As ccooke pointed out, if you want access to an unrelated session,
you're going to have to do it manually.

** Changed in: cron (Ubuntu)
   Status: New = Opinion

** Changed in: cron (Ubuntu)
   Status: Opinion = Invalid

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

Title:
  User Crontab is outside of GUI session

Status in “cron” package in Ubuntu:
  Invalid

Bug description:
  When trying to execute programs that require variables from the GUI
  session. the crontab fails. It can no longer execute tasks which
  relate to editing gnome gconf or any other session settings.

  I believe this is because the crontab is outside of the gnome session.
  There are two possible fixes, 1) Somehow allow the system cron to
  access session variables when users are logged in, 2) Create a special
  cron which runs when users log in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/327190/+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 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT

2014-10-20 Thread Daniel Llewellyn
seems fixed after installing ibus-dbg along with the utopic updates
accumulated for a week or so installed just now at 09:40 GMT on the 20th
october. Unsure whether it was the ibus-dbg and it's dependencies or the
latest utopic updates that fixed things.

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT

Status in IBus:
  Unknown
Status in “ibus” package in Ubuntu:
  Triaged

Bug description:
  Restarted system after installing updates was greeting me with that
  message

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: ibus 1.5.3-6ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Sat Oct  5 08:17:10 2013
  Disassembly: = 0x7f62f38f4f77:   Cannot access memory at address 
0x7f62f38f4f77
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2013-06-12 (114 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: ibus-ui-gtk3 crashed with SIGABRT
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1235567/+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 790173] Re: Cron doesn't send output properly

2014-10-20 Thread Christian Kastner
Fix

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

** Package changed: cron (Ubuntu) = speech-dispatcher (Ubuntu)

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

Title:
  Cron doesn't send output properly

Status in “speech-dispatcher” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: cron

  I have a bash script checking for new versions of Vim (in Bram
  Moolenaar's Mercurial repository) that's run by cron. The script saves
  its output into a log file and, if there is something interesting to
  say, at the and does 'cat $LOG_FILE'. The problem is that when run by
  cron on my newly installed Ubuntu 10.04.2 I don't get the output in
  mail but only 'expr: syntax error' line instead.

  Obviously I thought there was some error in the script at first, but
  after trying and checking I've found none. Besides, the script runs OK
  from command line and the same script runs OK from cron on Ubuntu
  8.04. And I've also found (via checking the script's log whilst it was
  running) that it actually runs OK even here on Ubuntu 10.04.2, only I
  don't get the output. Therefore I'm not even sure whether this bug
  belongs to Cron or Postfix.

  I've also tried to run by cron different parts of the script
  separately, they worked OK and output in mail was OK too.

  I think this might perhaps be related with this discussion I've
  googled: http://www.howtoforge.com/forums/showthread.php?t=45202

  Thx.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/790173/+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 1164083] Re: libreoffice spams stdout with Fontconfig warning: ignoring C.UTF-8: not a valid language tag

2014-10-20 Thread Mike Gerow
Facing the same issue. According to https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=717423 this has been fixed in fontconfig=2.11.0-2

** Bug watch added: Debian Bug tracker #717423
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717423

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

Title:
  libreoffice spams stdout with Fontconfig warning: ignoring C.UTF-8:
  not a valid language tag

Status in “fontconfig” package in Ubuntu:
  New

Bug description:
  when libreoffice is started from the shell command line, it spams the 
terminal window with a stream of messages
  Fontconfig warning: ignoring C.UTF-8: not a valid language tag
  This message should be reported at most once per libreoffice invocation.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: fontconfig 2.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Wed Apr  3 14:22:46 2013
  InstallationDate: Installed on 2011-11-01 (519 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to quantal on 2013-03-21 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1164083/+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 1381050] Re: Import Key File fails when the path of the file has special characters

2014-10-20 Thread Bruno Nova
Here's a traceback of the exception:

org.freedesktop.DBus.Python.UnicodeEncodeError: Traceback (most recent call 
last):
  File /usr/lib/python3/dist-packages/dbus/service.py, line 707, in 
_message_cb
retval = candidate_method(self, *args, **keywords)
  File 
/usr/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py,
 line 288, in AddKey
return self.add_key(path)
  File 
/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py, line 
800, in add_key
if not os.path.exists(path):
  File /usr/lib/python3.4/genericpath.py, line 19, in exists
os.stat(path)
UnicodeEncodeError: 'ascii' codec can't encode character '\xea' in position 20: 
ordinal not in range(128)

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

Title:
  Import Key File fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The Import Key File... button in the Authentication tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the /home/$USER/Downloads folder is 
named /home/$USER/Transferências here.
  Adding a key from that folder fails, but adding a key from /home/$USER (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_(Error importing selected file),
_(The selected file may not be a GPG key file 
  or it might be corrupt.))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error(Authentication canceled, changes have not 
been saved)

  self.backend.AddKey(chooser.get_filename()) throws a 
org.freedesktop.DBus.Python.UnicodeEncodeError exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 678421] Re: Error message for a faulty ~/.profile script

2014-10-20 Thread Martin Pitt
Gunnar,

Running it through sh -n is definitively a good way how to test a
shell script. It of course will miss a lot of errors (variable typos,
failing programs in a set -e script, etc.), but it at least will catch
obvious syntax errors. So ignoring faulty scripts and showing some error
message (in ~/.xsession-errors or even a dialog) seems appropriate to
me.

Thanks for working on this! I'll review the MP now.

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

Title:
  Error message for a faulty ~/.profile script

Status in Light Display Manager:
  In Progress
Status in “gdm” package in Ubuntu:
  Triaged
Status in “lightdm” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: gdm

  After adding function AddPath { PATH=$1:$PATH } to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in .profile
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user .profile and .xprofile scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/678421/+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 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.

2014-10-20 Thread Andy Smith
I don't know if this is at all relevant, but I also got the error
message:

xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed after
rebuilding and running an OPEN Windows (xview) application as a 32-bit
executable on a CentoS 6.4 x86_64 architecture. There is apparently no
native 64-bit xview - presumably because the data structures inherent in
the package assume 4 bytes for address pointers, and too much trouble to
re-engineer, hence the 32-bit build and the error here.

The problem was resolved here by explicitly linking to the dynamic run
time library:

/usr/lib/libX11-xcb.so.1.

The linker does not require the libX11-xcb.so.1 to be specified, but it
clearly defaults to the 64-bit /usr/lib64/libX11-xcb.so.1 version. For
users where they only have a 32 bit binary xview application, there is
probably some Linux command to reset the default  libX11-xcb.so.1
dynamic library path.

Frankly I don't know much at all about the inner workings of Linux, but
this post may be hepful to anyone else who is having similar problems.
If irrelevant, please ignore.

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

Title:
  nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID:
  Assertion `ret != inval_id' failed.

Status in Modular X11 Libraries:
  Confirmed
Status in “libx11” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  Here is a backtrace from Ubuntu Precise.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.2.1-2ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-5.11-generic-pae 3.2.0-rc5
  Uname: Linux 3.2.0-5-generic-pae i686
  ApportVersion: 1.90-0ubuntu1
  Architecture: i386
  AssertionMessage: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret 
!= inval_id' failed.
  Date: Sat Dec 17 14:16:03 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/nautilus
  ExecutableTimestamp: 1324036665
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  ProcCmdline: nautilus -n
  ProcCwd: /
  Signal: 6
  SourcePackage: nautilus
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6
  Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: 
Assertion `ret != inval_id' failed.
  UpgradeStatus: Upgraded to precise on 2011-12-16 (1 days ago)
  UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare 
vboxusers

To manage notifications about this bug go to:
https://bugs.launchpad.net/xlibs/+bug/905686/+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 846407] Re: xrdp is not able to transmitt unity desktop correct - different clients

2014-10-20 Thread Stephen M. Webb
** Changed in: unity
Milestone: None = 7.3.2

** Changed in: unity
   Importance: Undecided = Medium

** Changed in: unity (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  xrdp is not able to transmitt unity desktop correct - different
  clients

Status in Posix RDP server:
  Unknown
Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed
Status in “x2goclient” package in Ubuntu:
  New
Status in “xrdp” package in Ubuntu:
  Confirmed

Bug description:
  After login nothing is shown except desktop wallpaper

  Steps to repeat

  1. sudo apt-get install xrdp
  2. Install CoRD 
http://sourceforge.net/projects/cord/files/cord/0.5.5/CoRD_0.5.5.zip/download
  3. Login to the server using CoRD

  Expected result:

  Unity desktop with menus, taskbars, etc.

  Actual result:

  Unity desktop wallpaper

To manage notifications about this bug go to:
https://bugs.launchpad.net/posixrdp/+bug/846407/+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 764424] Re: Launcher - dropping a file on a launcher app icon should open that file in the app

2014-10-20 Thread Stephen M. Webb
Bug does not meet the definition of critical.

** Changed in: unity
   Importance: Critical = High

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

Title:
  Launcher - dropping a file on a launcher app icon should open that
  file in the app

Status in Ayatana Design:
  Fix Committed
Status in Unity:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged

Bug description:
  If a user drags and drops a file on top of a Launcher app icon, the
  application should open the file if it is a file type it supports.

  If the application does not support the file type nothing should
  happen.

  Also at the moment many Launcher icons do not highlight when the user
  starts dragging, even if the application supports opening the file
  type being dragged.

  For example, if the user starts dragging a text file firefox and
  libreoffice writer should illuminate in addition to gedit.

  Another example is dragging a tarball; thunderbird should illuminate
  and if the tarball is dropped on the thunderbird icon it should open a
  new message with it as an attachment.

  
  UPDATE : Compiz screws up the handling when a drop happens at about the same 
time as the scale timeout goes off. It doesn't freeze so much as grab the mouse 
forever.


  
  -
  Desired resolution:

  - create a new desktop key that details all file types that can be
  imported into an application. See Robert Carr's comments #1 and #4 for
  details.

  - For the following applications, ensure the information about which
  file types can be opened by a drag and drop operation is updated:
  LibreOffice, Thunderbird, Chormium, Firefox, Gedit, Image viewer,
  Shotwell, GIMP, Transmission, Terminal, Brasero Disk Burner, Archive
  Manager, Evolution, Rhythembox, VLC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/764424/+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 1381050] Re: Import Key File fails when the path of the file has special characters

2014-10-20 Thread Bruno Nova
I finally found the cause of the problem!
It seems that the DBus service (or the whole DBus) is not running in a UTF-8 
locale, thus causing errors in UTF-8 strings.

The workaround is to edit softwareproperties/SoftwareProperties.py and add:
path = path.encode('utf-8')
in method def add_key(self, path) around line 800 before the line:
if not os.path.exists(path):

This encoding issue may be causing problems in other parts of the
program, and other programs.


Meanwhile, I found another bug:
Dragging and dropping a key file to the list doesn't work, raising an exception:
Traceback (most recent call last):
  File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
keydata = selection.data.strip()
AttributeError: 'SelectionData' object has no attribute 'data'

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

Title:
  Import Key File fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The Import Key File... button in the Authentication tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the /home/$USER/Downloads folder is 
named /home/$USER/Transferências here.
  Adding a key from that folder fails, but adding a key from /home/$USER (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_(Error importing selected file),
_(The selected file may not be a GPG key file 
  or it might be corrupt.))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error(Authentication canceled, changes have not 
been saved)

  self.backend.AddKey(chooser.get_filename()) throws a 
org.freedesktop.DBus.Python.UnicodeEncodeError exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-20 Thread Andras Muranyi
BTW not only Gnome Settings but also `pactl list` has the same info.
The right names are there too, however.

alsa.card = 0
alsa.card_name = PHASE 88 Rack FW
alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a
alsa.driver_name = snd_bebob
device.bus_path = pci-:01:09.0
sysfs.path = 
/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0
udev.id = firewire-0x000aac0300592827
device.bus = firewire
device.vendor.name = Texas Instruments
device.product.name = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]
device.string = 0
device.description = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]
module-udev-detect.discovered = 1
device.icon_name = audio-card-firewire
profiles:
input:10-channels: 10 Channels Input (priority 10, available: 
unknown)
output:10-channels: 10 Channels Output (priority 1000, 
available: unknown)
output:10-channels+input:10-channels: 10 Channels Output + 10 
Channels Input (priority 1010, available: unknown)

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

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use help for usage information.
   4 sink(s) available.
  [...]
  index: 2
name: alsa_output.firewire-0x000aac0300592827.10-channels
driver: module-alsa-card.c
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 alsa_card.firewire-0x000aac0300592827
module: 8
properties:
alsa.resolution_bits = 16
device.api = alsa
device.class = sound
alsa.class = generic
alsa.subclass = generic-mix
alsa.name = PHASE 88 Rack FW PCM
alsa.id = BeBoB
alsa.subdevice = 0
alsa.subdevice_name = subdevice #0
alsa.device = 0
alsa.card = 0
alsa.card_name = PHASE 88 Rack FW
alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a
alsa.driver_name = snd_bebob
device.bus_path = pci-:01:09.0
sysfs.path = 
/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0
udev.id = firewire-0x000aac0300592827
device.bus = firewire
device.vendor.name = Texas Instruments
device.product.name = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]
device.string = hw:0
device.buffering.buffer_size = 163840
device.buffering.fragment_size = 81920
device.access_mode = mmap+timer
device.profile.name = 10-channels
device.profile.description = 10 Channels
device.description = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels
alsa.mixer_name = PHASE 88 Rack FW
module-udev-detect.discovered = 1
device.icon_name = audio-card-firewire

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go 

[Touch-packages] [Bug 1067779] Re: missing pam_loginuid.so breaks getlogin()

2014-10-20 Thread Christian Kastner
3.0pl1-124.1ubuntu1 contains a fix for this.

** Changed in: cron (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  missing pam_loginuid.so breaks getlogin()

Status in “at” package in Ubuntu:
  Fix Committed
Status in “cron” package in Ubuntu:
  Fix Committed
Status in “openssh” package in Ubuntu:
  Fix Released
Status in “shadow” package in Ubuntu:
  Confirmed
Status in “at” package in Debian:
  Fix Released
Status in “cron” package in Debian:
  Fix Released
Status in “openssh” package in Debian:
  Fix Released
Status in “shadow” package in Debian:
  Fix Released

Bug description:
  getlogin() call in new glibc checks /proc/self/loginuid presence and
  trust its value as most safe source (due it's audit-related nature).
  But default /etc/pam.d/common-account doesn't contains entry to
  pam_loginuid.so which modify /proc/self/loginuid properly. This breaks
  getlogin() at many scenarios like this:

  (pam session without pam_loginuid)$  perl -e '$t=getlogin; print $t\n;'
  root
  (pam session without pam_loginuid)$  id
  uid=1000(...

  just because /proc/self/loginuid contains '0' value

  If I add pam_loginuid.so to /etc/pam.d/common-account like
  http://manpages.ubuntu.com/manpages/precise/man8/pam_loginuid.8.html
  recommend, everything worked as expected:

  (pam session with pam_loginuid)$  perl -e '$t=getlogin; print $t\n;'
  user
  (pam session with pam_loginuid)$  id
  uid=1000(...

  # cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION=Ubuntu 12.04 LTS

  # dpkg -l|fgrep libpam
  ii  libpam-ck-connector  0.4.5-2  
ConsoleKit PAM module
  ii  libpam-modules   1.1.3-7ubuntu2   
Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin   1.1.3-7ubuntu2   
Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime   1.1.3-7ubuntu2   
Runtime support for the PAM library
  ii  libpam0g 1.1.3-7ubuntu2   
Pluggable Authentication Modules library

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at/+bug/1067779/+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 1240198] Re: Wrong keyboard layout active after booting into desktop

2014-10-20 Thread Cheddie Merai
My problem was when I run gnome-shell --replace, the keyboard layout
changes fron UK to US.

I fixed it by following a
href=https://bugs.launchpad.net/ubuntu/+source/indicator-
keyboard/+bug/1240198Comment 19's fix./a

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

Title:
  Wrong keyboard layout active after booting into desktop

Status in “ibus” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged

Bug description:
  I upgraded from raring to saucy.

  After booting into the desktop (unity), the english keyboard layout is
  active, although everything on the system is set to be german
  (keyboard layout, language...)

  Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and
  changes the layout to the german layout.

  all the time, the new input settings indicator says the german layout
  is active.

  locale says: 
  LANG=de_DE.UTF-8
  LANGUAGE=de_DE
  LC_CTYPE=de_DE.UTF-8
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE=de_DE.UTF-8
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES=de_DE.UTF-8
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  /etc/default/keyboard says:
  # Check /usr/share/doc/keyboard-configuration/README.Debian for
  # documentation on what to do after having modified this file.

  # The following variables describe your keyboard and can have the same
  # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
  # in /etc/X11/xorg.conf.

  XKBMODEL=pc105
  XKBLAYOUT=de
  XKBVARIANT=
  XKBOPTIONS=

  # If you don't want to use the XKB layout on the console, you can
  # specify an alternative keymap.  Make sure it will be accessible
  # before /usr is mounted.
  # KMAP=/etc/console-setup/defkeymap.kmap.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:49:03 2013
  InstallationDate: Installed on 2013-04-26 (171 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: indicator-keyboard
  UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 1383144] [NEW] Apple devices won't unmount after they are unplugged, plugging in again causes windows to appear that don't respond to user input

2014-10-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Version: Linux Mint 17
What I did: I simply plugged in my iPhone to charge it and then unplugged it 
after Mint recognized it and the Autorun windows popped up. I then disconnected 
my iPhone and reconnected it later.
What happened: Well, a couple of things. First, when I unplugged, the Autorun 
windows disappeared, as expected. However, the real problem lies when I plug 
the phone back in. I plug it in and Mint tells me, Location is already 
mounted, and that window, along with the Autorun windows, will not go away. I 
have to restart my computer in order to make these windows go away, or remember 
to unmount the drive before disconnecting (which can be hard when using the 
computer simply for USB power).
What I expected to happen instead: I expected these windows not to show up and 
for the iPhone to unmount automatically when I disconnected it. There are two 
partitions (I guess they're partitions?) that should have unmounted upon 
disconnecting: The main partition and the Documents partition.
This problem always happens with the mentioned steps. It also happens with my 
iPod Touch.

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


** Tags: apple iphone ipod mount mounting unmount unmounting
-- 
Apple devices won't unmount after they are unplugged, plugging in again causes 
windows to appear that don't respond to user input
https://bugs.launchpad.net/bugs/1383144
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to libimobiledevice in Ubuntu.

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


[Touch-packages] [Bug 244250] Re: Spurious reboot notifications caused by libssl upgrades.

2014-10-20 Thread Marc Deslauriers
@khaled-blah: please file a new bug, you are not supposed to see reboot
notifications when openssl gets upgraded on a desktop system.

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

Title:
  Spurious reboot notifications caused by libssl upgrades.

Status in “openssl” package in Ubuntu:
  Fix Released

Bug description:
  The postinst script for libssl0.9.8 currently has a bug where it sends
  a reboot notifcation whenever libssl is configured.  So reconfiguring
  libssl0.9.8 or even just installing libssl0.9.8 will result in a
  reboot notification.  Sending of the reboot notification should
  definitely be moved inside the upgrading guard.  The correct fix is
  likely to move it inside a version comparison guard for particular
  important updates like Colin suggests below -- this is what every
  other standard package using notify-reboot-required does.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+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 1383144] Re: Apple devices won't unmount after they are unplugged, plugging in again causes windows to appear that don't respond to user input

2014-10-20 Thread Monsta
** Project changed: linuxmint = libimobiledevice (Ubuntu)

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

Title:
  Apple devices won't unmount after they are unplugged, plugging in
  again causes windows to appear that don't respond to user input

Status in “libimobiledevice” package in Ubuntu:
  New

Bug description:
  Version: Linux Mint 17
  What I did: I simply plugged in my iPhone to charge it and then unplugged it 
after Mint recognized it and the Autorun windows popped up. I then disconnected 
my iPhone and reconnected it later.
  What happened: Well, a couple of things. First, when I unplugged, the Autorun 
windows disappeared, as expected. However, the real problem lies when I plug 
the phone back in. I plug it in and Mint tells me, Location is already 
mounted, and that window, along with the Autorun windows, will not go away. I 
have to restart my computer in order to make these windows go away, or remember 
to unmount the drive before disconnecting (which can be hard when using the 
computer simply for USB power).
  What I expected to happen instead: I expected these windows not to show up 
and for the iPhone to unmount automatically when I disconnected it. There are 
two partitions (I guess they're partitions?) that should have unmounted upon 
disconnecting: The main partition and the Documents partition.
  This problem always happens with the mentioned steps. It also happens with my 
iPod Touch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1383144/+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 794141] Re: cron needs to re-lookup users when trying to run a job

2014-10-20 Thread Christian Kastner
** Changed in: cron (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  cron needs to re-lookup users when trying to run a job

Status in “cron” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: cron

  Please backport the fix for LP: #27520 to all supported releases. It
  breaks, among others, on lucid.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cron 3.0pl1-106ubuntu5
  ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16
  Uname: Linux 2.6.32-32-generic x86_64
  Architecture: amd64
  Date: Tue Jun  7 18:32:53 2011
  ProcEnviron:
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/794141/+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 934337] Re: cron truncates command before execution, gives no erro

2014-10-20 Thread Christian Kastner
*** This bug is a duplicate of bug 826702 ***
https://bugs.launchpad.net/bugs/826702

** This bug has been marked a duplicate of bug 826702
   crontab cuts off file names at 100 characters

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

Title:
  cron truncates command before execution, gives no erro

Status in “cron” package in Ubuntu:
  Confirmed

Bug description:
  cron truncates commands at 999 characters, then executes them, giving
  no errors or warnings.

  I'd prefer that cron NOT run the job, and instead throw an error.

  Much less important, it would be nice if the limit were increased.

  
  Worst case actually happened to me, rsync --del output directory got 
truncated just right, deleting lots of data.  That was fun to figure out.  
Length was due to many --excludes.

  I suspect that the truncation is related to the MAX_COMMAND value.

  As a test case, I created the job:

  * * * * * echo
  
a;
  date 
  
/home/darxus/tmp/a

  Which should create a file in /home/darxus/tmp/ 93 characters long,
  but truncates it at 72 characters long.

  rsync mailing list discussion: http://www.mail-
  archive.com/rs...@lists.samba.org/msg26564.html

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cron 3.0pl1-116ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8
  Uname: Linux 2.6.38-13-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Fri Feb 17 11:59:40 2012
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: Upgraded to natty on 2011-05-02 (290 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/934337/+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 872552] Re: Too long line in crontab isn't executed

2014-10-20 Thread Christian Kastner
*** This bug is a duplicate of bug 826702 ***
https://bugs.launchpad.net/bugs/826702

** This bug has been marked a duplicate of bug 826702
   crontab cuts off file names at 100 characters

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

Title:
  Too long line in crontab isn't executed

Status in “cron” package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 11.10 dev with cron 3.0pl1-116ubuntu3. Too long
  entries in a crontab seems to make problems. For example create the
  file /etc/cron.d/test and write in it:

  * * * * * root dash -c '/bin/sleep 1  /bin/sleep 1  /bin/sleep 1
   /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1 
  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1  /bin/sleep 1'

  The command should be executed every minute but it doesn't (or maybe
  it is executed and failing immediately). If the last sleep command is
  removed the cronjob is working fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/872552/+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 826702] Re: crontab cuts off file names at 100 characters

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

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

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

Title:
  crontab cuts off file names at 100 characters

Status in “cron” package in Ubuntu:
  Fix Committed

Bug description:
  The crontab command silently cuts off file names after 100 characters.
  This means that it won't work if you have a file with a path longer
  than 100 characters, and want to feed it into crontab. Example:

  
  $ crontab 
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_this_will_be_cut_off
  
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345678:
 No such file or directory

  
  This is due to a MAX_FNAME constant set to 100 characters in cron.h. I 
updated the code to use PATH_MAX instead. This will still cut off the paths, 
but at least after a more reasonable number of characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/826702/+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 826702] Re: crontab cuts off file names at 100 characters

2014-10-20 Thread Christian Kastner
A fix has been prepared that recognizes too long commands and produces
an error message when attempting to create one, both via crontab(1) and
cron(8). Furthermore, this limit has been documented in the man pages.

** Changed in: cron (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  crontab cuts off file names at 100 characters

Status in “cron” package in Ubuntu:
  Fix Committed

Bug description:
  The crontab command silently cuts off file names after 100 characters.
  This means that it won't work if you have a file with a path longer
  than 100 characters, and want to feed it into crontab. Example:

  
  $ crontab 
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_this_will_be_cut_off
  
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345678:
 No such file or directory

  
  This is due to a MAX_FNAME constant set to 100 characters in cron.h. I 
updated the code to use PATH_MAX instead. This will still cut off the paths, 
but at least after a more reasonable number of characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/826702/+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 826702] Re: crontab cuts off file names at 100 characters

2014-10-20 Thread Christian Kastner
In the mean time, this limit has been raised to 1000 chars.

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

Title:
  crontab cuts off file names at 100 characters

Status in “cron” package in Ubuntu:
  Fix Committed

Bug description:
  The crontab command silently cuts off file names after 100 characters.
  This means that it won't work if you have a file with a path longer
  than 100 characters, and want to feed it into crontab. Example:

  
  $ crontab 
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_this_will_be_cut_off
  
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345678:
 No such file or directory

  
  This is due to a MAX_FNAME constant set to 100 characters in cron.h. I 
updated the code to use PATH_MAX instead. This will still cut off the paths, 
but at least after a more reasonable number of characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/826702/+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 826702] Re: crontab cuts off file names at 100 characters

2014-10-20 Thread Ubuntu Foundations Team Bug Bot
The attachment vixiecron-pathmax.patch seems to be a patch.  If it
isn't, please remove the patch flag from the attachment, remove the
patch tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  crontab cuts off file names at 100 characters

Status in “cron” package in Ubuntu:
  Fix Committed

Bug description:
  The crontab command silently cuts off file names after 100 characters.
  This means that it won't work if you have a file with a path longer
  than 100 characters, and want to feed it into crontab. Example:

  
  $ crontab 
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_this_will_be_cut_off
  
_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_12345678:
 No such file or directory

  
  This is due to a MAX_FNAME constant set to 100 characters in cron.h. I 
updated the code to use PATH_MAX instead. This will still cut off the paths, 
but at least after a more reasonable number of characters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/826702/+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 1381050] Re: Import Key File fails when the path of the file has special characters

2014-10-20 Thread Bruno Nova
** Branch linked: lp:~brunonova/software-properties/lp1381050

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

Title:
  Import Key File fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The Import Key File... button in the Authentication tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the /home/$USER/Downloads folder is 
named /home/$USER/Transferências here.
  Adding a key from that folder fails, but adding a key from /home/$USER (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_(Error importing selected file),
_(The selected file may not be a GPG key file 
  or it might be corrupt.))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error(Authentication canceled, changes have not 
been saved)

  self.backend.AddKey(chooser.get_filename()) throws a 
org.freedesktop.DBus.Python.UnicodeEncodeError exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1383086] Re: rebooting defeats the screen lock timeout

2014-10-20 Thread Michael Zanetti
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Michael Terry (mterry)

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

Title:
  rebooting defeats the screen lock timeout

Status in “unity8” package in Ubuntu:
  New

Bug description:
  If you enable pin unlock, then repeatedly enter the incorrect pin,
  eventually you'll get a message stating that the phone cannot be
  unlocked for 5 minutes. However, this restriction can be trivially
  bypassed by simply rebooting the phone (which takes less than 5
  minutes :-)

  krillin, r117.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383086/+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 1383277] Re: Power dialog sometimes shown on resume

2014-10-20 Thread 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/1383277

Title:
  Power dialog sometimes shown on resume

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Unfortunately no good steps to reproduce, other than resume your
  phone, from time to time you'll get the power dialog displayed on
  screen.

  The reason for this could be twofold: a) you pressed the power button
  in your pocket b) input is confused and keyUp event does not reach
  unity8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383277/+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 1382621] Re: sim pin prompt on boot but after greeter

2014-10-20 Thread Michael Zanetti
I remember design requested this explicitly. The reason is that we don't
want the user to forget to enter the SIM PIN, leaving him with a locked
SIM and not being reachable for phone calls.

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

Title:
  sim pin prompt on boot but after greeter

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

Bug description:
  Per this bug 1382604

  it was discussed that the sim pin prompt is occuring before the
  greeter on boot, and doesn't seem to match the spec per this bug
  1333121

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382621/+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 1382182] Re: Pull to refresh doesn't make sense on apps scope

2014-10-20 Thread Michael Zanetti
*** This bug is a duplicate of bug 1378806 ***
https://bugs.launchpad.net/bugs/1378806

** This bug has been marked a duplicate of bug 1378806
   [Dash] Pull to refresh feels really odd in click scope

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

Title:
  Pull to refresh doesn't make sense on apps scope

Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Pull to refresh does not make sense for the click scope. The installed
  app grid is static and only gets updated when a new app is installed.
  We end up mistakenly doing a pull-to-refresh in the click scope which
  just shows the visually problematic reloading of icons.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity-scope-click 0.1.1+14.10.20141010-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: armhf
  Date: Thu Oct 16 23:58:14 2014
  InstallationDate: Installed on 2014-10-16 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141016-162207)
  SourcePackage: unity-scope-click
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382182/+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 1381050] Re: Import Key File fails when the path of the file has special characters

2014-10-20 Thread Bruno Nova
** Branch linked: lp:~brunonova/software-properties/lp1381050

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

Title:
  Import Key File fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The Import Key File... button in the Authentication tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the /home/$USER/Downloads folder is 
named /home/$USER/Transferências here.
  Adding a key from that folder fails, but adding a key from /home/$USER (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_(Error importing selected file),
_(The selected file may not be a GPG key file 
  or it might be corrupt.))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error(Authentication canceled, changes have not 
been saved)

  self.backend.AddKey(chooser.get_filename()) throws a 
org.freedesktop.DBus.Python.UnicodeEncodeError exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 985924] Re: Permission denied for custom entries in /etc/crontab

2014-10-20 Thread Christian Kastner
Closed as per submitter's request

** Changed in: cron (Ubuntu)
   Status: New = Invalid

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

Title:
  Permission denied for custom entries in /etc/crontab

Status in “cron” package in Ubuntu:
  Invalid

Bug description:
  Upon upgrade to Precise from Oneiric, my custom cron jobs stopped
  working.

  Custom entries in '/etc/crontab' result in these errors:

  Apr 19 14:59:01 hostname CRON[5898]: Permission denied
  Apr 19 14:59:01 hostname CRON[5899]: Permission denied

  Jobs in '/var/spool/cron/crontabs' are not executed either, but there
  are no error messages.

  I expected these jobs to run normally. Using full paths made no
  difference. The commands run manually.

  Description:  Ubuntu 12.04 LTS
  Release:  12.04

Installed: 3.0pl1-120ubuntu3
Candidate: 3.0pl1-120ubuntu3
Version table:
   *** 3.0pl1-120ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/985924/+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 1379836] Re: dialer and messaging app show unlocked pin as locked

2014-10-20 Thread Launchpad Bug Tracker
This bug was fixed in the package telepathy-ofono -
0.2+14.10.20141015-0ubuntu1

---
telepathy-ofono (0.2+14.10.20141015-0ubuntu1) 14.09; urgency=low

  [ Ubuntu daily release ]
  * New rebuild forced

  [ Tiago Salem Herrmann ]
  * Check if the SimManager interface is available and property not
empty before assuming the sim is locked. (LP: #1379836)
 -- Ubuntu daily release ps-jenk...@lists.canonical.com   Wed, 15 Oct 2014 
13:33:36 +

** Changed in: telepathy-ofono (Ubuntu RTM)
   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-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1379836

Title:
  dialer and messaging app show unlocked pin as locked

Status in Telepathy Ofono:
  In Progress
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “telepathy-ofono” package in Ubuntu:
  In Progress
Status in “telepathy-ofono” package in Ubuntu RTM:
  Fix Released

Bug description:
  Ubuntu System Settings and ofono say it's unlocked but trying to use
  the dialer and messaging app is blocked by thinking the PIN is locked.

  $ system-image-cli -i
  current build number: 81
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-10-10 15:33:48
  version version: 81
  version ubuntu: 20141010.1
  version device: 20140929.1
  version custom: mako-0.7

  $ phablet-shell 
  /home/sergiusens/.ssh/known_hosts updated.
  Original contents retained as /home/sergiusens/.ssh/known_hosts.old
  Warning: Permanently added '[localhost]:' (RSA) to the list of known 
hosts.
  Welcome to Ubuntu Utopic Unicorn (development branch) (GNU/Linux 3.4.0-5-mako 
armv7l)

   * Documentation:  https://help.ubuntu.com/
  Last login: Fri Oct 10 15:37:40 2014 from localhost.localdomain
  phablet@ubuntu-phablet:~$ lis^C
  phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems 
  [ /ril_0 ]
  Features = gprs ussd net sms rat sim 
  Model = Fake Modem Model
  Powered = 1
  Emergency = 0
  Online = 1
  Interfaces = org.ofono.ConnectionManager org.ofono.CallBarring 
org.ofono.CallSettings org.ofono.SupplementaryServices 
org.ofono.NetworkRegistration org.ofono.CallForwarding org.ofono.SmartMessaging 
org.ofono.PushNotification org.ofono.MessageManager org.ofono.NetworkTime 
org.ofono.MessageWaiting org.ofono.RadioSettings org.ofono.SimManager 
org.ofono.CallVolume org.ofono.VoiceCallManager 
  Revision = M9615A-CEFWMAZM-2.0.1701.03
  Type = hardware
  Manufacturer = Fake Manufacturer
  Serial = 355136052657866
  Lockdown = 0
  [ org.ofono.ConnectionManager ]
  Bearer = hspa
  RoamingAllowed = 0
  Suspended = 0
  Powered = 1
  Attached = 1
  [ org.ofono.CallBarring ]
  VoiceIncoming = disabled
  VoiceOutgoing = disabled
  [ org.ofono.CallSettings ]
  CallingLineRestriction = off
  HideCallerId = default
  ConnectedLinePresentation = unknown
  ConnectedLineRestriction = unknown
  CallingLinePresentation = enabled
  CallingNamePresentation = unknown
  CalledLinePresentation = disabled
  VoiceCallWaiting = enabled
  [ org.ofono.SupplementaryServices ]
  State = idle
  [ org.ofono.NetworkRegistration ]
  Mode = auto
  Name = Personal
  LocationAreaCode = 394
  Status = registered
  CellId = 14122637
  MobileCountryCode = 722
  Technology = umts
  Strength = 61
  MobileNetworkCode = 34
  [ org.ofono.CallForwarding ]
  VoiceNotReachable = +541151009255
  VoiceNoReplyTimeout = 25
  VoiceUnconditional = 
  VoiceNoReply = +541151009255
  ForwardingFlagOnSim = 0
  VoiceBusy = +541151009255
  [ org.ofono.SmartMessaging ]
  [ org.ofono.PushNotification ]
  [ org.ofono.MessageManager ]
  Alphabet = default
  UseDeliveryReports = 0
  ServiceCenterAddress = +541151740055
  Bearer = cs-preferred
  [ org.ofono.NetworkTime ]
  [ org.ofono.MessageWaiting ]
  VoicemailWaiting = 0
  VoicemailMailboxNumber = *555
  VoicemailMessageCount = 0
  [ org.ofono.RadioSettings ]
  TechnologyPreference = umts
  ModemTechnologies = gsm umts 
  FastDormancy = 0
  [ org.ofono.SimManager ]
  CardIdentifier = 89543421113404033941
  ServiceNumbers = [Llam. a su Cargo] = '11' [Club Personal] = 
'*2582' [Personal] = '+810' [At. Clientes] = '*111' 
  Retries = 
  FixedDialing = 0
  SubscriberIdentity = 722341240403394
  MobileCountryCode = 722
  BarredDialing = 0
  PinRequired = none
  LockedPins = 
  SubscriberNumbers = 
  Present = 1
  PreferredLanguages = es en pt it 

[Touch-packages] [Bug 1378806] Re: [Dash] Pull to refresh feels really odd in click scope

2014-10-20 Thread 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/1378806

Title:
  [Dash] Pull to refresh feels really odd in click scope

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Having a pull to refresh entry in the applications scope feels really
  wrong, given it shows only local content and should be up to date all
  the time anyways.

  It would be great to disable this feature for some local-only scopes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1378806/+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 1383279] Re: power button events queued, should probably be dropped

2014-10-20 Thread Michał Sawicz
** Package changed: unity8 (Ubuntu) = unity-system-compositor (Ubuntu)

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

Title:
  power button events queued, should probably be dropped

Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  Lock phone
  Repeatedly and rapidly press the power button.
  Wait
  Observe the screen blink on and off for some seconds after you finish 
pressing the power button.

  The presses after the first few should probably be dropped?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1383279/+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 1383208] Re: Manage Scopes does not display all scopes

2014-10-20 Thread Albert Astals Cid
** Also affects: unity-scopes-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Manage Scopes does not display all scopes

Status in “unity-scopes-shell” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu-rtm/14.09 r4 and ubuntu-rtm/14.09-proposed r100, bringing up
  the Manage Scopes view and tapping All does not display all
  installed scopes after install.  Only after a search or a reboot are
  additional scopes displayed as well.

  This occurs in unity8 8.00+14.10.20141017-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1383208/+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 1379366] Re: App names are not translated in preview

2014-10-20 Thread Rodney Dawes
** Also affects: unity-scope-click (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: unity-scope-click (Ubuntu RTM)
 Assignee: (unassigned) = Rodney Dawes (dobey)

** Changed in: unity-scope-click (Ubuntu RTM)
   Importance: Undecided = High

** Changed in: unity-scope-click (Ubuntu RTM)
   Status: New = In Progress

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

Title:
  App names are not translated in preview

Status in “unity-scope-click” package in Ubuntu:
  In Progress
Status in “unity-scope-click” package in Ubuntu RTM:
  In Progress

Bug description:
  So i am in the Ubuntu scope, long click on the Calculadora icon
  and get a preview that says Calculator.

  The description and stuff is also in English, but that makes some
  sense since it's free text, but the app name shoud be translated.

  Will attach the two screenshots.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1379366/+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 1383279] [NEW] power button events queued, should probably be dropped

2014-10-20 Thread Alan Pope
Public bug reported:

Lock phone
Repeatedly and rapidly press the power button.
Wait
Observe the screen blink on and off for some seconds after you finish pressing 
the power button.

The presses after the first few should probably be dropped?

** Affects: unity-system-compositor (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/1383279

Title:
  power button events queued, should probably be dropped

Status in “unity-system-compositor” package in Ubuntu:
  New

Bug description:
  Lock phone
  Repeatedly and rapidly press the power button.
  Wait
  Observe the screen blink on and off for some seconds after you finish 
pressing the power button.

  The presses after the first few should probably be dropped?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1383279/+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 1383213] [NEW] [Dash] Categorydropbox touch state

2014-10-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

A touch state is needed. Light grey colour, same as on the rest of the
UI.

** Affects: ubuntu-ux
 Importance: Medium
 Assignee: Estibaliz Landa Torres (estilanda)
 Status: New

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


** Tags: rtmvisualbugs
-- 
[Dash] Categorydropbox touch state
https://bugs.launchpad.net/bugs/1383213
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

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


[Touch-packages] [Bug 1383220] Re: [Dash] Open apps visual incorrect.

2014-10-20 Thread Michał Sawicz
** No longer affects: unity8

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

Title:
  [Dash] Open apps visual incorrect.

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  A touch estate is needed. Light grey colour, same as on the rest of
  the UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383220/+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 1383215] [NEW] [Dash] Ubuntu store card icon is not aligned and is missing a dark overlay

2014-10-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

A touch estate is needed. Light grey colour, same as on the rest of the
UI.

** Affects: ubuntu-ux
 Importance: Undecided
 Assignee: Estibaliz Landa Torres (estilanda)
 Status: New

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


** Tags: rtmvisualbugs
-- 
[Dash] Ubuntu store card icon is not aligned and is missing a dark overlay
https://bugs.launchpad.net/bugs/1383215
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to unity8 in Ubuntu.

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


[Touch-packages] [Bug 1383221] Re: [dash] Text alignment in Dash

2014-10-20 Thread Michał Sawicz
*** This bug is a duplicate of bug 1382470 ***
https://bugs.launchpad.net/bugs/1382470

** No longer affects: unity8

** This bug has been marked a duplicate of bug 1382470
   [Dash] Aligment of typography is wrong

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

Title:
  [dash] Text alignment in Dash

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  A touch estate is needed. Light grey colour, same as on the rest of
  the UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383221/+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 1382470] Re: [Dash] Aligment of typography is wrong

2014-10-20 Thread Michał Sawicz
** No longer affects: unity8

** Changed in: unity8 (Ubuntu)
   Status: New = Triaged

** Changed in: unity8 (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  [Dash] Aligment of typography is wrong

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  There should be 2 grid units space (margin) between the typography and the 
border.
  See attached screenshots for details

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1382470/+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 1383213] Re: [Dash] Categorydropbox touch state

2014-10-20 Thread Michał Sawicz
** Summary changed:

- [Dash] Categorydropbox touch estate
+ [Dash] Categorydropbox touch state

** Description changed:

- A touch estate is needed. Light grey colour, same as on the rest of the
+ A touch state is needed. Light grey colour, same as on the rest of the
  UI.

** Project changed: unity8 = unity8 (Ubuntu)

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

Title:
  [Dash] Categorydropbox touch state

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  A touch state is needed. Light grey colour, same as on the rest of the
  UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383213/+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 1383208] Re: Manage Scopes does not display all scopes

2014-10-20 Thread Niklas Wenzel
Also happens on ubuntu-rtm/14.09 r5.

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

Title:
  Manage Scopes does not display all scopes

Status in “unity-scopes-shell” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu-rtm/14.09 r4 and ubuntu-rtm/14.09-proposed r100, bringing up
  the Manage Scopes view and tapping All does not display all
  installed scopes after install.  Only after a search or a reboot are
  additional scopes displayed as well.

  This occurs in unity8 8.00+14.10.20141017-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1383208/+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 1382475] Re: [Dash] Margins typography

2014-10-20 Thread Michał Sawicz
*** This bug is a duplicate of bug 1382470 ***
https://bugs.launchpad.net/bugs/1382470

** No longer affects: unity8

** This bug has been marked a duplicate of bug 1382470
   [Dash] Aligment of typography is wrong

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

Title:
  [Dash] Margins typography

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  Typography should be aligned, all at the same distance from the edge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1382475/+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 1382078] Re: Revealed Indicators UI hides some indicators

2014-10-20 Thread Nick Dedekind
** Changed in: unity8 (Ubuntu)
   Status: Confirmed = In Progress

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

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

** Changed in: unity8 (Ubuntu RTM)
 Assignee: (unassigned) = Nick Dedekind (nick-dedekind)

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

Title:
  Revealed Indicators UI hides some indicators

Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  The new indicator panel code (correctly) honors the indicators'
  visible flag when deciding what to hide from the status bar.

  However, it also (incorrectly) honors this flag in the Revealed
  Indicators UI. The RTM Usability Fixes document lists that all of our
  indicators should be visible there, regardless of whether they're
  hidden in the status bar.

  IIUC this was one of the original goals of the redesign -- to
  declutter the status bar without losing access to the lesser
  indicators

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382078/+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 1381475] Re: Firewire sound card registered by the name of the fw controller

2014-10-20 Thread Takashi Sakamoto
Hi David,

 The ID_MODEL_FROM_DATABASE is probably set (for the firewire controller) by 
 udev/systemd,
 see the hwdb directory of systemd sources.

Exactly. I've already realized it and it require discussion between
ALSA, PulseAudio and systemd about which part of userspace has these
information for FireWire sound devices. This requires a batch of time so
I made it pending. Currently I would like to concentrate on my work for
ALSA kernel-land.

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

Title:
  Firewire sound card registered by the name of the fw controller

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  I am testing the new snd-firewire ALSA module which is currently getting 
accepted into the kernel.
  I have noticed that while ALSA recognizes the correct name for the card, 
PulseAudio displays another, wrong name, which is apparently the name of the 
FireWire controller through which the sound card is connected.

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM]
Subdevices: 1/1
Subdevice #0: subdevice #0

  $ pacmd list-sinks
  Welcome to PulseAudio! Use help for usage information.
   4 sink(s) available.
  [...]
  index: 2
name: alsa_output.firewire-0x000aac0300592827.10-channels
driver: module-alsa-card.c
flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: SUSPENDED
suspend cause: IDLE 
priority: 9000
volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 
8: 100% 9: 100%
0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 
dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
balance 0,00
base volume: 100%
 0,00 dB
volume steps: 65537
muted: no
current latency: 0,00 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 5
sample spec: s16le 10ch 44100Hz
channel map: 
front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1
used by: 0
linked by: 0
configured latency: 0,00 ms; range is 0,50 .. 185,76 ms
card: 3 alsa_card.firewire-0x000aac0300592827
module: 8
properties:
alsa.resolution_bits = 16
device.api = alsa
device.class = sound
alsa.class = generic
alsa.subclass = generic-mix
alsa.name = PHASE 88 Rack FW PCM
alsa.id = BeBoB
alsa.subdevice = 0
alsa.subdevice_name = subdevice #0
alsa.device = 0
alsa.card = 0
alsa.card_name = PHASE 88 Rack FW
alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW 
(id:3, rev:1), GUID 000aac0300592827 a
alsa.driver_name = snd_bebob
device.bus_path = pci-:01:09.0
sysfs.path = 
/devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0
udev.id = firewire-0x000aac0300592827
device.bus = firewire
device.vendor.name = Texas Instruments
device.product.name = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx]
device.string = hw:0
device.buffering.buffer_size = 163840
device.buffering.fragment_size = 81920
device.access_mode = mmap+timer
device.profile.name = 10-channels
device.profile.description = 10 Channels
device.description = TSB43AB22A IEEE-1394a-2000 Controller 
(PHY/Link) [iOHCI-Lynx] 10 Channels
alsa.mixer_name = PHASE 88 Rack FW
module-udev-detect.discovered = 1
device.icon_name = audio-card-firewire

  
  PulseAudio 1:4.0-0ubuntu11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+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 1383220] Re: [Dash] Open apps visual incorrect.

2014-10-20 Thread Michał Sawicz
The bug description seems to be completely unrelated? Is this design
final?

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

Title:
  [Dash] Open apps visual incorrect.

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  New

Bug description:
  A touch estate is needed. Light grey colour, same as on the rest of
  the UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383220/+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 1148594] Re: [12.04] crontab -e is not showing PATH in the example, so the example with tar will fail

2014-10-20 Thread Christian Kastner
The man page for crontab(5) states that PATH is initialized with
/usr/bin:/bin, so the tar invocation in the example is correct. Or did I
misunderstand your question?

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

Title:
  [12.04] crontab -e is not showing PATH in the example, so the example
  with tar will fail

Status in “cron” package in Ubuntu:
  New

Bug description:
  crontab -e is showing

  # 
  # Each task to run has to be defined through a single line
  # indicating with different fields when the task will be run
  # and what command to run for the task
  # 
  # To define the time you can provide concrete values for
  # minute (m), hour (h), day of month (dom), month (mon),
  # and day of week (dow) or use '*' in these fields (for 'any').# 
  # Notice that tasks will be started based on the cron's system
  # daemon's notion of time and timezones.
  # 
  # Output of the crontab jobs (including errors) is sent through
  # email to the user the crontab file belongs to (unless redirected).
  # 
  # For example, you can run a backup of all your user accounts
  # at 5 a.m every week with:
  # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
  # 
  # For more information see the manual pages of crontab(5) and cron(8)
  # 
  # m h  dom mon dow   command

  There is no line with PATH but in the example tar is used (instead of
  /bin/tar), so the example should be include PATH or /bin/tar instead
  of tar

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cron 3.0pl1-120ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Mar  6 06:01:04 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: Upgraded to precise on 2013-01-15 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1148594/+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 1383215] Re: [Dash] Ubuntu store card icon is not aligned and is missing a dark overlay

2014-10-20 Thread Michał Sawicz
How does that relate to this visual that we recently got to try and
implement?

https://drive.google.com/a/canonical.com/file/d/0B9e_psEGDNw0b1lqLU5ackZ3b0FQcVBGaVJKSDE3T05qZVpF/view

** Project changed: unity8 = unity8 (Ubuntu)

** Also affects: unity-scope-click (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/1383215

Title:
  [Dash] Ubuntu store card icon is not aligned and is missing a dark
  overlay

Status in Ubuntu UX bugs:
  New
Status in “unity-scope-click” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  A touch estate is needed. Light grey colour, same as on the rest of
  the UI.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383215/+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 1382596] Re: [Dash] Launcher home button (BFB) and pinned apps visuals incorrect

2014-10-20 Thread Michał Sawicz
The pinning indication you described conflicts with bug #1381054

** No longer affects: unity8

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

Title:
  [Dash] Launcher home button (BFB) and pinned apps visuals incorrect

Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  The orange button (home is incorrect (should have rounded corners) and
  the pinned apps should have a white dot on the top left, they
  shouldn´t be cut

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1382596/+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 1383283] [NEW] Видеокарта 63: проба на режим 800x600@60Hz с изход 1920x1080@60Hz

2014-10-20 Thread Кристиян
Public bug reported:

os -vmware worcstation guest ubunu

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
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
Date: Mon Oct 20 05:32:30 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2014-10-11 (8 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0471:032d Philips (or NXP) SPC 210NC PC Camera
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=bbaf7775-a595-444a-a59e-2067c8300bda ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, 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.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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Oct 20 05:30:06 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVMware VMware Virtual USB Mouse MOUSE, id 7
 inputgspca_zc3xx  KEYBOARD, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
 inputImPS/2 Generic Wheel Mouse MOUSE, id 10
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2 
   Virtual3Virtual4Virtual5Virtual6Virtual7 
   Virtual8
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: vmware

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

Title:
  Видеокарта 63: проба на режим 800x600@60Hz с изход 1920x1080@60Hz

Status in “xorg” package in Ubuntu:
  New

Bug description:
  os -vmware worcstation guest ubunu

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  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
  Date: Mon Oct 20 05:32:30 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2014-10-11 (8 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0471:032d Philips (or NXP) SPC 210NC PC Camera
   Bus 002 Device 003: ID 

[Touch-packages] [Bug 1382621] Re: sim pin prompt on boot but after greeter

2014-10-20 Thread Michał Sawicz
Hmm the linked bug does say immediately after boot, am I
misunderstanding something?

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

Title:
  sim pin prompt on boot but after greeter

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

Bug description:
  Per this bug 1382604

  it was discussed that the sim pin prompt is occuring before the
  greeter on boot, and doesn't seem to match the spec per this bug
  1333121

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382621/+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 1280808] Re: Support for afterwards execution of missing jobs

2014-10-20 Thread Christian Kastner
The feature you are describing is the exact purpose of anacron. Could
you elaborate what you mean by hasn't the precision of cron? What can
cron do that you can't do with /etc/anacrontab?

BTW, it doesn't make sense for anacron to be a full-time daemon, because
when the system is up, you already have the cron daemon executing your
jobs.

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

Title:
  Support for afterwards execution of missing jobs

Status in “cron” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 14.04 dev with cron 3.0pl1-124ubuntu2 and maybe cron
  can get the ability to run missing jobs on booting like anacron. The
  question why I'm not using anacron: It has limitations as it is not a
  full time deamon and hasn't the precision of cron. For example if I'm
  defining a job to run every day at 02:30 but the computer gets a power
  loss at 2:29 and is online at 2:31 it would be nice if cron does
  calculate on startup if there were jobs that had to be executed. For
  this case cron needs to store the last execution time of a job and an
  extra column on the job entry as option list to en-/disable this
  feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1280808/+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 1383085] Re: background in app carousel view does not show background image

2014-10-20 Thread Michał Sawicz
** Also affects: ubuntu-ux
   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/1383085

Title:
  background in app carousel view does not show background image

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  A swipe from the right edge of the phone towards the center fans out
  all the apps, showing a carousel-like view.

  However, the background is always black, whereas I would have expected
  the background to be the selected background image.

  Black is problematic since if one of the open apps is the camera, and
  the camera is face-down on a table for example, it will be showing a
  black image meaning that the camera app is presented as a pure black
  preview on a black background.

  krillin, r117.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1383085/+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 1313132] Re: Nautilus, Ubuntu 14.04 64 bit, Nautilus opens another window instead to use that window which is allready open

2014-10-20 Thread gevra
*** This bug is a duplicate of bug 1170647 ***
https://bugs.launchpad.net/bugs/1170647

The same here on the same 14.04 with 3.13.0-37.
Thanks to @ibrahim for well noticed detail about NTFS. I hadn't paid attention 
to this before.

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

Title:
  Nautilus,Ubuntu 14.04 64 bit, Nautilus opens another window instead to
  use that window which is allready open

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  Hey Ubuntu Team

  i Use Ubuntu 14.04 64 bit and my problem is if i open nautilus from
  Unity  and minimize + maximize

  nautilus within my home directory but if i minimize  maximize nautilus
  during i´ another partion it opens

  second  nautilus window instead to use the nautilus windows which is
  allready open/minimize + maximize

  1.Nautilus works fine if you want to use minimize or maximize  or get
  nautilus back to foreground

  2.Nautilus/file version is 3.10.1

  3.what i expect was if maximize nautilus/files again

  3.no  matter where that´s only open one window instead a seconde one

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 26 16:37:02 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']
  InstallationDate: Installed on 2014-04-24 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313132/+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 1383289] [NEW] Dropping a key into the list of keys fails

2014-10-20 Thread Bruno Nova
Public bug reported:

When I drag a key text/file and drop it into the list of keys in the
Authentication list, it fails silently (sometimes an apport bug report
appears), throwing an exception:

Traceback (most recent call last):
  File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
keydata = selection.data.strip()
AttributeError: 'SelectionData' object has no attribute 'data'

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: software-properties-gtk 0.92.37.1
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Oct 20 14:01:10 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-10-13 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  Authentication list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1383289/+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 1382466] Re: Greeter lock timeout can be reset by rebooting device

2014-10-20 Thread Michał Sawicz
*** This bug is a duplicate of bug 1383086 ***
https://bugs.launchpad.net/bugs/1383086

** This bug has been marked a duplicate of bug 1383086
   rebooting defeats the screen lock timeout

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

Title:
  Greeter lock timeout can be reset by rebooting device

Status in “ubuntu-system-settings” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  New

Bug description:
  14.09-proposed image #113

  STEPS:
  1. Ensure passphrase is set.
  2. Lock device.
  3. At locked greeter, attempt to unlock using incorrect passphrase 7 times 
until 'Device Locked' notice is displayed. This displays a 5 minute timeout 
before device can be unlocked again.
  4. Reboot device straight away.
  5. At locked greeter attempt to unlock device again.

  EXPECTED:
  The lock period should persist after reboot so it is not possible to unlock 
the device until the timeout period has expired.

  ACTUAL:
  The lock period is removed, so it is possible to unlock (or attempt to 
unlock) device immediately after reboot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1382466/+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 1367832] Comment bridged from LTC Bugzilla

2014-10-20 Thread bugproxy
--- Comment From emach...@br.ibm.com 2014-10-20 13:05 EDT---
Tested and verified as fixed with gdb 7.8-1ubuntu4.
Thanks.

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

Title:
  gdbserver gets conditionals wrong on ppc64le

Status in “gdb” package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  Single stepping has issues with conditionals when debugging with gdbserver, 
taking the wrong path through the code.
   
  Machine Type = Power8 LE 
   
  ---Steps to Reproduce---
   ubuntu@ubuntu:~$ cat  test.c
  #include stdio.h
  #include stdlib.h

  typedef enum {
Success = 0,
Failure,
  } dev_status_t;

  dev_status_t getDeviceCount(int *countp)
  { 
*countp = 1;
return Success;
  }

  int
  main(int argc, char **argv)
  { 
int count = 0;
dev_status_t status = getDeviceCount(count);

if (status != Success)
  { 
printf(getDeviceCount returned %d\n, (int)status);
printf(Result = FAIL\n);
exit(EXIT_FAILURE);
  }

if (count == 0)
  { 
printf(There are no devices\n);
  }
else
  { 
printf(Detected %d device(s)\n, count);
  }

exit(EXIT_SUCCESS);
  }

  ubuntu@ubuntu:~$ gcc -g test.c -o test
  ubuntu@ubuntu:~$ gdbserver : ./test
  Process ./test created; pid = 25600
  Listening on port 
  Remote debugging from host 127.0.0.1

  In another terminal, run gdb:

  ubuntu@ubuntu:~$ gdb ./test 
  GNU gdb (Ubuntu 7.8-0ubuntu1) 7.8
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  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 powerpc64le-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from ./test...done.
  (gdb) target remote :
  Remote debugging using :
  Reading symbols from /lib64/ld64.so.2...(no debugging symbols found)...done.
  Loaded symbols for /lib64/ld64.so.2
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  0x3fffb7fc1a60 in ?? () from /lib64/ld64.so.2
  (gdb) b main
  Breakpoint 1 at 0x16d4: file test.c, line 17.
  (gdb) cont
  Continuing.

  Breakpoint 1, main (argc=1, argv=0x3088) at test.c:17
  17  {
  (gdb) next
  18int count = 0;
  (gdb) next
  19dev_status_t status = getDeviceCount(count);
  (gdb) next
  21if (status != Success)
  (gdb) next
  23printf(getDeviceCount returned %d\n, (int)status);
  (gdb) print status
  $1 = Success

  Notice the program took the wrong direction on if() block.
   
  ---uname output---
  Linux ubuntu 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:45:12 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool common name: gdbserver

  The root cause of this issue was a routine that collect/supply ptrace
  registers on gdbserver, originally developed for BE only.

  The attached patch against gdb 7.8-0ubuntu1 sources fixes this problem
  on gdbserver. It was already accepted and committed upstream:

  https://sourceware.org/ml/gdb-patches/2014-09/msg00181.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1367832/+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 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope

2014-10-20 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  [scopes] Ubuntu button on launcher is hardcoded to click scope

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu button should bring the user to their first favorite scope,
  rather than always the click scope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 30 19:11:58 2014
  InstallationDate: Installed on 2013-04-26 (522 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+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 1383086] Re: rebooting defeats the screen lock timeout

2014-10-20 Thread Michał Sawicz
I think this was discussed and ACKed by security, the time needed to
reboot is enough to prevent any real bruteforcing of the password.

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

** Changed in: unity8 (Ubuntu)
 Assignee: Michael Terry (mterry) = (unassigned)

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

Title:
  rebooting defeats the screen lock timeout

Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  If you enable pin unlock, then repeatedly enter the incorrect pin,
  eventually you'll get a message stating that the phone cannot be
  unlocked for 5 minutes. However, this restriction can be trivially
  bypassed by simply rebooting the phone (which takes less than 5
  minutes :-)

  krillin, r117.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383086/+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 1381050] Re: Import Key File fails when the path of the file has special characters

2014-10-20 Thread Bruno Nova
Reported that other bug I mentioned in Bug #1383289.

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

Title:
  Import Key File fails when the path of the file has special
  characters

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  The Import Key File... button in the Authentication tab fails
  silently when the path of the selected key file includes special
  characters.

  I'm using Ubuntu in Portuguese, so the /home/$USER/Downloads folder is 
named /home/$USER/Transferências here.
  Adding a key from that folder fails, but adding a key from /home/$USER (no 
special characters) succeeds.

  The problem is that, in
  softwareproperties/gtk/SoftwarePropertiesGtk.py in method
  SoftwarePropertiesGtk.add_key_clicked() at around line 952:

  if res == Gtk.ResponseType.ACCEPT:
  try:
  if not self.backend.AddKey(chooser.get_filename()):
  error(self.window_main,
_(Error importing selected file),
_(The selected file may not be a GPG key file 
  or it might be corrupt.))
  except dbus.DBusException as e:
  if e._dbus_error_name == 
'com.ubuntu.SoftwareProperties.PermissionDeniedByPolicy':
  logging.error(Authentication canceled, changes have not 
been saved)

  self.backend.AddKey(chooser.get_filename()) throws a 
org.freedesktop.DBus.Python.UnicodeEncodeError exception for paths with 
special characters.
  This is probably a side effect of switching from Python 2 to 3 (and 'bytes' 
now being used in network communications where 'str' was previously used).

  Another issue is that the error isn't reported to the user, and it
  should be.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 14 13:22:21 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1381050/+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 1382267] Re: edges intro fails on rtm krillin 112

2014-10-20 Thread Michał Sawicz
** Branch linked: lp:~nick-dedekind/unity8/edges-demo-indicator-
improvements

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

Title:
  edges intro fails on rtm krillin 112

Status in “unity8” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu RTM:
  In Progress

Bug description:
  On rtm krillin image 112, the edges intro doesn't work.  After swiping
  down from the top to reveal an indicator menu, the bottom-edge
  tutorial overlay doesn't appear.  However, if I swipe it up anyway,
  the final edge overlay appears and I can proceed to use the device.
  Only one of the five overlays fails (right, top, bottom, left, tap...
  bottom fails).

  This worked in image 109.

  Update: Saviq reports it's also failing on 109.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1382267/+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 1376281] Comment bridged from LTC Bugzilla

2014-10-20 Thread bugproxy
--- Comment From emach...@br.ibm.com 2014-10-20 13:08 EDT---
Tested and verified as fixed with gdb 7.8-1ubuntu4.
Thanks.

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

Title:
  gdb: Can't read symbols from system-supplied DSO at 0x3fffb7fa:
  File truncated

Status in “gdb” package in Ubuntu:
  Fix Released

Bug description:
  ---Problem Description---
  GDB produces an odd message about a failure to read symbols from the system 
DSO when running executables on LE Ubuntu 14.10 with 3.16 kernel.  This is a 
regression from LE Ubuntu 14.04, where the message is not produced.

  Bad case:

  $ uname -r
  3.16.0-6-generic
  $ gdb /bin/ls
  GNU gdb (Ubuntu 7.7.91.20140723-0ubuntu1) 7.7.91.20140723-cvs
  ...
  (gdb) run
  Starting program: /bin/ls 
  Can't read symbols from system-supplied DSO at 0x3fffb7fa: File truncated
  ...
  [Inferior 1 (process 1573) exited normally]
  (gdb) 

  Note the Can't read symbols... message.

  Good case (LE Ubuntu 14.04):

  $ uname -r
  3.13.0-32-generic
  $ gdb /bin/ls
  GNU gdb (Ubuntu 7.7-0ubuntu3.2) 7.7
  ...
  (gdb) run
  Starting program: /bin/ls 
  ...
  [Inferior 1 (process 91140) exited normally]
  (gdb)

  I haven't tried on the 3.15 kernel, so I don't know if the problem is
  sensitve to the 3.16 kernel being ELFv2.

   
  ---uname output---
  Linux tul115p1 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 
ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8286-42A 
   
  ---Steps to Reproduce---
   See description; occurs when running any application under gdb.
   
  The failing output above is with the 3.16 kernel supplied by Ubuntu, so the 
problem happens both with locally-built and Canonical/Ubuntu-supplied kernels 
on 14.10.

  This issue was recently fixed on upstream binutils-gdb:

  https://sourceware.org/ml/gdb-patches/2014-09/msg00594.html

  The attached patch against gdb 7.8-0ubuntu1 for Ubuntu 14.10 fixes the
  issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1376281/+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 1316036] Re: cron package does not install MTA

2014-10-20 Thread Christian Kastner
Apparently the MTA dependency in Ubuntu's cron has been demoted from
Recommends (as it is in Debian), to a Suggests, so this bug should be
re-assigned to Ubuntu's installation documentation.

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

Title:
  cron package does not install MTA

Status in “cron” package in Ubuntu:
  New

Bug description:
  I just did a fresh install of trusty and deliberately made a failing
  entry in the crontab:

  * * * * * mkdir /qwer/qwer

  In /var/syslog, this results in:

  
  May  4 16:04:01 dekker CRON[2395]: (root) CMD (mkdir /qwer/qwer)
  May  4 16:04:01 dekker CRON[2394]: (CRON) info (No MTA installed, discarding 
output)

  When I look in the documentation (https://help.ubuntu.com/14.04
  /installation-guide/amd64/ch08s05.html), it says:

 For this reason the packages exim4 and mutt will be installed by
 default (provided you did not unselect the “standard” task during
 the installation). exim4 is a combination MTA/MDA that is relatively
 small but very flexible. By default it will be configured to only
 handle e-mail local to the system itself and e-mails addressed to
 the system administrator (root account) will be delivered to the
 regular user account created during the installation.

  Still, mutt and exim4 appear not to be installed, although I did not
  exclude or remove any packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cron 3.0pl1-124ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  5 09:52:04 2014
  InstallationDate: Installed on 2014-03-26 (39 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140325.1)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1316036/+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 1383289] Re: Dropping a key into the list of keys fails

2014-10-20 Thread Bruno Nova
** Summary changed:

- Dropping a key file into the list of keys fails
+ Dropping a key into the list of keys fails

** Description changed:

- When I drag a key file and drop it into the list of keys in the
+ When I drag a key text/file and drop it into the list of keys in the
  Authentication list, it fails silently (sometimes an apport bug report
  appears), throwing an exception:
  
  Traceback (most recent call last):
-   File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
- keydata = selection.data.strip()
+   File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
+ keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  Authentication list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1383289/+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 1277493] Re: MAILTO Environment Variable is ignored when set in a file in /etc/cron.d/

2014-10-20 Thread Christian Kastner
Could you check your MTA's log files (and /var/log/cron.*, if you have
it) for clues as to what could be going on? I just tried this locally
and it works fine: both mails are sent, and the MAILTO header is
included.

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

Title:
  MAILTO Environment Variable is ignored when set in a file in
  /etc/cron.d/

Status in “cron” package in Ubuntu:
  Confirmed

Bug description:
  I have a cron job definition file with the following:
  
  # Runs every 5 minutes, logging into the proftpd database checking for 
expired accounts and disabling them.
  MAILTO=sysadmin@[redacted].com,io@[redacted].com
  */5 *   * * *   root/usr/local/sbin/proftpd-expire.sh
  

  Any output from the script ought to be emailed to both the sysadmin  io 
group addresses, but instead output is always sent to 'root@[local FQDN]', 
presumably becasue the cron job is being executed as root. For some reason, the 
MAILTO environment variable is being ignored, as can be confirmed when looking 
at the email (sent to root) for all the X-cron-env headers:
  
  X-cron-env: SHELL=/bin/sh
  X-cron-env: HOME=/root
  X-cron-env: PATH=/usr/bin:/bin
  X-cron-env: LOGNAME=root
  
  There is clearly no MAILTO header in this email, and obviously the main proof 
is that this still only went to root@fqdn.

  All documentation appears to say that the combination of MAILTO and a
  file in /etc/cron.d/ should work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1277493/+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 1382039] Re: Apps scope empty on boot

2014-10-20 Thread Michał Sawicz
** Also affects: unity-scope-click (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Apps scope empty on boot

Status in “unity-scope-click” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Several people reported today that the apps scope came up empty on
  boot. A pull-to-refresh makes results come in again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1382039/+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 1148594] Re: [12.04] crontab -e is not showing PATH in the example, so the example with tar will fail

2014-10-20 Thread Michael Basse
Hi Christian,
i think it was my fault. I thought that the PATH should be in the file crontab 
-e is editing. As it seems cron itself is using the path somewhere because its 
definitely on in the crontab -e file

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

Title:
  [12.04] crontab -e is not showing PATH in the example, so the example
  with tar will fail

Status in “cron” package in Ubuntu:
  New

Bug description:
  crontab -e is showing

  # 
  # Each task to run has to be defined through a single line
  # indicating with different fields when the task will be run
  # and what command to run for the task
  # 
  # To define the time you can provide concrete values for
  # minute (m), hour (h), day of month (dom), month (mon),
  # and day of week (dow) or use '*' in these fields (for 'any').# 
  # Notice that tasks will be started based on the cron's system
  # daemon's notion of time and timezones.
  # 
  # Output of the crontab jobs (including errors) is sent through
  # email to the user the crontab file belongs to (unless redirected).
  # 
  # For example, you can run a backup of all your user accounts
  # at 5 a.m every week with:
  # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
  # 
  # For more information see the manual pages of crontab(5) and cron(8)
  # 
  # m h  dom mon dow   command

  There is no line with PATH but in the example tar is used (instead of
  /bin/tar), so the example should be include PATH or /bin/tar instead
  of tar

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cron 3.0pl1-120ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Mar  6 06:01:04 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: Upgraded to precise on 2013-01-15 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1148594/+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 1383086] Re: rebooting defeats the screen lock timeout

2014-10-20 Thread Michael Terry
This is relatively easy to fix -- need to just save the time we should
allow login again in a field.

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

Title:
  rebooting defeats the screen lock timeout

Status in “unity8” package in Ubuntu:
  Incomplete

Bug description:
  If you enable pin unlock, then repeatedly enter the incorrect pin,
  eventually you'll get a message stating that the phone cannot be
  unlocked for 5 minutes. However, this restriction can be trivially
  bypassed by simply rebooting the phone (which takes less than 5
  minutes :-)

  krillin, r117.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383086/+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 1383289] Re: Dropping a key into the list of keys fails

2014-10-20 Thread Bruno Nova
'SelectionData' has indeed no 'data' attribute. But it has a 'get_data()' 
method.
So, selection.data.strip() should be renamed to 
selection.get_data().strip() in 
softwareproperties/gtk/SoftwarePropertiesGtk.py (there are 2 occurrences).
Don't know if the bug exists in the KDE version.

But that doesn't fix everything. It will then throw these errors:
gpg: no writable keyring found: eof
gpg: error reading `/tmp/tmpcszfsj3q': general error
gpg: import from `/tmp/tmpcszfsj3q' failed: general error

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  Authentication list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1383289/+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 1148594] Re: [12.04] crontab -e is not showing PATH in the example, so the example with tar will fail

2014-10-20 Thread Christian Kastner
OK,  closing then. Thank you for your quick reply!

** Changed in: cron (Ubuntu)
   Status: New = Invalid

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

Title:
  [12.04] crontab -e is not showing PATH in the example, so the example
  with tar will fail

Status in “cron” package in Ubuntu:
  Invalid

Bug description:
  crontab -e is showing

  # 
  # Each task to run has to be defined through a single line
  # indicating with different fields when the task will be run
  # and what command to run for the task
  # 
  # To define the time you can provide concrete values for
  # minute (m), hour (h), day of month (dom), month (mon),
  # and day of week (dow) or use '*' in these fields (for 'any').# 
  # Notice that tasks will be started based on the cron's system
  # daemon's notion of time and timezones.
  # 
  # Output of the crontab jobs (including errors) is sent through
  # email to the user the crontab file belongs to (unless redirected).
  # 
  # For example, you can run a backup of all your user accounts
  # at 5 a.m every week with:
  # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
  # 
  # For more information see the manual pages of crontab(5) and cron(8)
  # 
  # m h  dom mon dow   command

  There is no line with PATH but in the example tar is used (instead of
  /bin/tar), so the example should be include PATH or /bin/tar instead
  of tar

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cron 3.0pl1-120ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Wed Mar  6 06:01:04 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: Upgraded to precise on 2013-01-15 (49 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1148594/+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 1383297] [NEW] Edge intro/demo redesign

2014-10-20 Thread Michael Terry
Public bug reported:

A while ago, Design gave me new visuals for the edge demo [1], but it
kept getting put off for other work.

I'm filing a bug here to help it not get forgotten and so it can be
assigned a priority.

[1] https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH-
8SsM1QyMmhWbkpRLTg

** Affects: unity8 (Ubuntu)
 Importance: Undecided
 Assignee: Michael Terry (mterry)
 Status: Triaged

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

Title:
  Edge intro/demo redesign

Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  A while ago, Design gave me new visuals for the edge demo [1], but it
  kept getting put off for other work.

  I'm filing a bug here to help it not get forgotten and so it can be
  assigned a priority.

  [1] https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH-
  8SsM1QyMmhWbkpRLTg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383297/+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 1378806] Re: [Dash] Pull to refresh feels really odd in click scope

2014-10-20 Thread Michael Terry
** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) = Michael Terry (mterry)

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

Title:
  [Dash] Pull to refresh feels really odd in click scope

Status in Ubuntu UX bugs:
  Triaged
Status in “unity8” package in Ubuntu:
  Confirmed

Bug description:
  Having a pull to refresh entry in the applications scope feels really
  wrong, given it shows only local content and should be up to date all
  the time anyways.

  It would be great to disable this feature for some local-only scopes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1378806/+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 1378462] Re: cannot reply to second notification

2014-10-20 Thread Nick Dedekind
** Changed in: unity8 (Ubuntu)
   Status: Triaged = In Progress

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

Title:
  cannot reply to second notification

Status in “indicator-messages” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  In Progress

Bug description:
  build 88, rtm on krillin

  - unlock the phone
  - make sure messaging-app is not running
  - send two sms messages to the phone
  - once they appear, open the messaging-menu
  - reply to the first message by clicking the message which makes it expand to 
reveal the send field
  - this works
  - attempt to reply to the second message by clicking the message to make it 
expand

  Expected results:
  the item should expand and allow you to send a message

  Actual results:
  the item cannot be expanded and you can't reply

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1378462/+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 1383289] Re: Dropping a key into the list of keys fails

2014-10-20 Thread Bruno Nova
Oh, before that there's another error:

Traceback (most recent call last):
  File 
/home/bruno/src/software-properties/software-properties/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 760, in on_auth_drag_data_received
if not self.add_key_from_data(keydata):
  File 
/home/bruno/src/software-properties/software-properties/softwareproperties/SoftwareProperties.py,
 line 815, in add_key_from_data
tmp.write(keydata.encode())
AttributeError: 'bytes' object has no attribute 'encode'

Just replace:
tmp.write(keydata.encode())
with:
tmp.write(keydata)
because keydata is already bytes at that point.

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

Title:
  Dropping a key into the list of keys fails

Status in “software-properties” package in Ubuntu:
  New

Bug description:
  When I drag a key text/file and drop it into the list of keys in the
  Authentication list, it fails silently (sometimes an apport bug
  report appears), throwing an exception:

  Traceback (most recent call last):
    File 
/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py,
 line 759, in on_auth_drag_data_received
  keydata = selection.data.strip()
  AttributeError: 'SelectionData' object has no attribute 'data'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: software-properties-gtk 0.92.37.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 20 14:01:10 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-10-13 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1383289/+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 1382039] Re: Apps scope empty on boot

2014-10-20 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
 Assignee: Michał Sawicz (saviq) = Albert Astals Cid (aacid)

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

Title:
  Apps scope empty on boot

Status in “unity-scope-click” package in Ubuntu:
  New
Status in “unity-scopes-shell” package in Ubuntu:
  Confirmed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  Several people reported today that the apps scope came up empty on
  boot. A pull-to-refresh makes results come in again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1382039/+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 1376044] Re: [scopes] Ubuntu button on launcher is hardcoded to click scope

2014-10-20 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) = Michael Zanetti (mzanetti)

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

Title:
  [scopes] Ubuntu button on launcher is hardcoded to click scope

Status in Ubuntu UX bugs:
  New
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  The Ubuntu button should bring the user to their first favorite scope,
  rather than always the click scope

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity8 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
  Uname: Linux 3.16.0-10-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 30 19:11:58 2014
  InstallationDate: Installed on 2013-04-26 (522 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1376044/+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 1333187] Re: [Dash] [design] Preview images display as black thumbnails

2014-10-20 Thread Michał Sawicz
** Changed in: unity8 (Ubuntu)
 Assignee: Michał Sawicz (saviq) = Andrea Cimitan (cimi)

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

Title:
  [Dash] [design] Preview images display as black thumbnails

Status in The Savilerow project:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in “unity8” package in Ubuntu:
  Triaged

Bug description:
  If the image is large, the Ubuntu shape rounded corners become very
  little, hardly noticable.

  REQUESTED UX SOLUTION
  Updated spec so images only zoomable once full screen.

  For all other instances of ubuntu shape, SDK documentation should be
  used (see link from Jouni in comments)

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1333187/+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 1103353] Re: Invalid GnuTLS cipher suite strings causes libldap to crash

2014-10-20 Thread Bug Watch Updater
** Changed in: openldap (Debian)
   Status: Confirmed = Fix Released

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

Title:
  Invalid GnuTLS cipher suite strings causes libldap to crash

Status in “openldap” package in Ubuntu:
  Triaged
Status in “openldap” package in Debian:
  Fix Released

Bug description:
  If the cipher suite string is unacceptable to GnuTLS, libldap_r-2.4
  crashes due to a double free. GnuTLS is extremely picky about the
  cipher suite strings it accepts; as a first measure, try LDAP cipher
  suite string SECURE256 or NORMAL. If that stops the crash, then
  you have encountered this bug.

  Typically, the crash report begins with something like

  *** glibc detected *** APPLICATION: double free or corruption (!prev)
  /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fc68cff0b96]
  /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x38769)[0x7fc68bb13769]
  /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x3570e)[0x7fc68bb1070e]
  
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_pvt_tls_init_def_ctx+0x1d)[0x7fc68bb108ed]
  /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35965)[0x7fc68bb10965]
  /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(+0x35a6d)[0x7fc68bb10a6d]
  
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2(ldap_int_tls_start+0x5d)[0x7fc68bb1149d]

  The actual double free happens in
  openldap/libraries/libldap/tls2.c:ldap_int_tls_init_ctx(), in the
  ldap_pvt_tls_ctx_free(lo-ldo_tls_ctx); call in the error_exit: path.

  The root cause of the double free is lack of GnuTLS return value
  checks when calling gnutls_priority*() functions. The code simply
  assumes they succeed, and when GnuTLS fails to provide a valid context
  due to those failures, ldap_int_tls_init_ctx() tries to free the
  never-fully-initialized context.

  A simple fix is to create GnuTLS security contexts using the
  configured cipher suite string, instead of NORMAL as
  openldap/libraries/libldap/tls_g.c now does. If the cipher suite
  string is invalid, then do not create the context at all. This is
  caught earlier in ldap_int_tls_init_ctx(), and avoids the crash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1103353/+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 1285951] Re: bluetooth indicator disappears after turning off bluetooth

2014-10-20 Thread Bhabba
I'm also on 14.04 and can confirm the behaviour Andre described in post
#4: If I turn off bluetooth the indicator disappears after the next
reboot. As long as bluetooth stays turned on the indicator remains
visible regardless of rebooting.

If bluetooth is turned off and the indicator is not visible I can
reactivate it through the system settings – but after the turning-on
bluetooth keeps being deactivated and only the indicator becomes visible
again (greyed out; regardless of how many times I try to activate it in
the system settings, the switch always rebounds)! At least I'm then able
to activate bluetooth again through the indicator.

Another bug I've noticed (I guess it's related to this one): If
bluetooth is deactivated but the indicator is visible (greyed out) and I
click on the switch to enable bluetooth visibility in the indicator
(without actually enabling bluetooth beforehand) the indicator crashes
(and disappears of course). Naturally it seems weird to turn visibility
on while bluetooth is actually disabled but it is still a bug! To
improve usability and consistency the visibility switch should be
inactive (i.e. greyed out) while the switch to enable bluetooth is
off.

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

Title:
  bluetooth indicator disappears after turning off bluetooth

Status in “indicator-bluetooth” package in Ubuntu:
  Invalid

Bug description:
  Although bug 1126108 is marked as Fix released, my indicator-
  bluetooth icon disappears after I use it to turn bluetooth off. See
  the attached animated gif.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-bluetooth 0.0.6+13.10.20131016-0ubuntu1
  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: Thu Feb 27 22:37:17 2014
  InstallationDate: Installed on 2013-01-12 (411 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: indicator-bluetooth
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (127 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1285951/+subscriptions

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


  1   2   3   >