from:"James Hunt"

[Desktop-packages] [Bug 1800277] [NEW] "chmod u-w ~/.ICEauthority" breaks login

2018-10-27 Thread James Hunt

Public bug reported:

= Problem =

It is too easy to make a system unusable.

= Examples

The following commands will all cause subsequent graphical logins to
fail:

== User is returned to login screen ==

- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority

In this scenario, the user is returned to the login screen with no
indication of what went wrong.

== Session "dead" ==

- chmod 444 ~/.cache
- chmod 000 ~/.config
- chmod 444 ~
- chmod 000 ~

In this scenario, the system just freezes: the cursor is unresponsive
and users will be reaching for the power button.

= Observation =

These scenarios would all be caused by human error.

However, clearly it is possible for the system to detect such issues and
either alert the user to the problem or simply just fix the problem.
This does not happen in Ubuntu 18.04 LTS though.

= Idea =

Have the display manager call a utility prior to executing the users
preferred session. This utility -- which could be a simple shell script
I think ("friendly-session-fixer" maybe? :) -- would do one or both of
the following:

- Perform checks for the issues outlined above warn the user graphically
if any are found.

- Fix any issues found to allow the user to login.

However they are treated, all issues should also be logged in the
journal (could be the user journal, but the system journal may be best
to allow admins to spot such issues being detected more easily?)

= Rationale =

1) All the problems above, although user-generated, are:

- trivially fixable.
- potentially very hard / impossible for a naeve user to debug and resolve.

2) By handling such errors, users won't have a bad experience of Linux
if they inadvertently perturb a critical file.

3) Users will not need to resort to a re-install (which I can imagine
some may have to given the current behaviour).

= Ideas for further checks =

- Check to ensure key files exist and if not, copy them in from /etc/skel/, etc.
- Check to ensure users home directory is owned by them and not root, etc.
- If the home partition / disk is 100% full, the script could logrotate and 
compress the contents of ~/.cache/ ?

= Notes =

You could argue that the session managers themselves should deal with
these issues. In some cases that may be a fair comment. However, by
having a single central check/fix script, the problems can be handled
centrally without the issue whereby some session managers tolerate
certain scenarios whereas others don't.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1800277

Title:
  "chmod u-w ~/.ICEauthority" breaks login

Status in gdm3 package in Ubuntu:
  New

Bug description:
  = Problem =

  It is too easy to make a system unusable.

  = Examples

  The following commands will all cause subsequent graphical logins to
  fail:

  == User is returned to login screen ==

  - chmod 400 ~/.ICEauthority
  - rm ~/.ICEauthority

  In this scenario, the user is returned to the login screen with no
  indication of what went wrong.

  == Session "dead" ==

  - chmod 444 ~/.cache
  - chmod 000 ~/.config
  - chmod 444 ~
  - chmod 000 ~

  In this scenario, the system just freezes: the cursor is unresponsive
  and users will be reaching for the power button.

  = Observation =

  These scenarios would all be caused by human error.

  However, clearly it is possible for the system to detect such issues
  and either alert the user to the problem or simply just fix the
  problem. This does not happen in Ubuntu 18.04 LTS though.

  = Idea =

  Have the display manager call a utility prior to executing the users
  preferred session. This utility -- which could be a simple shell
  script I think ("friendly-session-fixer" maybe? :) -- would do one or
  both of the following:

  - Perform checks for the issues outlined above warn the user
  graphically if any are found.

  - Fix any issues found to allow the user to login.

  However they are treated, all issues should also be logged in the
  journal (could be the user journal, but the system journal may be best
  to allow admins to spot such issues being detected more easily?)

  = Rationale =

  1) All the problems above, although user-generated, are:

  - trivially fixable.
  - potentially very hard / impossible for a naeve user to debug and resolve.

  2) By handling such errors, users won't have a bad experience of Linux
  if they inadvertently perturb a critical file.

  3) Users will not need to resort to a re-install (which I can imagine
  some may have to given the current behaviour).

  = Ideas for further checks =

  - Check to ensure key files exist and if not, copy them in from /etc/skel/, 
etc.
  - Check to ensure users home directory is owned by them and not root, etc.
  - If the home partition / disk is 100% full, the script could logrotate and 
compress the contents of ~/.cache/ ?

  =

[Desktop-packages] [Bug 1300235] Re: init (chromium-browser) crashed with SIGSEGV

2015-03-16 Thread James Hunt

** Package changed: upstart (Ubuntu) = chromium-browser (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1300235

Title:
  init (chromium-browser) crashed with SIGSEGV

Status in chromium-browser package in Ubuntu:
  Triaged

Bug description:
  none

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu1
  Uname: Linux 3.14.0-031400rc8-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  Date: Mon Mar 31 09:53:16 2014
  Disassembly: = 0x7fa2b65e94d7:   Cannot access memory at address 
0x7fa2b65e94d7
  ExecutablePath: /sbin/init
  InstallationDate: Installed on 2014-03-05 (25 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140305)
  ProcCmdline: /sbin/init
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.14.0-031400rc8-generic 
root=UUID=bef08855-3273-4d41-ac06-bad06bdd08a4 ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7fa2b65e94d7:Cannot access memory at address 
0x7fa2b65e94d7
   PC (0x7fa2b65e94d7) not located in a known VMA region (needed executable 
region)!
   Stack pointer not within stack segment
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  UserGroups:
   
  modified.conffile..etc.default.cups: [modified]
  mtime.conffile..etc.default.cups: 2014-03-11T13:23:34.740893

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

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

[Desktop-packages] [Bug 1385444] Re: lightm/upstart crash leaves 2 unity8 processes around

2014-10-24 Thread James Hunt

The oldest of the two unity8 proceses (pid 2640) has been SIGSTOP'ed.
Since unity8 uses SIGSTOP to indicate to upstart that it is ready, this
suggests that when lightdm died, the session init was killed somehow
before unity8 was ready (either on first start or respawn).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1385444

Title:
  lightm/upstart crash leaves 2 unity8 processes around

Status in “lightdm” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  lightm/upstart crash leaves 2 unity8 processes around

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

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

[Desktop-packages] [Bug 1385444] Re: lightm/upstart crash leaves 2 unity8 processes around

2014-10-24 Thread James Hunt

Daniel - please can you attach the existing /var/crash/_sbin_init* to
this bug. I appreciate they do not represent the current issue, but if
may have been a re-occurence of the problem which did generated the
crash files so I'd like to see those anyway.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1385444

Title:
  lightm/upstart crash leaves 2 unity8 processes around

Status in “lightdm” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  lightm/upstart crash leaves 2 unity8 processes around

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

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

[Desktop-packages] [Bug 1381075] Re: [ubuntu-touch] upstart should report applications that hit respawn limit to errors.ubuntu.com

2014-10-14 Thread James Hunt

The most appropriate way to do this would probably be to use apport to
check for respawn limit messages in:

- the system log, and
- the users $HOME/.xsession-errors file.

Even at the default upstart log priority of 'message', when a job
reaches the respawn limit, upstart will log a message to one of the logs
above like this:

init: foo respawning too fast, stopped

So apport, or some such utility could watch for these messages using
inotify and raise an informational error that would be visible on
errors.u.c.



** Also affects: apport (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1381075

Title:
  [ubuntu-touch] upstart should report applications that hit respawn
  limit to errors.ubuntu.com

Status in “apport” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  We have important system and session services that we rely on being
  running and functional.

  If such a component hits the upstart respawn limit for any reason, we
  should be able to get a report that something is seriously wrong.

  Inspiration for this bug as per the discussion in:
  https://bugs.launchpad.net/ubuntu/+source/indicator-
  network/+bug/1371320

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-30 Thread James Hunt

@elfy - is plymouth is still crashing for you?

$ sudo grep SEGV /var/log/syslog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Invalid
Status in “plymouth” package in Ubuntu:
  Fix Released

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

As discussed on irc, the problem seemed to be that the plymouth-ready
event was not being emitted since udev was not tagging a graphics device
with PRIMARY_DEVICE_FOR_DISPLAY, so it looked like the problem was
udev/kernel related.

According to jibel, if he enters the grub boot menu lightdm will
reliably start suggesting that grub is possibly setting up the
framebuffer which for some reason is not happening normally.

Looking at the log in #22, we can also see that plymouth itself is
crashing (SEGV). This may also suggest a problem with the graphics
setup.

I've just tried utopic-desktop-amd64.iso (20140923) under kvm and do not
see the issue reported.


** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  New

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

I have now recreated using utopic-desktop-amd64.iso (20140923) and
http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf to force
continuous reboots.

It appears that the problem only occurs if quiet splash is specified
since I ran 25 boots without those options and was unable to recreate
the issue.



[1] - http://people.canonical.com/~jhunt/upstart/conf/rebooter.conf

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

Note also that I do have PRIMARY_DEVICE_FOR_DISPLAY=1 in /var/log/udev.

Recreation is under kvm.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

It's looking like either quiet or more likely splash is the
triggering factor here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Triaged
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

After removing both 'quiet' and 'splash' options from
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, and running 'sudo
update-grub', I am no longer able to recreate the bug (over 100 boots on
a 64-bit kvm instance using utopic-desktop-amd64.iso (20140923)).

@elfy: can you provide details on how reliable this failure is for you?
Do you see it on every boot?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

205 boots and no problem with the 2 options removed.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1371651] Re: Daily does not boot into graphical interface after installation

2014-09-25 Thread James Hunt

@arges: can you try reproducing without quiet splash as that seems to
be the best lead we have so far.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1371651

Title:
  Daily does not boot into graphical interface after installation

Status in Light Display Manager:
  Invalid
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  used the daily iso 2015-09-19 i386
  ran installation on virtualbox 4.3.16

  after installation, the system won't boot into the graphical
  interface. instead, switching to vt1 and back to vt7 reveals the
  attached errors.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
  Uname: Linux 3.16.0-16-generic i686
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: i386
  Date: Fri Sep 19 17:09:17 2014
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de 
keyboard-configuration/layoutcode?=de
  InstallationDate: Installed on 2014-09-19 (0 days ago)
  InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140919)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1365535] Re: Desktop fails to start properly after 14.04 14.10

2014-09-04 Thread James Hunt

This sounds like a unity issue as I've seen no evidence of Upstart
misbehaving yet. That .xsession-errors log would be useful to have if
you can attach it though.

