[Touch-packages] [Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails

2015-02-20 Thread Martin Pitt
Notekeeping:

- installing self-built .debs: boot ok
- reinstalling ubuntu debs: boot fail
- Removing persistant journal (sudo rm -r /var/log/journal) with the ubuntu 
binaries: boot ok
- rebooting a few times with re-enabling persistant journal: boot ok
- QEMU with enabling persistant journal and booting a few times: bootok
- Didier has no persistant journal and got the issue once, so this only appears 
to change timing, not a fundamental thing

So now I need to figure out how to make boot fail again.

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

Title:
  219-1ubuntu1 regression: boot hangs, logind fails

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since yesterday, systemd does not boot properly any more. It takes
  very long, ends up in an X failsafe session, and eventually you just
  get a getty on VT1.

  Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
  https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the
  boot again.

  This happens both with the standard quiet splash $vt_handoff as well
  as without these tree options, i. e. text mode boot.

  $ sudo systemctl list-jobs
   JOB UNITTYPESTATE
  1634 sound.targetstopwaiting
  1176 NetworkManager.service  start   running
  1598 cgproxy.service start   waiting
  1632 failsafe-graphical.target   stopwaiting
  1563 alsa-restore.servicestart   waiting
  1594 plymouth-quit-wait.service  start   waiting
  1588 getty-static.servicestart   waiting
  1562 alsa-state.service  start   waiting
   121 systemd-update-utmp-runlevel.servicestart   waiting
  1640 ifup@wlan0.service  stopwaiting
  1544 systemd-ask-password-plymouth.path  start   waiting
  1507 friendly-recovery.service   start   waiting
  1607 anacron.service start   waiting
  1489 systemd-binfmt.service  start   waiting
  1637 system-systemd\x2drfkill.slice  stopwaiting
  1636 systemd-rfkill@rfkill1.service  stopwaiting
  1631 failsafe-x.service  stopwaiting
  1638 systemd-backlight@backlight:intel_backlight.service stopwaiting
  1610 pppd-dns.servicestart   waiting
  1483 systemd-machine-id-commit.service   start   waiting
  1635 system-systemd\x2dbacklight.slice   stopwaiting
  1557 systemd-hwdb-update.service start   waiting
  1630 systemd-backlight@backlight:acpi_video0.service stopwaiting
  1500 sys-kernel-config.mount start   waiting
    92 multi-user.target   start   waiting
  1509 debian-fixup.servicestart   waiting
  1641 systemd-rfkill@rfkill0.service  stopwaiting
  1613 plymouth-quit.service   start   waiting
  1639 system-ifup.slice   stopwaiting
  1642 ifup@lxcbr0.service stopwaiting
  1633 acpid.service   stopwaiting
  1643 systemd-logind.service  restart waiting
  1543 plymouth-start.service  start   waiting
  1499 plymouth-read-write.service start   waiting

  Attaching debug journal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-1ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 07:39:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (91 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141119)
  MachineType: LENOVO 2324CTO
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 init=/sbin/upstart
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 1421117] Re: fails to boot with Attempted to kill init in VMWare, absolute /sbin/init symlink does not work

2015-02-20 Thread Michael Bienia
I managed to some more output to the serial log (booted with
console=ttyS1,115200 only, no console=tty0):

starting version 219
[1.851984] sd 2:0:0:0: [sda] Assuming drive cache: write through
/init: line 307: chroot: not found
Target filesystem doesn't have requested /sbin/init.
/init: line 325: chroot: not found
/bin/sh: 0: Can't open splash
[2.909334] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00

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

Title:
  fails to boot with Attempted to kill init in VMWare, absolute
  /sbin/init symlink does not work

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after 
permanently switching to systemd.
  I've switched to systemd with apt install systemd-sysv --purge (it only 
purged the upstart package) and with the default Ubuntu entry the boot fails 
after about 2.5 sec with a kernel panic (Attempted to kill init). But it 
works when edit the grub entry (in the grub shell) and add 
init=/lib/systemd/systemd.

  Attached is the serial output (with debug but no init= parameter).

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

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


[Touch-packages] [Bug 1347638] Re: Launch1 button doesn't work on shortcuts

2015-02-20 Thread Massimo
Today I updated the system to Ubuntu 14.04.02.
The BUG # 1347638 is not solved.
Still it is possible to assign it (ThinkVantage) to a shortcut in the 
keyboard settings dialog, where it
shows up as Launch1, but it does not work - they shortcut is not activated by 
hitting that key.

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

Title:
  Launch1 button doesn't work on shortcuts

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

Bug description:
  Hardware: Thinkpad X230, but seemingly all Thinkpads.

  (Apologies if this is mis-characterized as a Unity bug - not sure
  where to put it)

  The special Thinkpad button, often called ThinkVantage button, used
  to work fine for keyboard shortcuts in 12.04, as configured in the
  keyboard settings panel.

  In 14.04 it is possible to assign it to a shortcut in the keyboard
  settings dialog, where it shows up as Launch1, but it doesn't work -
  they shortcut is not activated by hitting that key.

  The key appears to get through to the desktop and apps, because if I
  hit it while Emacs has focus it complains that nothing is assigned to
  XF86Launch1 (in 12.04 the key didn't get through to Emacs and there
  was no problem)

  Discussion of this, including some other's outputs, is here:
  http://ubuntuforums.org/showthread.php?t=890

  -

  xev gives this on keypress/release:

  MappingNotify event, serial 37, synthetic NO, window 0x0,
  request MappingKeyboard, first_keycode 8, count 248

  KeyPress event, serial 37, synthetic NO, window 0x401,
  root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758),
  state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x401,
  root 0xa2, subw 0x0, time 2883009, (-1684,706), root:(610,758),
  state 0x0, keycode 156 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False

  -

  acpi_listen gives:
  button/prog1 PROG1 0080  K

  -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.2+14.04.20140714-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,vpswitch,gnomecompat,mousepoll,session,move,obs,imgpng,snap,regex,animation,expo,ezoom,staticswitcher,workarounds,wall,fade,scale]
  CurrentDesktop: Unity
  Date: Wed Jul 23 08:11:18 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-07-11 (11 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1421117] Re: fails to boot with Attempted to kill init in VMWare, absolute /sbin/init symlink does not work

2015-02-20 Thread Martin Pitt
Michael confirmed on IRC that with an explicit ln -s busybox
${DESTDIR}/bin/chroot in /usr/share/initramfs-tools/hooks/busybox it
works. It's indeed a bit curious where the existing hardlink comes
from..

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided = Medium

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete = In Progress

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) = Martin Pitt (pitti)

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

Title:
  fails to boot with Attempted to kill init in VMWare, absolute
  /sbin/init symlink does not work

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after 
permanently switching to systemd.
  I've switched to systemd with apt install systemd-sysv --purge (it only 
purged the upstart package) and with the default Ubuntu entry the boot fails 
after about 2.5 sec with a kernel panic (Attempted to kill init). But it 
works when edit the grub entry (in the grub shell) and add 
init=/lib/systemd/systemd.

  Attached is the serial output (with debug but no init= parameter).

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

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


[Touch-packages] [Bug 1423752] Re: Sound Settings not opening from indicator

2015-02-20 Thread Elfy
clean installed - indicator working now

** Changed in: indicator-sound (Ubuntu)
   Status: New = Invalid

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

Title:
  Sound Settings not opening from indicator

Status in indicator-sound package in Ubuntu:
  Invalid

Bug description:
  Saw an update for indicator-sound just now .

  indicator-sound (12.10.2+15.04.20150205-0ubuntu1) vivid;
  urgency=medium

  Double checked that indicator-sound worked correctly.

  Updated and rebooted.

  Sound Settings no longer starts from indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb 19 23:39:35 2015
  InstallationDate: Installed on 2015-01-09 (41 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1421117] Re: fails to boot with Attempted to kill init in VMWare, absolute /sbin/init symlink does not work

2015-02-20 Thread Martin Pitt
FTR, that happens if busybox-static is *not* installed; that's in
ubuntu-standard, which explains why most people have it.

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

Title:
  fails to boot with Attempted to kill init in VMWare, absolute
  /sbin/init symlink does not work

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after 
permanently switching to systemd.
  I've switched to systemd with apt install systemd-sysv --purge (it only 
purged the upstart package) and with the default Ubuntu entry the boot fails 
after about 2.5 sec with a kernel panic (Attempted to kill init). But it 
works when edit the grub entry (in the grub shell) and add 
init=/lib/systemd/systemd.

  Attached is the serial output (with debug but no init= parameter).

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

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


[Touch-packages] [Bug 1423867] [NEW] init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on kvm

2015-02-20 Thread Didier Roche
Public bug reported:

if setting init=/lib/systemd/systemd-bootchart, this one doesn't
reexecute systemd as expected:

opening output file '/run/log/bootchart-timestamp': No such file or directory
opening output file '/run/log/bootchart-timestamp': No such file or directory
and then, triggers a kernel panic.

Had to use init='/lib/systemd/systemd-bootchart -i /lib/systemd/systemd'
to get it booting.

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

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

Title:
  init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on
  kvm

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  if setting init=/lib/systemd/systemd-bootchart, this one doesn't
  reexecute systemd as expected:

  opening output file '/run/log/bootchart-timestamp': No such file or 
directory
  opening output file '/run/log/bootchart-timestamp': No such file or 
directory
  and then, triggers a kernel panic.

  Had to use init='/lib/systemd/systemd-bootchart -i
  /lib/systemd/systemd' to get it booting.

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

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


[Touch-packages] [Bug 1423031] Re: NSS incorrectly preferring a longer, weaker chain over a shorter, stronger chain

2015-02-20 Thread Marco
tested on Ubuntu 14.04 , great it fixed the problem!

Thanks

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

Title:
  NSS incorrectly preferring a longer, weaker chain over a shorter,
  stronger chain

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Lucid:
  Fix Released
Status in nss source package in Precise:
  Fix Released
Status in nss source package in Trusty:
  Fix Released
Status in nss source package in Utopic:
  Fix Released
Status in nss source package in Vivid:
  Fix Released
Status in nss package in Debian:
  Confirmed

Bug description:
  See:

  https://code.google.com/p/chromium/issues/detail?id=437733

  and

  https://code.google.com/p/chromium/issues/detail?id=459131

  This issue is fixed in upstream libnss3 version = 3.17.4

  This issue causes incorrect SHA1 sunset behaviour in Google Chrome.

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

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


[Touch-packages] [Bug 1423867] Re: init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on kvm

2015-02-20 Thread Martin Pitt
** Changed in: systemd (Ubuntu)
   Status: New = Triaged

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

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

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

Title:
  init=/lib/systemd/systemd-bootchart on 219 triggers a kernel panic on
  kvm

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  if setting init=/lib/systemd/systemd-bootchart, this one doesn't
  reexecute systemd as expected:

  opening output file '/run/log/bootchart-timestamp': No such file or 
directory
  opening output file '/run/log/bootchart-timestamp': No such file or 
directory
  and then, triggers a kernel panic.

  Had to use init='/lib/systemd/systemd-bootchart -i
  /lib/systemd/systemd' to get it booting.

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

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


[Touch-packages] [Bug 1390474]

2015-02-20 Thread Raymond
Created attachment 113564
add SNDRV_PCM_INFO_BATCH when precise_ptr is not enabled

rme9652 driver need to specify SNDRV_PCM_INFO_BATCH when precise_ptr is
not enabled

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

Title:
  Volume element PCM has 6 channels. That's too much! - PA doesn't
  support elements with more than two channels

Status in PulseAudio sound server:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error Volume element PCM has 6 channels. That's too much! I can't handle 
that!  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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


[Touch-packages] [Bug 1390474]

2015-02-20 Thread Raymond
refer rme9652_hw_pointer() to rme9652.c

if (!rme9652-precise_ptr)
return (status  RME9652_buffer_id) ? period_size : 0;

if precise_ptr is not enabled by module parameter, it just return
pointer value as period_size or zero, this mean time scheduling should
be disabled since driver can only use two periods (impossible to rewind)

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

Title:
  Volume element PCM has 6 channels. That's too much! - PA doesn't
  support elements with more than two channels

Status in PulseAudio sound server:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error Volume element PCM has 6 channels. That's too much! I can't handle 
that!  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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


[Touch-packages] [Bug 1423837] Re: OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with systemimage.gpg.SignatureError

2015-02-20 Thread Oliver Grawert
this is fixed now, seemingly the channels.json file was edited by hand
and not by using system-image-shell on the server ... so the automatic
signing step teh shell usually does did not happen

** Changed in: system-image (Ubuntu)
 Assignee: (unassigned) = Steve Langasek (vorlon)

** Changed in: system-image (Ubuntu)
   Importance: Undecided = Critical

** Changed in: system-image (Ubuntu)
   Status: New = Fix Released

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

Title:
  OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with
  systemimage.gpg.SignatureError

Status in system-image package in Ubuntu:
  Fix Released

Bug description:
  OTA from 240 to 241 fails with the following error message in /var/log
  /system-image/client.log

  [systemimage] Feb 20 09:09:37 2015 (21576) check_for_update failed
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/systemimage/api.py, line 104, in 
check_for_update
  self._state.run_until('download_files')
File /usr/lib/python3/dist-packages/systemimage/state.py, line 175, in 
run_until
  step()
File /usr/lib/python3/dist-packages/systemimage/state.py, line 294, in 
_get_channel
  ctx.validate(asc_path, channels_path)
File /usr/lib/python3/dist-packages/systemimage/gpg.py, line 216, in 
validate
  self.keyring_paths, self.blacklist_path)
  systemimage.gpg.SignatureError: 
  sig path : b23d5b2a14027f6775f4012123f5e8c1
 /tmp/system-image-bk33lz3z/channels.json.asc
  data path: 2e42b9826ba73fb2b4a79e6769012c17
 /tmp/system-image-bk33lz3z/channels.json
  keyrings : ['45d56eb2cbc1394a6c3dd3e51d7a256c']
 ['/var/lib/system-image/keyrings/image-signing.tar.xz']
  blacklist: 573804b9f5149eaf253c8cbaa7ab1b83 
/var/lib/system-image/blacklist.tar.xz

  [systemimage] Feb 20 09:33:26 2015 (21576) test and acquire checking lock
  [systemimage] Feb 20 09:33:26 2015 (21576) checking lock not acquired

  
  And 241 is never visible for upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: system-image-common 2.5.1-0ubuntu1~rtm2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Feb 20 09:52:14 2015
  InstallationDate: Installed on 2015-02-18 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
  PackageArchitecture: all
  SourcePackage: system-image
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1422898] Re: Excessive CPU usage, even when the screen is turned off

2015-02-20 Thread Timo Jyrinki
Testing with

adb shell
sudo apt-add-repository ppa:ci-train-ppa-service/landing-021
sudo apt update
sudo apt dist-upgrade

Seems to show the linked branch greatly increases performance at least
on my mako.

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

Title:
  Excessive CPU usage, even when the screen is turned off

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Since mako image r102 (vivid-proposed), the CPU usage of Unity8 is very 
excessive and increasing over time.
  After boot, the phone runs smooth but after some time it lags heavily.

  As you can see from the attached output of the top command, Unity8
  consumes 23% of CPU power when the screen is TURNED OFF (command run
  via adb). When the screen is on, this figure is much higher and
  sometimes rises up to 60%.

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

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


[Touch-packages] [Bug 1423877] [NEW] shut down dialog shuts down when pressing cancel

2015-02-20 Thread Ori Avtalion
Public bug reported:

I'm using gnome-panel on 14.04.

When choosing Shut Down... from the menu, a dialog pops up asking me if I 
want to shut down.
If I press Cancel or press the 'x' button on the window, the system still 
shuts down.

The dialog window should respect my choice :)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubuntu-desktop 1.325
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 20 13:01:51 2015
InstallationDate: Installed on 2011-10-19 (1219 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
SourcePackage: ubuntu-meta
UpgradeStatus: Upgraded to trusty on 2014-04-18 (308 days ago)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  shut down dialog shuts down when pressing cancel

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I'm using gnome-panel on 14.04.

  When choosing Shut Down... from the menu, a dialog pops up asking me if I 
want to shut down.
  If I press Cancel or press the 'x' button on the window, the system still 
shuts down.

  The dialog window should respect my choice :)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-desktop 1.325
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 13:01:51 2015
  InstallationDate: Installed on 2011-10-19 (1219 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (308 days ago)

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

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


[Touch-packages] [Bug 1312882] Re: Main menu of Qt apps locally integrated in the window title bar disappears after activation of any menu item

2015-02-20 Thread Mateusz Stachowski
*** This bug is a duplicate of bug 1312137 ***
https://bugs.launchpad.net/bugs/1312137

This bug is resolved in Vivid the current development release.

Also this should be marked as duplicate of Bug #1312137 even if that bug
has less people affected because it has target assigned for the next
Trusty SRU and this one doesn't.

** This bug has been marked a duplicate of bug 1312137
   Local menus broken for Qt apps after opening dialog

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

Title:
  Main menu of Qt apps locally integrated in the window title bar
  disappears after activation of any menu item

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

Bug description:
  [The bug]
  When the integration of the app menus into the window title bars is turned 
on, call of any dialogue from the menu leads to disappearance of the menu. 
After that, the window title bar displays only the application title string. 
The main menu cannot be seen and cannot be accessed until you switch to another 
application and then return. The bug is observed only for unmaximized windows. 
The main menu of maximized windows works fine.
  This bug is observed only for Qt applications. I have “succeeded” to 
reproduce it for VLC, Gwenview, digiKam, Krita, Calliga, VirtualBox, 
GoldenDict, Mixx.

  [How to reproduce]
  1. Make sure that “Show the menus for a window” parameter (System Settings - 
Appearance - Behavior) is set to “In the window's title bar”.
  2. Start any Qt application, say, one of mentioned above. Let it be, for 
example, Gwenview.
  3. Unmaximize the app window.
  4. Activate any dialogue from the main menu. For instance, File - Open... or 
Settings - Configure Gwenview...
  5. Press Cancel to close the dialogue.
  6. Hover the mouse pointer over the window title bar.

  [What is expected]
  The app menu should appear and be accessible.

  [What happens]
  The app menu is not shown. Only the application title is displayed in the 
title bar.

  The following screencast shows the bug “in action”:
  http://www.youtube.com/watch?v=WAfJXmwDJpgfeature=youtu.be

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  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
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,imgjpeg,decor,snap,move,gnomecompat,imgpng,vpswitch,place,grid,resize,text,imgsvg,unitymtgrabhandles,regex,mousepoll,session,wall,animation,fade,expo,workarounds,scale,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Apr 25 22:38:19 2014
  InstallationDate: Installed on 2012-05-02 (723 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-04-21 (3 days ago)

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

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


[Touch-packages] [Bug 1423855] Re: Unity can't show the global menu item for some gnome apps

2015-02-20 Thread Stephen M. Webb
** Also affects: unity
   Importance: Undecided
   Status: New

** Changed in: unity
   Status: New = Triaged

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

** Changed in: unity
   Importance: Undecided = High

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

** Changed in: unity
 Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0)

** Changed in: unity
Milestone: None = 7.3.2

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

Title:
  Unity can't show the global menu item for some gnome apps

Status in Unity:
  Triaged
Status in unity package in Ubuntu:
  Triaged

Bug description:
  Unity can't show the global menu item for some gnome apps.

  For example, the 'terminal' menu for gnome-terminal, or the
  'calculator' menu for gnome-calculator cannot be opened.  Other menus
  can be displayed (file, edit,...)

  This is a recent regression I think.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Feb 20 21:14:01 2015
  InstallationDate: Installed on 2015-01-31 (20 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1421847] Re: No webcam video input ubuntu 14.04 x86_64

2015-02-20 Thread Jaufré Aligé
Hello again,

Sry I'm late.. It looks like it's fixed from Wednesday with kernel 3.13.0-46. 
I'm relieved !
My cams work again and my customer's too. I don't know what was done, I don't 
even know if it came from kernel package but it' looks fixed.

Thx,
Jaufré

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

** No longer affects: cheese (Ubuntu)

** No longer affects: guvcview (Ubuntu)

** Changed in: v4l-utils (Ubuntu)
   Status: New = Fix Released

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

Title:
  No webcam video input ubuntu 14.04 x86_64

Status in v4l-utils package in Ubuntu:
  Fix Released

Bug description:
  I tried different webcams on different machines with Ubuntu 14.04 x86,
  x86_64 and Ubuntu 14.10 x86_64.

  This is a BIG trouble : No video on 14.04 x86_64 systems !

  Latest tests :
  Ubuntu 14.04 x86_64
  Lowlatency Kernel and Generic kernel on a second machine.

  lsusb : Bus 003 Device 003: ID 093a:2621 Pixart Imaging, Inc. PAC731x Trust 
Webcam
  No image on /dev/video0

  vlc : main demux error: option v4l2-exposure does not exist
  guvcview : Could not grab image (select timeout): Resource temporarily 
unavailable
  cheese : no output
  skype : nothing

  Same cam pluged on my netbook under Ubuntu x86 : worked out of the box with 
the same softwares.
  Tried on a Ubuntu 14.10 x86_64 Laptop : perfect

  Two of my customers have the same problem with logitech webcams under
  Ubuntu 14.04 x86_64.

  Any idea ?
  I can't ask them to use normal versions with only 6 months lifetime !

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libv4l-0 1.0.1-1
  ProcVersionSignature: Ubuntu 3.13.0-46.75-lowlatency 3.13.11-ckt15
  Uname: Linux 3.13.0-46-lowlatency x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 13 22:16:16 2015
  InstallationDate: Installed on 2014-04-10 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410)
  SourcePackage: v4l-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1423886] [NEW] network-manager auto-connect to the wrong wifi network

