[Touch-packages] [Bug 1522746] Re: apply palette on ListItem drag mode background

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

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

Title:
  apply palette on ListItem drag mode background

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  May require additional API to be added.

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

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

[Touch-packages] [Bug 1523237] [NEW] Stuck at 640x480 screen resolution

[Marcin Wojtarowicz]

Public bug reported:

Ubuntu 14.04.03 LTS
Xorg version: 1:7.7+1ubuntu8.1

! Live cd worked at native resolution. !
After installing it on hard drive I'm left with maximum 640x480:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
default connected primary 640x480+0+0 0mm x 0mm
   640x48073.0* 

Installing mesa-utils and xserver-xorg-lts-precise didn't help

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
Uname: Linux 3.19.0-39-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.19
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: Sun Dec  6 15:10:44 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter [1039:6351] 
(rev 10) (prog-if 00 [VGA controller])
   Subsystem: Fujitsu Technology Solutions Device [1734:1125]
InstallationDate: Installed on 2015-12-06 (0 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5535
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-39-generic 
root=UUID=2ff25fe2-c953-4546-9c99-c6a2e205c495 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf: Section "Device" Identifier "Card0" Driver "Intel" Option 
"AccelMethod" "sna" EndSection
dmi.bios.date: 09/30/08
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.08
dmi.board.name: Z17M2.0
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 04
dmi.chassis.type: 1
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: 1.2
dmi.modalias: 
dmi:bvnPhoenix:bvrV1.08:bd09/30/08:svnFUJITSUSIEMENS:pnESPRIMOMobileV5535:pvrV1.06:rvnFUJITSUSIEMENS:rnZ17M2.0:rvr04:cvnFUJITSUSIEMENS:ct1:cvr1.2:
dmi.product.name: ESPRIMO Mobile V5535
dmi.product.version: V1.06
dmi.sys.vendor: FUJITSU SIEMENS
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Dec  6 15:08:46 2015
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.1-0ubuntu3~trusty1

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


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

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

Title:
  Stuck at 640x480 screen resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.03 LTS
  Xorg version: 1:7.7+1ubuntu8.1

  ! Live cd worked at native resolution. !
  After installing it on hard drive I'm left with maximum 640x480:

  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
  default connected primary 640x480+0+0 0mm x 0mm
 640x48073.0* 

  Installing mesa-utils and xserver-xorg-lts-precise didn't help

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Sun Dec  6 15:10:44 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology 

[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

[Maxime.J]

Bug report for the Packard Bell DOTS:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523232

Thanks.

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

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

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

[Touch-packages] [Bug 1523232] [NEW] Packard Bell DOTS inverted internal microphone

[Maxime.J]

Public bug reported:

As stated in https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978,
I attached the alsa-info txt to this bug for the Packard Bell DOTS.

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

** Attachment added: "alsa-info.txt"
   
https://bugs.launchpad.net/bugs/1523232/+attachment/4530453/+files/alsa-info.txt

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

Title:
  Packard Bell DOTS inverted internal microphone

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As stated in 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978,
  I attached the alsa-info txt to this bug for the Packard Bell DOTS.

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

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

[Touch-packages] [Bug 1515446] Re: NFS shares in FSTAB no longer mount at boot

[mtd0]

I've been able to work around the problem by adding
'x-systemd.automount,' to the list of options on the fstab line.

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in nfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 15.10, nfs shares no longer mount on boot.
  I'm using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
 Loaded: loaded (/etc/fstab)
 Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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

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

[Touch-packages] [Bug 1518118] Re: IBus 1.5.11 needs to be packaged, to avoid breaking certain software

[Launchpad Bug Tracker]

*** This bug is a duplicate of bug 1512956 ***
https://bugs.launchpad.net/bugs/1512956

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

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

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

Title:
  IBus 1.5.11 needs to be packaged, to avoid breaking certain software

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  IBus 1.5.11 needs to be packaged.

  Whenever I launch a recent JetBrains IDE (such as PyCharm), it warns
  on startup that IBus has a bug that can cause input to be blocked.

  See: https://youtrack.jetbrains.com/issue/IDEA-78860

  They claim that IBus 1.5.11 is needed in order to resolve the issue.

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

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

[Touch-packages] [Bug 1523261] [NEW] Unable to access sites using a self-signed SSL certificate

[Laryllan]

Public bug reported:

Hi there,

I'm trying to access my owncloud hosted on my private NAS.

WHAT I EXPECT:
I can accept the certificate and access my OwnCloud.

WHAT HAPPENS:
I cannot access my OwnCloud.
It shows the login prompt, but doesn't allow me to log in.
As if the login button doesn't work.

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

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

Title:
  Unable to access sites using a self-signed SSL certificate

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Hi there,

  I'm trying to access my owncloud hosted on my private NAS.

  WHAT I EXPECT:
  I can accept the certificate and access my OwnCloud.

  WHAT HAPPENS:
  I cannot access my OwnCloud.
  It shows the login prompt, but doesn't allow me to log in.
  As if the login button doesn't work.

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

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

[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

[xtrchessreal]

You held down alt+SysRq and then typed REISUB one key at a time, and that 
didn't work?
This: "Dec 5 09:31:21 deepblue systemd[1811]: shutdown.target: Fixing 
conflicting jobs shutdown.target/stop,shutdown.target/start by deleting job 
shutdown.target/stop" Looks like something is wrong but I am not expert - you 
might be onto something.  I'm gonna do what you did and see what I get in 
Syslog.
This still affects me in 15.04 and only when I run Chromium but every time I 
run Chromium SMH - I hate intermittent issues.  Firefox does not cause this - 
go figure.

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

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted my 15.04 system, and found it hanging indefinitely at the
  plymouth shutdown screen.  Hitting esc to reveal the console showed a
  normal set of shutdown messages, ending with 'Reached target Shutdown'
  (paraphrased from memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1492546] Re: Systemd runs ifdown on shutdown even when it shouldn't

[Alkis Georgopoulos]

Martin, I'm seeing a regression for this with systemd 228-2ubuntu1 in Ubuntu 
Xenial.
Now I again have to remove the "ExecStop=/sbin/ifdown %I" stanza in order to 
get netbooted clients to shut down.

Maybe something else is stopping the ifup service on shutdown now?
I tried to downgrade to the version shipped with Wily, but I was blocked by 
some dependency issues.

** Changed in: systemd (Ubuntu)
   Status: Fix Released => 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/1492546

Title:
  Systemd runs ifdown on shutdown even when it shouldn't

Status in ltsp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Fix Released

Bug description:
  The unit /lib/systemd/system/ifup@.service is Debian and Ubuntu specific, 
it's not part of upstream systemd.
  On shutdown, it unconditionally ifdowns all interfaces:
ExecStop=/sbin/ifdown %I

  This is a regression from previous init systems (sysvinit and upstart)
  which cared so that when a network file system was in use, they didn't
  ifdown the interfaces.

  Specifically, both /etc/init.d/networking and /etc/init/networking contain 
these functions:
check_network_file_systems()
check_network_swaps()
  which output the message "not deconfiguring network interfaces: network file 
systems still mounted" and exit.

  So, please call the same functions in the ExecStop= part of
  ifup@.service.

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

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

[Touch-packages] [Bug 221363] Re: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP

[Alkis Georgopoulos]

Is this still an issue in recent Ubuntu/LTSP versions?

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

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

Title:
  Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP

Status in FreeNX Server:
  Fix Released
Status in gdm:
  New
Status in PolicyKit:
  Invalid
Status in system-tools-backends:
  Fix Released
Status in ltsp package in Ubuntu:
  Incomplete
Status in policykit package in Ubuntu:
  Invalid
Status in policykit-1 package in Ubuntu:
  Invalid
Status in system-tools-backends package in Ubuntu:
  Triaged

Bug description:
  I installed 8.04 LTS server on a system.  Then installed ubuntu-
  desktop using apt.  Installed Nomachine's NX server and connected to
  it.

  The unlock buttons on Users and Groups or Network are greyed out and
  un-accessible.  Tried running from a term 'sudo users-admin' with the
  same results.

  Works fine with VNC and NX "Shadow" session however this is not really
  acceptable as it means a session has to be running on console first.

  I have tried to enable every option in Authorizations to allow the
  remote session to have privileges to no avail.

  output of dpkg relevant packages:

  ii  gnome-system-t 2.22.0-0ubuntu Cross-platform configuration utilities for G
  ii  liboobs-1-42.22.0-0ubuntu GObject based interface to system-tools-back
  ii  policykit  0.7-2ubuntu7   framework for managing administrative polici
  ii  system-tools-b 2.6.0-0ubuntu7 System Tools to manage computer configuratio

  
  == Workarounds  ==
  

  1) *Jaunty or older*

  From
  https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/238799/comments/16
  (the packages from comment 24 are broken links now):

  I was able to get access via VNC tunneled through SSH by changing the
  following settings in policykit. You can do it locally via
  Authorizations, or you can do it remotely using "sudo ck-launch-
  session polkit-gnome-authorization" in a terminal window in your
  tunneled VNC session. This worked on Ubuntu 9.04 Server RC running
  xubuntu-desktop, so as always YMMV.

  For system configuration, change all implicit authorizations under org
  -> freedesktop -> systemtoolsbackends -> Manage System Configuration
  (org.freedesktop.systemtoolsbackends.set) to "Admin Authentication."

  For user management, change all implicit authorizations under org ->
  freedesktop -> systemtoolsbackends -> self -> Change User
  Configuration (org.freedesktop.systemtoolsbackends.self.set) to
  "Authentication."

  Reset gdm by rebooting or running "sudo /etc/init.d/gdm restart" from
  a terminal window, and you should be able to unlock the user settings
  control panel and other similarly useful things through your tunneled
  VNC session.

  2) *Karmic or newer*

  Apply this patch: 
http://launchpadlibrarian.net/39471473/polkit-systemtools-remote-allow.patch
  # sudo cp -a 
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy 
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy.ori
  # sudo patch 
/usr/share/polkit-1/actions/org.freedesktop.SystemToolsBackends.policy 
polkit-systemtools-remote-allow.patch

  Then kill polkitd, it will be restarted automatically:
  # sudo pkill polkitd

To manage notifications about this bug go to:
https://bugs.launchpad.net/freenx-server/+bug/221363/+subscriptions

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

[Touch-packages] [Bug 1515446] Re: NFS shares in FSTAB no longer mount at boot

[Doug Rohm]

@mtd0, adding that to my fstab worked as well.

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in nfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 15.10, nfs shares no longer mount on boot.
  I'm using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
 Loaded: loaded (/etc/fstab)
 Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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

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

[Touch-packages] [Bug 1313370] Re: Support for installing Digital Certificates

[Laryllan]

I guess this is why I can't access my OwnCloud with a self-signed
certificate?

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

Title:
  Support for installing Digital Certificates

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  I am trying to enter a page, and to me it is necessary to have in the
  digital certificate installed browser. Where is the option to install
  the digital certificate. Without that the browser is unusable.

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

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

[Touch-packages] [Bug 1518118] Re: IBus 1.5.11 needs to be packaged, to avoid breaking certain software

[jesper knutzen]

*** This bug is a duplicate of bug 1512956 ***
https://bugs.launchpad.net/bugs/1512956

+1

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

Title:
  IBus 1.5.11 needs to be packaged, to avoid breaking certain software

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  IBus 1.5.11 needs to be packaged.

  Whenever I launch a recent JetBrains IDE (such as PyCharm), it warns
  on startup that IBus has a bug that can cause input to be blocked.

  See: https://youtrack.jetbrains.com/issue/IDEA-78860

  They claim that IBus 1.5.11 is needed in order to resolve the issue.

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

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

[Touch-packages] [Bug 1523261] Re: Unable to access sites using a self-signed SSL certificate

[Laryllan]

** Attachment added: "the page is not loaded correctly"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1523261/+attachment/4530525/+files/screenshot.png

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

Title:
  Unable to access sites using a self-signed SSL certificate

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Hi there,

  I'm trying to access my owncloud hosted on my private NAS.

  WHAT I EXPECT:
  I can accept the certificate and access my OwnCloud.

  WHAT HAPPENS:
  I cannot access my OwnCloud.
  It shows the login prompt, but doesn't allow me to log in.
  As if the login button doesn't work.

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

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

[Touch-packages] [Bug 1173915] Re: initctl continuously takes 100% of CPU

[Юрий Чудновский]

Confirming for Ubuntu 15.10 64bit, HP Probook 4320s, after day-two
uptime.

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

Title:
  initctl continuously takes 100% of CPU

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Many programs are fairly slow to start on my computer, despite it
  being relatively new (core i5). Suspecting a heavy CPU usage, I
  started gnome-system-monitor: all processes were displayed at 0% CPU,
  but the overall load was 1.33; 1.33; 1.34.

  Using the "top" command, however, revealed the real CPU use, with the
  "initctl" process taking 100%CPU, even 1 hour after startup.

  I upgraded to roaring ringtail before checking this but the symptoms
  were the same with quantal quetzal, so there is a fair chance the
  causes were identical.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a
  CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
  Date: Sun Apr 28 13:04:05 2013
  ExecutablePath: /sbin/initctl
  InstallationDate: Installed on 2012-12-15 (133 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  ProcEnviron:
   
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7
  SourcePackage: upstart
  UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago)
  UpstartBugCategory: System

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

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

[Touch-packages] [Bug 1523237] Re: Stuck at 640x480 screen resolution

[Marcin Wojtarowicz]

** Description changed:

  Ubuntu 14.04.03 LTS
  Xorg version: 1:7.7+1ubuntu8.1
  
  ! Live cd worked at native resolution. !
  After installing it on hard drive I'm left with maximum 640x480:
  
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
  default connected primary 640x480+0+0 0mm x 0mm
-640x48073.0* 
+    640x48073.0*
  
  Installing mesa-utils and xserver-xorg-lts-precise didn't help
+ 
+ =
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  .tmp.unity.support.test.1:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.19
  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: Sun Dec  6 15:10:44 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
-Subsystem: Fujitsu Technology Solutions Device [1734:1125]
+  Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
+    Subsystem: Fujitsu Technology Solutions Device [1734:1125]
  InstallationDate: Installed on 2015-12-06 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5535
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-39-generic 
root=UUID=2ff25fe2-c953-4546-9c99-c6a2e205c495 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf: Section "Device" Identifier "Card0" Driver "Intel" Option 
"AccelMethod" "sna" EndSection
  dmi.bios.date: 09/30/08
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.08
  dmi.board.name: Z17M2.0
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: 04
  dmi.chassis.type: 1
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: 1.2
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.08:bd09/30/08:svnFUJITSUSIEMENS:pnESPRIMOMobileV5535:pvrV1.06:rvnFUJITSUSIEMENS:rnZ17M2.0:rvr04:cvnFUJITSUSIEMENS:ct1:cvr1.2:
  dmi.product.name: ESPRIMO Mobile V5535
  dmi.product.version: V1.06
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Dec  6 15:08:46 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  
+ 
  xserver.version: 2:1.17.1-0ubuntu3~trusty1

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

Title:
  Stuck at 640x480 screen resolution

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 14.04.03 LTS
  Xorg version: 1:7.7+1ubuntu8.1

  ! Live cd worked at native resolution. !
  After installing it on hard drive I'm left with maximum 640x480:

  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
  default connected primary 640x480+0+0 0mm x 0mm
     640x48073.0*

  Installing mesa-utils and xserver-xorg-lts-precise didn't help

  =

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  Uname: Linux 3.19.0-39-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: 

[Touch-packages] [Bug 1523223] [NEW] error in man page

[rm damerell]

Public bug reported:


L-Ubuntu 14.04,  udev  204-5ubuntu20.15 (latest).   man udev  says that 
udev reads rules from 

/usr/lib/udev/rules.d
/run/udev/rules.d 

and

/etc/udev/rules.d

The first 2 do not exist. There are rule files in

/lib/udev/rules.d

but I do not know any way to find out whether or not these are being read.
(if any human reads this, I would be grateful if you could tell me).
I was advised to file a bug report.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: udev 204-5ubuntu20.15
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: i386
CurrentDesktop: LXDE
Date: Sun Dec  6 11:50:36 2015
InstallationDate: Installed on 2015-07-19 (140 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=30c969c8-8299-4020-8ecc-bc228a671810 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.

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


** Tags: apport-bug i386 trusty

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

Title:
  error in man page

Status in systemd package in Ubuntu:
  New

Bug description:
  
  L-Ubuntu 14.04,  udev  204-5ubuntu20.15 (latest).   man udev  says that 
  udev reads rules from 

  /usr/lib/udev/rules.d
  /run/udev/rules.d 

  and

  /etc/udev/rules.d

  The first 2 do not exist. There are rule files in

  /lib/udev/rules.d

  but I do not know any way to find out whether or not these are being read.
  (if any human reads this, I would be grateful if you could tell me).
  I was advised to file a bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: udev 204-5ubuntu20.15
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Dec  6 11:50:36 2015
  InstallationDate: Installed on 2015-07-19 (140 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Dell Inc. Inspiron 1525
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=30c969c8-8299-4020-8ecc-bc228a671810 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 566381] Re: Lag when using module-loopback

[Jason Robinson]

Sorry, meant to say on 15.04, not 14.04.

** Tags added: vivid

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

Title:
  Lag when using module-loopback

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  Using
  pactl load-module module-loopback
  I can route the mic input through output. However, the audio that comes out 
is about half a second behind the audio coming in. This is okay for some 
things, but for others, like musical instruments, game consoles, etc., the lag 
makes it pretty much unusable for these uses.
  Back in alsa this used to work fine without lag.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: nls_iso8859_1 nls_cp437 btrfs zlib_deflate crc32c 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs 
reiserfs pata_jmicron acpiphp michael_mic arc4 hidp rfcomm binfmt_misc sco 
bridge stp bnep l2cap vboxnetadp vboxnetflt dm_crypt snd_hda_codec_idt 
snd_hda_codec_intelhdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss 
snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi vboxdrv 
snd_rawmidi joydev snd_seq_midi_event lp snd_seq snd_timer snd_seq_device 
lib80211_crypt_tkip snd parport soundcore wl dell_wmi btusb psmouse dell_laptop 
dcdbas ricoh_mmc snd_page_alloc lib80211 sdhci_pci sdhci led_class serio_raw 
bluetooth dm_raid45 xor fbcon tileblit font bitblit softcursor vga16fb vgastate 
usbhid hid i915 drm_kms_helper ohci1394 drm i2c_algo_bit ieee1394 sky2 
intel_agp ahci video output
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthew   10508 F pulseaudio
   /dev/snd/pcmC0D0c:   matthew   10508 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matthew   10508 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:14f12c06,14f1000f,0010 
HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402'
 Controls  : 23
 Simple ctrls  : 12
  Date: Sun Apr 18 21:42:33 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 566381] Re: Lag when using module-loopback

[Jason Robinson]

Also on 14.04 and affected by this.

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

Title:
  Lag when using module-loopback

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  Using
  pactl load-module module-loopback
  I can route the mic input through output. However, the audio that comes out 
is about half a second behind the audio coming in. This is okay for some 
things, but for others, like musical instruments, game consoles, etc., the lag 
makes it pretty much unusable for these uses.
  Back in alsa this used to work fine without lag.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: nls_iso8859_1 nls_cp437 btrfs zlib_deflate crc32c 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs 
reiserfs pata_jmicron acpiphp michael_mic arc4 hidp rfcomm binfmt_misc sco 
bridge stp bnep l2cap vboxnetadp vboxnetflt dm_crypt snd_hda_codec_idt 
snd_hda_codec_intelhdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss 
snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi vboxdrv 
snd_rawmidi joydev snd_seq_midi_event lp snd_seq snd_timer snd_seq_device 
lib80211_crypt_tkip snd parport soundcore wl dell_wmi btusb psmouse dell_laptop 
dcdbas ricoh_mmc snd_page_alloc lib80211 sdhci_pci sdhci led_class serio_raw 
bluetooth dm_raid45 xor fbcon tileblit font bitblit softcursor vga16fb vgastate 
usbhid hid i915 drm_kms_helper ohci1394 drm i2c_algo_bit ieee1394 sky2 
intel_agp ahci video output
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthew   10508 F pulseaudio
   /dev/snd/pcmC0D0c:   matthew   10508 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matthew   10508 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:14f12c06,14f1000f,0010 
HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402'
 Controls  : 23
 Simple ctrls  : 12
  Date: Sun Apr 18 21:42:33 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1523225] [NEW] ubuntu-bug gives error message