** Also affects: unity (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1365535

Title:
  Desktop fails to start properly after 14.04  14.10

Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  Yesterday I upgraded my laptop from 14.04 to 14.10  - after the
  upgrade, when I logged in, I saw Unity on the left with the icons I
  expected, and the bar across the top, however the time and date,
  network indicator icon, sound icon, etc were missing.. Clicking on any
  of the icons in Unity didn't load anything... Couldn't load the dash..
  Keyboard shortcuts such as ctrl+alt+t failed to load the terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: upstart 1.13.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
  Uname: Linux 3.16.0-12-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Thu Sep  4 10:30:43 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-06-29 (66 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: upstart 1.13.1
  UpstartRunningSystemVersion: init (upstart 1.13.1)
  mtime.conffile..etc.X11.Xsession.d.99upstart: 2014-08-28T00:30:06
  mtime.conffile..etc.cron.daily.upstart: 2014-08-28T00:35:25
  mtime.conffile..etc.upstart.xsessions: 2014-08-28T00:30:06

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

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

[Desktop-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch

2014-07-24 Thread James Hunt

** Changed in: upstart
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1235649

Title:
  uevent spam causes libdbus client code in session upstart to consume
  massive amounts of memory on Ubuntu Touch

Status in Touch Landing Plan:
  Fix Released
Status in Unity:
  Confirmed
Status in Upstart:
  Fix Released
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  Invalid
Status in “unity” source package in Saucy:
  Confirmed
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per 
minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

To manage notifications about this bug go to:
https://bugs.launchpad.net/landing-plan/+bug/1235649/+subscriptions

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

[Desktop-packages] [Bug 1344869] Re: simple-scan consumes 100% cpu and fills disk with logs attempting to scan wirelessly with Brother MFC-7860DW

2014-07-22 Thread James Hunt

Yes, I confirm that the issue is resolved with 3.13.4.2-0ubuntu1.

Not relevant to this bug, but I do notice that the scan speed is quit
slow using simple-scan. Comparing with xsane at the same resolution
(300dpi):

- xsane: 23 seconds
- simple-scan: 2 minutes.

Thanks very much for the fast turn-around!

** Changed in: simple-scan (Ubuntu)
   Status: Incomplete = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1344869

Title:
  simple-scan consumes 100% cpu and fills disk with logs attempting to
  scan wirelessly with Brother MFC-7860DW

Status in Simple Scan:
  Incomplete
Status in “simple-scan” package in Ubuntu:
  Fix Released

Bug description:
  Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
  scanner shows scanning but:

  - no image appears in simple-scan.
  - simple-scan consumes 100% CPU
  - the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk 
space is exhausted.

  This used to work perfectly and indeed the following provides an
  instant work-around:

  $ sudo apt-get install -y xsane  xsane

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.13.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 19 13:44:59 2014
  DriverPackageVersions:
   libsane 1.0.24-1.1ubuntu1
   libsane-extras N/A
   hplip 3.14.6-1
   hpoj N/A
  InstallationDate: Installed on 2014-04-11 (98 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1344869/+subscriptions

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

[Desktop-packages] [Bug 1344869] Re: simple-scan consumes 100% cpu and fills disk with logs attempting to scan wirelessly with Brother MFC-7860DW

2014-07-21 Thread James Hunt

Hi Robert,

Sorry to be vague, but I don't actually scan much so the last time I
recall doing it I was running trusty.

Yes, the proprietary brother drivers are required for wireless scanning
AIUI.

$ dpkg -l | grep brscan
ii  brscan-skey   0.2.4-1   
 amd64Brother Linux scanner S-KEY tool
ii  brscan4   0.4.2-3   
 amd64Brother Scanner Driver

Gah - I've just got an updated simple-scan package (3.13.4-0ubuntu1).
The behaviour with this version is different; simple-scan tellms me
there is no scanner connected, yet if I click scan, it clearly is
talking to the scanner (which I can hear whirring in the background).
So, although I no longer get ENOSPC, the scanned image never appears in
simple-scan. When I quit simple-scan, it seems a command is sent to the
scanner to reset since it sounds like it is resetting itself.

Updated simple-scan debug log attached.






** Attachment added: 'simple-scan --debug' log
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4158766/+files/simple-scan-21july2014.log.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1344869

Title:
  simple-scan consumes 100% cpu and fills disk with logs attempting to
  scan wirelessly with Brother MFC-7860DW

Status in Simple Scan:
  Incomplete
Status in “simple-scan” package in Ubuntu:
  Incomplete

Bug description:
  Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
  scanner shows scanning but:

  - no image appears in simple-scan.
  - simple-scan consumes 100% CPU
  - the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk 
space is exhausted.

  This used to work perfectly and indeed the following provides an
  instant work-around:

  $ sudo apt-get install -y xsane  xsane

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.13.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 19 13:44:59 2014
  DriverPackageVersions:
   libsane 1.0.24-1.1ubuntu1
   libsane-extras N/A
   hplip 3.14.6-1
   hpoj N/A
  InstallationDate: Installed on 2014-04-11 (98 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1344869/+subscriptions

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

[Desktop-packages] [Bug 1344869] Re: simple-scan consumes 100% cpu and fills disk with logs attempting to scan wirelessly with Brother MFC-7860DW

2014-07-21 Thread James Hunt

'ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl libsane.so.1
xsane' log from a successful wireless scan using xsane.


** Attachment added: ltrace -o /tmp/bug-1344869-ltrace-xsane.log -s 1024 -fl 
libsane.so.1 xsane
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4158767/+files/bug-1344869-ltrace-xsane.log.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1344869

Title:
  simple-scan consumes 100% cpu and fills disk with logs attempting to
  scan wirelessly with Brother MFC-7860DW

Status in Simple Scan:
  Incomplete
Status in “simple-scan” package in Ubuntu:
  Incomplete

Bug description:
  Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
  scanner shows scanning but:

  - no image appears in simple-scan.
  - simple-scan consumes 100% CPU
  - the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk 
space is exhausted.

  This used to work perfectly and indeed the following provides an
  instant work-around:

  $ sudo apt-get install -y xsane  xsane

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.13.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 19 13:44:59 2014
  DriverPackageVersions:
   libsane 1.0.24-1.1ubuntu1
   libsane-extras N/A
   hplip 3.14.6-1
   hpoj N/A
  InstallationDate: Installed on 2014-04-11 (98 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/1344869/+subscriptions

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

[Desktop-packages] [Bug 1345505] [NEW] lightdm leaks keystrokes to window behind greeter

2014-07-20 Thread James Hunt

*** This bug is a security vulnerability ***

Public security bug reported:

When my machine comes out of suspend, I am shown the lightdm greeter.
However, occasionally I am unable to enter my password since the
password box is not given focus. Clicking with the mouse in the password
box also doesn't help.

I've found that clicking the settings cog (top right) twice allows me to
regain control of the focus and enter my password.

Aside from the inability to enter my password in the password box, it
seems that simply typing my password (or in fact any text) results in
those keystrokes being passed to the full-screen window *behind* the
greeter. This should not be possible and is a security issue: imagine if
my full-screen console was connected to a remote shared session, or was
running an irc client, etc.).

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: lightdm 1.11.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 20 09:08:47 2014
InstallationDate: Installed on 2014-04-11 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: lightdm
UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)

** Affects: lightdm (Ubuntu)
 Importance: High
 Status: New


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

** Information type changed from Public to Public Security

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1345505

Title:
  lightdm leaks keystrokes to window behind greeter

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  When my machine comes out of suspend, I am shown the lightdm greeter.
  However, occasionally I am unable to enter my password since the
  password box is not given focus. Clicking with the mouse in the
  password box also doesn't help.

  I've found that clicking the settings cog (top right) twice allows me
  to regain control of the focus and enter my password.

  Aside from the inability to enter my password in the password box, it
  seems that simply typing my password (or in fact any text) results in
  those keystrokes being passed to the full-screen window *behind* the
  greeter. This should not be possible and is a security issue: imagine
  if my full-screen console was connected to a remote shared session, or
  was running an irc client, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: lightdm 1.11.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 20 09:08:47 2014
  InstallationDate: Installed on 2014-04-11 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)

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

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

[Desktop-packages] [Bug 1344869] [NEW] simple-scan consumes 100% cpu and fills disk with logs attempting to scan wirelessly with Brother MFC-7860DW

2014-07-19 Thread James Hunt

Public bug reported:

Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
scanner shows scanning but:

- no image appears in simple-scan.
- simple-scan consumes 100% CPU
- the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk space 
is exhausted.

This used to work perfectly and indeed the following provides an instant
work-around:

$ sudo apt-get install -y xsane  xsane

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: simple-scan 3.13.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
Uname: Linux 3.16.0-4-generic x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jul 19 13:44:59 2014
DriverPackageVersions:
 libsane 1.0.24-1.1ubuntu1
 libsane-extras N/A
 hplip 3.14.6-1
 hpoj N/A
InstallationDate: Installed on 2014-04-11 (98 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
MachineType: LENOVO 20AQCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: simple-scan
UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

** Affects: simple-scan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1344869

Title:
  simple-scan consumes 100% cpu and fills disk with logs attempting to
  scan wirelessly with Brother MFC-7860DW

Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
  scanner shows scanning but:

  - no image appears in simple-scan.
  - simple-scan consumes 100% CPU
  - the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk 
space is exhausted.

  This used to work perfectly and indeed the following provides an
  instant work-around:

  $ sudo apt-get install -y xsane  xsane

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.13.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 19 13:44:59 2014
  DriverPackageVersions:
   libsane 1.0.24-1.1ubuntu1
   libsane-extras N/A
   hplip 3.14.6-1
   hpoj N/A
  InstallationDate: Installed on 2014-04-11 (98 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1344869] Re: simple-scan consumes 100% cpu and fills disk with logs attempting to scan wirelessly with Brother MFC-7860DW

2014-07-19 Thread James Hunt

When simple-scan is spinning, the following entry is added to the log
repeatedly until ENOSPC:

[+15,29s] DEBUG: scanner.vala:1310: sane_read (0) - (SANE_STATUS_GOOD,
0)

Further details:

$ cat /proc/$(pidof simple-scan)/stack  

 
[] poll_schedule_timeout+0x49/0x70
[] do_sys_poll+0x422/0x540
[] SyS_poll+0x65/0x100
[] tracesys+0xe1/0xe6
[] 0x


** Attachment added: ~/.cache/simple-scan/simple-scan.log from startup to 
start of 100% CPU logging activity
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4156868/+files/bug-1344869.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1344869

Title:
  simple-scan consumes 100% cpu and fills disk with logs attempting to
  scan wirelessly with Brother MFC-7860DW

Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
  scanner shows scanning but:

  - no image appears in simple-scan.
  - simple-scan consumes 100% CPU
  - the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk 
space is exhausted.

  This used to work perfectly and indeed the following provides an
  instant work-around:

  $ sudo apt-get install -y xsane  xsane

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.13.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 19 13:44:59 2014
  DriverPackageVersions:
   libsane 1.0.24-1.1ubuntu1
   libsane-extras N/A
   hplip 3.14.6-1
   hpoj N/A
  InstallationDate: Installed on 2014-04-11 (98 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1344869] Re: simple-scan consumes 100% cpu and fills disk with logs attempting to scan wirelessly with Brother MFC-7860DW

2014-07-19 Thread James Hunt

** Attachment added: strace snapshot of simple-scan consuming 100% CPU
   
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1344869/+attachment/4156869/+files/bug-1344869-strace.txt.gz

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1344869

Title:
  simple-scan consumes 100% cpu and fills disk with logs attempting to
  scan wirelessly with Brother MFC-7860DW

Status in “simple-scan” package in Ubuntu:
  New

Bug description:
  Attempting to scan via wifi from a Brother MFC-7860 DW fails; the
  scanner shows scanning but:

  - no image appears in simple-scan.
  - simple-scan consumes 100% CPU
  - the ~/.cache/simple-scan/simple-scan.log grows indefinately until disk 
space is exhausted.

  This used to work perfectly and indeed the following provides an
  instant work-around:

  $ sudo apt-get install -y xsane  xsane

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: simple-scan 3.13.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5
  Uname: Linux 3.16.0-4-generic x86_64
  ApportVersion: 2.14.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jul 19 13:44:59 2014
  DriverPackageVersions:
   libsane 1.0.24-1.1ubuntu1
   libsane-extras N/A
   hplip 3.14.6-1
   hpoj N/A
  InstallationDate: Installed on 2014-04-11 (98 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  MachineType: LENOVO 20AQCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-4-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: simple-scan
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1321602] Re: chromium browser chews 100% CPU in epoll_wait()

2014-07-09 Thread James Hunt

Interestingly, the problem is also seen if chromium is restarted and one
of the tabs is http://translate.google.com - closing that tab resolves
the cpu usage issue, and subsequently opening a new tab and going to
http://translate.google.com does *not* manifest the problem.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1321602

Title:
  chromium browser chews 100% CPU in epoll_wait()

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  This happens frequently (I have a script that monitors CPU usage).

  $ top -b -n1 | head
  top - 07:44:06 up 30 min,  3 users,  load average: 1.35, 1.08, 0.82
  Tasks: 329 total,   2 running, 327 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 17.4 us,  1.6 sy,  0.4 ni, 80.1 id,  0.5 wa,  0.1 hi,  0.0 si,  0.0 
st
  KiB Mem:  12182444 total,  5215508 used,  6966936 free,   338356 buffers
  KiB Swap: 12455932 total,0 used, 12455932 free.  2614244 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  16165 james 20   0 1428628  72860  50624 R  95.5  0.6   3:11.69 
chromium-browse
   2908 james 20   0 1329964 485940  87724 S  12.7  4.0   2:17.25 firefox
  15993 james 20   0 3303180 257376 104592 S   6.4  2.1   0:18.28 
chromium-browse
  $ sudo cat /proc/16165/stack
  [] 0x
  $ sudo strace -fFv -s 1024 -p 16165
  Process 16165 attached with 9 threads
  [pid 16241] futex(0x7fe0ff7fdac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16182] futex(0x7fe0eac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16181] futex(0x7fe1279b7f88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16179] futex(0x7fe1279e7e68, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16178] futex(0x7fe1279d00f8, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16180] futex(0x7fe1279eeb88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16177] futex(0x7fe1279fa918, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16176] epoll_wait(3, 
  ^C

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5
  Uname: Linux 3.15.0-1-generic x86_64
  ApportVersion: 2.14.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 21 07:42:35 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-11 (39 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (12 days ago)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-05-06T16:47:55.748923

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

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

[Desktop-packages] [Bug 1335438] Re: unity-control-center crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

2014-07-01 Thread James Hunt

This happens every time the user attempts to access the unity settings.
Running from the command-line:

$ gnome-control-center

(unity-control-center:6424): Gtk-CRITICAL **:
gtk_radio_button_set_group: assertion '!g_slist_find (group,
radio_button)' failed

(unity-control-center:6424): Gtk-CRITICAL **:
gtk_radio_button_set_group: assertion '!g_slist_find (group,
radio_button)' failed

(unity-control-center:6424): Gtk-CRITICAL **:
gtk_radio_button_set_group: assertion '!g_slist_find (group,
radio_button)' failed

(unity-control-center:6424): unity-control-center-WARNING **: Could not load 
/usr/share/themes/Adwaita/index.theme: No such file or directory
Erreur de segmentation (core dumped)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1335438

Title:
  unity-control-center crashed with SIGSEGV in
  g_type_check_instance_is_fundamentally_a()

Status in “unity-control-center” package in Ubuntu:
  Confirmed

Bug description:
  Test case : System Settings  Appearances

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: unity-control-center 14.10.0+14.10.20140604-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 28 10:26:02 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-05-28 (30 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520)
  ProcCmdline: unity-control-center
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdbe10bfab7 
g_type_check_instance_is_fundamentally_a+39:  movzbl 0x14(%rax),%edx
   PC (0x7fdbe10bfab7) ok
   source 0x14(%rax) (0x0014) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   g_type_check_instance_is_fundamentally_a (type_instance=0x2ddb000, 
fundamental_type=80) at /build/buildd/glib2.0-2.41.1/./gobject/gtype.c:3978
   g_object_unref (_object=0x2ddb000) at 
/build/buildd/glib2.0-2.41.1/./gobject/gobject.c:3026
   ?? () from 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libappearance.so
   g_type_create_instance (type=optimized out) at 
/build/buildd/glib2.0-2.41.1/./gobject/gtype.c:1866
   g_object_new_internal (class=class@entry=0x2bec760, 
params=params@entry=0x7fff9d15f680, n_params=3) at 
/build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1741
  Title: unity-control-center crashed with SIGSEGV in 
g_type_check_instance_is_fundamentally_a()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu6

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

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

[Desktop-packages] [Bug 1334204] Re: ogg123 crashes after playing sound file

2014-06-26 Thread James Hunt

Yes.

** Changed in: vorbis-tools (Ubuntu)
   Status: Incomplete = New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vorbis-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1334204

Title:
  ogg123 crashes after playing sound file

Status in “vorbis-tools” package in Ubuntu:
  New

Bug description:
  $ gdb --args `which ogg123` redalert.ogg
  GNU gdb (Ubuntu 7.7.1-0ubuntu3) 7.7.1
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as x86_64-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from /usr/bin/ogg123...(no debugging symbols found)...done.
  (gdb) r
  Starting program: /usr/bin/ogg123 redalert.ogg
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

  Audio Device:   Advanced Linux Sound Architecture (ALSA) output

  [New Thread 0x7fffecd4d700 (LWP 10744)]
  Playing: redalert.ogg
  Ogg Vorbis stream: 1 channel, 22050 Hz
  [New Thread 0x7fffe3ffe700 (LWP 10745)]
  [Thread 0x7fffecd4d700 (LWP 10744) exited]3.0 kbps)  Output Buffer   0.0% 
(EOS) 

  Program received signal SIGSEGV, Segmentation fault.
  __lll_unlock_elision (lock=0x613c40, private=0) at 
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
  29  ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or 
directory.
  (gdb) bt full
  #0  __lll_unlock_elision (lock=0x613c40, private=0) at 
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
  No locals.
  #1  0x0040895a in ?? ()
  No symbol table info available.
  #2  0x00403bda in ?? ()
  No symbol table info available.
  #3  0x7661fec5 in __libc_start_main (main=0x403860, argc=2, 
argv=0x7fffda28, init=optimized out, fini=optimized out, 
rtld_fini=optimized out, stack_end=0x7fffda18) at libc-start.c:287
  result = optimized out
  unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4502378785248176378, 
4209892, 140737488345632, 0, 0, -4502378786266224390, -4502397425389737734}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x40dd40, 
0x7fffda28}, data = {prev = 0x0, cleanup = 0x0, canceltype 
= 4250944}}}
  not_first_call = optimized out
  #4  0x00403d0d in ?? ()
  No symbol table info available.
  #5  0x7fffda18 in ?? ()
  No symbol table info available.
  #6  0x001c in ?? ()
  No symbol table info available.
  #7  0x0002 in ?? ()
  No symbol table info available.
  #8  0x7fffdece in ?? ()
  No symbol table info available.
  #9  0x7fffdede in ?? ()
  No symbol table info available.
  #10 0x in ?? ()
  No symbol table info available.
  (gdb) 

  
  Every file I tried experiences the same crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: vorbis-tools 1.4.0-1ubuntu3
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:07:13 2014
  InstallationDate: Installed on 2014-04-11 (74 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: vorbis-tools
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (47 days ago)

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

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

[Desktop-packages] [Bug 1334204] [NEW] ogg123 crashes after playing sound file

2014-06-25 Thread James Hunt

Public bug reported:

$ gdb --args `which ogg123` redalert.ogg
GNU gdb (Ubuntu 7.7.1-0ubuntu3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from /usr/bin/ogg123...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/ogg123 redalert.ogg
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

Audio Device:   Advanced Linux Sound Architecture (ALSA) output

[New Thread 0x7fffecd4d700 (LWP 10744)]
Playing: redalert.ogg
Ogg Vorbis stream: 1 channel, 22050 Hz
[New Thread 0x7fffe3ffe700 (LWP 10745)]
[Thread 0x7fffecd4d700 (LWP 10744) exited]3.0 kbps)  Output Buffer   0.0% (EOS) 

Program received signal SIGSEGV, Segmentation fault.
__lll_unlock_elision (lock=0x613c40, private=0) at 
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
29  ../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c: No such file or 
directory.
(gdb) bt full
#0  __lll_unlock_elision (lock=0x613c40, private=0) at 
../nptl/sysdeps/unix/sysv/linux/x86/elision-unlock.c:29
No locals.
#1  0x0040895a in ?? ()
No symbol table info available.
#2  0x00403bda in ?? ()
No symbol table info available.
#3  0x7661fec5 in __libc_start_main (main=0x403860, argc=2, 
argv=0x7fffda28, init=optimized out, fini=optimized out, 
rtld_fini=optimized out, stack_end=0x7fffda18) at libc-start.c:287
result = optimized out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 4502378785248176378, 
4209892, 140737488345632, 0, 0, -4502378786266224390, -4502397425389737734}, 
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x40dd40, 
  0x7fffda28}, data = {prev = 0x0, cleanup = 0x0, canceltype = 
4250944}}}
not_first_call = optimized out
#4  0x00403d0d in ?? ()
No symbol table info available.
#5  0x7fffda18 in ?? ()
No symbol table info available.
#6  0x001c in ?? ()
No symbol table info available.
#7  0x0002 in ?? ()
No symbol table info available.
#8  0x7fffdece in ?? ()
No symbol table info available.
#9  0x7fffdede in ?? ()
No symbol table info available.
#10 0x in ?? ()
No symbol table info available.
(gdb) 


Every file I tried experiences the same crash.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: vorbis-tools 1.4.0-1ubuntu3
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 25 11:07:13 2014
InstallationDate: Installed on 2014-04-11 (74 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: vorbis-tools
UpgradeStatus: Upgraded to utopic on 2014-05-08 (47 days ago)

** Affects: vorbis-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vorbis-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1334204

Title:
  ogg123 crashes after playing sound file

Status in “vorbis-tools” package in Ubuntu:
  New

Bug description:
  $ gdb --args `which ogg123` redalert.ogg
  GNU gdb (Ubuntu 7.7.1-0ubuntu3) 7.7.1
  Copyright (C) 2014 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as x86_64-linux-gnu.
  Type show configuration for configuration details.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/.
  Find the GDB manual and other documentation resources online at:
  http://www.gnu.org/software/gdb/documentation/.
  For help, type help.
  Type apropos word to search for commands related to word...
  Reading symbols from /usr/bin/ogg123...(no debugging symbols found)...done.
  (gdb) r
  Starting program: /usr/bin/ogg123 redalert.ogg
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

  Audio Device:   Advanced Linux Sound Architecture (ALSA) output

  [New Thread 0x7fffecd4d700 (LWP 10744)]
  Playing: redalert.ogg
  Ogg

[Desktop-packages] [Bug 1330387] [NEW] 'pactl load-module module-native-protocol-unix' tries to autoload module-esound-protocol-unix which now fails

2014-06-16 Thread James Hunt

Public bug reported:

Running the following as part of an lxc unprivileged container setup
(see [1]) used to work fine:

pactl load-module module-native-protocol-unix auth-anonymous=1
socket=$PULSE_PATH

However, as of today, this fails. Looking in syslog I see:

___

Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] socket-server.c: bind(): 
Adresse déjà utilisée
Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] module.c: Failed to load 
module module-esound-protocol-unix (argument: ): initialization failed.
Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] main.c: Module load 
failed.
Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] main.c: Échec lors de 
l'initialisation du démon
Jun 16 09:30:33 faire pulseaudio[25349]: [pulseaudio] main.c: Échec lors du 
démarrage du démon.
Jun 16 09:30:34 faire pulseaudio[25365]: [pulseaudio] socket-server.c: bind(): 
Adresse déjà utilisée
___

The solution for me as to remove the esound compat module:

$ sudo apt-get remove pulseaudio-esound-compat


[1] - https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: pulseaudio 1:4.0-0ubuntu12
ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
Uname: Linux 3.15.0-6-generic x86_64
ApportVersion: 2.14.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Jun 16 09:33:38 2014
InstallationDate: Installed on 2014-04-11 (65 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to utopic on 2014-05-08 (38 days ago)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1330387

Title:
  'pactl load-module module-native-protocol-unix' tries to autoload
  module-esound-protocol-unix which now fails

Status in “pulseaudio” package in Ubuntu:
  New

Bug description:
  Running the following as part of an lxc unprivileged container setup
  (see [1]) used to work fine:

  pactl load-module module-native-protocol-unix auth-anonymous=1
  socket=$PULSE_PATH

  However, as of today, this fails. Looking in syslog I see:

  ___

  Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] socket-server.c: 
bind(): Adresse déjà utilisée
  Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] module.c: Failed to 
load module module-esound-protocol-unix (argument: ): initialization failed.
  Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] main.c: Module load 
failed.
  Jun 16 09:30:33 faire pulseaudio[25352]: [pulseaudio] main.c: Échec lors de 
l'initialisation du démon
  Jun 16 09:30:33 faire pulseaudio[25349]: [pulseaudio] main.c: Échec lors du 
démarrage du démon.
  Jun 16 09:30:34 faire pulseaudio[25365]: [pulseaudio] socket-server.c: 
bind(): Adresse déjà utilisée
  ___

  The solution for me as to remove the esound compat module:

  $ sudo apt-get remove pulseaudio-esound-compat

  
  [1] - https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: pulseaudio 1:4.0-0ubuntu12
  ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0
  Uname: Linux 3.15.0-6-generic x86_64
  ApportVersion: 2.14.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 16 09:33:38 2014
  InstallationDate: Installed on 2014-04-11 (65 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (38 days ago)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Desktop-packages] [Bug 1321602] [NEW] chromium browser chews 100% CPU in epoll_wait()

2014-05-21 Thread James Hunt

Public bug reported:

This happens frequently (I have a script that monitors CPU usage).

$ top -b -n1 | head
top - 07:44:06 up 30 min,  3 users,  load average: 1.35, 1.08, 0.82
Tasks: 329 total,   2 running, 327 sleeping,   0 stopped,   0 zombie
%Cpu(s): 17.4 us,  1.6 sy,  0.4 ni, 80.1 id,  0.5 wa,  0.1 hi,  0.0 si,  0.0 st
KiB Mem:  12182444 total,  5215508 used,  6966936 free,   338356 buffers
KiB Swap: 12455932 total,0 used, 12455932 free.  2614244 cached Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
16165 james 20   0 1428628  72860  50624 R  95.5  0.6   3:11.69 
chromium-browse
 2908 james 20   0 1329964 485940  87724 S  12.7  4.0   2:17.25 firefox