2015-02-20 Thread Patrizio Bruno
Public bug reported:

I added a second access-point to my office, but I want that my ubuntu pc
still connects to the old access point, so I disabled  auto connect
for the new access point. When I boot the pc network-manager still
connects to the new access-point.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
Uname: Linux 3.16.0-29-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Feb 20 12:31:22 2015
IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.15.1 dev wlan1  proto static 
 192.168.15.0/24 dev wlan1  proto kernel  scope link  src 192.168.15.107  
metric 9 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to utopic on 2014-12-02 (79 days ago)
WpaSupplicantLog:
 
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
 eth5   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
 eth4   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: amd64 apport-bug gnome3-ppa third-party-packages utopic

** Attachment added: auto-connect off
   
https://bugs.launchpad.net/bugs/1423886/+attachment/4323222/+files/Schermata%20da%202015-02-20%2012%3A44%3A46.png

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

Title:
  network-manager auto-connect to the wrong wifi network

Status in network-manager package in Ubuntu:
  New

Bug description:
  I added a second access-point to my office, but I want that my ubuntu
  pc still connects to the old access point, so I disabled  auto
  connect  for the new access point. When I boot the pc network-manager
  still connects to the new access-point.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu28
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Feb 20 12:31:22 2015
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.15.1 dev wlan1  proto static 
   192.168.15.0/24 dev wlan1  proto kernel  scope link  src 192.168.15.107  
metric 9 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-12-02 (79 days ago)
  WpaSupplicantLog:
   
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   eth5   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth4   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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


[Touch-packages] [Bug 1423859] Re: package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 zurück

2015-02-20 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 colord in Ubuntu.
https://bugs.launchpad.net/bugs/1423859

Title:
  package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess
  neues pre-removal-Skript gab den Fehlerwert 143 zurück

Status in colord package in Ubuntu:
  New

Bug description:
  during apt update probably related to systemd sysv scripts not running
  (dbus and policykit)

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: colord 1.2.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 20 08:50:09 2015
  Dmesg:
   
  DuplicateSignature: package:colord:1.2.8-0ubuntu1:Unterprozess neues 
pre-removal-Skript gab den Fehlerwert 143 zurück
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 
zurück
  SourcePackage: colord
  Title: package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 143 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1423859] [NEW] package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 zurück

2015-02-20 Thread Josef Hopfgartner
Public bug reported:

during apt update probably related to systemd sysv scripts not running
(dbus and policykit)

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: colord 1.2.8-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Fri Feb 20 08:50:09 2015
Dmesg:
 
DuplicateSignature: package:colord:1.2.8-0ubuntu1:Unterprozess neues 
pre-removal-Skript gab den Fehlerwert 143 zurück
ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 
zurück
SourcePackage: colord
Title: package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 143 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package vivid

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

Title:
  package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess
  neues pre-removal-Skript gab den Fehlerwert 143 zurück

Status in colord package in Ubuntu:
  New

Bug description:
  during apt update probably related to systemd sysv scripts not running
  (dbus and policykit)

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: colord 1.2.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Fri Feb 20 08:50:09 2015
  Dmesg:
   
  DuplicateSignature: package:colord:1.2.8-0ubuntu1:Unterprozess neues 
pre-removal-Skript gab den Fehlerwert 143 zurück
  ErrorMessage: Unterprozess neues pre-removal-Skript gab den Fehlerwert 143 
zurück
  SourcePackage: colord
  Title: package colord 1.2.8-0ubuntu1 failed to install/upgrade: Unterprozess 
neues pre-removal-Skript gab den Fehlerwert 143 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1403867] Re: Desktop/wallpaper flickers dreadfully

2015-02-20 Thread Steven Pemberton
With the latest update of 14.10 this problem seems to be resolved.

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

Title:
  Desktop/wallpaper flickers dreadfully

Status in Unity:
  New
Status in unity package in Ubuntu:
  New

Bug description:
  Since 14.10 the only way to use the system is with apps full-screen,
  because the background/desktop is constantly flickering. If you close
  a window, it leaves flickering ghosts of itself, like a nightmare. See
  enclosed ogv file for an example.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2
  Uname: Linux 3.16.0-29-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,vpswitch,unitymtgrabhandles,grid,place,move,resize,regex,animation,expo,mousepoll,session,snap,gnomecompat,ezoom,wall,workarounds,fade,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Dec 18 13:45:17 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0344]
  InstallationDate: Installed on 2011-12-09 (1105 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  MachineType: Acer Aspire X3900
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic 
root=UUID=b7a5a606-5ebd-444b-8760-c11800be9c9e ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/16/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A3
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FIH57
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A3:bd12/16/2009:svnAcer:pnAspireX3900:pvr:rvnAcer:rnFIH57:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Aspire X3900
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Thu Dec 18 12:31:24 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1139 
   vendor SAM
  xserver.version: 2:1.16.0-1ubuntu1.2

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

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


[Touch-packages] [Bug 1390474]

2015-02-20 Thread David Henningsson
Thanks, so in fact the card is detected now.

The crackling looks like a driver problem but I'm not sure. You could
try to change this line in default.pa:

load-module module-udev-detect

to this:

load-module module-udev-detect tsched=0

...and try again.

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

Title:
  Volume element PCM has 6 channels. That's too much! - PA doesn't
  support elements with more than two channels

Status in PulseAudio sound server:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error Volume element PCM has 6 channels. That's too much! I can't handle 
that!  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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


[Touch-packages] [Bug 1422835] Re: Unity8 stucks in icon loading code

2015-02-20 Thread Albert Astals Cid
** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Unity8 stucks in icon loading code

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  With today updates (and qt 5.4) unity8-desktop freezes on start on my
  test machine, backtrace

  #0  0x7f9b3c209fef in qt_memfill32(unsigned int*, unsigned int, int) 
(__B=..., __A=0x7f9aca955700) at 
/usr/lib/gcc/x86_64-linux-gnu/4.9/include/emmintrin.h:1465
  #1  0x7f9b3c209fef in qt_memfill32(unsigned int*, unsigned int, int) 
(dest=optimized out, value=0, count=optimized out) at 
painting/qdrawhelper_sse2.cpp:272
  #2  0x7f9b3bf08915 in QRasterPlatformPixmap::fill(QColor const) 
(this=0x26251e0, color=...) at image/qpixmap_raster.cpp:211
  #3  0x7f9b3befcefc in QPixmap::fill(QColor const) 
(this=this@entry=0x7fff63823e30, color=...) at image/qpixmap.cpp:952
  #4  0x7f9afee1dbae in IconTheme::findBestIcon(QStringList const, int) 
(size=7519, filename=...) at unitythemeiconprovider.cpp:136
  #5  0x7f9afee1dbae in IconTheme::findBestIcon(QStringList const, int) 
(size=7519, iconName=..., this=0x21113e0) at unitythemeiconprovider.cpp:193
  #6  0x7f9afee1dbae in IconTheme::findBestIcon(QStringList const, int) 
(size=7519, iconName=..., this=0x21113e0) at unitythemeiconprovider.cpp:166
  #7  0x7f9afee1dbae in IconTheme::findBestIcon(QStringList const, int) 
(this=0x21113e0, names=..., size=size@entry=7519) at 
unitythemeiconprovider.cpp:54
  #8  0x7f9afee19905 in UnityThemeIconProvider::requestPixmap(QString 
const, QSize*, QSize const) (this=0x2110b70, id=..., size=0x7fff63824040, 
requestedSize=...)
  at unitythemeiconprovider.cpp:253
  #9  0x7f9b3b67db9b in QQuickPixmap::load(QQmlEngine*, QUrl const, QSize 
const, QFlagsQQuickPixmap::Option) () at 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5

  
  the icon it seems to try to load is 
/usr/share/icons/suru/status/scalable/battery-100.svg

  unity8 is eating cpu and the UI is not displaying (I see part of the
  lock screen, or the wizard if trying a new user, but can't interact
  with those)

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

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


[Touch-packages] [Bug 1416018] Re: Words in single quotes have the final quote removed by autocorrect

2015-02-20 Thread Launchpad Bug Tracker
** Branch linked: lp:~michael-sheldon/ubuntu-keyboard/fix-apostrophe-
preedit

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

Title:
  Words in single quotes have the final quote removed by autocorrect

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu Keyboard:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  Steps to reproduce:

  1) Type 'here' (including single quotes)

  2) Press space

  Expected result:

  'here'

  Actual result:

  'here

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

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


[Touch-packages] [Bug 1390474]

2015-02-20 Thread Bejjamin
tsched=0 !!!
That seems to do the trick! Pulseaudio 6.0 is running with every app 
simultaneously without a glitch! I will do more testing, but it looks perfect 
right now!

Thank you all!

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

Title:
  Volume element PCM has 6 channels. That's too much! - PA doesn't
  support elements with more than two channels

Status in PulseAudio sound server:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the 
error Volume element PCM has 6 channels. That's too much! I can't handle 
that!  and the card fails to show up in Sound Settings.
  Everything is fine with 24/48 mode (2 channels).

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

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


[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins

2015-02-20 Thread Didier Roche
ack with 0.2.13-3ubuntu3, please upload something depending on it and
I'll promote the needed parts.

** Changed in: grilo-plugins (Ubuntu)
   Status: Incomplete = Fix Committed

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

Title:
  [MIR] grilo-plugins

Status in grilo-plugins package in Ubuntu:
  Fix Committed

Bug description:
  Availability: In universe, builds on all archs

  Rational: grilo-plugins is now a dependency of totem and is hard to
  patch out. See lp:1393067

  Security: No known CVEs

  Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are
  feature requests. Active debian maintainer. Has watch file. Tests are
  run during build.

  UI standards: The package is translated upstream.

  Dependencies: All deps in main

  Standards compliance: No issues

  Maintenance: Actively maintained in debian. ubuntu-gnome team will
  subscribe in ubuntu.

  Background info: Grilo is a framework focused on making media
  discovery and browsing easy for application developers. This package
  contains it's plugins, including the tracker one, which is now needed
  by totem

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

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


[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

2015-02-20 Thread Yanpas
14.04.2 had been just released with new kernel 3.16 Is the big still
persists? And what is wicd? Package that fixes bug ?

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  Invalid
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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


[Touch-packages] [Bug 1422898] Re: Excessive CPU usage, even when the screen is turned off

2015-02-20 Thread Albert Astals Cid
** Changed in: unity8 (Ubuntu)
   Status: Confirmed = In Progress

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

Title:
  Excessive CPU usage, even when the screen is turned off

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Since mako image r102 (vivid-proposed), the CPU usage of Unity8 is very 
excessive and increasing over time.
  After boot, the phone runs smooth but after some time it lags heavily.

  As you can see from the attached output of the top command, Unity8
  consumes 23% of CPU power when the screen is TURNED OFF (command run
  via adb). When the screen is on, this figure is much higher and
  sometimes rises up to 60%.

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

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


[Touch-packages] [Bug 1423837] Re: OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with systemimage.gpg.SignatureError

2015-02-20 Thread Jean-Baptiste Lallement
** Attachment added: client.log
   
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1423837/+attachment/4323152/+files/client.log

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

Title:
  OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with
  systemimage.gpg.SignatureError

Status in system-image package in Ubuntu:
  New

Bug description:
  OTA from 240 to 241 fails with the following error message in /var/log
  /system-image/client.log

  [systemimage] Feb 20 09:09:37 2015 (21576) check_for_update failed
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/systemimage/api.py, line 104, in 
check_for_update
  self._state.run_until('download_files')
File /usr/lib/python3/dist-packages/systemimage/state.py, line 175, in 
run_until
  step()
File /usr/lib/python3/dist-packages/systemimage/state.py, line 294, in 
_get_channel
  ctx.validate(asc_path, channels_path)
File /usr/lib/python3/dist-packages/systemimage/gpg.py, line 216, in 
validate
  self.keyring_paths, self.blacklist_path)
  systemimage.gpg.SignatureError: 
  sig path : b23d5b2a14027f6775f4012123f5e8c1
 /tmp/system-image-bk33lz3z/channels.json.asc
  data path: 2e42b9826ba73fb2b4a79e6769012c17
 /tmp/system-image-bk33lz3z/channels.json
  keyrings : ['45d56eb2cbc1394a6c3dd3e51d7a256c']
 ['/var/lib/system-image/keyrings/image-signing.tar.xz']
  blacklist: 573804b9f5149eaf253c8cbaa7ab1b83 
/var/lib/system-image/blacklist.tar.xz

  [systemimage] Feb 20 09:33:26 2015 (21576) test and acquire checking lock
  [systemimage] Feb 20 09:33:26 2015 (21576) checking lock not acquired

  
  And 241 is never visible for upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: system-image-common 2.5.1-0ubuntu1~rtm2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Feb 20 09:52:14 2015
  InstallationDate: Installed on 2015-02-18 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
  PackageArchitecture: all
  SourcePackage: system-image
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1393542] Re: SRU: exfat not detected by blkid

2015-02-20 Thread Jarl
Can we expect to get a fix for this in Utopic?

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

Title:
   SRU: exfat not detected by blkid

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux source package in Trusty:
  Invalid
Status in util-linux source package in Utopic:
  Confirmed

Bug description:
  [Impact]

  Due to a upstream bug blkid is unable to detect exfat partitions. This
  breaks proper detection and automount of exfat formatted partitions
  (e.g. SD cards or USB sticks)  in Ubuntu 14.10.

  [Test Case]

  Insert an exfat formatted SD Card (card is neither detected nor automounted)
  or
  run as root: blkid [partition]

  [Regression Potential]

  None known, the bugfix is simple and part of already released upstream
  stable release (2.25.2).

  [Other Info]

  Bug reference: bug #1389021
  Upstream issue: https://github.com/karelzak/util-linux/issues/119
  Upstream bugfix commit: 
https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb

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

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


[Touch-packages] [Bug 1421117] Re: fails to boot with Attempted to kill init in VMWare, absolute /sbin/init symlink does not work

2015-02-20 Thread Martin Pitt
For the record, the chroot is done here:

# Work around absolute symlinks
if [ -d ${rootmnt} ]  [ -h ${rootmnt}${checktarget} ]; then
case $(readlink ${rootmnt}${checktarget}) in /*)
checktarget=$(chroot ${rootmnt} readlink 
${checktarget})
;;
esac
fi

So if chroot doesn't work, we would indeed fail if /sbin/init is an
absolute symlink. However, /sbin/chroot is supposed to exist in the
initramfs:

$ zcat /initrd.img |cpio -tv | grep chroot
-rwxr-xr-x 141 root root0 Oct 27 09:40 sbin/chroot

How does that look for you? Perhaps you have a different initramfs
config which skips that?

** Package changed: systemd (Ubuntu) = initramfs-tools (Ubuntu)

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

Title:
  fails to boot with Attempted to kill init in VMWare, absolute
  /sbin/init symlink does not work

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  My Ubuntu 15.04 VM (running under VMware) doesn't boot anymore after 
permanently switching to systemd.
  I've switched to systemd with apt install systemd-sysv --purge (it only 
purged the upstart package) and with the default Ubuntu entry the boot fails 
after about 2.5 sec with a kernel panic (Attempted to kill init). But it 
works when edit the grub entry (in the grub shell) and add 
init=/lib/systemd/systemd.

  Attached is the serial output (with debug but no init= parameter).

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

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


[Touch-packages] [Bug 1423825] [NEW] Ubuntu Touch dims screen backlight with Bluetooth keyboard in use

2015-02-20 Thread sokolgeo
Public bug reported:

I have latest Ubuntu Touch 15.04 (r101) installed on Nexus 7 Wifi
tablet.

When I have Bluetooth keyboard in use in, say, terminal application -
the system dims the screen after a short period of time as if system is
not in use. All this time I do use the system - just only via keyboard
input.

I believe this is the same when wired keyboard is plugged in via OTG
cable.

In summary: it seems like Ubuntu Touch does not currently register
hardware keyboard input as user interaction for the purpose of keeping
the high screen brightness and just dims the screen backlight as if
there is no user entry/interaction with the device, even when hardware
attached keyboard is used all the time.

The somehow ugly workaround is to open terminal window and key in: `$
powerd-cli display on bright` and then keep this terminal tab open all
the time while you use hardware attached keyboard. This will keep the
screen at full bright all the time.

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


** Tags: backlight hardware keyboard screen touch ubuntu

** Description changed:

  I have latest Ubuntu Touch 15.04 (r101) installed on Nexus 7 Wifi
  tablet.
  
  When I have Bluetooth keyboard in use in, say, terminal application -
  the system dims the screen after a short period of time as if system is
- not in use. If I touch screen at this moment - the screen brightness
- gets increased again. But then I keep working on keyboard only again and
- the screen dims again after a short while.
+ not in use. All this time I do use the system - just only via keyboard
+ input.
  
  I believe this is the same when wired keyboard is plugged in via OTG
  cable.
  
  In summary: it seems like Ubuntu Touch does not currently register
  hardware keyboard input as user interaction for the purpose of keeping
  the high screen brightness and just dims the screen backlight as if
  there is no user entry/interaction with the device, even when hardware
  attached keyboard is used all the time.
  
  The somehow ugly workaround is to open terminal window and key in: `$
  powerd-cli display on bright` and then keep this terminal tab open all
  the time while you use hardware attached keyboard. This will keep the
  screen at full bright all the time.

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

Title:
  Ubuntu Touch dims screen backlight with Bluetooth keyboard in use

Status in unity package in Ubuntu:
  New

Bug description:
  I have latest Ubuntu Touch 15.04 (r101) installed on Nexus 7 Wifi
  tablet.

  When I have Bluetooth keyboard in use in, say, terminal application -
  the system dims the screen after a short period of time as if system
  is not in use. All this time I do use the system - just only via
  keyboard input.

  I believe this is the same when wired keyboard is plugged in via OTG
  cable.

  In summary: it seems like Ubuntu Touch does not currently register
  hardware keyboard input as user interaction for the purpose of keeping
  the high screen brightness and just dims the screen backlight as if
  there is no user entry/interaction with the device, even when hardware
  attached keyboard is used all the time.

  The somehow ugly workaround is to open terminal window and key in: `$
  powerd-cli display on bright` and then keep this terminal tab open all
  the time while you use hardware attached keyboard. This will keep the
  screen at full bright all the time.

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

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


[Touch-packages] [Bug 1423810] Re: [krillin] apparmor fd_inheritance regression test causes kernel to crash

2015-02-20 Thread Steve Beattie
... and the unix_socket_unamed test:

phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo sh 
-c 'VERBOSE=1 bash unix_socket_unnamed.sh'
[sudo] password for phablet:
ok: AF_UNIX unnamed socket (stream); unconfined server
ok: AF_UNIX unnamed socket (stream); confined server (implicit perms)
ok: AF_UNIX unnamed socket (stream); confined server (explicit perms)
ok: AF_UNIX unnamed socket (stream); confined server (type)
ok: AF_UNIX unnamed socket (stream); confined server (addr)
ok: AF_UNIX unnamed socket (stream); confined server (peer label w/ implicit 
perms)
ok: AF_UNIX unnamed socket (stream); confined server (peer label w/ explicit 
perms)
ok: AF_UNIX unnamed socket (stream); confined server (type, addr)
ok: AF_UNIX unnamed socket (stream); confined server (type, addr, peer label)
ok: AF_UNIX unnamed socket (stream); confined server (no unix rule)
ok: AF_UNIX unnamed socket (stream); confined server (missing perm: create)
ok: AF_UNIX unnamed socket (stream); confined server (missing perm: getopt)
ok: AF_UNIX unnamed socket (stream); confined server (missing perm: setopt)
ok: AF_UNIX unnamed socket (stream); confined server (missing perm: shutdown)
ok: AF_UNIX unnamed socket (stream); confined server (missing perm: read)
ok: AF_UNIX unnamed socket (stream); confined server (missing perm: write)
ok: AF_UNIX unnamed socket (stream); confined server (bad type)
ok: AF_UNIX unnamed socket (stream); confined server (bad addr)
ok: AF_UNIX unnamed socket (stream); confined server (bad peer label)
ok: AF_UNIX unnamed socket (stream); unconfined client
ok: AF_UNIX unnamed socket (stream); confined client (implicit perms)
ok: AF_UNIX unnamed socket (stream); confined client (explicit perms)
ok: AF_UNIX unnamed socket (stream); confined client (type)
ok: AF_UNIX unnamed socket (stream); confined client (peer label w/ implicit 
perms)
ok: AF_UNIX unnamed socket (stream); confined client (peer label w/ explicit 
perms)
ok: AF_UNIX unnamed socket (stream); confined client (peer addr)
ok: AF_UNIX unnamed socket (stream); confined client (peer label, peer addr)
ok: AF_UNIX unnamed socket (stream); confined client (type, peer label, peer 
addr)
ok: AF_UNIX unnamed socket (stream); confined client (no unix rule)
ok: AF_UNIX unnamed socket (stream); confined client (missing perm: getopt)
ok: AF_UNIX unnamed socket (stream); confined client (missing perm: setopt)
ok: AF_UNIX unnamed socket (stream); confined client (missing perm: getattr)

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

Title:
  [krillin] apparmor fd_inheritance regression test causes kernel to
  crash

Status in apparmor package in Ubuntu:
  New

Bug description:
  On krillin with vivid-proposed, running the fd_inheritance test from
  the apparmor regression tests causes the kernel to crash and
  spontaneously reboot the device:

  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ logger 
running fd_inheritance tests now
  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo 
sh -c 'VERBOSE=1 bash fd_inheritance.sh'
  ok: fd inheritance; unconfined - unconfined
  ok: fd inheritance; confined - unconfined
  ok: fd inheritance; confined (bad perm) - unconfined
  ok: fd inheritance; confined (no perm) - unconfined
  ok: fd inheritance; unconfined - confined
  ok: fd inheritance; unconfined - confined (no perm)
  ok: fd inheritance; confined - confined
  ok: fd inheritance; confined (bad perm) - confined
  ok: fd inheritance; confined (no perm) - confined
  ok: fd inheritance; confined - confined (bad perm)
  [device reboots here]

  This is what syslog sees before it falls over, though nothing after the 
logger invocation makes it to the disk:
  Feb 20 03:51:47 ubuntu-phablet phablet: running fd_inheritance tests now
  Feb 20 03:52:05 ubuntu-phablet kernel: [  489.942611]type=1400 
audit(1424404325.798:141): apparmor=STATUS operation=profile_load 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7449 comm=apparmor_parser
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.272023]type=1400 
audit(1424404326.128:142): apparmor=STATUS operation=profile_replace 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7477 comm=apparmor_parser
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.305028]type=1400 
audit(1424404326.158:143): apparmor=DENIED operation=open 
profile=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 name=/tmp/sdtest.7416-27080-LFDs8z/file pid=7483 comm=fd_inheritance 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.573275]type=1400 
audit(1424404326.428:144): apparmor=STATUS operation=profile_replace 
profile=unconfined 

[Touch-packages] [Bug 1333140] Re: Fix udev rules to consider mmc rpmb partitions

2015-02-20 Thread MitraX
The issue also affects Ubuntu 14.10 installed on 32GB eMMC (built-in
instead of hard disk) on Acer Aspire ES1-111M.

Will the fix be released for Utopic Unicorn, too?

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

Title:
  Fix udev rules to consider mmc rpmb partitions

Status in systemd package in Ubuntu:
  Fix Released
Status in udev package in Ubuntu:
  Invalid
Status in udisks package in Ubuntu:
  Triaged
Status in udev source package in Precise:
  Triaged
Status in udisks source package in Precise:
  Confirmed
Status in systemd source package in Trusty:
  Fix Committed
Status in udisks source package in Trusty:
  Confirmed

Bug description:
  As per JEDEC 4.5 spec for eMMC devices,
  There is a new partitions as part of eMMC storage devices it self. (Further 
details please refer eMMC spec)

  *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
  with mmcblkXrpmb if device expresses it support of RPMB.

  Issues observed:

  issue 1:
  RPMB (Replay Protected Memory Block), A signed access to a Replay Protected 
Memory Block is provided. This function provides means for the system to store 
data to the specific memory area in an authenticated and replay protected 
manner.
  In that case, any read/write access to this partition device will report 
errors.

  issue 2:
  The by-path, line is wrongly mapping to platform-sdhci-tegra.1  - 
mmcblk2rpmb were as
  it should be platform-sdhci-tegra.1  - mmcblk2

  ls -l /dev/disk/by-path/
  total 0
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.1 - 
../../mmcblk2rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.1-part1 - 
../../mmcblk2p1
  lrwxrwxrwx 1 root root 13 Jan  3  2000 platform-sdhci-tegra.2 - ../../mmcblk1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.2-part1 - 
../../mmcblk1p1
  lrwxrwxrwx 1 root root 17 Jan  3  2000 platform-sdhci-tegra.3 - 
../../mmcblk0rpmb
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part1 - 
../../mmcblk0p1
  lrwxrwxrwx 1 root root 15 Jan  3  2000 platform-sdhci-tegra.3-part2 - 
../../mmcblk0p2

  We have locally resolved in our platform in this file 60-persistent-
  storage.rules

  For issue 1: (with this rule)
  # skip block read for partitions of type rpmb
  KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end

  For issue 2:
  ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb, 
SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb
  ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb, 
SYMLINK+=disk/by-path/$env{ID_PATH}

  Please consider this issues fix in next udev release .

  
  SRU INFO: This is mostly an issue with running backported kernels on 12.04 
and 14.04. There is no test case which would reproduce this on arbitrary 
hardware, but there are several reporters which are in a position to verify a 
proposed update.

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

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


[Touch-packages] [Bug 1423837] [NEW] OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with systemimage.gpg.SignatureError

2015-02-20 Thread Jean-Baptiste Lallement
Public bug reported:

OTA from 240 to 241 fails with the following error message in /var/log
/system-image/client.log

[systemimage] Feb 20 09:09:37 2015 (21576) check_for_update failed
Traceback (most recent call last):
  File /usr/lib/python3/dist-packages/systemimage/api.py, line 104, in 
check_for_update
self._state.run_until('download_files')
  File /usr/lib/python3/dist-packages/systemimage/state.py, line 175, in 
run_until
step()
  File /usr/lib/python3/dist-packages/systemimage/state.py, line 294, in 
_get_channel
ctx.validate(asc_path, channels_path)
  File /usr/lib/python3/dist-packages/systemimage/gpg.py, line 216, in 
validate
self.keyring_paths, self.blacklist_path)
systemimage.gpg.SignatureError: 
sig path : b23d5b2a14027f6775f4012123f5e8c1
   /tmp/system-image-bk33lz3z/channels.json.asc
data path: 2e42b9826ba73fb2b4a79e6769012c17
   /tmp/system-image-bk33lz3z/channels.json
keyrings : ['45d56eb2cbc1394a6c3dd3e51d7a256c']
   ['/var/lib/system-image/keyrings/image-signing.tar.xz']
blacklist: 573804b9f5149eaf253c8cbaa7ab1b83 
/var/lib/system-image/blacklist.tar.xz

[systemimage] Feb 20 09:33:26 2015 (21576) test and acquire checking lock
[systemimage] Feb 20 09:33:26 2015 (21576) checking lock not acquired


And 241 is never visible for upgrade.

ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: system-image-common 2.5.1-0ubuntu1~rtm2
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Fri Feb 20 09:52:14 2015
InstallationDate: Installed on 2015-02-18 (1 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
PackageArchitecture: all
SourcePackage: system-image
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: system-image (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug armhf utopic

** Summary changed:

- OTA from 240 to 241 fails with systemimage.gpg.SignatureError
+ OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with 
systemimage.gpg.SignatureError

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

Title:
  OTA of rtm/14.09-proposed/krillin from 240 to 241 fails with
  systemimage.gpg.SignatureError

Status in system-image package in Ubuntu:
  New

Bug description:
  OTA from 240 to 241 fails with the following error message in /var/log
  /system-image/client.log

  [systemimage] Feb 20 09:09:37 2015 (21576) check_for_update failed
  Traceback (most recent call last):
File /usr/lib/python3/dist-packages/systemimage/api.py, line 104, in 
check_for_update
  self._state.run_until('download_files')
File /usr/lib/python3/dist-packages/systemimage/state.py, line 175, in 
run_until
  step()
File /usr/lib/python3/dist-packages/systemimage/state.py, line 294, in 
_get_channel
  ctx.validate(asc_path, channels_path)
File /usr/lib/python3/dist-packages/systemimage/gpg.py, line 216, in 
validate
  self.keyring_paths, self.blacklist_path)
  systemimage.gpg.SignatureError: 
  sig path : b23d5b2a14027f6775f4012123f5e8c1
 /tmp/system-image-bk33lz3z/channels.json.asc
  data path: 2e42b9826ba73fb2b4a79e6769012c17
 /tmp/system-image-bk33lz3z/channels.json
  keyrings : ['45d56eb2cbc1394a6c3dd3e51d7a256c']
 ['/var/lib/system-image/keyrings/image-signing.tar.xz']
  blacklist: 573804b9f5149eaf253c8cbaa7ab1b83 
/var/lib/system-image/blacklist.tar.xz

  [systemimage] Feb 20 09:33:26 2015 (21576) test and acquire checking lock
  [systemimage] Feb 20 09:33:26 2015 (21576) checking lock not acquired

  
  And 241 is never visible for upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: system-image-common 2.5.1-0ubuntu1~rtm2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Fri Feb 20 09:52:14 2015
  InstallationDate: Installed on 2015-02-18 (1 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20150218-184321)
  PackageArchitecture: all
  SourcePackage: system-image
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1287361] Re: add support for keyboard shortcuts

2015-02-20 Thread Giorgio Venturi
** Changed in: ubuntu-ux
 Assignee: (unassigned) = Giorgio Venturi (giorgio-venturi)

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

Title:
  add support for keyboard shortcuts

Status in Ubuntu UX bugs:
  New
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1287361/+subscriptions

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


[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock

2015-02-20 Thread Burko
After another ~2 days and a bunch of hibernations I can confirm that
uninstalling Light-locker did the trick for me. I experienced absolutely
no problems in whatsoever. It even fixed two other bugs related to
login here.

Thanks again!

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

Title:
  After locking screen there is no input field to type password for
  unlock

Status in Unity:
  Fix Released
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released

Bug description:
  *** IMPORTANT **

  *** The fix is not included in TRUSTY. Will be included with next SRU.
  ***

  If you can reproduce this bug please be sure to provide the following info:
  1. Do you use a multi-head setup? If yes, using just one monitor fixes the 
issue?
  2. Can you reproduce all the time?
  3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see 
comment #115) can you still reproduce that?
  4. Please consider posting /var/log/auth.log (at least part of it, should not 
contain sensitive information)
  5. Please specify the unity version
  *** END IMPORTANT **

  Sometimes (but not always) after locking the screen there is the
  situation not having any input field where I can type the password to
  unlock the session again. The shaded gray area simply does not have
  the input field. I can't do anything, I have to switch to text console
  and stop/start lightdm service to cure the problem loosing all of my
  session :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Apr 22 22:17:57 2014
  InstallationDate: Installed on 2012-03-03 (780 days ago)
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)

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

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


[Touch-packages] [Bug 1423573] Re: Frequent launcher freezes on Krillin

2015-02-20 Thread Michael Zanetti
Joe, could this be a dupe of this? https://bugs.launchpad.net/ubuntu-
rtm/+source/unity8/+bug/1408266

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

Title:
  Frequent launcher freezes on Krillin

Status in unity8 package in Ubuntu:
  New

Bug description:
  Over the last few releases I have noticed that the launcher often
  freezes when it is 'pulled' onscreen.

  This manifests itself by you not being able to scroll the launcher
  content up and down (you need to have enough apps on the launcher to
  make it 'overflow').

  Closing the launcher and waiting for 15+ seconds or so usually cures
  the problem however sometimes it requires a restart.

  Unfortunately there does not seem to be any pattern as to which apps
  are running for this to happen.

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

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


[Touch-packages] [Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails

2015-02-20 Thread Martin Pitt
I can reproduce this quite reliably with:

  sudo rm -r /var/log/journal
  sudo mkdir /var/log/journal
  sudo apt-get install --reinstall systemd

I now managed to reproduce the hang in a VM as well, with these
commands.

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

Title:
  219-1ubuntu1 regression: boot hangs, logind fails

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since yesterday, systemd does not boot properly any more. It takes
  very long, ends up in an X failsafe session, and eventually you just
  get a getty on VT1.

  Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
  https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the
  boot again.

  This happens both with the standard quiet splash $vt_handoff as well
  as without these tree options, i. e. text mode boot.

  $ sudo systemctl list-jobs
   JOB UNITTYPESTATE
  1634 sound.targetstopwaiting
  1176 NetworkManager.service  start   running
  1598 cgproxy.service start   waiting
  1632 failsafe-graphical.target   stopwaiting
  1563 alsa-restore.servicestart   waiting
  1594 plymouth-quit-wait.service  start   waiting
  1588 getty-static.servicestart   waiting
  1562 alsa-state.service  start   waiting
   121 systemd-update-utmp-runlevel.servicestart   waiting
  1640 ifup@wlan0.service  stopwaiting
  1544 systemd-ask-password-plymouth.path  start   waiting
  1507 friendly-recovery.service   start   waiting
  1607 anacron.service start   waiting
  1489 systemd-binfmt.service  start   waiting
  1637 system-systemd\x2drfkill.slice  stopwaiting
  1636 systemd-rfkill@rfkill1.service  stopwaiting
  1631 failsafe-x.service  stopwaiting
  1638 systemd-backlight@backlight:intel_backlight.service stopwaiting
  1610 pppd-dns.servicestart   waiting
  1483 systemd-machine-id-commit.service   start   waiting
  1635 system-systemd\x2dbacklight.slice   stopwaiting
  1557 systemd-hwdb-update.service start   waiting
  1630 systemd-backlight@backlight:acpi_video0.service stopwaiting
  1500 sys-kernel-config.mount start   waiting
    92 multi-user.target   start   waiting
  1509 debian-fixup.servicestart   waiting
  1641 systemd-rfkill@rfkill0.service  stopwaiting
  1613 plymouth-quit.service   start   waiting
  1639 system-ifup.slice   stopwaiting
  1642 ifup@lxcbr0.service stopwaiting
  1633 acpid.service   stopwaiting
  1643 systemd-logind.service  restart waiting
  1543 plymouth-start.service  start   waiting
  1499 plymouth-read-write.service start   waiting

  Attaching debug journal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-1ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 07:39:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (91 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141119)
  MachineType: LENOVO 2324CTO
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 init=/sbin/upstart
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET95WW(2.55):bd07/09/2013:svnLENOVO:pn2324CTO:pvrThinkPadX230:rvnLENOVO:rn2324CTO:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324CTO
  dmi.product.version: ThinkPad X230
  

[Touch-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)

2015-02-20 Thread Jarl
@osaier and everyone else on Utopic. If you are affected by this, then
you should also mark yourself as affected by bug #1393542 as mentioned
in comment #7

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

Title:
  Does not detect hotplugged storage device (exfat)

Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  It used to work then stopped for some reason.

  Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x7c367968

  Device Boot Start   End   Sectors   Size Id Type
  /dev/sdb1  63 488392064 488392002 232.9G  7 HPFS/NTFS/exFAT

  
  exfatfsck /dev/sdb1 finds no error

  mount -t exfat works, it's just auto-mounting that doesn't. 
  '-t' is required though, not sure if that's normal:
  mount: /dev/sdb1: more filesystems detected. This should not happen,
 use -t type to explicitly specify the filesystem type or
 use wipefs(8) to clean up the device.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: gvfs 1.20.2-1ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  4 00:39:03 2014
  HotplugNewDevices: /dev/sdb1 /dev/sdb
  HotplugNewMounts:
   
  InstallationDate: Installed on 2014-10-03 (31 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gvfs
  Symptom: storage
  Title: Does not detect hotplugged storage device
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago)

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

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


[Touch-packages] [Bug 1287361] Re: add support for keyboard shortcuts

2015-02-20 Thread Giorgio Venturi
On desktop  tablet, the order of tabs will not change

https://docs.google.com/a/canonical.com/presentation/d/1ggKmkxUFR5xCBcvkjJ4On9b4iKzEqcycz4hjc16tBGo/edit#slide=id.g2bb58620d_040

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

Title:
  add support for keyboard shortcuts

Status in Ubuntu UX bugs:
  New
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1287361/+subscriptions

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


[Touch-packages] [Bug 1422898] Re: Excessive CPU usage, even when the screen is turned off

2015-02-20 Thread Albert Astals Cid
** Branch linked: lp:~aacid/qtmir/timer_thread

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

Title:
  Excessive CPU usage, even when the screen is turned off

Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  Since mako image r102 (vivid-proposed), the CPU usage of Unity8 is very 
excessive and increasing over time.
  After boot, the phone runs smooth but after some time it lags heavily.

  As you can see from the attached output of the top command, Unity8
  consumes 23% of CPU power when the screen is TURNED OFF (command run
  via adb). When the screen is on, this figure is much higher and
  sometimes rises up to 60%.

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

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


[Touch-packages] [Bug 1287361] Re: add support for keyboard shortcuts

2015-02-20 Thread Giorgio Venturi
** Changed in: ubuntu-ux
   Status: New = In Progress

** Changed in: ubuntu-ux
   Importance: Undecided = Medium

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

Title:
  add support for keyboard shortcuts

Status in Ubuntu UX bugs:
  In Progress
Status in Web Browser App:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1287361/+subscriptions

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


[Touch-packages] [Bug 1423855] [NEW] Unity can't show the global menu item for some gnome apps

2015-02-20 Thread Michael Blennerhassett
Public bug reported:

Unity can't show the global menu item for some gnome apps.

For example, the 'terminal' menu for gnome-terminal, or the 'calculator'
menu for gnome-calculator cannot be opened.  Other menus can be
displayed (file, edit,...)

This is a recent regression I think.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Feb 20 21:14:01 2015
InstallationDate: Installed on 2015-01-31 (20 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Unity can't show the global menu item for some gnome apps

Status in unity package in Ubuntu:
  New

Bug description:
  Unity can't show the global menu item for some gnome apps.

  For example, the 'terminal' menu for gnome-terminal, or the
  'calculator' menu for gnome-calculator cannot be opened.  Other menus
  can be displayed (file, edit,...)

  This is a recent regression I think.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.1+15.04.20150219.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Feb 20 21:14:01 2015
  InstallationDate: Installed on 2015-01-31 (20 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1412352] Re: Crash in scopes run time if scope throws exception from PreviewQueryBase::run()

2015-02-20 Thread Pete Woods
** Branch linked: lp:~unity-api-team/unity-scopes-api/RTM-plus-306

** Changed in: unity-scopes-api (Ubuntu RTM)
   Status: New = In Progress

** Changed in: unity-scopes-api (Ubuntu RTM)
 Assignee: (unassigned) = Pete Woods (pete-woods)

** Changed in: unity-scopes-api (Ubuntu RTM)
   Importance: Undecided = Critical

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

Title:
  Crash in scopes run time if scope throws exception from
  PreviewQueryBase::run()

Status in the base for Ubuntu mobile products:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Fix Released
Status in unity-scopes-api package in Ubuntu RTM:
  In Progress

Bug description:
  If a scope throws an exception from its PreviewQueryBase::run()
  implementation, the scopes run time dumps core (stack trace below).
  This affects both RTM and Vivid. I have a fix for this, which I'll MR
  tomorrow.

  #0  __libc_do_syscall () at 
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
  No locals.
  #1  0xb6b7ae5e in __GI_raise (sig=sig@entry=6) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
  _a1 = 0
  _a3tmp = 6
  _a1tmp = 0
  _a3 = 6
  _nametmp = 268
  _a2tmp = 3737
  _a2 = 3737
  _name = 268
  _sys_result = optimized out
  pd = 0x9f5ff380
  pid = 0
  selftid = 3737
  #2  0xb6b7bb4e in __GI_abort () at abort.c:89
  save_stage = 2
  act = {__sigaction_handler = {sa_handler = 0x0, sa_sigaction = 0x0}, 
sa_mask = {__val = {1, 3066296895, 3066296824, 3065897499, 3065664229, 1, 
3065664193, 3069661904, 2673865600, 3066482688, 729240, 0, 1, 30451216, 0, 
3069594101, 3069661904, 1, 5, 0, 2673862536, 3065359272, 3066296824, 
3066297880, 1, 30448212, 3068579119, 2673862316, 2673862536, 3069612528, 
30451184, 2673866896}}, sa_flags = 1, sa_restorer = 0x0}
  sigs = {__val = {32, 0 repeats 31 times}}
  #3  0xb6cb8128 in __gnu_cxx::__verbose_terminate_handler () at 
../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
  terminating = true
  t = optimized out
  #4  0xb6cb694c in __cxxabiv1::__terminate (handler=optimized out) at 
../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:47
  No locals.
  #5  0xb6cb5d5a in __cxa_call_terminate (ue_header=0x1d0a610) at 
../../../../src/libstdc++-v3/libsupc++/eh_call.cc:54
  No locals.
  #6  0xb6cb64ae in __cxxabiv1::__gxx_personality_v0 (state=optimized out, 
ue_header=0x1d0a610, context=optimized out) at 
../../../../src/libstdc++-v3/libsupc++/eh_personality.cc:676
  action_record = optimized out
  p = optimized out
  thrown_ptr = 0x0
  info = {Start = 2673862680, LPStart = 30451216, ttype_base = 0, TType 
= 0xb6e6cd2d 
unity::scopes::internal::PreviewQueryObject::run(std::shared_ptrunity::scopes::internal::MWReply
 const, unity::scopes::internal::InvokeInfo const)+1288 
GXFb\360:\375?K\004\230\363X\f8\230B\002\320YF\212\367a\376KI\360XyD\210\367\032\353\331\370,
 action_table = 0x1d12000 \001, ttype_encoding = 136 '\210', 
call_site_encoding = 231 '\347'}
  landing_pad = 0
  ip = optimized out
  handler_switch_value = 0
  foreign_exception = false
  actions = optimized out
  found_type = optimized out
  language_specific_data = optimized out
  #7  0xb6c59c0a in unwind_phase2 (ucbp=ucbp@entry=0x1d0a610, 
vrs=vrs@entry=0x9f5fe6ac) at ../../../src/libgcc/unwind-arm-common.inc:294
  pr_result = optimized out
  #8  0xb6c59dda in __gnu_Unwind_Resume (ucbp=0x1d0a610, entry_vrs=0x9f5fe6ac) 
at ../../../src/libgcc/unwind-arm-common.inc:502
  pr_result = optimized out
  #9  0xb6c5a66e in _Unwind_Resume () at 
../../../src/libgcc/config/arm/libunwind.S:357
  No locals.
  #10 0xb6e6cd2e in unity::scopes::internal::PreviewQueryObject::run 
(this=optimized out, reply=...) at 
/build/buildd/unity-scopes-api-0.6.8+15.04.20141119/src/scopes/internal/PreviewQueryObject.cpp:80
  e = @0xa6e0e070: {_vptr.exception = 0xb3a56418}
  __PRETTY_FUNCTION__ = virtual void 
unity::scopes::internal::PreviewQueryObject::run(const MWReplyProxy, const 
unity::scopes::internal::InvokeInfo)
  reply_proxy = 
{std::__shared_ptrunity::scopes::internal::PreviewReplyImpl, 
(__gnu_cxx::_Lock_policy)2 = {_M_ptr = optimized out, _M_refcount = {_M_pi 
= 0x1d14c70}}, No data fields}
  #11 0x9f5f0006 in ?? ()
  No symbol table info available.
  Backtrace stopped: previous frame identical to this frame (corrupt stack?)

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

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

[Touch-packages] [Bug 1313360] Re: Xorg freeze

2015-02-20 Thread Christopher M. Penalver
M MATHEW GEORGE, as per
https://downloadcenter.intel.com/SearchResult.aspx?lang=engFamilyId=36ProductID=2781ProdId=2781
an update to your computer's buggy and outdated BIOS is available
(0571). 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.

** Tags added: bios-outdated-0572

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  screen freezes after I upgraded to Ubuntu 14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 27 19:27:37 2014
  DistUpgraded: 2014-04-26 03:39:02,906 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0401] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:2286]
  InstallationDate: Installed on 2014-04-25 (2 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-04-25 (1 days ago)
  dmi.bios.date: 05/21/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0437.2008.0521.1933
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DG33FB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81072-308
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0437.2008.0521.1933:bd05/21/2008:svn:pn:pvr:rvnIntelCorporation:rnDG33FB:rvrAAD81072-308:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Apr 27 19:23:06 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputMicrosoft Basic Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: nouveau

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

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


[Touch-packages] [Bug 1418552] Re: dhclient uses lots of memory on systems with many interfaces

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

** Changed in: isc-dhcp (Ubuntu)
   Status: New = Confirmed

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

Title:
  dhclient uses lots of memory on systems with many interfaces

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  This is with 4.2.4-7ubuntu12, but since there's not a lot of code
  changing in ISC dhcpd (and its client), I guess this is a quite
  general problem: We're currently preapring a box to test a captive
  portal, thus this system has a hugh amount (ie. 1000) interfaces
  bridged to a physical network port.

  Calling dhclient (with a custom script to configure the different
  interfaces independently by using non-default routing tables) works
  perfectly find for the first few interfaces. However, when there are
  already a few hundred interfaces up, it takes longer and longer for
  each new dhclient instance to get an IP address.

  As strace reveals, it seems dhclient scans all interfaces, even
  several times, during start-up. I guess that it prepares data for each
  interface that's already configured with an IP address, thus wasting a
  lot of memory for no good. This should be reported upstream.

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

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


[Touch-packages] [Bug 1423904] [NEW] CA certs are outdated

2015-02-20 Thread Marc Deslauriers
*** This bug is a security vulnerability ***

Public security bug reported:

CA certs in stable releases are outdated. They should be updated to the
version in vivid.

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: ca-certificates (Ubuntu Lucid)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: ca-certificates (Ubuntu Precise)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: ca-certificates (Ubuntu Trusty)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: ca-certificates (Ubuntu Utopic)
 Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
 Status: In Progress

** Affects: ca-certificates (Ubuntu Vivid)
 Importance: Undecided
 Status: Fix Released

** Also affects: ca-certificates (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: ca-certificates (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: ca-certificates (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: ca-certificates (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Also affects: ca-certificates (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: ca-certificates (Ubuntu Vivid)
   Status: New = Fix Released

** Changed in: ca-certificates (Ubuntu Lucid)
   Status: New = In Progress

** Changed in: ca-certificates (Ubuntu Lucid)
 Assignee: (unassigned) = Marc Deslauriers (mdeslaur)

** Changed in: ca-certificates (Ubuntu Precise)
   Status: New = In Progress

** Changed in: ca-certificates (Ubuntu Precise)
 Assignee: (unassigned) = Marc Deslauriers (mdeslaur)

** Changed in: ca-certificates (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: ca-certificates (Ubuntu Trusty)
 Assignee: (unassigned) = Marc Deslauriers (mdeslaur)

** Changed in: ca-certificates (Ubuntu Utopic)
   Status: New = In Progress

** Changed in: ca-certificates (Ubuntu Utopic)
 Assignee: (unassigned) = Marc Deslauriers (mdeslaur)

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

Title:
  CA certs are outdated

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Lucid:
  In Progress
Status in ca-certificates source package in Precise:
  In Progress
Status in ca-certificates source package in Trusty:
  In Progress
Status in ca-certificates source package in Utopic:
  In Progress
Status in ca-certificates source package in Vivid:
  Fix Released

Bug description:
  CA certs in stable releases are outdated. They should be updated to
  the version in vivid.

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

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


[Touch-packages] [Bug 1301998] Re: Xorg freeze

2015-02-20 Thread Christopher M. Penalver
** Description changed:

  Backtrace:
  https://launchpadlibrarian.net/171690059/XorgLogOld.txt
+ 
+ WORKAROUND: Use gnome-session-flashback.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  Date: Thu Apr  3 10:46:59 2014
  DistUpgraded: 2014-01-22 19:30:50,196 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: BFG Tech Device [19f1:201f]
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-01-23 (70 days ago)
  dmi.bios.date: 06/26/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP55WB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE64798-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-207:cvn:ct2:cvr:
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr  3 10:38:37 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputSleep Button KEYBOARD, id 7
   inputLogitech Optical USB Mouse MOUSE, id 8
   inputBTC USB Multimedia Keyboard KEYBOARD, id 9
   inputBTC USB Multimedia Keyboard KEYBOARD, id 10
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.0-1ubuntu7
  xserver.video_driver: nouveau

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Backtrace:
  https://launchpadlibrarian.net/171690059/XorgLogOld.txt

  WORKAROUND: Use gnome-session-flashback.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8
  Uname: Linux 3.13.0-21-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell]
  Date: Thu Apr  3 10:46:59 2014
  DistUpgraded: 2014-01-22 19:30:50,196 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: BFG Tech Device [19f1:201f]
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-21-generic 
root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to trusty on 2014-01-23 (70 days ago)
  dmi.bios.date: 

[Touch-packages] [Bug 1313500] Re: run xdiagnose

2015-02-20 Thread Christopher M. Penalver
Gordon McIntosh, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1313500

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

As well, please note given that the information from the prior release
is already available, doing this on a release prior to the development
one would not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

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

Title:
  run xdiagnose

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  file comes from running xdiagnose / will not shutdown  act as if
  suspend but not  will restart ok

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Apr 28 14:08:31 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Foxconn International, Inc. Device [105b:0dcc]
   NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 
[VGA controller])
  InstallationDate: Installed on 2014-04-20 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=befb18c8-51c3-4695-a4ce-b4f7fe31f95f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A48F1020
  dmi.board.name: H67M-S/H67M-V/H67
  dmi.board.vendor: Foxconn
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA48F1020:bd02/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnFoxconn:rnH67M-S/H67M-V/H67:rvr:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 28 13:28:19 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   input

[Touch-packages] [Bug 1313392] Re: dnsmasq crashes dhcp/internet connection and uses a lot of cpu

2015-02-20 Thread Christopher M. Penalver
** Package changed: xorg (Ubuntu) = dnsmasq (Ubuntu)

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

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

Title:
  dnsmasq crashes dhcp/internet connection and uses a lot of cpu

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  dnsmasq crashes dhcp/internet connection and uses a lot of cpu. One has to 
use dhclient eth0 or wlan0 as root, to connect to the internet although the LAN 
is connected between pcs on the local network.
  Temporary solution is to edit /etc/NetworkManager/NetworkManager.conf by 
placing # in front of the line: dns=dnsnmasq,in order for network-manager to 
auto connect to eth0 or wlan0 at login.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Apr 27 12:41:01 2014
  InstallationDate: Installed on 2014-04-11 (15 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140407)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1323051] Re: Refresh problems after turning up resolution

2015-02-20 Thread Christopher M. Penalver
themusicgod1, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1323051

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

As well, given the information from the prior release is already
available, testing a release prior to the development one would not be
helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

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

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

Title:
  Refresh problems after turning up resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Recently turned up the resolution on my 2nd monitor (IBM ThinkVision detected 
as 'IBM France 17') up to  1280x1024 (5:4) counterclockwise (along with the 
built in monitor at 1024x600) and now both my gnome-terminal and emacs24 
session seem to take turns looking like the attempt to refresh their window 
went bad(screenshot attached - see bottom right window, that should be a white 
emacs window).
   
  Typically these come when interacting with these windows, highlighting, right 
clicking, etc.  Resizing the windows seems to force a refresh.

  gnome-terminal:
Installed: 3.6.2-0ubuntu1
Candidate: 3.6.2-0ubuntu1
Version table:

  emacs24:
Installed: 24.3+1-2ubuntu1
Candidate: 24.3+1-2ubuntu1

  00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express 
Integrated Graphics Controller (rev 03)
  00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)

  apt-cache policy xserver-xorg-video-intel 
  xserver-xorg-video-intel:
Installed: 2:2.99.910-0ubuntu1
Candidate: 2:2.99.910-0ubuntu1

  xorg:
Installed: 1:7.7+1ubuntu8
Candidate: 1:7.7+1ubuntu8

  
  lsb_release -rd 
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun May 25 13:49:20 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.13.0-23-generic, i686: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, i686: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:022f]
 Subsystem: Acer Incorporated [ALI] Device [1025:022f]
  InstallationDate: Installed on 2014-03-28 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326)
  MachineType: Acer Aspire one
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire one
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnAcer:bvrV1.21:bd09/28/2009:svnAcer:pnAspireone:pvrV1.21:rvnAcer:rnAspireone:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.name: Aspire one
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Touch-packages] [Bug 1313392] Re: dnsmasq crashes dhcp/internet connection and uses a lot of cpu

2015-02-20 Thread Thomas Hood
*** This bug is a duplicate of bug 1314697 ***
https://bugs.launchpad.net/bugs/1314697

** This bug has been marked a duplicate of bug 1314697
   DNS resolution no longer works; dnsmasq uses 100% CPU

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

Title:
  dnsmasq crashes dhcp/internet connection and uses a lot of cpu

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  dnsmasq crashes dhcp/internet connection and uses a lot of cpu. One has to 
use dhclient eth0 or wlan0 as root, to connect to the internet although the LAN 
is connected between pcs on the local network.
  Temporary solution is to edit /etc/NetworkManager/NetworkManager.conf by 
placing # in front of the line: dns=dnsnmasq,in order for network-manager to 
auto connect to eth0 or wlan0 at login.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Apr 27 12:41:01 2014
  InstallationDate: Installed on 2014-04-11 (15 days ago)
  InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140407)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1313296] Re: Screen won't fit the monitor resolution on my laptop

2015-02-20 Thread Christopher M. Penalver
Jdavid-1385, thank you for reporting this and helping make Ubuntu
better. 12.04.3 reached EOL in August 2014. For more on this, please see
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and
https://wiki.ubuntu.com/Releases .

Is this an issue in a supported release?

** Tags added: bios-outdated-f.0d

** Package changed: xorg (Ubuntu) = linux (Ubuntu)

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

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

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

Title:
  Screen won't fit the monitor resolution on my laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading the linux kernel, the next boot X started with wrong
  resolution, after looking around I think it could be related to the
  auto i915.modeset=0 in the kernel args, but  I don't know how to get
  this fixed. Moreover the xorg fallsback to vesa on init (I am not sure
  this is the proper way to express that).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-39.57~precise1-generic 3.8.13.20
  Uname: Linux 3.8.0-39-generic i686
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 27 11:46:45 2014
  DistUpgraded: 2014-04-27 09:47:02,400 DEBUG enabling apt cron job
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.1.12, 3.8.0-38-generic, i686: installed
   virtualbox, 4.1.12, 3.8.0-39-generic, i686: installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:30d8]
 Subsystem: Hewlett-Packard Company Device [103c:30d8]
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 
(20130820.1)
  MachineType: Hewlett-Packard HP Compaq 6720s
  MarkForUpload: True
  ProcEnviron:
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   LANGUAGE=es_ES:en
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-39-generic 
root=UUID=33a0c2f1-d3d3-4679-8cd9-c3b5ac1d2ce2 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to precise on 2014-04-27 (0 days ago)
  dmi.bios.date: 07/05/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68MDU Ver. F.01
  dmi.board.name: 30D8
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 83.0C
  dmi.chassis.asset.tag: CNU746249V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68MDUVer.F.01:bd07/05/2007:svnHewlett-Packard:pnHPCompaq6720s:pvrF.01:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq 6720s
  dmi.product.version: F.01
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.7.12-0ubuntu3
  version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3~glasen~ppa1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3~glasen~ppa1
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.14
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.99.99~git20120913.8637f772-0ubuntu1~precise~xup2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.21.15~precise~ppa1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.2-0ubuntu3~precise~xup2

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

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


[Touch-packages] [Bug 1316601] Re: shell gnome

2015-02-20 Thread Christopher M. Penalver
dav49, thank you for taking the time to report this and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read How to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and
https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would
then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem,
2. The behavior you expected, and
3. The behavior you actually encountered (in as much detail as possible).

Thank you for your understanding.

** Tags added: latest-bios-218

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

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

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

Title:
  shell gnome

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  troppo macchinosa ! meglio 11.04
  grazie

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May  6 15:19:07 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1be2]
  InstallationDate: Installed on 2014-04-30 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
  MachineType: ASUSTeK Computer Inc. K52F
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=fce7bc8d-ba05-4d92-95f0-778757821253 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52F.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52F
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52F.218:bd07/12/2011:svnASUSTeKComputerInc.:pnK52F:pvr1.0:rvnASUSTeKComputerInc.:rnK52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K52F
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 15:07:47 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9964 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1317546] Re: 12.04 invisible cursor after screensaver exists

2015-02-20 Thread Christopher M. Penalver
Wade Hampton, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1317546

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

As well, given that the information from the prior release is already
available, doing this on a release prior to the development one would
not be helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags added: bios-outdated-2.2.7

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

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

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

Title:
  12.04 invisible cursor after screensaver exists

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  System is stable Dell workstation with Ubuntu 12.04. It was updated a couple 
of day ago.
  After the recent update, sometimes the mouse cursor is not visible after 
returning from the screensaver.
  The only way it is useful with the invisible cursor is having the ctrl key 
make the cursor visible.

  The problem is not fixed by killing the X server and logging in again.

  The problem is only fixed by shutting down and rebooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-61.92-generic-pae 3.2.55
  Uname: Linux 3.2.0-61-generic-pae i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  CompizPlugins:
   (gconftool-2:11718): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Did not receive a reply. Possible causes include: the remote application did 
not send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: compiz
  Date: Thu May  8 10:47:07 2014
  DistUpgraded: 2012-11-08 16:04:04,695 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: precise
  DistroVariant: ubuntu
  DkmsStatus:
   blcr, 0.8.2: added
   vboxhost, 4.3.10, 3.2.0-56-generic-pae, i686: installed
   vboxhost, 4.3.10, 3.2.0-61-generic-pae, i686: installed
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   NVIDIA Corporation C51 [GeForce 6150 LE] [10de:0241] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Dell Device [1028:01ec]
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. OptiPlex 740 Enhanced
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-61-generic-pae 
root=UUID=6928eccf-9e05-4a27-93d6-0e15b7e34694 ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to precise on 2012-11-08 (545 days ago)
  dmi.bios.date: 05/04/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.6
  dmi.board.name: 0YP696
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.6:bd05/04/2008:svnDellInc.:pnOptiPlex740Enhanced:pvr:rvnDellInc.:rn0YP696:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 740 Enhanced
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu3
  version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.0.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.7
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.7
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.14
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build3

To manage notifications about this bug go to:

[Touch-packages] [Bug 1423890] [NEW] AppArmor support for the XDG Base Directory spec is incomplete

2015-02-20 Thread Sergio Gelato
Public bug reported:

Based on the version of apparmor in trusty-updates:

Various profiles grant permissions for files in @{HOME}/.cache/. This is
only sufficient as long as one hasn't set the environment variable
XDG_CACHE_HOME to point somewhere else. (Use case: store caches locally
when home directories are on a remote fileserver.)

I'd suggest defining a new tunable
@{XDG_CACHE_HOME}=@{HOME}/.cache/
which local administrators could augment as needed (e.g.,
@{XDG_CACHE_HOME}+=/var/cache/xdg/*/
or whatever the local convention may be).

