[Touch-packages] [Bug 1040987] Re: Invalid unfocused background color on GNOME Character Map

[Adolfo Jayme]

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

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

Title:
  Invalid unfocused background color on GNOME Character Map

Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  On application GNOME Character Map (gnome-character-map), when you
  select a character from the table and then unfocus the character table
  widget, the selected item now has a background color like if the item
  is no longer selected, resulting on confusion.

  The expected result is that when user unfocus the character table
  widget, the orange color for the selected item background remains as
  before and when application window lose focus, use the backdrop color
  for the background.

  A screenshot is attached showing the problem. Note that, in this case,
  I have selected the "U+0041 LATIN CAPITAL LETTER A" but I have the
  focus on the widget to configure font size.

  Thanks!

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

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

[Touch-packages] [Bug 1036360] Re: Normal titlebar alignment is off

[Adolfo Jayme]

Since 14.04 this is fixed on default installations because Unity has
stopped using Metacity/Compiz decorations. This bug still exists for
GNOME Flashback though.

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

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

Title:
  Normal titlebar alignment is off

Status in Themes for Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  When using a non-maximized window, the alignment of the text is to the
  top of the window control buttons, leaving a gap in spacing between
  the bottom of the button and the bottom of the text. However, on a
  maximized window, the alignment is such that the text is more or less
  centered along the horizontal axis of the window control buttons.

  Will include two shots to demonstrate this issue.

  This is on an up-to-date Precise install.

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

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

[Touch-packages] [Bug 994252] Re: Remove shadows

[Adolfo Jayme]

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

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

Title:
  Remove shadows

Status in Ayatana Design:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Shadows can be done via CSS, there's no reason to have them in the
  icons theirselves. For example look at the user accounts panel and how
  the shadows look on big icons

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

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

[Touch-packages] [Bug 994153] Re: No visual distinction between floating windows and other windows

[Adolfo Jayme]

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

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

Title:
  No visual distinction between floating windows and other windows

Status in Ayatana Design:
  New
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In light-themes, there is no visual way to tell that a floating window
  (_NET_WM_WINDOW_TYPE_UTILITY) will behave differently from a normal
  window.

  On Windows and Mac OS X, the standard way to show that a window is a
  floating window is to give it a thinner title bar -- including smaller
  window controls and a smaller title font.

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

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

[Touch-packages] [Bug 1357069] Re: Missing vertical separation

[Adolfo Jayme]

** Project changed: ubuntu-themes => ubuntu-themes (Ubuntu)

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

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

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

Title:
  Missing vertical separation

Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  In tree view, there is no vertical separation between columns in GTK 3
  (see screenshot, on the left is the same application with gtk2 and on
  the right with GTK3). Is that a bug or a design decision? There are
  vertical separation in the headers of those columns, which looks a bit
  weird.

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

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

[Touch-packages] [Bug 1046129] Re: Use New Radio/Check Assets for Gtk-2.0 Theme Consistency

[Adolfo Jayme]

** Changed in: ubuntu-themes (Ubuntu)
   Status: Confirmed => Triaged

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

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

Title:
  Use New Radio/Check Assets for Gtk-2.0 Theme Consistency

Status in Themes for Ubuntu:
  Fix Committed
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Add new radio and check assets for use with gtk-2.0 Ambiance/Radiance
  for theme consistency.

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

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

[Touch-packages] [Bug 1357069] [NEW] Missing vertical separation

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In tree view, there is no vertical separation between columns in GTK 3
(see screenshot, on the left is the same application with gtk2 and on
the right with GTK3). Is that a bug or a design decision? There are
vertical separation in the headers of those columns, which looks a bit
weird.

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

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

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

[Touch-packages] [Bug 1370135] Re: Add alternating background rows

[Adolfo Jayme]

** Project changed: ubuntu-themes => ubuntu-themes (Ubuntu)

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

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

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New => Triaged

** Changed in: hundredpapercuts
   Importance: Undecided => Wishlist

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

Title:
  Add alternating background rows

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  This would make it easier to find the corresponding cell in a column
  (e.g. rating) to the cell in another column (e.g. artist) you are
  currently looking at, if they are far apart.

  There are other people wanting this:
  http://askubuntu.com/questions/285559/how-to-reenable-alternating-
  grey-lines-in-nautilus-files-3-6-list-view

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

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

[Touch-packages] [Bug 1362305] Re: Listitems without actions shouldn't animate on click events

[Launchpad Bug Tracker]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/78-action-property

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

Title:
  Listitems without actions shouldn't animate on click events

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Using current utopic, doing a tap/click on a ListItem.Standard with
  only a text define (e.g no action) leads to have visual feedback about
  the click, whic seems to lead to confusion (see e.g bug #1360364 "rows
  can be clicked, give feedback, do nothing")

  Would it make sense to have the animation only enable if the is an
  action/control for the widget?

  (Not to be confused with bug 1289329, where an item normally would
  respond to a tap, but has been held down too long.)

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

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

[Touch-packages] [Bug 1369935] Re: New ListItem needs action property

[Launchpad Bug Tracker]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/78-action-property

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

Title:
  New ListItem needs action property

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ListItem should have an action property that sets the text, onClicked
  and icon.

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

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

[Touch-packages] [Bug 1370135] Re: Add alternating background rows

[Launchpad Bug Tracker]

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

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

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

Title:
  Add alternating background rows

Status in One Hundred Papercuts:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  This would make it easier to find the corresponding cell in a column
  (e.g. rating) to the cell in another column (e.g. artist) you are
  currently looking at, if they are far apart.

  There are other people wanting this:
  http://askubuntu.com/questions/285559/how-to-reenable-alternating-
  grey-lines-in-nautilus-files-3-6-list-view

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

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

[Touch-packages] [Bug 1350759] Re: dhclient logs DHCPDISCOVER request (stdout and syslog) but doesn't send anything

[Stefan Felkel]

We found the root of the problem. 
In our case the problem was located in the network driver e1000e.
We sniffed the network *on* the PC and *before* the PC and found out that DHCP 
offers were sent, indeed, but not forwarded through the driver (for what 
reason, ever).

The  upgrade of e1000e to 3.1.0.2 solved our problem.

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

Title:
  dhclient logs DHCPDISCOVER request (stdout and syslog) but doesn't
  send anything

Status in isc-dhcp package in Ubuntu:
  Fix Released

Bug description:
  I'm experiencing the problem that `dhclient -4 -w -v` logs messages in
  the form `DHCPDISCOVER on  to 255.255.255.255 port 67
  interval 13 (xid=)`, e.g. `DHCPDISCOVER on wlan0 to
  255.255.255.255 port 67 interval 13 (xid=0x6d59d111)` both to console
  (stdout or stderr) and syslog, but wireshark shows that there're no
  requests sent over the network!! It works as expected, i.e. DHCP
  requests are actually sent over the network, if (as far as I
  experienced iff) I invoke `dhclient -r` before.

  experienced with isc-dhcp-client 4.2.4-7ubuntu12 on Ubuntu 14.04

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

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

[Touch-packages] [Bug 1370135] [NEW] Add alternating background rows

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This would make it easier to find the corresponding cell in a column
(e.g. rating) to the cell in another column (e.g. artist) you are
currently looking at, if they are far apart.

There are other people wanting this:
http://askubuntu.com/questions/285559/how-to-reenable-alternating-grey-
lines-in-nautilus-files-3-6-list-view

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

-- 
Add alternating background rows
https://bugs.launchpad.net/bugs/1370135
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-themes in Ubuntu.

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

[Touch-packages] [Bug 1400467] Re: Problemes found by Xdiagnose

[Christopher M. Penalver]

Mendels, thank you for reporting this and helping make Ubuntu better. If
your system was working before you made changes to /etc/sudoers, then
the root cause is your changes, versus a software bug in Ubuntu.

Please work through this issue via more appropriate support channels ->
http://www.ubuntu.com/support . A Launchpad bug report is the wrong
venue for this.

Thank you for your understanding.

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

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

Title:
  Problemes found by Xdiagnose

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I have problemes for acces since I did changes in etc/sudoers file
  Not the first bug report on that but always happening during an other usage 
(other aplications)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  Date: Mon Dec  8 20:22:17 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:18fe]
  InstallationDate: Installed on 2014-10-15 (54 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP Pavilion Sleekbook 15
  ProcEnviron:
   LANGUAGE=fr_BE:fr
   PATH=(custom, no user)
   LANG=fr_BE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=2cf50ca9-363a-479d-ba5b-4dc3eec8874c ro vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe nomdmonddf nomdmonisw
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/08/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18FE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 82.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd02/08/2013:svnHewlett-Packard:pnHPPavilionSleekbook15:pvr088A1135590320100:rvnHewlett-Packard:rn18FE:rvr82.27:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Sleekbook 15
  dmi.product.version: 088A1135590320100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 15:20:31 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5547 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 1400244] Re: Qtbase 5.4.0 fails to build on powerpc

[Dmitry Shachnev]

https://codereview.qt-project.org/101769

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

Title:
  Qtbase 5.4.0 fails to build on powerpc

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

Bug description:
  Build log at https://launchpadlibrarian.net/192081247/buildlog_ubuntu-
  vivid-powerpc.qtbase-opensource-src_5.4.0~rc-
  0ubuntu1~vivid1~test3_FAILEDTOBUILD.txt.gz

  
  g++ -c -include .pch/Qt5Network -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -D_FORTIFY_SOURCE=2 -O2 -fvisibility=hidden 
-fvisibility-inlines-hidden -std=c++0x -fno-exceptions -Wall -W -D_REENTRANT 
-fPIC -DQT_NO_USING_NAMESPACE -DQT_BUILD_NETWORK_LIB -DQT_BUILDING_QT 
-DQT_NO_CAST_TO_ASCII -DQT_ASCII_CAST_WARNINGS -DQT_MOC_COMPAT 
-DQT_USE_QSTRINGBUILDER -DQT_DEPRECATED_WARNINGS 
-DQT_DISABLE_DEPRECATED_BEFORE=0x05 -DQT_NO_EXCEPTIONS 
-D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_CORE_LIB 
-I../../mkspecs/linux-g++ -I. -I../../include -I../../include/QtNetwork 
-I../../include/QtNetwork/5.4.0 -I../../include/QtNetwork/5.4.0/QtNetwork 
-Ikernel -I../../include/QtCore/5.4.0 -I../../include/QtCore/5.4.0/QtCore 
-I../../include/QtCore -I.moc -o .obj/qabstractsocketengine.o 
socket/qabstractsocketengine.cpp
  image/qimage_conversions.cpp:2257:9: error: expected '}' before numeric 
constant
   0, 0, 0, 0
   ^
  image/qimage_conversions.cpp:2257:9: error: expected '}' before numeric 
constant
  image/qimage_conversions.cpp:2257:9: error: expected ',' or ';' before 
numeric constant
  image/qimage_conversions.cpp:2258:5: error: expected declaration before '}' 
token
   }, // Format_RGBA
   ^
  

  More information about Qt testing at
  https://wiki.ubuntu.com/Touch/QtTesting

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

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

[Touch-packages] [Bug 1400186] Re: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out)

[Kieran Ramos]

I've run hda-jack-retask and got the Internal Speakers, Headphone, and
Microphone working. I cannot teste the port replicator as of yet, but
will test it later when I retrieve it from storage.