[rm damerell]

Public bug reported:

L-ubuntu 14.04, apport 2.14.1-0ubuntu3.19 (latest). In terminal 
the command

ubuntu-bug apport

generates this error:

** (apport-gtk:5888): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-QrmYTrFUXT: Connection refused

but the command still seems to work.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.16
ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
Uname: Linux 3.13.0-66-generic i686
NonfreeKernelModules: wl
ApportLog:
 
ApportVersion: 2.14.1-0ubuntu3.16
Architecture: i386
CurrentDesktop: LXDE
Date: Sun Dec  6 12:12:21 2015
InstallationDate: Installed on 2015-07-19 (140 days ago)
InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 trusty

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

Title:
  ubuntu-bug gives error message

Status in apport package in Ubuntu:
  New

Bug description:
  L-ubuntu 14.04, apport 2.14.1-0ubuntu3.19 (latest). In terminal 
  the command

  ubuntu-bug apport

  generates this error:

  ** (apport-gtk:5888): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-QrmYTrFUXT: Connection
  refused

  but the command still seems to work.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.16
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic i686
  NonfreeKernelModules: wl
  ApportLog:
   
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Sun Dec  6 12:12:21 2015
  InstallationDate: Installed on 2015-07-19 (140 days ago)
  InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1504688] Re: fsck runs on every boot (clean install, single ext4 filesystem)