Similar treatment may be needed for the other environment variables mentioned 
in the XDG basedir spec:
XDG_CONFIG_HOME for @{HOME}/.config
XDG_DATA_HOME for @{HOME}/.local/share (and/or @{HOME}/.local ?)

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

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

Title:
  AppArmor support for the XDG Base Directory spec is incomplete

Status in apparmor package in Ubuntu:
  New

Bug description:
  Based on the version of apparmor in trusty-updates:

  Various profiles grant permissions for files in @{HOME}/.cache/. This
  is only sufficient as long as one hasn't set the environment variable
  XDG_CACHE_HOME to point somewhere else. (Use case: store caches
  locally when home directories are on a remote fileserver.)

  I'd suggest defining a new tunable
  @{XDG_CACHE_HOME}=@{HOME}/.cache/
  which local administrators could augment as needed (e.g.,
  @{XDG_CACHE_HOME}+=/var/cache/xdg/*/
  or whatever the local convention may be).

  Similar treatment may be needed for the other environment variables mentioned 
in the XDG basedir spec:
  XDG_CONFIG_HOME for @{HOME}/.config
  XDG_DATA_HOME for @{HOME}/.local/share (and/or @{HOME}/.local ?)

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

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


[Touch-packages] [Bug 1423892] [NEW] force-adb task not triggered by password change

2015-02-20 Thread Jani Monoses
Public bug reported:

On the krillin the force-adb task is not started when changing the password 
from the UI.
On the other hand sudo touch /var/lib/extrausers/shadow triggers it.
This can be seen by adding logger statements to the script.

** Affects: lxc-android-config (Ubuntu)
 Importance: Undecided
 Assignee: Oliver Grawert (ogra)
 Status: New

** Changed in: lxc-android-config (Ubuntu)
 Assignee: (unassigned) = Oliver Grawert (ogra)

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

Title:
  force-adb task not triggered by password change

Status in lxc-android-config package in Ubuntu:
  New

Bug description:
  On the krillin the force-adb task is not started when changing the password 
from the UI.
  On the other hand sudo touch /var/lib/extrausers/shadow triggers it.
  This can be seen by adding logger statements to the script.

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

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


[Touch-packages] [Bug 1423894] [NEW] pulseaudio 6 sometimes jumps to 100%

2015-02-20 Thread Sandra Karuving
Public bug reported:

after switch to pulse 6 pavucontrol/kmix behavior changed in a bad way
and sometimes jumps to 100%

some applications (i made some howto) just let them jump to 100% wich is
bad, because when you play a loud song this can cause ear damage and
hardware damage.


(how to recreate)
be in KDE Plasma, go to dolphin and to your settings. now loog at the trashcan 
menu whats the maximum size. close and create a file  bigger as the maximum. 
trs to move that file to the trash. a notification will show you that you cant 
move it to the trash can AND pulseaudio will jump to 100% for your master 
channel

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:6.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Feb 20 13:03:55 2015
InstallationDate: Installed on 2015-02-01 (18 days ago)
InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150130)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.50
dmi.board.name: FM2A88X-ITX+
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd11/11/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88X-ITX+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug kubuntu pulseaudio ubuntu vivid

** Attachment added: video that shows off the problem
   https://bugs.launchpad.net/bugs/1423894/+attachment/4323243/+files/out.ogv

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

Title:
  pulseaudio 6 sometimes jumps to 100%

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  after switch to pulse 6 pavucontrol/kmix behavior changed in a bad way
  and sometimes jumps to 100%

  some applications (i made some howto) just let them jump to 100% wich
  is bad, because when you play a loud song this can cause ear damage
  and hardware damage.

  
  (how to recreate)
  be in KDE Plasma, go to dolphin and to your settings. now loog at the 
trashcan menu whats the maximum size. close and create a file  bigger as the 
maximum. trs to move that file to the trash. a notification will show you that 
you cant move it to the trash can AND pulseaudio will jump to 100% for your 
master channel

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: pulseaudio 1:6.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Feb 20 13:03:55 2015
  InstallationDate: Installed on 2015-02-01 (18 days ago)
  InstallationMedia: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150130)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.50
  dmi.board.name: FM2A88X-ITX+
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd11/11/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88X-ITX+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Touch-packages] [Bug 1322960] Re: Rendering randomly not as expected

2015-02-20 Thread Christopher M. Penalver
ben_31, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1322960

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

As well, given the information from the prior release is already
available, testing a release prior to the development one would not be
helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags added: latest-bios-214

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

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

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

Title:
  Rendering randomly not as expected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Randomly during a gnome session windows are blurring. Backgroud image
  does not always appear at session opening, it appears after a while.
  It happened after upgrade to 14.04 (ubuntu-gnome).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,commands,compiztoolbox,gnomecompat,vpswitch,resize,grid,snap,mousepoll,move,place,wall,imgpng,regex,session,animation,expo,fade,ezoom,scale,workarounds]
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun May 25 09:09:02 2014
  DistUpgraded: 2014-04-23 19:44:48,348 DEBUG failed to SystemUnLock() (E:Non 
verrouillé)
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1427]
  InstallationDate: Installed on 2013-12-29 (146 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  MachineType: ASUSTeK Computer Inc. UX31E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-04-23 (31 days ago)
  dmi.bios.date: 08/14/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.214:bd08/14/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat May 24 09:51:43 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id6107 
   vendor COR
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1322861] Re: dell touch pad

2015-02-20 Thread Christopher M. Penalver
jeff lee, this bug was reported a while ago and there hasn't been any
activity in it recently. We were wondering if this is still an issue? If
so, could you please test for this with the latest development release
of Ubuntu? ISO images are available from http://cdimage.ubuntu.com
/daily-live/current/ .

If it remains an issue, could you please run the following command in
the development release from a Terminal as it will automatically gather
and attach updated debug information to this report:

apport-collect -p xorg 1322861

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

As well, given the information from the prior release is already
available, testing a release prior to the development one would not be
helpful.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags added: latest-bios-a09

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

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

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

Title:
  dell touch pad

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  keeps sticking and freezing !

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat May 24 15:31:51 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0227]
 Subsystem: Dell Device [1028:0227]
  InstallationDate: Installed on 2014-05-24 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: Dell Inc. Vostro 1400
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=d620bc4a-b6f6-4c45-92b4-79fe77478fb4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0TT347
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/10/2008:svnDellInc.:pnVostro1400:pvr:rvnDellInc.:rn0TT347:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Vostro 1400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat May 24 15:29:38 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12631 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1323231] Re: Ubuntu freezes completly and a power button restart is needed

2015-02-20 Thread Christopher M. Penalver
Miguel de Freitas Fonseca, thank you for taking the time to report this
and trying to help make Ubuntu better. However, the Ubuntu Kernel PPA
and Firefox nightly are not software packages provided by the official
Ubuntu repositories. Because of this the Ubuntu project can not support
or fix your particular bug. Please report this bug to the provider of
the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories

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

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

Title:
  Ubuntu freezes completly and a power button restart is needed

Status in xorg package in Ubuntu:
  Invalid

Bug description:
   It is the second time I report this bug!

   I'm using a fresh install of Ubuntu Gnome 14.04 64 bits.

   I have a desktop HP dual-core 2,8 Ghz with a ATI X1600 with 512 MB
  and 2 GB RAM.

   I have zswap enable in the Kernel using the 3.14-4 version downloaded from 
Kernel Mianline Ubuntu PPA.
   I reduced the swapiness to 5 and I have a 4GB swap partition enable and 
working.
   I had Firefox Nightly version 32.0a1 open with three tabs, Vuze Torrent 
program and playing Mahjongg.

   I also had the terminal open and because this bug happens VERY often, I was 
cheking the RAM available.
   I had, after using the comand sudo sync  sudo echo 3 | sudo tee 
/proc/sys/vm/drop_caches, around 600 MB free RAM available when the PC freezed 
completly!!

   A power button restart is allways needed when this happens!
   And, as I described above, it happens VERY often!!

   After much search, finding lots os users with this porblem, I've come
  to descover that using this comands:

   - sudo update-rc.d ondemand disable
   and then, doing:

   - sudo update-rc.d ondemand enable

   Minimizes the problem, and sometimes, I'm able to use the PC for 24 Hours or 
more with no problem!
   But, sometimes, even after I executed this command, the PC freezes again and 
a power button restart is necessary to resolve the issue!

   Like I wote the first time I reported this bug, this situation started to 
happen in my machine since the launch of 11.04 Natty!
   Up until 10.10 Maverick, nothing like this ever happended!

   Please solve this issue!

   If you need adicional information, tell me how to get it and I will
  suply it!

   I think that's all.
   -

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  Uname: Linux 3.14.4-031404-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon May 26 10:33:33 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1600/X1650 Series] 
[1002:7181] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:0400]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:0401]
  InstallationDate: Installed on 2014-04-04 (51 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Daily amd64 
(20140403.1)
  MachineType: HP Pavilion 061 RJ770AA-AB9 m7660.pt
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.14.4-031404-generic 
root=UUID=eda039e6-958f-4dac-837a-257149aa91e1 ro quiet splash zswap.enabled=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/08/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 3.19
  dmi.board.name: LEUCITE3
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 2.00
  dmi.chassis.type: 3
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr3.19:bd12/08/2006:svnHPPavilion061:pnRJ770AA-AB9m7660.pt:pvr0nx0114RE101LEUC300:rvnASUSTekComputerINC.:rnLEUCITE3:rvr2.00:cvn:ct3:cvr:
  dmi.product.name: RJ770AA-AB9 m7660.pt
  dmi.product.version: 0nx0114RE101LEUC300
  dmi.sys.vendor: HP Pavilion 061
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1323389] Re: Xorg freezes when resuming laptop with external monitors

2015-02-20 Thread Christopher M. Penalver
Will Shackleton, as per http://www.dell.com/support/home/us/en/04
/product-support/product/precision-m3800-workstation/drivers an update
to your computer's buggy and outdated BIOS is available (A07). 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.

** Tags added: bios-outdated-a07

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

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

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

Title:
  Xorg freezes when resuming laptop with external monitors

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When resuming my laptop from sleep via the keyboard, occasionally X
  will freeze up - this is usually associated with one of my monitors
  not displaying output. I can't reach a terminal with Ctrl-Alt-F2 and I
  have to open the laptop and reboot with Alt-PrtScr-(REISUB) (hard
  reboot) - the USB keyboard won't work in this situation.

  This only happens occasionally and will usually happen if I wake the
  laptop before turning the screens back on.

  There are other cases that can also trigger X freezes but I'm not sure
  if they are related (eg. unplugging screens).

  The following is commonly seen in dmesg during normal behaviour:
  [drm:intel_dp_aux_native_write] *ERROR* too many retries, giving up
  [drm:intel_dp_start_link_train] *ERROR* failed to enable link training

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon May 26 19:46:18 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 3.13.0-24-generic, x86_64: installed
   nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060d]
 Subsystem: Dell Device [1028:060d]
  InstallationDate: Installed on 2014-05-24 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  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.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  

[Touch-packages] [Bug 1287222] Re: openssh-client 6.5 regression bug with certain servers

2015-02-20 Thread Robie Basak
Looks like there's a patch for openssh available the RH bug which
detects broken server implementations and sends options that they can
accept (by matching Cisco-* in the banner).

We probably don't want to have to maintain this patch in Ubuntu
indefinitely though. But we could cherry-pick it if upstream commit the
patch. Is there a bug filed with openssh upstream?

** Tags added: needs-upstream-report

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

Title:
  openssh-client 6.5 regression bug with certain servers

Status in openssh package in Ubuntu:
  Confirmed
Status in openssh package in Debian:
  New
Status in openssh package in Fedora:
  Unknown

Bug description:
  Previous working versions of SSH (6.2p2) work fine on certain host
  machines as follows:

  penSSH_6.2p2 Ubuntu-6, OpenSSL 1.0.1f 6 Jan 2014
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to hostname [IPAddress] port 22.
  debug1: Connection established.
  debug1: identity file /home/nelsot08/.ssh/identity type -1
  debug1: identity file /home/nelsot08/.ssh/identity-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_rsa type 1
  debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
  debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
  debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1
  debug1: Remote protocol version 2.0, remote software version Cisco-1.25
  debug1: no match: Cisco-1.25
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.2p2 Ubuntu-6
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server-client aes128-cbc hmac-md5 none
  debug1: kex: client-server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102410248192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
  debug1: Server host key: RSA 24:75:76:a1:80:0e:6c:4e:a8:c4:a6:a9:d3:34:98:18
  Warning: Permanently added 'hostname,IPAddress' (RSA) to the list of known 
hosts.
  debug1: ssh_rsa_verify: signature correct
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: Roaming not allowed by server
  debug1: SSH2_MSG_SERVICE_REQUEST sent
  debug1: SSH2_MSG_SERVICE_ACCEPT received

  
  But in 6.5p1 the following bug occurs:

  OpenSSH_6.5, OpenSSL 1.0.1f 6 Jan 2014
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: Applying options for *
  debug1: Connecting to hostname [IPAddress] port 22.
  debug1: Connection established.
  debug1: identity file /home/nelsot08/.ssh/identity type -1
  debug1: identity file /home/nelsot08/.ssh/identity-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_rsa type 1
  debug1: identity file /home/nelsot08/.ssh/id_rsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_dsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa type -1
  debug1: identity file /home/nelsot08/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/nelsot08/.ssh/id_ed25519 type -1
  debug1: identity file /home/nelsot08/.ssh/id_ed25519-cert type -1
  debug1: Remote protocol version 2.0, remote software version Cisco-1.25
  debug1: no match: Cisco-1.25
  debug1: Enabling compatibility mode for protocol 2.0
  debug1: Local version string SSH-2.0-OpenSSH_6.5p1 Ubuntu-4
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: server-client aes128-cbc hmac-md5 none
  debug1: kex: client-server aes128-cbc hmac-md5 none
  debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102430728192) sent
  debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
  Connection closed by IPAddress

  
  This is a regression and there are multiple references to this bug occurring 
previously:

  http://www.held.org.il/blog/2011/05/the-myterious-case-of-broken-ssh-
  client-connection-reset-by-peer/

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

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


[Touch-packages] [Bug 1423908] Re: Upgrade to vivid (whoopsie_0.2.46) failed

2015-02-20 Thread Christian Kirbach
dpkg.log:

2015-02-20 14:11:43 upgrade whoopsie:amd64 0.2.39ubuntu0.1 0.2.46
2015-02-20 14:11:43 status half-configured whoopsie:amd64 0.2.39ubuntu0.1
2015-02-20 14:11:44 upgrade libwhoopsie0:amd64 0.2.39ubuntu0.1 0.2.46
2015-02-20 14:11:44 status half-configured libwhoopsie0:amd64 0.2.39ubuntu0.1
2015-02-20 14:11:44 status unpacked libwhoopsie0:amd64 0.2.39ubuntu0.1
2015-02-20 14:11:44 status half-installed libwhoopsie0:amd64 0.2.39ubuntu0.1
2015-02-20 14:11:44 status half-installed libwhoopsie0:amd64 0.2.39ubuntu0.1
2015-02-20 14:11:44 status unpacked libwhoopsie0:amd64 0.2.46
2015-02-20 14:11:44 status unpacked libwhoopsie0:amd64 0.2.46

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

Title:
  Upgrade to vivid (whoopsie_0.2.46) failed

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi

  upgrading from whoopsie   0.2.39ubuntu amd64
  to
  whoopsie_0.2.46_amd64.deb

  failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: whoopsie 0.2.39ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  .var.log.upstart.whoopsie.log: Error: [Errno 13] Keine Berechtigung: 
'/var/log/upstart/whoopsie.log'
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashReports: 600:0:110:1118314:2015-02-20 14:11:46.692910153 
+0100:2015-02-20 14:11:43.944910063 +0100:/var/crash/whoopsie.0.crash
  CurrentDesktop: GNOME
  Date: Fri Feb 20 14:20:24 2015
  InstallationDate: Installed on 2013-01-08 (772 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to vivid on 2015-02-20 (0 days ago)

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

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


[Touch-packages] [Bug 1423908] Re: Upgrade to vivid (whoopsie_0.2.46) failed

2015-02-20 Thread Christian Kirbach
I upgraded using 
update-manager -c -d

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

Title:
  Upgrade to vivid (whoopsie_0.2.46) failed

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi

  upgrading from whoopsie   0.2.39ubuntu amd64
  to
  whoopsie_0.2.46_amd64.deb

  failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: whoopsie 0.2.39ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  .var.log.upstart.whoopsie.log: Error: [Errno 13] Keine Berechtigung: 
'/var/log/upstart/whoopsie.log'
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashReports: 600:0:110:1118314:2015-02-20 14:11:46.692910153 
+0100:2015-02-20 14:11:43.944910063 +0100:/var/crash/whoopsie.0.crash
  CurrentDesktop: GNOME
  Date: Fri Feb 20 14:20:24 2015
  InstallationDate: Installed on 2013-01-08 (772 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to vivid on 2015-02-20 (0 days ago)

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

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


[Touch-packages] [Bug 49521] Re: Screen locks up black on laptop lid close.

2015-02-20 Thread snurfle
Sorry for taking so long to respond to this.

bug # 1423917 created this morning after upgrading to 14.04.2, just in
case it was fixed in that release, but it was not.

Not sure how to subscribe someone else to a bug report.

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

Title:
  Screen locks up black on laptop lid close.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: acpi

  On my Dell 640C laptop, my screen locks up black whenever I close the
  lid.

  Doesn't matter if I have it set to sleep/suspend, blank screen, or
  just no event. Whenever I close the lid, it locks up black and nothing
  short of restarting Gnome or rebooting can get my screen back.

  Thanks for any fixes/suggestions.

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

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


[Touch-packages] [Bug 1423473] Re: all Unit tests don't pass with Qt5.4

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

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

Title:
  all Unit tests don't pass with Qt5.4

Status in U1DB Qt/ QML:
  In Progress
Status in u1db-qt package in Ubuntu:
  New

Bug description:
  With Qt 5.4 all unit tests don't pass:

  FAIL!  : qmltestrunner::U1dbDatabase::test_0_documentCreate() Compared values 
are not the same
   Actual (): 
   Expected (): 
   Loc: [./tests/tst_database.qml(70)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_1_databasePopulated() Compared 
values are not the same
   Actual (): 
   Expected (): 
   Loc: [./tests/tst_database.qml(84)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_3_documentContents() Compared 
values are not the same
   Actual (): 
   Expected (): 
   Loc: [./tests/tst_database.qml(103)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_1_defaults() uno: {} != 
[1,_,a] ({} [1,_,a])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_2_numbers() uno: {} != [1] ({} 
[1])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_3_wildcards() uno: {} != [1] ({} 
[1])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_4_delete() uno: {} != 
[1,_,a] ({} [1,_,a])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_5_fields() one field: {} != [G] 
({} [G])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_6_definition() ichi: {} != 
[gokaiger,ooo] ({} [gokaiger,ooo])
   Loc: [./tests/tst_query.qml(276)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/u1db-qt/+bug/1423473/+subscriptions

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


[Touch-packages] [Bug 1422898] Re: Excessive CPU usage, even when the screen is turned off

2015-02-20 Thread Timo Jyrinki
Fixed in
https://launchpad.net/ubuntu/+source/qtmir/0.4.4+15.04.20150220-0ubuntu1

Until new image is created, you can just:
adb shell
sudo apt update
sudo apt dist-upgrade

** Package changed: unity8 (Ubuntu) = qtmir (Ubuntu)

** Changed in: qtmir (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 unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1422898

Title:
  Excessive CPU usage, even when the screen is turned off

Status in qtmir package in Ubuntu:
  Fix Released

Bug description:
  Since mako image r102 (vivid-proposed), the CPU usage of Unity8 is very 
excessive and increasing over time.
  After boot, the phone runs smooth but after some time it lags heavily.

  As you can see from the attached output of the top command, Unity8
  consumes 23% of CPU power when the screen is TURNED OFF (command run
  via adb). When the screen is on, this figure is much higher and
  sometimes rises up to 60%.

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

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


[Touch-packages] [Bug 1423908] [NEW] Upgrade to vivid (whoopsie_0.2.46) failed

2015-02-20 Thread Christian Kirbach
Public bug reported:

Hi

upgrading from whoopsie   0.2.39ubuntu amd64
to
whoopsie_0.2.46_amd64.deb

failed.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: whoopsie 0.2.39ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: fglrx
.var.log.upstart.whoopsie.log: Error: [Errno 13] Keine Berechtigung: 
'/var/log/upstart/whoopsie.log'
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
CrashReports: 600:0:110:1118314:2015-02-20 14:11:46.692910153 +0100:2015-02-20 
14:11:43.944910063 +0100:/var/crash/whoopsie.0.crash
CurrentDesktop: GNOME
Date: Fri Feb 20 14:20:24 2015
InstallationDate: Installed on 2013-01-08 (772 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: Upgraded to vivid on 2015-02-20 (0 days ago)

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


** Tags: amd64 apport-bug autoreport-false vivid

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

Title:
  Upgrade to vivid (whoopsie_0.2.46) failed

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi

  upgrading from whoopsie   0.2.39ubuntu amd64
  to
  whoopsie_0.2.46_amd64.deb

  failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: whoopsie 0.2.39ubuntu0.1
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: fglrx
  .var.log.upstart.whoopsie.log: Error: [Errno 13] Keine Berechtigung: 
'/var/log/upstart/whoopsie.log'
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CrashReports: 600:0:110:1118314:2015-02-20 14:11:46.692910153 
+0100:2015-02-20 14:11:43.944910063 +0100:/var/crash/whoopsie.0.crash
  CurrentDesktop: GNOME
  Date: Fri Feb 20 14:20:24 2015
  InstallationDate: Installed on 2013-01-08 (772 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  RelatedPackageVersions: apport-noui N/A
  SourcePackage: whoopsie
  UpgradeStatus: Upgraded to vivid on 2015-02-20 (0 days ago)

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

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


[Touch-packages] [Bug 1323051] Re: Refresh problems after turning up resolution

2015-02-20 Thread themusicgod1
Unfortunately the computer I had which exhibited this bug has died.  I
can no longer reproduce

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

Title:
  Refresh problems after turning up resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Recently turned up the resolution on my 2nd monitor (IBM ThinkVision detected 
as 'IBM France 17') up to  1280x1024 (5:4) counterclockwise (along with the 
built in monitor at 1024x600) and now both my gnome-terminal and emacs24 
session seem to take turns looking like the attempt to refresh their window 
went bad(screenshot attached - see bottom right window, that should be a white 
emacs window).
   
  Typically these come when interacting with these windows, highlighting, right 
clicking, etc.  Resizing the windows seems to force a refresh.

  gnome-terminal:
Installed: 3.6.2-0ubuntu1
Candidate: 3.6.2-0ubuntu1
Version table:

  emacs24:
Installed: 24.3+1-2ubuntu1
Candidate: 24.3+1-2ubuntu1

  00:02.0 VGA compatible controller: Intel Corporation Mobile 945GSE Express 
Integrated Graphics Controller (rev 03)
  00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller (rev 03)

  apt-cache policy xserver-xorg-video-intel 
  xserver-xorg-video-intel:
Installed: 2:2.99.910-0ubuntu1
Candidate: 2:2.99.910-0ubuntu1

  xorg:
Installed: 1:7.7+1ubuntu8
Candidate: 1:7.7+1ubuntu8

  
  lsb_release -rd 
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun May 25 13:49:20 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.13.0-23-generic, i686: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, i686: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:022f]
 Subsystem: Acer Incorporated [ALI] Device [1025:022f]
  InstallationDate: Installed on 2014-03-28 (58 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta i386 (20140326)
  MachineType: Acer Aspire one
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.21
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire one
  dmi.board.vendor: Acer
  dmi.board.version: V1.21
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.21
  dmi.modalias: 
dmi:bvnAcer:bvrV1.21:bd09/28/2009:svnAcer:pnAspireone:pvrV1.21:rvnAcer:rnAspireone:rvrV1.21:cvnAcer:ct10:cvrV1.21:
  dmi.product.name: Aspire one
  dmi.product.version: V1.21
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun May 25 12:55:13 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4100 
   vendor CMO
  xserver.version: 2:1.15.1-0ubuntu2

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

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


[Touch-packages] [Bug 1423811] Re: 219-1ubuntu1 regression: boot hangs, logind fails

2015-02-20 Thread Martin Pitt
I continued to bisect binaries (/lib/systemd/{systemd,systemd-logind
,systemd-journald,systemd-fsck,systemd-fsckd}.

I never got a hang with 219 + journald from 218, and I did get a hang
with 218 + journald from 219, which indicates that this is related to
journald. Didier confirmed the latter hang.

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

Title:
  219-1ubuntu1 regression: boot hangs, logind fails

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Since yesterday, systemd does not boot properly any more. It takes
  very long, ends up in an X failsafe session, and eventually you just
  get a getty on VT1.

  Downgrading libpam-systemd libsystemd0 systemd systemd-sysv to
  https://launchpad.net/ubuntu/+source/systemd/218-10ubuntu2 fixes the
  boot again.

  This happens both with the standard quiet splash $vt_handoff as well
  as without these tree options, i. e. text mode boot.

  $ sudo systemctl list-jobs
   JOB UNITTYPESTATE
  1634 sound.targetstopwaiting
  1176 NetworkManager.service  start   running
  1598 cgproxy.service start   waiting
  1632 failsafe-graphical.target   stopwaiting
  1563 alsa-restore.servicestart   waiting
  1594 plymouth-quit-wait.service  start   waiting
  1588 getty-static.servicestart   waiting
  1562 alsa-state.service  start   waiting
   121 systemd-update-utmp-runlevel.servicestart   waiting
  1640 ifup@wlan0.service  stopwaiting
  1544 systemd-ask-password-plymouth.path  start   waiting
  1507 friendly-recovery.service   start   waiting
  1607 anacron.service start   waiting
  1489 systemd-binfmt.service  start   waiting
  1637 system-systemd\x2drfkill.slice  stopwaiting
  1636 systemd-rfkill@rfkill1.service  stopwaiting
  1631 failsafe-x.service  stopwaiting
  1638 systemd-backlight@backlight:intel_backlight.service stopwaiting
  1610 pppd-dns.servicestart   waiting
  1483 systemd-machine-id-commit.service   start   waiting
  1635 system-systemd\x2dbacklight.slice   stopwaiting
  1557 systemd-hwdb-update.service start   waiting
  1630 systemd-backlight@backlight:acpi_video0.service stopwaiting
  1500 sys-kernel-config.mount start   waiting
    92 multi-user.target   start   waiting
  1509 debian-fixup.servicestart   waiting
  1641 systemd-rfkill@rfkill0.service  stopwaiting
  1613 plymouth-quit.service   start   waiting
  1639 system-ifup.slice   stopwaiting
  1642 ifup@lxcbr0.service stopwaiting
  1633 acpid.service   stopwaiting
  1643 systemd-logind.service  restart waiting
  1543 plymouth-start.service  start   waiting
  1499 plymouth-read-write.service start   waiting

  Attaching debug journal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-1ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 20 07:39:03 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-20 (91 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141119)
  MachineType: LENOVO 2324CTO
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.18.0-13-generic.efi.signed 
root=UUID=f86539b0-3a1b-4372-83b0-acdd029ade68 ro rootflags=subvol=@ quiet 
splash vt.handoff=7 init=/sbin/upstart
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 

[Touch-packages] [Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)

2015-02-20 Thread Pete Woods
Okay, further debugging reveals that if you put the phone to sleep with
a scope that requires location visible, the location updates are not
disabled.

Looks like this is a regression. The location service listens to when
scopes are marked as active/inactive, and they all used to be marked
inactive when the phone went to sleep. This is obviously no-longer the
case.

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

Title:
  GPS stays active after location data is used by a scope (even after
  not not using the scopes anymore)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in location-service package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu RTM:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 237
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-17 17:04:34
  version version: 237
  version ubuntu: 20150217
  version device: 20150216-fe747ac
  version custom: 20150207-538-29-183

  You can easily see if the GPS is active or not by checking the logcat
  output (running as root). In this case the hardware remains on
  (consumed by the location-service) after opening a scope such as the
  weather channel one, and retrieving location.

  To reproduce:
  1 - Reboot the phone;
  2 - Open logcat as root: sudo /system/bin/logcat
  3 - From today's scope, click on the weather icon (opening the weather 
channel scopes)
  4 - See that the GPS is active and location works as expected
  5 - Move away from that scope, and check logcat's output (it will stay 
active, meaning that the location-service is still active).

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

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


[Touch-packages] [Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)

2015-02-20 Thread Pete Woods
So it's *possible* the problem could be in the location service, maybe?

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

Title:
  GPS stays active after location data is used by a scope (even after
  not not using the scopes anymore)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in location-service package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu RTM:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 237
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-17 17:04:34
  version version: 237
  version ubuntu: 20150217
  version device: 20150216-fe747ac
  version custom: 20150207-538-29-183

  You can easily see if the GPS is active or not by checking the logcat
  output (running as root). In this case the hardware remains on
  (consumed by the location-service) after opening a scope such as the
  weather channel one, and retrieving location.

  To reproduce:
  1 - Reboot the phone;
  2 - Open logcat as root: sudo /system/bin/logcat
  3 - From today's scope, click on the weather icon (opening the weather 
channel scopes)
  4 - See that the GPS is active and location works as expected
  5 - Move away from that scope, and check logcat's output (it will stay 
active, meaning that the location-service is still active).

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

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


[Touch-packages] [Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)

2015-02-20 Thread Pete Woods
I just put together a branch for unity-scopes-shell that logs when GPS
updates from the location service are being enabled and disabled:

lp:~unity-api-team/unity-scopes-shell/log-when-updating-location

Trying this on my device produces the expected behaviour, i.e.:

* When looking at a scope that requires location, it enables location updates.
* When you move away from that scope, location updates stay enabled for a 5 
second timeout (in order that the GPS isn't rapidly turned on and off as you 
browse through scopes).

To be clear, the location session remains active all the time, we just
toggle the updates property. This is the (I believe correct) way tvoß
explained to use the location service to me.

Log output:
Enabling location updates
Disabling location updates
Enabling location updates
Disabling location updates
Enabling location updates
Disabling location updates

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

Title:
  GPS stays active after location data is used by a scope (even after
  not not using the scopes anymore)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in location-service package in Ubuntu:
  New
Status in unity-scopes-api package in Ubuntu RTM:
  New

Bug description:
  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 237
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2015-02-17 17:04:34
  version version: 237
  version ubuntu: 20150217
  version device: 20150216-fe747ac
  version custom: 20150207-538-29-183

  You can easily see if the GPS is active or not by checking the logcat
  output (running as root). In this case the hardware remains on
  (consumed by the location-service) after opening a scope such as the
  weather channel one, and retrieving location.

  To reproduce:
  1 - Reboot the phone;
  2 - Open logcat as root: sudo /system/bin/logcat
  3 - From today's scope, click on the weather icon (opening the weather 
channel scopes)
  4 - See that the GPS is active and location works as expected
  5 - Move away from that scope, and check logcat's output (it will stay 
active, meaning that the location-service is still active).

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

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


[Touch-packages] [Bug 1423473] Re: all Unit tests don't pass with Qt5.4

2015-02-20 Thread Launchpad Bug Tracker
This bug was fixed in the package u1db-qt -
0.1.5+15.04.20150220-0ubuntu1

---
u1db-qt (0.1.5+15.04.20150220-0ubuntu1) vivid; urgency=medium

  [ Albert Astals Cid ]
  * Make tests pass with Qt 5.4 (LP: #1423473)

u1db-qt (0.1.5+15.04.2014~rtm-0ubuntu1) 14.09; urgency=low

  [ Christian Dywan ]
  * Create parent folder for full database path (LP: #1390166)
 -- CI Train Bot ci-train-...@canonical.com   Fri, 20 Feb 2015 10:26:14 +

** Changed in: u1db-qt (Ubuntu)
   Status: New = Fix Released

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

Title:
  all Unit tests don't pass with Qt5.4

Status in U1DB Qt/ QML:
  In Progress
Status in u1db-qt package in Ubuntu:
  Fix Released

Bug description:
  With Qt 5.4 all unit tests don't pass:

  FAIL!  : qmltestrunner::U1dbDatabase::test_0_documentCreate() Compared values 
are not the same
   Actual (): 
   Expected (): 
   Loc: [./tests/tst_database.qml(70)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_1_databasePopulated() Compared 
values are not the same
   Actual (): 
   Expected (): 
   Loc: [./tests/tst_database.qml(84)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_3_documentContents() Compared 
values are not the same
   Actual (): 
   Expected (): 
   Loc: [./tests/tst_database.qml(103)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_1_defaults() uno: {} != 
[1,_,a] ({} [1,_,a])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_2_numbers() uno: {} != [1] ({} 
[1])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_3_wildcards() uno: {} != [1] ({} 
[1])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_4_delete() uno: {} != 
[1,_,a] ({} [1,_,a])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_5_fields() one field: {} != [G] 
({} [G])
   Loc: [./tests/tst_query.qml(276)]
  FAIL!  : qmltestrunner::U1dbDatabase::test_6_definition() ichi: {} != 
[gokaiger,ooo] ({} [gokaiger,ooo])
   Loc: [./tests/tst_query.qml(276)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/u1db-qt/+bug/1423473/+subscriptions

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


[Touch-packages] [Bug 881137] Re: UFW does not clean iptables setting from /etc/ufw/before.rules

2015-02-20 Thread Jamie Strandboge
Sam, while ufw has added support for managing the FORWARD chain, it does
not yet support the nat table which is why you are seeing this issue.
Please see comments #1 and #5 in this bug for more details.

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

Title:
  UFW does not clean iptables setting from /etc/ufw/before.rules

Status in ufw package in Ubuntu:
  Won't Fix

Bug description:
  Adding some additional settings to /etc/ufw/before.rules is not
  deleted when ufw is stopped.

  I added these lines at top of file /etc/ufw/before.rules

  *nat
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE
  COMMIT

  Then I reloaded ufw firewall with command: ufw reload. Output from
  iptables-save

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  COMMIT

  Then I reloaded ufw firewall again:

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE 
  COMMIT

  And ufw reload again

  $ iptables-save -t nat
  *nat
  :PREROUTING ACCEPT [4:478]
  :INPUT ACCEPT [4:478]
  :OUTPUT ACCEPT [0:0]
  :POSTROUTING ACCEPT [0:0]
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE 
  -A POSTROUTING -o eth0 -j MASQUERADE
  COMMIT

  And again and postrouting is never deleted when ufw is stopped and
  added again when stared. Same happen if I stop ufw firewall with: $
  stop ufw. nat lines are not cleaned.

  UFW should remove all iptables settings specified in config files
  after ufw is stopped! This can be dangerous if apt-get is updating
  some ufw files and scripts needs to reload ufw (some lines will be
  more times).

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

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


[Touch-packages] [Bug 1419249] Re: UFW not allowing GEOIP rule

2015-02-20 Thread Jamie Strandboge
Thank you for using Ubuntu and filing a bug. Curiously, a Debian bug
came in just before this one that is essentially the same. Please see my
comment in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777150 and
report back if that helps you.

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

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

Title:
  UFW not allowing GEOIP rule

Status in ufw package in Ubuntu:
  Incomplete
Status in ufw package in Debian:
  Unknown

Bug description:
  Hai,

  Ufw is not allowing my GEOIP country block rule.

  I tried to add these  rules.  ( which work fine when added with
  iptables )

  -A ufw-before-logging-input -m geoip --src-cc KR,CN,VN,UA,BR,VE,JP -m limit 
--limit 3/minute -j LOG --log-level 5 --log-prefix '[UFW BLOCK COUNTRIES] '
  -A ufw-before-logging-input -m geoip --src-cc KR,CN,VN,UA,BR,VE,JP -j DROP

  
  i get the message UFW INIT error. 

  if i manualy add these rules with iptables they work fine, but these
  rules dissapeer after a while, how come ?

  and yes, even if i add these rule to ufw-before-input the same happens. 
  I cant figure this out so im reporting this as a bug. 

  At least how can i make it so that it stops removing (somehow) my
  geoip rules.. i really need them for security reasons.

  Im running ubuntu 14.04 LTS

  TLo

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

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


[Touch-packages] [Bug 1424071] Re: usb mouse

2015-02-20 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/1424071

Title:
  usb mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  stop working

  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.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Feb 20 22:29:34 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.125, 3.13.0-45-generic, x86_64: installed
   virtualbox, 4.3.10, 3.13.0-45-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0651]
  InstallationDate: Installed on 2015-02-14 (6 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  LightdmGreeterLog:
   (lightdm-webkit-greeter:1373): GLib-GObject-WARNING **: 
/build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:2462: signal 'show-error' is 
invalid for instance '0x10a6170' of type 'LightDMGreeter'
   
   (lightdm-webkit-greeter:1373): GLib-GObject-WARNING **: 
/build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:2462: signal 'timed-login' is 
invalid for instance '0x10a6170' of type 'LightDMGreeter'
   
   (lightdm-webkit-greeter:1373): GLib-GObject-WARNING **: 
/build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:2462: signal 'quit' is invalid 
for instance '0x10a6170' of type 'LightDMGreeter'
  LightdmGreeterLogOld:
   (lightdm-webkit-greeter:1385): GLib-GObject-WARNING **: 
/build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:2462: signal 'show-error' is 
invalid for instance '0x7e0170' of type 'LightDMGreeter'
   
   (lightdm-webkit-greeter:1385): GLib-GObject-WARNING **: 
/build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:2462: signal 'timed-login' is 
invalid for instance '0x7e0170' of type 'LightDMGreeter'
   
   (lightdm-webkit-greeter:1385): GLib-GObject-WARNING **: 
/build/buildd/glib2.0-2.40.2/./gobject/gsignal.c:2462: signal 'quit' is invalid 
for instance '0x7e0170' of type 'LightDMGreeter'
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=dbc01855-84aa-47fd-8a9c-12b4f1dc0e1f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 09V1VC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd11/14/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn09V1VC:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  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.7
  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: Fri Feb 20 22:21:45 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16620 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.7

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

-- 
Mailing list: 

[Touch-packages] [Bug 1418077] Re: NM fails to create a cellular data connection for a unacceptably long time

2015-02-20 Thread Pat McGowan
from what I see this only happens when changing the technology in
settings, whereas when turning off wifi or when coming up at boot cell
data is ready right away

seems less critical given that is not a frequent occurrence although
obviously a lousy user experience

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

Title:
  NM fails to create a cellular data connection for a unacceptably long
  time

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Confirm cellular data (disable wifi)
  2. Change TechnologyPreference on online SIM
  3. Confirm no cellular data
  4. Wait ~10 minutes
  5. Confirm cellular data 

  What happens:
  Changing something on the modem causes cellular data to disappear for 10 
minutes

  What should happen:
  It should behave as before, i.e. cellular data should come back immediately

  current build number: 97
  device name: krillin
  channel: ubuntu-touch/devel-proposed
  alias: ubuntu-touch/vivid-proposed
  last update: 2015-02-02 12:48:25
  version version: 97
  version ubuntu: 20150202
  version device: 20150128-5379bdb
  version custom: 20150202

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

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


[Touch-packages] [Bug 1419249] Re: UFW not allowing GEOIP rule

2015-02-20 Thread Jamie Strandboge
** Bug watch added: Debian Bug tracker #777150
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777150

** Also affects: ufw (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777150
   Importance: Unknown
   Status: Unknown

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

Title:
  UFW not allowing GEOIP rule

Status in ufw package in Ubuntu:
  New
Status in ufw package in Debian:
  Unknown

Bug description:
  Hai,

  Ufw is not allowing my GEOIP country block rule.

  I tried to add these  rules.  ( which work fine when added with
  iptables )

  -A ufw-before-logging-input -m geoip --src-cc KR,CN,VN,UA,BR,VE,JP -m limit 
--limit 3/minute -j LOG --log-level 5 --log-prefix '[UFW BLOCK COUNTRIES] '
  -A ufw-before-logging-input -m geoip --src-cc KR,CN,VN,UA,BR,VE,JP -j DROP

  
  i get the message UFW INIT error. 

  if i manualy add these rules with iptables they work fine, but these
  rules dissapeer after a while, how come ?

  and yes, even if i add these rule to ufw-before-input the same happens. 
  I cant figure this out so im reporting this as a bug. 

  At least how can i make it so that it stops removing (somehow) my
  geoip rules.. i really need them for security reasons.

  Im running ubuntu 14.04 LTS

  TLo

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

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


[Touch-packages] [Bug 1423193] Re: Dialer doesn't know call is connected over bluetooth

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

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

Title:
  Dialer doesn't know call is connected over bluetooth

Status in Dialer app for Ubuntu Touch:
  New
Status in telepathy-qt5 package in Ubuntu:
  Fix Released
Status in telepathy-qt5 package in Ubuntu RTM:
  New

Bug description:
  Attempt 1:
  Phone was locked
  Initiated a call to a conference line using the phone book on the car as 
provided from the phone
  The call connected  and the dialer was shown but it said Emergency call in 
the header and the UI was ready to make a call, not showing a cal in progress

  Attempt 2:
  Unlocked the phone and opened the dialer
  Initiated call with the car UI
  the call connected but the dialer stayed in the state to make a call

  Attempt 3:
  Same as 2 but the dialer showed the call was connected
  Entered the conference number and #, the tones were echoed and numbers shown 
in the phone UI
  The conference service did not receive the numbers

  Mako running rtm 195

  I have been using this scenario for 6 months and two different cars
  without ever having a problem. Last time was probably a month ago.

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

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


[Touch-packages] [Bug 1423944] Re: Sometime incorrectly format numbers

2015-02-20 Thread Tiago Salem Herrmann
Can you get the LineIdentification property coming from ofono to make
sure what's the exact number provided by the carrier?

dbus-monitor --system interface=org.ofono.VoiceCallManager | grep -C 2
LineIdentification

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

Title:
  Sometime incorrectly format numbers

Status in the base for Ubuntu mobile products:
  New
Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  Using rtm 240, calling from a landline to a mobile and missing calls,
  sometime the calls log/message notification/call back feature have the
  wrong number...

  The caller is a local number, 01 58 86, the country code is +31,
  sometime the call is displayed as coming from +31 1 58 86... which
  is correct, sometime it displays as +1 58 8 ... which is not (that's
  the U.S country code)

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

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


[Touch-packages] [Bug 1423810] Re: [krillin] apparmor fd_inheritance regression test causes kernel to crash

2015-02-20 Thread Steve Beattie
While it's not surprising, I've confirmed that this issues affects
ubuntu-rtm/14.09 on krillin as well.

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

Title:
  [krillin] apparmor fd_inheritance regression test causes kernel to
  crash

Status in apparmor package in Ubuntu:
  New

Bug description:
  On krillin with vivid-proposed, running the fd_inheritance test from
  the apparmor regression tests causes the kernel to crash and
  spontaneously reboot the device:

  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ logger 
running fd_inheritance tests now
  phablet@ubuntu-phablet:~/src/apparmor-2.9.1/tests/regression/apparmor$ sudo 
sh -c 'VERBOSE=1 bash fd_inheritance.sh'
  ok: fd inheritance; unconfined - unconfined
  ok: fd inheritance; confined - unconfined
  ok: fd inheritance; confined (bad perm) - unconfined
  ok: fd inheritance; confined (no perm) - unconfined
  ok: fd inheritance; unconfined - confined
  ok: fd inheritance; unconfined - confined (no perm)
  ok: fd inheritance; confined - confined
  ok: fd inheritance; confined (bad perm) - confined
  ok: fd inheritance; confined (no perm) - confined
  ok: fd inheritance; confined - confined (bad perm)
  [device reboots here]

  This is what syslog sees before it falls over, though nothing after the 
logger invocation makes it to the disk:
  Feb 20 03:51:47 ubuntu-phablet phablet: running fd_inheritance tests now
  Feb 20 03:52:05 ubuntu-phablet kernel: [  489.942611]type=1400 
audit(1424404325.798:141): apparmor=STATUS operation=profile_load 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7449 comm=apparmor_parser
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.272023]type=1400 
audit(1424404326.128:142): apparmor=STATUS operation=profile_replace 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7477 comm=apparmor_parser
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.305028]type=1400 
audit(1424404326.158:143): apparmor=DENIED operation=open 
profile=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 name=/tmp/sdtest.7416-27080-LFDs8z/file pid=7483 comm=fd_inheritance 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.573275]type=1400 
audit(1424404326.428:144): apparmor=STATUS operation=profile_replace 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7505 comm=apparmor_parser
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.606454]type=1400 
audit(1424404326.468:145): apparmor=DENIED operation=open 
profile=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 name=/tmp/sdtest.7416-27080-LFDs8z/file pid=7510 comm=fd_inheritance 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.886149]type=1400 
audit(1424404326.748:146): apparmor=STATUS operation=profile_remove 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7536 comm=apparmor_parser
  Feb 20 03:52:06 ubuntu-phablet kernel: [  490.916538]type=1400 
audit(1424404326.778:147): apparmor=STATUS operation=profile_load 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor 
pid=7537 comm=apparmor_parser
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.226336]type=1400 
audit(1424404327.088:148): apparmor=STATUS operation=profile_replace 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor 
pid=7568 comm=apparmor_parser
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.734888]type=1400 
audit(1424404327.588:149): apparmor=STATUS operation=profile_remove 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor 
pid=7612 comm=apparmor_parser
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.786710]type=1400 
audit(1424404327.648:150): apparmor=STATUS operation=profile_load 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7613 comm=apparmor_parser
  Feb 20 03:52:07 ubuntu-phablet kernel: [  491.787186]type=1400 
audit(1424404327.648:151): apparmor=STATUS operation=profile_load 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritor 
pid=7613 comm=apparmor_parser
  Feb 20 03:52:08 ubuntu-phablet kernel: [  492.354445]type=1400 
audit(1424404328.208:152): apparmor=STATUS operation=profile_replace 
profile=unconfined 
name=/home/phablet/src/apparmor-2.9.1/tests/regression/apparmor/fd_inheritance
 pid=7658 comm=apparmor_parser
  Feb 20 03:52:08 ubuntu-phablet kernel: [  492.354874]type=1400 
audit(1424404328.208:153): apparmor=STATUS operation=profile_replace 
profile=unconfined 

[Touch-packages] [Bug 1424121] [NEW] Spotify apparmor=DENIED operation=ptrace

2015-02-20 Thread Patricio Carreño Mancilla
Public bug reported:

Syslog repeat

Spotify  apparmor=DENIED operation=ptrace

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apparmor 2.8.95~2430-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 21 00:55:29 2015
InstallationDate: Installed on 2015-02-20 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
ProcEnviron:
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=2ff057ee-3a8a-4dd6-97f1-f1b31b832062 ro quiet splash vt.handoff=7
SourcePackage: apparmor
Syslog:
 Feb 20 18:45:04 aventino dbus[515]: [system] AppArmor D-Bus mediation is 
enabled
 Feb 20 23:55:55 aventino dbus[661]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=Hello mask=send 
name=org.freedesktop.DBus pid=30179 
profile=/opt/spotify/spotify-client/spotify peer_profile=unconfined
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug trusty

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

Title:
  Spotify  apparmor=DENIED operation=ptrace

Status in apparmor package in Ubuntu:
  New

Bug description:
  Syslog repeat

  Spotify  apparmor=DENIED operation=ptrace

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.95~2430-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 00:55:29 2015
  InstallationDate: Installed on 2015-02-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=es_CL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed 
root=UUID=2ff057ee-3a8a-4dd6-97f1-f1b31b832062 ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   Feb 20 18:45:04 aventino dbus[515]: [system] AppArmor D-Bus mediation is 
enabled
   Feb 20 23:55:55 aventino dbus[661]: apparmor=DENIED 
operation=dbus_method_call  bus=system path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=Hello mask=send 
name=org.freedesktop.DBus pid=30179 
profile=/opt/spotify/spotify-client/spotify peer_profile=unconfined
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1181106] Re: Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and 14.04 (trusty)

2015-02-20 Thread Carlos Eduardo Moreira dos Santos
I'm running 14.04 and I could not set a2dp today. I had it working, but
now I have a terrible sound without a2dp. I can select a2dp in the GUI,
but it makes no difference and when I go back to those settings,
telephone quality is selected. This is the output from cli:

$ pactl list cards short
0   alsa_card.pci-_00_1b.0  module-alsa-card.c
4   bluez_card.8C_DE_52_91_9A_ABmodule-bluetooth-device.c

$ sudo pactl set-card-profile 4 a2dp
Failure: Input/Output error

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

Title:
  Failed to change profile to A2DP in 13.04 (Raring), 13.10 (saucy), and
  14.04 (trusty)

Status in Bluez Utilities:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Fix Released

Bug description:
  I upgraded to 13.04 recently and my A2DP profile, which had been
  working great under 12.10 is suddenly gone.  Neither my blueman applet
  nor the built-in bluetooth manager applet can connect my external
  bluetooth speaker to the A2DP profile.  They can connect to the
  bluetooth device itself just fine.

  Steps I'm using:

  * using blueman, I can connect to the external bluetooth speaker and view the 
device in the devices listing
  * I can connect the device to the Audio sink and I get a message saying it is 
now connected and will show in the PulseAudio mixer
  * After connecting the external speaker to the audio sink, I can also see the 
device in the Play sound through listing in the Sound system control panel, 
but the icon has a circle with a line through it.
  * but if I right-click the device and choose Audio Profile from the context 
menu and try to select High Fidelity Playback (A2DP) as the new profile, I 
get an error message stating failed to change profile to a2dp

  I've already added Enable=Socket in /etc/bluetooth/audio.conf,
  without that I can't pair my headset. Now I can pair it, but I can't
  activate the A2DP profile.

  When I try to activate it, I see this message in my syslog :
  pulseaudio[2603]: [pulseaudio] module-bluetooth-device.c: Profile has no 
transport

  I tried the kernel 3.9.0 because of a sound problem with my soundcard,
  this kernel fixed my soundcard problem, but A2DP still doesn't work

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

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


[Touch-packages] [Bug 1424122] [NEW] indicator-sound-service crashed with signal 5 in main()

2015-02-20 Thread dino99
Public bug reported:

Got that crash on opening a gnome-shell session after a cold boot with
systemd-sysv

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
Uname: Linux 3.19.0-5-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.16.1-0ubuntu2
Architecture: i386
Date: Sat Feb 21 05:11:24 2015
ExecutablePath: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
Signal: 5
SourcePackage: indicator-sound
StacktraceTop: main ()
Title: indicator-sound-service crashed with signal 5 in main()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: indicator-sound (Ubuntu)
 Importance: Medium
 Status: New


** Tags: apport-crash i386 third-party-packages vivid

** Information type changed from Private to Public

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Got that crash on opening a gnome-shell session after a cold boot with
  systemd-sysv

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sat Feb 21 05:11:24 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1404731] Re: [ Dell OptiPlex 7020, Realtek ALC3220, Green Line Out, Rear] Background noise

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

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

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

Title:
  [ Dell OptiPlex 7020, Realtek ALC3220, Green Line Out, Rear]
  Background noise

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Any time I start Ubuntu, just a  sec before it starts I begin to hear 
background noise from speakers. And the noise isn't gone until I 
  shutdown the system.

  By the way, when I start listening to any music, I can't get any bass
  (although, I have a speaker system with sub woofer, and it worked fine
  for me on the previous computer).

  A lot of workaround didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  byte   1547 F pulseaudio
   /dev/snd/controlC0:  byte   1547 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg:
   [   18.943961] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
   [   19.717121] init: plymouth-upstart-bridge main process ended, respawning
   [   19.722598] init: plymouth-upstart-bridge main process ended, respawning
  Date: Mon Dec 22 00:11:51 2014
  InstallationDate: Installed on 2014-12-21 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [OptiPlex 7020, Realtek ALC3220, Green Line Out, Rear] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 08WKV3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd04/25/2014:svnDellInc.:pnOptiPlex7020:pvr01:rvnDellInc.:rn08WKV3:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 7020
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1412730] Re: DELL U2415 monitor detection issues

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

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

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

Title:
  DELL U2415 monitor detection issues

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My Laptop HP Elitebook 8740w has two external screens connected.
  1 DELL U2412M connected to vga connector
  1 DELL U2415 connected to Displayport.

  I worked for about a year with a single external display, just U2412M
  on the displayport without the issue I decribe.

  The first issue:
  When booting up and with screens attatched and active, the 2415 boots in 
1024x768 resolution, the 2412 boots at the same moment in 1920x1200 as it 
should.
  At the point where the login screen appears the 2415 goes in power save mode, 
most of the time.
  The 2412 displays just fine at the moment.
  After logging in, turning the 2415 off and on, sometimes helps the get the 
screen active (out of power save).
  When it gets active, the resoltion is 1024x768, not 1920x1200.
  In unity-control-center in display settings the 2415 is displayed as Unknown 
Display and the maximum resolution I can select is 1024x768.

  Second issue:
  After a laptop suspend the 2415 doenst alway become active again, the 2412 
always.
  Turning off an on the 2415 multiple time mostly helps to get the screen 
active.

  Current partial workaround:
  xorg.conf with monitor section for 1920x1200 as in attatchment.
  This doesn't solve booting in 1024x768, but solves the resolution after 
logging in.
  unity-control-center still lists Unknown Screen

  Another strange behavior:
  when executing xrandr command, most of the time the 2415 stays in 1024, but 
after a number of executions the screen swithes to 1920x1200. At that moment 
xrandr outputs all possible resolutions as it should.
  When executing xrandr another time the 2415 switches back to 1024x768

  Already tried kernel v3.18.3-vivid, no change.
  Also tried Utopic live cd, no change.
  Tried Windows 8.1, no issues with both screens. (however my main OS is Ubuntu 
trusty, so..., just for testing)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-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: Tue Jan 20 10:48:24 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-43-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Broadway XT [Mobility Radeon HD 5870] 
[1002:68a0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company FirePro M7820 [103c:1520]
  InstallationDate: Installed on 2014-05-11 (253 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 8740w
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/@trusty/boot/vmlinuz-3.13.0-44-generic 
root=UUID=cfafe8f3-4766-4fc7-b6f3-857eefcd2aff ro rootflags=subvol=@trusty 
plymouth:debug splash quiet drm.debug=0xe radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.50
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.31
  dmi.chassis.asset.tag: CNU1152Q9W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Touch-packages] [Bug 1419249] Re: UFW not allowing GEOIP rule

2015-02-20 Thread Bug Watch Updater
** Changed in: ufw (Debian)
   Status: Unknown = New

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

Title:
  UFW not allowing GEOIP rule

Status in ufw package in Ubuntu:
  Incomplete
Status in ufw package in Debian:
  New

Bug description:
  Hai,

  Ufw is not allowing my GEOIP country block rule.

  I tried to add these  rules.  ( which work fine when added with
  iptables )

  -A ufw-before-logging-input -m geoip --src-cc KR,CN,VN,UA,BR,VE,JP -m limit 
--limit 3/minute -j LOG --log-level 5 --log-prefix '[UFW BLOCK COUNTRIES] '
  -A ufw-before-logging-input -m geoip --src-cc KR,CN,VN,UA,BR,VE,JP -j DROP

  
  i get the message UFW INIT error. 

  if i manualy add these rules with iptables they work fine, but these
  rules dissapeer after a while, how come ?

  and yes, even if i add these rule to ufw-before-input the same happens. 
  I cant figure this out so im reporting this as a bug. 

  At least how can i make it so that it stops removing (somehow) my
  geoip rules.. i really need them for security reasons.

  Im running ubuntu 14.04 LTS

  TLo

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

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


[Touch-packages] [Bug 1424114] [NEW] lvm snapshot is not being autoextended

2015-02-20 Thread Doug Fultz
Public bug reported:

After setting auto extend threshold and rebooting, lvm snapshots are not
being auto extended.

Steps to recreate:
1. Using Ubuntu 14.04 LTS
2. Set snapshot_autoextend_threshold to less than 100
# grep autoext /etc/lvm/lvm.conf 
snapshot_autoextend_threshold = 50
snapshot_autoextend_percent = 20
3. Reboot server to have lvm reread lvm.conf
4. Create a snapshot of a mounted logical volume
# lvcreate -s /dev/testVG/testLV -L 1G -n testLVsnap
5. Make modifications to mounted logical volume
6. List logical volumes and snapshots
# lvs
  LV VG Attr  LSize  Pool Origin Data%  Move Log Copy%  Convert
  testLV testVG owi-aos-- 10.00g   
  testLVsnap testVG swi-a-s--  1.00g  testLV  95.04

What I expected to have happened:
Once Data% of snapshot reached the snapshot_autoextend_threshold, the snapshot 
logical volume should have been auto extended.

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


** Tags: lvm snapshot

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

Title:
  lvm snapshot is not being autoextended

Status in lvm2 package in Ubuntu:
  New

Bug description:
  After setting auto extend threshold and rebooting, lvm snapshots are
  not being auto extended.

  Steps to recreate:
  1. Using Ubuntu 14.04 LTS
  2. Set snapshot_autoextend_threshold to less than 100
  # grep autoext /etc/lvm/lvm.conf 
  snapshot_autoextend_threshold = 50
  snapshot_autoextend_percent = 20
  3. Reboot server to have lvm reread lvm.conf
  4. Create a snapshot of a mounted logical volume
  # lvcreate -s /dev/testVG/testLV -L 1G -n testLVsnap
  5. Make modifications to mounted logical volume
  6. List logical volumes and snapshots
  # lvs
LV VG Attr  LSize  Pool Origin Data%  Move Log Copy%  
Convert
testLV testVG owi-aos-- 10.00g  
 
testLVsnap testVG swi-a-s--  1.00g  testLV  95.04

  What I expected to have happened:
  Once Data% of snapshot reached the snapshot_autoextend_threshold, the 
snapshot logical volume should have been auto extended.

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

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


[Touch-packages] [Bug 1424117] [NEW] package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-02-20 Thread awer
Public bug reported:

Ubuntu 14.10

package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: cups-daemon 1.7.5-3ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
CupsErrorLog:
 
Date: Fri Feb 20 21:19:27 2015
DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-01-07 (44 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
MachineType: LENOVO Lenovo IdeaPad Y580
Papersize: a4
PpdFiles:
 Brother-HL-2170W: Brother HL-2170W Foomatic/lj4dith
 Brother-HL-2170W-series: Brother HL-2170W Foomatic/hl1250
 Hewlett-Packard-HP-LaserJet-1020: HP LaserJet 1020 Foomatic/foo2zjs-z1 
(recommended)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
SourcePackage: cups
Title: package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5DCN40WW(V2.07)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Mainboard version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y580
dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN40WW(V2.07):bd10/10/2012:svnLENOVO:pnLenovoIdeaPadY580:pvrLenovoIdeaPadY580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
dmi.product.name: Lenovo IdeaPad Y580
dmi.product.version: Lenovo IdeaPad Y580
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package utopic

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

Title:
  package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10

  package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: cups-daemon 1.7.5-3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Feb 20 21:19:27 2015
  DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-01-07 (44 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO Lenovo IdeaPad Y580
  Papersize: a4
  PpdFiles:
   Brother-HL-2170W: Brother HL-2170W Foomatic/lj4dith
   Brother-HL-2170W-series: Brother HL-2170W Foomatic/hl1250
   Hewlett-Packard-HP-LaserJet-1020: HP LaserJet 1020 Foomatic/foo2zjs-z1 
(recommended)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
  SourcePackage: cups
  Title: package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN40WW(V2.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 

[Touch-packages] [Bug 1424117] Re: package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2015-02-20 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 cups in Ubuntu.
https://bugs.launchpad.net/bugs/1424117

Title:
  package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in cups package in Ubuntu:
  New

Bug description:
  Ubuntu 14.10

  package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: cups-daemon 1.7.5-3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Feb 20 21:19:27 2015
  DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-01-07 (44 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: LENOVO Lenovo IdeaPad Y580
  Papersize: a4
  PpdFiles:
   Brother-HL-2170W: Brother HL-2170W Foomatic/lj4dith
   Brother-HL-2170W-series: Brother HL-2170W Foomatic/hl1250
   Hewlett-Packard-HP-LaserJet-1020: HP LaserJet 1020 Foomatic/foo2zjs-z1 
(recommended)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=5f67b03e-c274-4953-b487-b67be9d10ae7 ro quiet splash
  SourcePackage: cups
  Title: package cups-daemon 1.7.5-3ubuntu3 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5DCN40WW(V2.07)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Mainboard version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Y580
  dmi.modalias: 
dmi:bvnLENOVO:bvr5DCN40WW(V2.07):bd10/10/2012:svnLENOVO:pnLenovoIdeaPadY580:pvrLenovoIdeaPadY580:rvnLENOVO:rnProductName:rvrMainboardversion:cvnLENOVO:ct10:cvrLenovoIdeaPadY580:
  dmi.product.name: Lenovo IdeaPad Y580
  dmi.product.version: Lenovo IdeaPad Y580
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 1412730] Re: DELL U2415 monitor detection issues

2015-02-20 Thread Matthew Tucker-Simmons
Just wanted to add that I am experiencing a similar issue with the 2415
not waking after suspend. I don't seem to be having the some problems
with screen resolution, monitor detection, or weirdness with xrandr
commands. If I can get the monitor working, xrandr works correctly every
time.

Essentially, if the screen goes into power save mode, I am forced to
reboot in order to wake it up.

My other monitor is an HP ZR24w and I'm running a fully updated 14.04 on
a desktop machine.

I'm not sure what further info or log files might be useful, but let me
know and I'll try to provide whatever I can.

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

Title:
  DELL U2415 monitor detection issues

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My Laptop HP Elitebook 8740w has two external screens connected.
  1 DELL U2412M connected to vga connector
  1 DELL U2415 connected to Displayport.

  I worked for about a year with a single external display, just U2412M
  on the displayport without the issue I decribe.

  The first issue:
  When booting up and with screens attatched and active, the 2415 boots in 
1024x768 resolution, the 2412 boots at the same moment in 1920x1200 as it 
should.
  At the point where the login screen appears the 2415 goes in power save mode, 
most of the time.
  The 2412 displays just fine at the moment.
  After logging in, turning the 2415 off and on, sometimes helps the get the 
screen active (out of power save).
  When it gets active, the resoltion is 1024x768, not 1920x1200.
  In unity-control-center in display settings the 2415 is displayed as Unknown 
Display and the maximum resolution I can select is 1024x768.

  Second issue:
  After a laptop suspend the 2415 doenst alway become active again, the 2412 
always.
  Turning off an on the 2415 multiple time mostly helps to get the screen 
active.

  Current partial workaround:
  xorg.conf with monitor section for 1920x1200 as in attatchment.
  This doesn't solve booting in 1024x768, but solves the resolution after 
logging in.
  unity-control-center still lists Unknown Screen

  Another strange behavior:
  when executing xrandr command, most of the time the 2415 stays in 1024, but 
after a number of executions the screen swithes to 1920x1200. At that moment 
xrandr outputs all possible resolutions as it should.
  When executing xrandr another time the 2415 switches back to 1024x768

  Already tried kernel v3.18.3-vivid, no change.
  Also tried Utopic live cd, no change.
  Tried Windows 8.1, no issues with both screens. (however my main OS is Ubuntu 
trusty, so..., just for testing)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-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: Tue Jan 20 10:48:24 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-43-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Broadway XT [Mobility Radeon HD 5870] 
[1002:68a0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company FirePro M7820 [103c:1520]
  InstallationDate: Installed on 2014-05-11 (253 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 8740w
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/@trusty/boot/vmlinuz-3.13.0-44-generic 
root=UUID=cfafe8f3-4766-4fc7-b6f3-857eefcd2aff ro rootflags=subvol=@trusty 
plymouth:debug splash quiet drm.debug=0xe radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.50
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.31
  dmi.chassis.asset.tag: CNU1152Q9W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  

[Touch-packages] [Bug 1424122] Stacktrace.txt

2015-02-20 Thread Apport retracing service
** Attachment added: Stacktrace.txt
   
https://bugs.launchpad.net/bugs/1424122/+attachment/4323730/+files/Stacktrace.txt

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Got that crash on opening a gnome-shell session after a cold boot with
  systemd-sysv

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sat Feb 21 05:11:24 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1424122] StacktraceSource.txt

2015-02-20 Thread Apport retracing service
** Attachment added: StacktraceSource.txt
   
https://bugs.launchpad.net/bugs/1424122/+attachment/4323731/+files/StacktraceSource.txt

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Got that crash on opening a gnome-shell session after a cold boot with
  systemd-sysv

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sat Feb 21 05:11:24 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1424122]

2015-02-20 Thread Apport retracing service
StacktraceTop: main (argc=1, argv=0xbff9fcb4) at /build/buildd
/indicator-sound-12.10.2+15.04.20150219.1/src/main.c:53

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Got that crash on opening a gnome-shell session after a cold boot with
  systemd-sysv

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sat Feb 21 05:11:24 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1424122] ThreadStacktrace.txt

2015-02-20 Thread Apport retracing service
** Attachment added: ThreadStacktrace.txt
   
https://bugs.launchpad.net/bugs/1424122/+attachment/4323732/+files/ThreadStacktrace.txt

** Attachment removed: CoreDump.gz
   
https://bugs.launchpad.net/bugs/1424122/+attachment/4323721/+files/CoreDump.gz

** Changed in: indicator-sound (Ubuntu)
   Importance: Undecided = Medium

** Tags removed: need-i386-retrace

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

Title:
  indicator-sound-service crashed with signal 5 in main()

Status in indicator-sound package in Ubuntu:
  New

Bug description:
  Got that crash on opening a gnome-shell session after a cold boot with
  systemd-sysv

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0
  Uname: Linux 3.19.0-5-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  Date: Sat Feb 21 05:11:24 2015
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-sound/indicator-sound-service
  Signal: 5
  SourcePackage: indicator-sound
  StacktraceTop: main ()
  Title: indicator-sound-service crashed with signal 5 in main()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Touch-packages] [Bug 1412730] Re: DELL U2415 monitor detection issues

2015-02-20 Thread Matthew Tucker-Simmons
I neglected to mention that my monitor is also connected via
displayport. I am going to order an HDMI cable to see if that fixes it,
will post back here again either way.

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

Title:
  DELL U2415 monitor detection issues

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My Laptop HP Elitebook 8740w has two external screens connected.
  1 DELL U2412M connected to vga connector
  1 DELL U2415 connected to Displayport.

  I worked for about a year with a single external display, just U2412M
  on the displayport without the issue I decribe.

  The first issue:
  When booting up and with screens attatched and active, the 2415 boots in 
1024x768 resolution, the 2412 boots at the same moment in 1920x1200 as it 
should.
  At the point where the login screen appears the 2415 goes in power save mode, 
most of the time.
  The 2412 displays just fine at the moment.
  After logging in, turning the 2415 off and on, sometimes helps the get the 
screen active (out of power save).
  When it gets active, the resoltion is 1024x768, not 1920x1200.
  In unity-control-center in display settings the 2415 is displayed as Unknown 
Display and the maximum resolution I can select is 1024x768.

  Second issue:
  After a laptop suspend the 2415 doenst alway become active again, the 2412 
always.
  Turning off an on the 2415 multiple time mostly helps to get the screen 
active.

  Current partial workaround:
  xorg.conf with monitor section for 1920x1200 as in attatchment.
  This doesn't solve booting in 1024x768, but solves the resolution after 
logging in.
  unity-control-center still lists Unknown Screen

  Another strange behavior:
  when executing xrandr command, most of the time the 2415 stays in 1024, but 
after a number of executions the screen swithes to 1920x1200. At that moment 
xrandr outputs all possible resolutions as it should.
  When executing xrandr another time the 2415 switches back to 1024x768

  Already tried kernel v3.18.3-vivid, no change.
  Also tried Utopic live cd, no change.
  Tried Windows 8.1, no issues with both screens. (however my main OS is Ubuntu 
trusty, so..., just for testing)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-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: Tue Jan 20 10:48:24 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-43-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Broadway XT [Mobility Radeon HD 5870] 
[1002:68a0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company FirePro M7820 [103c:1520]
  InstallationDate: Installed on 2014-05-11 (253 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 8740w
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcKernelCmdLine: BOOT_IMAGE=/@trusty/boot/vmlinuz-3.13.0-44-generic 
root=UUID=cfafe8f3-4766-4fc7-b6f3-857eefcd2aff ro rootflags=subvol=@trusty 
plymouth:debug splash quiet drm.debug=0xe radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.50
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.31
  dmi.chassis.asset.tag: CNU1152Q9W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  

Re: [Touch-packages] [Bug 1404779] Re: Hp Designjet 130 prints part of page then freezes

2015-02-20 Thread Rod Boudreaux
Ok We can inform Ubuntu about this. I found the solution. I just don't 
know who to send it to.
Ubuntu 14.10 uses the :

HP-DesignJet_130-cdnj500.ppd

as the driver for the HP DesignJet 130 printer.
This driver does not work properly.
However by changing the driver to :

HP-DesignJet_130-chp220.ppd

Which is also an option, it is working great as far as I have tested it.

Thanks for Jugging me to pursue it further. I can now retire my old XP
O/S.

On 02/19/2015 05:11 PM, Rod Boudreaux wrote:
 Ok Seems like we got off track. Where should I go to get help?

 When I connect my HP DesignJet 130 to Ubuntu 14.10 it installs a driver
 that says it is for my printer.

 attached is a picture of the printer properties that shows the details.

 Also attached is the HP-DesignJet_130_cdnj500.ppd which appears to be
 the driver scrip.

 The driver prints part of a page then freezes. However it printed one
 test page complete When I set it to 11x17.

 Please direct me to the proper place to get help. If you need more
 information let me know.

 On 02/19/2015 02:07 AM, Sanjay Kumar wrote:
 Hello Rod,

 HP Designjet 130 printer is not supported in HP Linux driver (HPLIP).
 List of Designjet printers Supported/Not_Supported can be found at
 http://hplipopensource.com/hplip-web/supported_devices/designjet.html .
 Sorry for the inconvenience caused.

 Thanks,
 Sanjay


 ** Attachment added: HP-DesignJet_130-cdnj500.ppd
 
 https://bugs.launchpad.net/bugs/1404779/+attachment/4322824/+files/HP-DesignJet_130-cdnj500.ppd

 ** Attachment added: printerProperties.png
 
 https://bugs.launchpad.net/bugs/1404779/+attachment/4322825/+files/printerProperties.png


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

Title:
  Hp Designjet 130 prints part of page then freezes

Status in HP Linux Imaging and Printing:
  New
Status in cups package in Ubuntu:
  New

Bug description:
  Cups

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

  
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ lsmod | grep usb
  usblp  18277  0 
  usbhid 47070  0 
  hid87604  2 hid_generic,usbhid
  rod@rod-HP-Compaq-dc7900-Convertible-Minitower:~$ tail -f /var/log/syslog
  Dec 21 21:45:39 rod-HP-Compaq-dc7900-Convertible-Minitower python: 
io/hpmud/musb.c 2105: ignoring hp:/usb/hp_designjet_130?serial=MY6AID80CM 
support=0
  Dec 21 21:45:39 rod-HP-Compaq-dc7900-Convertible-Minitower python: 
io/hpmud/pp.c 627: unable to read device-id ret=-1
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.816339] type=1400 audit(1419216354.023:68): apparmor=DENIED 
operation=signal profile=/usr/sbin/cupsd pid=2520 comm=cups-deviced 
requested_mask=send denied_mask=send signal=term peer=unconfined
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.818276] type=1400 audit(1419216354.023:69): apparmor=DENIED 
operation=signal profile=/usr/sbin/cupsd pid=2150 comm=cupsd 
requested_mask=send denied_mask=send signal=term peer=unconfined
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.820058] parport0: lp tried to release parport when not owner
  Dec 21 21:45:54 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
1975.820072] parport0: ppdev0 forgot to release port
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2294.664108] usb 3-2: USB disconnect, device number 4
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2294.664280] usblp0: removed
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower 
udev-configure-printer: remove /devices/pci:00/:00:1a.0/usb3/3-2
  Dec 21 21:51:12 rod-HP-Compaq-dc7900-Convertible-Minitower colord: device 
removed: sysfs-Hewlett-Packard-hp_designjet_130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.104036] usb 3-2: new full-speed USB device number 5 using uhci_hcd
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303075] usb 3-2: New USB device found, idVendor=03f0, idProduct=0314
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303080] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303083] usb 3-2: Product: hp designjet 130
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303085] usb 3-2: Manufacturer: Hewlett-Packard
  Dec 21 21:51:45 rod-HP-Compaq-dc7900-Convertible-Minitower kernel: [ 
2327.303088] usb 3-2: SerialNumber: MY6AID80CM
  Dec 21 21:51:45 

  1   2   >