The headphone jack is not its own output and the laptop auto-switches
internal speakers to headphone upon pluggin them in. The microphone port
does not have plug in detection as far as I can tell. The A/V Out port
on the back of the laptop is always on when set to internal speakers but
it does have its own output which I was able to configure. Since this
A/V Out port is a 4 conductor 3.5mm, I don't know if it is compatible
with a standard 3.5mm stereo output which is all I have to test. As a
result I can only confirm that the left channel is working.

I've attached my new alsa-info after applying the changes from hda-jack-
retask to startup. In what kernel version was that commit you posted
applied to? Before submitting this bug I tested kernel 3.17.6 and still
had the same issue. I can test a newer kernel to be sure the commit
fixes the problem on the VGN-A690.

** Attachment added: "alsa-info.txt.Xe9xiLj3L5"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1400186/+attachment/4276710/+files/alsa-info.txt.Xe9xiLj3L5

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

Title:
  [VGN-A690, Realtek ALC260] No sound at all internal speakers and
  headphone (Green out)

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I have tried using different options in /etc/modprobe.d/alsa-
  base.conf. Without probe_mask=1 it also detects a Conexant modem.

  I just discovered there is sound output from the rear A/V Out port of
  the laptop, but there is popping whether or not audio is playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic i686
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  beat   1823 F pulseaudio
  CurrentDesktop: XFCE
  CurrentDmesg:
   [   42.213440] systemd-logind[805]: Failed to start user service: Unknown 
unit: user@1000.service
   [   42.220873] systemd-logind[805]: New session c1 of user beat.
   [   42.220901] systemd-logind[805]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  Date: Sun Dec  7 20:10:30 2014
  InstallationDate: Installed on 2014-12-06 (1 days ago)
  InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  beat   1823 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [VGN-A690, Realtek ALC260, Green Line Out, Rear] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2005
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0080F2
  dmi.chassis.asset.tag: 8S4Lf716540bab4851f0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0080F2:bd03/14/2005:svnSonyCorporation:pnVGN-A690:pvrC00071GZ:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VGN-A690
  dmi.product.version: C00071GZ
  dmi.sys.vendor: Sony Corporation
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-12-07T18:28:32.827133

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

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

[Touch-packages] [Bug 1397997] Re: vs-thumb gets stalled when trying to get thumbnail from video

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-bad1.0 - 1.4.4-2ubuntu2

---
gst-plugins-bad1.0 (1.4.4-2ubuntu2) vivid; urgency=medium

  * Refreshing adding-mirsink-and-android-media-over-hybris-support.patch:
- androidmedia: Fix stagnation when obtaining thumb (LP: #1397997)
- Don't flush while the dec loop is working (LP: #1364466)
 -- Ricardo Salveti de AraujoMon, 08 Dec 
2014 23:46:12 -0200

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: New => Fix Released

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

Title:
  vs-thumb gets stalled when trying to get thumbnail from video

Status in the base for Ubuntu mobile products:
  New
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Invalid
Status in gst-plugins-bad1.0 package in Ubuntu RTM:
  New

Bug description:
  vs-thumb stalls when trying to get a thumbnail from the attached
  video. To reproduce:

  $ /usr/lib/arm-linux-gnueabihf/thumbnailer/vs-thumb
  /home/phablet/Videos/IMG_4277.3gp img.jpg

  System image:

  current build number: 169
  device name: krillin
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-11-25 16:03:24
  version version: 169
  version ubuntu: 20141124
  version device: 20141119-db417fa
  version custom: 20141119-442-21-160

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

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

[Touch-packages] [Bug 1400580] [NEW] Color Inverse on display. Toggle Negative Image

[Mike O'Donnell]

Public bug reported:

I would like to see a feature that allowed Unity8, to easily inverse the
desktop colors.  To be able to easily turn on and off a negative
(inverse) display of the desktop. For now, it can be done with X
(xcalib). It would be nice to see Unity8 do this natively, instead of
Ubuntu users needing this feature hoping, X-11 support will always be
available.

This is a feature I use, due to impaired eye-sight.

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

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

Title:
   Color Inverse on display. Toggle Negative Image

Status in unity8 package in Ubuntu:
  New

Bug description:
  I would like to see a feature that allowed Unity8, to easily inverse
  the desktop colors.  To be able to easily turn on and off a negative
  (inverse) display of the desktop. For now, it can be done with X
  (xcalib). It would be nice to see Unity8 do this natively, instead of
  Ubuntu users needing this feature hoping, X-11 support will always be
  available.

  This is a feature I use, due to impaired eye-sight.

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

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

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Launchpad Bug Tracker]

This bug was fixed in the package gst-plugins-bad1.0 - 1.4.4-2ubuntu2

---
gst-plugins-bad1.0 (1.4.4-2ubuntu2) vivid; urgency=medium

  * Refreshing adding-mirsink-and-android-media-over-hybris-support.patch:
- androidmedia: Fix stagnation when obtaining thumb (LP: #1397997)
- Don't flush while the dec loop is working (LP: #1364466)
 -- Ricardo Salveti de AraujoMon, 08 Dec 
2014 23:46:12 -0200

** Changed in: gst-plugins-bad1.0 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in the base for Ubuntu mobile products:
  In Progress
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in mediascanner2 package in Ubuntu:
  Invalid
Status in gst-plugins-bad1.0 package in Ubuntu RTM:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  and
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1272028] Re: remount, not honored on bind mounts

[Launchpad Bug Tracker]

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

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

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

Title:
  remount, not honored on bind mounts

Status in apparmor package in Ubuntu:
  Expired
Status in apparmor source package in Precise:
  Expired
Status in apparmor source package in Trusty:
  Expired
Status in apparmor source package in Utopic:
  Expired

Bug description:
  I was trying to run docker in a nested container.  docker wants to
  remount a bind-mounted dir as ro.  Audit log showed this failed.  I
  first tried to add more specific rules, but when those did not work i
  tried just

  remount,

  in the policy.  Still the mount was denied.  Finally when I added
  'mount,', it worked.

  Ideally I would be able to say

remount options=(ro,bind) -> /var/lib/docker/**/,

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

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

[Touch-packages] [Bug 1065390] Re: Please add /usr/bin/parole to the ubuntu-media-players abstraction

[Launchpad Bug Tracker]

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

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

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

Title:
  Please add /usr/bin/parole to the ubuntu-media-players abstraction

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  This would allow Firefox and other applications to open media files
  with parole which is on the Xubuntu default image.

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

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

[Touch-packages] [Bug 571065] Re: asterisk apparmor profile

[Launchpad Bug Tracker]

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

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

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

Title:
  asterisk apparmor profile

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  Binary package hint: apparmor

  Attached is a profile for asterisk with the intention of including it
  in apparmor-profiles.

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

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

[Touch-packages] [Bug 511493] Re: Add Acrobat reader and flash restrictions

[Launchpad Bug Tracker]

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

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

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

Title:
  Add Acrobat reader and flash restrictions

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  Binary package hint: apparmor

  Add a rule file for Acrobat Reader and Flash

  - Acrobat reader is used by about 20 % of Ubuntu users, Flash by 50 %
  - Most targeted attacks use PDF
  - Many web attacks (drive-by-infection) use PDF and Flash
  - The PDF Reader and Flash have lots of security vulnerabilities
  - Acrobat is very slow in fixing them at the moment
  - The exploits made public also work for Linux

  Adding rules for the reader and flash would give some bang for the
  buck

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

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

[Touch-packages] [Bug 811885] Re: AppArmor profile for Dropbox

[Launchpad Bug Tracker]

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

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

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

Title:
  AppArmor profile for Dropbox

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  Disclaimer: This is not a real bug report, this is a new profile.

  Attached is an AppArmor-Profile for Dropbox.  IMO it should be include
  either in the default package or in apparmor-profiles.

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

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

[Touch-packages] [Bug 1270784] Re: aa-status --enabled failed in LXC container with Permission denied: '/sys/kernel/security/apparmor/profiles'

[Launchpad Bug Tracker]

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

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

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

Title:
  aa-status --enabled failed in LXC container with  Permission denied:
  '/sys/kernel/security/apparmor/profiles'

Status in lxc package in Ubuntu:
  Expired

Bug description:
  In an up to date Trusty container install apparmor and run:

  root@trusty-amd64:~# aa-status --enabled
  Traceback (most recent call last):
File "/usr/sbin/aa-status", line 194, in 
  commands[cmd]()
File "/usr/sbin/aa-status", line 17, in cmd_enabled
  if get_profiles() == {}:
File "/usr/sbin/aa-status", line 92, in get_profiles
  for p in open(apparmor_profiles).readlines():
  PermissionError: [Errno 13] Permission denied: 
'/sys/kernel/security/apparmor/profiles'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apparmor 2.8.0-0ubuntu38
  ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8
  Uname: Linux 3.13.0-4-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jan 20 11:26:01 2014
  KernLog:
   Jan 20 08:03:53 sark kernel: [163212.225370] type=1400 
audit(1390201433.425:86): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=16135 
comm="apparmor_parser"
   Jan 20 08:03:53 sark kernel: [163212.225382] type=1400 
audit(1390201433.425:87): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=16135 comm="apparmor_parser"
   Jan 20 08:03:53 sark kernel: [163212.225931] type=1400 
audit(1390201433.425:88): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=16135 comm="apparmor_parser"
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-4-generic 
root=UUID=cf89ba34-108b-404d-9804-32d54a1df2ea ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to trusty on 2012-01-31 (719 days ago)

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

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

[Touch-packages] [Bug 1010629] Re: Google video chat plugin needs it's apparmor abstraction revised

[Launchpad Bug Tracker]

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

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

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

Title:
  Google video chat plugin needs it's apparmor abstraction revised

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  This is related to #626451 - I have confirmed that the fix from that
  ticket is present in /etc/apparmor.d/abstractions/ubuntu-
  browsers.d/multimedia however the problem is not fixed.

  The Google Talk plugin (64 bit on my 12.04 system) is installed, but
  does not show up in plugins.

  I applied the fix from http://sifter.org/~simon/journal/20110823.html
  which resolved the problem.

  Dist config is:

# Googletalk
/opt/google/talkplugin/*.so mr,
/opt/google/talkplugin/lib/*.so mr,
/opt/google/talkplugin/GoogleTalkPlugin ixr,
owner @{HOME}/.config/google-googletalkplugin/** rw,

  Working config is:

/opt/google/talkplugin/*.so mr,
/opt/google/talkplugin/lib/*.so mr,
/opt/google/talkplugin/GoogleTalkPlugin ixr,
/usr/bin/lsb_release Ux,
@{PROC}/[0-9]*/net/route r,

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

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

[Touch-packages] [Bug 1272028] Re: remount, not honored on bind mounts

[Launchpad Bug Tracker]

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

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

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

Title:
  remount, not honored on bind mounts

Status in apparmor package in Ubuntu:
  Expired
Status in apparmor source package in Precise:
  Expired
Status in apparmor source package in Trusty:
  Expired
Status in apparmor source package in Utopic:
  Expired

Bug description:
  I was trying to run docker in a nested container.  docker wants to
  remount a bind-mounted dir as ro.  Audit log showed this failed.  I
  first tried to add more specific rules, but when those did not work i
  tried just

  remount,

  in the policy.  Still the mount was denied.  Finally when I added
  'mount,', it worked.

  Ideally I would be able to say

remount options=(ro,bind) -> /var/lib/docker/**/,

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

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

[Touch-packages] [Bug 1305280] Re: apparmor get_cgroup fails when creating lxc with juju local provider

[Launchpad Bug Tracker]

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

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

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

Title:
  apparmor get_cgroup fails when creating lxc with juju local provider

Status in juju-core:
  Invalid
Status in apparmor package in Ubuntu:
  Expired

Bug description:
  I wanted to try out 1.18 on the local provider for armhf.

  juju-core:
    Installed: 1.18.0-0ubuntu1
    Candidate: 1.18.0-0ubuntu1

  After installing juju-local, followed by juju init.  The local
  bootstrap appears to start successfully. When deploying charms the
  following error occurs below. This also occurs when adding a machine
  by itself with the ' $juju add-machine  ' command.

  ubuntu@g7:/var/log/juju-ubuntu-local$ juju status
  environment: local
  machines:
    "0":
  agent-state: started
  agent-version: 1.18.0.1
  dns-name: localhost
  instance-id: localhost
  series: trusty
    "1":
  agent-state-info: '(error: error executing "lxc-start": command 
get_cgroup failed
    to receive response)'
  instance-id: pending
  series: precise
  services: {}

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1305280/+subscriptions

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