[korakios]

Workaround: disable fsck in /etc/fstab (not recommended).
Edit fstab and replace the last digit ("1" for the root partition, "2" for the 
others) with zero "0".
Waiting for a fix.

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

Title:
  fsck runs on every boot (clean install, single ext4 filesystem)

Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  fsck runs early on *every* boot (and always says "/dev/sda1: clean ...")
  The system was always shut down using the regular Unity mechanism (Gear->Shut 
Down...)

  Strangely, the "Last checked" time shown by "sudo dumpe2fs /dev/sda1"
  shows the date of installation and never changes.

  This system is a brand new, clean install from the 15.10 beta2 iso, with 
subsequent updates.
  I took all the installer defaults, which created a single ext4 file system.

  Please see attached:
bootscreen.png - screen shot of fsck output at start of bootup (from VM 
window)
dumpe2fs_out.txt - output from "sudo dumpe2fs /dev/sda1"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: upstart 1.13.2-0ubuntu16
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:10:05 2015
  InstallationDate: Installed on 2015-10-07 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic 
root=UUID=5944d29d-f058-4836-a160-4da2d77554e3 ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: upstart 1.13.2
  UpstartRunningSystemJobs:
   Error: command ['initctl', '--system', 'list'] failed with exit code 1: 
initctl: Name "com.ubuntu.Upstart" does not exist
  UpstartRunningSystemVersion: Error: command ['initctl', '--system', 
'version'] failed with exit code 1: initctl: Name "com.ubuntu.Upstart" does not 
exist

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

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

[Touch-packages] [Bug 1523196] [NEW] installation fails due to " unable to make backup symlink for './usr/bin/captoinfo': No such file or directory"

[Karl-Philipp Richter]

Public bug reported:

installation of `ncurses-bin` fails due to `installation fails due to "
unable to make backup symlink for './usr/bin/captoinfo': No such file or
directory"`

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ncurses-bin 5.9+20150516-2ubuntu1
Uname: Linux 4.2.5-040205-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Sun Dec  6 08:38:53 2015
Dependencies:
 gcc-5-base 5.2.1-22ubuntu2
 libc6 2.21-0ubuntu4
 libgcc1 1:5.2.1-22ubuntu2
 libtinfo5 5.9+20150516-2ubuntu1
InstallationDate: Installed on 2015-04-20 (229 days ago)
InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ncurses
UpgradeStatus: Upgraded to wily on 2015-10-26 (40 days ago)

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


** Tags: amd64 apport-bug wily

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

Title:
  installation fails due to " unable to make backup symlink for
  './usr/bin/captoinfo': No such file or directory"

Status in ncurses package in Ubuntu:
  New