15993 james 20   0 3303180 257376 104592 S   6.4  2.1   0:18.28 
chromium-browse
$ sudo cat /proc/16165/stack
[] 0x
$ sudo strace -fFv -s 1024 -p 16165
Process 16165 attached with 9 threads
[pid 16241] futex(0x7fe0ff7fdac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
[pid 16182] futex(0x7fe0eac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
[pid 16181] futex(0x7fe1279b7f88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
[pid 16179] futex(0x7fe1279e7e68, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
[pid 16178] futex(0x7fe1279d00f8, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
[pid 16180] futex(0x7fe1279eeb88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
[pid 16177] futex(0x7fe1279fa918, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
[pid 16176] epoll_wait(3, 
^C

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: chromium-browser 34.0.1847.116-0ubuntu2
ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5
Uname: Linux 3.15.0-1-generic x86_64
ApportVersion: 2.14.2-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 21 07:42:35 2014
Desktop-Session:
 DESKTOP_SESSION = ubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
InstallationDate: Installed on 2014-04-11 (39 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to utopic on 2014-05-08 (12 days ago)
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-05-06T16:47:55.748923

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug utopic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1321602

Title:
  chromium browser chews 100% CPU in epoll_wait()

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  This happens frequently (I have a script that monitors CPU usage).

  $ top -b -n1 | head
  top - 07:44:06 up 30 min,  3 users,  load average: 1.35, 1.08, 0.82
  Tasks: 329 total,   2 running, 327 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 17.4 us,  1.6 sy,  0.4 ni, 80.1 id,  0.5 wa,  0.1 hi,  0.0 si,  0.0 
st
  KiB Mem:  12182444 total,  5215508 used,  6966936 free,   338356 buffers
  KiB Swap: 12455932 total,0 used, 12455932 free.  2614244 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  16165 james 20   0 1428628  72860  50624 R  95.5  0.6   3:11.69 
chromium-browse
   2908 james 20   0 1329964 485940  87724 S  12.7  4.0   2:17.25 firefox
  15993 james 20   0 3303180 257376 104592 S   6.4  2.1   0:18.28 
chromium-browse
  $ sudo cat /proc/16165/stack
  [] 0x
  $ sudo strace -fFv -s 1024 -p 16165
  Process 16165 attached with 9 threads
  [pid 16241] futex(0x7fe0ff7fdac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16182] futex(0x7fe0eac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16181] futex(0x7fe1279b7f88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16179] futex(0x7fe1279e7e68, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16178] futex(0x7fe1279d00f8, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16180] futex(0x7fe1279eeb88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16177] futex(0x7fe1279fa918, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16176] epoll_wait(3, 
  ^C

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser

[Desktop-packages] [Bug 1321602] Re: chromium browser chews 100% CPU in epoll_wait()

2014-05-21 Thread James Hunt

Looks like this might be being caused by flashplugin. After closing a
few tabs the problem is no longer recreatable.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1321602

Title:
  chromium browser chews 100% CPU in epoll_wait()

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  This happens frequently (I have a script that monitors CPU usage).

  $ top -b -n1 | head
  top - 07:44:06 up 30 min,  3 users,  load average: 1.35, 1.08, 0.82
  Tasks: 329 total,   2 running, 327 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 17.4 us,  1.6 sy,  0.4 ni, 80.1 id,  0.5 wa,  0.1 hi,  0.0 si,  0.0 
st
  KiB Mem:  12182444 total,  5215508 used,  6966936 free,   338356 buffers
  KiB Swap: 12455932 total,0 used, 12455932 free.  2614244 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  16165 james 20   0 1428628  72860  50624 R  95.5  0.6   3:11.69 
chromium-browse
   2908 james 20   0 1329964 485940  87724 S  12.7  4.0   2:17.25 firefox
  15993 james 20   0 3303180 257376 104592 S   6.4  2.1   0:18.28 
chromium-browse
  $ sudo cat /proc/16165/stack
  [] 0x
  $ sudo strace -fFv -s 1024 -p 16165
  Process 16165 attached with 9 threads
  [pid 16241] futex(0x7fe0ff7fdac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16182] futex(0x7fe0eac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16181] futex(0x7fe1279b7f88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16179] futex(0x7fe1279e7e68, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16178] futex(0x7fe1279d00f8, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16180] futex(0x7fe1279eeb88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16177] futex(0x7fe1279fa918, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16176] epoll_wait(3, 
  ^C

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5
  Uname: Linux 3.15.0-1-generic x86_64
  ApportVersion: 2.14.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 21 07:42:35 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-11 (39 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (12 days ago)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-05-06T16:47:55.748923

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

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

[Desktop-packages] [Bug 1321602] Re: chromium browser chews 100% CPU in epoll_wait()

2014-05-21 Thread James Hunt

After performing a few tests, the problem seems to be that if a tab
using youtube's html5 player exists at browser start, chromium will spin
@ 100% cpu. Closing that tab makes the cpu usage drop to normal levels.

What is odd is that if no youtube html5 tab exists at startup and I then
create a new tab and visit the same URL, the problem is not observed, so
it seems it might be a bug related to auto-playing html5 embedded media?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1321602

Title:
  chromium browser chews 100% CPU in epoll_wait()

Status in “chromium-browser” package in Ubuntu:
  New

Bug description:
  This happens frequently (I have a script that monitors CPU usage).

  $ top -b -n1 | head
  top - 07:44:06 up 30 min,  3 users,  load average: 1.35, 1.08, 0.82
  Tasks: 329 total,   2 running, 327 sleeping,   0 stopped,   0 zombie
  %Cpu(s): 17.4 us,  1.6 sy,  0.4 ni, 80.1 id,  0.5 wa,  0.1 hi,  0.0 si,  0.0 
st
  KiB Mem:  12182444 total,  5215508 used,  6966936 free,   338356 buffers
  KiB Swap: 12455932 total,0 used, 12455932 free.  2614244 cached Mem

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
  16165 james 20   0 1428628  72860  50624 R  95.5  0.6   3:11.69 
chromium-browse
   2908 james 20   0 1329964 485940  87724 S  12.7  4.0   2:17.25 firefox
  15993 james 20   0 3303180 257376 104592 S   6.4  2.1   0:18.28 
chromium-browse
  $ sudo cat /proc/16165/stack
  [] 0x
  $ sudo strace -fFv -s 1024 -p 16165
  Process 16165 attached with 9 threads
  [pid 16241] futex(0x7fe0ff7fdac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16182] futex(0x7fe0eac4, FUTEX_WAIT_PRIVATE, 1, NULL unfinished ...
  [pid 16181] futex(0x7fe1279b7f88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16179] futex(0x7fe1279e7e68, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16178] futex(0x7fe1279d00f8, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16180] futex(0x7fe1279eeb88, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16177] futex(0x7fe1279fa918, FUTEX_WAIT_PRIVATE, 0, NULL unfinished ...
  [pid 16176] epoll_wait(3, 
  ^C

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5
  Uname: Linux 3.15.0-1-generic x86_64
  ApportVersion: 2.14.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 21 07:42:35 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-11 (39 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to utopic on 2014-05-08 (12 days ago)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-05-06T16:47:55.748923

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

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

[Desktop-packages] [Bug 1315281] [NEW] skype occasionally makes constant crackling / humming sound until restarted or pulseaudio killed

2014-05-02 Thread James Hunt

Public bug reported:

Occasionally my Lenovo t440s starts to make a constant crackling /
humming sound. This doesn't stop sound from being played, but if no
sound is playing, the noise persists.

As it's a new laptop, I thought it might be a hardware issue. It almost
sounds like a bad earth connection.

However, the culprit seems to be pulseaudio since killing it and
restarting solves the problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  james  2843 F pulseaudio
 /dev/snd/pcmC1D0p:   james  2843 F...m pulseaudio
 /dev/snd/controlC0:  james  2843 F pulseaudio
CurrentDesktop: Unity
Date: Fri May  2 09:09:37 2014
InstallationDate: Installed on 2014-04-11 (20 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/10/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET71WW (2.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98405 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1315281

Title:
  skype occasionally makes constant crackling / humming sound until
  restarted or pulseaudio killed

Status in “skype” package in Ubuntu:
  New

Bug description:
  Occasionally my Lenovo t440s starts to make a constant crackling /
  humming sound. This doesn't stop sound from being played, but if no
  sound is playing, the noise persists.

  As it's a new laptop, I thought it might be a hardware issue. It
  almost sounds like a bad earth connection.

  However, the culprit seems to be pulseaudio since killing it and
  restarting solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  2843 F pulseaudio
   /dev/snd/pcmC1D0p:   james  2843 F...m pulseaudio
   /dev/snd/controlC0:  james  2843 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  2 09:09:37 2014
  InstallationDate: Installed on 2014-04-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1315281] Re: pulseaudio occasionally makes constant crackling / humming sound until killed

2014-05-02 Thread James Hunt

Note that the noise is heard when the laptop is connected on AC and on
battery alone.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1315281

Title:
  skype occasionally makes constant crackling / humming sound until
  restarted or pulseaudio killed

Status in “skype” package in Ubuntu:
  New

Bug description:
  Occasionally my Lenovo t440s starts to make a constant crackling /
  humming sound. This doesn't stop sound from being played, but if no
  sound is playing, the noise persists.

  As it's a new laptop, I thought it might be a hardware issue. It
  almost sounds like a bad earth connection.

  However, the culprit seems to be pulseaudio since killing it and
  restarting solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  2843 F pulseaudio
   /dev/snd/pcmC1D0p:   james  2843 F...m pulseaudio
   /dev/snd/controlC0:  james  2843 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  2 09:09:37 2014
  InstallationDate: Installed on 2014-04-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1315281] Re: pulseaudio occasionally makes constant crackling / humming sound until killed

2014-05-02 Thread James Hunt

diwic has identified the problem to be skype rather than pulse itself.

** Package changed: pulseaudio (Ubuntu) = skype (Ubuntu)

** Summary changed:

- pulseaudio occasionally makes constant crackling / humming sound until killed
+ skype occasionally makes constant crackling / humming sound until restarted 
or pulseaudio killed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1315281

Title:
  skype occasionally makes constant crackling / humming sound until
  restarted or pulseaudio killed

Status in “skype” package in Ubuntu:
  New

Bug description:
  Occasionally my Lenovo t440s starts to make a constant crackling /
  humming sound. This doesn't stop sound from being played, but if no
  sound is playing, the noise persists.

  As it's a new laptop, I thought it might be a hardware issue. It
  almost sounds like a bad earth connection.

  However, the culprit seems to be pulseaudio since killing it and
  restarting solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  2843 F pulseaudio
   /dev/snd/pcmC1D0p:   james  2843 F...m pulseaudio
   /dev/snd/controlC0:  james  2843 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  2 09:09:37 2014
  InstallationDate: Installed on 2014-04-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1315281] Re: pulseaudio occasionally makes constant crackling / humming sound until killed

2014-05-02 Thread James Hunt

Problem persists with all peripherals unplugged.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1315281

Title:
  skype occasionally makes constant crackling / humming sound until
  restarted or pulseaudio killed

Status in “skype” package in Ubuntu:
  New

Bug description:
  Occasionally my Lenovo t440s starts to make a constant crackling /
  humming sound. This doesn't stop sound from being played, but if no
  sound is playing, the noise persists.

  As it's a new laptop, I thought it might be a hardware issue. It
  almost sounds like a bad earth connection.

  However, the culprit seems to be pulseaudio since killing it and
  restarting solves the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  james  2843 F pulseaudio
   /dev/snd/pcmC1D0p:   james  2843 F...m pulseaudio
   /dev/snd/controlC0:  james  2843 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  2 09:09:37 2014
  InstallationDate: Installed on 2014-04-11 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET71WW (2.21 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AQCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGJET71WW(2.21):bd02/10/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20AQCTO1WW
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1311488] Re: Missing letters

2014-04-24 Thread James Hunt

Sounds like bug 861268.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1311488

Title:
  Missing letters

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  New

Bug description:
  The desktop  tabs  menus have letters missing.,  Example: Sys em Se
  ings  or Repor ing Bugs

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl 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  304.117  Tue Nov 26 21:25:36 
PST 2013
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 22 23:56:49 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
   nvidia-304, 304.117, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C51 [GeForce Go 6150] [10de:0244] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company Presario V6133CL [103c:30b7]
  InstallationDate: Installed on 2014-04-22 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  Lsusb:
   Bus 001 Device 002: ID 064e:a110 Suyin Corp. HP Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard HP Pavilion dv9000 (EZ459UA#ABA)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=98ef5c50-008d-4f32-970b-2d601469882c ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.3D
  dmi.board.name: 30B9
  dmi.board.vendor: Quanta
  dmi.board.version: 65.2B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.3D:bd11/22/2007:svnHewlett-Packard:pnHPPaviliondv9000(EZ459UA#ABA):pvrRev1:rvnQuanta:rn30B9:rvr65.2B:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv9000 (EZ459UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Apr 22 22:27:55 2014
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1311488/+subscriptions

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

[Desktop-packages] [Bug 1295639] [NEW] move to workspace loses track of window entirely

2014-03-21 Thread James Hunt

Public bug reported:

Moving a window to another workspace using the context menu options
Move to Workspace right or Move to Another Workspace causes unity to
lose track of the window entirely - it disappears never to return.

Note: the processes associated with the windows *are* still running as
shown by xlsclients.

Moving the windows manually to another workspace (by shifting the window
almost off the screen to the right or bottom, then changing to the
appropriate workspace and pulling the half-obscured window into that
workspace) works.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140318-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
Uname: Linux 3.13.0-18-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Fri Mar 21 11:36:12 2014
InstallationDate: Installed on 2010-10-21 (1247 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2013-11-01 (139 days ago)

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


** Tags: apport-bug i386 trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1295639

Title:
  move to workspace loses track of window entirely

Status in “unity” package in Ubuntu:
  New

Bug description:
  Moving a window to another workspace using the context menu options
  Move to Workspace right or Move to Another Workspace causes unity
  to lose track of the window entirely - it disappears never to return.

  Note: the processes associated with the windows *are* still running as
  shown by xlsclients.

  Moving the windows manually to another workspace (by shifting the
  window almost off the screen to the right or bottom, then changing to
  the appropriate workspace and pulling the half-obscured window into
  that workspace) works.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140318-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Fri Mar 21 11:36:12 2014
  InstallationDate: Installed on 2010-10-21 (1247 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (139 days ago)

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

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

[Desktop-packages] [Bug 1288667] [NEW] No notification when VPN connection disconnected

2014-03-06 Thread James Hunt

Public bug reported:

When a VPN connection has been created, a notification appears stating:

VPN Login Message

VPN connection has been successfully established.

However, the converse is not true; disconnecting from the VPN does not
result in a message like this:

VPN Logout Message

VPN connection has been successfully stopped.

Note that if the network is lost, a message does pop up fleetingly
(rather too briefly) stating something like VPN Connection failed.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1288667

Title:
  No notification when VPN connection disconnected

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  When a VPN connection has been created, a notification appears
  stating:

  VPN Login Message

  VPN connection has been successfully established.

  However, the converse is not true; disconnecting from the VPN does not
  result in a message like this:

  VPN Logout Message

  VPN connection has been successfully stopped.

  Note that if the network is lost, a message does pop up fleetingly
  (rather too briefly) stating something like VPN Connection failed.

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

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

[Desktop-packages] [Bug 1288667] Re: No notification when VPN connection disconnected

2014-03-06 Thread James Hunt

To be clear, I am suggesting we have a notification appear when the user
manually disconnects the VPN at the point the connection is brought
down.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1288667

Title:
  No notification when VPN connection disconnected

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  When a VPN connection has been created, a notification appears
  stating:

  VPN Login Message

  VPN connection has been successfully established.

  However, the converse is not true; disconnecting from the VPN does not
  result in a message like this:

  VPN Logout Message

  VPN connection has been successfully stopped.

  Note that if the network is lost, a message does pop up fleetingly
  (rather too briefly) stating something like VPN Connection failed.

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

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

[Desktop-packages] [Bug 1286698] Re: Logout, Restart Shutdown does not work

2014-03-05 Thread James Hunt

Thank you for reporting this bug. However, please do not report the same
bug three times :-)

** Package changed: upstart (Ubuntu) = gnome-session (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1286698

Title:
  Logout, Restart  Shutdown does not work

Status in “gnome-session” package in Ubuntu:
  Incomplete

Bug description:
  None of the options from the menu works

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Sun Mar  2 06:45:56 2014
  InstallationDate: Installed on 2014-03-01 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140224)
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.11)
  UpstartRunningSystemVersion: init (upstart 1.11)
  upstart.upstart-event-bridge.log:
   upstart-event-bridge: Connection is closed
   process 1206: arguments to dbus_pending_call_unref() were incorrect, 
assertion pending != NULL failed in file ../../dbus/dbus-pending-call.c line 
608.
   This is normally a bug in some application using the D-Bus library.
   upstart-event-bridge: Disconnected from Upstart

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

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

[Desktop-packages] [Bug 1288152] [NEW] keyboard shortcuts overlay does not specify super+L for lockscreen

2014-03-05 Thread James Hunt

Public bug reported:

(Long) Pressing the super (aka windows) key displays the Keyboard
Shortcuts overlay. However, this summary does not show that Super+L is
now a shortcut for locking the screen.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140303-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
Uname: Linux 3.13.0-14-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CurrentDesktop: Unity
Date: Wed Mar  5 09:55:53 2014
InstallationDate: Installed on 2010-10-21 (1231 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2013-11-01 (123 days ago)

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


** Tags: apport-bug i386 trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1288152

Title:
  keyboard shortcuts overlay does not specify super+L for lockscreen

Status in “unity” package in Ubuntu:
  New

Bug description:
  (Long) Pressing the super (aka windows) key displays the Keyboard
  Shortcuts overlay. However, this summary does not show that Super+L
  is now a shortcut for locking the screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140303-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5
  Uname: Linux 3.13.0-14-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CurrentDesktop: Unity
  Date: Wed Mar  5 09:55:53 2014
  InstallationDate: Installed on 2010-10-21 (1231 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: unity
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (123 days ago)

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

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

[Desktop-packages] [Bug 1285726] Re: Wired VPN connection icon unclear

2014-02-27 Thread James Hunt

I don't know if the padlock is actually being overlayed onto the
existing connection-type image, but I'd prefer to see an icon like the
attached. In other words, invert the 2 arrows for a wired connection and
make the right-hand arrow stem shorter, allowing space for a padlock
bottom-right.

** Attachment added: proposed design for wired VPN connection icon
   
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1285726/+attachment/3999552/+files/vpn.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1285726

Title:
  Wired VPN connection icon unclear

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  The current nm-applet icon that is shown for a wired VPN connection is
  very unclear - overlaying a padlock onto the existing connection-type
  icon works fine for the usual wifi icon, but with a wired connection
  the padlock merges into the down arrow and looks like screen
  corruption.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Feb 27 15:17:00 2014
  InstallationDate: Installed on 2010-10-21 (1225 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (117 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1285726] [NEW] Wired VPN connection icon unclear

2014-02-27 Thread James Hunt

Public bug reported:

The current nm-applet icon that is shown for a wired VPN connection is
very unclear - overlaying a padlock onto the existing connection-type
icon works fine for the usual wifi icon, but with a wired connection the
padlock merges into the down arrow and looks like screen corruption.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager-gnome 0.9.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu5
Architecture: i386
CurrentDesktop: Unity
Date: Thu Feb 27 15:17:00 2014
InstallationDate: Installed on 2010-10-21 (1225 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to trusty on 2013-11-01 (117 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
 wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
 eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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


** Tags: apport-bug i386 trusty

** Attachment added: nm-vpn-on-wired-connection.png
   
https://bugs.launchpad.net/bugs/1285726/+attachment/3999529/+files/nm-vpn-on-wired-connection.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1285726

Title:
  Wired VPN connection icon unclear

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  The current nm-applet icon that is shown for a wired VPN connection is
  very unclear - overlaying a padlock onto the existing connection-type
  icon works fine for the usual wifi icon, but with a wired connection
  the padlock merges into the down arrow and looks like screen
  corruption.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager-gnome 0.9.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Feb 27 15:17:00 2014
  InstallationDate: Installed on 2010-10-21 (1225 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager-applet
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (117 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/2  
   wlan1  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1284164] Re: ~/.cache/upstart grows enormous

2014-02-24 Thread James Hunt

This isn't really a bug with Upstart since it appears the problem is
that bamfdaemon is spamming dbus somehow. Upstart is simply logging the
output.

That said, there is an outstanding merge proposal to have the session
logrotate job run periodically which would have avoided so much disk
space being taken (although it would also potentially have caused the
bamfdaemon problem from being noticed):

https://code.launchpad.net/~jamesodhunt/ubuntu/trusty/upstart/periodic-
logrotate

Once approved (and an FFE raised if necessary), this will resolve the
Upstart aspect of this issue.


** Also affects: dbus (Ubuntu)
   Importance: Undecided
   Status: New

** Package changed: dbus (Ubuntu) = bamf (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1284164

Title:
  ~/.cache/upstart grows enormous

Status in “bamf” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  
  $ du -hs ~/.cache/upstart/
  454M  /home/smoser/.cache/upstart/

  $ ls -altr ~/.cache/upstart/ | egrep [0-9]{6,} 
  -rw-r-  1 smoser smoser  14105029 Feb 10 08:53 gnome-session.log
  -rw-r-  1 smoser smoser   3112634 Feb 23 23:09 gnome-settings-daemon.log
  -rw-r-  1 smoser smoser   1179973 Feb 24 08:29 indicator-application.log
  -rw-r-  1 smoser smoser   4129955 Feb 24 09:31 hud.log
  -rw-r-  1 smoser smoser  18668572 Feb 24 10:13 unity-panel-service.log
  -rw-r-  1 smoser smoser 429582393 Feb 24 10:13 dbus.log
  -rw-r-  1 smoser smoser   3708061 Feb 24 10:13 gnome-session-ubuntu.log

  $ uptime
   10:15:17 up 14 days,  1:20, 24 users,  load average: 1.09, 0.95, 1.33

  I suspect my desktop has been logged in and being used for about 14
  days, but clearly not longer.  Also, it has gone through 'apt-get
  dist-upgrade' in that time (those are possible excuses for the above).

  However, I have 450M of data in a ~/.cache/upstart and 430M in a
  single file.

  I'll attach the log shortly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Feb 24 10:11:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-19 (859 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-05-20 (280 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.11)
  UpstartRunningSystemVersion: init (upstart 1.11)

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

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

[Desktop-packages] [Bug 1284164] Re: ~/.cache/upstart grows enormous

2014-02-24 Thread James Hunt

** Package changed: bamf (Ubuntu) = dbus (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to bamf in Ubuntu.
https://bugs.launchpad.net/bugs/1284164

Title:
  ~/.cache/upstart grows enormous

Status in “dbus” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  
  $ du -hs ~/.cache/upstart/
  454M  /home/smoser/.cache/upstart/

  $ ls -altr ~/.cache/upstart/ | egrep [0-9]{6,} 
  -rw-r-  1 smoser smoser  14105029 Feb 10 08:53 gnome-session.log
  -rw-r-  1 smoser smoser   3112634 Feb 23 23:09 gnome-settings-daemon.log
  -rw-r-  1 smoser smoser   1179973 Feb 24 08:29 indicator-application.log
  -rw-r-  1 smoser smoser   4129955 Feb 24 09:31 hud.log
  -rw-r-  1 smoser smoser  18668572 Feb 24 10:13 unity-panel-service.log
  -rw-r-  1 smoser smoser 429582393 Feb 24 10:13 dbus.log
  -rw-r-  1 smoser smoser   3708061 Feb 24 10:13 gnome-session-ubuntu.log

  $ uptime
   10:15:17 up 14 days,  1:20, 24 users,  load average: 1.09, 0.95, 1.33

  I suspect my desktop has been logged in and being used for about 14
  days, but clearly not longer.  Also, it has gone through 'apt-get
  dist-upgrade' in that time (those are possible excuses for the above).

  However, I have 450M of data in a ~/.cache/upstart and 430M in a
  single file.

  I'll attach the log shortly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  Date: Mon Feb 24 10:11:04 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-10-19 (859 days ago)
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcEnviron:
   TERM=screen-bce
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: Upgraded to trusty on 2013-05-20 (280 days ago)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.11)
  UpstartRunningSystemVersion: init (upstart 1.11)

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

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

[Desktop-packages] [Bug 1276653] [NEW] udisksd crashed with SIGSEGV in ffi_call_SYSV()

2014-02-05 Thread James Hunt

Public bug reported:

.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: udisks2 2.1.2-1
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CustomUdevRuleFiles: 51-android.rules
Date: Tue Feb  4 09:23:58 2014
ExecutablePath: /usr/lib/udisks2/udisksd
InstallationDate: Installed on 2010-10-21 (1203 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MachineType: LENOVO 2516CTO
ProcCmdline: /usr/lib/udisks2/udisksd --no-debug
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash 
intel_pstate=enable
SegvAnalysis:
 Segfault happened at: 0x807dca4:   mov(%eax),%esi
 PC (0x0807dca4) ok
 source (%eax) (0x) not located in a known VMA region (needed 
readable region)!
 destination %esi ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
 ?? ()
 ?? ()
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: udisksd crashed with SIGSEGV in ffi_call_SYSV()
UpgradeStatus: Upgraded to trusty on 2013-11-01 (95 days ago)
UserGroups:
 
dmi.bios.date: 08/27/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET72WW (1.32 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2516CTO
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

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


** Tags: apport-crash i386 need-i386-retrace trusty

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1276653

Title:
  udisksd crashed with SIGSEGV in ffi_call_SYSV()

Status in “udisks2” package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: udisks2 2.1.2-1
  ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
  Uname: Linux 3.13.0-6-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  CustomUdevRuleFiles: 51-android.rules
  Date: Tue Feb  4 09:23:58 2014
  ExecutablePath: /usr/lib/udisks2/udisksd
  InstallationDate: Installed on 2010-10-21 (1203 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MachineType: LENOVO 2516CTO
  ProcCmdline: /usr/lib/udisks2/udisksd --no-debug
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic 
root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash 
intel_pstate=enable
  SegvAnalysis:
   Segfault happened at: 0x807dca4: mov(%eax),%esi
   PC (0x0807dca4) ok
   source (%eax) (0x) not located in a known VMA region (needed 
readable region)!
   destination %esi ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: udisks2
  StacktraceTop:
   ?? ()
   ?? ()
   ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: udisksd crashed with SIGSEGV in ffi_call_SYSV()
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (95 days ago)
  UserGroups:
   
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 1269731] Re: init crashed with SIGSEGV

2014-01-21 Thread James Hunt

** Changed in: upstart (Ubuntu)
   Status: In Progress = Fix Committed

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

** Changed in: upstart
 Assignee: (unassigned) = James Hunt (jamesodhunt)

** Changed in: upstart
   Status: New = Fix Committed

** Changed in: upstart
   Importance: Undecided = Critical

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

Title:
  init crashed with SIGSEGV

Status in Upstart:
  Fix Committed
Status in “alsa-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Fix Committed

Bug description:
  
  $ telinit U

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 16 08:03:58 2014
  ExecutablePath: /sbin/init
  ExecutableTimestamp: 1384521990
  InstallationDate: Installed on 2012-12-22 (389 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  ProcCmdline: /sbin/init
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic 
root=UUID=8905185c-9d82-498c-970c-6fdb9ee07c45 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f1191eb98d9:mov0x20(%rax),%rsi
   PC (0x7f1191eb98d9) ok
   source 0x20(%rax) (0x0020) not located in a known VMA region (needed 
readable region)!
   destination %rsi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: Upgraded to trusty on 2013-06-19 (210 days ago)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.11)
  UserGroups:
   
  _LogindSession: /
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-12-11T09:58:09.227262
  mtime.conffile..etc.default.whoopsie: 2013-12-19T16:30:43.528594
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2013-06-29T21:43:59.656854

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

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

[Desktop-packages] [Bug 1269731] Re: init crashed with SIGSEGV

2014-01-21 Thread James Hunt

This bug is fixed in upstart 1.11-0ubuntu2 which will be pushed out once
the alpha 2 freeze is over (Thurday).

If you are still affected by this problem (in other words you have not
managed to upgrade to alsa-utils 1.0.27.2-1ubuntu2), you will need to do
*one* of the following:

1) Disable upstart re-exec whilst running the upgrade:

$ sudo su -
# mkdir /root/bin
# ln -s /bin/true /root/bin/telinit
# chmod 755 /root/bin/telinit
# export PATH=/root/bin:$PATH
# dpkg --configure -a  sudo apt-get update  sudo apt-get upgrade

2) Temporarily move the invalid alsa job file aside whilst performing
the upgrade

$ sudo mkdir /root/tmp/
$ sudo mv /etc/init/alsa-*.conf /root/tmp/
$ sudo dpkg --reconfigure -a  sudo apt-get update  sudo apt-get upgrade
$ sudo mv /root/tmp/alsa-*.conf /etc/init/

I'd recommend doing (1) as it does not require you to undo anything
(as required in the final 'mv' operation in (2) above).

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

Title:
  init crashed with SIGSEGV

Status in Upstart:
  Fix Committed
Status in “alsa-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Fix Committed

Bug description:
  
  $ telinit U

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 16 08:03:58 2014
  ExecutablePath: /sbin/init
  ExecutableTimestamp: 1384521990
  InstallationDate: Installed on 2012-12-22 (389 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  ProcCmdline: /sbin/init
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic 
root=UUID=8905185c-9d82-498c-970c-6fdb9ee07c45 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f1191eb98d9:mov0x20(%rax),%rsi
   PC (0x7f1191eb98d9) ok
   source 0x20(%rax) (0x0020) not located in a known VMA region (needed 
readable region)!
   destination %rsi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: Upgraded to trusty on 2013-06-19 (210 days ago)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.11)
  UserGroups:
   
  _LogindSession: /
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-12-11T09:58:09.227262
  mtime.conffile..etc.default.whoopsie: 2013-12-19T16:30:43.528594
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2013-06-29T21:43:59.656854

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

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

[Desktop-packages] [Bug 1269731] Re: init crashed with SIGSEGV

2014-01-18 Thread James Hunt

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

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

Title:
  init crashed with SIGSEGV

Status in “alsa-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  In Progress

Bug description:
  
  $ telinit U

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 16 08:03:58 2014
  ExecutablePath: /sbin/init
  ExecutableTimestamp: 1384521990
  InstallationDate: Installed on 2012-12-22 (389 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  ProcCmdline: /sbin/init
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic 
root=UUID=8905185c-9d82-498c-970c-6fdb9ee07c45 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f1191eb98d9:mov0x20(%rax),%rsi
   PC (0x7f1191eb98d9) ok
   source 0x20(%rax) (0x0020) not located in a known VMA region (needed 
readable region)!
   destination %rsi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: Upgraded to trusty on 2013-06-19 (210 days ago)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.11)
  UserGroups:
   
  _LogindSession: /
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-12-11T09:58:09.227262
  mtime.conffile..etc.default.whoopsie: 2013-12-19T16:30:43.528594
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2013-06-29T21:43:59.656854

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

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

[Desktop-packages] [Bug 1269838] Re: gnome-session.log takes 8 GB in a few hours

2014-01-17 Thread James Hunt

There is an upstart logrotate job that runs automatically soon after
session start, however, it does not (yet) run periodically to handle
rogue jobs such as gnome-session. You can however run the job yourself
simply enough as a non-root user:

$ start logrotate

Please attach a few lines of the output from your gnome-session log.


** Package changed: upstart (Ubuntu) = gnome-session (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1269838

Title:
  gnome-session.log takes 8 GB in a few hours

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  Hello,

  On a fresh install of saucy 64 bits, ~/.cache/upstart/gnome-session.log grows 
incredibly fast. 8 GB in a few hours.
  Worked it around with a rm as cron task.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Thu Jan 16 16:02:23 2014
  InstallationDate: Installed on 2014-01-10 (5 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)
  upstart.upstart-file-bridge.log:
   Job got added /com/ubuntu/Upstart/jobs/unicast_2dlocal_2davahi
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2dcrash
   Job got added /com/ubuntu/Upstart/jobs/update_2dnotifier_2drelease

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

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

[Desktop-packages] [Bug 1269731] Re: init crashed with SIGSEGV

2014-01-17 Thread James Hunt

@TJ - thanks for your analysis, which mirrors our findings. We now have a fix 
to Upstart and new tests to ensure this problem stays fixed.
@Luke - thanks too for fixing alsa-utils! :)

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

Title:
  init crashed with SIGSEGV

Status in “alsa-utils” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  
  $ telinit U

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.11-0ubuntu1
  ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6
  Uname: Linux 3.12.0-8-generic x86_64
  ApportVersion: 2.13.1-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 16 08:03:58 2014
  ExecutablePath: /sbin/init
  ExecutableTimestamp: 1384521990
  InstallationDate: Installed on 2012-12-22 (389 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  ProcCmdline: /sbin/init
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.12.0-8-generic 
root=UUID=8905185c-9d82-498c-970c-6fdb9ee07c45 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f1191eb98d9:mov0x20(%rax),%rsi
   PC (0x7f1191eb98d9) ok
   source 0x20(%rax) (0x0020) not located in a known VMA region (needed 
readable region)!
   destination %rsi ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: upstart
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: init crashed with SIGSEGV
  UpgradeStatus: Upgraded to trusty on 2013-06-19 (210 days ago)
  UpstartBugCategory: System
  UpstartRunningSystemVersion: init (upstart 1.11)
  UserGroups:
   
  _LogindSession: /
  _MarkForUpload: True
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  modified.conffile..etc.default.whoopsie: [modified]
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-12-11T09:58:09.227262
  mtime.conffile..etc.default.whoopsie: 2013-12-19T16:30:43.528594
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2013-06-29T21:43:59.656854

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

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

[Desktop-packages] [Bug 1261177] Re: initctl does not terminate at computer shutdown

2013-12-16 Thread James Hunt

This looks like either a problem with network-manager, or a problem with
your network configuration / hardware. Have you modified
/etc/network/interfaces?

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

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

Title:
  initctl does not terminate at computer shutdown

Status in “network-manager” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  New

Bug description:
  fresh install of ubuntu 13.10 on asus zenbook ux31e doesn't ever
  shutdown properly

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: upstart 1.10-0ubuntu7
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Dec 15 15:34:46 2013
  ExecutablePath: /sbin/initctl
  InstallationDate: Installed on 2013-10-22 (54 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  OmitPids: 1459 1093 610 6817 6821 588 480 838 1055 574 610 6817 588 480 6937 
574 6953
  ProcCmdline: initctl emit plymouth-ready
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SourcePackage: upstart
  Title: initctl does not terminate at computer shutdown
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: Session
  UpstartRunningSessionCount: 1
  UpstartRunningSessionVersion: init (upstart 1.10)
  UpstartRunningSystemVersion: init (upstart 1.10)

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

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

[Desktop-packages] [Bug 1256262] Re: stop triggers logout (from gnome-session?) without warning. Argument required but ignored?

2013-12-09 Thread James Hunt

** Changed in: upstart (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1256262

Title:
  stop triggers logout (from gnome-session?) without warning. Argument
  required but ignored?

Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  In shell:
  stop

  Result:
  logout

  Intended:
  Nothing (was a typo, meant to write top).

  Fortunetly I didn't loose any data, but I would have if I would have
  had any unsaved files so this is at least a critical usablity issue if
  not a security vulnerability (Denial of Service vulnereabilty from
  authenticated user.. (myself)? Didn't check the box. shutdown requires
  sudo..).

  Also (all?) other initctl commands affected:

  start
  start: Job is already running: gnome-session

  man stop
  start  JOB [KEY=VALUE]...

  stop   JOB [KEY=VALUE]...

  JOB should be required(?)

  Just in case (not sure how to report/change Affects), using 13.10,
  upstart 1.10-0ubuntu7, but I guess older/newer versions are also
  affected..

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

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

[Desktop-packages] [Bug 1256262] Re: stop triggers logout (from gnome-session?) without warning. Argument required but ignored?

2013-12-05 Thread James Hunt

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

** Changed in: gnome-session (Ubuntu)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1256262

Title:
  stop triggers logout (from gnome-session?) without warning. Argument
  required but ignored?

Status in “gnome-session” package in Ubuntu:
  Fix Released
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  In shell:
  stop

  Result:
  logout

  Intended:
  Nothing (was a typo, meant to write top).

  Fortunetly I didn't loose any data, but I would have if I would have
  had any unsaved files so this is at least a critical usablity issue if
  not a security vulnerability (Denial of Service vulnereabilty from
  authenticated user.. (myself)? Didn't check the box. shutdown requires
  sudo..).

  Also (all?) other initctl commands affected:

  start
  start: Job is already running: gnome-session

  man stop
  start  JOB [KEY=VALUE]...

  stop   JOB [KEY=VALUE]...

  JOB should be required(?)

  Just in case (not sure how to report/change Affects), using 13.10,
  upstart 1.10-0ubuntu7, but I guess older/newer versions are also
  affected..

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

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

[Desktop-packages] [Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch

2013-10-18 Thread James Hunt

** Changed in: upstart (Ubuntu)
   Status: Fix Released = Incomplete

** Changed in: upstart (Ubuntu)
   Status: Incomplete = In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1235649

Title:
  uevent spam causes libdbus client code in session upstart to consume
  massive amounts of memory on Ubuntu Touch

Status in Upstart:
  New
Status in “linux” package in Ubuntu:
  Invalid
Status in “systemd” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  In Progress
Status in “linux” source package in Saucy:
  Invalid
Status in “systemd” source package in Saucy:
  Invalid
Status in “unity” source package in Saucy:
  New
Status in “upstart” source package in Saucy:
  Fix Released

Bug description:
  using ubuntu touch image 82 i see the session init consume about 10MB per 
minute as long as the screen is on  with Mir.
  running the same session with surfaceflinger only consumes 1MB per minute.

  in both cases the system starts to swap heavily at some point, making
  the UI unresponsive.

  http://paste.ubuntu.com/6196223/ has the top output of a Mir session
  after 30min, the UI just got completely unresponsive when this
  snapshot was taken.

  http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
  session where the screen was off for about 10min

  apparently the leak only occurs while the screen is on, it seems to be
  permanently there but in the case of surfaceflinger it hits less hard.

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

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

[Desktop-packages] [Bug 1238208] [NEW] libreoffice icon is too bland

2013-10-10 Thread James Hunt

Public bug reported:

The main libreoffice icon seen in the dash is too bland.

I can see that it is attempting to represent in the most minimal way the
overall office suite (by not including text, cells, formulae, etc),
however, subtracting all content from the icon gives it an overly
ascetic air which on quick glance tends to look a little like a broken
image icon.

I suggest that the current icon be replaced with one which contains
elements of all (or atleast the most popular) libreoffice tools. For
example, it could display a combination of all of the following:

- a single letter (to represent Writer)
- a single cell (to represent Calc)
- a bar graph/chart (to represent Impress)
- a simple shape (to represent Draw)

This would allow a quick visual scan to determine what the icon
represents.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1238208

Title:
  libreoffice icon is too bland

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  The main libreoffice icon seen in the dash is too bland.

  I can see that it is attempting to represent in the most minimal way
  the overall office suite (by not including text, cells, formulae,
  etc), however, subtracting all content from the icon gives it an
  overly ascetic air which on quick glance tends to look a little like a
  broken image icon.

  I suggest that the current icon be replaced with one which contains
  elements of all (or atleast the most popular) libreoffice tools. For
  example, it could display a combination of all of the following:

  - a single letter (to represent Writer)
  - a single cell (to represent Calc)
  - a bar graph/chart (to represent Impress)
  - a simple shape (to represent Draw)

  This would allow a quick visual scan to determine what the icon
  represents.

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

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

[Desktop-packages] [Bug 1208891] [NEW] lightdm locks all ttys in kvm

2013-08-06 Thread James Hunt

Public bug reported:

Booting saucy under kvm and switching to tty1 results in the screen
going black once lightdm starts and this seems to also stop the user
switching vt's using ctrl-alt-fX.

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

** Attachment added: x-0-greeter.log
   
https://bugs.launchpad.net/bugs/1208891/+attachment/3762555/+files/x-0-greeter.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1208891

Title:
  lightdm locks all ttys in kvm

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Booting saucy under kvm and switching to tty1 results in the screen
  going black once lightdm starts and this seems to also stop the user
  switching vt's using ctrl-alt-fX.

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

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

[Desktop-packages] [Bug 1207848] Re: Shutdown takes an unusual amount of time

2013-08-05 Thread James Hunt

Hi Jan,

Thanks for reporting this issue. I think you are correct - nm looks like
the culprit. Re-assigning...

** Package changed: upstart (Ubuntu) = network-manager (Ubuntu)

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

Title:
  Shutdown takes an unusual amount of time

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  Hello,

  my system takes a rather long time to shutdown (~7-10 sec.) while
  there are often error messages flashing on the screen like:

  - Killing all remaining processes failed
  - Mount: / is busy

  To investigate the problem, I patched my /etc/init.d/umountfs and
  umountroot  scripts with the proposed changes from
  https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log-
  processes-and-open-files-on-shutdown/+merge/163740 to log open files
  at shutdown and attached the resulting shutdown-lsof.log here.

  The only thing in that log that looks suspicious to me are the ones
  regarding dhclient:

  dhclient  578610  cwdDIR  252,5 4096  2 /
  dhclient  578610  rtdDIR  252,5 4096  2 /
  dhclient  578610  txtREG  252,5  1659968 654751 /sbin/dhclient
  dhclient  578610  memREG  252,552168 786517 
/lib/x86_64-linux-gnu/libnss_files-2.17.so
  dhclient  578610  memREG  252,5  1848024 786477 
/lib/x86_64-linux-gnu/libc-2.17.so
  dhclient  578610  memREG  252,5   149312 786464 
/lib/x86_64-linux-gnu/ld-2.17.so
  dhclient  5786104w   REG  252,5 1058  21443 
/var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease

  Maybe there is some problem shutting down NetworkManager? I found the
  respective dhclient entries on two separate shutdown logs.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: upstart 1.8-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Fri Aug  2 19:30:06 2013
  InstallationDate: Installed on 2013-04-10 (114 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130410)
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic 
root=/dev/mapper/internal--ssd-root ro quiet
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: 
'/etc/at.deny']

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

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

[Desktop-packages] [Bug 1203660] [NEW] lightdm crashed with SIGSEGV in g_list_last()

2013-07-22 Thread James Hunt

Public bug reported:

Latest update to lightdm broke boot for me as ligthdm crashes on
startup.

dmesg shows:

[   38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4 
in libglib-2.0.so.0.3703.0[b746b000+102000]
[   39.364988] init: lightdm main process (1621) killed by SEGV signal

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: lightdm 1.7.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
Uname: Linux 3.10.0-3-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.11-0ubuntu1
Architecture: i386
Date: Mon Jul 22 08:52:53 2013
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2010-10-21 (1005 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
LightdmConfig:
 [SeatDefaults]
 greeter-session=unity-greeter
 user-session=ubuntu
MarkForUpload: True
ProcCmdline: lightdm
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0xb7467a42 g_list_last+18: mov0x4(%eax),%edx
 PC (0xb7467a42) ok
 source 0x4(%eax) (0x03f7) not located in a known VMA region (needed 
readable region)!
 destination %edx ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 g_list_last () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_list_append () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? ()
 __libc_start_main (main=0x804c570, argc=1, ubp_av=0xbfd75f44, init=0x8065a10, 
fini=0x8065a80, rtld_fini=0xb7731600 _dl_fini, stack_end=0xbfd75f3c) at 
libc-start.c:260
 ?? ()
Title: lightdm crashed with SIGSEGV in g_list_last()
UpgradeStatus: Upgraded to saucy on 2013-06-23 (28 days ago)
UserGroups:

** Affects: lightdm (Ubuntu)
 Importance: Medium
 Status: New


** Tags: apport-crash i386 saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203660

Title:
  lightdm crashed with SIGSEGV in g_list_last()

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Latest update to lightdm broke boot for me as ligthdm crashes on
  startup.

  dmesg shows:

  [   38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4 
in libglib-2.0.so.0.3703.0[b746b000+102000]
  [   39.364988] init: lightdm main process (1621) killed by SEGV signal

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Mon Jul 22 08:52:53 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2010-10-21 (1005 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0xb7467a42 g_list_last+18:   mov0x4(%eax),%edx
   PC (0xb7467a42) ok
   source 0x4(%eax) (0x03f7) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   g_list_last () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_list_append () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x804c570, argc=1, ubp_av=0xbfd75f44, 
init=0x8065a10, fini=0x8065a80, rtld_fini=0xb7731600 _dl_fini, 
stack_end=0xbfd75f3c) at libc-start.c:260
   ?? ()
  Title: lightdm crashed with SIGSEGV in g_list_last()
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (28 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1203660] Re: lightdm crashed with SIGSEGV in g_list_last()

2013-07-22 Thread James Hunt

** Changed in: lightdm (Ubuntu)
   Importance: Medium = High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203660

Title:
  lightdm crashed with SIGSEGV in g_list_last()

Status in “lightdm” package in Ubuntu:
  New

Bug description:
  Latest update to lightdm broke boot for me as ligthdm crashes on
  startup.

  dmesg shows:

  [   38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4 
in libglib-2.0.so.0.3703.0[b746b000+102000]
  [   39.364988] init: lightdm main process (1621) killed by SEGV signal

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Mon Jul 22 08:52:53 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2010-10-21 (1005 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0xb7467a42 g_list_last+18:   mov0x4(%eax),%edx
   PC (0xb7467a42) ok
   source 0x4(%eax) (0x03f7) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   g_list_last () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_list_append () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x804c570, argc=1, ubp_av=0xbfd75f44, 
init=0x8065a10, fini=0x8065a80, rtld_fini=0xb7731600 _dl_fini, 
stack_end=0xbfd75f3c) at libc-start.c:260
   ?? ()
  Title: lightdm crashed with SIGSEGV in g_list_last()
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (28 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1203660] Re: lightdm crashed with SIGSEGV in g_list_last()

2013-07-22 Thread James Hunt

Manually downloading the old revision and rebooting does resolve the
problem for me:

$ wget 
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/lightdm_1.7.4-0ubuntu1_i386.deb
$ wget 
http://gb.archive.ubuntu.com/ubuntu/pool/main/l/lightdm/liblightdm-gobject-1-0_1.7.4-0ubuntu1_i386.deb
$ sudo dpkg -i lightdm_1.7.4-0ubuntu1_i386.deb 
liblightdm-gobject-1-0_1.7.4-0ubuntu1_i386.deb

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203660

Title:
  lightdm crashed with SIGSEGV in g_list_last()

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Latest update to lightdm broke boot for me as ligthdm crashes on
  startup.

  dmesg shows:

  [   38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4 
in libglib-2.0.so.0.3703.0[b746b000+102000]
  [   39.364988] init: lightdm main process (1621) killed by SEGV signal

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Mon Jul 22 08:52:53 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2010-10-21 (1005 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0xb7467a42 g_list_last+18:   mov0x4(%eax),%edx
   PC (0xb7467a42) ok
   source 0x4(%eax) (0x03f7) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   g_list_last () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_list_append () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x804c570, argc=1, ubp_av=0xbfd75f44, 
init=0x8065a10, fini=0x8065a80, rtld_fini=0xb7731600 _dl_fini, 
stack_end=0xbfd75f3c) at libc-start.c:260
   ?? ()
  Title: lightdm crashed with SIGSEGV in g_list_last()
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (28 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1203660] Re: lightdm crashed with SIGSEGV in g_list_last()

2013-07-22 Thread James Hunt

The default behaviour of the boot with this bug is that the greeter
never appears; you just see the Ubuntu pulsing plymouth theme.

However, the system has booted so you can switch to a text console
(control+alt+f1 for example), login and take remedial action as shown in
#6.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1203660

Title:
  lightdm crashed with SIGSEGV in g_list_last()

Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Latest update to lightdm broke boot for me as ligthdm crashes on
  startup.

  dmesg shows:

  [   38.108529] lightdm[1621]: segfault at 3f7 ip b74ada42 sp bff82ccc error 4 
in libglib-2.0.so.0.3703.0[b746b000+102000]
  [   39.364988] init: lightdm main process (1621) killed by SEGV signal

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: lightdm 1.7.6-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.11-0ubuntu1
  Architecture: i386
  Date: Mon Jul 22 08:52:53 2013
  ExecutablePath: /usr/sbin/lightdm
  InstallationDate: Installed on 2010-10-21 (1005 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  MarkForUpload: True
  ProcCmdline: lightdm
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0xb7467a42 g_list_last+18:   mov0x4(%eax),%edx
   PC (0xb7467a42) ok
   source 0x4(%eax) (0x03f7) not located in a known VMA region (needed 
readable region)!
   destination %edx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: lightdm
  StacktraceTop:
   g_list_last () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_list_append () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   __libc_start_main (main=0x804c570, argc=1, ubp_av=0xbfd75f44, 
init=0x8065a10, fini=0x8065a80, rtld_fini=0xb7731600 _dl_fini, 
stack_end=0xbfd75f3c) at libc-start.c:260
   ?? ()
  Title: lightdm crashed with SIGSEGV in g_list_last()
  UpgradeStatus: Upgraded to saucy on 2013-06-23 (28 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1155522] [NEW] foo

2013-03-15 Thread James Hunt

Public bug reported:

.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: apport 2.9.1-0ubuntu1
Uname: Linux 3.8.0-999-generic i686
ApportLog:
 
ApportVersion: 2.9.1-0ubuntu1
Architecture: i386
CrashReports:
 664:1000:114:0:2013-03-15 09:46:50.80321 +:2013-03-15 
09:46:50.80321 +:/var/crash/_sbin_init.1000.upload
 640:1000:114:105212:2013-03-15 09:46:13.785219907 +:2013-03-15 
09:46:14.785219907 +:/var/crash/_sbin_init.1000.crash
Date: Fri Mar 15 09:48:20 2013
InstallationDate: Installed on 2012-05-30 (288 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120530)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to raring on 2012-11-15 (119 days ago)

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


** Tags: apport-bug i386 raring

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1155522

Title:
  foo

Status in “apport” package in Ubuntu:
  Invalid

Bug description:
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: apport 2.9.1-0ubuntu1
  Uname: Linux 3.8.0-999-generic i686
  ApportLog:
   
  ApportVersion: 2.9.1-0ubuntu1
  Architecture: i386
  CrashReports:
   664:1000:114:0:2013-03-15 09:46:50.80321 +:2013-03-15 
09:46:50.80321 +:/var/crash/_sbin_init.1000.upload
   640:1000:114:105212:2013-03-15 09:46:13.785219907 +:2013-03-15 
09:46:14.785219907 +:/var/crash/_sbin_init.1000.crash
  Date: Fri Mar 15 09:48:20 2013
  InstallationDate: Installed on 2012-05-30 (288 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120530)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to raring on 2012-11-15 (119 days ago)

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

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

[Desktop-packages] [Bug 737792] Re: compiz crashed with SIGABRT in Glib::exception_handlers_invoke()

2013-03-11 Thread James Hunt

Fix appears to have regressed.

** Changed in: unity
   Status: Invalid = New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/737792

Title:
  compiz crashed with SIGABRT in Glib::exception_handlers_invoke()

Status in Unity:
  New
Status in “compiz” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: compiz

  After i've installed my graphics driver the compiz crashed!
  I installed the Nvidia's 3d experimental driver.
  Thanks, the ubuntu 11.04 is becoming very bealtiful. Thanks very much!!

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: compiz-core 1:0.9.4-0ubuntu7
  ProcVersionSignature: Ubuntu 2.6.38-7.35-generic 2.6.38
  Uname: Linux 2.6.38-7-generic i686
  Architecture: i386
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell]
  CompositorRunning: None
  Date: Fri Mar 18 16:57:43 2011
  DistUpgraded: Fresh install
  DistroCodename: natty
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   nVidia Corporation G96 [GeForce 9400 GT] [10de:0641] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Device [1acc:915f]
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110301.7)
  InstallationMedia_: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20110301.7)
  MachineType: System manufacturer System Product Name
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=pt_BR:en
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic 
root=UUID=5a0df536-0aab-4b4e-a65f-0a88abfaceeb ro quiet splash vt.handoff=7
  ProcVersionSignature_: Ubuntu 2.6.38-7.35-generic 2.6.38
  Renderer: Unknown
  Signal: 6
  SourcePackage: compiz
  StacktraceTop:
   Glib::exception_handlers_invoke() () from /usr/lib/libglibmm-2.4.so.1
   Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from 
/usr/lib/libglibmm-2.4.so.1
   g_main_context_dispatch () from /lib/libglib-2.0.so.0
   ?? () from /lib/libglib-2.0.so.0
   g_main_loop_run () from /lib/libglib-2.0.so.0
  Title: compiz crashed with SIGABRT in Glib::exception_handlers_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 05/20/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0402
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM-CKD-VISUM-SI
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/20/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM-CKD-VISUM-SI:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.4-0ubuntu7
  version.libdrm2: libdrm2 2.4.23-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110107+b795ca6e-0ubuntu6

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

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

[Desktop-packages] [Bug 1118143] [NEW] zenity crashes due to missing libGL.so.1

2013-02-07 Thread James Hunt

Public bug reported:

$ zenity --calendar
zenity: error while loading shared libraries: libGL.so.1: cannot open shared 
object file: No such file or directory
$ ldd `which zenity`|grep -i gl
libglib-2.0.so.0 = /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb703b000)
libGL.so.1 = not found
libdbus-glib-1.so.2 = /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 
(0xb3f81000)
$

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: zenity 3.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Thu Feb  7 08:48:51 2013
InstallationDate: Installed on 2010-10-21 (840 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=fr_CA.UTF8
 SHELL=/bin/bash
SourcePackage: zenity
UpgradeStatus: Upgraded to raring on 2012-12-20 (48 days ago)

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


** Tags: apport-bug i386 raring running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1118143

Title:
  zenity crashes due to missing libGL.so.1

Status in “zenity” package in Ubuntu:
  New

Bug description:
  $ zenity --calendar
  zenity: error while loading shared libraries: libGL.so.1: cannot open shared 
object file: No such file or directory
  $ ldd `which zenity`|grep -i gl
  libglib-2.0.so.0 = /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb703b000)
  libGL.so.1 = not found
  libdbus-glib-1.so.2 = /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 
(0xb3f81000)
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: zenity 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Thu Feb  7 08:48:51 2013
  InstallationDate: Installed on 2010-10-21 (840 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: zenity
  UpgradeStatus: Upgraded to raring on 2012-12-20 (48 days ago)

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

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

[Desktop-packages] [Bug 1118143] Re: zenity crashes due to missing libGL.so.1

2013-02-07 Thread James Hunt

Problem was caused by failed background apt-get update on my system
which had not yet configured nvidia-current.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1118143

Title:
  zenity crashes due to missing libGL.so.1

Status in “zenity” package in Ubuntu:
  Invalid

Bug description:
  $ zenity --calendar
  zenity: error while loading shared libraries: libGL.so.1: cannot open shared 
object file: No such file or directory
  $ ldd `which zenity`|grep -i gl
  libglib-2.0.so.0 = /lib/i386-linux-gnu/libglib-2.0.so.0 (0xb703b000)
  libGL.so.1 = not found
  libdbus-glib-1.so.2 = /usr/lib/i386-linux-gnu/libdbus-glib-1.so.2 
(0xb3f81000)
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: zenity 3.6.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
  Uname: Linux 3.8.0-4-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Thu Feb  7 08:48:51 2013
  InstallationDate: Installed on 2010-10-21 (840 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: zenity
  UpgradeStatus: Upgraded to raring on 2012-12-20 (48 days ago)

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

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

[Desktop-packages] [Bug 1102960] Re: dia crashes on startup

2013-01-25 Thread James Hunt

Interestingly, since this issue is GUI related, it is still possible to
run dia without one:

$ dia --nosplash -t svg -e output.svg input.dia

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dia in Ubuntu.
https://bugs.launchpad.net/bugs/1102960

Title:
  dia crashes on startup

Status in “dia” package in Ubuntu:
  New

Bug description:
  $ dia
  sys:1: Warning: attempting to add an interface 
(DiaInteractiveRendererInterface) to class (DiaGdkRenderer) after class_init

  ** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion
  `irenderer != NULL' failed

  ** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion 
`irenderer != NULL' failed
  Segmentation fault (core dumped)
  $ file core.11678 
  core.11678: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), 
SVR4-style, from 'dia-normal --integrated'
  $ gdb `which dia-normal` core.*
  GNU gdb (GDB) 7.5-ubuntu
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as i686-linux-gnu.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/...
  Reading symbols from /usr/bin/dia-normal...(no debugging symbols 
found)...done.
  [New LWP 11678]
  [New LWP 11680]
  [New LWP 11679]
  [New LWP 11681]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
  Core was generated by `dia-normal --integrated'.
  Program terminated with signal 11, Segmentation fault.
  #0  0x08072d03 in ?? ()
  (gdb) bt
  #0  0x08072d03 in ?? ()
  #1  0xb6e2bab0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #2  0xb6e2e973 in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb6e2ed10 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb6e2f1eb in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb733a5c0 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  #6  0x0805d1a5 in main ()
  (gdb)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: dia 0.97.2-8
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  Date: Tue Jan 22 11:58:58 2013
  InstallationDate: Installed on 2010-10-21 (824 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: dia
  UpgradeStatus: Upgraded to raring on 2012-12-20 (32 days ago)

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

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

[Desktop-packages] [Bug 1102960] [NEW] dia crashes on startup

2013-01-22 Thread James Hunt

Public bug reported:

$ dia
sys:1: Warning: attempting to add an interface 
(DiaInteractiveRendererInterface) to class (DiaGdkRenderer) after class_init

** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion
`irenderer != NULL' failed

** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion `irenderer 
!= NULL' failed
Segmentation fault (core dumped)
$ file core.11678 
core.11678: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, 
from 'dia-normal --integrated'
$ gdb `which dia-normal` core.*
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i686-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/dia-normal...(no debugging symbols found)...done.
[New LWP 11678]
[New LWP 11680]
[New LWP 11679]
[New LWP 11681]
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
Core was generated by `dia-normal --integrated'.
Program terminated with signal 11, Segmentation fault.
#0  0x08072d03 in ?? ()
(gdb) bt
#0  0x08072d03 in ?? ()
#1  0xb6e2bab0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb6e2e973 in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb6e2ed10 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6e2f1eb in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb733a5c0 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
#6  0x0805d1a5 in main ()
(gdb)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: dia 0.97.2-8
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu2
Architecture: i386
Date: Tue Jan 22 11:58:58 2013
InstallationDate: Installed on 2010-10-21 (824 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=fr_CA.UTF8
 SHELL=/bin/bash
SourcePackage: dia
UpgradeStatus: Upgraded to raring on 2012-12-20 (32 days ago)

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


** Tags: apport-bug i386 raring running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dia in Ubuntu.
https://bugs.launchpad.net/bugs/1102960

Title:
  dia crashes on startup

Status in “dia” package in Ubuntu:
  New

Bug description:
  $ dia
  sys:1: Warning: attempting to add an interface 
(DiaInteractiveRendererInterface) to class (DiaGdkRenderer) after class_init

  ** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion
  `irenderer != NULL' failed

  ** (dia-normal:11678): CRITICAL **: dia_renderer_set_size: assertion 
`irenderer != NULL' failed
  Segmentation fault (core dumped)
  $ file core.11678 
  core.11678: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), 
SVR4-style, from 'dia-normal --integrated'
  $ gdb `which dia-normal` core.*
  GNU gdb (GDB) 7.5-ubuntu
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as i686-linux-gnu.
  For bug reporting instructions, please see:
  http://www.gnu.org/software/gdb/bugs/...
  Reading symbols from /usr/bin/dia-normal...(no debugging symbols 
found)...done.
  [New LWP 11678]
  [New LWP 11680]
  [New LWP 11679]
  [New LWP 11681]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
  Core was generated by `dia-normal --integrated'.
  Program terminated with signal 11, Segmentation fault.
  #0  0x08072d03 in ?? ()
  (gdb) bt
  #0  0x08072d03 in ?? ()
  #1  0xb6e2bab0 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #2  0xb6e2e973 in g_main_context_dispatch () from 
/lib/i386-linux-gnu/libglib-2.0.so.0
  #3  0xb6e2ed10 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #4  0xb6e2f1eb in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
  #5  0xb733a5c0 in gtk_main () from /usr/lib/i386-linux-gnu/libgtk-x11-2.0.so.0
  #6  0x0805d1a5 in main ()
  (gdb)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: dia 0.97.2-8
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  Date: Tue Jan 22 11:58:58 2013
  InstallationDate:

[Desktop-packages] [Bug 1101154] [NEW] all signal handlers have been removed in error

2013-01-18 Thread James Hunt

Public bug reported:

gnome-session/main.c has disabled all signal handling, but intention was
seemingly to only disable SIGSEGV signal handing:

10:43 jodh chrisccoulson: hi - I'm looking at how gnome-session currently
 shuts down and trying to understand why the following is
 commented out: http://paste.ubuntu.com/1544640/
10:44 chrisccoulson jodh, IIRC it was to stop gnome-session from swallowing
  those signals so we got crash reports with apport
10:44 chrisccoulson but this was a long time ago ;)
10:49 jodh chrisccoulson: ok, thanks.
10:49 chrisccoulson jodh, technically, i think only the call to
  gdm_signal_handler_add_fatal() needs to be commented out
10:49 chrisccoulson i can't remember why we disabled all signal handling
10:50 chrisccoulson i've slept and drank beer since then ;)
10:50 pitti chrisccoulson: or perhaps a merge error? in the original patch
  the commented out section might only have been for SIGSEGV, and
  in newer upstream versions the SIGTERMs got added?
10:52 chrisccoulson pitti, yeah, you're right
10:52 chrisccoulson the original patch was
  
http://bazaar.launchpad.net/~ubuntu-desktop/gnome-session/ubuntu/revision/18
10:52 chrisccoulson jodh ^^
10:53 chrisccoulson it got changed here by seb128:
  
http://bazaar.launchpad.net/~ubuntu-desktop/gnome-session/ubuntu/revision/233
10:53 chrisccoulson not sure why ;)
10:53 pitti that doesn't look intended
10:54 chrisccoulson jodh, so, the short summary is - the patch is only meant
  to disable the SEGV handler ;)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1101154

Title:
  all signal handlers have been removed in error

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  gnome-session/main.c has disabled all signal handling, but intention
  was seemingly to only disable SIGSEGV signal handing:

  10:43 jodh chrisccoulson: hi - I'm looking at how gnome-session currently
   shuts down and trying to understand why the following is
   commented out: http://paste.ubuntu.com/1544640/
  10:44 chrisccoulson jodh, IIRC it was to stop gnome-session from swallowing
those signals so we got crash reports with apport
  10:44 chrisccoulson but this was a long time ago ;)
  10:49 jodh chrisccoulson: ok, thanks.
  10:49 chrisccoulson jodh, technically, i think only the call to
gdm_signal_handler_add_fatal() needs to be commented out
  10:49 chrisccoulson i can't remember why we disabled all signal handling
  10:50 chrisccoulson i've slept and drank beer since then ;)
  10:50 pitti chrisccoulson: or perhaps a merge error? in the original patch
the commented out section might only have been for SIGSEGV, and
in newer upstream versions the SIGTERMs got added?
  10:52 chrisccoulson pitti, yeah, you're right
  10:52 chrisccoulson the original patch was

http://bazaar.launchpad.net/~ubuntu-desktop/gnome-session/ubuntu/revision/18
  10:52 chrisccoulson jodh ^^
  10:53 chrisccoulson it got changed here by seb128:

http://bazaar.launchpad.net/~ubuntu-desktop/gnome-session/ubuntu/revision/233
  10:53 chrisccoulson not sure why ;)
  10:53 pitti that doesn't look intended
  10:54 chrisccoulson jodh, so, the short summary is - the patch is only meant
to disable the SEGV handler ;)

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

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

[Desktop-packages] [Bug 1101227] [NEW] signond spams syslog

2013-01-18 Thread James Hunt

Public bug reported:

This looks to be a regression of bug 1049949.

$ wc -l /var/log/syslog
822 /var/log/syslog
$ grep signonpluginprocess /var/log/syslog | wc -l
557

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: signond 8.44-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu2
Architecture: i386
Date: Fri Jan 18 14:47:00 2013
InstallationDate: Installed on 2010-10-21 (820 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=fr_CA.UTF8
 SHELL=/bin/bash
SourcePackage: signon
UpgradeStatus: Upgraded to raring on 2012-12-20 (28 days ago)

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


** Tags: apport-bug i386 raring running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to signon in Ubuntu.
https://bugs.launchpad.net/bugs/1101227

Title:
  signond spams syslog

Status in “signon” package in Ubuntu:
  New

Bug description:
  This looks to be a regression of bug 1049949.

  $ wc -l /var/log/syslog
  822 /var/log/syslog
  $ grep signonpluginprocess /var/log/syslog | wc -l
  557

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: signond 8.44-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.8-0ubuntu2
  Architecture: i386
  Date: Fri Jan 18 14:47:00 2013
  InstallationDate: Installed on 2010-10-21 (820 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=fr_CA.UTF8
   SHELL=/bin/bash
  SourcePackage: signon
  UpgradeStatus: Upgraded to raring on 2012-12-20 (28 days ago)

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

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

[Desktop-packages] [Bug 997359] Re: nih uses eglibc private symbol __abort_msg

2012-10-25 Thread James Hunt

** Changed in: libnih (Ubuntu Raring)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/997359

Title:
  nih uses eglibc private symbol __abort_msg

Status in NIH Utility Library:
  New
Status in “apport” package in Ubuntu:
  Confirmed
Status in “libnih” package in Ubuntu:
  Fix Released
Status in “apport” source package in Precise:
  New
Status in “libnih” source package in Precise:
  New
Status in “apport” source package in Quantal:
  New
Status in “libnih” source package in Quantal:
  New
Status in “apport” source package in Raring:
  Confirmed
Status in “libnih” source package in Raring:
  Fix Released

Bug description:
  NIH uses the private eglibc '__abort_msg' symbol to save a string
  explaining why nih_assert() failed. However, __abort_msg is not a
  public symbol which causes problems when libc is upgraded - it
  actually necessitates that for every libc upgrade on, for example,
  Ubuntu systems the following has to happen:

  1) eglibc is upgraded with a version set to version~foo
  2) nih is rebuilt against the eglibc version
  3) nih is upgraded.
  4) the eglibc package is upgraded *again* to drop the ~foo.

  The symbol can be made use of like this:

  $ cat foo.cEOF
  int
  main(int argc, char *argv[])
  {
  nih_log_set_priority (NIH_LOG_FATAL);
  nih_assert (0 == 1);

  exit (EXIT_SUCCESS);
  }
  EOF
  $ gcc -std=gnu99 -g -Wall -pedantic -o foo foo.c `pkg-config --cflags --libs 
libnih`
  $ ./foo
  (null):nih_make_core.c:46: Assertion failed in main: 0 == 1
  Aborted (core dumped)
  $ gdb foo core.1597
  GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu1) 7.4-2012.04
  Copyright (C) 2012 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type show copying
  and show warranty for details.
  This GDB was configured as i686-linux-gnu.
  For bug reporting instructions, please see:
  http://bugs.launchpad.net/gdb-linaro/...
  Reading symbols from /home/james/src/c/foo...done.
  [New LWP 1597]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
  Core was generated by `foo'.
  Program terminated with signal 6, Aborted.
  #0  0xb770d1b2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
  (gdb) p (char *)__abort_msg
  $1 = 0x93fa098 nih_make_core.c:46: Assertion failed in main: 0 == 1
  (gdb)

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

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

[Desktop-packages] [Bug 1069624] Re: System failed to detect GPU.

2012-10-22 Thread James Hunt

Not an Upstart issue.

** Package changed: upstart (Ubuntu) = fglrx-installer (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1069624

Title:
  System failed to detect GPU.

Status in “fglrx-installer” package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 12.10
  Release:  12.10
  upstart:
Installed: 1.5-0ubuntu9
Candidate: 1.5-0ubuntu9
Version table:
   *** 1.5-0ubuntu9 0
  500 http://ca.archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
  100 /var/lib/dpkg/status

  I don't really know if this is an upstart bug, but it seems the
  logical place to start looking.

  I updated my 12.04 LTS system last evening on the basis of the
  announcement on the website.  To my great surprise it is not as good
  as the beta which now seems to be beyond where this verson is.

  The system failed to detect my GPU (ATI/AMD 780) and the DVI monitor
  (1920 x 1080) whereas the beta version most certainly does and handles
  it correctly.  In fact, it reports to applications that there is no
  accelerated 3D graphics at all, which cause my applications to not
  run.

  The normal driver for this chip set is fglrx, and it was not loaded by
  the upgrade (nor by the beta, but that didn't seem to matter).  I
  forced an install of fglrx which seemed to go OK, but the AMD/ATI
  control software does not detect it as installed.  Furthermore,
  although it appeared that the software did in fact generate the
  appropirate kernel image for this, nothing happens.  The system is
  running in the default display for a laptop (which is utterly beyond
  belief) but this is a desktop machine.

  I performed the upgrade in the usual manner by using the command for
  the software manager with the -d option and everything went OK for the
  next couple of hours.  The system restarted, but the Ubuntu desktop
  failed partially, and there was no launcher and no top of screen
  panel.  All I could do was force a restart.  I wound up in the GNOME
  classic desktop which works normally.  Not my choice, but there you
  are.

  This distrubution is not ready for people in spite of the exuberance
  of the web site.  For shame!  My beta version runs better than this.

  During the installation there were a couple of defective libraries
  reported and I was able, eventually, to install them with apt.  There
  was also a continuous reiteration of some message about duplicate
  values in some test file, which hardly seems to be proper for a final
  distribution.  There is a plethora of problems, and I hope this is the
  only report I need make.  I strongly suggest that somebody test this
  again.  You have now created a panic for yourselves with this
  premature, untested release.  Perhaps a public apology will absolve
  some of this, but I think you've set back your marketing efforts
  considerably.

  As of now, I am moving all my data files over to the beta partition.
  It is far superior to this box of bugs.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: upstart 1.5-0ubuntu9
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 01:12:17 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  SourcePackage: upstart
  UpgradeStatus: Upgraded to quantal on 2012-10-22 (0 days ago)

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

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

[Desktop-packages] [Bug 1069481] Re: external usb TOSHIBA disk could not be mounted

2012-10-22 Thread James Hunt

Not an upstart issue. Sounds like it might be a non-privileged mounting
problem.

** Package changed: upstart (Ubuntu) = gvfs (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1069481

Title:
  external usb TOSHIBA disk could not be mounted

Status in “gvfs” package in Ubuntu:
  New

Bug description:
  Hi, after upgradind from 12.04 LTS to 12.10 (my mistake!!) my external
  disk could not be mounted; it is reconigsed by nautilus, appears on it
  but it cannot be mountes givine the error: Incapaz de montar TOSHIBA.
  Adding read ACL for uid 1000 to `/media/paulo' failed: Operation not
  supported. The same error for my USB DVD drive.

  Help please.

  Regards

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

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

[Desktop-packages] [Bug 1060249] Re: frontend crashed with signal 5 in free_pending_nulls()

2012-10-17 Thread James Hunt

Branch for when 'R' opens:

https://code.launchpad.net/~jamesodhunt/ubuntu/quantal/debconf/bug-1060249

Patch sent to Debian.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.
https://bugs.launchpad.net/bugs/1060249

Title:
  frontend crashed with signal 5 in free_pending_nulls()

Status in “debconf” package in Ubuntu:
  Confirmed
Status in “gsettings-desktop-schemas” package in Ubuntu:
  Fix Released
Status in “debconf” source package in Precise:
  Invalid
Status in “debconf” source package in Quantal:
  Won't Fix
Status in “gsettings-desktop-schemas” source package in Quantal:
  Fix Released

Bug description:
  Crashed during upgrade from Precise to Quantal without any visible
  effect

  TEST CASE 1:
  1. Install Precise 12.04.1
  2. Upgrade to Quantal

  TEST CASE 2:
  This test case is used to reproduce the debconf crash:
  1. Install Precise 12.04.1 and apply updates
  2. Enable apt repository for Quantal
  3. Install gsettings-desktop-schemas from Quantal:
  $ sudo apt-get install  gsettings-desktop-schemas/quantal
  4. Run man-db trigger manually with:
$ sudo DEBIAN_FRONTEND=gnome \
  /usr/bin/perl -w /usr/share/debconf/frontend \
  /var/lib/dpkg/info/man-db.postinst triggered \
  /usr/share/man

  = Verify that debconf crashes
  Actually any gtk based application will crash.

  ACTUAL RESULT
  This crash is reported on first login after upgrade.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: debconf 1.5.46ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 14:59:09 2012
  ExecutablePath: /usr/share/debconf/frontend
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/man-db.postinst triggered /usr/share/man
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: debconf
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_node_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: frontend crashed with signal 5 in g_node_copy_deep()
  UpgradeStatus: Upgraded to quantal on 2012-10-02 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1060249] Re: frontend crashed with signal 5 in free_pending_nulls()

2012-10-17 Thread James Hunt

The problem with debconf needs a little explanation. As show, the
command that caused the failure was:

/usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/info/man-
db.postinst triggered /usr/share/man

The 'frontend' perl script determines which type of debconf frontend to
display. In this case, the gnome frontend was selected. debconf then
goes to some pains to ensure that the gtk bindings work. However,
because of the gsettings schema problem, as soon as any perl script
called 'use Gtk2;', the schema was queried, which resulted in the crash.

Since the master debconf process calls 'use Gtk2;' unconditionally, the
schema problem caused debconf (technically the perl interpreter) to
crash.  And since debconf re-execs the original caller (in this case
'/var/lib/dpkg/info/man-db.postinst') as itself, this stopped debconf
from falling back to other frontends as it should as it was now
effectively dead.

The fix is for debconf to only 'use Gtk2;' when it has proven that this
operation can be performed without impacting the perl interpreter. This
allows it to fall back gracefully to alternative frontends.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.
https://bugs.launchpad.net/bugs/1060249

Title:
  frontend crashed with signal 5 in free_pending_nulls()

Status in “debconf” package in Ubuntu:
  Confirmed
Status in “gsettings-desktop-schemas” package in Ubuntu:
  Fix Released
Status in “debconf” source package in Precise:
  Invalid
Status in “debconf” source package in Quantal:
  Won't Fix
Status in “gsettings-desktop-schemas” source package in Quantal:
  Fix Released

Bug description:
  Crashed during upgrade from Precise to Quantal without any visible
  effect

  TEST CASE 1:
  1. Install Precise 12.04.1
  2. Upgrade to Quantal

  TEST CASE 2:
  This test case is used to reproduce the debconf crash:
  1. Install Precise 12.04.1 and apply updates
  2. Enable apt repository for Quantal
  3. Install gsettings-desktop-schemas from Quantal:
  $ sudo apt-get install  gsettings-desktop-schemas/quantal
  4. Run man-db trigger manually with:
$ sudo DEBIAN_FRONTEND=gnome \
  /usr/bin/perl -w /usr/share/debconf/frontend \
  /var/lib/dpkg/info/man-db.postinst triggered \
  /usr/share/man

  = Verify that debconf crashes
  Actually any gtk based application will crash.

  ACTUAL RESULT
  This crash is reported on first login after upgrade.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: debconf 1.5.46ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 14:59:09 2012
  ExecutablePath: /usr/share/debconf/frontend
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/man-db.postinst triggered /usr/share/man
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: debconf
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_node_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: frontend crashed with signal 5 in g_node_copy_deep()
  UpgradeStatus: Upgraded to quantal on 2012-10-02 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1060249] Re: frontend crashed with signal 5 in free_pending_nulls()

2012-10-17 Thread James Hunt

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

** Also affects: debconf via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690776
   Importance: Unknown
   Status: Unknown

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu.
https://bugs.launchpad.net/bugs/1060249

Title:
  frontend crashed with signal 5 in free_pending_nulls()

Status in Debconf:
  Unknown
Status in “debconf” package in Ubuntu:
  Fix Committed
Status in “gsettings-desktop-schemas” package in Ubuntu:
  Fix Released
Status in “debconf” source package in Precise:
  Invalid
Status in “debconf” source package in Quantal:
  Won't Fix
Status in “gsettings-desktop-schemas” source package in Quantal:
  Fix Released

Bug description:
  Crashed during upgrade from Precise to Quantal without any visible
  effect

  TEST CASE 1:
  1. Install Precise 12.04.1
  2. Upgrade to Quantal

  TEST CASE 2:
  This test case is used to reproduce the debconf crash:
  1. Install Precise 12.04.1 and apply updates
  2. Enable apt repository for Quantal
  3. Install gsettings-desktop-schemas from Quantal:
  $ sudo apt-get install  gsettings-desktop-schemas/quantal
  4. Run man-db trigger manually with:
$ sudo DEBIAN_FRONTEND=gnome \
  /usr/bin/perl -w /usr/share/debconf/frontend \
  /var/lib/dpkg/info/man-db.postinst triggered \
  /usr/share/man

  = Verify that debconf crashes
  Actually any gtk based application will crash.

  ACTUAL RESULT
  This crash is reported on first login after upgrade.

  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: debconf 1.5.46ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic x86_64
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: amd64
  Date: Tue Oct  2 14:59:09 2012
  ExecutablePath: /usr/share/debconf/frontend
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  InterpreterPath: /usr/bin/perl
  PackageArchitecture: all
  ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/man-db.postinst triggered /usr/share/man
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: debconf
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_node_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: frontend crashed with signal 5 in g_node_copy_deep()
  UpgradeStatus: Upgraded to quantal on 2012-10-02 (0 days ago)
  UserGroups:

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

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

[Desktop-packages] [Bug 1049664] Re: libreoffice crashes on --help

2012-10-05 Thread James Hunt

I have the same problem.

After installing the dbg packages...

$ gdb --args /usr/lib/libreoffice/program/soffice.bin --help
GNU gdb (GDB) 7.5-ubuntu
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i686-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/lib/libreoffice/program/soffice.bin...Reading symbols 
from /usr/lib/debug/usr/lib/libreoffice/program/soffice.bin...done.
done.
(gdb) r
Starting program: /usr/lib/libreoffice/program/soffice.bin --help
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/ure/lib/libuno_sal.so.3-gdb.py, line 39, in 
module
from libreoffice.sal import register_pretty_printers
ImportError: No module named libreoffice.sal
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/ure/lib/libuno_sal.so.3-gdb.py, line 39, in 
module
from libreoffice.sal import register_pretty_printers
ImportError: No module named libreoffice.sal
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1.
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/ure/lib/libuno_cppu.so.3-gdb.py, line 39, in 
module
from libreoffice.cppu import register_pretty_printers
ImportError: No module named libreoffice.cppu
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/ure/lib/libuno_cppu.so.3-gdb.py, line 39, in 
module
from libreoffice.cppu import register_pretty_printers
ImportError: No module named libreoffice.cppu
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/libreoffice/program/libsvllo.so-gdb.py, line 
39, in module
from libreoffice.svl import register_pretty_printers
ImportError: No module named libreoffice.svl
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/libreoffice/program/libsvllo.so-gdb.py, line 
39, in module
from libreoffice.svl import register_pretty_printers
ImportError: No module named libreoffice.svl
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/libreoffice/program/libtllo.so-gdb.py, line 39, 
in module
from libreoffice.tl import register_pretty_printers
ImportError: No module named libreoffice.tl
Traceback (most recent call last):
  File /usr/lib/debug/usr/lib/libreoffice/program/libtllo.so-gdb.py, line 39, 
in module
from libreoffice.tl import register_pretty_printers
ImportError: No module named libreoffice.tl
[New Thread 0xb47d3b40 (LWP 1418)]

Program received signal SIGSEGV, Segmentation fault.
0xb7b080e0 in cppu::_copyConstructAnyFromData (pDestAny=0x804cef8, 
pSource=0xb250, pType=0x804dc58, pTypeDescr=0x0, acquire=
0xb6f8d318 com::sun::star::uno::cpp_acquire(void*), mapping=0x0) at 
/build/buildd/libreoffice-3.6.1~rc2/cppu/source/uno/copy.hxx:260
260 /build/buildd/libreoffice-3.6.1~rc2/cppu/source/uno/copy.hxx: No such 
file or directory.
(gdb) bt
#0  0xb7b080e0 in cppu::_copyConstructAnyFromData (pDestAny=0x804cef8, 
pSource=0xb250, pType=0x804dc58, pTypeDescr=0x0, 
acquire=0xb6f8d318 com::sun::star::uno::cpp_acquire(void*), mapping=0x0) 
at /build/buildd/libreoffice-3.6.1~rc2/cppu/source/uno/copy.hxx:260
#1  0xb7b08442 in cppu::_copyConstructAny (pDestAny=0x804cef8, 
pSource=optimized out, pType=0x804dc58, pTypeDescr=0x0, 
acquire=0xb6f8d318 com::sun::star::uno::cpp_acquire(void*), mapping=0x0) 
at /build/buildd/libreoffice-3.6.1~rc2/cppu/source/uno/copy.hxx:371
#2  0xb7b07a36 in uno_type_any_assign (pDest=0x804cef8, pSource=0xb250, 
pType=0x804dc58, acquire=0xb6f8d318 com::sun::star::uno::cpp_acquire(void*), 
release=0xb6f8d32c com::sun::star::uno::cpp_release(void*)) at 
/build/buildd/libreoffice-3.6.1~rc2/cppu/source/uno/any.cxx:48
#3  0xb6f9efc8 in 
com::sun::star::uno::operator=com::sun::star::beans::NamedValue (rAny=..., 
value=...)
at 
/build/buildd/libreoffice-3.6.1~rc2/solver/unxlngi6.pro/inc/com/sun/star/uno/Any.hxx:204
#4  0xb6f9d3d7 in (anonymous namespace)::getConfigurationString (module=..., 
path=...) at 
/build/buildd/libreoffice-3.6.1~rc2/unotools/source/config/configmgr.cxx:92
#5  0xb6f9d8df in utl::ConfigManager::getProductName () at 
/build/buildd/libreoffice-3.6.1~rc2/unotools/source/config/configmgr.cxx:145
#6  0xb7f5098a in desktop::ReplaceStringHookProc (rStr=...) at 
/build/buildd/libreoffice-3.6.1~rc2/desktop/source/app/app.cxx:483
#7  0xb7f67786 in desktop::displayCmdlineHelp () at 
/build/buildd/libreoffice-3.6.1~rc2/desktop/source/app/cmdlinehelp.cxx:148
#8  0xb7f727a2 in soffice_main () at 
/build/buildd/libreoffice-3.6.1~rc2/desktop/source/app/sofficemain.cxx:72
#9  0x0804857c in sal_main () at 
/build/buildd/libreoffice-3.6.1~rc2/desktop/source/app/main.c:34
#10 main (argc=2,

[Desktop-packages] [Bug 1062378] [NEW] libreoffice crashes with SIGSEGV opening some .docx files

2012-10-05 Thread James Hunt

Public bug reported:

I have the dbg packages installed. See attached gdb transcript for
backtrace for all threads.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
Uname: Linux 3.5.0-16-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
Date: Fri Oct  5 16:31:28 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to quantal on 2012-09-30 (4 days ago)

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


** Tags: apport-bug i386 quantal running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1062378

Title:
  libreoffice crashes with SIGSEGV opening some .docx files

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  I have the dbg packages installed. See attached gdb transcript for
  backtrace for all threads.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
  Date: Fri Oct  5 16:31:28 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-09-30 (4 days ago)

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

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

[Desktop-packages] [Bug 1062378] Re: libreoffice crashes with SIGSEGV opening some .docx files

2012-10-05 Thread James Hunt

** Attachment added: gdb-transcript.log
   
https://bugs.launchpad.net/bugs/1062378/+attachment/3376376/+files/gdb-transcript.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1062378

Title:
  libreoffice crashes with SIGSEGV opening some .docx files

Status in “libreoffice” package in Ubuntu:
  New

Bug description:
  I have the dbg packages installed. See attached gdb transcript for
  backtrace for all threads.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4
  Uname: Linux 3.5.0-16-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu1
  Architecture: i386
  Date: Fri Oct  5 16:31:28 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to quantal on 2012-09-30 (4 days ago)

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

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

[Desktop-packages] [Bug 942530] Re: on-screen keyboard always displays once enabled

2012-05-25 Thread James Hunt

A way to fix this:

$ gsettings set org.gnome.desktop.screensaver embedded-keyboard-command
''

For some reason, I had the following set:

$ gsettings get org.gnome.desktop.screensaver embedded-keyboard-command
'onboard -xid'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/942530

Title:
  on-screen keyboard always displays once enabled

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  Whilst investigating bug 937611, I enabled the on-screen keyboard.
  However, I subsequently switched if off via System Settings -
  Universal Access - Typing tab - Typing Assistant.

  As expected, the keyboard no longer displays on the desktop but when
  the screen locks automatically or is locked manually, the on-screen
  keyboard is displayed again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screensaver 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  Date: Tue Feb 28 10:28:11 2012
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to precise on 2012-01-12 (46 days ago)
  WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

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

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

[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?

2012-05-23 Thread James Hunt

This looks like it might be a duplicate of bug 615549.

I've done some digging and although I'm not sure this will fully resolve
the issue observed, I have found a bug in lightdm.conf which could cause
the behaviour seen...

As Clint intimates in #11, the current 'start on' condition...

drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1

... is *NOT* valid. What this condition is asking Upstart to do is match
on an event whose first _positional_ environment variable *exactly
matches* the string 'card0' and which also has an environment variable
called 'PRIMARY_DEVICE_FOR_DISPLAY' with value '1'.

However, if you look at /var/log/udev:

$ awk 'BEGIN{RS=;ORS=\n\n}; /UDEV *\[/  /PRIMARY_DEVICE_FOR_DISPLAY=1/ { 
print; }' /var/log/udev
UDEV  [34.559987] add  
/devices/pci:00/:00:01.0/:01:00.0/drm/card0 (drm)
ACTION=add
DEVNAME=/dev/dri/card0
DEVPATH=/devices/pci:00/:00:01.0/:01:00.0/drm/card0
DEVTYPE=drm_minor
MAJOR=226
MINOR=0
PRIMARY_DEVICE_FOR_DISPLAY=1
SEQNUM=2231
SUBSYSTEM=drm
TAGS=:udev-acl:
UDEV_LOG=3
USEC_INITIALIZED=34559916
$

... you'll see that there are no variables that exactly match 'card0'!
The fix is as simple as adding an asterisk to perform a wild-card match:

  drm-device-added *card0 PRIMARY_DEVICE_FOR_DISPLAY=1

However, my preference would to make our intent explicit and say:

  drm-device-added DEVPATH=*card0 PRIMARY_DEVICE_FOR_DISPLAY=1

This would protect against a change to the way the upstart-udev-bridge
handles udev environment variable ordering and is much easier to
understand.

@serge - could you add the missing asterisk and report back?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489

Title:
  lightdm tries (and fails) to start too early?

Status in Upstart:
  New
Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes lightdm comes up fine.  Other times it appears to fail.
  x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is
  what actually exists).  When I then log into console and 'start
  lightdm', it comes up fine (on :1).

  I've not had it come up ok today, so I don't know if, when it comes up
  fine, it starts on :0.  No idea if the lightdm.conf needs a change to
  'start on'clause, or if this is just a case of a bad shipped config
  file (for module 'nv').

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 13:40:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120323)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?

2012-05-23 Thread James Hunt

Addendum to #19:

Currently the 'card0' matching is being attempted on DEVPATH. This isn't
obvious from the /var/log/udev extract shown, but the upstart-udev-
bridge will in this scenario create the event with the following
environment variable ordering:

1) DEVPATH
2) DEVNAME
3) SUBSYSTEM
4) ACTION
5) the rest

So if in doubt, prefer name=value pairs to positional variables.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489

Title:
  lightdm tries (and fails) to start too early?

Status in Upstart:
  New
Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes lightdm comes up fine.  Other times it appears to fail.
  x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is
  what actually exists).  When I then log into console and 'start
  lightdm', it comes up fine (on :1).

  I've not had it come up ok today, so I don't know if, when it comes up
  fine, it starts on :0.  No idea if the lightdm.conf needs a change to
  'start on'clause, or if this is just a case of a bad shipped config
  file (for module 'nv').

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 13:40:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120323)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?

2012-05-23 Thread James Hunt

Please could those affected attach /var/log/udev?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489

Title:
  lightdm tries (and fails) to start too early?

Status in Upstart:
  New
Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes lightdm comes up fine.  Other times it appears to fail.
  x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is
  what actually exists).  When I then log into console and 'start
  lightdm', it comes up fine (on :1).

  I've not had it come up ok today, so I don't know if, when it comes up
  fine, it starts on :0.  No idea if the lightdm.conf needs a change to
  'start on'clause, or if this is just a case of a bad shipped config
  file (for module 'nv').

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 13:40:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120323)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 987220] Re: no complete shutdown

2012-05-05 Thread James Hunt

This problem sounds like it could be kernel issue.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/987220

Title:
  no complete shutdown

Status in “gnome-session” package in Ubuntu:
  Confirmed
Status in “indicator-session” package in Ubuntu:
  Incomplete
Status in “linux” package in Ubuntu:
  New
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Shutting down the computer using the menue does not work always correct. It 
often does not complete turn off the computer. The power LED and the LED of the 
bluetooth unit remain on. Also the fan is still running and won't stop. 
  Shutting down the computer with sudo shutdown -h now using the terminal 
works fine.

  I am using a Dell Inspiron 1720.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: indicator-session 0.3.96-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: i386
  Date: Mon Apr 23 12:26:10 2012
  ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper
  InstallationMedia: Kubuntu 10.04.1 LTS Lucid Lynx - Release i386 
(20100816.2)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
  SourcePackage: indicator-session
  UpgradeStatus: Upgraded to precise on 2012-04-21 (1 days ago)

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

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

[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?

2012-04-17 Thread James Hunt

For 12.10, we really should add a 'primary-graphics-card' event alias or
abstract job that abstracts the udev complexities since that confusing
condition (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or
stopped udev-fallback-graphics) is also semi-duplicated in other jobs:

- plymouth-splash.conf
- udev-fallback-graphics.conf

I think the definitive condition that becomes true when the first
graphics device becomes available is:

(graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udev-fallback-graphics)

I agree that 'card0' seems bogus - looks like it's trying to match
DEVPATH but that will never match since there is no wildcard in the
expression. It should be something like the following (note the asterisk
after the equals!!):

drm-device-added DEVPATH=*card0 PRIMARY_DEVICE_FOR_DISPLAY=1

Using named variables ('name=value' as opposed to positional ones where
only a *value* is given) as I've done above is *much* safer in this
scenario since to use positional variables, you need to know the exact
content of the corresponding udev message that the upstart-udev-bridge
converts into an Upstart event.

File /lib/udev/rules.d/78-graphics-card.rules is what is modifying the
udev message to add PRIMARY_DEVICE_FOR_DISPLAY=1 so I'm wondering if we
can simplify the logic to be simply:

drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1

... since udev will tag both KMS and non-KMS devices correctly.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/969489

Title:
  lightdm tries (and fails) to start too early?

Status in Upstart:
  New
Status in “lightdm” package in Ubuntu:
  Confirmed

Bug description:
  Sometimes lightdm comes up fine.  Other times it appears to fail.
  x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is
  what actually exists).  When I then log into console and 'start
  lightdm', it comes up fine (on :1).

  I've not had it come up ok today, so I don't know if, when it comes up
  fine, it starts on :0.  No idea if the lightdm.conf needs a change to
  'start on'clause, or if this is just a case of a bad shipped config
  file (for module 'nv').

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: lightdm 1.1.9-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
  Uname: Linux 3.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu1
  Architecture: amd64
  Date: Fri Mar 30 13:40:27 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 
(20120323)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 942539] Re: Ubiquity desktop icon text looks messy

2012-04-11 Thread James Hunt

This problem appears to be resolved for me on an installed precise
system. Copying bar.desktop to ~/Desktop/ and once I allow the file to
be executable (right click, properties), the icon text shows line 1 as
Install Ubuntu 12.04 and line 2 as LTS.

** Attachment added: bar.desktop
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/942539/+attachment/3047337/+files/bar.desktop

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/942539

Title:
  Ubiquity desktop icon text looks messy

Status in “nautilus” package in Ubuntu:
  Triaged
Status in “ubiquity” package in Ubuntu:
  Triaged

Bug description:
  On a live CD/USB of Ubuntu the icon for Ubiquity looks like this:-

  Install Ubuntu 12.
  04 LTS

  (with the 04 LTS on the second line, and centred).

  It would look more pretty like this:-

  Install Ubuntu
  12.04 LTS

  Can we add a soft carriage return in there, or some other way to make
  it look less disjointed?

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

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

[Desktop-packages] [Bug 954391] Re: something is performing a controlled system shutdown

2012-03-14 Thread James Hunt

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

It's not aliens, it is of course the kernel :)

** This bug has been marked a duplicate of bug 751689
   ThinkPads overheat due to slow fans when on 'auto'

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/954391

Title:
  something is performing a controlled system shutdown

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  I'm not entirely sure where or why this is happening, but I have seen
  on ~5 occasions now my system spontaneously switch off.

  Initially, I thought it might be an init/kernel issue, but today I saw
  the problem occur twice and crucially, I also got to see the console
  and there was no kernel panic - the system was shutting itself down
  cleanly as if the user had typed, sudo shutdown -h now or selected
  shutdown on the Unity panel.

  I'm seeing this on a fully updated Precise system.  I'm wondering what
  higher-level parts of the system might possibly be invoking /usr/lib
  /indicator-session/gtk-logout-helper --shutdown or the D-Bus
  org.freedesktop.ConsoleKit.Manager.Stop() method?

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

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

[Desktop-packages] [Bug 954391] [NEW] something is performing a controlled system shutdown

2012-03-13 Thread James Hunt

Public bug reported:

I'm not entirely sure where or why this is happening, but I have seen on
~5 occasions now my system spontaneously switch off.

Initially, I thought it might be an init/kernel issue, but today I saw
the problem occur twice and crucially, I also got to see the console and
there was no kernel panic - the system was shutting itself down cleanly
as if the user had typed, sudo shutdown -h now or selected shutdown
on the Unity panel.

I'm seeing this on a fully updated Precise system.  I'm wondering what
higher-level parts of the system might possibly be invoking /usr/lib
/indicator-session/gtk-logout-helper --shutdown or the D-Bus
org.freedesktop.ConsoleKit.Manager.Stop() method?

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/954391

Title:
  something is performing a controlled system shutdown

Status in “gnome-session” package in Ubuntu:
  New

Bug description:
  I'm not entirely sure where or why this is happening, but I have seen
  on ~5 occasions now my system spontaneously switch off.

  Initially, I thought it might be an init/kernel issue, but today I saw
  the problem occur twice and crucially, I also got to see the console
  and there was no kernel panic - the system was shutting itself down
  cleanly as if the user had typed, sudo shutdown -h now or selected
  shutdown on the Unity panel.

  I'm seeing this on a fully updated Precise system.  I'm wondering what
  higher-level parts of the system might possibly be invoking /usr/lib
  /indicator-session/gtk-logout-helper --shutdown or the D-Bus
  org.freedesktop.ConsoleKit.Manager.Stop() method?

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

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

[Desktop-packages] [Bug 942530] [NEW] on-screen keyboard always displays once enabled

2012-02-28 Thread James Hunt

Public bug reported:

Whilst investigating bug 937611, I enabled the on-screen keyboard.
However, I subsequently switched if off via System Settings -
Universal Access - Typing tab - Typing Assistant.

As expected, the keyboard no longer displays on the desktop but when the
screen locks automatically or is locked manually, the on-screen keyboard
is displayed again.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-screensaver 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
Uname: Linux 3.2.0-16-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Tue Feb 28 10:28:11 2012
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session idle-delay uint32 600
 org.gnome.desktop.session session-name 'ubuntu'
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: Upgraded to precise on 2012-01-12 (46 days ago)
WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

** Affects: gnome-screensaver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/942530

Title:
  on-screen keyboard always displays once enabled

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  Whilst investigating bug 937611, I enabled the on-screen keyboard.
  However, I subsequently switched if off via System Settings -
  Universal Access - Typing tab - Typing Assistant.

  As expected, the keyboard no longer displays on the desktop but when
  the screen locks automatically or is locked manually, the on-screen
  keyboard is displayed again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screensaver 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  Date: Tue Feb 28 10:28:11 2012
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to precise on 2012-01-12 (46 days ago)
  WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

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

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

[Desktop-packages] [Bug 942530] Re: on-screen keyboard always displays once enabled

2012-02-28 Thread James Hunt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/942530

Title:
  on-screen keyboard always displays once enabled

Status in “gnome-screensaver” package in Ubuntu:
  New

Bug description:
  Whilst investigating bug 937611, I enabled the on-screen keyboard.
  However, I subsequently switched if off via System Settings -
  Universal Access - Typing tab - Typing Assistant.

  As expected, the keyboard no longer displays on the desktop but when
  the screen locks automatically or is locked manually, the on-screen
  keyboard is displayed again.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screensaver 3.2.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
  Uname: Linux 3.2.0-16-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  Date: Tue Feb 28 10:28:11 2012
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 600
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  UpgradeStatus: Upgraded to precise on 2012-01-12 (46 days ago)
  WindowManager: No value set for 
`/desktop/gnome/session/required_components/windowmanager'

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

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

[Desktop-packages] [Bug 874987] Re: PHS101 USB GSM HSDPA can't connect on ubuntu 11.10

2012-02-14 Thread James Hunt

I have a Huawei E220 HSDPA USB Modem which fails with the same assertion
errors as above. I wonder if this is related to bug 840082?

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

Title:
  PHS101 USB GSM HSDPA can't connect on ubuntu 11.10

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  I'm using ubuntu 11.10 in my netbook axioo pico pjm. i'm can't connect
  the PHS101 USB modem after fresh install oneiric today. but this is no
  problem in natty and previous version.

  this is log of syslog:

  Oct 15 19:04:45 coys NetworkManager[746]: info Activation (ttyUSB1) 
starting connection 'Telkomsel'
  Oct 15 19:04:45 coys NetworkManager[746]: info (ttyUSB1): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 15 19:04:45 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 15 19:04:45 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) started...
  Oct 15 19:04:45 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) complete.
  Oct 15 19:04:56 coys NetworkManager[746]: warn GSM connection failed: (32) 
Sending command failed: 'Resource temporarily unavailable'
  Oct 15 19:04:56 coys NetworkManager[746]: info (ttyUSB1): device state 
change: prepare - failed (reason 'unknown') [40 120 1]
  Oct 15 19:04:56 coys NetworkManager[746]: warn Activation (ttyUSB1) failed.
  Oct 15 19:04:56 coys NetworkManager[746]: info (ttyUSB1): device state 
change: failed - disconnected (reason 'none') [120 30 0]
  Oct 15 19:04:56 coys NetworkManager[746]: info (ttyUSB1): deactivating 
device (reason 'none') [0]
  Oct 15 19:04:56 coys NetworkManager[746]: nm_system_iface_flush_routes: 
assertion `ifindex  0' failed
  Oct 15 19:04:56 coys NetworkManager[746]: nm_system_iface_flush_addresses: 
assertion `ifindex  0' failed
  Oct 15 19:04:59 coys NetworkManager[746]: info Auto-activating connection 
'Telkomsel'.
  Oct 15 19:04:59 coys NetworkManager[746]: info Activation (ttyUSB1) 
starting connection 'Telkomsel'
  Oct 15 19:04:59 coys NetworkManager[746]: info (ttyUSB1): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 15 19:04:59 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 15 19:04:59 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) started...
  Oct 15 19:04:59 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) complete.
  Oct 15 19:05:06 coys NetworkManager[746]: warn GSM connection failed: (32) 
Sending command failed: 'Resource temporarily unavailable'
  Oct 15 19:05:06 coys NetworkManager[746]: info (ttyUSB1): device state 
change: prepare - failed (reason 'unknown') [40 120 1]
  Oct 15 19:05:06 coys NetworkManager[746]: warn Activation (ttyUSB1) failed.
  Oct 15 19:05:06 coys NetworkManager[746]: info (ttyUSB1): device state 
change: failed - disconnected (reason 'none') [120 30 0]
  Oct 15 19:05:06 coys NetworkManager[746]: info (ttyUSB1): deactivating 
device (reason 'none') [0]
  Oct 15 19:05:06 coys NetworkManager[746]: nm_system_iface_flush_routes: 
assertion `ifindex  0' failed
  Oct 15 19:05:06 coys NetworkManager[746]: nm_system_iface_flush_addresses: 
assertion `ifindex  0' failed
  Oct 15 19:05:10 coys NetworkManager[746]: info Auto-activating connection 
'Telkomsel'.
  Oct 15 19:05:10 coys NetworkManager[746]: info Activation (ttyUSB1) 
starting connection 'Telkomsel'
  Oct 15 19:05:10 coys NetworkManager[746]: info (ttyUSB1): device state 
change: disconnected - prepare (reason 'none') [30 40 0]
  Oct 15 19:05:10 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) scheduled...
  Oct 15 19:05:10 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) started...
  Oct 15 19:05:10 coys NetworkManager[746]: info Activation (ttyUSB1) Stage 1 
of 5 (Device Prepare) complete.
  Oct 15 19:05:26 coys NetworkManager[746]: warn GSM connection failed: (32) 
Sending command failed: 'Resource temporarily unavailable'
  Oct 15 19:05:26 coys NetworkManager[746]: info (ttyUSB1): device state 
change: prepare - failed (reason 'unknown') [40 120 1]
  Oct 15 19:05:26 coys NetworkManager[746]: warn Activation (ttyUSB1) failed.
  Oct 15 19:05:26 coys NetworkManager[746]: info (ttyUSB1): device state 
change: failed - disconnected (reason 'none') [120 30 0]
  Oct 15 19:05:26 coys NetworkManager[746]: info (ttyUSB1): deactivating 
device (reason 'none') [0]
  Oct 15 19:05:26 coys NetworkManager[746]: nm_system_iface_flush_routes: 
assertion `ifindex  0' failed
  Oct 15 19:05:26 coys NetworkManager[746]: nm_system_iface_flush_addresses: 
assertion `ifindex  0' failed
  Oct 15 19:05:29 coys NetworkManager[746]: info Auto-activating connection

[Desktop-packages] [Bug 840082] Re: Huawei broadband modem fails to connect after the most recent Ocelot update (Sep. 3.2011)

2012-02-14 Thread James Hunt

I have a Huawei E220 HSDPA USB Modem which fails to work with precise.
I'm seeing NM assertion failures in syslog as shown on bug 874987, so
for me this bug is not fixed. Is there some way to disable NM
configureing IPv6 for a connection? There is only an IPv4 tab displayed
when editing the connection in question.

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

Title:
  Huawei broadband modem fails to connect after the most recent Ocelot
  update (Sep. 3.2011)

Status in “network-manager” package in Ubuntu:
  Fix Released

Bug description:
  Huawei broadband modem fails to connect to Tigo, Honduras, after the
  most recent Ocelot update (Sep. 3.2011). 3.0.0.9 Kernel.

  Ocelot finds and recognises the modem, and dials, but it just fails to
  connect to the Internet service. I'm back in Natty now and I'm
  connecting fine. Also, it was connecting without issue (in Ocelot) 10
  minutes ago before the upgrade.

  The update log is attached.

  Any thoughts?

  Regards,

  CaymanPirate

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

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

[Desktop-packages] [Bug 925411] [NEW] dispatcher script 01ifupdown never emits net-device-down

2012-02-02 Thread James Hunt

Public bug reported:

NM runs /etc/NetworkManager/dispatcher.d/01ifupdown when a connection
changes state.

If a connection is made, the dispatcher script runs:

exec run-parts /etc/network/if-up.d

However, when a connection goes down, the dispatcher script runs:

exec run-parts /etc/network/if-post-down.d

Crucially, it does not currently run:

exec run-parts /etc/network/if-down.d

The problem here is that since it runs the post-down scripts, the net-
device-down Upstart event is never emitted. This is emitted though by
/etc/network/if-down.d/upstart.

Should the dispatcher run the if-down.d scripts rather than the if-post-
down.d scripts? Or maybe it should run both?

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.2.0+git201201101813.0b30200-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
Uname: Linux 3.2.0-12-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Thu Feb  2 11:06:29 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static 
 10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 2 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-01-12 (20 days ago)
WifiSyslog:
 
modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [modified]
mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 
2011-11-23T08:49:12.888228
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   
 eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0  
 wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
nmcli-nm:
 RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   WIFI  
 WWAN-HARDWARE   WWAN  
 running 0.9.3.0connected   enabled   enabled 
enabledenabled disabled

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


** Tags: apport-bug i386 precise running-unity

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

Title:
  dispatcher script 01ifupdown never emits net-device-down

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  NM runs /etc/NetworkManager/dispatcher.d/01ifupdown when a connection
  changes state.

  If a connection is made, the dispatcher script runs:

  exec run-parts /etc/network/if-up.d

  However, when a connection goes down, the dispatcher script runs:

  exec run-parts /etc/network/if-post-down.d

  Crucially, it does not currently run:

  exec run-parts /etc/network/if-down.d

  The problem here is that since it runs the post-down scripts, the net-
  device-down Upstart event is never emitted. This is emitted though by
  /etc/network/if-down.d/upstart.

  Should the dispatcher run the if-down.d scripts rather than the if-
  post-down.d scripts? Or maybe it should run both?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.2.0+git201201101813.0b30200-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
  Uname: Linux 3.2.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Thu Feb  2 11:06:29 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-01-12 (20 days ago)
  WifiSyslog:
   
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [modified]
  mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 
2011-11-23T08:49:12.888228
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0  
   wlan0  802-11-wireless   connected

[Desktop-packages] [Bug 925411] Re: dispatcher script 01ifupdown never emits net-device-down

2012-02-02 Thread James Hunt

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

Title:
  dispatcher script 01ifupdown never emits net-device-down

Status in “network-manager” package in Ubuntu:
  New

Bug description:
  NM runs /etc/NetworkManager/dispatcher.d/01ifupdown when a connection
  changes state.

  If a connection is made, the dispatcher script runs:

  exec run-parts /etc/network/if-up.d

  However, when a connection goes down, the dispatcher script runs:

  exec run-parts /etc/network/if-post-down.d

  Crucially, it does not currently run:

  exec run-parts /etc/network/if-down.d

  The problem here is that since it runs the post-down scripts, the net-
  device-down Upstart event is never emitted. This is emitted though by
  /etc/network/if-down.d/upstart.

  Should the dispatcher run the if-down.d scripts rather than the if-
  post-down.d scripts? Or maybe it should run both?

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: network-manager 0.9.2.0+git201201101813.0b30200-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2
  Uname: Linux 3.2.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  Date: Thu Feb  2 11:06:29 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to precise on 2012-01-12 (20 days ago)
  WifiSyslog:
   
  modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: [modified]
  mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 
2011-11-23T08:49:12.888228
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.3.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 922154] [NEW] Tabs and Content tabs in edit-preferences do nothing

2012-01-26 Thread James Hunt

Public bug reported:

1) Edit-preferences
2) click General
3) observer that general options are shown
4) click Tabs or Content and notice that window continues to show general 
options (however long you wait).

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 10.0~b5+build1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1
Uname: Linux 3.2.0-10-generic-pae i686
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: i386
ArecordDevices:
  List of CAPTURE Hardware Devices 
 card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  james 24595 F alsamixer
  james 25302 F mocp
 /dev/snd/pcmC0D0p:   james 25302 F...m mocp
 /dev/snd/timer:  james 25302 f mocp
BuildID: 20120119214859
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 46'
   Mixer name   : 'Conexant CX20585'
   Components   : 'HDA:14f15069,17aa214c,00100302 
HDA:14f12c06,17aa2122,0010'
   Controls  : 9
   Simple ctrls  : 6
Card1.Amixer.info:
 Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
   Mixer name   : 'Nvidia GPU 0b HDMI/DP'
   Components   : 'HDA:10de000b,10de0101,00100100'
   Controls  : 20
   Simple ctrls  : 4
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6IHT37WW-1.12'
   Mixer name   : 'ThinkPad EC 6IHT37WW-1.12'
   Components   : ''
   Controls  : 1
   Simple ctrls  : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Channel: beta
Date: Thu Jan 26 15:43:14 2012
ForcedLayersAccel: False
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
IpRoute:
 default via 192.168.1.1 dev wlan0  proto static 
 10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 2 
 192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=10.0/20120119214859 (Running)
PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 1: 
No PulseAudio daemon running, or not running as session daemon.
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: Upgraded to precise on 2012-01-12 (14 days ago)
dmi.bios.date: 08/27/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET72WW (1.32 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2516CTO
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug beta-channel i386 precise running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/922154

Title:
  Tabs and Content tabs in edit-preferences do nothing

Status in “firefox” package in Ubuntu:
  New

Bug description:
  1) Edit-preferences
  2) click General
  3) observer that general options are shown
  4) click Tabs or Content and notice that window continues to show general 
options (however long you wait).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 10.0~b5+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1
  Uname: Linux 3.2.0-10-generic-pae i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james 24595 F alsamixer
james 25302 F mocp
   /dev/snd/pcmC0D0p:   james 25302 F...m mocp
   /dev/snd/timer:  james 25302 f mocp
  BuildID: 20120119214859
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 46'
 Mixer name :

[Desktop-packages] [Bug 922154] Re: Tabs and Content tabs in edit-preferences do nothing

2012-01-26 Thread James Hunt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/922154

Title:
  Tabs and Content tabs in edit-preferences do nothing

Status in “firefox” package in Ubuntu:
  New

Bug description:
  1) Edit-preferences
  2) click General
  3) observer that general options are shown
  4) click Tabs or Content and notice that window continues to show general 
options (however long you wait).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: firefox 10.0~b5+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1
  Uname: Linux 3.2.0-10-generic-pae i686
  NonfreeKernelModules: nvidia
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.91-0ubuntu1
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james 24595 F alsamixer
james 25302 F mocp
   /dev/snd/pcmC0D0p:   james 25302 F...m mocp
   /dev/snd/timer:  james 25302 f mocp
  BuildID: 20120119214859
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf242 irq 46'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,17aa214c,00100302 
HDA:14f12c06,17aa2122,0010'
 Controls  : 9
 Simple ctrls  : 6
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xcdefc000 irq 16'
 Mixer name : 'Nvidia GPU 0b HDMI/DP'
 Components : 'HDA:10de000b,10de0101,00100100'
 Controls  : 20
 Simple ctrls  : 4
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
6IHT37WW-1.12'
 Mixer name : 'ThinkPad EC 6IHT37WW-1.12'
 Components : ''
 Controls  : 1
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Channel: beta
  Date: Thu Jan 26 15:43:14 2012
  ForcedLayersAccel: False
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   10.0.3.0/24 dev lxcbr0  proto kernel  scope link  src 10.0.3.1 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.2  metric 
2 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=10.0/20120119214859 (Running)
  PulseSinks: Error: command ['pacmd', 'list-sinks'] failed with exit code 1: 
No PulseAudio daemon running, or not running as session daemon.
  PulseSources: Error: command ['pacmd', 'list-sources'] failed with exit code 
1: No PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  UpgradeStatus: Upgraded to precise on 2012-01-12 (14 days ago)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET72WW (1.32 )
  dmi.board.name: 2516CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2516CTO
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 917165] Re: gnome-control-center does not allow selection of USB headset for input or output

2012-01-17 Thread James Hunt

Hmm after a reboot, the problem appears to have gone away. My selected
h/w profile is Analogue Stereo Output + Analogue Mono Input (which has
not changed).

There are a couple of extra odd things going on here:

1) if I change the h/w profile for the headset to Analogue Stereo
Output and switch to the Output tab, the selected device is Internal
Audio Analogue Stereo (!), and yet the sound is still coming out of my
headset! And no sound is emitted by my internal speakers or via the
headphone socket. Additionally, I now have no control over the volume:
changing the sliders does nothing.

2) Selecting Analogue Mono Output for the headset device degrades the
sound quality significantly (I can hear a lot of crackling mixed in with
the sound).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/917165

Title:
  gnome-control-center does not allow selection of USB headset for input
  or output

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  If I plug in my Logitech H530 USB Headset, it shows as ClearChat Pro
  USB under Hardware in 'gnome-control-center sound', but it does *not*
  show up as a valid input or output device if I click either the Input
  or Output tabs.

  On the input tab, the Connector menu only has 1 entry: Analogue
  Input.

  This is a regression since Oneiric where it worked flawlessly.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.2.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
  Uname: Linux 3.2.0-8-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.90-0ubuntu2
  Architecture: i386
  Date: Mon Jan 16 11:28:44 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to precise on 2012-01-12 (4 days ago)
  usr_lib_gnome-control-center:
   deja-dup   21.2-0ubuntu3
   gnome-bluetooth3.2.1-1ubuntu3
   indicator-datetime 0.3.1-0ubuntu3

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

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

[Desktop-packages] [Bug 917165] [NEW] gnome-control-center does not allow selection of USB headset for input or output

2012-01-16 Thread James Hunt

Public bug reported:

If I plug in my Logitech H530 USB Headset, it shows as ClearChat Pro
USB under Hardware in 'gnome-control-center sound', but it does *not*
show up as a valid input or output device if I click either the Input or
Output tabs.

On the input tab, the Connector menu only has 1 entry: Analogue
Input.

This is a regression since Oneiric where it worked flawlessly.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.2.2-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
Uname: Linux 3.2.0-8-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu2
Architecture: i386
Date: Mon Jan 16 11:28:44 2012
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to precise on 2012-01-12 (4 days ago)
usr_lib_gnome-control-center:
 deja-dup   21.2-0ubuntu3
 gnome-bluetooth3.2.1-1ubuntu3
 indicator-datetime 0.3.1-0ubuntu3

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 precise running-unity

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/917165

Title:
  gnome-control-center does not allow selection of USB headset for input
  or output

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  If I plug in my Logitech H530 USB Headset, it shows as ClearChat Pro
  USB under Hardware in 'gnome-control-center sound', but it does *not*
  show up as a valid input or output device if I click either the Input
  or Output tabs.

  On the input tab, the Connector menu only has 1 entry: Analogue
  Input.

  This is a regression since Oneiric where it worked flawlessly.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.2.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
  Uname: Linux 3.2.0-8-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.90-0ubuntu2
  Architecture: i386
  Date: Mon Jan 16 11:28:44 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to precise on 2012-01-12 (4 days ago)
  usr_lib_gnome-control-center:
   deja-dup   21.2-0ubuntu3
   gnome-bluetooth3.2.1-1ubuntu3
   indicator-datetime 0.3.1-0ubuntu3

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

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

[Desktop-packages] [Bug 917165] Re: gnome-control-center does not allow selection of USB headset for input or output

2012-01-16 Thread James Hunt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/917165

Title:
  gnome-control-center does not allow selection of USB headset for input
  or output

Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  If I plug in my Logitech H530 USB Headset, it shows as ClearChat Pro
  USB under Hardware in 'gnome-control-center sound', but it does *not*
  show up as a valid input or output device if I click either the Input
  or Output tabs.

  On the input tab, the Connector menu only has 1 entry: Analogue
  Input.

  This is a regression since Oneiric where it worked flawlessly.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.2.2-2ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-8.15-generic-pae 3.2.0
  Uname: Linux 3.2.0-8-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.90-0ubuntu2
  Architecture: i386
  Date: Mon Jan 16 11:28:44 2012
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to precise on 2012-01-12 (4 days ago)
  usr_lib_gnome-control-center:
   deja-dup   21.2-0ubuntu3
   gnome-bluetooth3.2.1-1ubuntu3
   indicator-datetime 0.3.1-0ubuntu3

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

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

[Desktop-packages] [Bug 890903] Re: terminal contents don't refresh/update

2011-11-18 Thread James Hunt

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

** This bug has been marked a duplicate of bug 861268
   text corruption in terminals (xterm, urxvt) and emacs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/890903

Title:
  terminal contents don't refresh/update

Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  1. open a terminal.
  2. ssh to machine1.
  3. ssh to machine2 from machine1.

  see that the screen is now not refreshed properly.
  i've even seen this bug when I open vi and only a local part of the screen is 
refreshed.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Tue Nov 15 17:35:58 2011
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (32 days ago)

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

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

[Desktop-packages] [Bug 888008] [NEW] print to file defaults to PostScript when it should probably default to PDF

2011-11-09 Thread James Hunt

Public bug reported:

File-Print-Print to file defaults to output format PostScript.
Although I'm a big fan of PostScript (even having programmed in it), I
think PDF should be the default now since:

(1) the resulting files are smaller (being compressed)
(2) standard desktop tooling handles PDF widely
(3) almost everyone knowns what a PDF file is (whereas the same is not true of 
PostScript).

I think (3) is the most important aspect here.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/888008

Title:
  print to file defaults to PostScript when it should probably default
  to PDF

Status in “firefox” package in Ubuntu:
  New

Bug description:
  File-Print-Print to file defaults to output format PostScript.
  Although I'm a big fan of PostScript (even having programmed in it), I
  think PDF should be the default now since:

  (1) the resulting files are smaller (being compressed)
  (2) standard desktop tooling handles PDF widely
  (3) almost everyone knowns what a PDF file is (whereas the same is not true 
of PostScript).

  I think (3) is the most important aspect here.

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

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

1 2 >

1 - 100 of 116 matches

Mail list logo