[Touch-packages] [Bug 590636] Re: please include an apparmor profile for tinyproxy

[Launchpad Bug Tracker]

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

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

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

Title:
  please include an apparmor profile for tinyproxy

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  Binary package hint: tinyproxy

  Hello; tinyproxy is ideally suited for an AppArmor profile because its
  behaviour can be very clearly defined, and it serves as a gateway
  between probably trusted programs and probably untrusted sites. (Not
  that AppArmor can prevent it from passing along bad data, but protocol
  parsing in C is notoriously difficult.)

  I've included an AppArmor profile I generated while testing tinyproxy
  for an application. It's not exhaustive by any stretch, but a good
  start none-the-less.

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

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

[Touch-packages] [Bug 148984] Re: We should have Java and Mono abstractions

[Launchpad Bug Tracker]

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

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

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

Title:
  We should have Java and Mono abstractions

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  Binary package hint: apparmor

  We already have abstractions for Python and Ruby and many other
  language frameworks; I think we should do the same for Java and Mono

  For Java, I think it should be as simple as:

/usr/lib/jvm/**/bin/java ixr,
/usr/lib/jvm/**/bin/java_vm ixr,
/usr/lib/jvm/** r,

  For Mono, it should be something like

  /usr/bin/mono ixr,
  /usr/lib/mono/**.dll mr,
  /etc/mono/** r,


  I have roughly tested the Java abstraction, but am completely guessing
  on Mono.

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

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

[Touch-packages] [Bug 1070950] Re: /run/lxc/dnsmasq.pid denied by dnsmasq apparmor-profile

[Launchpad Bug Tracker]

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

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

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

Title:
  /run/lxc/dnsmasq.pid denied by dnsmasq apparmor-profile

Status in apparmor package in Ubuntu:
  Expired

Bug description:
  installing lxc after apparmor-profiles results in following error:

  [ 1908.149861] type=1400 audit(1351098588.635:143): apparmor="DENIED"
  operation="mknod" parent=25607 profile="/usr/sbin/dnsmasq"
  name="/run/lxc/dnsmasq.pid" pid=25608 comm="dnsmasq"
  requested_mask="c" denied_mask="c" fsuid=0 ouid=0

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

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

[Touch-packages] [Bug 494259] Re: pulse audio remembers muted applications without notification

[Mathew Hodson]

** Tags removed: mute pulse pulseaudio

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

Title:
  pulse audio remembers muted applications without notification

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  pulseaudio remembers which applications were muted last time. so i
  muted skype via pulseaudio in sound preferences -> applications awhile
  back and skype output audio "hasn't worked" since.

  it took me a while to realize that skype was muted. this was
  compounded by the fact that skype doesn't show up in the applications
  list when it is not actively trying to make a sound, so i couldn't
  tell that skype was muted without making a call.

  i think this is a usability problem - it would be nice if pa used the
  notification system to alert the user when an app starts that it will
  run muted...

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

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

[Touch-packages] [Bug 1272028] Re: remount, not honored on bind mounts

[Launchpad Bug Tracker]

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

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

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

Title:
  remount, not honored on bind mounts

Status in apparmor package in Ubuntu:
  Expired
Status in apparmor source package in Precise:
  Expired
Status in apparmor source package in Trusty:
  Expired
Status in apparmor source package in Utopic:
  Expired

Bug description:
  I was trying to run docker in a nested container.  docker wants to
  remount a bind-mounted dir as ro.  Audit log showed this failed.  I
  first tried to add more specific rules, but when those did not work i
  tried just

  remount,

  in the policy.  Still the mount was denied.  Finally when I added
  'mount,', it worked.

  Ideally I would be able to say

remount options=(ro,bind) -> /var/lib/docker/**/,

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

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

[Touch-packages] [Bug 1272028] Re: remount, not honored on bind mounts

[Launchpad Bug Tracker]

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

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

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

Title:
  remount, not honored on bind mounts

Status in apparmor package in Ubuntu:
  Expired
Status in apparmor source package in Precise:
  Expired
Status in apparmor source package in Trusty:
  Expired
Status in apparmor source package in Utopic:
  Expired

Bug description:
  I was trying to run docker in a nested container.  docker wants to
  remount a bind-mounted dir as ro.  Audit log showed this failed.  I
  first tried to add more specific rules, but when those did not work i
  tried just

  remount,

  in the policy.  Still the mount was denied.  Finally when I added
  'mount,', it worked.

  Ideally I would be able to say

remount options=(ro,bind) -> /var/lib/docker/**/,

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

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

[Touch-packages] [Bug 1400404] Re: [HP EliteBook 8560w] Changing the screen brightness does not work

[Christopher M. Penalver]

** Package changed: xorg (Ubuntu) => linuxmint

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

Title:
  [HP EliteBook 8560w] Changing the screen brightness does not work

Status in The Linux Mint Distribution:
  New

Bug description:
  Changing the screen brightness does not work in 331.38 on my HP
  Elitebook 8560w.

  Description:  Linux Mint 17.1 Rebecca
  Release:  17.1

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: X-Cinnamon
  Date: Mon Dec  8 17:57:29 2014
  DistUpgraded: Fresh install
  DistroCodename: rebecca
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
   nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
   virtualbox-guest, 4.3.18, 3.13.0-24-generic, x86_64: installed 
(original_module exists)
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1631]
  InstallationDate: Installed on 2014-12-04 (3 days ago)
  InstallationMedia: Linux Mint 17 "Qiana" - Release amd64 20140530
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=cc5dc2fd-1460-4011-afd8-fb904d6446a5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.42
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.3D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8560w
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 17:45:17 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 594257] Re: cannot disable system beep [10.04]

[Mathew Hodson]

** Tags removed: 10.04 beep mute shutdown sleep
** Tags added: lucid

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

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

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

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

Title:
  cannot disable system beep [10.04]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Tried:
  - Sound-->Alertvolume: Slider to 0
  - Sound-->Alertvolume: Mute enabled
  - Blacklisting pcspkr according to this:
  
http://www.arsgeek.com/2006/08/23/how-to-turn-off-the-annoying-system-beep-in-linux-debianubuntu/
  - and at least one other forum topic, i cant remember which though

  It still beeps annoyingly loud everytime I put the laptop to sleep or
  shut it down

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

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

[Touch-packages] [Bug 927116] Re: sound does not come from headphones when they are plugged in

[Mathew Hodson]

** Tags removed: headphones jack mute speakers
** Tags added: kubuntu oneiric

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  sound does not come from headphones when they are plugged in

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a Meoo Design Box DB-N6643/U notebook, running Kubuntu Oneiric
  11.10 64.

  When I plug in earphones or external speakers, phonon correctly
  detects it and in (my free translation from Brazilian Portuguese
  labels to English) Phonon -> Audio Hardware configuration -> Sound
  device, with "Reproduction (Internal analog stereo audio)" selected,
  it changes "conector" automatically to "analog earphones".

  BUT when ths happens, sound stops coming from internal speakers as
  expected, but does not come from the headphones neither.

  IF I change manually "Conector" back to "Analog Speakers", everything
  works OK, sound coming from the jack and no sound from internal
  speakers.

  Unfortunatelly it is very annoying to have to open KDE configuration
  and going to Phonon to manually change "conector" to "analog speakers"
  everytime I plug in my headphones or external speakers.

  My hardware:
  $ lspci
  00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
  00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
  00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b3)
  00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
  00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
  00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
  00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)  
  
  00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev 
b1)   
  00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev 
b1)   
  00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1) 
  
  00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1)  
  
  00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1)   
  
  00:0b.0 SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)
  
  00:10.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)  
  
  00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)  
  
  00:17.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)  
  
  02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9200M G] 
(rev b1)
  06:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 
35)

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

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

[Touch-packages] [Bug 927116] [NEW] sound does not come from headphones when they are plugged in

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have a Meoo Design Box DB-N6643/U notebook, running Kubuntu Oneiric
11.10 64.

When I plug in earphones or external speakers, phonon correctly detects
it and in (my free translation from Brazilian Portuguese labels to
English) Phonon -> Audio Hardware configuration -> Sound device, with
"Reproduction (Internal analog stereo audio)" selected, it changes
"conector" automatically to "analog earphones".

BUT when ths happens, sound stops coming from internal speakers as
expected, but does not come from the headphones neither.

IF I change manually "Conector" back to "Analog Speakers", everything
works OK, sound coming from the jack and no sound from internal
speakers.

Unfortunatelly it is very annoying to have to open KDE configuration and
going to Phonon to manually change "conector" to "analog speakers"
everytime I plug in my headphones or external speakers.

My hardware:
$ lspci
00:00.0 Host bridge: nVidia Corporation MCP79 Host Bridge (rev b1)
00:00.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.0 ISA bridge: nVidia Corporation MCP79 LPC Bridge (rev b3)
00:03.1 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.2 SMBus: nVidia Corporation MCP79 SMBus (rev b1)
00:03.3 RAM memory: nVidia Corporation MCP79 Memory Controller (rev b1)
00:03.5 Co-processor: nVidia Corporation MCP79 Co-processor (rev b1)

00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev 
b1)   
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev 
b1)   
00:08.0 Audio device: nVidia Corporation MCP79 High Definition Audio (rev b1)   

00:09.0 PCI bridge: nVidia Corporation MCP79 PCI Bridge (rev b1)

00:0a.0 Ethernet controller: nVidia Corporation MCP79 Ethernet (rev b1) 

00:0b.0 SATA controller: nVidia Corporation MCP79 AHCI Controller (rev b1)  

00:10.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)

00:15.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)

00:17.0 PCI bridge: nVidia Corporation MCP79 PCI Express Bridge (rev b1)

02:00.0 VGA compatible controller: nVidia Corporation C79 [GeForce 9200M G] 
(rev b1)
06:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)

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


** Tags: kubuntu oneiric sound
-- 
sound does not come from headphones when they are plugged in
https://bugs.launchpad.net/bugs/927116
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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

[Touch-packages] [Bug 594257] [NEW] cannot disable system beep [10.04]

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Tried:
- Sound-->Alertvolume: Slider to 0
- Sound-->Alertvolume: Mute enabled
- Blacklisting pcspkr according to this:
http://www.arsgeek.com/2006/08/23/how-to-turn-off-the-annoying-system-beep-in-linux-debianubuntu/
- and at least one other forum topic, i cant remember which though

It still beeps annoyingly loud everytime I put the laptop to sleep or
shut it down

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


** Tags: audio lucid
-- 
cannot disable system beep [10.04]
https://bugs.launchpad.net/bugs/594257
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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

