[Touch-packages] [Bug 1198653] Re: It is not possible to drag & drop and pin icon to launch bar when auto-hiding is turned on

2015-02-02 Thread Andrea Azzarone
@Lukas please provide the output of:
apt-cache policy unity

Also are you using an hdpi monitor?

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

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

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

Title:
  It is not possible to drag & drop and pin icon to launch bar when
  auto-hiding is turned on

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

Bug description:
  When you have auto-hiding of launch bar turned on, you can not drag an
  application from search, because when you just put mouse with icon
  over the bar, it hides all the time and if you want to add it though,
  you have to disable auto-hiding first.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul  7 13:23:45 2013
  InstallationDate: Installed on 2013-06-20 (16 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.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/1198653/+subscriptions

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


[Touch-packages] [Bug 1417010] Re: systemd init gets stuck reloading smbd.service

2015-02-02 Thread Martin Pitt
Keeping notes:

> 50 network.target start waiting

This is another bug, because ifup@.service has Before=network.target.
That's too strict, and should be Before=network-online.target.

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

Title:
  systemd init gets stuck reloading smbd.service

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  since today (although haven't rebooted in a few days), systemd init is
  hanging trying to bring up ifup@eth0. I had to revert to upstart boot
  to get in, although sometimes it would successfully boot with systemd
  .debug-shell

  JOB UNIT TYPE  STATE  
  120 winbind.service  start waiting
  175 nmbd.service start waiting
  159 libvirt-bin.service  start waiting
  151 dns-clean.servicestart waiting
  116 vmware-workstation-server.servicestart waiting
  177 smbd.service start waiting
  178 fail2ban.service start waiting
  331 rpcbind.service  start waiting
  109 apache2.service  start waiting
  124 openvpn.service  start waiting
  184 x-display-manager.target start waiting
  173 vmware.service   start waiting
  143 getty@tty1.service   start waiting
  141 samba-ad-dc.service  start waiting
2 multi-user.targetstart waiting
  332 rpcbind.target   start waiting
  108 hddtemp.service  start waiting
  172 plymouth-quit-wait.service   start waiting
  152 autofs.service   start waiting
  123 schroot.service  start waiting
  130 mail-transport-agent.target  start waiting
  129 postfix.service  start waiting
  128 isc-dhcp-server.service  start waiting
  131 mysql.servicestart waiting
  142 getty.target start waiting
  164 sabnzbdplus.service  start waiting
1 graphical.target start waiting
  176 apt-cacher-ng.servicestart waiting
  183 gdm.service  start waiting
  174 ssh.service  start waiting
   77 network-online.targetstart waiting
  112 systemd-update-utmp-runlevel.service start waiting
  133 urfkill.service  start waiting
  111 kerneloops.service   start waiting
  161 rc-local.service start waiting
  106 lxc.service  start waiting
  107 lxc-net.service  start waiting
  155 virtualbox.service   start waiting
  191 ifup@eth0.servicestart running
   50 network.target   start waiting

  40 jobs listed.
  * ifup@eth0.service - ifup for eth0
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: activating (start-post) since Mon 2015-02-02 19:17:25 AEDT; 9min 
ago
Process: 800 ExecStart=/sbin/ifup --allow=hotplug %I (code=exited, 
status=0/SUCCESS)
   Main PID: 800 (code=exited, status=0/SUCCESS); : 803 (ifup)
 CGroup: /system.slice/system-ifup.slice/ifup@eth0.service
 `-control
   |- 803 /sbin/ifup --allow=auto eth0
   |- 832 /bin/sh -c dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0  
   |- 833 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
   |-1269 /bin/sh /sbin/dhclient-script
   |-1273 /bin/sh /usr/sbin/invoke-rc.d smbd reload
   `-1294 systemctl reload smbd.service

  Feb 02 19:17:25 duhast dhclient[833]: Sending on   Socket/fallback
  Feb 02 19:17:25 duhast dhclient[833]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:25 duhast ifup[803]: Listening on LPF/eth0/1c:6f:65:c4:63:1b
  Feb 02 19:17:25 duhast ifup[803]: Sending on   LPF/eth0/1c:6f:65:c4:63:1b
  Feb 02 19:17:25 duhast ifup[803]: Sending on   Socket/fallback
  Feb 02 19:17:25 duhast ifup[803]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast dhclient[833]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast ifup[803]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast dhclient[833]: DHCPACK of 192.168.15.67 from 
192.168.15.1
  Feb 02 19:17:28 duhast ifup[803]: DHCPACK of 192.168.15.67 from 192.168.15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-6ubuntu1
  Pr

[Touch-packages] [Bug 1417010] Re: systemd init gets stuck reloading smbd.service

2015-02-02 Thread Tim
journalctl debug logs from hang

** Attachment added: "logs"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1417010/+attachment/4310992/+files/logs

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

Title:
  systemd init gets stuck reloading smbd.service

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  since today (although haven't rebooted in a few days), systemd init is
  hanging trying to bring up ifup@eth0. I had to revert to upstart boot
  to get in, although sometimes it would successfully boot with systemd
  .debug-shell

  JOB UNIT TYPE  STATE  
  120 winbind.service  start waiting
  175 nmbd.service start waiting
  159 libvirt-bin.service  start waiting
  151 dns-clean.servicestart waiting
  116 vmware-workstation-server.servicestart waiting
  177 smbd.service start waiting
  178 fail2ban.service start waiting
  331 rpcbind.service  start waiting
  109 apache2.service  start waiting
  124 openvpn.service  start waiting
  184 x-display-manager.target start waiting
  173 vmware.service   start waiting
  143 getty@tty1.service   start waiting
  141 samba-ad-dc.service  start waiting
2 multi-user.targetstart waiting
  332 rpcbind.target   start waiting
  108 hddtemp.service  start waiting
  172 plymouth-quit-wait.service   start waiting
  152 autofs.service   start waiting
  123 schroot.service  start waiting
  130 mail-transport-agent.target  start waiting
  129 postfix.service  start waiting
  128 isc-dhcp-server.service  start waiting
  131 mysql.servicestart waiting
  142 getty.target start waiting
  164 sabnzbdplus.service  start waiting
1 graphical.target start waiting
  176 apt-cacher-ng.servicestart waiting
  183 gdm.service  start waiting
  174 ssh.service  start waiting
   77 network-online.targetstart waiting
  112 systemd-update-utmp-runlevel.service start waiting
  133 urfkill.service  start waiting
  111 kerneloops.service   start waiting
  161 rc-local.service start waiting
  106 lxc.service  start waiting
  107 lxc-net.service  start waiting
  155 virtualbox.service   start waiting
  191 ifup@eth0.servicestart running
   50 network.target   start waiting

  40 jobs listed.
  * ifup@eth0.service - ifup for eth0
 Loaded: loaded (/lib/systemd/system/ifup@.service; static; vendor preset: 
enabled)
 Active: activating (start-post) since Mon 2015-02-02 19:17:25 AEDT; 9min 
ago
Process: 800 ExecStart=/sbin/ifup --allow=hotplug %I (code=exited, 
status=0/SUCCESS)
   Main PID: 800 (code=exited, status=0/SUCCESS); : 803 (ifup)
 CGroup: /system.slice/system-ifup.slice/ifup@eth0.service
 `-control
   |- 803 /sbin/ifup --allow=auto eth0
   |- 832 /bin/sh -c dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0  
   |- 833 dhclient -1 -v -pf /run/dhclient.eth0.pid -lf 
/var/lib/dhcp/dhclient.eth0.leases eth0
   |-1269 /bin/sh /sbin/dhclient-script
   |-1273 /bin/sh /usr/sbin/invoke-rc.d smbd reload
   `-1294 systemctl reload smbd.service

  Feb 02 19:17:25 duhast dhclient[833]: Sending on   Socket/fallback
  Feb 02 19:17:25 duhast dhclient[833]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:25 duhast ifup[803]: Listening on LPF/eth0/1c:6f:65:c4:63:1b
  Feb 02 19:17:25 duhast ifup[803]: Sending on   LPF/eth0/1c:6f:65:c4:63:1b
  Feb 02 19:17:25 duhast ifup[803]: Sending on   Socket/fallback
  Feb 02 19:17:25 duhast ifup[803]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast dhclient[833]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast ifup[803]: DHCPREQUEST of 192.168.15.67 on eth0 to 
255.255.255.255 port 67 (xid=0x502572c4)
  Feb 02 19:17:28 duhast dhclient[833]: DHCPACK of 192.168.15.67 from 
192.168.15.1
  Feb 02 19:17:28 duhast ifup[803]: DHCPACK of 192.168.15.67 from 192.168.15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 218-6ubuntu1
  ProcVersionSignature: Ubun

[Touch-packages] [Bug 1198653] Re: It is not possible to drag & drop and pin icon to launch bar when auto-hiding is turned on

2015-02-02 Thread Stephen M. Webb
** Changed in: unity
   Importance: Undecided => Medium

** Changed in: unity
   Status: Expired => Confirmed

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

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

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

Title:
  It is not possible to drag & drop and pin icon to launch bar when
  auto-hiding is turned on

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

Bug description:
  When you have auto-hiding of launch bar turned on, you can not drag an
  application from search, because when you just put mouse with icon
  over the bar, it hides all the time and if you want to add it though,
  you have to disable auto-hiding first.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul  7 13:23:45 2013
  InstallationDate: Installed on 2013-06-20 (16 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.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/1198653/+subscriptions

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


[Touch-packages] [Bug 1417297] Re: [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at all

2015-02-02 Thread Raymond
Simple mixer control 'Speaker',0
  Capabilities: pvolume pswitch
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 74
  Mono:
  Front Left: Playback 0 [0%] [-9.99dB] [off]
  Front Right: Playback 0 [0%] [-9.99dB] [off]


control.21 {
iface CARD
name 'Dock Headphone Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.22 {
iface CARD
name 'Headphone Jack'
value true
comment {
access read
type BOOLEAN
count 1
}


active profile: 
sinks:
alsa_output.pci-_00_1b.0.analog-stereo/#4: Built-in Audio 
Analogue Stereo
sources:
alsa_input.pci-_00_1b.0.analog-stereo/#1: Built-in Audio 
Analogue Stereo
alsa_output.pci-_00_1b.0.analog-stereo.monitor/#5: Monitor 
of Built-in Audio Analogue Stereo
ports:
analog-input-microphone-internal: Internal Microphone (priority 
8900, latency offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-input-microphone"
analog-input-microphone-dock: Dock Microphone (priority 7800, 
latency offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-microphone: Microphone (priority 8700, latency 
offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-output-speaker: Speakers (priority 1, latency offset 
0 usec, available: no)
properties:
device.icon_name = "audio-speakers"
analog-output-headphones: Headphones (priority 9000, latency 
offset 0 usec, available: yes)
properties:
device.icon_name = "audio-headphones"
iec958-stereo-output: Digital Output (S/PDIF) (priority 0, 
latency offset 0 usec, available: unknown)
properties:



speaker is muted when headphone is plugged


** Changed in: alsa-driver (Ubuntu)
   Status: New => Incomplete

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

Title:
  [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  No sound at all after the installation of ubuntu 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tanvi  1963 F pulseaudio
  Date: Mon Feb  2 22:17:21 2015
  InstallationDate: Installed on 2015-02-02 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tanvi  1963 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VET82WW (3.12 )
  dmi.board.name: 2768GP6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VET82WW(3.12):bd01/12/2010:svnLENOVO:pn2768GP6:pvrThinkPadR400:rvnLENOVO:rn2768GP6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2768GP6
  dmi.product.version: ThinkPad R400
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1296133] Re: Suspend and hibernate missing from KMenu and Power Management in System settings

2015-02-02 Thread randyyang
FWIW. This solved my issue. 
https://www.kubuntuforums.net/showthread.php?64800-Unable-to-contact-KDED/page3&s=74ff58b7ae099185c514987936844a7f

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

Title:
  Suspend and hibernate missing from KMenu and Power Management in
  System settings

Status in upower package in Ubuntu:
  Invalid

Bug description:
  I have used install scripts to install Kubuntu 14.04 on three
  completely different systems. Although the packages installed are
  basically the same, one of the system has no Suspend/hibernate options
  in the KMenu nor in the Power management in the KDE System settings.
  Since this is a laptop, this also means that the battery life is
  greatly reduced, because it cannot go to standby when lid is closed or
  when it's idle. Interestingly, If I logout,  there is a Standby button
  on the lighdm login screen. If I click it, the laptop goes to standby
  and wakes up without problems.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upower 0.9.23-2ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 22 21:18:53 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-03-14 (8 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 
(20140130)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1296133/+subscriptions

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


[Touch-packages] [Bug 1133162] Re: video does not recover after suspend with nouveau driver

2015-02-02 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  video does not recover after suspend with nouveau driver

Status in xorg package in Ubuntu:
  Expired

Bug description:
  When running 12.04.2 with the nouveau driver, the system (X) does not
  recover after suspend and the system eventually freezes.

  The machine starts to recover from suspend, however, the screen
  remains black, or in one case, became a weird black and white zig-zag
  pattern with a mouse pointer visible.  At this point, the machine
  churns for a bit then completely freezes, requiring a power-cycle to
  return to a working state.

  Installing the nVidia proprietary driver resolves this issue:
  ii  nvidia-common1:0.2.44.2   
Find obsolete NVIDIA drivers
  ii  nvidia-current-updates   304.64-0ubuntu0.2
NVIDIA binary Xorg driver, kernel module and VDPAU library

  Using that as a workaround, I am able to suspend and resume this
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xserver-xorg-video-nouveau-lts-quantal 1:1.0.2-0ubuntu3~precise2
  ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2
  Uname: Linux 3.5.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Tue Feb 26 02:22:24 2013
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau-lts-quantal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1133162/+subscriptions

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


[Touch-packages] [Bug 1198653] Re: It is not possible to drag & drop and pin icon to launch bar when auto-hiding is turned on

2015-02-02 Thread Launchpad Bug Tracker
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  It is not possible to drag & drop and pin icon to launch bar when
  auto-hiding is turned on

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  When you have auto-hiding of launch bar turned on, you can not drag an
  application from search, because when you just put mouse with icon
  over the bar, it hides all the time and if you want to add it though,
  you have to disable auto-hiding first.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul  7 13:23:45 2013
  InstallationDate: Installed on 2013-06-20 (16 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.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/1198653/+subscriptions

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


[Touch-packages] [Bug 1198653] Re: It is not possible to drag & drop and pin icon to launch bar when auto-hiding is turned on

2015-02-02 Thread Launchpad Bug Tracker
[Expired for Unity because there has been no activity for 60 days.]

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

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

Title:
  It is not possible to drag & drop and pin icon to launch bar when
  auto-hiding is turned on

Status in Unity:
  Expired
Status in unity package in Ubuntu:
  Expired

Bug description:
  When you have auto-hiding of launch bar turned on, you can not drag an
  application from search, because when you just put mouse with icon
  over the bar, it hides all the time and if you want to add it though,
  you have to disable auto-hiding first.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Jul  7 13:23:45 2013
  InstallationDate: Installed on 2013-06-20 (16 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.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/1198653/+subscriptions

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


[Touch-packages] [Bug 1222637] Re: [nVidia GTX645][10de:11c4] System is extremely slow after resume from suspend with nouveau driver

2015-02-02 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [nVidia GTX645][10de:11c4] System is extremely slow after resume from
  suspend with nouveau driver

Status in xorg package in Ubuntu:
  Expired

Bug description:
  CID: 201303-13031 Dell Alienware X51

  System become very slow after resume from suspend with nouveau  driver
  (version 1.0.7).

  Steps:
  1. Boot to desktop, and suspend the system.
  2. Press the power button to wake it up.

  Expected results:
  1. System successfully suspended.
  2. System works normally after resume from suspend.

  Actual results:
  1. System successfully suspended.
  2. System successfuly wake up from suspend, but very laggy.

  I'll update this bug after this system was tested with the proprietary
  video driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 [modified: 
boot/vmlinuz-3.8.0-29-generic]
  ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  Date: Sun Sep  8 23:30:39 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  Package: xserver-xorg-video-nouveau-lts-raring 1:1.0.7-0ubuntu1~precise1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5
  Tags:  precise running-unity
  Uname: Linux 3.8.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1222637/+subscriptions

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


[Touch-packages] [Bug 1417370] [NEW] Qt 5 uses grayscale instead of subpixel font antialiasing

2015-02-02 Thread Brian Marshall
Public bug reported:

Qt 5 applications like Qt Creator or the Ubuntu web browser (webbrowser-
app) use grayscale font antialiasing. GTK 3, GTK 2, and Qt 4 use
subpixel antialiasing as expected, so fonts in Qt 5 look weird. Attached
screenshot shows an example of the problem.

This upstream bug report might be related:
https://bugreports.qt.io/browse/QTBUG-36445

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libqt5gui5 5.2.1+dfsg-1ubuntu14.2
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  2 19:35:10 2015
InstallationDate: Installed on 2014-08-30 (156 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

** Attachment added: "Screenshot comparing Qt 5 and GTK 3 font antialiasing."
   
https://bugs.launchpad.net/bugs/1417370/+attachment/4310929/+files/Qt%205%20Font%20Antialiasing.png

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

Title:
  Qt 5 uses grayscale instead of subpixel font antialiasing

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

Bug description:
  Qt 5 applications like Qt Creator or the Ubuntu web browser
  (webbrowser-app) use grayscale font antialiasing. GTK 3, GTK 2, and Qt
  4 use subpixel antialiasing as expected, so fonts in Qt 5 look weird.
  Attached screenshot shows an example of the problem.

  This upstream bug report might be related:
  https://bugreports.qt.io/browse/QTBUG-36445

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libqt5gui5 5.2.1+dfsg-1ubuntu14.2
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Feb  2 19:35:10 2015
  InstallationDate: Installed on 2014-08-30 (156 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1417370/+subscriptions

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


[Touch-packages] [Bug 1153389] Re: "no codecs initialized"

2015-02-02 Thread Raymond
https://bugzilla.kernel.org/show_bug.cgi?id=24052

you have to follow up the up stream bug report

** Bug watch added: Linux Kernel Bug Tracker #24052
   http://bugzilla.kernel.org/show_bug.cgi?id=24052

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

Title:
  "no codecs initialized"

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on a new computer (samsung all-in-one), and on a live ubuntu disk
  12.04 x64, my sound card is not detected.

  I have checked many forums for several months and cannot find the fix.

  I have two sound cards, motherboard and hdmi. Only the hdmi gets
  detected by alsa. It is not good as I am only using the motherboard
  one.

  The dmesg shows "no codecs initialized" for the first card.

  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  ubuntu@ubuntu:~$ lspci | grep -i audio
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
  01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Caicos HDMI Audio 
[Radeon HD 6400 Series]

  ubuntu@ubuntu:~$ dmesg | grep -i hda-intel
  [   97.691334] hda-intel: azx_get_response timeout, switching to polling 
mode: last cmd=0x000f
  [   98.692766] hda-intel: No response from codec, disabling MSI: last 
cmd=0x000f
  [   99.694197] hda-intel: Codec #0 probe error; disabling it...
  [  100.731901] hda-intel: no codecs initialized
  [  100.732057] hda-intel: :01:00.1: Handle VGA-switcheroo audio client

  The same happens on other debian linux distributions. Before I change
  my distribution to ubuntu, I would like to make sure the sound can
  work on ubuntu.

  Happy to help debugging this if necessary.

  Many thanks in advance.

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

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


[Touch-packages] [Bug 1386840] Re: failure to start a container

2015-02-02 Thread Felipe Reyes
** Changed in: lxc (Ubuntu Trusty)
 Assignee: (unassigned) => Felipe Reyes (freyes)

** Changed in: lxc (Ubuntu Utopic)
 Assignee: (unassigned) => Felipe Reyes (freyes)

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

Title:
  failure to start a container

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Confirmed
Status in lxc source package in Utopic:
  Confirmed

Bug description:
  On utopic using lxc version 1.1.0~alpha2-0ubuntu3, I was unable to
  start a container.

  $ sudo lxc-start -F -n lxc-errors
  lxc-start: lsm/apparmor.c: mount_feature_enabled: 61 Permission denied - 
Error mounting securityfs
  lxc-start: lsm/apparmor.c: apparmor_process_label_set: 186 If you really want 
to start this container, set
  lxc-start: lsm/apparmor.c: apparmor_process_label_set: 187 
lxc.aa_allow_incomplete = 1
  lxc-start: lsm/apparmor.c: apparmor_process_label_set: 188 in your container 
configuration file
  lxc-start: sync.c: __sync_wait: 51 invalid sequence number 1. expected 4
  lxc-start: start.c: __lxc_start: 1087 failed to spawn 'lxc-errors'
  lxc-start: cgmanager.c: cgm_remove_cgroup: 503 call to cgmanager_remove_sync 
failed: invalid request
  lxc-start: cgmanager.c: cgm_remove_cgroup: 505 Error removing 
name=systemd:lxc/lxc-errors-2

  Switching to the version of lxc in http://ppa.launchpad.net/ubuntu-
  lxc/daily/ resolved the failure to start for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1386840/+subscriptions

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


[Touch-packages] [Bug 1417341] Re: Empty contact list should provide way to sync contacts

2015-02-02 Thread Renato Araujo Oliveira Filho
@Olga, could you provide me some visuals for that?

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

Title:
  Empty contact list should provide way to sync contacts

Status in Address Book App:
  New
Status in the base for Ubuntu mobile products:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Ubuntu UX bugs:
  New
Status in address-book-app package in Ubuntu:
  New
Status in address-book-app package in Ubuntu RTM:
  New

Bug description:
  From usability tests:
  Contacts' view on the dialer does not have instruction for empty state, and 
as a result, testers struggled to know how to import the contacts. 

  Some testers went to the dialer, wanting to sync the contacts so that
  they could make a phone call. They clicked on the 'Contacts' icon, but
  there was no empty state instruction, apart from an empty screen with
  '+add a contact'. One of the tesers had to manually put the contacts
  in. It took him three days to finally figure out how to sync the
  contacts.

  As discussed, if the contact list is empty we should display a message
  in the list with a button to setup Google account, similar to how it's
  done in the address book app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1417341/+subscriptions

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


[Touch-packages] [Bug 1417359] [NEW] make swipe to reveal more discoverable

2015-02-02 Thread Bill Filler
Public bug reported:

on all the apps that use it (dialer, messaging, address book), we need a
way to make the swipe to reveal action more discoverable.

This was listed in usability testing:
messaging-app: Swipe to reveal 'copy' and 'info' options had poor 
discoverability
dialer-app: message or see the contact information

Suggestions:
- small arrows (< on left side and > on right side) of the list item to inform 
users that there are actions to be taken
- first time tutorial when the list is empty or when it's populated with first 
item showing an overlay of how to swipe to reveal more actions

** Affects: dialer-app
 Importance: High
 Assignee: Renato Araujo Oliveira Filho (renatofilho)
 Status: New

** Affects: messaging-app
 Importance: High
 Assignee: Renato Araujo Oliveira Filho (renatofilho)
 Status: New

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

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


** Tags: usability ww07

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Also affects: dialer-app
   Importance: Undecided
   Status: New

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

** Also affects: messaging-app (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: usability ww07

** Changed in: dialer-app
   Importance: Undecided => High

** Changed in: messaging-app
   Importance: Undecided => High

** Changed in: dialer-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Changed in: messaging-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

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

Title:
  make swipe to reveal more discoverable

Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Ubuntu UX bugs:
  New
Status in dialer-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu:
  New

Bug description:
  on all the apps that use it (dialer, messaging, address book), we need
  a way to make the swipe to reveal action more discoverable.

  This was listed in usability testing:
  messaging-app: Swipe to reveal 'copy' and 'info' options had poor 
discoverability
  dialer-app: message or see the contact information

  Suggestions:
  - small arrows (< on left side and > on right side) of the list item to 
inform users that there are actions to be taken
  - first time tutorial when the list is empty or when it's populated with 
first item showing an overlay of how to swipe to reveal more actions

To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1417359/+subscriptions

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


[Touch-packages] [Bug 1417353] [NEW] Make it easier to resend messages that can't be sent

2015-02-02 Thread Bill Filler
Public bug reported:

>From usability testing:
Testers expected the phone to provide a resent option or to automatically 
resend the message when the singal is back if a message is not sent successfully

Testers received a 'no network' pop up, and the full text message stayed
in the compose bar. As a result, they had to constantly check if the
network is back, and then resend the message again. Phone is often used
on the move, and network issue can be a common issue when such as on the
train or around places where full of high buildings. It is important to
design for these retrictions.

Proposed solution:
Until we have "Save as draft" support, I'd propose the following:
- If we detect No Network or No SIM Card and the user presses Send, directly 
add the message to the message thread, but mark it as failed (with the resend 
icon visible)
- Then pop up the dialog as we do today

This way, the message is part of the history and the user can resend whenever 
is convenient without losing their message.
Also, eventually when we have auto resend these messages will be in the queue.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: messaging-app
 Importance: High
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: New

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

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


** Tags: usability ww07

** Changed in: messaging-app
   Importance: Undecided => High

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Also affects: messaging-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: messaging-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Tags added: usability ww07

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: messaging-app
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

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

Title:
  Make it easier to resend messages that can't be sent

Status in the base for Ubuntu mobile products:
  New
Status in Messaging App:
  New
Status in Ubuntu UX bugs:
  New
Status in messaging-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu RTM:
  New

Bug description:
  From usability testing:
  Testers expected the phone to provide a resent option or to automatically 
resend the message when the singal is back if a message is not sent successfully

  Testers received a 'no network' pop up, and the full text message
  stayed in the compose bar. As a result, they had to constantly check
  if the network is back, and then resend the message again. Phone is
  often used on the move, and network issue can be a common issue when
  such as on the train or around places where full of high buildings. It
  is important to design for these retrictions.

  Proposed solution:
  Until we have "Save as draft" support, I'd propose the following:
  - If we detect No Network or No SIM Card and the user presses Send, directly 
add the message to the message thread, but mark it as failed (with the resend 
icon visible)
  - Then pop up the dialog as we do today

  This way, the message is part of the history and the user can resend whenever 
is convenient without losing their message.
  Also, eventually when we have auto resend these messages will be in the queue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417353/+subscriptions

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


[Touch-packages] [Bug 1417350] [NEW] no feedback provided on copy operation

2015-02-02 Thread Bill Filler
Public bug reported:

Expected to see 'Copied to clipboard' as a confirmation after clicking
on the 'Copy' icon

The testers were not quite sure what happened after they tapped on the
'Copy' icon. The change of colour does not comfirm the effect of users'
action effectively.

We should display a message saying "Selection copied to clipboard" or
something like that.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: messaging-app
 Importance: Medium
 Assignee: Tiago Salem Herrmann (tiagosh)
 Status: New

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

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


** Tags: usability ww07

** Also affects: messaging-app
   Importance: Undecided
   Status: New

** Also affects: messaging-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: messaging-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Changed in: messaging-app
   Importance: Undecided => Medium

** Tags added: usability ww07

** Changed in: messaging-app
 Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh)

** 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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1417350

Title:
  no feedback provided on copy operation

Status in the base for Ubuntu mobile products:
  New
Status in Messaging App:
  New
Status in Ubuntu UX bugs:
  New
Status in messaging-app package in Ubuntu:
  New
Status in messaging-app package in Ubuntu RTM:
  New

Bug description:
  Expected to see 'Copied to clipboard' as a confirmation after clicking
  on the 'Copy' icon

  The testers were not quite sure what happened after they tapped on the
  'Copy' icon. The change of colour does not comfirm the effect of
  users' action effectively.

  We should display a message saying "Selection copied to clipboard" or
  something like that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417350/+subscriptions

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


[Touch-packages] [Bug 1417309] Re: goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

2015-02-02 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: Unknown => New

** Changed in: gnome-online-accounts
   Importance: Unknown => Critical

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

Title:
  goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

Status in GNOME Online Accounts:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Upgrade Ubuntu vidid and reboot and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-online-accounts 3.14.2-1
  Uname: Linux 3.19.0-031900rc7-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  2 19:46:37 2015
  ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
  InstallationDate: Installed on 2014-09-25 (130 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f55b957e94d:mov(%rcx),%rax
   PC (0x7f55b957e94d) ok
   source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   __nptl_deallocate_tsd () at pthread_create.c:157
   start_thread (arg=0x7f5597182700) at pthread_create.c:322
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
  Title: goa-daemon crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1417309/+subscriptions

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


[Touch-packages] [Bug 1160569]

2015-02-02 Thread Rumijah-2
ok. got the bloody thing to start via:

/usr/bin/thunderbird -safe-mode

and deleting add-ons; still get:

   (process:28133): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed

But I don't really care anymore. 
Anyway, hope this helps someone...

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

Title:
  GLib-CRITICAL **: g_slice_set_config: assertion `sys_page_size == 0'
  failed

Status in The Mozilla Firefox Browser:
  Confirmed
Status in The "G" Library - GLib:
  Unknown
Status in apport package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Triaged
Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  Have a look at the screen-shot for more details.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: firefox 19.0.2+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  BuildID: 20130308124351
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Channel: Unavailable
  Date: Tue Mar 26 21:48:57 2013
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-03-26 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64+mac (20130326)
  IpRoute:
   default via 10.0.1.1 dev eth0  proto static
   10.0.1.0/24 dev eth0  proto kernel  scope link  src 10.0.1.16  metric 1
   169.254.0.0/16 dev eth0  scope link  metric 1000
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  MarkForUpload: True
  Plugins:
   Windows Media Player Plug-in 10 (compatible; Videos) - 
/usr/lib/mozilla/plugins/libtotem-gmp-plugin.so (totem-mozilla)
   VLC Multimedia Plugin (compatible Videos 3.6.3) - 
/usr/lib/mozilla/plugins/libtotem-cone-plugin.so (totem-mozilla)
   DivX® Web Player - /usr/lib/mozilla/plugins/libtotem-mully-plugin.so 
(totem-mozilla)
   QuickTime Plug-in 7.6.6 - 
/usr/lib/mozilla/plugins/libtotem-narrowspace-plugin.so (totem-mozilla)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=19.0.2/20130308124351
  RelatedPackageVersions:
   totem-mozilla 3.6.3-0ubuntu4
   rhythmbox-mozilla 2.98-0ubuntu3
  RfKill:

  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1160569/+subscriptions

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


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

2015-02-02 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

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

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This occurred upon reboot after failing to complete standard update.

  I was brought to this bug report by system finding problem and
  requesting a report be made.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Mon Feb  2 12:47:26 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2014-07-06 (211 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1417343/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Morten Hundevad
>>>@penalvch i don't have same computer as him and i have the same
compute, tho i still have dell, but i

err brain fart i meant

@penalvch i don't have same computer as him and i have the newest bios,
tho i still have dell

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

 

[Touch-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Morten Hundevad
@penalvch i don't have same computer as him and i have the same compute,
tho i still have dell, but i

I have a XPS l7020 and i have the latest bios.

i have attatched image showing my config.

** Attachment added: "Image showing the config for my case."
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1382462/+attachment/4310916/+files/dual%20monitor.png

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

[Touch-packages] [Bug 1417341] [NEW] Empty contact list should provide way to sync contacts

2015-02-02 Thread Bill Filler
Public bug reported:

>From usability tests:
Contacts' view on the dialer does not have instruction for empty state, and as 
a result, testers struggled to know how to import the contacts. 

Some testers went to the dialer, wanting to sync the contacts so that
they could make a phone call. They clicked on the 'Contacts' icon, but
there was no empty state instruction, apart from an empty screen with
'+add a contact'. One of the tesers had to manually put the contacts in.
It took him three days to finally figure out how to sync the contacts.

As discussed, if the contact list is empty we should display a message
in the list with a button to setup Google account, similar to how it's
done in the address book app.

** Affects: address-book-app
 Importance: High
 Assignee: Renato Araujo Oliveira Filho (renatofilho)
 Status: New

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: dialer-app
 Importance: Undecided
 Status: New

** Affects: messaging-app
 Importance: Undecided
 Status: New

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

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

** Affects: address-book-app (Ubuntu RTM)
 Importance: Undecided
 Status: New


** Tags: usability ww07

** Also affects: messaging-app
   Importance: Undecided
   Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

** Also affects: address-book-app
   Importance: Undecided
   Status: New

** Also affects: address-book-app (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: address-book-app (Ubuntu RTM)
   Importance: Undecided
   Status: New

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: ww07

** Changed in: address-book-app
   Importance: Undecided => High

** Changed in: address-book-app
 Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho)

** Tags added: usability

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

Title:
  Empty contact list should provide way to sync contacts

Status in Address Book App:
  New
Status in the base for Ubuntu mobile products:
  New
Status in Dialer app for Ubuntu Touch:
  New
Status in Messaging App:
  New
Status in Ubuntu UX bugs:
  New
Status in address-book-app package in Ubuntu:
  New
Status in address-book-app package in Ubuntu RTM:
  New

Bug description:
  From usability tests:
  Contacts' view on the dialer does not have instruction for empty state, and 
as a result, testers struggled to know how to import the contacts. 

  Some testers went to the dialer, wanting to sync the contacts so that
  they could make a phone call. They clicked on the 'Contacts' icon, but
  there was no empty state instruction, apart from an empty screen with
  '+add a contact'. One of the tesers had to manually put the contacts
  in. It took him three days to finally figure out how to sync the
  contacts.

  As discussed, if the contact list is empty we should display a message
  in the list with a button to setup Google account, similar to how it's
  done in the address book app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1417341/+subscriptions

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


[Touch-packages] [Bug 1417343] [NEW] package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2015-02-02 Thread Gary Hooley
Public bug reported:

This occurred upon reboot after failing to complete standard update.

I was brought to this bug report by system finding problem and
requesting a report be made.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: rsyslog 7.4.4-1ubuntu2.5
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic i686
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
Date: Mon Feb  2 12:47:26 2015
DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:subprocess installed 
post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2014-07-06 (211 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
SourcePackage: rsyslog
Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This occurred upon reboot after failing to complete standard update.

  I was brought to this bug report by system finding problem and
  requesting a report be made.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: rsyslog 7.4.4-1ubuntu2.5
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic i686
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  Date: Mon Feb  2 12:47:26 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu2.5:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2014-07-06 (211 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu2.5 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1417343/+subscriptions

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


[Touch-packages] [Bug 774643] Re: sched-powersave is outdated

2015-02-02 Thread Jérôme
Same bug on 14.04 LTS release.

--
a@B:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename:   trusty
a@B:~$ ls /sys/devices/system/cpu
cpu0  cpuidle  kernel_max  microcode  modalias  offline  online  possible  
power  present  uevent
a@B:~$
-

/usr/lib/pm-utils/power.d/sched-powersave :
--
(...)
sched_powersave() {
for pool in mc smp smt; do
dev="/sys/devices/system/cpu/sched_${pool}_power_savings"
[ -w "$dev" ] || continue
echo $1 > "$dev"
done
}
(...)


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

Title:
  sched-powersave is outdated

Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pm-utils

  /usr/lib/pm-utils/power.d/sched-powersave

  This file is outdated, because these controls do not exist anymore:

  sched_powersave() {
  for pool in mc smp smt; do
  dev="/sys/devices/system/cpu/sched_${pool}_power_savings"
  [ -w "$dev" ] || continue
  echo $1 > "$dev"
  done
  }

  $ ls /sys/devices/system/cpu/
  cpu0  cpu1  cpufreq  cpuidle  kernel_max  offline  online  perf_events  
possible  present  probe  release

  This is on Maverick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/774643/+subscriptions

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


[Touch-packages] [Bug 1417309] Re: goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

2015-02-02 Thread Cristian Aravena Romero
** Information type changed from Private to Public

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

** Also affects: gnome-online-accounts via
   https://bugzilla.gnome.org/show_bug.cgi?id=743903
   Importance: Unknown
   Status: Unknown

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

Title:
  goa-daemon crashed with SIGSEGV in magazine_chain_pop_head()

Status in GNOME Online Accounts:
  Unknown
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Upgrade Ubuntu vidid and reboot and crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: gnome-online-accounts 3.14.2-1
  Uname: Linux 3.19.0-031900rc7-generic x86_64
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Feb  2 19:46:37 2015
  ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
  InstallationDate: Installed on 2014-09-25 (130 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
  SegvAnalysis:
   Segfault happened at: 0x7f55b957e94d:mov(%rcx),%rax
   PC (0x7f55b957e94d) ok
   source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   __nptl_deallocate_tsd () at pthread_create.c:157
   start_thread (arg=0x7f5597182700) at pthread_create.c:322
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
  Title: goa-daemon crashed with SIGSEGV in __nptl_deallocate_tsd()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1417309/+subscriptions

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


[Touch-packages] [Bug 1408748] Re: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2015-02-02 Thread Favio D'Ercole
** Tags added: precise

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

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

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  Installed with gui updater

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: rsyslog 7.4.4-1ubuntu11.1
  Uname: Linux 3.16.6-031606-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Thu Jan  8 13:12:56 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu11.1:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2013-09-18 (476 days ago)
  InstallationMedia: This
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu11.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1408748/+subscriptions

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


[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

2015-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package whoopsie - 0.2.45

---
whoopsie (0.2.45) vivid; urgency=medium

  * Merge patch from Bryan Quigley to only log when whoopsie's state changes.
(LP: #1217407)
 -- Brian MurrayMon, 02 Feb 2015 13:54:58 -0800

** Changed in: whoopsie (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Fix Released
Status in whoopsie package in Ubuntu:
  Fix Released
Status in whoopsie source package in Trusty:
  In Progress
Status in whoopsie source package in Utopic:
  In Progress

Bug description:
  Test Case
  -
  In the event your system's install of whoopsie isn't spamming syslog (or 
/var/log/upstart/whoopsie.log) with online messages you can recreate the 
situation via the following.
  1) sudo route add -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
  2) sudo route del -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0

  The adding and removing of routes should for force whoopsie to log
  that it is online.  With the version of the package from the -proposed
  repository you should no longer see the online messages due to a route
  change.

  Original Description
  
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: whoopsie 0.2.23
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:109:135:1442457:2013-08-24 15:45:54.414105810 -0500:2013-08-24 
15:45:52.882072686 -0500:/var/crash/_usr_bin_nm-applet.109.crash
   640:1000:135:5451572:2013-08-23 10:46:16.804771591 -0500:2013-08-23 
10:46:13.688702452 -0500:/var/crash/_usr_share_apport_apport-kde.1000.crash
   640:109:135:3258098:2013-08-24 15:45:52.826071475 -0500:2013-08-24 
15:45:50.822028146 -0500:/var/crash/_usr_sbin_unity-greeter.109.crash
   644:0:135:14684:2013-08-27 08:26:39.114007907 -0500:2013-08-19 
19:15:13.128538279 -0500:/var/crash/lttng-modules-dkms.0.crash
   640:1000:135:28058162:2013-08-23 11:45:22.587948069 -0500:2013-08-23 
11:45:04.267536872 -0500:/var/crash/_usr_bin_calibre.1000.crash
  Date: Tue Aug 27 09:53:16 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-10 (197 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130209)
  MarkForUpload: TrueSourcePackage: whoopsie
  UpgradeStatus: Upgraded to saucy on 2013-06-25 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1217407/+subscriptions

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


[Touch-packages] [Bug 1315770] Re: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Strong background noise

2015-02-02 Thread Raymond
http://en.community.dell.com/support-forums/software-
os/f/3525/t/19563481

do jayfree 's solution fix the problem ?

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

Title:
  [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left]
  Strong background noise

Status in Dell Sputnik:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in Fedora:
  New

Bug description:
  When I connect the headphones, there is a strong hissing in both left
  and right side. It does not amplify or reduce along with the master
  volume. Instead, if I completely mute the master volume, the hissing
  disappears. It comes back as soon as I unmute the master volume.

  The internal speakers of the laptop are not affected: when headphones
  are not connected, there is no background hissing noise.

  Standard four questions:
  1) Ubuntu release: 14.04 LTS
  2) Package affected: kernel? (linux-image-3.13.0-24-generic) or maybe 
alsa-driver?
  3) Unless I play music, I expect no to hear anything in the headphones
  4) I get a background hissing noise in the headphones

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sun1875 F pulseaudio
   /dev/snd/controlC1:  sun1875 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May  4 02:46:01 2014
  InstallationDate: Installed on 2014-05-02 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd02/06/2014:svnDellInc.:pnDellPrecisionM3800:pvrA03:rvnDellInc.:rnDellPrecisionM3800:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Dell Precision M3800
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1315770/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Christopher M. Penalver
Piotr Kołaczkowski, as per 
http://www.dell.com/support/home/us/en/dhs/product-support/product/precision-m4600/drivers
 an update to your computer's buggy and outdated BIOS is available (A16). If 
you update to this following https://help.ubuntu.com/community/BIOSUpdate does 
it change anything?  If it doesn't, could you please both specify what 
happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, and the information above is provided, then
please mark this report Status New.

Thank you for your understanding.

** Summary changed:

- Desktop/windows painted incorrectly in dual monitor configuration
+ 10de:0dfa Desktop/windows painted incorrectly in dual monitor configuration

** Tags added: bios-outdated-a16

** No longer affects: unity (Ubuntu)

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

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happen

[Touch-packages] [Bug 1417135] Re: Xorg Bug

2015-02-02 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Xorg Bug

Status in xorg package in Ubuntu:
  New

Bug description:
  Xorg Bug

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb  2 20:37:03 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.10, 3.13.0-45-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2015-01-24 (9 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=8d2f6350-c920-4303-89e1-6d6cbd2d85f9 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-DS2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb  2 20:20:27 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVideo BusKEYBOARD, id 7
   inputPower Button 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:
   product id   15235 
   vendor GSM
  xserver.version: 2:1.15.1-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1417135/+subscriptions

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


[Touch-packages] [Bug 1200906] Re: Apport detect a suspend/resume failure after a reboot

2015-02-02 Thread Christopher M. Penalver
proteus, this report has nothing to do with your problem. In order to have your 
problem addressed, please file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  Apport detect a suspend/resume failure after a reboot

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Apport summary was "[Hewlett-Packard HP EliteBook 8530p]
  suspend/resume failure"

  I was not comming back from suspend/resume, so this is probably an
  Apport error.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-2-generic 3.10.0-2.11
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nicolas1759 F pulseaudio
   /dev/snd/controlC0:  nicolas1759 F pulseaudio
  Date: Sat Jul 13 15:18:10 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=7e493485-d08d-4944-8362-444f69fd1e08
  InstallationDate: Installed on 2013-07-10 (2 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130710)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Hewlett-Packard HP EliteBook 8530p
  MarkForUpload: True
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic 
root=UUID=821ce4aa-35e4-436c-93cc-c8c2d9aba532 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-2-generic N/A
   linux-backports-modules-3.10.0-2-generic  N/A
   linux-firmware1.112
  SourcePackage: linux
  Title: [Hewlett-Packard HP EliteBook 8530p] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/08/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.11
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530p:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530p
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1200906/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Morten Hundevad
ok i figured out how to use it..

I can confirm that unchecked "detect_outputs"

and configuring "outputs" to match screen revolution.  Fix the
overlapping issue.

Under ubunto system settings i also had to correct the settings to match
config in "outputs"

-Thanks

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

Title:
  10de:0dfa Desktop/windows painted incorrectly in dual monitor
  configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when 

[Touch-packages] [Bug 1416712] Re: package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2015-02-02 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in ifupdown package in Ubuntu:
  New

Bug description:
  package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: ifupdown 0.7.48.1ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  AptOrdering:
   netscript-2.4: Remove
   ifupdown: Install
   upstart: Install
   ifupdown: Configure
   upstart: Configure
  Architecture: amd64
  Date: Fri Jan 30 20:48:37 2015
  DuplicateSignature: package:ifupdown:0.7.48.1ubuntu5:el subproceso instalado 
el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2014-08-25 (159 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: ifupdown
  Title: package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1416712/+subscriptions

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


[Touch-packages] [Bug 1416712] Re: package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2015-02-02 Thread Seth Arnold
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in ifupdown package in Ubuntu:
  New

Bug description:
  package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: ifupdown 0.7.48.1ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  AptOrdering:
   netscript-2.4: Remove
   ifupdown: Install
   upstart: Install
   ifupdown: Configure
   upstart: Configure
  Architecture: amd64
  Date: Fri Jan 30 20:48:37 2015
  DuplicateSignature: package:ifupdown:0.7.48.1ubuntu5:el subproceso instalado 
el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2014-08-25 (159 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: ifupdown
  Title: package ifupdown 0.7.48.1ubuntu5 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1416712/+subscriptions

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


[Touch-packages] [Bug 218637] Re: Non-breaking space is easy to write accidentally and impossible to distinguish from regular space.

2015-02-02 Thread Jarno Suni
** Also affects: nano
   Importance: Undecided
   Status: New

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

Title:
  Non-breaking space is easy to write accidentally and impossible to
  distinguish from regular space.

Status in Geany:
  New
Status in Light-Weight Text Editor for Gnome:
  New
Status in GNOME Terminal:
  New
Status in nano:
  New
Status in XFCE4 Terminal Emulator:
  New
Status in xorg package in Ubuntu:
  Invalid

Bug description:
  OS: from Hardy to at least Trusty.

  When you use Finnish keyboard, you have to hold Alt Gr down to type |
  or \ or certain other characters. When typing a shell command, you may
  often want to enter a space character after such characters. But it
  easily happens that Alt Gr is still down when you press space, and
  consequently you type non-breaking space character U+00A0 (at least,
  if you use UTF-8 keyboard layout, which is default in Ubuntu).

  $cd /tmp ; echo 0 > foo\ bar ; ls "foo bar"
  ls: cannot access foo bar: No such file or directory
  $cat foo bar | grep 0
  No command ' grep' found, but there are 16 similar ones
   grep: command not found

  Besides it may be hard to see the typing error, as non-breaking space
  character looks exactly same as regular space character.

  A way to avoid such typos would be to use another keyboard shortcut
  for non-breaking space. Besides non-breaking space should look
  different than regular space in terminal emulators and in editors.

  A workaround in to run
  setxkbmap -option "nbsp:none"
  to make  type regular space character,
  and use `printf '\u00a0'` or `printf "\xc2\xa0"` to have a non-breaking space 
in scripts and in command line.

  Non-breaking space can be typed (in GTK apps) by u 00a0, 
if needed, but it looks exactly like a regular space.
  For me,  would be a good shortcut for non-breaking space.

To manage notifications about this bug go to:
https://bugs.launchpad.net/geany/+bug/218637/+subscriptions

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


[Touch-packages] [Bug 808587] Re: Launcher - Unity should automatically select Keep In Launcher for icons that are sorted

2015-02-02 Thread Treviño
Well, it would be possible, but it also seems that right-clicking an
icon and un-stick it isn't a big deal, and it's just better to consider
that as the configuration parameter, more than a generic option.

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

Title:
  Launcher - Unity should automatically select Keep In Launcher for
  icons that are sorted

Status in Ayatana Design:
  Fix Released
Status in Unity:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  Bug:
  After opening an application, sorting it in the launcher and then closing the 
application the icon disappears.

  Solution:
  After opening an application, it should be understood that sorting it means 
you want to keep it in the launcher. This option should be automatically 
checked after drag/dropping an icon that isn't already sent to stay.  Note that 
if a user then chooses the option to un-pin the app icon from the Launcher, it 
position should still be remembered next time the app is started, see bug 
https://bugs.launchpad.net/ayatana-design/+bug/772517

  Why this solution is better:
  Typically, when a user sorts an icon it shows intent to keep the icon 
displayed among the others. This would also save the user one manual step of 
clicking "Keep in launcher" when they expect that to be the behavior of sorting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/808587/+subscriptions

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


[Touch-packages] [Bug 1153389] Re: "no codecs initialized"

2015-02-02 Thread Neil Hearn
Having same issue on upstream kernel.

have tried multiple solutions regarding alsa-base configurations.

Please see attached alsa-report.txt generated by alsa-info.sh from alsa
site.

** Attachment added: "alsa-info.sh output"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1153389/+attachment/4310870/+files/alsa-report.txt

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

Title:
  "no codecs initialized"

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on a new computer (samsung all-in-one), and on a live ubuntu disk
  12.04 x64, my sound card is not detected.

  I have checked many forums for several months and cannot find the fix.

  I have two sound cards, motherboard and hdmi. Only the hdmi gets
  detected by alsa. It is not good as I am only using the motherboard
  one.

  The dmesg shows "no codecs initialized" for the first card.

  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  ubuntu@ubuntu:~$ lspci | grep -i audio
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
  01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Caicos HDMI Audio 
[Radeon HD 6400 Series]

  ubuntu@ubuntu:~$ dmesg | grep -i hda-intel
  [   97.691334] hda-intel: azx_get_response timeout, switching to polling 
mode: last cmd=0x000f
  [   98.692766] hda-intel: No response from codec, disabling MSI: last 
cmd=0x000f
  [   99.694197] hda-intel: Codec #0 probe error; disabling it...
  [  100.731901] hda-intel: no codecs initialized
  [  100.732057] hda-intel: :01:00.1: Handle VGA-switcheroo audio client

  The same happens on other debian linux distributions. Before I change
  my distribution to ubuntu, I would like to make sure the sound can
  work on ubuntu.

  Happy to help debugging this if necessary.

  Many thanks in advance.

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

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


[Touch-packages] [Bug 1153389] Re: "no codecs initialized"

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  "no codecs initialized"

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  on a new computer (samsung all-in-one), and on a live ubuntu disk
  12.04 x64, my sound card is not detected.

  I have checked many forums for several months and cannot find the fix.

  I have two sound cards, motherboard and hdmi. Only the hdmi gets
  detected by alsa. It is not good as I am only using the motherboard
  one.

  The dmesg shows "no codecs initialized" for the first card.

  ubuntu@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  ubuntu@ubuntu:~$ lspci | grep -i audio
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 04)
  01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Caicos HDMI Audio 
[Radeon HD 6400 Series]

  ubuntu@ubuntu:~$ dmesg | grep -i hda-intel
  [   97.691334] hda-intel: azx_get_response timeout, switching to polling 
mode: last cmd=0x000f
  [   98.692766] hda-intel: No response from codec, disabling MSI: last 
cmd=0x000f
  [   99.694197] hda-intel: Codec #0 probe error; disabling it...
  [  100.731901] hda-intel: no codecs initialized
  [  100.732057] hda-intel: :01:00.1: Handle VGA-switcheroo audio client

  The same happens on other debian linux distributions. Before I change
  my distribution to ubuntu, I would like to make sure the sound can
  work on ubuntu.

  Happy to help debugging this if necessary.

  Many thanks in advance.

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

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


[Touch-packages] [Bug 1367963] Re: NM tries to activate GPRS context of non-present SIM

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  NM tries to activate GPRS context of non-present SIM

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  If a device has had more than one SIM installed, the filesystem will
  include ofono-specific directories for each of these SIMs.

  When NetworkManager walks through the list of possible GPRS contexts (
  aka APNs ), it currently doesn't apply any logic to filter non-present
  SIMs.

  Here's a filtered set of NetworkManager messages that shows activation
  attempts after boot, you'll notice that NM tries to activate two
  different "context1"s, one for each SIM that'd been detected and read
  by ofono.

  Sep 10 21:19:16 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context1'.
  Sep 10 21:19:21 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context1'.
  Sep 10 21:19:28 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context1'.
  Sep 10 21:19:33 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context1'.
  Sep 10 21:19:38 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context2'.
  Sep 10 21:19:43 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context2'.
  Sep 10 21:19:48 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context2'.
  Sep 10 21:19:53 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310410674422772/context2'.
  Sep 10 21:19:58 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310260006686790/context1'.
  Sep 10 21:20:03 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310260006686790/context1'.
  Sep 10 21:20:08 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310260006686790/context1'.
  Sep 10 21:20:13 ubuntu-phablet NetworkManager[1476]:  Auto-activating 
connection '/310260006686790/context1'.

  Here's the output from "nmcli c l":

  espy@shrike:% more nmcli-c-l.out 
  NAME  UUID   TYPE 
 TIMESTAMP-REAL
  /310260006686790/context1 eb36e8dd-f8dc-d7f4-6661-8346df5600ee   gsm  
 never 
  /310410674422772/context2 4915a9cd-88fb-33d7-05c9-88b0f041a022   gsm  
 never 
  /310410674422772/context1 77d2b549-57a9-a12a-c736-5e087c3e87f2   gsm  
 never

  In a dual-SIM situation, this will mean that NM may try activate
  connections from both SIM on each modem.

  I'm marking this as "high", as there's a good chance that this could
  cause problems in the future that aren't easily corrected by a user.

  NM should only try and activate GPRS contexts for the SIM for which
  they've been provisioned.

  This was reproduced on mako running rtm image #26,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1367963/+subscriptions

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


[Touch-packages] [Bug 676886] Re: Launcher - Add 'new document' option to Open Office, Gimp and Inkscape quicklists

2015-02-02 Thread Alex Valavanis
** Changed in: inkscape
   Status: Fix Committed => Fix Released

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

Title:
  Launcher - Add 'new document' option to Open Office, Gimp and Inkscape
  quicklists

Status in Ayatana Design:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  Fix Released
Status in Unity:
  Fix Released
Status in Unity 2D:
  Fix Released
Status in obsolete project, use ayatana-design instead:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in unity-2d package in Ubuntu:
  Fix Released

Bug description:
  Launcher - Add 'new document (or drawing, spreadsheet, etc...)' option
  to Open Office, Gimp and Inkscape quicklists

  Description:

  In user testing we found that users had difficulty creating new
  documents.  To provide a shortcut to this common use case a 'new
  document' entry should be added to the quicklist of the following
  applications:

  1) Open Office word processor - "New Document"
  2) Open Office spreadsheet - "New Spreadsheet"
  3) Open Office presentation - "New Presentation"
  4) Gimp - "New Image"
  5) Inkscape - "New Drawing"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/676886/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Morten Hundevad
well i figured out what you meant by ccsm it is just the manager.. but i
am still unable to find the setting you referee to ?

Is it "detect_outputs" ? if so.. what do i need to put in the output
array ?

Currently it is:
1680x1050+0+0

left is
1920x1080 (built in)

right is
1920x1200 (external)

I do not know what to put in the array ? i cant find info about it
anywhere. and if i change it and reboot or logout and back in .. it
seems to be "reset" and not there anymore.

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange pos

[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

2015-02-02 Thread Brian Murray
** Also affects: whoopsie (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

** Changed in: whoopsie (Ubuntu Trusty)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie (Ubuntu Utopic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie (Ubuntu Trusty)
   Importance: Undecided => Low

** Changed in: whoopsie (Ubuntu Utopic)
   Importance: Undecided => Low

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

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

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Fix Released
Status in whoopsie package in Ubuntu:
  In Progress
Status in whoopsie source package in Trusty:
  In Progress
Status in whoopsie source package in Utopic:
  In Progress

Bug description:
  Test Case
  -
  In the event your system's install of whoopsie isn't spamming syslog (or 
/var/log/upstart/whoopsie.log) with online messages you can recreate the 
situation via the following.
  1) sudo route add -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
  2) sudo route del -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0

  The adding and removing of routes should for force whoopsie to log
  that it is online.  With the version of the package from the -proposed
  repository you should no longer see the online messages due to a route
  change.

  Original Description
  
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: whoopsie 0.2.23
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:109:135:1442457:2013-08-24 15:45:54.414105810 -0500:2013-08-24 
15:45:52.882072686 -0500:/var/crash/_usr_bin_nm-applet.109.crash
   640:1000:135:5451572:2013-08-23 10:46:16.804771591 -0500:2013-08-23 
10:46:13.688702452 -0500:/var/crash/_usr_share_apport_apport-kde.1000.crash
   640:109:135:3258098:2013-08-24 15:45:52.826071475 -0500:2013-08-24 
15:45:50.822028146 -0500:/var/crash/_usr_sbin_unity-greeter.109.crash
   644:0:135:14684:2013-08-27 08:26:39.114007907 -0500:2013-08-19 
19:15:13.128538279 -0500:/var/crash/lttng-modules-dkms.0.crash
   640:1000:135:28058162:2013-08-23 11:45:22.587948069 -0500:2013-08-23 
11:45:04.267536872 -0500:/var/crash/_usr_bin_calibre.1000.crash
  Date: Tue Aug 27 09:53:16 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-10 (197 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130209)
  MarkForUpload: TrueSourcePackage: whoopsie
  UpgradeStatus: Upgraded to saucy on 2013-06-25 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1217407/+subscriptions

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


[Touch-packages] [Bug 1417302] [NEW] NetworkManager fails to activate connection on modem

2015-02-02 Thread Jonas G. Drange
ablet NetworkManager[1365]:  NetworkManager 
state is now CONNECTED_LOCAL
Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Disabling 
autoconnect for connection '/242013054944676/context1'.
Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation (ril_0) 
failed for connection '/242013054944676/context1'
Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation (ril_0) 
Stage 1 of 5 (Device Prepare) complete.
Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ril_0): device 
state change: failed -> disconnected (reason 'none') [120 30 0]
Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ril_0): 
deactivating device (reason 'none') [0]
Feb  2 22:35:49 ubuntu-phablet NetworkManager[1365]:  (ccmni0): link 
disconnected (deferring action for 4 seconds)
Feb  2 22:35:50 ubuntu-phablet NetworkManager[1365]:  Could not send ARP 
for local address 2.149.176.49: Failed to execute child process 
"/usr/bin/arping" (No such file or directory)
Feb  2 22:35:53 ubuntu-phablet NetworkManager[1365]:  (ccmni0): link 
disconnected (calling deferred action)
Feb  2 22:35:53 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
Feb  2 22:35:53 ubuntu-phablet NetworkManager[1365]:  (ccmni0): 
deactivating device (reason 'carrier-changed') [40]
Feb  2 22:35:53 ubuntu-phablet NetworkManager[1365]:  NetworkManager 
state is now DISCONNECTED
Feb  2 22:35:53 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: unavailable -> unmanaged (reason 'none') [20 10 0]

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu4
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.15.1-0ubuntu4
Architecture: armhf
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon Feb  2 22:25:38 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 # Include files from /etc/network/interfaces.d:
 source-directory /etc/network/interfaces.d
InstallationDate: Installed on 2015-02-02 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
IpRoute:
 default via 10.0.0.1 dev wlan0  proto static  metric 1024 
 10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.6
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
PciNetwork:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dbus.1.system.d.org.freedesktop.NetworkManager.conf: 
2015-02-02T02:31:45
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: apport-bug armhf vivid

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  NetworkManager fails to activate connection on modem

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Trying to activate /ril_0/context1 on ril_0 and get the following.
  It's almost the same code that produced this classic bug #1378102

  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): link 
connected
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ril_0): IPv4 
static configuration:
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:address 
2.149.176.49/24
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:gateway 
2.149.176.49
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:DNS 
193.213.112.4
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:DNS 
130.67.15.198
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:mms proxy: 
10.10.10.11:8080
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 
41]
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) starting connection 'ccmni0'
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 1 of 5 (Device Prepare) scheduled...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  Activation 
(ccmni0) Stage 1 of 5 (Device Prepare) started...
  Feb  2 22:35:48 ubuntu-phablet NetworkManager[1365]:  (ccmni0): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
  Feb  2 22:35:48 ubuntu-phable

[Touch-packages] [Bug 1417298] Re: Upgrade harfbuzz to 0.9.38

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Upgrade harfbuzz to 0.9.38

Status in harfbuzz package in Ubuntu:
  Confirmed

Bug description:
  Please upgrade harfbuzz to 0.9.38

  See also http://www.freedesktop.org/software/harfbuzz/release/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1417298/+subscriptions

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


[Touch-packages] [Bug 1417298] [NEW] Upgrade harfbuzz to 0.9.38

2015-02-02 Thread Pander
Public bug reported:

Please upgrade harfbuzz to 0.9.38

See also http://www.freedesktop.org/software/harfbuzz/release/

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


** Tags: 15.04 upgrade-software-version

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

Title:
  Upgrade harfbuzz to 0.9.38

Status in harfbuzz package in Ubuntu:
  Confirmed

Bug description:
  Please upgrade harfbuzz to 0.9.38

  See also http://www.freedesktop.org/software/harfbuzz/release/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1417298/+subscriptions

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


[Touch-packages] [Bug 1417297] [NEW] [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at all

2015-02-02 Thread Vikrant
Public bug reported:

No sound at all after the installation of ubuntu 13.10

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: alsa-base 1.0.25+dfsg-0ubuntu4
ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
Uname: Linux 3.11.0-26-generic i686
ApportVersion: 2.12.5-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tanvi  1963 F pulseaudio
Date: Mon Feb  2 22:17:21 2015
InstallationDate: Installed on 2015-02-02 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tanvi  1963 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/12/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7VET82WW (3.12 )
dmi.board.name: 2768GP6
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7VET82WW(3.12):bd01/12/2010:svnLENOVO:pn2768GP6:pvrThinkPadR400:rvnLENOVO:rn2768GP6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2768GP6
dmi.product.version: ThinkPad R400
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug i386 saucy

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

Title:
  [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound at all after the installation of ubuntu 13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tanvi  1963 F pulseaudio
  Date: Mon Feb  2 22:17:21 2015
  InstallationDate: Installed on 2015-02-02 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tanvi  1963 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [2768GP6, Conexant CX20561 (Hermosa), Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7VET82WW (3.12 )
  dmi.board.name: 2768GP6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7VET82WW(3.12):bd01/12/2010:svnLENOVO:pn2768GP6:pvrThinkPadR400:rvnLENOVO:rn2768GP6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2768GP6
  dmi.product.version: ThinkPad R400
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1170647] Re: After minimizing an external media, clicking on the "Files" icon on the Launcher doesn't restore the minimized window, but opens a new one

2015-02-02 Thread Luigi R.
...but only for the trash and the external media. The local partition
which is mounted as:

/mnt/Data auto uid=1000,gid=1000,umask=077,nodev,nofail,x-gvfs-show 0 0

do not show the problem.

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

Title:
  After minimizing an external media, clicking on the "Files" icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the "Files" icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the "Files" icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - One way to navigate between windows at this moment is to use the
  "control + tabulation" key combination, or to click again on the
  "Files" icon so windows are exposed.

  Otherwise the minimized window Can be restored by clicking on the
  Volume's launcher icon or scrolling on the Files icon

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the "Files" icon and select the
  "unlock from Launcher" option.

  FIX

  - The launcher icon for "Files" to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the "Files" icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+subscriptions

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


[Touch-packages] [Bug 1170647] Re: After minimizing an external media, clicking on the "Files" icon on the Launcher doesn't restore the minimized window, but opens a new one

2015-02-02 Thread Luigi R.
I do not know what happens, I did not reinstall ubuntu but just keeping
updating, now as everyone here I am facing again the bug.

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

Title:
  After minimizing an external media, clicking on the "Files" icon on
  the Launcher doesn't restore the minimized window, but opens a new one

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Connect a removable media to the computer.
  2. On the launcher, click on the "Files" icon.
  3. On the left sidebar, click on the removable media icon or the trash.
  4. Minimize the window.
  5. Click on the "Files" icon.

  EXPECTED BEHAVIOUR

  - The Files window to be maximized.

  REAL BEHAVIOUR

  - A new window is opened.

  RELEVANT DETAILS

  - One way to navigate between windows at this moment is to use the
  "control + tabulation" key combination, or to click again on the
  "Files" icon so windows are exposed.

  Otherwise the minimized window Can be restored by clicking on the
  Volume's launcher icon or scrolling on the Files icon

  **
   SOLUTION
  **

  WORK-AROUND

  - On the launcher, left click on the "Files" icon and select the
  "unlock from Launcher" option.

  FIX

  - The launcher icon for "Files" to be treated the same way as if it
  was unlocked.

  REGRESSION POTENTIAL

  - Clicking on the "Files" icon won't send the user to its home folder,
  but to the latest opened Files window.

  
   TECHNICAL INFO
  

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  Uname: Linux 3.8.0-18-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: i386
  Date: Fri Apr 19 11:33:13 2013
  EcryptfsInUse: Yes
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'814x493+136+38'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'182'
  InstallationDate: Installed on 2011-07-23 (635 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1170647/+subscriptions

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


[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

2015-02-02 Thread Brian Murray
** Changed in: whoopsie (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: whoopsie
   Importance: Undecided => Medium

** Changed in: whoopsie
   Status: Confirmed => Fix Released

** Changed in: whoopsie (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Fix Released
Status in whoopsie package in Ubuntu:
  In Progress

Bug description:
  Test Case
  -
  In the event your system's install of whoopsie isn't spamming syslog (or 
/var/log/upstart/whoopsie.log) with online messages you can recreate the 
situation via the following.
  1) sudo route add -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
  2) sudo route del -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0

  The adding and removing of routes should for force whoopsie to log
  that it is online.  With the version of the package from the -proposed
  repository you should no longer see the online messages due to a route
  change.

  Original Description
  
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: whoopsie 0.2.23
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:109:135:1442457:2013-08-24 15:45:54.414105810 -0500:2013-08-24 
15:45:52.882072686 -0500:/var/crash/_usr_bin_nm-applet.109.crash
   640:1000:135:5451572:2013-08-23 10:46:16.804771591 -0500:2013-08-23 
10:46:13.688702452 -0500:/var/crash/_usr_share_apport_apport-kde.1000.crash
   640:109:135:3258098:2013-08-24 15:45:52.826071475 -0500:2013-08-24 
15:45:50.822028146 -0500:/var/crash/_usr_sbin_unity-greeter.109.crash
   644:0:135:14684:2013-08-27 08:26:39.114007907 -0500:2013-08-19 
19:15:13.128538279 -0500:/var/crash/lttng-modules-dkms.0.crash
   640:1000:135:28058162:2013-08-23 11:45:22.587948069 -0500:2013-08-23 
11:45:04.267536872 -0500:/var/crash/_usr_bin_calibre.1000.crash
  Date: Tue Aug 27 09:53:16 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-10 (197 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130209)
  MarkForUpload: TrueSourcePackage: whoopsie
  UpgradeStatus: Upgraded to saucy on 2013-06-25 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1217407/+subscriptions

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


[Touch-packages] [Bug 1417048] Re: Tapping input source button opens menu instead of cycling layouts

2015-02-02 Thread Michael Sheldon
** Changed in: ubuntu-keyboard (Ubuntu)
 Assignee: (unassigned) => Michael Sheldon (michael-sheldon)

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

Title:
  Tapping input source button opens menu instead of cycling layouts

Status in ubuntu-keyboard package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 r78

  1. If you do not have more than one keyboard layout active, add one in System 
Settings > "Language & Text" > "Keyboard layouts".
  2. Focus a text field, for example the search field on the System Settings 
main screen.
  3. Tap the input source button. 🌐
  What happens: The keyboard layout menu opens.

  What should happen: The keyboard cycles to the next-most-recently-used
  layout. The menu should open on long-press, not on tap.

  : "Tap on
  language switcher allows you to go to cycle to next language ... Long-
  press on bottom-left button labelled with current language [opens the
  menu illustrated]."

  [Originally reported by guy luz in .]

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

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


[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

2015-02-02 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/whoopsie

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Fix Released
Status in whoopsie package in Ubuntu:
  In Progress

Bug description:
  Test Case
  -
  In the event your system's install of whoopsie isn't spamming syslog (or 
/var/log/upstart/whoopsie.log) with online messages you can recreate the 
situation via the following.
  1) sudo route add -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
  2) sudo route del -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0

  The adding and removing of routes should for force whoopsie to log
  that it is online.  With the version of the package from the -proposed
  repository you should no longer see the online messages due to a route
  change.

  Original Description
  
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: whoopsie 0.2.23
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:109:135:1442457:2013-08-24 15:45:54.414105810 -0500:2013-08-24 
15:45:52.882072686 -0500:/var/crash/_usr_bin_nm-applet.109.crash
   640:1000:135:5451572:2013-08-23 10:46:16.804771591 -0500:2013-08-23 
10:46:13.688702452 -0500:/var/crash/_usr_share_apport_apport-kde.1000.crash
   640:109:135:3258098:2013-08-24 15:45:52.826071475 -0500:2013-08-24 
15:45:50.822028146 -0500:/var/crash/_usr_sbin_unity-greeter.109.crash
   644:0:135:14684:2013-08-27 08:26:39.114007907 -0500:2013-08-19 
19:15:13.128538279 -0500:/var/crash/lttng-modules-dkms.0.crash
   640:1000:135:28058162:2013-08-23 11:45:22.587948069 -0500:2013-08-23 
11:45:04.267536872 -0500:/var/crash/_usr_bin_calibre.1000.crash
  Date: Tue Aug 27 09:53:16 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-10 (197 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130209)
  MarkForUpload: TrueSourcePackage: whoopsie
  UpgradeStatus: Upgraded to saucy on 2013-06-25 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1217407/+subscriptions

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


[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

2015-02-02 Thread Brian Murray
** Description changed:

+ Test Case
+ -
+ In the event your system's install of whoopsie isn't spamming syslog (or 
/var/log/upstart/whoopsie.log) with online messages you can recreate the 
situation via the following.
+ 1) sudo route add -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
+ 2) sudo route del -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
+ 
+ The adding and removing of routes should for force whoopsie to log that
+ it is online.  With the version of the package from the -proposed
+ repository you should no longer see the online messages due to a route
+ change.
+ 
+ Original Description
+ 
  It is mostly the "online" messages:
  
  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times
- Aug 27 07:47:50  whoopsie[1832]: last message repeated 18 times
- Aug 27 07:48:50  whoopsie[1832]: last message repeated 15 times
- Aug 27 07:49:50  whoopsie[1832]: last message repeated 16 times
- Aug 27 07:50:50  whoopsie[1832]: last message repeated 21 times
- Aug 27 07:51:50  whoopsie[1832]: last message repeated 18 times
- Aug 27 07:52:50  whoopsie[1832]: last message repeated 20 times
- Aug 27 07:53:50  whoopsie[1832]: last message repeated 22 times
- Aug 27 07:54:50  whoopsie[1832]: last message repeated 15 times
- Aug 27 07:55:50  whoopsie[1832]: last message repeated 22 times
- Aug 27 07:56:50  whoopsie[1832]: last message repeated 20 times
- Aug 27 07:57:50  whoopsie[1832]: last message repeated 18 times
- Aug 27 07:58:51  whoopsie[1832]: last message repeated 16 times
- Aug 27 07:59:46  whoopsie[1832]: last message repeated 17 times
- Aug 27 07:59:47 xango3 whoopsie[1832]: online
- Aug 27 08:00:51  whoopsie[1832]: last message repeated 24 times
- Aug 27 08:01:51  whoopsie[1832]: last message repeated 24 times
- Aug 27 08:02:51  whoopsie[1832]: last message repeated 19 times
- Aug 27 08:03:51  whoopsie[1832]: last message repeated 19 times
- Aug 27 08:04:51  whoopsie[1832]: last message repeated 17 times
- Aug 27 08:05:51  whoopsie[1832]: last message repeated 19 times
- Aug 27 08:06:51  whoopsie[1832]: last message repeated 16 times
- Aug 27 08:07:51  whoopsie[1832]: last message repeated 18 times
- Aug 27 08:08:51  whoopsie[1832]: last message repeated 28 times
- Aug 27 08:09:51  whoopsie[1832]: last message repeated 21 times
- Aug 27 08:10:51  whoopsie[1832]: last message repeated 22 times
- Aug 27 08:11:51  whoopsie[1832]: last message repeated 20 times
- Aug 27 08:12:51  whoopsie[1832]: last message repeated 18 times
- Aug 27 08:13:51  whoopsie[1832]: last message repeated 16 times
- Aug 27 08:14:51  whoopsie[1832]: last message repeated 18 times
- Aug 27 08:15:51  whoopsie[1832]: last message repeated 18 times
- Aug 27 08:16:51  whoopsie[1832]: last message repeated 15 times
- Aug 27 08:17:01  whoopsie[1832]: last message repeated 2 times
- Aug 27 08:17:12 xango3 whoopsie[1832]: online
- Aug 27 08:18:21  whoopsie[1832]: last message repeated 22 times
- Aug 27 08:19:21  whoopsie[1832]: last message repeated 15 times
- Aug 27 08:19:44  whoopsie[1832]: last message repeated 5 times
- Aug 27 08:19:44 xango3 whoopsie[1832]: online
- Aug 27 08:20:48  whoopsie[1832]: last message repeated 29 times
- Aug 27 08:21:49  whoopsie[1832]: last message repeated 23 times
- Aug 27 08:22:50  whoopsie[1832]: last message repeated 24 times
- Aug 27 08:23:05  whoopsie[1832]: last message repeated 8 times
- Aug 27 08:23:10 xango3 whoopsie[1832]: online
- Aug 27 08:23:11 xango3 whoopsie[1832]: online
- Aug 27 08:23:15 xango3 whoopsie[1832]: online
- Aug 27 08:23:16 xango3 whoopsie[1832]: online
- Aug 27 08:24:17  whoopsie[1832]: last message repeated 22 times
- Aug 27 08:24:27 xango3 whoopsie[1832]: online
- Aug 27 08:24:28 xango3 whoopsie[1832]: online
- Aug 27 08:25:29  whoopsie[1832]: last message repeated 17 times
- Aug 27 08:25:40  whoopsie[1832]: last message repeated 3 times
- Aug 27 08:25:42 xango3 whoopsie[1832]: online
- Aug 27 08:25:42 xango3 whoopsie[1832]: online
- Aug 27 08:25:43 xango3 whoopsie[1832]: online
- Aug 27 08:26:44  whoopsie[1832]: last message repeated 15 times
- Aug 27 08:26:55  whoopsie[1832]: last message repeated 2 times
- Aug 27 08:26:56 xango3 whoopsie[1832]: online
- Aug 27 08:33:23 xango3 whoopsie[1568]: whoopsie 0.2.23 starting up.
- Aug 27 08:33:23 xango3 whoopsie[1568]: Using lock path: 
/var/lock/whoopsie/lock
- Aug 27 08:33:23 xango3 whoopsie[1794]: offline
- Aug 27 08:33:27 xango3 whoopsie[1794]: offline
- Aug 27 08:33:27 xango3 whoopsie[1794]: online
- Aug 27 08:33:28 xango3 whoopsie[1794]: online
- Aug 27 08:33:29 xango3 whoopsie[1794]: online
- Aug 27 08:33:29 xango3 whoopsie[1794]: online
- Aug 27 08:33:30 xango3 whoopsie

[Touch-packages] [Bug 1217407] Re: whoopsie spams the log with "online" messages

2015-02-02 Thread Launchpad Bug Tracker
** Branch linked: lp:whoopsie

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

Title:
  whoopsie spams the log with "online" messages

Status in One Hundred Papercuts:
  Invalid
Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in whoopsie package in Ubuntu:
  Confirmed

Bug description:
  Test Case
  -
  In the event your system's install of whoopsie isn't spamming syslog (or 
/var/log/upstart/whoopsie.log) with online messages you can recreate the 
situation via the following.
  1) sudo route add -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0
  2) sudo route del -net 10.0.3.0/24 gw 192.168.10.1 dev wlan0

  The adding and removing of routes should for force whoopsie to log
  that it is online.  With the version of the package from the -proposed
  repository you should no longer see the online messages due to a route
  change.

  Original Description
  
  It is mostly the "online" messages:

  $ grep whoopsie /var/log/syslog
  Aug 27 07:42:21 xango3 whoopsie[1832]: online
  Aug 27 07:42:27 xango3 whoopsie[1832]: online
  Aug 27 07:43:32  whoopsie[1832]: last message repeated 18 times
  Aug 27 07:44:50  whoopsie[1832]: last message repeated 17 times
  Aug 27 07:45:50  whoopsie[1832]: last message repeated 16 times
  Aug 27 07:46:50  whoopsie[1832]: last message repeated 16 times

  ProblemType: BugDistroRelease: Ubuntu 13.10
  Package: whoopsie 0.2.23
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:109:135:1442457:2013-08-24 15:45:54.414105810 -0500:2013-08-24 
15:45:52.882072686 -0500:/var/crash/_usr_bin_nm-applet.109.crash
   640:1000:135:5451572:2013-08-23 10:46:16.804771591 -0500:2013-08-23 
10:46:13.688702452 -0500:/var/crash/_usr_share_apport_apport-kde.1000.crash
   640:109:135:3258098:2013-08-24 15:45:52.826071475 -0500:2013-08-24 
15:45:50.822028146 -0500:/var/crash/_usr_sbin_unity-greeter.109.crash
   644:0:135:14684:2013-08-27 08:26:39.114007907 -0500:2013-08-19 
19:15:13.128538279 -0500:/var/crash/lttng-modules-dkms.0.crash
   640:1000:135:28058162:2013-08-23 11:45:22.587948069 -0500:2013-08-23 
11:45:04.267536872 -0500:/var/crash/_usr_bin_calibre.1000.crash
  Date: Tue Aug 27 09:53:16 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-02-10 (197 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130209)
  MarkForUpload: TrueSourcePackage: whoopsie
  UpgradeStatus: Upgraded to saucy on 2013-06-25 (62 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1217407/+subscriptions

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


[Touch-packages] [Bug 1414675] Re: [messaging-app] message search do not show all matches

2015-02-02 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Released

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

Title:
  [messaging-app] message search do not show all matches

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Messaging App:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Fix Released

Bug description:
  If the latest message in a given thread comes from a certain sim card,
  it will only display matches of messages belonging to that particular
  sim card.

  Steps to reproduce:
  1) have a dual sim phone
  2) open messaging app and send two sms's to the same contact, using a 
different sim card for each. Say the message contents are "message1" and 
"message2"
  3) go back to the previous screen and do a search for both message1 and 
message2

  Expected behavior:
  There should be possible to find either message1 or message2

  Current behavior:
  Only message2 is found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1414675/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Morten Hundevad
@Rockwalrus i would like to try that. can you be a bit more spesefic ?
what is CCSM ? i dont see that option or a manual option .. maybe
translation is off i am using danish.

-Thanks

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia se

[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10

2015-02-02 Thread svenmeier
Same as #74: Running with Gnome 3.14 from gnome3-team PPA, everything
smooth now.

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

Title:
  Graphics Slow After Upgrade 14.04 - 14.10

Status in xorg package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions

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


Re: [Touch-packages] [Bug 1416895] Re: /etc/dnsmasq.conf does not contain an ending newline character

2015-02-02 Thread Simon Kelley
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Thomas, this is fixed upstream. I'll add (LP: #1416895) to the
changelog.


Cheers,

Simon.


On 01/02/15 21:04, Thomas Hood wrote:
> Confirmed that the bug affects 2.72-2.
> 
> $ cat /etc/dnsmasq.conf | tail -n 2 # Include all files in a
> directory which end in .conf #conf-dir=/etc/dnsmasq.d/*.conf$ od -t
> c /etc/dnsmasq.conf | tail -n 2 0062620   /   *   .   c   o   n
> f 0062627 $
> 
> 
> ** Changed in: dnsmasq (Ubuntu) Status: New => Confirmed
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJUz+wdAAoJEBXN2mrhkTWi/gwP/1QL4kncy+NHv4u9XUu7C3Nf
ilfwOPmZquxXL6Xe2SyoLcM6O5cMPamfMRNvp6upVozZqvn3buBSflXn5I5lgl6j
J3/fmHwOl2uUg+GT7kM+6lca8SrFVaWuyOVLsCzlH1PVIuucrVoQmCGjMxo/3dy2
PB6fvMve21vGYYXs39rsmhoPFIOB+Xz10cbDeeyF4GIwFB15s3dPaL/9yy4y8x9O
TUNivrrUVBAKqTFjx9rWx8Xi/h98sy2WJ0dZWnWCJuA0Vy01lnzwMK6WRDaZ4FKy
XQ7anFgnLCD6I18PrFEb7g2kYzzwVGxqtvK53h8PNYh7swGxyr2eHxBHlkc6OC3E
eZa20aqhgVENVC/5PSmR/jpoR1CJta52aNhu3lJy+Ym1aIy/fdQVog4TZ44osyHG
VAOV4FEP0Ucw+tKAXzYlRDnCpMCsR/O8iycwgaJa2dhXPn156zY29MNxXdELMWo0
IUpBXG+KNm9NJty1HOZVoagUFI2pglXxnvYoh66sudBX3g27lXTIWTFjVoX5MyjY
duxBo6leRzY7OrK8A2j/73OrgudBU94kLQF7iig3vEYx3EYwl8yIzB6yEP5TNzYf
pX38rgBrSi3klsxg9ZVWXIIGz0demLCDO43rHnom6Uglq+zTFl6qePJ8XWwwPxMb
bETeMWMAG08HQJoMDoYW
=+g4T
-END PGP SIGNATURE-

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

Title:
  /etc/dnsmasq.conf does not contain an ending newline character

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.04 dev with dnsmasq 2.72-2 and there is no ending
  newline character in /etc/dnsmasq.conf.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1416895/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Rockwalrus
If I set the outputs manually under CCSM using General Options/Display
Settings, it displays fine.

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubun

[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Rockwalrus
I suspect this is related to #1394665.

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu Display configuration dialog detects both displays correc

[Touch-packages] [Bug 1417261] [NEW] On app removal, account access permissions persist

2015-02-02 Thread Niklas Wenzel
Public bug reported:

How to reproduce:

1) Install an app which uses online accounts.
2) Uninstall it.
3) Reinstall the application OR ANOTHER APP WITH THE SAME NAMESPACE and it will 
still be able to access the online account.

I could see this being used for phishing when the user is asked to manually 
install a click package with the same namespace as another app, which would 
then allow bad entities to have access to the online accounts of the original 
app.
It could either be presented as a completely seperate app when the user has 
removed the original one or as an "official version" by the people doing the 
phishing.

Therefore, I vote for removing account information from apps when they
are uninstalled.

** Affects: ubuntu-system-settings-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  On app removal, account access permissions persist

Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  New

Bug description:
  How to reproduce:

  1) Install an app which uses online accounts.
  2) Uninstall it.
  3) Reinstall the application OR ANOTHER APP WITH THE SAME NAMESPACE and it 
will still be able to access the online account.

  I could see this being used for phishing when the user is asked to manually 
install a click package with the same namespace as another app, which would 
then allow bad entities to have access to the online accounts of the original 
app.
  It could either be presented as a completely seperate app when the user has 
removed the original one or as an "official version" by the people doing the 
phishing.

  Therefore, I vote for removing account information from apps when they
  are uninstalled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1417261/+subscriptions

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


[Touch-packages] [Bug 1414675] Re: [messaging-app] message search do not show all matches

2015-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package messaging-app - 0.1+15.04.20150127.1
~rtm-0ubuntu1

---
messaging-app (0.1+15.04.20150127.1~rtm-0ubuntu1) 14.09; urgency=low

  [ Tiago Salem Herrmann ]
  * Generate filters dynamically using a UnionFilter with all grouped
threads. (LP: #1414675)
 -- Ubuntu daily releaseTue, 27 Jan 2015 
13:54:11 +

** Changed in: messaging-app (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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1414675

Title:
  [messaging-app] message search do not show all matches

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Messaging App:
  In Progress
Status in messaging-app package in Ubuntu:
  Fix Released
Status in messaging-app package in Ubuntu RTM:
  Fix Released

Bug description:
  If the latest message in a given thread comes from a certain sim card,
  it will only display matches of messages belonging to that particular
  sim card.

  Steps to reproduce:
  1) have a dual sim phone
  2) open messaging app and send two sms's to the same contact, using a 
different sim card for each. Say the message contents are "message1" and 
"message2"
  3) go back to the previous screen and do a search for both message1 and 
message2

  Expected behavior:
  There should be possible to find either message1 or message2

  Current behavior:
  Only message2 is found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1414675/+subscriptions

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


[Touch-packages] [Bug 1315422] Re: add-apt-repository should have an option for adding only binary DEBs (without DEB-SRC)

2015-02-02 Thread Brian Murray
** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  add-apt-repository should have an option for adding only binary DEBs
  (without DEB-SRC)

Status in Charm Helpers:
  New
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  STEPS TO REPRODUCE:
1. launch terminal
2. add some repository (for example, proprietary Opera without source code) 
with 
 sudo add-apt-repository 'deb http://deb.opera.com/opera/ stable non-free'
3. update repositories with 
 sudo apt-get update

  EXPECTED RESULTS:
Index files are updated, opera package may be installed with 
  sudo apt-get install opera

  ACTUAL RESULTS:
Got error messages:
 W: Failed to fetch http://deb.opera.com/opera/dists/stable/Release  Unable 
to find expected entry 'non-free/source/Sources' in Release file (Wrong 
sources.list entry or malformed file)

  E: Some index files failed to download. They have been ignored, or
  old ones used instead.

Unable to install opera with   
  sudo apt-get install opera
Able to install opera after commenting out deb-src line.

  
  Please add option to add-apt-repository for skipping deb-src line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-helpers/+bug/1315422/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Rockwalrus
If I switch WM to sawfish, this problem goes away.  Switching back to
Unity makes it come back.

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu 

[Touch-packages] [Bug 1417227] Re: Leaks hostname in XorgLog.txt

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Leaks hostname in XorgLog.txt

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Apport uploads the file XorgLog.txt which contain;
  [ 7.186] Current Operating System: Linux bunker15.example.gov 
3.18.0-12-generic #13-Ubuntu SMP Thu Jan 28 05:12:13 UTC 2015 x86_64

  The hostname ought to be scrubbed by Apport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1417227/+subscriptions

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


[Touch-packages] [Bug 1417225] Re: Leaks login username in CurrentDmesg.txt

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Leaks login username in CurrentDmesg.txt

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Apport uploads the file CurrentDmesg.txt which may contain;
  [   49.635156] systemd-logind[1465]: New session c2 of user alice.

  The username ought to be replaced by Apport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1417225/+subscriptions

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


[Touch-packages] [Bug 1382462] Re: Desktop/windows painted incorrectly in dual monitor configuration

2015-02-02 Thread Rockwalrus
** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Desktop/windows painted incorrectly in dual monitor configuration

Status in unity package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My setup: Dell M4600 laptop with Dell U3011 2560x1600 monitor attached
  to DisplayPort.

  I was using Nvidia 331.38 prioprietary driver for quite a long time
  with Ubuntu 14.04 LTS and everything worked perfectly. Today I
  upgraded to Ubuntu 14.10, which comes with Nvidia 331.89 and observed
  the following problem:

  1. When I boot up the computer with the monitor connected, the login
  screen looks fine. Both displays get detected properly and resolutions
  are ok (1920x1080 on the builtin laptop display and 2560x1600 on
  U3011) and screen contents scaled properly.

  2. Then I log into my account, for 3 seconds U3011 displays some
  rubbish (but it was always like that) and when it finally logs in, it
  displays everything stretched horizontally through both my screens. It
  looks as if it tried to paint the contents of a single display on two
  of them, by stretching the content horizontally, so everything (icons,
  windows, wallpaper) has wrong aspect-ratio. Funny, the top status bar
  seem to render correctly and the resolution/size of the top menu is
  correct. Physical resolution of both screens is ok. I'll attach a
  photo, because it is hard to describe how it looks.

  3. I cannot use system in this state - mouse click position seems to
  not be synchronized with what's on the display - e.g. I can start
  applications, but then they don't react to mouseclicks.

  However: booting up without the second display connected, logging in
  and *then* connecting the second display works fine.

  If I boot up with connected monitor and log in (desktop distorted), 
disconnecting and connecting monitor does *not* help. After disconnecting the 
U3011, the builtin display is painted ok, but after connecting, it returns back 
to the incorrect state and both are rendered incorrectly.
  The only thing that helps recovering from this state seems to be 
disconnecting the second monitor, reboot, logging in and then connecting.

  Suspending to memory and waking up does not change the layout of the
  screen (neither fixes the "broken" one nor destroys the "good" one).

  Using a Guest session instead of my account does not fix my problem (I
  was hoping this was something screwed up in my .config).

  Switching to a Guest user account while I'm using both monitors in the
  good layout creates a session with a broken layout. Then logging out
  from Guest and switching back to my original session restores the good
  layout. The good layout seems to not be forgotten until I finish the
  session and logout. The bad layout is "created" whenever I start a new
  session with both monitors plugged in.

  BTW: I'm using a docking station - not sure if it is related - if you
  think it might be, I can try with connecting the monitor directly.

  I tried deleting ~/.compiz and ~/.config/compiz-1 directories but the problem 
remains.
  I also tried to go into the Displays configuration when everything is ok, 
apply the settings there (without any changes) in hope it will persist them 
somehow, but after restart it is broken again.

  I also tried reinstalling nvidia 331.89 drivers, because it complained
  about not being able to install nvidia-uvm during the upgrade process
  (reported separately), and now all nvidia packages installed cleanly.
  Before that I also got rid of all the ppa mainline kernels I had, just
  in case they mess something up.

  I remember the same problem happened on Ubuntu 14.04 when I tried to
  upgrade nvidia from ppa/xorg-edgers to 331.89, but then the easy
  workaround was to downgrade back to official 331.38. Now I have no
  choice :(

  Some other observations that may or may not be related to the problem,
  but I disclose them anyway, maybe they are helpful:

  * Notifications (e.g. network connection) displayed on the login
  screen in dual screen mode seem to be misplaced and instead of being
  painted in the upper right corner of one of the displays they get
  painted in some hard to logically explain position - neither at the
  center, nor in any corner.

  * The splash screen of IntelliJ IDEA (this is using Java / AWT
  probably) is also rendered in a strange position - below the center of
  the laptop screen, moved to the right (but not touching the edge),
  instead of exact center as it should be.

  * GMail notification just displayed at the moment when I'm writing it
  exactly at the left-lower corner of the bigger screen (U3011).

  * Nvidia settings lists only U3011 in the list of the devices
  (attached screenshot).

  * Ubuntu Display configuratio

[Touch-packages] [Bug 1385817] Re: initscripts package fails to upgrade if there are local init scripts on the system with no LSB headers

2015-02-02 Thread Brian Murray
** Changed in: sysvinit (Ubuntu)
   Importance: Critical => Medium

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

Title:
  initscripts package fails to upgrade if there are local init scripts
  on the system with no LSB headers

Status in Release Notes for Ubuntu:
  Triaged
Status in sysvinit package in Ubuntu:
  Triaged

Bug description:
  The dependency-based boot sequencing originally introduced upstream
  with Debian 6.0 is now always enabled in Ubuntu 14.10.

  For optimal sequencing, all init.d scripts should declare their
  dependencies in an LSB header. This is already the case for scripts
  shipped in Ubuntu, but users should check their local scripts and
  consider adding that information.

  For more information on this feature refer to the information
  available in /usr/share/doc/insserv/README.Debian.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: initscripts-2.88dsf 41ubuntu18
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux x86_64 3.13.0-37-generic
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sun October 26 2014 7:52:55
  DuplicateSignature: Package: initscripts: 2.88dsf-41ubuntu18: the 
post-installation script subprocess installed returned error exit status 1
  ErrorMessage: The post-install script subprocess installed returned error 
exit status 1
  InstallationDate: Installed on 2014-08-06 (80 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sysvinit
  Title: initscripts package 2.88dsf-41ubuntu18 failed to install / upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to utopic on 2014-10-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1385817/+subscriptions

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


[Touch-packages] [Bug 1399595] Re: systemd is activating swap twice, through both fstab and gpt generators

2015-02-02 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: Confirmed => Fix Released

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

Title:
  systemd is activating swap twice, through both fstab and gpt
  generators

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  systemd is activating swap twice, via its sda name and its uuid.

  It looks like it's because two swap units are being generated.

  
  # journalctl | grep swap | grep -v unit_create_cgroups
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb...
  Dec 05 04:30:40 yoga.lenovo swapon[396]: swapon: 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb: swapon failed: Device 
or resource busy
  Dec 05 04:30:40 yoga.lenovo systemd[1]: 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap swap 
process exited, code=exited status=255
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Failed to activate swap 
/dev/disk/by-uuid/73d341f1-eedc-43fc-9e53-ba4194dae3fb.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Unit 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap 
entered failed state.
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.
  Dec 05 04:30:40 yoga.lenovo kernel: Adding 8298492k swap on /dev/sda3.  
Priority:-1 extents:1 across:8298492k SSFS

  
  # systemctl status dev-sda3.swap 
  ● dev-sda3.swap - Swap Partition
 Loaded: loaded (/run/systemd/generator.late/dev-sda3.swap)
 Active: active since Fri 2014-12-05 04:30:40 EST; 27min ago
   What: /dev/sda3
   Docs: man:systemd-gpt-auto-generator(8)
Process: 395 ExecActivate=/sbin/swapon /dev/sda3 (code=exited, 
status=0/SUCCESS)

  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activating swap Swap Partition...
  Dec 05 04:30:40 yoga.lenovo systemd[1]: Activated swap Swap Partition.

  
  # systemctl status 
dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  ● dev-disk-byx2duuid-73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb.swap - 
/dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb
 Loaded: loaded
 Active: inactive (dead)
   What: /dev/disk/byx2duuid/73d341f1x2deedcx2d43fcx2d9e53x2dba4194dae3fb

  
  # swapon -s
  Filename  TypeSizeUsedPriority
  /dev/sda3 partition   8298492 0   
-1

  
  # blkid /dev/sda3
  /dev/sda3: UUID="73d341f1-eedc-43fc-9e53-ba4194dae3fb" TYPE="swap" 
PARTUUID="63a48c8a-8c88-482c-9577-50060d5afcb0"

  
  # find /run -name "*73d341f1*"
  
/run/systemd/generator/swap.target.wants/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  
/run/systemd/generator/dev-disk-by\x2duuid-73d341f1\x2deedc\x2d43fc\x2d9e53\x2dba4194dae3fb.swap
  /run/udev/links/\x2fdisk\x2fby-uuid\x2f73d341f1-eedc-43fc-9e53-ba4194dae3fb

  
  # find /run -name "*sda3*"
  /run/systemd/generator.late/swap.target.wants/dev-sda3.swap
  /run/systemd/generator.late/dev-sda3.swap

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 217-3ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: No such file 
or directory
  Date: Fri Dec  5 04:51:30 2014
  MachineType: LENOVO 20266
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic 
root=UUID=b51ee688-137c-47ec-9635-b69434b4e1f8 ro init=/lib/systemd/systemd 
ipv6.disable_ipv6=1
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN35WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN35WW:bd03/25/2014:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.journald.conf: 2014-10-17T14:43:13.493155

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1399595/+subscriptions

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

[Touch-packages] [Bug 1416423] Re: Reviews should be in chronological order with most recent first

2015-02-02 Thread Martin Albisetti
** Changed in: rnr-server
 Assignee: (unassigned) => Fabián Ezequiel Gallina (fgallina)

** Changed in: unity-scope-click (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Reviews should be in chronological order with most recent first

Status in Ratings and Reviews server:
  Triaged
Status in unity-scope-click package in Ubuntu:
  Invalid

Bug description:
  I think it'd make more sense for reviews to be ordered chronologically
  with the most recent reviews first, as these are most likely to be
  relevant to the current version of an app (currently they appear to be
  unordered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/rnr-server/+bug/1416423/+subscriptions

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


[Touch-packages] [Bug 1416423] Re: Reviews should be in chronological order with most recent first

2015-02-02 Thread Martin Albisetti
** Changed in: rnr-server
   Status: New => Triaged

** Changed in: rnr-server
   Importance: Undecided => Medium

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

Title:
  Reviews should be in chronological order with most recent first

Status in Ratings and Reviews server:
  Triaged
Status in unity-scope-click package in Ubuntu:
  Triaged

Bug description:
  I think it'd make more sense for reviews to be ordered chronologically
  with the most recent reviews first, as these are most likely to be
  relevant to the current version of an app (currently they appear to be
  unordered).

To manage notifications about this bug go to:
https://bugs.launchpad.net/rnr-server/+bug/1416423/+subscriptions

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


[Touch-packages] [Bug 1417232] [NEW] Rename 'overlayfs' module as per upstream name 'overlay'

2015-02-02 Thread Giuseppe Mazzotta
Public bug reported:

Module has been renamed upstream:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ef94b1864d1ed5be54376404bb23d22ed0481feb

The reason is that some distros might want to keep 2 modules, 'overlay'
and 'overlayfs'.

However this is not the case for the kernel shipped by Ubuntu; would it
be possible to support the new module name?

** Affects: linux-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: apport (Ubuntu) => linux-meta (Ubuntu)

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

Title:
  Rename 'overlayfs' module as per upstream name 'overlay'

Status in linux-meta package in Ubuntu:
  New

Bug description:
  Module has been renamed upstream:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ef94b1864d1ed5be54376404bb23d22ed0481feb

  The reason is that some distros might want to keep 2 modules,
  'overlay' and 'overlayfs'.

  However this is not the case for the kernel shipped by Ubuntu; would
  it be possible to support the new module name?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1417232/+subscriptions

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


[Touch-packages] [Bug 1417228] [NEW] Documentation bug in man rsyslogd

2015-02-02 Thread Giuseppe Mazzotta
Public bug reported:

This has been reported without any feedback to ubuntu-
ser...@lists.ubuntu.com.

Although minor, there is an issue in the man page for current rsyslogd
package in Ubuntu 14.04.1 LTS.

Regarding "-d" option, man page says:

--
  -d Turns  on  debug  mode.   Using this the daemon will not
proceed a fork(2) to set itself in the background, but opposite to
that stay in the
  foreground and write much debug information on the
current tty.  See the DEBUGGING section for more information.
--

This is a lie. Using the "-d" option alone will still fork rsyslog to
background.

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

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

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

Title:
  Documentation bug in man rsyslogd

Status in rsyslog package in Ubuntu:
  New

Bug description:
  This has been reported without any feedback to ubuntu-
  ser...@lists.ubuntu.com.

  Although minor, there is an issue in the man page for current rsyslogd
  package in Ubuntu 14.04.1 LTS.

  Regarding "-d" option, man page says:

  --
-d Turns  on  debug  mode.   Using this the daemon will not
  proceed a fork(2) to set itself in the background, but opposite to
  that stay in the
foreground and write much debug information on the
  current tty.  See the DEBUGGING section for more information.
  --

  This is a lie. Using the "-d" option alone will still fork rsyslog to
  background.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1417228/+subscriptions

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


[Touch-packages] [Bug 1417227] [NEW] Leaks hostname in XorgLog.txt

2015-02-02 Thread Fred
Public bug reported:

Apport uploads the file XorgLog.txt which contain;
[ 7.186] Current Operating System: Linux bunker15.example.gov 
3.18.0-12-generic #13-Ubuntu SMP Thu Jan 28 05:12:13 UTC 2015 x86_64

The hostname ought to be scrubbed by Apport.

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


** Tags: privacy

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

Title:
  Leaks hostname in XorgLog.txt

Status in apport package in Ubuntu:
  New

Bug description:
  Apport uploads the file XorgLog.txt which contain;
  [ 7.186] Current Operating System: Linux bunker15.example.gov 
3.18.0-12-generic #13-Ubuntu SMP Thu Jan 28 05:12:13 UTC 2015 x86_64

  The hostname ought to be scrubbed by Apport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1417227/+subscriptions

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


[Touch-packages] [Bug 1417225] [NEW] Leaks login username in CurrentDmesg.txt

2015-02-02 Thread Fred
Public bug reported:

Apport uploads the file CurrentDmesg.txt which may contain;
[   49.635156] systemd-logind[1465]: New session c2 of user alice.

The username ought to be replaced by Apport.

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


** Tags: privacy

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

Title:
  Leaks login username in CurrentDmesg.txt

Status in apport package in Ubuntu:
  New

Bug description:
  Apport uploads the file CurrentDmesg.txt which may contain;
  [   49.635156] systemd-logind[1465]: New session c2 of user alice.

  The username ought to be replaced by Apport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1417225/+subscriptions

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


[Touch-packages] [Bug 1415140] Re: fullscreen mode should be dynamic

2015-02-02 Thread Launchpad Bug Tracker
** Branch linked: lp:~artmello/gallery-app/gallery-app-
fullscreen_on_device

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

Title:
  fullscreen mode should be dynamic

Status in the base for Ubuntu mobile products:
  New
Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  New
Status in gallery-app package in Ubuntu RTM:
  New

Bug description:
  on touch, gallery is launched in fullscreen mode because previously
  there wasn't a way to dynamically toggle between fullscreen mode for
  different views within the app.

  The desired behavior on touch would be the following:

  - Don't launch app in fullscreen mode by default
  - Switch to fullscreen mode when viewing a photo (i.e. in slideshow mode)
  - When tapping on the photo to display the header we should switch out of 
fullscreen mode

  I think basically the rule would be when the header is visible we are
  not fullscreen and when the header is hidden (i.e. viewing pictures)
  the app should be in fullscreen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415140/+subscriptions

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


[Touch-packages] [Bug 1409133] Re: Heavy black flickering after VT switching on Intel graphics

2015-02-02 Thread Christopher M. Penalver
William Hua, the issue you are reporting is an upstream one. Could you
please report this problem to the appropriate mailing list (intel-
g...@lists.freedesktop.org) by following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you
have made it so that it may be tracked via http://vger.kernel.org/vger-
lists.html . It can take a day for the new e-mail to show up in the
respective archive.

Thank you for your understanding.

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

Title:
  Heavy black flickering after VT switching on Intel graphics

Status in Mir:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 
1, the demo server really flickers black quite a lot (entire screen, pointer 
included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic 
at the same time, if it's because of that, please mark invalid.
  --- 
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  william5932 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 3249CTO
  Package: mir
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.140
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Tags:  vivid
  Uname: Linux 3.18.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev 
sambashare sbuild sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET35WW (1.05 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1409133/+subscriptions

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


[Touch-packages] [Bug 1200906] Re: Apport detect a suspend/resume failure after a reboot

2015-02-02 Thread proteus
I am encountering a similar issue. It occured after an upgrade from
Ubuntu 12 to Ubuntu 14. Since the upgrade, the suspend/resume doesn't
work anymore.

I'm not sure what additional information you need (e.g. what details
about the hardware) - let me know how I can help. It is a self-built
system, with a Gygabyte GA-C847N mainboard and a Core i7-3770K CPU.

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

Title:
  Apport detect a suspend/resume failure after a reboot

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Apport summary was "[Hewlett-Packard HP EliteBook 8530p]
  suspend/resume failure"

  I was not comming back from suspend/resume, so this is probably an
  Apport error.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.10.0-2-generic 3.10.0-2.11
  ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0
  Uname: Linux 3.10.0-2-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nicolas1759 F pulseaudio
   /dev/snd/controlC0:  nicolas1759 F pulseaudio
  Date: Sat Jul 13 15:18:10 2013
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=7e493485-d08d-4944-8362-444f69fd1e08
  InstallationDate: Installed on 2013-07-10 (2 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130710)
  InterpreterPath: /usr/bin/python3.3
  MachineType: Hewlett-Packard HP EliteBook 8530p
  MarkForUpload: True
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic 
root=UUID=821ce4aa-35e4-436c-93cc-c8c2d9aba532 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.10.0-2-generic N/A
   linux-backports-modules-3.10.0-2-generic  N/A
   linux-firmware1.112
  SourcePackage: linux
  Title: [Hewlett-Packard HP EliteBook 8530p] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 12/08/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PDV Ver. F.11
  dmi.board.name: 30E7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 90.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PDVVer.F.11:bd12/08/2009:svnHewlett-Packard:pnHPEliteBook8530p:pvrF.11:rvnHewlett-Packard:rn30E7:rvrKBCVersion90.26:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8530p
  dmi.product.version: F.11
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1200906/+subscriptions

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


[Touch-packages] [Bug 1415753] Re: help asked

2015-02-02 Thread Brian Murray
Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker. We appreciate the difficulties you
are facing, but it would make more sense to raise problems you are
having in the support tracker at https://answers.launchpad.net/ubuntu if
you are uncertain if they are bugs. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs#When%20not%20to%20file%20a%20bug.

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/261583

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

Title:
  help asked

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I can't record my music to m SD card,at the beginnig and at the end
  when I use the computer.the screen who ask the password don't function
  correctly,it come back occasionnaly.the computer say me this is a spam
  in my boxletter who make that,but I think this is the system of the
  computer who is touch.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Jan 29 07:40:39 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.59, 3.13.0-40-generic, x86_64: installed
   ndiswrapper, 1.59, 3.13.0-41-generic, x86_64: installed
   ndiswrapper, 1.59, 3.13.0-43-generic, x86_64: installed
   ndiswrapper, 1.59, 3.13.0-44-generic, x86_64: installed
   ndiswrapper, 1.59, 3.13.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0649]
  InstallationDate: Installed on 2014-05-19 (254 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b337 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Packard Bell EasyNote TE11HC
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=c41f8877-7f18-4fb7-ac14-8934c002fa97 ro splash quiet drm.debug=0xe 
plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EG50_HC_HR
  dmi.board.vendor: Packard Bell
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.13
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.13:bd01/17/2013:svnPackardBell:pnEasyNoteTE11HC:pvrV2.13:rvnPackardBell:rnEG50_HC_HR:rvrType2-BoardVersion:cvnInsydeCorp.:ct10:cvrV2.13:
  dmi.product.name: EasyNote TE11HC
  dmi.product.version: V2.13
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Jan 29 07:20:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8940 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1415753/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post t

[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus

2015-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-system-settings -
0.3+15.04.20150130-0ubuntu1

---
ubuntu-system-settings (0.3+15.04.20150130-0ubuntu1) vivid; urgency=medium

  [ Ken VanDine ]
  * Use device-state from indicator-power to determine charging status.
QtSystemsInfo doesn't support UPower 0.99. (LP: #1416096)
 -- Ubuntu daily releaseFri, 30 Jan 2015 
22:53:18 +

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  expose battery charging state on the bus

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in indicator-power package in Ubuntu RTM:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show
  the right battery status.

  He needs it for bug 1329702. Since that's a proprietary bug that can't
  affect multiple projects, this is a separately filed ticket.

  Since this for the qml in u-s-s, this should be a GAction state
  similar to how auto-brightness' state is exposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions

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


[Touch-packages] [Bug 1408963] Re: [Kubuntu 14.10] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reas

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [Kubuntu 14.10] Network manager stops working: iwl3945 :03:00.0:
  BSM uCode verification failed at addr ...; wlan0: deauthenticating
  from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions

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


[Touch-packages] [Bug 1408963] Re: [Kubuntu 14.10] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reas

2015-02-02 Thread Helio Loureiro
This happens to me on 14.04 as well.

If I stop network-manager and connect directly via wpa_supplicant to
wireless router, it just works.

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

Title:
  [Kubuntu 14.10] Network manager stops working: iwl3945 :03:00.0:
  BSM uCode verification failed at addr ...; wlan0: deauthenticating
  from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions

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


[Touch-packages] [Bug 1408963] Re: [Kubuntu 14.10] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reas

2015-02-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Confirmed

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

Title:
  [Kubuntu 14.10] Network manager stops working: iwl3945 :03:00.0:
  BSM uCode verification failed at addr ...; wlan0: deauthenticating
  from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions

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


[Touch-packages] [Bug 1408963] Re: [Kubuntu 14.10] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reas

2015-02-02 Thread Helio Loureiro
I just forgot to mention it isn't probably related to wifi interface
since I've an Intel 6235 instead (kernel module iwlwifi).

5c:00.0 Network controller: Intel Corporation Centrino Advanced-N 6235
(rev 24)

I'm running on top o kernel 3.17.7.

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

Title:
  [Kubuntu 14.10] Network manager stops working: iwl3945 :03:00.0:
  BSM uCode verification failed at addr ...; wlan0: deauthenticating
  from... by local choice (Reason: 3=DEAUTH_LEAVING),

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  From time to time, the system loses all wireles networks and kubuntu
  network manager applet goes blank - not even one network is shown. All
  wifi connections are broken. Rebooting fixes the issue, switching to
  WICD on-the-fly enables to continue browsing without rebooting, so it
  seems to be no hardware issue or iwl3945 issue.

  What to expect: stable connections and flawless network managing.
  What happens: so above.

  Further informations about the system, the network configuration, the
  package version can be found in the attachment, also parts of rsyslog
  and dmesg.

  Interesting, according to some helpers, are the following lines:
  dmesg:   wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice 
(Reason: 3=DEAUTH_LEAVING)

  lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 14.10
  Release:14.10
  Codename:   utopic

  apt-cache policy network-manager
  network-manager:
    Installiert:   0.9.8.8-0ubuntu28
    Installationskandidat: 0.9.8.8-0ubuntu28
    Versionstabelle:
   *** 0.9.8.8-0ubuntu28 0
  500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+subscriptions

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


[Touch-packages] [Bug 1409133] Re: Heavy black flickering after VT switching on Intel graphics

2015-02-02 Thread Christopher M. Penalver
** Tags removed: needs-bisect
** Tags added: bisect-done

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Heavy black flickering after VT switching on Intel graphics

Status in Mir:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 
1, the demo server really flickers black quite a lot (entire screen, pointer 
included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic 
at the same time, if it's because of that, please mark invalid.
  --- 
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  william5932 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 3249CTO
  Package: mir
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.140
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Tags:  vivid
  Uname: Linux 3.18.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev 
sambashare sbuild sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET35WW (1.05 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1409133/+subscriptions

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


[Touch-packages] [Bug 1417192] Re: sometimes the keyboard is set to qwerty

2015-02-02 Thread Gunnar Hjalmarsson
Which input sources do you have in System Settings -> Text Entry?

** Package changed: lightdm (Ubuntu) => unity-control-center (Ubuntu)

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

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

Title:
  sometimes the keyboard is set to qwerty

Status in unity-control-center package in Ubuntu:
  Incomplete

Bug description:
  I'm french with azerty keyboard as first choice and greek kbd as
  second choice. Sometimes, after reboot, my kbd is set to qwerty, don't
  know why... by hiting the fr option in taskbar, I can't get the french
  kbd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1417192/+subscriptions

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


[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

2015-02-02 Thread franglais.125
I see, you are actually using 14.10. I'm on 14.04, that's a big
difference between our systems.

Good luck with the new bug report! Hopefully it will get fixed soon...

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

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in GNOME Screensaver:
  Invalid
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  [Test Case]

  Suspend and resume the computer (closing the lid or using the session
  indicator).  Since this problem involves a race condition, it is not
  reliably reproducable at will.

  [Regression Potential]

  This fix unmaps windows when a suspend or shutdown event occurs:  it
  is possible that the window(s) do not get remapped when a wake event
  occurs, or the wake even does not get propagated.  This does not
  appear to occur in practice.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been released in the Ubuntu "Vivid Vervet" development release
  for a couple of months with no apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+subscriptions

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


[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus

2015-02-02 Thread Launchpad Bug Tracker
This bug was fixed in the package indicator-power -
12.10.6+15.04.20150130-0ubuntu1

---
indicator-power (12.10.6+15.04.20150130-0ubuntu1) vivid; urgency=medium

  [ Charles Kerr ]
  * Publish the primary device's state for on the bus. (LP: #1416096)
 -- Ubuntu daily releaseFri, 30 Jan 2015 
22:51:49 +

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

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

Title:
  expose battery charging state on the bus

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-power package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu RTM:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show
  the right battery status.

  He needs it for bug 1329702. Since that's a proprietary bug that can't
  affect multiple projects, this is a separately filed ticket.

  Since this for the qml in u-s-s, this should be a GAction state
  similar to how auto-brightness' state is exposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions

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


[Touch-packages] [Bug 1302716] Re: webapp-container crashed with SIGABRT in qt_message_fatal()

2015-02-02 Thread David Barth
** Changed in: webbrowser-app (Ubuntu)
 Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned)

** Changed in: webbrowser-app (Ubuntu)
 Assignee: (unassigned) => Alexandre Abreu (abreu-alexandre)

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

Title:
  webapp-container crashed with SIGABRT in qt_message_fatal()

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  [Errors Bucket]
  https://errors.ubuntu.com/problem/04985f09fd55c083565c82ec0358799c46e5370b
  This is a regularly occurring problem.

  at install Lanchpad with Firefox webapp-container crashed

  ProblemType: CrashDistroRelease: Ubuntu 14.04
  Package: webapp-container 0.23+14.04.20140402-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2
  Uname: Linux 3.13.0-8-generic i686
  ApportVersion: 2.14-0ubuntu1
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Apr  4 19:04:01 2014
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2014-02-14 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140214)
  ProcCmdline: webapp-container --app-id=Launchpadlaunchpadnet 
--webapp=TGF1bmNocGFk --enable-back-forward
  Signal: 6SourcePackage: webbrowser-app
  StacktraceTop:
   QMessageLogger::fatal(char const*, ...) const () from 
/usr/lib/i386-linux-gnu/libQt5Core.so.5
   ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
   ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so
   QOpenGLContext::create() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5
   BrowserApplication::initialize(QString const&) ()
  Title: webapp-container crashed with SIGABRT in QMessageLogger::fatal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1302716/+subscriptions

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


[Touch-packages] [Bug 1417188] Re: Shell frozen/crashed on when alarm triggered

2015-02-02 Thread Bill Filler
** Attachment added: "_usr_bin_unity8.32011.crash"
   
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1417188/+attachment/4310605/+files/_usr_bin_unity8.32011.crash

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

** Summary changed:

- Shell frozen/crashed on when alarm triggered
+ Shell frozen/crashed when alarm triggered

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

** Changed in: indicator-datetime (Ubuntu)
   Importance: Undecided => Critical

** Also affects: canonical-devices-system-image
   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/1417188

Title:
  Shell frozen/crashed when alarm triggered

Status in the base for Ubuntu mobile products:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  rtm build 224 on krillin

  - I set an alarm for 9am with the clock app and then went to bed
  - The alarm was ringing in the morning
  - The phone screen was black
  - I pressed the power button to turn on the screen and there was no 
notification on the screen, just the greeter
  - The shell was completely frozen. I couldn't unlock or do anything, yet the 
alarm played on

  I had to hold down the power key to hard boot the phone as there was
  no way to silence the alarm, the volume keys were not working either.

  Found the attached crash file in /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417188/+subscriptions

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


[Touch-packages] [Bug 1417188] [NEW] Shell frozen/crashed when alarm triggered

2015-02-02 Thread Bill Filler
Public bug reported:

rtm build 224 on krillin

- I set an alarm for 9am with the clock app and then went to bed
- The alarm was ringing in the morning
- The phone screen was black
- I pressed the power button to turn on the screen and there was no 
notification on the screen, just the greeter
- The shell was completely frozen. I couldn't unlock or do anything, yet the 
alarm played on

I had to hold down the power key to hard boot the phone as there was no
way to silence the alarm, the volume keys were not working either.

Found the attached crash file in /var/crash

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

** Affects: indicator-datetime (Ubuntu)
 Importance: Critical
 Status: New

** Affects: unity8 (Ubuntu)
 Importance: Critical
 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/1417188

Title:
  Shell frozen/crashed when alarm triggered

Status in the base for Ubuntu mobile products:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  rtm build 224 on krillin

  - I set an alarm for 9am with the clock app and then went to bed
  - The alarm was ringing in the morning
  - The phone screen was black
  - I pressed the power button to turn on the screen and there was no 
notification on the screen, just the greeter
  - The shell was completely frozen. I couldn't unlock or do anything, yet the 
alarm played on

  I had to hold down the power key to hard boot the phone as there was
  no way to silence the alarm, the volume keys were not working either.

  Found the attached crash file in /var/crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1417188/+subscriptions

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


[Touch-packages] [Bug 1417192] [NEW] sometimes the keyboard is set to qwerty

2015-02-02 Thread D'hulst Dominique
Public bug reported:

I'm french with azerty keyboard as first choice and greek kbd as second
choice. Sometimes, after reboot, my kbd is set to qwerty, don't know
why... by hiting the fr option in taskbar, I can't get the french kbd.

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

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

Title:
  sometimes the keyboard is set to qwerty

Status in lightdm package in Ubuntu:
  New

Bug description:
  I'm french with azerty keyboard as first choice and greek kbd as
  second choice. Sometimes, after reboot, my kbd is set to qwerty, don't
  know why... by hiting the fr option in taskbar, I can't get the french
  kbd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1417192/+subscriptions

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


[Touch-packages] [Bug 1409133] Re: Heavy black flickering after VT switching on Intel graphics

2015-02-02 Thread William Hua
Kernel bisection yielded this as the culprit:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c51f71679042a5f388d9580ffbede14c897f1e86

Might try to bisect that branch, but it might be more difficult to test.

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

Title:
  Heavy black flickering after VT switching on Intel graphics

Status in Mir:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in mir package in Ubuntu:
  Confirmed

Bug description:
  After running mir_demo_server on VT 1, when I switch to VT 7 then back to VT 
1, the demo server really flickers black quite a lot (entire screen, pointer 
included). I'm not sure, but I also upgraded my kernel to 3.18.2-031802-generic 
at the same time, if it's because of that, please mark invalid.
  --- 
  ApportVersion: 2.15.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  william5932 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=f950febe-baf1-425c-8ab5-f4f43a86839b
  Lsusb:
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1)
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 3249CTO
  Package: mir
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.0-9-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash thinkpad_acpi.fan_control=Y 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-9-generic N/A
   linux-backports-modules-3.18.0-9-generic  N/A
   linux-firmware1.140
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  Tags:  vivid
  Uname: Linux 3.18.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip disk fuse kvm libvirtd lpadmin plugdev 
sambashare sbuild sudo video
  _MarkForUpload: True
  dmi.bios.date: 01/26/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET35WW (1.05 )
  dmi.board.name: 3249CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET35WW(1.05):bd01/26/2010:svnLENOVO:pn3249CTO:pvrThinkPadX201:rvnLENOVO:rn3249CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3249CTO
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1409133/+subscriptions

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


[Touch-packages] [Bug 1270579] Re: On laptops, screen brightness isn't memorized between sessions

2015-02-02 Thread Jorge Juan
I wrote a couple of upstart scripts to save and retore brightness
between bootups. I hope the scripts are smart enough to run unmodified
in any system with /sys/class/backlight.

You can find them at bitbucket with install instructions:

https://bitbucket.org/jjchico/upstart-brightness

Quick manual:

cd /etc/init
sudo wget 
https://bitbucket.org/jjchico/upstart-brightness/raw/d9a5d9484475eb1256d56c64b28e680a7aeae72c/brightness-store.conf
sudo wget 
https://bitbucket.org/jjchico/upstart-brightness/raw/d9a5d9484475eb1256d56c64b28e680a7aeae72c/brightness-restore.conf

Test reports and patches are wellcome (these are my first upstart
scripts).

Enjoy!

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

Title:
  On laptops, screen brightness isn't memorized between sessions

Status in elementary OS:
  Confirmed
Status in One Hundred Papercuts:
  Won't Fix
Status in The Linux Mint Distribution:
  Confirmed
Status in Upstart:
  Confirmed
Status in upstart package in Ubuntu:
  Won't Fix

Bug description:
  HOW TO REPRODUCE:
  1. Boot a laptop.
  2. Set a different screen brightness level.
  3. Reboot.

  RESULT:
  Backlight is not memorized.

  FIX:
  Into the "Terminal" application, enter the following lines one by one:
    - wget 
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1270579/+attachment/4288756/+files/upstart_brightness.tar.gz
    - sudo rm /etc/rc?.d/?25backlight /etc/init.d/brightness
    - sudo tar -zxvf upstart_brightness.tar.gz -C /
    - rm upstart_brightness.tar.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initscripts 2.88dsf-41ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic i686
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jan 19 17:20:26 2014
  InstallationDate: Installed on 2013-10-20 (91 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  SourcePackage: sysvinit
  UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/elementaryos/+bug/1270579/+subscriptions

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


[Touch-packages] [Bug 1128236] Re: Moving an icon on the launcher implies locking it

2015-02-02 Thread Andrea Azzarone
** This bug is no longer a duplicate of bug 808587
   Launcher - Unity should automatically select Keep In Launcher for icons that 
are sorted

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

** Changed in: unity
   Importance: Undecided => Wishlist

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

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

Title:
  Moving an icon on the launcher implies locking it

Status in Unity:
  Opinion
Status in unity package in Ubuntu:
  Opinion

Bug description:
  Steps to reproduce:
  1. Suppose that Gedit and Firefox are not locked on the launcher.
  2. Open Gedit and Firefox.
  3. Move the Gedit icon above/below the Firefox one.

  What I expect to happen?
  The Gedit icon should be above/below the Firefox one, and nothing else should 
have changed.

  What happens instead?
  The icon is correctly moved, however it is also locked.

  To be clear: with 'locked' here I mean that right-clicking the icon
  shows "Unlock from launcher", i.e. when I close Gedit, its icon is
  still on the launcher.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: unity 6.12.0daily13.02.08-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
  Uname: Linux 3.8.0-6-generic x86_64
  ApportVersion: 2.8-0ubuntu4
  Architecture: amd64
  CheckboxSubmission: 23d4ad9b5457fd302024f47052e863ca
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  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 Feb 17 17:54:05 2013
  InstallationDate: Installed on 2011-10-17 (489 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  SourcePackage: unity
  UpgradeStatus: Upgraded to raring on 2013-02-13 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1128236/+subscriptions

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


[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost

2015-02-02 Thread Michał Sawicz
Oh and yeah, if you reproduce the issue, grab unity8.log and
unity8-dash.log from ~/.cache/upstart/ and upload it somewhere.

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

Title:
  Edge gestures still get lost

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  There are still cases where edge gestures are lost. Over the christmas
  holidays It happened about 5 times to me (in 2 weeks). Only way to
  recover is to reboot the phone. It always happened while the phone was
  in my pocket. When pulling it out of the pocket the edge gestures
  (launcher and right edge) were gone. This is most likely related to
  random taps on the screen, maybe in combination with the display
  toggling on/off.

  Haven't found a way yet to manually trigger it. Will keep on trying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408263/+subscriptions

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


[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost

2015-02-02 Thread Michał Sawicz
I built touch-debug packages of unity8 to get as much output as possible
for this.

Interesting data point: playing music seems to trigger this more often -
suspicion is not allowing the device to fully suspend increases the
chance to get this bug.

To get the debug-enabled unity8:

$ wget http://people.canonical.com/~msawicz/unity8/touch-debug/repo-key.pub
$ gpg --home-dir /dev/null --with-fingerprint repo-key.pub
# verify fingerprint: C09A 0EA9 555F 5A80 D53B  EE1F 47EA 8F76 B005 9747
$ sudo apt-key add repo-key.pub
$ sudo apt update
$ sudo apt install unity8 unity8-common unity8-private
$ sudo reboot

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

Title:
  Edge gestures still get lost

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  There are still cases where edge gestures are lost. Over the christmas
  holidays It happened about 5 times to me (in 2 weeks). Only way to
  recover is to reboot the phone. It always happened while the phone was
  in my pocket. When pulling it out of the pocket the edge gestures
  (launcher and right edge) were gone. This is most likely related to
  random taps on the screen, maybe in combination with the display
  toggling on/off.

  Haven't found a way yet to manually trigger it. Will keep on trying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408263/+subscriptions

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


[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost

2015-02-02 Thread Michał Sawicz
D'oh, to actually add the repo, after adding the key:

$ sudo add-apt-repository "deb
http://people.canonical.com/~msawicz/unity8/touch-debug/ /"

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

Title:
  Edge gestures still get lost

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  There are still cases where edge gestures are lost. Over the christmas
  holidays It happened about 5 times to me (in 2 weeks). Only way to
  recover is to reboot the phone. It always happened while the phone was
  in my pocket. When pulling it out of the pocket the edge gestures
  (launcher and right edge) were gone. This is most likely related to
  random taps on the screen, maybe in combination with the display
  toggling on/off.

  Haven't found a way yet to manually trigger it. Will keep on trying.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408263/+subscriptions

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


[Touch-packages] [Bug 1416096] Re: expose battery charging state on the bus

2015-02-02 Thread Launchpad Bug Tracker
** Branch linked: lp:ubuntu/vivid-proposed/indicator-power

** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-system-settings

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

Title:
  expose battery charging state on the bus

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-power package in Ubuntu:
  In Progress
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in indicator-power package in Ubuntu RTM:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu RTM:
  In Progress

Bug description:
  Requested by kenvandine in #ubuntu-touch on freenode for u-s-s to show
  the right battery status.

  He needs it for bug 1329702. Since that's a proprietary bug that can't
  affect multiple projects, this is a separately filed ticket.

  Since this for the qml in u-s-s, this should be a GAction state
  similar to how auto-brightness' state is exposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1416096/+subscriptions

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


[Touch-packages] [Bug 1391368] Re: Thumbnail generation is slow when requesting a sourceSize that needs to be rescaled

2015-02-02 Thread Pat McGowan
** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Released

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

Title:
  Thumbnail generation is slow when requesting a sourceSize that needs
  to be rescaled

Status in the base for Ubuntu mobile products:
  Fix Released
Status in Thumbnail generator for all kinds of files:
  New
Status in thumbnailer package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu RTM:
  Fix Released

Bug description:
  The music app sets the "sourceSize" property of the Image component
  used for the Thumbnailer image provider. The values used are based on
  the size of the displayed image. For instance, on a Nexus 4  in the
  Music app's Albums tab this appears to be either "330" or "165"
  depending on if it is the full image or if is part of a quadrant/grid.
  However, setting the sourceSize to these values causes the
  thumbnailing processing to be extremely slow. Simply requesting that
  the source be 512 (which is the size of the xlarge) art is much faster
  --because I assume the image is not resized.

  One or both of the following could/should be done 1) the resizing
  needs to be made significantly faster, and/or 2) there needs to be an
  API that provides a property so users of the Thumbnailer can request
  sizes of 128 (normal), 256 (large), or 512 (xlarge). Hardcoding these
  values in the app would cause regression if the Thumbnailing service
  ever changed the corresponding default sizes.  Ideally I think both of
  these enhancements should be made.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391368/+subscriptions

-- 
Mailing list: https://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   >