Bug description:
  installation of `ncurses-bin` fails due to `installation fails due to
  " unable to make backup symlink for './usr/bin/captoinfo': No such
  file or directory"`

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ncurses-bin 5.9+20150516-2ubuntu1
  Uname: Linux 4.2.5-040205-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Sun Dec  6 08:38:53 2015
  Dependencies:
   gcc-5-base 5.2.1-22ubuntu2
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-22ubuntu2
   libtinfo5 5.9+20150516-2ubuntu1
  InstallationDate: Installed on 2015-04-20 (229 days ago)
  InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 
(20141022.2)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ncurses
  UpgradeStatus: Upgraded to wily on 2015-10-26 (40 days ago)

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

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

[Touch-packages] [Bug 1453538] Re: Invisible mouse pointer

[QkiZ]

I think it's different issue.

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

Title:
  Invisible mouse pointer

Status in Light Display Manager:
  Confirmed
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  After system boot on login screen mouse pointer is invisible. I am
  able to click to gadgets but its blind clicking. I dont know where is
  mouse pointer. When I'm switch to virtual console (CTRL+ALT+F1) and
  type

  sudo service lightdm restart

  command LightDM restarts and mouse pointer back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: lightdm 1.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-17.17-lowlatency 3.19.6
  Uname: Linux 3.19.0-17-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 10 14:27:50 2015
  InstallationDate: Installed on 2015-02-13 (85 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  LightdmConfig:
   [SeatDefaults]
   allow-guest = false
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to vivid on 2015-04-25 (15 days ago)

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

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

[Touch-packages] [Bug 1517998] Re: Crash after resume.

[Boban Aleksov]

I have i5 4210U CPU so, when i select I5-4xxxU  CPU family i am not offered 
with 503 bios, only with 310.
503 bios seems to be available only for i5-5xxxU familiy of CPU's. That is 
where misunderstanding came from.

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

Title:
  Crash after resume.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ocasional crash on resume, once in every 10 to 20 resume from standby.

  Using dual monitor setup, with laptop monitor disabled.
  Happened in 15.04 and in 15.10, although i think it is not so frequent in 
15.10 64bit.
  External display via VGA. It turns on display, and then freezes.

  WORKAROUND: Ensure bluetooth is disabled in the BIOS.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu4
  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: Thu Nov 19 18:19:25 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-11-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-17-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.2.0-18-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-17-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-18-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:16cd]
  InstallationDate: Installed on 2015-11-05 (14 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: ASUSTeK COMPUTER INC. X555LA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=b885d432-2156-4c66-91a3-d6b99d21a47e ro noprompt quiet splash 
acpi_osi= vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LA.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LA
  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.:bvrX555LA.310:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX555LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Nov 17 19:57:10 2015
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17132
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9

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

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

[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

[Steve Brorens]

It's just removed a kernel corrctly, so I've tagged as "confirmed"


** Changed in: unattended-upgrades (Ubuntu Trusty)
   Status: Fix Committed => Confirmed

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Confirmed

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies "true";'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

  but nothing happens (note the line "Packages that are auto removed: ''
  ":

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  Checking: bc ([""])
  Checking: grub-common ([""])
  Checking: grub-pc ([""])
  Checking: grub-pc-bin ([""])
  Checking: grub2-common ([""])
  Checking: iproute ([""])
  Checking: landscape-common ([""])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS

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

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

[Touch-packages] [Bug 1506914] Re: Screen brightness not working using keyboard shortcut fn+F5/F6 not working.

[Vidvranjek]

I upgraded my bios, here is the output:

vid@G550:~$  sudo dmidecode -s bios-version && sudo dmidecode -s 
bios-release-date
[sudo] password for vid: 
G550JK.205
09/26/2014

It didn't solve the problem, so I guess this isnt due to outdated BIOS?
What solves my problem is adding 'acpi_osi=' to '/etc/default/grub' as
such:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="

Can someone please explain what exactly is causing the problem and how
adding  'acpi_osi=' solvse it. Thanks!

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

Title:
  Screen brightness not working using keyboard shortcut fn+F5/F6 not
  working.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  
  The fix is editing /etc/default/grub and replacing 

   GRUB_CMDLINE_LINUX_DEFAULT=""
  with
   GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  run $ sudo update-grub
  reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.5
  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 Oct 16 17:27:47 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus: bbswitch, 0.7, 3.19.0-30-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. Device [1043:11cd]
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  MachineType: ASUSTeK COMPUTER INC. G550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=9a6cce6e-ddfb-40c7-a64c-823140602164 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G550JK.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G550JK
  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.:bvrG550JK.204:bd08/11/2014:svnASUSTeKCOMPUTERINC.:pnG550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1
  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.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Sat Oct 10 11:46:59 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [GLAMOR] failed to initialise EGL
   NOUVEAU(G0): Error creating GPU channel: -19
   NOUVEAU(G0): Error initialising acceleration.  Falling back to NoAccel
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.17.1-0ubuntu3.1

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

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

[Touch-packages] [Bug 1523261] Re: Unable to access sites using a self-signed SSL certificate

[Olivier Tilloy]

This is unlikely to be because of the self-signed certificate. Self-
signed certificates are correctly handled in webbrowser-app, when
accessing a site using one of those you should see a warning screen,
with two buttons: [back to safety] [proceed anyway]. If you choose to
proceed anyway, the browser will let you browse the site, and will
display a broken red lock in the address bar (as shown in your
screenshot).

Can you please reproduce the issue and attach the log file for
webbrowser-app. You will find it on your device at:

/home/phablet/.cache/upstart/application-legacy-webbrowser-app-.log

** Changed in: webbrowser-app (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- Unable to access sites using a self-signed SSL certificate
+ Unable to log in to owncloud hosted on private NAS

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

Title:
  Unable to log in to owncloud hosted on private NAS

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I'm trying to access my owncloud hosted on my private NAS.

  WHAT I EXPECT:
  I can accept the certificate and access my OwnCloud.

  WHAT HAPPENS:
  I cannot access my OwnCloud.
  It shows the login prompt, but doesn't allow me to log in.
  As if the login button doesn't work.

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

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

[Touch-packages] [Bug 1523072] Re: Physical Keyboard ENTER key doesn't work in input fields

[Olivier Tilloy]

*** This bug is a duplicate of bug 1433138 ***
https://bugs.launchpad.net/bugs/1433138

** This bug has been marked a duplicate of bug 1433138
   Bluetooth keyboard Return key does not work within web pages

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

Title:
  Physical Keyboard ENTER key doesn't work in input fields

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  WHAT HAPPENS: Pressing the ENTER key from a connected physical
  keyboard, does nothing. This includes when pressing enter after
  inputting your credentials to login and when you want to start a new
  line in a multiline input field.

  
  WHAT'S EXPECTED: Pressing the ENTER key should invoke the login/submit button 
when trying to login in a site and should insert a line feed when in a 
multiline input field.

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

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

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Uranicus]

One add-on to the Jabra device:

I realized that I have missed to put the "bluetoothctl", "info" data in
the report above (1). So I did the same procedure as above again today
and acquired the info data. But I also managed to get the info data the
second time after I have turned the Jabra off and back on again before
it looses connection (2).  The difference is that the
"ConnectedProfiles:" section is empty:

Information about the Jabra device directly after pairing before I have
turned it off and on again:

[JABRA 250]# info
Device 00:07:A4:00:A7:05
Name: JABRA 250
Alias: JABRA 250
Class: 0x200404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
ConnectedProfiles:
  Headset   (1108--1000-8000-00805f9b34fb)
  Handsfree (111e--1000-8000-00805f9b34fb)
LegacyPairing: yes
UUIDs:
  Headset   (1108--1000-8000-00805f9b34fb)
  Handsfree (111e--1000-8000-00805f9b34fb)

Information about the Jabra device after I have turned it off and on
again (before it looses connection to the phone):

[JABRA 250]# info
Device 00:07:A4:00:A7:05
Name: JABRA 250
Alias: JABRA 250
Class: 0x20040c
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
ConnectedProfiles:
  None
LegacyPairing: yes
UUIDs:
  Headset   (1108--1000-8000-00805f9b34fb)
  Handsfree (111e--1000-8000-00805f9b34fb)

Hope this also helps in finding the issue.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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

[Touch-packages] [Bug 1508744] Re: Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade

[Julian Edwards]

I was getting this too. I say was, because Adam's tip helped me resolve
it. I'll also note that this is on a machine still running vivid.

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

Title:
  Upgrade to Ubuntu 15.10 Broken: lxc-net.service fails on upgrade

Status in Release Notes for Ubuntu:
  New
Status in lxc package in Ubuntu:
  Incomplete

Bug description:
  With lxc installed, the 15.04 -> 15.10 upgrade fails. The upgrade
  completes if LXC is removed and then reinstalled later. Here is me
  using apt to try and make it work (gives same errors as upgrade-
  manager did):

  
  Setting up lxc (1.1.4-0ubuntu1) ...
  Job for lxc-net.service failed because the control process exited with error 
code. See "systemctl status lxc-net.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript lxc-net, action "start" failed.
  dpkg: error processing package lxc (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of lxc-templates:
   lxc-templates depends on lxc (>= 0.8.0~rc1-4ubuntu43); however:
Package lxc is not configured yet.

  dpkg: error processing package lxc-templates (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   lxc
   lxc-templates
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ╭─michael@michael-desktop-ubuntu  ~ ‹› 
  ╰─$ systemctl status lxc-net.service  

   100 ↵
  ● lxc-net.service - LXC network bridge setup
 Loaded: loaded (/lib/systemd/system/lxc-net.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2015-10-22 12:50:07 AEDT; 27s 
ago
Process: 22655 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-net start 
(code=exited, status=1/FAILURE)
   Main PID: 22655 (code=exited, status=1/FAILURE)

  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: Starting LXC network 
bridge setup...
  Oct 22 12:50:07 michael-desktop-ubuntu lxc-net[22655]: lxc-net is already 
running
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Main 
process exited, code=exited, status=1/FAILURE
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: Failed to start LXC 
network bridge setup.
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Unit 
entered failed state.
  Oct 22 12:50:07 michael-desktop-ubuntu systemd[1]: lxc-net.service: Failed 
with result 'exit-code'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508744/+subscriptions

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

[Touch-packages] [Bug 1512826] Re: when i delete .trash_1000 folder frm usb nautilus freeses

[dlalonde]

Oh yeah that did fix it. The only problem remaining now is that when the
folder is used as the Desktop, the files won't go to the trash bin. But
that's no big deal as such.

Thanks!

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

Title:
  when i delete .trash_1000 folder frm usb nautilus freeses

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Wily:
  Fix Committed

Bug description:
  when i delete .trash_1000 folder frm usb nautilus freeses on ubuntu
  15.10. please help

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

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

[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

[Steve Brorens]

I'm sure that it's possible to "tag" this as also applying to Precise
(12.04) - but it's not clear to me how to do that. Could someone do so,
or point me to instructions? Thx

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Confirmed

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies "true";'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

  but nothing happens (note the line "Packages that are auto removed: ''
  ":

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  Checking: bc ([""])
  Checking: grub-common ([""])
  Checking: grub-pc ([""])
  Checking: grub-pc-bin ([""])
  Checking: grub2-common ([""])
  Checking: iproute ([""])
  Checking: landscape-common ([""])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS

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

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

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

[HuaiDan]

Same issue on Ubuntu 15.04 on Asus fx550j.
I downloaded a driver form here:
https://www.dropbox.com/s/xbmm9vfg2fby2zn/fw-04ca_2006.hcd
and reloaded the module. I got BT connectivity after a reboot, but lost it the 
next day. I can't seem to bring it back.

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system 00:06: Plug and Play ACPI device, IDs INT3f0d PNP0c02 
(active)
  [0.261059] system 00:07: [io  0x04d0-0x04d1] has been reserved
  [0.261061] system 00:07: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.261089] system 00:08: [io  0x0240-0x0259] has been reserved
  [0.261091] 

[Touch-packages] [Bug 1504065] Re: Cannot play videos when a wired headphone is connected

[Matthew Paul Thomas]

The relevant bit from the regulation, as quoted in the spec, is "Provide
a means to actively inform the user of the increased sound pressure ...
Any means used shall be acknowledged by the user". Tapping a button in a
dialog is acknowledgement by the user. Toggling a settings switch, ahead
of time, would arguably be acknowledgement by the user (I'd want to
check with a lawyer first). But maybe or maybe not noticing that the
volume gauge is a different color is not acknowledgement by the user.

"What's more, it's not the dialog, nor the shell, that decides to pause
the video or not. It's the media player that does, because it's been
unfocused. Do you believe that some dialogs should change focus, some
shouldn't?"

I'd happily answer in detail, but that issue seems to be four steps
removed from fixing this bug. First, focus and layering are not the same
thing. Focus stealing prevention is important, but on phones Unity might
need to layer dialogs in front even when denying them focus, because --
unlike on PCs -- it can't rely on the Launcher to show you that they've
opened. All my examples assume the dialogs will be in front, but not
necessarily focused.

Second, even if being unfocused was a reliable indicator of being in the
background, that would be a highly questionable reason to pause video.
For example, it would be annoying to pause music merely because the
player is in the background -- but currently, 40% of music listening is
done on YouTube, and is therefore video.

Third, regardless of whether being in the background is a good reason to
pause video, individual media-playing apps seem like the wrong place to
make that decision. For example, a phone call should pause video, and
pause music, and mute any other multimedia audio, in every app, when the
call rings. Does that mean every media-playing app should contain code
for pausing on phone calls? Of course not; app developers would usually
not know, not remember, or not bother. It's a job for the media
frameworks, not the apps.

And fourth, even if apps were responsible for pausing video, I don't
think that pausing should have any effect on the volume warning dialog.
I think that's the root problem, and the reason for my spec change
above: as long as the dialog is up, audio pausing shouldn't change the
active output role and therefore shouldn't dismiss the dialog.

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

Title:
  Cannot play videos when a wired headphone is connected

Status in Canonical System Image:
  Confirmed
Status in The Sound Menu:
  New
Status in mediaplayer-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  When having a wired headset connected to the device, video playback
  keeps on being paused as soon as playback is started. Looks like some
  snap-decision notification is shown, but it's too short time to read
  what it actually says because it disappears again when the playback
  stops again.

  : "So that both buttons do what
  you expect and the dialog does not disappear unexpectedly, any role
  change should be postponed as long as the dialog is up."

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

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

[Touch-packages] [Bug 1523274] [NEW] nvidia-settings: Couldn't connect to accessibility bus

[Tobias Burkard]

Public bug reported:

When trying to restore .nvidia-settings-rc by executing:

$ nvidia-settings --load-config-only --config /path/to/config

the output is:

** (nvidia-settings:6149): WARNING **: Couldn't connect to accessibility
bus: Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection
refused

the settings are not being restored. It doesn't matter if the command is
executed as root or not.

I also spotted such messages in other places, for example when executing
"ubuntu-bug" which lead me here:

** (apport-gtk:6236): WARNING **: Couldn't connect to accessibility bus:
Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection refused

I am running Xubuntu 15.10 which is an upgraded installation from 15.04
which again is an upgraded installation from 14.10. I hope that's not
the root of my problem.

Thanks in advance for any help!

Greetings from Germany,

Tobias Burkard

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: dbus 1.10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Dec  6 20:20:16 2015
InstallationDate: Installed on 2015-03-09 (271 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: dbus
UpgradeStatus: Upgraded to wily on 2015-11-05 (30 days ago)

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


** Tags: amd64 apport-bug wily

** Description changed:

  When trying to restore .nvidia-settings-rc by executing:
  
- $ nvidia-settings --load-config-only --config /paht/to/config
+ $ nvidia-settings --load-config-only --config /path/to/config
  
  the output is:
  
  ** (nvidia-settings:6149): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection
  refused
  
  the settings are not being restored. It doesn't matter if the command is
  executed as root or not.
  
  I also spotted such messages in other places, for example when executing
  "ubuntu-bug" which lead me here:
  
  ** (apport-gtk:6236): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection refused
  
  I am running Xubuntu 15.10 which is an upgraded installation from 15.04.
  
  Thanks in advance for any help!
  
  Greetings from Germany,
  
  Tobias Burkard
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Dec  6 20:20:16 2015
  InstallationDate: Installed on 2015-03-09 (271 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to wily on 2015-11-05 (30 days ago)

** Description changed:

  When trying to restore .nvidia-settings-rc by executing:
  
  $ nvidia-settings --load-config-only --config /path/to/config
  
  the output is:
  
  ** (nvidia-settings:6149): WARNING **: Couldn't connect to accessibility
  bus: Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection
  refused
  
  the settings are not being restored. It doesn't matter if the command is
  executed as root or not.
  
  I also spotted such messages in other places, for example when executing
  "ubuntu-bug" which lead me here:
  
  ** (apport-gtk:6236): WARNING **: Couldn't connect to accessibility bus:
  Failed to connect to socket /tmp/dbus-J3LbSsVkdy: Connection refused
  
- I am running Xubuntu 15.10 which is an upgraded installation from 15.04.
+ I am running Xubuntu 15.10 which is an upgraded installation from 15.04
+ which again is an upgraded installation from 14.10. I hope that's not
+ the root of my problem.
  
  Thanks in advance for any help!
  
  Greetings from Germany,
  
  Tobias Burkard
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dbus 1.10.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Dec  6 20:20:16 2015
  InstallationDate: Installed on 2015-03-09 (271 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to wily on 2015-11-05 (30 days ago)

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

Title:
  nvidia-settings: Couldn't connect to accessibility bus

Status in dbus package in Ubuntu:
  New

Bug description:
  When trying to restore .nvidia-settings-rc by executing:

  $ nvidia-settings --load-config-only --config /path/to/config

  the 

[Touch-packages] [Bug 1523280] [NEW] ModemManager dies (core dump) on free() call

[Hrvoje]

Public bug reported:


Hi.

With latest update, something changed, and now ModemManager is dying
with SIGSEGV in free() call. Since it is configured as "respawn" in
upstart scripts, it's clogging syslog, and adding additional load on cpu
- it's restarting quite fast.

What is expected:

That modem manager is running.

What happened:

The modemmanager process is fast re-spawning and dying every time,
clogging syslog and adding to cpu load.


Package info:

Version is 1.0.0-2ubuntu1.1, running on latest 14.04.01
(3.13.0-71-generic, #114), 64bit arch.


Additional info:

I'm experiencing this on at least two machines, with similar hardware
(same 3G modem), different other stuff. This did not happen before last
update - i think!


Here is the trace (full size attached):

*** Error in `ModemManager': free(): invalid pointer: 0x011ba2a0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7338f)[0x7f958a98f38f]
/lib/x86_64-linux-gnu/libc.so.6(+0x81fb6)[0x7f958a99dfb6]
/usr/lib/x86_64-linux-gnu/ModemManager/libmm-plugin-dell.so(+0x578a)[0x7f9585b6978a]
ModemManager[0x4901fb]
ModemManager[0x48db73]
ModemManager[0x48f76b]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x135)[0x7f958af47ce5]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49048)[0x7f958af48048]
/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x6a)[0x7f958af4830a]
ModemManager(main+0xf6)[0x428fa6]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f958a93dec5]
ModemManager[0x429102]
=== Memory map: 
0040-004df000 r-xp  fc:01 421732 
/usr/sbin/ModemManager
006de000-006e r--p 000de000 fc:01 421732 
/usr/sbin/ModemManager
006e-006e3000 rw-p 000e fc:01 421732 
/usr/sbin/ModemManager
006e3000-006e4000 rw-p  00:00 0 
01189000-0121d000 rw-p  00:00 0  [heap]
7f9583cdb000-7f9583cf1000 r-xp  fc:01 1311237
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9583cf1000-7f9583ef ---p 00016000 fc:01 1311237
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f9583ef-7f9583ef1000 rw-p 00015000 fc:01 1311237
/lib/x86_64-linux-gnu/libgcc_s.so.1

This is how kernel initializes card (tty USB ports):

[   15.031607] usbcore: registered new interface driver usbserial
[   15.031661] usbcore: registered new interface driver usbserial_generic
[   15.031711] usbserial: USB Serial support registered for generic
[   15.038822] usbcore: registered new interface driver option
[   15.038910] usbserial: USB Serial support registered for GSM modem (1-port)
[   15.039071] option 4-2:1.0: GSM modem (1-port) converter detected
[   15.039516] usb 4-2: GSM modem (1-port) converter now attached to ttyUSB0
[   15.039564] option 4-2:1.1: GSM modem (1-port) converter detected
[   15.039973] usb 4-2: GSM modem (1-port) converter now attached to ttyUSB1

Listing of USB devices:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 003: ID 0483:2016 STMicroelectronics Fingerprint Reader
Bus 007 Device 004: ID 0b97:7772 O2 Micro, Inc. OZ776 CCID Smartcard Reader
Bus 007 Device 002: ID 0b97:7761 O2 Micro, Inc. Oz776 1.1 Hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 413c:8137 Dell Computer Corp. Wireless 5520 Voda L 
Mobile Broadband (3G HSDPA) Minicard Status Port
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

WORKAROUND!

ModemManager works by disabling free check. THIS IS DANGEROUS, since it
can have other. To do this, start ModemManager with "MALLOC_CHECK_"
environment set to 0.

Regards,

H.

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

** Attachment added: "ModemManager debug output with stack trace"
   https://bugs.launchpad.net/bugs/1523280/+attachment/4530555/+files/core.txt

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

Title:
  ModemManager dies (core dump) on free() call

Status in modemmanager package in Ubuntu:
  New

Bug description:
  
  Hi.

  With latest update, something changed, and now ModemManager is dying
  with SIGSEGV in free() call. Since it is configured as "respawn" in
  upstart scripts, it's clogging syslog, and adding additional load on
  cpu - it's restarting quite fast.

  What is expected:

  That modem manager is running.

  What happened:

  The modemmanager process is fast re-spawning and dying every time,
  clogging 

[Touch-packages] [Bug 1313370] Re: Support for installing Digital Certificates

[Olivier Tilloy]

Probably not, see my comment on bug #1523261.

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

Title:
  Support for installing Digital Certificates

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  I am trying to enter a page, and to me it is necessary to have in the
  digital certificate installed browser. Where is the option to install
  the digital certificate. Without that the browser is unusable.

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

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

[Touch-packages] [Bug 1294699] Re: Xubuntu desktop crashes in call to cairo after setting fixed-width bitmap (pcf) GTK font

[jpka]

Other affected apps:
Latest LibreOffice (Ubuntu 14.04.3 LTS):
soffice.bin: /build/buildd/cairo-1.13.0~20140204/src/cairo-scaled-font.c:459: 
_cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
 (crash on Writer's save dialogue, works well before save)
Latest Gimp (Ubuntu 14.04.3 LTS):
gimp: /build/buildd/cairo-1.13.0~20140204/src/cairo-scaled-font.c:459: 
_cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
gimp: terminated: Aborted
 (but very rarely it starts. Probability increases when dockable windows are 
closed. But even if it start, walking through menus crash it, at different menu 
each time, i.e. no particular word or symbol in menu is a problem. Before 
crash, i am able to draw and save).

I can't use fonts other than bitmap fonts. Please also see Bug #1476736. If 
these bugs are not going to be fixed, please give me starting point how i can 
debug and fix it myself. I have enough resources for that.
I can't work without Gimp and especially LO. Thanks.

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

Title:
  Xubuntu desktop crashes in call to cairo after setting fixed-width
  bitmap (pcf) GTK font

Status in xfdesktop:
  New
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in terminator package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Arch Linux:
  New

Bug description:
  Reproduce: In Xubuntu (xfce), go to Settings Manager -> Appearance ->
  Fonts -> Default Font, select an installed fixed-width, bitmapped .pcf
  font (e.g. ProFont).  Desktop crashes; the new font does appear in the
  apport dialogs, but attempting to log back into the session, xfdesktop
  crashes with an assert in cairo, with gtk up the stacktrace:

  cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion
  `!scaled_font->cache_frozen' failed.

  To undo the change and be able to log in, I had to remove the GTK Font
  property in xfce4's xsettings.xml config file.  It would be a fair
  limitation if certain bitmap fonts failed over gracefully or were
  disallowed for selection, however, allowing an the interface to select
  the font without error, and then crashing and hanging the session on
  every login, leaving the config in a bad state should be fixed.

  uname:
  3.11.0-18-generic #32-Ubuntu SMP Tue Feb 18 21:11:14 UTC 2014 x86_64 x86_64 
x86_64 GNU/Linux

  lsb_release:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 13.10
  Release:  13.10
  Codename: saucy

  Similar report seen in archlinux/xfce4:
  https://bbs.archlinux.org/viewtopic.php?id=169433

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: libgtk2.0-0 2.24.20-1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Uname: Linux 3.11.0-18-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Wed Mar 19 10:41:54 2014
  InstallationDate: Installed on 2013-11-01 (138 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1515446] Re: NFS shares in FSTAB no longer mount at boot

[lnxusr]

Workaround seems good.  Adding 'x-systemd.automount' to fstab mounts NFS
shares during boot.

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in nfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 15.10, nfs shares no longer mount on boot.
  I'm using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
 Loaded: loaded (/etc/fstab)
 Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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

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

[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

[Honsan]

I'm newbie on linux and I had this problem too. I think I solved it that
way:


** Attachment added: "snapshot of isc-dhcp-server.service"
   
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+attachment/4530564/+files/VirtualBox_Ubuntu%20Server15.04%20_06_12_2015_20_57_31.png

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

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

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

[Touch-packages] [Bug 1515446] Re: NFS shares in FSTAB no longer mount at boot

[sanford rockowitz]

The x-systemd.automout option works for me as well running 15.10.

Interestingly, it was commented out in my fstab.   I believe I tried
that option on 15.04, and it didn't work then.

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

Title:
  NFS shares in FSTAB no longer mount at boot

Status in nfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After a fresh install of 15.10, nfs shares no longer mount on boot.
  I'm using the same line to mount as I did in 14.04 prior:

  :/share  /mnt/share  ntfs4  _netdev, auto 0 0

  This line worked just fine in 14.04, and 14.10 on my laptop, to mount
  the shares at boot.

  Manual mounting after boot works fine.  Systemctl shows a name
  resolution failure (see below)

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10

  lsb_release -rd
  Description:Ubuntu 15.10
  Release:15.10
  bjwest@razorback:~$ apt-cache policy nfs-common
  nfs-common:
Installed: 1:1.2.8-9ubuntu10
Candidate: 1:1.2.8-9ubuntu10
Version table:

   *** 1:1.2.8-9ubuntu10 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
  100 /var/lib/dpkg/status

  systemctl status mnt-share.mount
  ● mnt-share.mount - /mnt/share
 Loaded: loaded (/etc/fstab)
 Active: failed (Result: exit-code) since Wed 2015-11-11 18:58:13 CST; 2min 
15s ago
  Where: /mnt/share
   What: hog:/share
   Docs: man:fstab(5)
 man:systemd-fstab-generator(8)
Process: 731 ExecMount=/bin/mount hog:/share /mnt/share -t nfs4 -o _netdev 
(code=exited, status=32)

  Nov 11 18:58:13 razorback systemd[1]: Mounting /mnt/share...
  Nov 11 18:58:13 razorback mount[731]: mount.nfs4: Failed to resolve server 
hog: Temporary failure in name resolution
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Mount process exited, 
code=exited status=32
  Nov 11 18:58:13 razorback systemd[1]: Failed to mount /mnt/share.
  Nov 11 18:58:13 razorback systemd[1]: mnt-share.mount: Unit entered failed 
state.

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

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

[Touch-packages] [Bug 1472755] Re: corrupted double-linked list probably cause by telegram scope

[Michi Henning]

OK, I think I finally found it. There are some dummy loggers in the run
time that I added because some of the unit tests run without a fully
initialized run time (which provides access to the logger), but still
need a working logger. For these tests, a global dummy instance is used.
It's the clean-up of the dummy instance that causes the problem because,
depending on global destructor ordering, the instance may have been
destroyed at the time the atexit handler tries to finalize it.

Not sure what the best fix is yet. Working on it...

** Changed in: unity-scopes-api (Ubuntu)
   Status: Invalid => In Progress

** Changed in: libqtelegram (Ubuntu)
   Status: Triaged => Invalid

** Changed in: canonical-devices-system-image
 Assignee: Yuan-Chen Cheng (ycheng-twn) => Michi Henning (michihenning)

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

Title:
  corrupted double-linked list probably cause by telegram scope

Status in Canonical System Image:
  Triaged
Status in libqtelegram package in Ubuntu:
  Invalid
Status in unity-scope-mediascanner package in Ubuntu:
  Invalid
Status in unity-scopes-api package in Ubuntu:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity-scope-mediascanner.  This problem was most recently
  seen with version 1.7.16, the problem page at
  https://errors.ubuntu.com/problem/21d9e7ddf91a26b21abfb2758315ad41fcfd3fa9
  contains more details.

  "/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in
  `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': corrupted
  double-linked list: ADDR ***"

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

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

[Touch-packages] [Bug 1522726] Re: [regression] Linking mir_unit_tests.bin now takes a very long time (minutes) even on a fast machine (previously just seconds)

[Daniel van Vugt]

Tried, but can't test that. Putting the old binutils on the machine just
makes the build fail:

Linking CXX executable ../../bin/mir_unit_tests.bin
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/crti.o: 
unrecognised relocation (0x2a) in section `.init'
/usr/bin/ld: final link failed: Bad value

or starting again from scratch gives the same error and reports it as:

CMake Error at /usr/share/cmake-3.2/Modules/CMakeTestCCompiler.cmake:61 
(message):
  The C compiler "/usr/bin/cc" is not able to compile a simple test program.

Would need to downgrade the compilers on the machine too :P

That said, I think there's also a chance that some 3rd party library
we're pulling in (and have always pulled in) might cause this on xenial.

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

Title:
  [regression] Linking mir_unit_tests.bin now takes a very long time
  (minutes) even on a fast machine (previously just seconds)

Status in Mir:
  Incomplete
Status in binutils package in Ubuntu:
  New

Bug description:
  [regression] Linking mir_unit_tests.bin now takes a very long time (minutes) 
even on a fast machine (previously just seconds)
  --- 
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  Dependencies:
   gcc-5-base 5.2.1-27ubuntu1
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-27ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-03 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202)
  Package: binutils 2.25.90.20151125-2ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

[Simon Fels]

@Uranicus: Awesome writeup! Thanks a lot. However the most important
thing is missing: A copy of /var/log/syslog which would be the primary
source of information for us to debug this. The others are only side
note information.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Incomplete
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

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

[Touch-packages] [Bug 1493574] Re: [vegeta] Phone app makes screen stay black during call (so you can't hang up)

[Matthew Exon]

I submitted Bug #1523308 which is probably a duplicate of this.
Happened earlier today on my MX4 (one SIM card), first time I've noticed
it.  There's a syslog attached to that bug.  I don't seem to have a
powerd log though.

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

Title:
  [vegeta] Phone app makes screen stay black during call (so you can't
  hang up)

Status in Canonical System Image:
  Incomplete
Status in powerd package in Ubuntu:
  Confirmed

Bug description:
  A similar, if not the same bug, has been reported to be fixed for
  OTA6. This bug report explains that it's no necessary to wait for a
  minute or so on the phone call, but the screen turns black
  immediately, and doesn't turn back on again to allow hanging up via a
  screen control.

  Potential duplicate: https://bugs.launchpad.net/canonical-devices-
  system-image/+bug/1483127

  Device: Aquaris E5 HD Ubuntu Edition
  OS version: 15.04 (r5)

  A) Incoming phone call:
     - Accept the incoming call by sliding the grey middle button to the 
green button
     - Watch the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (continued from above, screen stays black after taking it away from 
your ear)
     - Press the screen lock/unlock button (= button above volume control)
     - Screen with phone app shows for about half a second, then turns 
black again
     - Press the screen lock/unlock button again, and try to press the red 
hangup button quickly
     - Repeat the previous step until hanging up succeeds

  B) Outbound phone call:
     - Open the phone app
     - Slide up Recent calls list from bottom edge, select a phone number
     - Press green dial button to initiate the call
     - Watch the phone dialling and the screen turning black
     - Bring the phone to your ear, speak (as in a normal phone call)
     - Take the phone away from your ear, note that the screen stays black

     How to hang up anyway: (workaround)
     - (same procedure as in A. above)
     - Difference in behavior:
   * In some calls after pressing the lock/unlock button for the first 
time the screen stays alight (doesn't turn black again after half a second).

  
  Jean-Baptiste Lallement confirms on the ubuntu-phone mailing list:
  In both cases, covering/uncovering the proximity sensor should turn the 
screen on, if the screen has not been turned off with the power button. (This 
is not happening.)

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

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

[Touch-packages] [Bug 1258778] Re: IBus input candidates not shown in GNOME Fallback session

[Mingye Wang]

Added gnome-flashback since this may also be aflashback problem if ibus
works elsewhere, and salty-horse also reported the non-working status on
14.04 LTS.

An upstream flashback bug has been fixed at
https://bugzilla.gnome.org/show_bug.cgi?id=759083, but they said it will
be a separate problem for Ubuntu.

** Also affects: gnome-flashback (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  IBus input candidates not shown in GNOME Fallback session

Status in gnome-flashback package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  I was able to add "Chinese (Pinyin)" as input method in Ubuntu 13.10's
  new "Text Entry Settings". Switching between "English (US)" and
  Chinese entry works for me, generally. When I'm using the "Ubuntu
  (Default)" (Unity) session, input candidates are also properly shown
  (a little floating window that shows candidate Chinese characters
  while typing).

  However, when I use the "GNOME Fallback" or "GNOME with Xmonad"
  session, as I normally do, the candidates do not show up at all. This
  makes Pinyin input useless.

  OS and package versions:

  ke@apis:~$ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10
  ke@apis:~$ apt-cache policy ibus
  ibus:
Installed: 1.5.3-6ubuntu2
Candidate: 1.5.3-6ubuntu2
Version table:
   *** 1.5.3-6ubuntu2 0
  500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

[Shane Synan]

@Steve Brorens:  It's actually the little "Tags" section under the bug
description and right before the comments that needs edited.  Remove
'verification-needed' and add 'verification-done', and that should be
it!

If you can, you may want to change "Confirmed" back to "Fix Committed" -
that's for confirming the bug exists, not for confirming that a proposed
package fixed it.  "Fix Committed" means the fix is developed, but
hasn't yet passed testing.

Unfortunately, I'm not sure about how to mark this as also affecting
Precise.

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Confirmed

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies "true";'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

  but nothing happens (note the line "Packages that are auto removed: ''
  ":

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  Checking: bc ([""])
  Checking: grub-common ([""])
  Checking: grub-pc ([""])
  Checking: grub-pc-bin ([""])
  Checking: grub2-common ([""])
  Checking: iproute ([""])
  Checking: landscape-common ([""])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS

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

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

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

[Launchpad Bug Tracker]

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

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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Expired

Bug description:
  running browser against local server and data base.  That is running
  browser, apache and sql on the same machine.

  Did do an update a few days back and another after the freeze just in
  case already found and fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep 28 05:00:33 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Within the last few days
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8411]
  InstallationDate: Installed on 2014-09-03 (389 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: ASUS All Series
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=614540d3-24cf-4ba7-9ff5-20b5269b8842 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z97-AR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  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.:bvr0702:bd04/23/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Sep 28 04:55:06 2015
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1503737] Re: [80E3, Conexant CX20751/2, Mic, Internal] No sound at all

[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/1503737

Title:
  [80E3, Conexant CX20751/2, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  When Skype or viber starts, the internal mic stops to work and
  Pavucontrol input seection shows no response to any sound...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Oct  7 17:22:13 2015
  InstallationDate: Installed on 2015-05-16 (144 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic successful
  Symptom_Type: No sound at all
  Title: [80E3, Conexant CX20751/2, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A2CN27WW(V1.09)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5B2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-45
  dmi.modalias: 
dmi:bvnLENOVO:bvrA2CN27WW(V1.09):bd12/12/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-45:
  dmi.product.name: 80E3
  dmi.product.version: Lenovo G50-45
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1503435] Re: [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card

[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/1503435

Title:
  [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  audio isnt working and the sound card isnt showing up in the audio
  settings. i tried going into the "alsamixer" to see if i can choose
  the proper driver but to no avail. even the sound control panel doesnt
  show the right driver, just a non working dummy driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-lowlatency 3.19.8-ckt6
  Uname: Linux 3.19.0-30-lowlatency i686
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', 
'/dev/snd/pcmC0D6p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Tue Oct  6 14:45:16 2015
  InstallationDate: Installed on 2015-10-03 (3 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.3 LTS "Trusty Tahr" - Beta i386 
(20150805)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel
  Symptom_Jack: Line Out, N/A
  Title: [D900T, Realtek ALC880, Line Out, N/A] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2005
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: D900T
  dmi.board.vendor: CLEVO
  dmi.board.version: Revision A
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/01/2005:svnCLEVO:pnD900T:pvrRevisionA:rvnCLEVO:rnD900T:rvrRevisionA:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: D900T
  dmi.product.version: Revision A
  dmi.sys.vendor: CLEVO

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

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

[Touch-packages] [Bug 1503787] Re: can only log in with another admin account. my old admin account doesnt show any desktop symbols at all. now the second admin account has starting problems too is no

[Launchpad Bug Tracker]

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

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

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

Title:
  can only log in with another admin account. my old admin account
  doesnt show any desktop symbols at all.  now the second admin account
  has starting problems too is not completing start up.. stays with the
  start screen and doesnt continue..system seems up to date with the
  ubuntu provided updates.

Status in lightdm package in Ubuntu:
  Expired

Bug description:
  in may the first prob occured with my one and only admin account. no desktop 
symbol showed up anymore so that you can only logg in but not shut down or 
anything else without ending the session per terminal command and write log 
off.. over the guest account we created a second admin account to safe all my 
data and continued. but actually didnt have the knowledge to fix the first 
issue permanently. now the second admin account is not even starting.. and the 
system seems extremly slowed down.
  i would really very much appreciate any help of you.
  thanks a lot beforehand for any reply or help provided.

  the problem is presumably located in the following package LightDM.



  yours sincereyl 
  swantje staaden.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubuntu-docs 14.04.5
  ProcVersionSignature: Ubuntu 3.13.0-66.107-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct  7 19:19:04 2015
  InstallationDate: Installed on 2014-01-11 (633 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-docs
  UpgradeStatus: Upgraded to trusty on 2014-07-20 (444 days ago)

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

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

[Touch-packages] [Bug 1503043] Re: package qtdeclarative5-xmllistmodel-plugin:amd64 5.2.1-3ubuntu15.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it b

[Launchpad Bug Tracker]

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

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

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

Title:
  package qtdeclarative5-xmllistmodel-plugin:amd64 5.2.1-3ubuntu15.1
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in apt package in Ubuntu:
  Expired

Bug description:
  every time there is software update there is an error

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: qtdeclarative5-xmllistmodel-plugin:amd64 5.2.1-3ubuntu15.1
  ProcVersionSignature: Ubuntu 3.16.0-50.66~14.04.1-generic 3.16.7-ckt16
  Uname: Linux 3.16.0-50-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Tue Oct  6 02:24:32 2015
  DuplicateSignature: 
package:qtdeclarative5-xmllistmodel-plugin:amd64:5.2.1-3ubuntu15.1:package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-08-06 (59 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: qtdeclarative-opensource-src
  Title: package qtdeclarative5-xmllistmodel-plugin:amd64 5.2.1-3ubuntu15.1 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1523261] Re: Unable to log in to owncloud hosted on private NAS

[Laryllan]

I attached the log you requested.
Please note that the screenshot is taken from the browser-app in 15.10 as it 
shows the same behaviour as the phone app.

Thanks for your support.

** Attachment added: "attachment from OTA-8 arale"
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1523261/+attachment/4530759/+files/application-legacy-webbrowser-app-.log

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

Title:
  Unable to log in to owncloud hosted on private NAS

Status in webbrowser-app package in Ubuntu:
  Incomplete

Bug description:
  Hi there,

  I'm trying to access my owncloud hosted on my private NAS.

  WHAT I EXPECT:
  I can accept the certificate and access my OwnCloud.

  WHAT HAPPENS:
  I cannot access my OwnCloud.
  It shows the login prompt, but doesn't allow me to log in.
  As if the login button doesn't work.

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

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