[Touch-packages] [Bug 574513] Re: Sound mute by default on fresh installation

[Mathew Hodson]

** Tags removed: mixer mute

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

Title:
  Sound mute by default on fresh installation

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  This is a fresh installation of Ubuntu on my PC. On starting the PC
  after installation I observed that sound is muted by default. Not a
  major problem but can be confusing to new users.

  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-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  onkar  1283 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'V8237'/'VIA 8237 with ALC658D at 0xe000, irq 22'
 Mixer name : 'Realtek ALC658D'
 Components : 'AC97a:414c4781'
 Controls  : 45
 Simple ctrls  : 27
  CurrentDmesg:
   [   22.480041] eth0: no IPv6 routers present
   [   27.320048] end_request: I/O error, dev fd0, sector 0
   [   27.364081] end_request: I/O error, dev fd0, sector 0
  Date: Mon May  3 19:44:10 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 12/19/2003
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 3.06
  dmi.board.name: Kamet2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 2.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr3.06:bd12/19/2003:svnCompaqPresario061:pnDT381A-ACJS6020ILIN430:pvr01H0411LX101KAME210:rvnASUSTekComputerINC.:rnKamet2:rvr2.01:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: DT381A-ACJ S6020IL IN430
  dmi.product.version: 01H0411LX101KAME210
  dmi.sys.vendor: Compaq Presario 061

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

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

[Touch-packages] [Bug 1400386] Re: computer turn on only when i make it so hot in blankets

[Christopher M. Penalver]

tuyishimire olivier, thank you for reporting this and helping make
Ubuntu better. Could you please provide the full computer model as noted
on the sticker of the computer itself (not from the Bug Description)?
For example, Compaq Presario CQ56-201NR Notebook PC.

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

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

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

Title:
  computer turn on only when i make it so hot in blankets

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  it started when i turned it off like usual but  whent i turned it on
  again only  i sow the black screen with capslock flashing and wifi
  button blanking its red color , when fortunately turns on it can't
  come from suspend or hibernation giving black screen

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-26.35-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-26-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Dec  8 18:09:50 2014
  DistUpgraded: 2014-12-04 11:36:36,603 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 3.16.0-26-generic, i686: installed
   tp-smapi, 0.41, 3.16.0-26-generic, i686: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1604]
  InstallationDate: Installed on 2012-11-04 (764 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Hewlett-Packard Presario CQ56 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-26-generic 
root=UUID=c7f6a484-fac9-4fa7-8276-ce78500e24d6 ro nopat splash quiet 
drm.debug=0xe plymouth:debug vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-12-04 (4 days ago)
  dmi.bios.date: 06/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.00
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1604
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 88.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.00:bd06/21/2010:svnHewlett-Packard:pnPresarioCQ56NotebookPC:pvr058D12242810010620100:rvnHewlett-Packard:rn1604:rvr88.04:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Presario CQ56 Notebook PC
  dmi.product.version: 058D12242810010620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Dec  7 17:22:48 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.16.0-1ubuntu1
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1400575] [NEW] sed segfaults on L command with long address lengths

[Jodie Cunningham]

Public bug reported:

To reproduce, run:
sed 'L22' <

[Touch-packages] [Bug 864494] Re: Wrong preview image in the file open dialog.

[Bug Watch Updater]

** Changed in: gtk
   Status: New => Fix Released

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

Title:
  Wrong preview image in the file open dialog.

Status in GTK+ GUI Toolkit:
  Fix Released
Status in One Hundred Papercuts:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Hello,
  File open dialog seems to display wrong preview image in some cases.
  Please study this video:
  http://www.futuredesktop.com/tmp/file-open-test.ogv

  You can reproduce this issue with:
  1)  Open the program for change-desktop-background (appearance dialog).

  2) Click the [+] button and browse to Test/  images.

  3) In the file open dialog, press "b" letter to browse just the images
  that start with "b".  This is important, ok?

  4) Now use arrow-keys to move from one bimage* to another. The preview
  image is wrong.

  Notice: I could only produce this when I restricted the search with a
  letter or word, and then used ARROW-KEYS to jump to next/previous
  file. Selection with mouse works always right.

  Here are the actual Test/ images:
  http://www.futuredesktop.com/tmp/Test.tar.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: nautilus 1:3.2.0-0ubuntu5
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu2
  Architecture: amd64
  Date: Sun Oct  2 09:35:33 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110919)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to oneiric on 2011-09-29 (2 days ago)

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

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

[Touch-packages] [Bug 1398434] Re: e4defrag has fatal CPU performance bottleneck

[Theodore Ts'o]

Please strace the e4defrag process to see if it is spinning in userspace
or in the kernel.If it is spinning in the kernel, then it's a kernel
bug, not an e2fsrpogs problem.  And since you're using a non-Ubuntu
kernel, you'll need to take this to the upstream linux-ext4 mailing
list.

If it turns out to be a case of spinning in the kernel,  what we'll want
to know is whether you can easily reproduce the problem, and if so,
whether you can give us a kernel stack trace by using magic-sysrq-l and
magic-sysrq-t.

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

Title:
  e4defrag has fatal CPU performance bottleneck

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  During defragmentation of a 5 TB ext4 filesystem with one 600 GB file
  with current value of 30 and optimal value of 300 shown by
  `e4defrag -c`, `e4defrag' seems to suffer from a huge CPU performance
  bottleneck. Over hours only one CPU core is used (-> no
  parallelization) and there's almost no I/O during that time <1 % of
  the underlying device's capabilities.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: e2fsprogs 1.42.10-1.1ubuntu1
  Uname: Linux 3.17.4-031704-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  2 16:29:12 2014
  SourcePackage: e2fsprogs
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1391954] Re: indicator-sound not running on first boot

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-touch-session -
0.108+15.04.20141209-0ubuntu1

---
ubuntu-touch-session (0.108+15.04.20141209-0ubuntu1) vivid; urgency=low

  [ Ted Gould ]
  * Override indicator sound to wait for Pulse to be ready (LP:
#1389008, #1391954)

ubuntu-touch-session (0.108+15.04.2014-0ubuntu2) 14.09;
urgency=medium

  * revert the former override change since it was found to be not working on
first boot on fresh installs during milestone testing.
 -- Ubuntu daily releaseTue, 09 Dec 2014 
02:10:38 +

** Changed in: ubuntu-touch-session (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  indicator-sound not running on first boot

Status in ubuntu-touch-session package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1. Boot the device after a fresh flash with --wipe or --bootstrap
  2. Complete the wizard steps
  3. Check the indicators for the presence of the sound indicator

  Expected result:

  Sound indicator is present and running

  Actual result:

  Indicator is not present. There is a placeholder for it on the menu as
  shown in http://people.canonical.com/~brendan-donegan/indicator-
  sound.png

  Running 'status indicator-sound' shows it is stopped

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Wed Nov 12 16:26:28 2014
  InstallationDate: Installed on 2014-11-12 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141112-135345)
  SourcePackage: indicator-sound
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1398419] Re: The screen blanks when continuously creating albums

[Launchpad Bug Tracker]

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

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

Title:
  The screen blanks when continuously creating albums

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu RTM:
  In Progress

Bug description:
  [Procedures]
  1.Open the gallery app
  2  select the album view
  3 .continuously click "+" key to add albums

  [Expect results]
  create albums normally without abnormalities
  [Actual results]
  the screen blanks and you are unable to interact with the app
  The app must be closed and restarted

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Seth Arnold]

If you're going to bodge this with a wrapper script, a better choice
would address the constant network monitoring performed in whoopsie by
using the assume-online command line option.

I don't know the whoopsie codebase but based on a quick reading it looks
like the only real downside to this change would be that error reports
generated when offline wouldn't be sent up as soon as possible, but
would wait until the next time the whoopsie daemon is restarted *and*
there is network connectivity.

It feels like if someone cared enough to devote two hours to this, a
better middle-ground could be found that only polled the network once an
error report had been generated. It might require even more abuse of
global variables, but it shouldn't be too hideous.

Thanks

** Information type changed from Public Security to Public

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  In Progress
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Touch-packages] [Bug 1387241] Re: systemctl is broken

[Omadas]

Also, there is no package libdbus or dbus-daemon.  So even if systemd
was the intent, how would it ever communicate?

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

Title:
  systemctl is broken

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  14.10 introduces the /bin/systemctl command. Unfortunately it does not
  work:

  root@ubuntu:~# systemctl start ssh
  Failed to get D-Bus connection: No connection to service manager.
  root@ubuntu:~# systemctl status
  Failed to get D-Bus connection: No connection to service manager.

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

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

[Touch-packages] [Bug 1387241] Re: systemctl is broken

[Omadas]

Affects multiple users.

** Changed in: systemd (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  systemctl is broken

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  14.10 introduces the /bin/systemctl command. Unfortunately it does not
  work:

  root@ubuntu:~# systemctl start ssh
  Failed to get D-Bus connection: No connection to service manager.
  root@ubuntu:~# systemctl status
  Failed to get D-Bus connection: No connection to service manager.

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

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

[Touch-packages] [Bug 1387241] Re: systemctl is broken

[Omadas]

Here are some conflicting results:

Output from:
:~$ initctl --systemlist

initctl: invalid option: --systemlist
Try `initctl --help' for more information.
brandon@RomeoMontague:~$ initctl --system list
avahi-daemon start/running, process 897
mountnfs-bootclean.sh start/running
rsyslog start/running, process 697
tty4 start/running, process 1186
udev start/running, process 385
upstart-udev-bridge start/running, process 376
whoopsie start/running, process 1281
nmbd start/running, process 2045
winbind start/running, process 2063
avahi-cups-reload stop/waiting
mountall-net stop/waiting
passwd stop/waiting
rc stop/waiting
startpar-bridge stop/waiting
ureadahead-other stop/waiting
apport start/running
smbd start/running, process 705
tty5 start/running, process 1190
console-setup stop/waiting
gpu-manager stop/waiting
hwclock-save stop/waiting
irqbalance stop/waiting
plymouth-log stop/waiting
modemmanager start/running, process 865
mountall.sh start/running
failsafe stop/waiting
procps-instance stop/waiting
rfkill-store stop/waiting
alsa-utils start/running
atd start/running, process 1236
dbus start/running, process 776
resolvconf start/running
failsafe-x stop/waiting
mounted-var stop/waiting
plymouth-shutdown stop/waiting
plymouth stop/waiting
udev-fallback-graphics stop/waiting
usb-modeswitch-upstart stop/waiting
checkroot.sh start/running
network-manager start/running, process 905
control-alt-delete stop/waiting
hwclock stop/waiting
mounted-proc stop/waiting
cups-browsed start/running, process 1282
alsa-store stop/waiting
setvtrgb stop/waiting
shutdown stop/waiting
cron start/running, process 1265
lightdm start/running, process 2202
mountkernfs.sh start/running
alsa-restore stop/waiting
mountall stop/waiting
mounted-debugfs stop/waiting
binfmt-support start/running
hostname.sh start/running
palm-novacomd start/running, process 2399
console stop/waiting
mounted-run stop/waiting
xboxdrv stop/waiting
acpid start/running, process 1263
bluetooth start/running, process 880
checkfs.sh start/running
checkroot-bootclean.sh start/running
mountnfs.sh start/running
plymouth-stop start/running
ufw start/running
kmod stop/waiting
rcS stop/waiting
reload-smbd stop/waiting
wait-for-state stop/waiting
bootmisc.sh start/running
flush-early-job-log stop/waiting
friendly-recovery stop/waiting
rc-sysinit stop/waiting
samba-ad-dc stop/waiting
cups start/running, process 3531
upstart-socket-bridge start/running, process 708
apparmor stop/waiting
cgproxy stop/waiting
pulseaudio stop/waiting
anacron start/running, process 1232
mountdevsubfs.sh start/running
tty2 start/running, process 1199
upstart-file-bridge start/running, process 665
cryptdisks start/running
udevtrigger stop/waiting
mtab.sh start/running
tty3 start/running, process 1200
udev-finish start/running
container-detect stop/waiting
mounted-dev stop/waiting
cgmanager start/running, process 303
hwclock.sh start/running
alsa-state stop/waiting
cryptdisks-udev stop/waiting
hostname stop/waiting
mountall-reboot stop/waiting
network-interface (lo) start/running
network-interface (eth0) start/running
network-interface (wlan0) start/running
tty1 start/running, process 2400
mountall-shell stop/waiting
mounted-tmp stop/waiting
plymouth-ready stop/waiting
plymouth-splash stop/waiting
plymouth-upstart-bridge stop/waiting
udevmonitor stop/waiting
mountall-bootclean.sh start/running
network-interface-security (network-manager) start/running
network-interface-security (network-interface/eth0) start/running
network-interface-security (network-interface/wlan0) start/running
network-interface-security (network-interface/lo) start/running
network-interface-security (networking) start/running
networking start/running
procps start/running
tty6 start/running, process 1203
dmesg stop/waiting
rfkill-restore stop/waiting
console-font stop/waiting
network-interface-container stop/waiting
ureadahead stop/waiting

Output from:
:~$ findmnt | grep /sys/fs/cgroup

│ ├─/sys/fs/cgroup none tmpfs rw,relatime,size=4k,mode=755
│ │ └─/sys/fs/cgroup/systemd systemd cgroup 
rw,nosuid,nodev,noexec,relatime,release_agent=/run/cgmanager/agents/cgm-release-agent.systemd,name=systemd

Is systemd marked as a recommended package for upstart and installed
during the upgrade process?

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

Title:
  systemctl is broken

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  14.10 introduces the /bin/systemctl command. Unfortunately it does not
  work:

  root@ubuntu:~# systemctl start ssh
  Failed to get D-Bus connection: No connection to service manager.
  root@ubuntu:~# systemctl status
  Failed to get D-Bus connection: No connection to service manager.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Po

[Touch-packages] [Bug 1387241] Re: systemctl is broken

[Omadas]

Also, systemd is not maintained in launchpad, but in bugzilla.  If this
is an error in systemd and it is required for 'some reason', then they
may have to be notified their as well?  I dont know if upstart is the
real problem here, and the package being reported for this bug might
need to be changed to reflect that.

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

Title:
  systemctl is broken

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  14.10 introduces the /bin/systemctl command. Unfortunately it does not
  work:

  root@ubuntu:~# systemctl start ssh
  Failed to get D-Bus connection: No connection to service manager.
  root@ubuntu:~# systemctl status
  Failed to get D-Bus connection: No connection to service manager.

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

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

[Touch-packages] [Bug 1387241] Re: systemctl is broken

[Omadas]

Also effects Haguichi, and presumably any package that calls on /bin/systemctl. 
 
see my Bug report here:  https://answers.launchpad.net/haguichi/+question/258759

This happened only after upgrade to 14.10.  Martin Pitt, care to write a
quick tutorial on how to change the correct boot settings to reflect
your change if that fixes it?  (I will test if you cannot reproduce this
error)

Also, maintainer/admin:  This bug is confirmed, I have it too.

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

Title:
  systemctl is broken

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  14.10 introduces the /bin/systemctl command. Unfortunately it does not
  work:

  root@ubuntu:~# systemctl start ssh
  Failed to get D-Bus connection: No connection to service manager.
  root@ubuntu:~# systemctl status
  Failed to get D-Bus connection: No connection to service manager.

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

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

[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[HRJ]

** Information type changed from Public to Public Security

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  In Progress
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Touch-packages] [Bug 874767] Re: Cannot use color profile nor profiling monitor with fglrx driver (colord).

[Mathew Hodson]

** Tags removed: color colord drivers profile restricted
** Tags added: oneiric

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

Title:
  Cannot use color profile nor profiling monitor with fglrx driver
  (colord).

Status in colord package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 11.10
  Release:  11.10
  Colord 0.1.12-1ubuntu2
  fgrlx-updates 2:8.881-0ubuntu6
  Ati Radeon HD 5650/4200

  There is not a display device in the color section of the system
  configuration. I can;t profile the monitor no matter the if I use the
  5650 or the 4200.

  Colord  works perfectly with the Gallium3D driver.

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

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

[Touch-packages] [Bug 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***

[Ricardo Salveti]

** Package changed: gstreamer (Ubuntu) => gst-plugins-bad1.0 (Ubuntu)

** Package changed: gstreamer (Ubuntu RTM) => gst-plugins-bad1.0 (Ubuntu
RTM)

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

Title:
  /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-
  service-2.0': double free or corruption (fasttop): ADDR ***

Status in the base for Ubuntu mobile products:
  In Progress
Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress
Status in mediascanner2 package in Ubuntu:
  Invalid
Status in gst-plugins-bad1.0 package in Ubuntu RTM:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediascanner2.  This problem was most recently seen with
  version 0.104+14.10.20140825-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56
  and
  https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83
  contains more details.

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

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

[Touch-packages] [Bug 1400133] Re: Wireless USB mouse not recognised by ubuntu 14.04 64 bit

[Christopher M. Penalver]

Capone Cash, as per 
http://www.asus.com/us/Notebooks_Ultrabooks/X550JK/HelpDesk_Download/ an update 
to your BIOS is available (303). If you update to this following 
https://help.ubuntu.com/community/BIOSUpdate does it change anything?  If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

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

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

** Tags added: bios-outdated-303

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2

[Touch-packages] [Bug 845577] Re: mii-tool reporting incorrect duplex mode

[kakaroto]

the bug is still present in 14.04.1 LTS:

[root->~]#  mii-tool eth0
eth0: negotiated 1000baseT-HD flow-control, link ok
[root->~]#  ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes:  10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 1000baseT/Half 1000baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x0033 (51)
   drv probe ifdown ifup
Link detected: yes

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

Title:
  mii-tool reporting incorrect duplex mode

Status in net-tools package in Ubuntu:
  Confirmed
Status in net-tools package in Debian:
  New

Bug description:
  mii-tool reports half duplex on full duplex connection when using
  RTL8168 series network cards. Ethtool does report the right speed.

  Same bug reported on debian by someone else.
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561851

  terminal:
  #sudo mii-tool
  eth0: negotiated 1000baseT-HD flow-control, link ok

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

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

[Touch-packages] [Bug 1393205] Re: Intel q35 bug on Ubuntu 14.04 (Screen Artifacts)

[Christopher M. Penalver]

Айдеед, as per 
http://www.dell.com/support/home/us/en/19/product-support/product/optiplex-755/drivers
 an update to your BIOS is available (A22). If you update to this following 
https://help.ubuntu.com/community/BIOSUpdate does it change anything?  If it 
doesn't, could you please both specify what happened, and provide the output of 
the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

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

Once the BIOS is updated, then please mark this report Status Confirmed.

Thank you for your understanding.

** Tags removed: 14 intel q35
** Tags added: bios-outdated-a22

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

Title:
  Intel q35 bug on Ubuntu 14.04 (Screen Artifacts)

Status in X.org xf86-video-intel:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Picture simliar of my problem: http://i.stack.imgur.com/0ARuB.jpg

  I went on a Ubuntu support chat website and was told that either this
  problem is a "glitch"  or intel q35 doesn't support Ubuntu 14.04. From
  the chat they told me i should downgrade to Ubuntu 12 which i did but
  i really want to use Ubuntu 14. They also told me to make a bug report
  of this.

  Is this a glitch or is my graphics card unsupportive.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82Q35 Express Integrated Graphics Controller [8086:29b2] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell OptiPlex 755 [1028:0211]
 Subsystem: Dell OptiPlex 755 [1028:0211]
  InstallationDate: Installed on 2014-12-07 (1 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Dell Inc. OptiPlex 755
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: i386
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=a6415cdd-4ad1-4159-845e-83a5d2c7eecc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags:  trusty ubuntu compiz-0.9
  Uname: Linux 3.13.0-40-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/06/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0GM819
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd04/06/2010:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0GM819:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 16:17:35 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Basic Optical Mouse MOUSE, id 8
   inputDELL DELL USB Keyboard KEYBOARD, id 9
   inputDELL DELL USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 435 
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1393205/+subscriptions

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

[Touch-packages] [Bug 959451] Re: Credentials from gnome-keyring is not used while printing

[Mathew Hodson]

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

** Package changed: gtk+2.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Confirmed

** Package changed: ubuntu => gtk+2.0 (Ubuntu)

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: In Progress => Confirmed

** Package changed: ubuntu => gtk+3.0 (Ubuntu)

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

Title:
  Credentials from gnome-keyring is not used while printing

Status in GTK+ GUI Toolkit:
  New
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  For end-user desktops, we've inserted the printing credentials in the
  user's gnome-keyring to make printing authentication automated.

  This worked perfectly last year and still works today ... up to the moment 
when the /etc/cups/printers.conf is auto-modified with the following change :
  AuthInfoRequired none
  to
  AuthInfoRequired username,password

  The result is that the user gets a Window which asks the username and
  the password to print.

  The printers are installed system wide (authentication can not be done
  with the printer's URI) and we send printing jobs to a Windows
  printing server.

  Thanks,

  == Workaround ==
  * add system-config-printer-applet to session start-up.
  * alternate, add the username/password to DeviceURI in printer.conf

  == Note ==
  * print indicator service is deprecated, and usually pops us s-c-p for queue 
mgmt.

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

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

[Touch-packages] [Bug 959451] Re: Credentials from gnome-keyring is not used while printing

[Launchpad Bug Tracker]

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

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

** Changed in: ubuntu
   Status: New => Confirmed

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

Title:
  Credentials from gnome-keyring is not used while printing

Status in GTK+ GUI Toolkit:
  New
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  For end-user desktops, we've inserted the printing credentials in the
  user's gnome-keyring to make printing authentication automated.

  This worked perfectly last year and still works today ... up to the moment 
when the /etc/cups/printers.conf is auto-modified with the following change :
  AuthInfoRequired none
  to
  AuthInfoRequired username,password

  The result is that the user gets a Window which asks the username and
  the password to print.

  The printers are installed system wide (authentication can not be done
  with the printer's URI) and we send printing jobs to a Windows
  printing server.

  Thanks,

  == Workaround ==
  * add system-config-printer-applet to session start-up.
  * alternate, add the username/password to DeviceURI in printer.conf

  == Note ==
  * print indicator service is deprecated, and usually pops us s-c-p for queue 
mgmt.

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

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

[Touch-packages] [Bug 959451] Re: Credentials from gnome-keyring is not used while printing

[Mathew Hodson]

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

** Tags removed: rfe

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

Title:
  Credentials from gnome-keyring is not used while printing

Status in GTK+ GUI Toolkit:
  New
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  For end-user desktops, we've inserted the printing credentials in the
  user's gnome-keyring to make printing authentication automated.

  This worked perfectly last year and still works today ... up to the moment 
when the /etc/cups/printers.conf is auto-modified with the following change :
  AuthInfoRequired none
  to
  AuthInfoRequired username,password

  The result is that the user gets a Window which asks the username and
  the password to print.

  The printers are installed system wide (authentication can not be done
  with the printer's URI) and we send printing jobs to a Windows
  printing server.

  Thanks,

  == Workaround ==
  * add system-config-printer-applet to session start-up.
  * alternate, add the username/password to DeviceURI in printer.conf

  == Note ==
  * print indicator service is deprecated, and usually pops us s-c-p for queue 
mgmt.

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

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

[Touch-packages] [Bug 959451] Re: Credentials from gnome-keyring is not used while printing

[Mathew Hodson]

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

** Package changed: debian => gtk+2.0 (Ubuntu)

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

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

Title:
  Credentials from gnome-keyring is not used while printing

Status in GTK+ GUI Toolkit:
  New
Status in gtk+2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Hi,

  For end-user desktops, we've inserted the printing credentials in the
  user's gnome-keyring to make printing authentication automated.

  This worked perfectly last year and still works today ... up to the moment 
when the /etc/cups/printers.conf is auto-modified with the following change :
  AuthInfoRequired none
  to
  AuthInfoRequired username,password

  The result is that the user gets a Window which asks the username and
  the password to print.

  The printers are installed system wide (authentication can not be done
  with the printer's URI) and we send printing jobs to a Windows
  printing server.

  Thanks,

  == Workaround ==
  * add system-config-printer-applet to session start-up.
  * alternate, add the username/password to DeviceURI in printer.conf

  == Note ==
  * print indicator service is deprecated, and usually pops us s-c-p for queue 
mgmt.

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

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

[Touch-packages] [Bug 959451] Re: Credentials from gnome-keyring is not used while printing

[Launchpad Bug Tracker]

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

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

** Changed in: gtk+2.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Credentials from gnome-keyring is not used while printing

Status in GTK+ GUI Toolkit:
  New
Status in gtk+2.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Hi,

  For end-user desktops, we've inserted the printing credentials in the
  user's gnome-keyring to make printing authentication automated.

  This worked perfectly last year and still works today ... up to the moment 
when the /etc/cups/printers.conf is auto-modified with the following change :
  AuthInfoRequired none
  to
  AuthInfoRequired username,password

  The result is that the user gets a Window which asks the username and
  the password to print.

  The printers are installed system wide (authentication can not be done
  with the printer's URI) and we send printing jobs to a Windows
  printing server.

  Thanks,

  == Workaround ==
  * add system-config-printer-applet to session start-up.
  * alternate, add the username/password to DeviceURI in printer.conf

  == Note ==
  * print indicator service is deprecated, and usually pops us s-c-p for queue 
mgmt.

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

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

[Touch-packages] [Bug 1007677] Re: overlayfs: on-boot, mount device issue.

[Launchpad Bug Tracker]

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  overlayfs: on-boot, mount device issue.

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Hello example fstab entries I've tested,

  overlayfs /usr overlayfs 
defaults,lowerdir=/.usr-ro/local/..,upperdir=/.usr-rw/lost+found/.. 0 2
  none /usr overlayfs 
defaults,lowerdir=/.usr-ro/local/..,upperdir=/.usr-rw/lost+found/.. 0 2

  On boot I get an error about the device overlayfs/none, so I'm
  prompted to enter maintenance mode.  I issue a "mount -a; exit;" and
  all is well the boot success.

  I'm sick of doing this.

  Here is a small script I wrote to resquash /usr, it's incomplete as
  I'm not sure how to size the lv.

  #!/bin/sh
  mksquashfs /usr /root/usr.sqfs -comp lzo -no-exports -always-use-fragments 
-wildcards -e local/*&
  kpid=$!

  (
  #unsquashfs -s usr.sqfs
  #lvcreate -L 5G Arcadia -n nuusr$$.ro
  cryptsetup -q luksFormat /dev/Arcadia/nuusr$$.ro /etc/keys/key.txt
  newo=$(cryptsetup luksUUID /dev/Arcadia/nuusr$$.ro)
  cryptsetup luksOpen /dev/Arcadia/nuusr$$.ro $newo --key-file /etc/keys/key.txt
  wait $kpid
  { dd if=/root/usr.sqfs bs=4k; cat /dev/urandom; } | dd bs=4M 
of=/dev/mapper/$newo
  cryptsetup luksClose $newo
  ) &
  opid=$!

  lvcreate -L 8G Arcadia -n nuusr$$.rw
  cryptsetup -q luksFormat /dev/Arcadia/nuusr$$.rw /etc/keys/key.txt
  neww=$(cryptsetup luksUUID /dev/Arcadia/nuusr$$.rw)
  cryptsetup luksOpen /dev/Arcadia/nuusr$$.rw $neww --key-file /etc/keys/key.txt
  mkfs.ext4 /dev/mapper/$neww
  tune2fs -e remount-ro -o journal_data_writeback,discard /dev/mapper/$neww
  cryptsetup luksClose $neww

  wait $opid
  newo=$(cryptsetup luksUUID /dev/Arcadia/nuusr$$.ro)
  oldo=$(grep fsUsr.ro /etc/crypttab | grep -o 
----)
  oldw=$(grep fsUsr.rw /etc/crypttab | grep -o 
----)
  sed -i -e "s/$oldo/$newo/" -e "s/$oldw/$neww/" /etc/crypttab

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: mount 2.20.1-1ubuntu3 [modified: bin/findmnt bin/mount bin/umount 
sbin/losetup sbin/swapon]
  ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14
  Uname: Linux 3.2.0-23-lowlatency-pae i686
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Fri Jun  1 19:28:18 2012
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to precise on 2012-01-03 (150 days ago)

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

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

[Touch-packages] [Bug 1391501] Re: Calendar reminders should mute if phone is muted

[Michał Sawicz]

** Summary changed:

- Calendar reminders should not use the alarm role
+ Calendar reminders should mute if phone is muted

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

Title:
  Calendar reminders should mute if phone is muted

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Calendar reminders seem to use the alarm role, which means muting your
  phone does not impact them.

  It should either use the same role as the ringer, or maybe a
  completely separate one.

  This is related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 11 13:06:24 2014
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1329584] Re: The label in the panel menu doesn't match the /etc/os-release NAME

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1329584

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

Title:
  The label in the panel menu doesn't match the  /etc/os-release NAME

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

Bug description:
  The desktop name "Ubuntu Desktop" can't change to "Ubuntu Kylin
  Desktop",it is not convenient for us to change it to our Special
  symbol.

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

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

[Touch-packages] [Bug 1391501] Re: Calendar reminders should not use the alarm role

[Michał Sawicz]

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

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

Title:
  Calendar reminders should not use the alarm role

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  New
Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Calendar reminders seem to use the alarm role, which means muting your
  phone does not impact them.

  It should either use the same role as the ringer, or maybe a
  completely separate one.

  This is related to bug #1291458.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov 11 13:06:24 2014
  SourcePackage: indicator-datetime
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Ubuntu Foundations Team Bug Bot]

The attachment "wrapper script for dnsmasq, purges option --cache-
size=0" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  In Progress
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Touch-packages] [Bug 1328677] Re: unity first-run stamp should not be in XDG_CACHE_HOME

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1328677

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

Title:
  unity first-run stamp should not be in XDG_CACHE_HOME

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

Bug description:
  The unity first_run.stamp file should not be in XDG_CACHE_HOME.  As it
  is a _cache_, it can be ephemeral.  Rather, it should be in
  XDG_CONFIG_HOME.  Once the keyboard shortcut list, for example, has
  been presented, I don't need to be told about it again, even if I need
  to purge my ~/.cache directory.

  This is a problem at our site, where XDG_CACHE_HOME is stored on a
  temporary filesystem, to cut down on the tremendous amount of useless
  network traffic between workstations and the user's file server.  As a
  result, users now have to learn about Unity keyboard shortcuts on
  every single login.

  Relevant info:

  unity:
Installed: 7.2.1+14.04.20140513-0ubuntu2
Candidate: 7.2.1+14.04.20140513-0ubuntu2
Version table:
   *** 7.2.1+14.04.20140513-0ubuntu2 0
  500 http://mirrors.mit.edu/ubuntu/ trusty-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ trusty/main amd64 Packages

  Distributor ID:   Ubuntu
  Description:  Ubuntu 14.04 LTS
  Release:  14.04
  Codename: trusty

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

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

[Touch-packages] [Bug 991481] Re: Constant dns traffic for daisy.ubuntu.com

[Klaus Bielke]

More experiments, results and proposed solution:

1) On a system with

  whoopsie running
  network-manager NOT running, but network interface initialized via 
/etc/network/interfaces
  dnsmask running with network-managers configuration for dnsmasq
  IPv6 aktivated

I see the annoying repetive DNS-traffic for daisy.ubuntu.com. One or
more packets per minute. This proves network-manager itself is not the
bad guy!

2) Network-manager provides a configuration to dnsmask which disabled
cache (--cache-size=0). Removing this option from dnsmasq configuration
reduces traffic rate to 1 packet per 10 minutes. This corresponds to the
lifetime for the DNS record of daisy.ubuntu.com which is set to 600
seconds.

3) Running network-manager again and dnsmasq started from network-
manager, but with the modified configuration shows same result as #2.

4) HOWTO modify configuration for dnsmasq: Network-manager provides the
option --cache-size=0 as argument on command line. This cannot be
overriden by config-files, but you can use a wrapper script which is
called by network-manager instead of real dnsmasq. The fake dnsmask
purges the option --cache-size=0 and calls the real dnsmasq.

I provide this wrapper script as attachment. Place it in /usr/local/sbin
(this directory is searched before /usr/sbin), name it dnsmasq, set
owner and group to root and set execute bits. Use at own risk.

Enjoy!

** Attachment added: "wrapper script for dnsmasq, purges option --cache-size=0"
   
https://bugs.launchpad.net/whoopsie/+bug/991481/+attachment/4276624/+files/dnsmasq

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

Title:
  Constant dns traffic for daisy.ubuntu.com

Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in glib2.0 package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  In Progress
Status in whoopsie package in Ubuntu:
  Triaged

Bug description:
  Watching GNetworkMonitor's network-changed signal causes constant DNS
  traffic.

  Andy Whitcroft points out that the NETLINK_ROUTE socket set up by
  GNetworkMonitor will fire events every time an ARP entry appears or
  disappears.

  Unfortunately, we currently need an additional layer of connectivity
  checking because checking NetworkManager's state for CONNECTED_GLOBAL
  is not enough to know whether we're really online. Ubuntu does not yet
  use the NetworkManager connectivity check [1].

  The likely solution to this bug is a replacement for GNetworkMonitor
  in whoopsie.

  1: http://bazaar.launchpad.net/~daisy-
  pluckers/whoopsie/trunk/view/head:/src/connectivity.c#L326

  Original report follows:

  Every few seconds, I see a dns query for daisy.ubuntu.com. After
  removing whoopsie, the traffic goes away.

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

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

[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1316265

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

Title:
  Maximized Window's Title Bar Does Not Merge into Menu Bar after
  Performing Super+W (window spread) filtering

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

Bug description:
  A maximized application's title bar does not merge into the menu bar
  once a user has performed Super + W (window slide). Note that if one
  does not do Super+E, then the bars to merge together. However, once
  Super+E has been performed, this bug persists for the lifetime of the
  windowed application. If the application is restarted after doing
  Super+E, then the bug is gone. Thus, it seems like Super+E introduces
  this bug for the lifetime of the windowed application.

  Expected behavior: Maximized window's title bar is merged into menu bar.
  Observed: Does not occur after Super+W is performed.

  Try this out using Terminal.

  ProblemType: BugDistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon May  5 14:48:01 2014
  InstallationDate: Installed on 2013-09-08 (239 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130424)SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago)

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

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

[Touch-packages] [Bug 1400495] Re: init-checkconf returns seemingly random results

[Rich Drewes]

Actually, it seems there isn't anything in particular about being in a
script that causes init-checkconf to return random results.  If I repeat
the same command a number of times the results vary:


root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
ERROR: File /etc/init/tty5.conf: syntax invalid:
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
ERROR: File /etc/init/tty5.conf: syntax invalid:
root@ladastra:/oldroot/home/drewes# init-checkconf /etc/init/tty5.conf
File /etc/init/tty5.conf: syntax ok


As is evident, sometimes the syntax is reported as being ok and
sometimes invalid.

Rich

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

Title:
  init-checkconf returns seemingly random results

Status in upstart package in Ubuntu:
  New

Bug description:
  While tracking down a problem related to upstart, I decided to check
  the syntax of all my upstart init files.  I wrote this simple script:

  for a in /etc/init/*; do init-checkconf $a; done 2>&1 | grep invalid

  This script said that a number of files had syntax errors.  When the
  file with the error is checked individually on the command line with
  init-checkconf, it shows no error.

  Running the script again showed a different set of files with errors.
  Checking each file individually on the command line does not show an
  error.

  Running it a third time gave yet another set of files with errors.

  Why would this give different results each time it is run?  Why does
  init-checkconf report seemingly random syntax errors when run in a
  script?

  Rich

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  .etc.init.glusterfs.server.override: manual
  .etc.init.mounting.glusterfs.override: manual
  .etc.init.mysql.override: manual
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Dec  8 13:08:53 2014
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=0feac9b2-7f2c-44ed-af0a-e7ace6c02b41 ro nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (233 days ago)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: 
'/etc/at.deny']
  modified.conffile..etc.dconf.db.gdm: [modified]
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.init.d.smbd: [modified]
  modified.conffile..etc.vsftpd.conf: [modified]
  mtime.conffile..etc.dconf.db.gdm: 2014-07-31T12:57:17
  mtime.conffile..etc.default.cups: 2014-04-19T12:34:54
  mtime.conffile..etc.init.d.smbd: 2014-12-08T11:57:38.341196
  mtime.conffile..etc.vsftpd.conf: 2014-06-06T13:12:21

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

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

[Touch-packages] [Bug 1302885] Re: Media keyboard shortcuts not working

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1302885

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

Title:
  Media keyboard shortcuts not working

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

Bug description:
  I can map the Volume Control keys in Keyboard Shortcuts e.g. Volume
  up/down to Volume up/down, but when I press the Volume keys on the
  keyboard nothing happens.

  I have noticed the same problem with other keys on my Logitech Internet 350 
keyboard with Tools, Mail, and HomePage.
  They can all be mapped with Keyboard Shortcuts, but nothing happens 
afterwards when the keyboard key is pressed.

  All these keyboard settings worked fine in older versions of Ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140328-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 23:49:58 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-04-02 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140402)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu12
   deja-dup 30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1350357] Re: Support disabling of user switching per seat

[Robert Ancell]

Confirmed fixed in 1.10.3-0ubuntu2

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Support disabling of user switching per seat

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  No method of disabling user switching for LightDM. Some system administrators 
require this. There are methods to disable this inside the session but it is 
preferrable for a single method of doing this.

  [Test Case]
  1. Disable user switching in the LightDM configuration:
   [SeatDefaults]
   allow-user-switching=false
  2. Start LightDM
  3. Log in
  4. Attempt to switch user
  Expected result:
  User is unable to switch
  Observed result:
  Currently not supported - switching is allowed

  [Regression Potential]
  There is some risk of unrelated code being changed. This has been reduced by 
the use of regression tests, manual testing and providing this in the Ubuntu 
Desktop PPA.

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

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

[Touch-packages] [Bug 1370852] Re: Scans all user accounts when not required

[Robert Ancell]

Confirmed fixed in 1.10.3-0ubuntu2

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Scans all user accounts when not required

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  When AccountsService is not present on startup LightDM scans all the user 
accounts and attempts to access the dmrc file for each user. It does not use 
any information from the dmrc files. If you have many users and/or the dmrc 
files are on a slow filesystem this creates a big startup delay.

  [Test Case]
  1. Start LightDM on a system that doesn't have AccountsService and has many 
users
  Expected result:
  LightDM starts quickly
  Observed result:
  LightDM takes a long time to start

  [Regression potential]
  Low. We now only access the dmrc files when information from them i s 
required (lazy load). Tested with regression tests.

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

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

[Touch-packages] [Bug 1377373] Re: Variables defined twice in config files lead to crash

[Robert Ancell]

Confirmed fixed in 1.10.3-0ubuntu2

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Variables defined twice in config files lead to crash

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in Light Display Manager 1.12 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Released
Status in lightdm package in Debian:
  Fix Released

Bug description:
  [Impact]
  Having the same configuration variable defined in two places causes LightDM 
to a double free and potentially crash.

  [Test Case]
  1. Install two configuration files in /etc/lightdm/lightdm.conf.d which both 
define the same variable.
  2. Run LightDM
  Expected result:
  LightDM runs correctly.
  Observed result:
  LightDM double frees a variable (seen with valgrind) and can crash.

  [Regression Potential]
  Low. The fix is not to double free the variable.

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

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

[Touch-packages] [Bug 1305006] Re: Crashes running display server scripts for non X servers

[Robert Ancell]

Confirmed fixed in 1.10.3-0ubuntu2

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Crashes running display server scripts for non X servers

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Running non X server setups (e.g. Unity 8) and having display server scripts 
configured leads to LightDM crashing. This is due to a faulty assumption in 
LightDM assuming all display servers are X servers. Commonly caused by having 
nVidia prime support installed. Error reports in [1].

  [Test Case]
  1. Install the Unity 8 desktop preview
  2. Configure a display setup script in the LightDM configuration:
   [SeatDefaults]
   display-setup-script=...
  3. Start LightDM
  4. Log in Unity 8
  Expected result:
  Setup script is run and you are logged into Unity 8
  Observed result:
  LightDM crashes

  [Regression Potential]
  Low, fix is simple. Tested with regression tests.

  [1]
  
https://errors.ubuntu.com/bucket/?id=/usr/sbin/lightdm%3A11%3Ax_server_local_get_authority_file_path%3Aseat_xlocal_run_script%3Arun_script%3Adisplay_server_ready_cb%3A_g_closure_invoke_va

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

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

[Touch-packages] [Bug 1320880] Re: Calendar notifications are treated the same as an alarm notification

[Charles Kerr]

** Branch unlinked: lp:~charlesk/indicator-datetime/lp-1317861-handle-
trigger-valarms-in-ical

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

Title:
  Calendar notifications are treated the same as an alarm notification

Status in Calendar application for Ubuntu devices:
  In Progress
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  If an alarm fires, the alarm sound seemingly will persist forever.
  This seems like perhaps the right choice for an alarm clock, but seems
  inappropriate for a calendar reminder. I would expect a calendar
  reminder to sound for only a short period.

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

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

[Touch-packages] [Bug 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered

[Charles Kerr]

** Branch unlinked: lp:~charlesk/indicator-datetime/lp-1317861-handle-
trigger-valarms-in-ical

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

Title:
  OneTime alarms are not automatically dismissed or delete after they
  are triggered

Status in The Date and Time Indicator:
  In Progress
Status in indicator-datetime package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:
  1. Create a one time alarm to ring in a few minutes
  2. Let the alarm ring
  3. Dismiss the alarm

  What happens:
  The OneTime alarm is still shown as enabled and as a result shows the wrong 
status in the clock app. The alarm is no longer shown in the indicator-datetime.

  What should happen:
  The OneTime alarm is either disabled or deleted from the alarm model.

  The clock app cannot disable the alarm since most likely the clock app
  is not even open at the time the alarm is triggered. Since the alarm
  is no longer shown in the indicator-datetime, my intuition tells me
  that indicator-datetime and EDS did its job. Its now up to the SDK
  Alarms API to update the alarm model correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1362341/+subscriptions

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

[Touch-packages] [Bug 1398419] Re: The screen blanks when continuously creating albums

[Bill Filler]

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

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

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

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

Title:
  The screen blanks when continuously creating albums

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Gallery App:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu RTM:
  In Progress

Bug description:
  [Procedures]
  1.Open the gallery app
  2  select the album view
  3 .continuously click "+" key to add albums

  [Expect results]
  create albums normally without abnormalities
  [Actual results]
  the screen blanks and you are unable to interact with the app
  The app must be closed and restarted

  [Reproduce]
  Always

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

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

[Touch-packages] [Bug 1364725] Re: logind session ID not used due to race condition

[Robert Ancell]

Confirmed fixed in 1.10.3-0ubuntu2

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  logind session ID not used due to race condition

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Committed
Status in lightdm source package in Utopic:
  Fix Released

Bug description:
  [Impact]
  Sometimes a session will fail to get the logind session ID to pass back to 
the LightDM daemon. This appears to be due to a race using the D-Bus method 
org.freedesktop.login1.Manager.GetSessionByPID instead of getting the 
environment variable XDG_SESSION_ID as set in PAM.

  This bug was detected by a bug in LightDM 1.11.7 where the daemon
  would attempt to read both a logind and ConsoleKit ID when this D-Bus
  call failed.

  The solution is to use the XDG_SESSION_ID environment variable and not
  GetSessionByPID() and to fix the passing of the session id(s) from the
  session to the daemon to be unambiguous.

  [Test Case]
  Check the LightDM log always contains lines like:
  [+0.78s] DEBUG: Activating login1 session c1
  for each session.

  [Regression Potential]
  Change is non-trivial and could cause other bugs. Regression tests confirm 
existing test cases work.

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

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

[Touch-packages] [Bug 1348251] Re: Not able to configure PAM services

[Robert Ancell]

Confirmed in 1.10.3-0ubuntu2

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Not able to configure PAM services

Status in Light Display Manager:
  Fix Released
Status in Light Display Manager 1.10 series:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in ubuntu-touch-session package in Ubuntu:
  Invalid
Status in lightdm source package in Trusty:
  Fix Committed
Status in ubuntu-touch-session source package in Trusty:
  New
Status in lightdm source package in Utopic:
  Fix Released
Status in ubuntu-touch-session source package in Utopic:
  Invalid

Bug description:
  [Impact]
  No method to configure PAM services used (hard-coded to "lightdm"). This is 
required in some cases, e.g. when running Ubuntu on the phone we want to use a 
different PAM stack. By making this configurable the phone can have a package 
that overrides the default.

  [Test Case]
  1. Set a different PAM stack in the LightDM configuration:
   [SeatDefaults]
   pam-service=custom-service
  2. Start LightDM
  3. Log in
  Expected result:
  PAM modules in "custom-service" are run, user is logged in.
  Observed result:
  PAM modules in "lightdm" are run, user is logged in. (feature not yet 
supported)

  [Regression Potential]
  Low, fix is just replacing hard-coded values with a configuration lookup. 
Tested with regression tests.

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

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

[Touch-packages] [Bug 1305440] Re: Allow a distinct pam config file for greeter and for lock-screen

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1305440

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

Title:
  Allow a distinct pam config file for greeter and for lock-screen

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity-greeter package in Ubuntu:
  Invalid

Bug description:
  It might be desirable to have a distinct pam config file when logging
  in and when unlocking the screen. Specifically, using a fingerprint
  reader is fine for sudo or for unlocking, but you want to use your
  password when logging in, to provide a secret and be able to unlock
  the gnome-keyring for example.

  See http://askubuntu.com/questions/445131/how-do-i-enable-a-specific-
  pam-config-in-the-lockscreen

  So this feature request is about allowing for a (optional) pam config
  file for the lock-screen, distinct from the /etc/pam.d/lightdm
  currently used and shared with the greeter.

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

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

[Touch-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1276177

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

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

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

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

[Touch-packages] [Bug 1299741] Re: Shadows shouldn't wrap around to other workspaces/monitors

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1276177

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

Title:
  Shadows shouldn't wrap around to other workspaces/monitors

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

Bug description:
  I suppose this could be seen as a matter of design opinion but, in my
  opinion, it's incredibly ugly.  To reproduce, launch a whole bunch
  (10, 20, a lot) of windows on workspace 2, and position them on or
  near the right edge.  Then switch to workspace 1, and observe the
  massive black blob on the left of the screen.  This really doesn't
  make a whole lot of sense visually, and it's pretty ugly, IMO.

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

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

[Touch-packages] [Bug 1373695] Re: Not resizable windows can be moved by dragging them on every edge

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1276177

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

Title:
  Not resizable windows can be moved by dragging them on every edge

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

Bug description:
  1. Open a non resizable window such as Calculator or Unity Control Center
  2. Move the mouse to the edge of the window, outside the window itself
 but in the area that is close at least 10 px.
  3. Press the mouse and start to drag

  Expected behavior: 
  4. nothing happens

  Actual behavior
  5. the hand cursor is shown and window can be dragged around
  As side effect, if LIMs are enabled, moving the mouse over a window edge 
makes the menus to show.

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

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

[Touch-packages] [Bug 1301776] Re: Update manager is really small and not resizeable

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1276177

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

Title:
  Update manager is really small and not resizeable

Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in compiz package in Ubuntu:
  Triaged
Status in unity package in Ubuntu:
  Fix Released
Status in compiz source package in Trusty:
  Triaged
Status in unity source package in Trusty:
  Triaged

Bug description:
  update-manager 1:0.196.9, Ubuntu Trusty

  Update manager's window, and especially its fields inside the window, are way 
too small and also it's not resizeable, making it almost useless at least on my 
HiDPI screen (3200 x 1800).
  https://launchpadlibrarian.net/171657786/update-manager-is-small.png

  : "The Updates
  Available window should be manually resizable only when it is in this
  expanded state."

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

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

[Touch-packages] [Bug 1364225] Re: Shadow applied inconsistently to windows that use XShape

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1276177

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

Title:
  Shadow applied inconsistently to windows that use XShape

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

Bug description:
  When using the XShape APIs*, windows that have a rectangular shape are
  treated like normal windows (they get a title bar and shadow) even if
  the rectangular region is much smaller than the window.

  When a non-rectangular window changes its shape to be rectangular, it
  gains a shadow that remains even after changing its shape back to be
  non-rectangular.

  Ideally there would always be a shadow that matches the shape of the
  window.

  In the mean time, the correct behavior might be to remove the shadow
  whenever a shape is applied. If the application wishes to remove an
  applied shape, they could do something like:

XShapeCombineMask(d, w, ShapeBounding, 0, 0, None, ShapeSet);

  Please let me know if you need any more details, or if I'm missing
  something. (Unfortunately, the ubuntu-bug tool wouldn't work when
  filing this bug).

  * http://www.x.org/releases/current/doc/xextproto/shape.html

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

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

[Touch-packages] [Bug 1324104] Re: Ctrl + Super + D hides windows but still resizable when cursor over border

[Launchpad Bug Tracker]

** Branch linked: lp:~unity-team/unity/trusty-1276177

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

Title:
  Ctrl + Super + D hides windows but still resizable when cursor over
  border

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

Bug description:
  If You Press Ctrl + Super + D Shortcut To minimize all windows
  it works but when you move the cursor you will see it change 
  to an arrow for resizing the hidden windows when the cursor
  is in the location of the border of the hidden windows

  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  unity:
Installed: 7.2.0+14.04.20140423-0ubuntu1.2
Candidate: 7.2.0+14.04.20140423-0ubuntu1.2
Version table:
   *** 7.2.0+14.04.20140423-0ubuntu1.2 0
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://lb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   7.2.0+14.04.20140416-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  500 http://lb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

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

[Touch-packages] [Bug 1372548] Re: Phone field doesn't accept symbols #*()

[Bill Filler]

just discussed this in further detail and evaluated what ios and android does
- ios only allows *#+ and Wait (",") and Pause (";") to be stored with numbers
- android allows any kind of formatting with pretty much all characters () 
space, -, etc..

Our model is more like ios. We should modify the keyboard layout to have a 
different set of extended keys: "*#,;"
When this is functional it will not be necessary to store the phone numbers 
formatted in the database, that should be a UI thing only, but that will be 
done in a separate bug.

** Also affects: ubuntu-keyboard (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-keyboard (Ubuntu RTM)
   Importance: Undecided
   Status: New

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

** Tags added: ww51

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

Title:
  Phone field doesn't accept symbols #*()

Status in Address Book App:
  Confirmed
Status in Ubuntu UX bugs:
  New
Status in address-book-app package in Ubuntu:
  New
Status in ubuntu-keyboard package in Ubuntu:
  New
Status in address-book-app package in Ubuntu RTM:
  New
Status in ubuntu-keyboard package in Ubuntu RTM:
  New

Bug description:
  The phone field in address book doesn't accept symbols available in
  the keyboard for phone numbers: #*

  Test case:
  - Open Contacts app.
  - Add a new contact.
  - Go to Phone number field.
  - Press "+" key for 5 seconds and select these symbols: *#()

  Expected result:
  - Field accepts symbols as part of a telephone number.

  Actual result:
  - Only "+" symbol is accepted.

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

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

[Touch-packages] [Bug 1399223] Re: python-testtools should be upgraded to version 1.5.0

[Chris Gagnon]

I've created https://bugs.launchpad.net/ubuntu/+source/python-
unittest2/+bug/1400512 for the unitest2 update request

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

Title:
  python-testtools should be upgraded to version 1.5.0

Status in python-testtools package in Ubuntu:
  Incomplete

Bug description:
  We are using an old version of testtools on ubuntu which prevents us
  from running all dashboard tests and keeping the dashboard from being
  green.

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

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

[Touch-packages] [Bug 1276177] Re: Applications using client-side decorations are not resizable in Unity

[Stephen M. Webb]

** Also affects: unity/7.2
   Importance: Undecided
   Status: New

** Changed in: unity/7.2
   Status: New => In Progress

** Changed in: unity/7.2
   Importance: Undecided => Medium

** Changed in: unity/7.2
Milestone: None => 7.2.4

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

Title:
  Applications using client-side decorations are not resizable in Unity

Status in Themes for Ubuntu:
  In Progress
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Debian:
  Confirmed

Bug description:
  GNOME applications that use client-side decorations can't be resized
  on Unity. I think it's because the frame extents hint is not
  supported.

  gnome-clocks and gnome-tweak-tool are two apps in the archive that
  have this problem.

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

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

[Touch-packages] [Bug 1400133] ProcCpuinfo.txt

[Capone Cash]

apport information

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

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad

Re: [Touch-packages] [Bug 1400133] Re: Wireless USB mouse not recognised by ubuntu 14.04 64 bit

[Capone Cash]

Dear Christopher!

Thanks for the fast answer, I did what you requested, I hope we can find
out what causes the problem, so that others won't have to face it.

2014-12-08 14:41 GMT+01:00 Christopher M. Penalver <
christopher.m.penal...@gmail.com>:

> Capone Cash, thank you for reporting this and helping make Ubuntu
> better. Could you please run the following command in a Terminal as it
> will automatically gather and attach updated debug information to this
> report:
>
> apport-collect -p xorg 1400133
>
> Please ensure you have xdiagnose installed, and that you click the Yes
> button for attaching additional debugging information.
>
> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1400133
>
> Title:
>   Wireless USB mouse not recognised by ubuntu 14.04 64 bit
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Ensure you report the bug via ubuntu-bug xorg as outlined above.
>   What is the full manufacturer and model of your mouse.
>   How is your mouse connected to your PC: serial, PS/2, USB, USB
> wireless, etc.
>   What mechanism does your mouse use: roller ball, optical, trackball,
> etc.
>   How many physical buttons and scrollwheels does you mouse have?
>
>   MAnufacturer and model: Akai, Model: wlm-5330
>   Connected via USB port, wireless
>   Optical mouse, 2,4ghz
>   3 phyisical buttons + scroll
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400133/+subscriptions
>

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd

[Touch-packages] [Bug 1400133] xserver.devices.txt

[Capone Cash]

apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1400133/+attachment/4276583/+files/xserver.devices.txt

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.l

[Touch-packages] [Bug 1400133] ProcEnviron.txt

[Capone Cash]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1400133/+attachment/4276575/+files/ProcEnviron.txt

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad

[Touch-packages] [Bug 1400133] XorgLogOld.txt

[Capone Cash]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1400133/+attachment/4276582/+files/XorgLogOld.txt

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.n

[Touch-packages] [Bug 1400133] XorgConf.txt

[Capone Cash]

apport information

** Attachment added: "XorgConf.txt"
   
https://bugs.launchpad.net/bugs/1400133/+attachment/4276580/+files/XorgConf.txt

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/u

[Touch-packages] [Bug 1400133] XorgLog.txt

[Capone Cash]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1400133/+attachment/4276581/+files/XorgLog.txt

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu

[Touch-packages] [Bug 1400133] ProcInterrupts.txt

[Capone Cash]

apport information

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

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

Title:
  Wireless USB mouse not recognised by ubuntu 14.04 64 bit

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ensure you report the bug via ubuntu-bug xorg as outlined above.
  What is the full manufacturer and model of your mouse.
  How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, 
etc.
  What mechanism does your mouse use: roller ball, optical, trackball, etc.
  How many physical buttons and scrollwheels does you mouse have? 

  MAnufacturer and model: Akai, Model: wlm-5330
  Connected via USB port, wireless
  Optical mouse, 2,4ghz 
  3 phyisical buttons + scroll
  --- 
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.58  Fri Oct 31 17:40:28 
PDT 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.141+bdcom, 3.13.0-40-generic, x86_64: installed
   nvidia-340, 340.58, 3.13.0-40-generic, x86_64: installed
   nvidia-340-uvm, 340.58, 3.13.0-40-generic, x86_64: installed
  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:178d]
 Subsystem: ASUSTeK Computer Inc. Device [1043:178d]
  InstallationDate: Installed on 2014-12-05 (3 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04ca:2006 Lite-On Technology Corp. 
   Bus 001 Device 002: ID 276d:1105  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JK
  NonfreeKernelModules: wl nvidia
  Package: xorg 1:7.7+1ubuntu8
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed 
root=UUID=10620e50-258e-432a-93d6-4da414673d30 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags: trusty third-party-packages ubuntu
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JK.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JK
  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.:bvrX550JK.302:bd07/09/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58+git20141201.f99522e6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141201.ebbd34a4-0ubuntu0ricotz~trusty
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Dec  8 23:02:10 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   NVIDIA(0): Failed to initiate mode change.
   NVIDIA(0): Failed to complete mode change
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1117 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.lau