[Desktop-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send

[Tomas Öqvist]

After looking into the apns-conf.xml on the device, I previously noted
that settings for Tele2 Sweden did not quite match the APN settings for
Nexus 4 recommended by the carrier. Strangely enough, sending MMS still
works. See settings comparison below, the most notable differences being
MNC and APN type. I did try changing the APN settings and putting an
edited copy of apns-conf.xml in /custom/etc/ earlier, but that didn't
make any difference for receiving MMS.

Ubuntu Touch RTM:
http://mmsc.tele2.se";
  mmsproxy="130.244.202.30"
  mmsport="8080"
  type="mms"
  mvno_match_data="Tele2"
  mvno_type="spn"
  />

Tele2 Sweden MMS suggested settings for Nexus 4:
Name - Tele2 
APN - 4g.tele2.se 
Proxy - TBD (not determined)
Port - TBD 
Username - TBD 
Password - TBD 
MMSC - http://mmsc.tele2.se 
MMS proxy - 130.244.202.30 
MMS port - 8080 
MCC - 240 
MNC - 07 
Authentication type - TBD 
APN type - default, supl, mms 
APN protocol - IPv4 
APN roaming protocol - IPv4

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

Title:
  Can't receive MMS despite ability to send

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

Bug description:
  I can send MMS (and they actually come through to the recipient), but
  I can't receive MMS. I am not sure if this is an APN settings issue,
  but I would have thought it either worked both ways or not at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+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 1080787] Re: hp scanner 5300c does no longer work after upgrading to quantal

[mgfrobozz]

** Attachment added: "patch_1080787.txt"
   
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1080787/+attachment/4215681/+files/patch_1080787.txt

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

Title:
  hp scanner 5300c does no longer work after upgrading to quantal

Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  on 12.10 the scanner doesn't work anymore.
  on 12.04 it worked on the same machine.
  the scanner still works on a second machine that was not upgraded by now.

  
  uname:
  Linux matrix 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release:
  Description:  Ubuntu 12.10
  Release:  12.10

  versions:
  sane: 1.0.14-9
  libsane: 1.0.23-0ubuntu1

  dmesg:
  [12883.928037] usb 3-6: >new full-speed USB device number 23 using ohci_hcd
  [12884.157054] usb 3-6: >New USB device found, idVendor=03f0, idProduct=0701
  [12884.157059] usb 3-6: >New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [12884.157062] usb 3-6: >Product: Hewlett Packard ScanJet 5300C/5370C 
  [12884.157064] usb 3-6: >Manufacturer: Hewlett Packard
  [12884.157067] usb 3-6: >SerialNumber: 

  lsusb:
  Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
  Bus 003 Device 023: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c
  Bus 004 Device 002: ID 08e6:3437 Gemplus GemPC Twin SmartCard Reader
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  scanimage -Lv
  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1080787/+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 1374285] Re: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1229021, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215667/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215669/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215672/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215673/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215674/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215677/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374285/+attachment/4215678/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1229021
   chromium-browser crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()

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

Bug description:
  I'm not sure when exactly this happened - the browser is still up

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 26 07:57:32 2014
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  ProcCmdline: chromium-browser\ --type=gpu-process\ 
--channel=13711.0.1660615688\ --supports-dual-gpus=false\ 
--gpu-driver-bug-workarounds=1,15,22\ --disable-accelerated-video-decode\ 
--gpu-vendor-id=0x1002\ --gpu-device-id=0x9614\ --gpu-driver-vendor\ 
--gpu-driver-versi
  SegvAnalysis:
   Segfault happened at: 0x7f0fd23c6d98:movl   $0x1337,0x0
   PC (0x7f0fd23c6d98) ok
   source "$0x1337" ok
   destination "0x0" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: chromium-browser
  StacktraceTop:
   ?? () from /usr/lib/chromium-browser/libs/libcontent.so
   base::MessageLoop::RunTask(base::PendingTask const&) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DeferOrRunPendingTask(base::PendingTask const&) () from 
/usr/lib/chromium-browser/libs/libbase.so
   base::MessageLoop::DoDelayedWork(base::TimeTicks*) () from 
/usr/lib/chromium-browser/libs/libbase.so
   ?? () from /usr/lib/chromium-browser/libs/libbase.so
  Title: chromium-browser crashed with SIGSEGV in base::MessageLoop::RunTask()
  UpgradeStatus: Upgraded to trusty on 2014-08-29 (27 days ago)
  UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd 
lpadmin netdev plugdev pulse sambashare saned tape vboxusers video
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-08-30T00:07:57.340239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1374285/+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 1318360] Re: Poor microphone quality (mako)

[Tomas Öqvist]

I guess that Android applies some kind of filter to prevent the
distortion somehow picked up by the mic. Sound gets worse if I speak in
a louder voice and the output at the other end is apparantly very loud
also. As Nexus 4 is still the main phone used for Ubuntu Touch, I
believe the platform would benefit greatly if this issue could be solved
sooner than later.

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

Title:
  Poor microphone quality (mako)

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  After months of complaints from people talking to me on the phone
  (mako ubuntu touch), I finally got around to use multiROM to dual boot
  Ubuntu Touch and Android. Several people can confirm that there is a
  noticable difference in terms of sound/microphone quality between
  Android and UT in phone calls. With UT, my voice gets distorted to an
  extent that person at the other end have real difficulties to hear
  what I am saying, while with Android call quality is much better with
  no distortion.

  I have had a suspicion for a long time that this might be a software
  and not a hardware issue. After trying Android and Ubuntu on the same
  hardware I believe this suspicion is proved correct. This issue has
  persisted in all the builds I have tried since at least the beginning
  of the year, but probably longer. I am now at r17 of Utopic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1318360/+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 1080787] Re: hp scanner 5300c does no longer work after upgrading to quantal

[mgfrobozz]

File "patch_1080787.txt" (reverting SHA1 fec4800d7d) fixes the problem in my 
system, using this procedure ...

sudo apt-get install libusb-dev
git clone git://git.debian.org/sane/sane-backends.git
cd sane-backends 
./configure BACKENDS="avision"
patch -p1 < ~/Downloads/patch_1080787.txt
make
lib_dir=/usr/lib/x86_64-linux-gnu/sane
sudo cp backend/.libs/libsane-avision.so.1.0.25 $lib_dir
sudo ln -f -s libsane-avision.so.1.0.25 $lib_dir/libsane-avision.so.1

Set lib_dir to the system directory containing libsane-avision.so.1 (this will 
be different in a 32-bit system). After doing this, test using ...

> scanimage -L
device `avision:libusb:005:057' is a Hewlett-Packard ScanJet 5370C flatbed 
scanner
# and then ...
> simple-scan

Note that if you use a non-functional version of libsane-avision.so (eg 
1.0.23), 
you will need to disconnect and reconnect scanner's usb cable before a 
functional version (1.0.22 or the patched 1.0.25) will work.

My system is ...

> cat /etc/lsb-release 
...
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
> uname -oirv
3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 
GNU/Linux
> lsusb
...
Bus 005 Device 054: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c
...

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

Title:
  hp scanner 5300c does no longer work after upgrading to quantal

Status in “sane-backends” package in Ubuntu:
  Confirmed

Bug description:
  on 12.10 the scanner doesn't work anymore.
  on 12.04 it worked on the same machine.
  the scanner still works on a second machine that was not upgraded by now.

  
  uname:
  Linux matrix 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux

  lsb_release:
  Description:  Ubuntu 12.10
  Release:  12.10

  versions:
  sane: 1.0.14-9
  libsane: 1.0.23-0ubuntu1

  dmesg:
  [12883.928037] usb 3-6: >new full-speed USB device number 23 using ohci_hcd
  [12884.157054] usb 3-6: >New USB device found, idVendor=03f0, idProduct=0701
  [12884.157059] usb 3-6: >New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [12884.157062] usb 3-6: >Product: Hewlett Packard ScanJet 5300C/5370C 
  [12884.157064] usb 3-6: >Manufacturer: Hewlett Packard
  [12884.157067] usb 3-6: >SerialNumber: 

  lsusb:
  Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
  Bus 003 Device 023: ID 03f0:0701 Hewlett-Packard ScanJet 5300c/5370c
  Bus 004 Device 002: ID 08e6:3437 Gemplus GemPC Twin SmartCard Reader
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  scanimage -Lv
  No scanners were identified. If you were expecting something different,
  check that the scanner is plugged in, turned on and detected by the
  sane-find-scanner tool (if appropriate). Please read the documentation
  which came with this software (README, FAQ, manpages).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1080787/+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 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly

[Wiktor: Nizio]

Is is still not fixed on my machine. I use two full HD monitors on
Compiz 0.9.12 with Ubuntu 14.10. When I play VirtualbBox on 2nd (right)
monitor, its left edge is right in the middle of the physical screen.

I have downloaded all up to date packages from their corresponding
repositories and rebooted the machine.

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

Title:
  _NET_WM_FULLSCREEN_MONITORS not handled correctly

Status in Compiz:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  PrivateWindow::setFullscreenMonitors() contains the following:

  CompRect fsRect (screen->outputDevs ()[monitors->left].x1 (),
   screen->outputDevs ()[monitors->top].y1 (),
   screen->outputDevs ()[monitors->right].x2 (),
   screen->outputDevs ()[monitors->bottom].y2 ());

  However, the prototype is:

  CompRect::CompRect (int x, int y, int width, int height)

  This causes Compiz to miscalculate the dimensions of a full-screen
  window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1
  Uname: Linux 3.15.8-031508-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  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: Wed Aug  6 22:18:39 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05cb]
  InstallationDate: Installed on 2014-08-01 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Aug  6 15:17:04 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4413 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1353675/+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 1369673] Re: LibreOffice kde file dialog integration broken (not working) in 14.04

[Mads Bondo Dydensborg]

Thanks, Björn.

That is highly relevant information.

I will personally run the risk, as the file dialog is really important
to me, but others may not want to.

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

Title:
  LibreOffice kde file dialog integration broken (not working) in 14.04

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Screenshot: http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-kde (not installed)
  Uname: Linux 3.16.2-031602-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Sep 15 19:17:48 2014
  InstallationDate: Installed on 2014-02-02 (224 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673/+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 1374269] [NEW] nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

[Nathaniel Meyer]

Public bug reported:

Occurred during regular system update.  My other computer also had this
bug, it becaame unstable afterwards, and I am unable to boot it to
troubleshoot.  This one works for now, but I haven't rebooted.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.38-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
DKMSKernelVersion: 3.13.0-36-generic
Date: Thu Sep 25 21:07:05 2014
InstallationDate: Installed on 2014-05-30 (118 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageVersion: 331.38-0ubuntu7.1
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build

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

Bug description:
  Occurred during regular system update.  My other computer also had
  this bug, it becaame unstable afterwards, and I am unable to boot it
  to troubleshoot.  This one works for now, but I haven't rebooted.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.38-0ubuntu7.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-36-generic
  Date: Thu Sep 25 21:07:05 2014
  InstallationDate: Installed on 2014-05-30 (118 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 331.38-0ubuntu7.1
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.38-0ubuntu7.1: nvidia-331 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1374269/+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 1374271] [NEW] Segfault when using %stdin

[Edward Z. Yang]

Public bug reported:

Steps to reproduce:

1. Run 'gs %stdin'

Expected result: Ghostscript waits to receive input on stdin

Actual result: Ghostscript segfaults

Here's the stacktrace from GDB:

Program received signal SIGSEGV, Segmentation fault.
stdin_open (iodev=0x62f100, access=0x77503d99 "r", ps=0x7fffbe88, 
mem=0x604778) at ./psi/ziodevsc.c:123
123 ./psi/ziodevsc.c: No such file or directory.
(gdb) bt
#0  stdin_open (iodev=0x62f100, access=0x77503d99 "r", ps=0x7fffbe88, 
mem=0x604778) at ./psi/ziodevsc.c:123
#1  0x771e913b in zlibfile (i_ctx_p=i_ctx_p@entry=0x655d48) at 
./psi/zfile.c:603
#2  0x771f1a48 in specific_vm_op (i_ctx_p=0x655d48, 
opproc=0x771e90a0 , space=) at ./psi/zsysvm.c:40
#3  0x771d7ee2 in interp (pi_ctx_p=pi_ctx_p@entry=0x6033f0, 
pref=, perror_object=perror_object@entry=0x7fffd010) at 
./psi/interp.c:1561
#4  0x771d8999 in gs_call_interp (perror_object=0x7fffd010, 
pexit_code=0x7fffd00c, user_errors=1, pref=0x7fffceb0, 
pi_ctx_p=0x603490) at ./psi/interp.c:510
#5  gs_interpret (pi_ctx_p=pi_ctx_p@entry=0x6033f0, 
pref=pref@entry=0x7fffcfe0, user_errors=1, user_errors@entry=-12272, 
pexit_code=0x7fffd00c, perror_object=0x7fffd010) at ./psi/interp.c:468
#6  0x771cdd49 in gs_main_interpret (perror_object=, 
pexit_code=, user_errors=-12272, pref=0x7fffcfe0, 
minst=) at ./psi/imain.c:241
#7  gs_main_run_string_end (minst=minst@entry=0x603350, user_errors=, pexit_code=pexit_code@entry=0x7fffd00c, 
perror_object=perror_object@entry=0x7fffd010) at ./psi/imain.c:621
#8  0x771cddce in gs_main_run_string_with_length 
(minst=minst@entry=0x603350, str=str@entry=0x976c50 "<25737464696e>.runfile", 
length=, user_errors=, 
pexit_code=pexit_code@entry=0x7fffd00c, 
perror_object=perror_object@entry=0x7fffd010) at ./psi/imain.c:579
#9  0x771cde0d in gs_main_run_string (minst=minst@entry=0x603350, 
str=str@entry=0x976c50 "<25737464696e>.runfile", user_errors=, 
pexit_code=pexit_code@entry=0x7fffd00c, 
perror_object=perror_object@entry=0x7fffd010) at ./psi/imain.c:561
#10 0x771cf219 in run_string (minst=minst@entry=0x603350, 
str=str@entry=0x976c50 "<25737464696e>.runfile", options=options@entry=3) at 
./psi/imainarg.c:897
#11 0x771cf398 in runarg (minst=0x603350, pre=0x77506f7d "", 
arg=, post=0x7747e40d ".runfile", options=3) at 
./psi/imainarg.c:887
#12 0x771d086b in gs_main_init_with_args (minst=0x603350, argc=2, 
argv=0x7fffdbf8) at ./psi/imainarg.c:233
#13 0x004009bb in main (argc=2, argv=0x7fffdbf8) at 
./psi/dxmainc.c:86
 
Don't know if this is upstream bug, I haven't build a more recent version to 
check.

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

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

Title:
  Segfault when using %stdin

Status in “ghostscript” package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Run 'gs %stdin'

  Expected result: Ghostscript waits to receive input on stdin

  Actual result: Ghostscript segfaults

  Here's the stacktrace from GDB:

  Program received signal SIGSEGV, Segmentation fault.
  stdin_open (iodev=0x62f100, access=0x77503d99 "r", ps=0x7fffbe88, 
mem=0x604778) at ./psi/ziodevsc.c:123
  123   ./psi/ziodevsc.c: No such file or directory.
  (gdb) bt
  #0  stdin_open (iodev=0x62f100, access=0x77503d99 "r", ps=0x7fffbe88, 
mem=0x604778) at ./psi/ziodevsc.c:123
  #1  0x771e913b in zlibfile (i_ctx_p=i_ctx_p@entry=0x655d48) at 
./psi/zfile.c:603
  #2  0x771f1a48 in specific_vm_op (i_ctx_p=0x655d48, 
opproc=0x771e90a0 , space=) at ./psi/zsysvm.c:40
  #3  0x771d7ee2 in interp (pi_ctx_p=pi_ctx_p@entry=0x6033f0, 
pref=, perror_object=perror_object@entry=0x7fffd010) at 
./psi/interp.c:1561
  #4  0x771d8999 in gs_call_interp (perror_object=0x7fffd010, 
pexit_code=0x7fffd00c, user_errors=1, pref=0x7fffceb0, 
pi_ctx_p=0x603490) at ./psi/interp.c:510
  #5  gs_interpret (pi_ctx_p=pi_ctx_p@entry=0x6033f0, 
pref=pref@entry=0x7fffcfe0, user_errors=1, user_errors@entry=-12272, 
pexit_code=0x7fffd00c, perror_object=0x7fffd010) at ./psi/interp.c:468
  #6  0x771cdd49 in gs_main_interpret (perror_object=, 
pexit_code=, user_errors=-12272, pref=0x7fffcfe0, 
minst=) at ./psi/imain.c:241
  #7  gs_main_run_string_end (minst=minst@entry=0x603350, 
user_errors=, pexit_code=pexit_code@entry=0x7fffd00c, 
perror_object=perror_object@entry=0x7fffd010) at ./psi/imain.c:621
  #8  0x771cddce in gs_main_run_string_with_length 
(minst=minst@entry=0x603350, str=str@entry=0x976c50 "<25737464696e>.runfile", 
length=, user_errors=, 
pexit_code=pexit_code@entry=0x7fffd00c, 
perror_object=perror_object@entry=0x7fffd010) at ./psi/ima

[Desktop-packages] [Bug 1289730] Re: systemd-udev fails to execute alsactl during start-up if /usr and/or /var are separate volumes

[z_mikowski]

I have confirmed that the solution proposed in comment #6 completely
resolves this issue.  Can this be included in 14.10 perhaps?

** Changed in: alsa-utils (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  systemd-udev fails to execute alsactl during start-up if /usr and/or
  /var are separate volumes

Status in “alsa-utils” package in Ubuntu:
  Confirmed

Bug description:
  During system startup systemd-udev will print the following error
  messages:

  [   15.089778] systemd-udevd[683]: failed to execute '/usr/sbin/alsactl' 
'/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0': No such file or directory
  [   15.090130] systemd-udevd[684]: failed to execute '/usr/sbin/alsactl' 
'/usr/sbin/alsactl -E HOME=/var/run/alsa restore 1': No such file or directory

  alsactl is present:

  $ which alsactl
  /usr/sbin/alsactl

  but on a separate partition:
  $ df -h /usr/sbin/alsactl 
  DateisystemGröße Benutzt Verf. Verw% Eingehängt auf
  /dev/mapper/scaleo-usr   12G6,6G  4,1G   62% /usr

  $ df -h /var
  DateisystemGröße Benutzt Verf. Verw% Eingehängt auf
  /dev/mapper/scaleo-var  7,3G2,5G  4,4G   37% /var

  This suggests that systemd-udev is called before all local partitions
  have been mounted.

  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy udev
  udev:
Installiert:   204-5ubuntu13
Installationskandidat: 204-5ubuntu13
Versionstabelle:
   *** 204-5ubuntu13 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Kind regards,
Dominik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1289730/+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 1289730] Re: systemd-udev fails to execute alsactl during start-up if /usr and/or /var are separate volumes

[z_mikowski]

Hey gang, I'm still seeing this on 14.04.  I'm sorry there hasn't been
"activity" for 60 days, but this bug is still very real and annoying.
Can we reopen it?

This shouldn't be happening, and it is disconcerting for less
experienced users who think their system is broken when (apparently) it
really isn't.

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

Title:
  systemd-udev fails to execute alsactl during start-up if /usr and/or
  /var are separate volumes

Status in “alsa-utils” package in Ubuntu:
  Confirmed

Bug description:
  During system startup systemd-udev will print the following error
  messages:

  [   15.089778] systemd-udevd[683]: failed to execute '/usr/sbin/alsactl' 
'/usr/sbin/alsactl -E HOME=/var/run/alsa restore 0': No such file or directory
  [   15.090130] systemd-udevd[684]: failed to execute '/usr/sbin/alsactl' 
'/usr/sbin/alsactl -E HOME=/var/run/alsa restore 1': No such file or directory

  alsactl is present:

  $ which alsactl
  /usr/sbin/alsactl

  but on a separate partition:
  $ df -h /usr/sbin/alsactl 
  DateisystemGröße Benutzt Verf. Verw% Eingehängt auf
  /dev/mapper/scaleo-usr   12G6,6G  4,1G   62% /usr

  $ df -h /var
  DateisystemGröße Benutzt Verf. Verw% Eingehängt auf
  /dev/mapper/scaleo-var  7,3G2,5G  4,4G   37% /var

  This suggests that systemd-udev is called before all local partitions
  have been mounted.

  $ lsb_release -rd
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04

  $ apt-cache policy udev
  udev:
Installiert:   204-5ubuntu13
Installationskandidat: 204-5ubuntu13
Versionstabelle:
   *** 204-5ubuntu13 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  Kind regards,
Dominik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1289730/+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 1311515] Re: Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

[Launchpad Bug Tracker]

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

** Changed in: xserver-xorg-input-synaptics (Ubuntu)
   Status: New => Confirmed

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

Title:
  Touchpad pinch zoom-in/zoom-out detection is sometimes reversed

Status in “xserver-xorg-input-synaptics” package in Ubuntu:
  Confirmed

Bug description:
  [Test details]
  Image: 14.04 LTS
  Platforms:
  ThinkPad-Edge-E531:~$ dmesg | grep -i syn
  [4.135984] hda_codec: Enable sync_write for stable communication
  [4.846020] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 
0x1e2b1, caps: 0xd001a3/0x940300/0x127c00, board id: 2722, fw id: 1310036
  [4.846024] psmouse serio1: synaptics: serio: Synaptics pass-through port 
at isa0060/serio1/input0
  [4.906051] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input6

  [Steps]
  1. install image kittyhawk-trusty-amd64-iso-20140314-1.iso via bootable USB 
or DVD
  2. launch google maps in web browser
  3. pinch touchpad with two fingers and see if map zooms in & out accordingly

  [Expected result]
  map should zoom-in when user pinches two fingers apart, zoom-out when user 
pinches two fingers together.

  [Actual result]
  sometimes zoom in & out behavior is reversed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1311515/+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 1365769] Re: [pulseaudio-discuss] [V4 PATCH] module-switch-on-connect: add an argument for conditionally connecting

[Raymond]

>> >>
>> >> >
>> >> > On a machine without fixed connecting audio devices like internal
>> >> > microphone or internal speaker, and when there is no external audio
>> >> > devices plugging in, the default source/sink is
alsa_input/alsa_output
>> >> > and there is no input devices/output devices listed in the gnome
>> >> > sound-setting.
>>
>> https://launchpadlibrarian.net/184055917/PulseList.txt
>>
>> Seem line in is active port when all ports are not available
>> Pulseaudio won't switch away from line in but gnome won't show line in
since it is not plugged
>>
>> ports:
>> analog-input-microphone-front: Front Microphone (priority 8500, latency
offset 0 usec, available: no)
>> properties:
>> device.icon_name = "audio-input-microphone"
>> analog-input-microphone-rear: Rear Microphone (priority 8200, latency
offset 0 usec, available: no)
>> properties:
>> device.icon_name = "audio-input-microphone"
>> analog-input-linein: Line In (priority 8100, latency offset 0 usec,
available: no)
>> properties:
>>
>> active port: 
>
> Yes, in this situation, the default-source->active_port->available=no, if
you use this module and pass "only_from_unavailable=yes", when connect
bluetooth headset, the default source will automatically switch to
bluez-source.
>
> In this situation, if you plug something in the line-in jack, the
default-source->active_port-available=yes, and if you pass
"only_from_unavailable=yes", the default source will not switch.
>>
>> https://launchpadlibrarian.net/184417469/alsa2.txt
>>
>>

>I do not have the hda-jack-sense-test command.

>I  was not aware that I was overriding the pcm.default. Is it worth
changing this to see if the bug goes away? How would I do that?

Seem upgrade does not remove previous conf

System wide config file (/etc/asound.conf)

## /etc/asound.conf ##
pcm.!default {
   type plug
   slave.pcm "asymed"
}

pcm.asymed {
   type asym
   playback.pcm "swmixer"
   capture.pcm "mixin"
}

pcm.dsp0 {
   type plug
   slave.pcm "asymed"
}

pcm.swmixer {
   type dmix
   ipc_key 1234
   slowptr yes
   slave {
   pcm "hw:0,0"
   period_time 0
   period_size 1024
   buffer_size 4096
   rate 48000
   }
}

ctl.dmixer {
   type hw
   card 0
}

pcm.mixin {
   type dsnoop
   ipc_key 5978293 # must be unique for all dmix plugins
   ipc_key_add_uid yes
   slave {
   pcm "hw:0,0"
   channels 2
   period_size 1024
   buffer_size 4096
   rate 48000
   periods 0
   period_time 0
   }
   bindings {
   0 0
   0 1
   }
}


> Do I need to build my own version of the kernel to disable jack detection?

https://launchpad.net/~diwic/+archive/ubuntu/hda

Install snd-hda-tools and run hda-jack-sense-test to find out whether rear
Mic Jack , line in and front Mic report correct Jack state when you plugged
and unplugged

If it work in windows, you may need to file an upstream bug report

If rear Mic Jack cannot report correct Jack state,

The workaround is disable Jack detection of rear Mic jack by hda-jack-
retask

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  Upgr

[Desktop-packages] [Bug 1306507] Re: 网络连接默认名称"Wired connection 1"-应汉化 - Network indicator is not localizing connection names

[Anthony Wong]

** Tags added: l10n

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

Title:
  网络连接默认名称"Wired connection 1"-应汉化 - Network indicator is not localizing
  connection names

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

Bug description:
  系统测试版本：UK14.04-Daily-0410-i386
  网络连接默认名称"Wired connection 1"-应汉化，应和新建网络的默认名称一样：“有线连接 *”。

  --

  Network indicator is not localizing connection names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1306507/+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 1306513] Re: 计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Kylin live session

[Anthony Wong]

** Tags added: l10n

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

Title:
  计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Kylin
  live session

Status in Ubuntu Translations:
  New
Status in Ubuntu Kylin:
  Triaged
Status in “gnome-calculator” package in Ubuntu:
  New

Bug description:
  系统测试版本：UK14.04-Daily-0410-i386
  计算器-编辑&帮助下拉框汉化不全。

  gnome-calculator menu is not translated under Kylin live session

  see screenshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1306513/+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 1321350] Re: Trash applet don't change the 'full icon' after the system disconnect a USB driver in Ubuntu 14.04

[antonioni]

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

This is a old bug never fixed. There is a similar and old bug here:

https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/269441

** This bug has been marked a duplicate of bug 269441
   Trash always full

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

Title:
  Trash applet don't change the 'full icon' after the system disconnect
  a USB driver in Ubuntu 14.04

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  After than I work with files in a USB pendrive and I disconnect the
  device from the USB port, if I have files in the trash applet and I
  delete then from the trash, the "full icon" of trash applet don't
  change to the "empty icon".

  The icon only changes correctly when the system is logged out or restarted.
  Steps:

  1. Plug a USB pendrive;
  2. Work with some files on this pendrive (create, move and delete to trash);
  3. Remove safety the pendrive;
  4. Empty the trash;
  5. The icon continues "full", even when the trash folder is empty.

  (Obs.: this problem don't occur every time.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1321350/+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 1365769] Re: [pulseaudio-discuss] [V4 PATCH] module-switch-on-connect: add an argument for conditionally connecting

[Hui Wang]

On 09/26/2014 12:13 AM, Raymond Yau wrote:
>
>
> >>
> >> >
> >> > On a machine without fixed connecting audio devices like internal
> >> > microphone or internal speaker, and when there is no external audio
> >> > devices plugging in, the default source/sink is 
> alsa_input/alsa_output
> >> > and there is no input devices/output devices listed in the gnome
> >> > sound-setting.
>
> https://launchpadlibrarian.net/184055917/PulseList.txt
>
> Seem line in is active port when all ports are not available
> Pulseaudio won't switch away from line in but gnome won't show line in 
> since it is not plugged
>
> ports:
> analog-input-microphone-front: Front Microphone (priority 8500, 
> latency offset 0 usec, available: no)
> properties:
> device.icon_name = "audio-input-microphone"
> analog-input-microphone-rear: Rear Microphone (priority 8200, latency 
> offset 0 usec, available: no)
> properties:
> device.icon_name = "audio-input-microphone"
> analog-input-linein: Line In (priority 8100, latency offset 0 usec, 
> available: no)
> properties:
>
> active port: 
>
Yes, in this situation, the default-source->active_port->available=no, 
if you use this module and pass "only_from_unavailable=yes", when 
connect bluetooth headset, the default source will automatically switch 
to bluez-source.

In this situation, if you plug something in the line-in jack, the 
default-source->active_port-available=yes, and if you pass 
"only_from_unavailable=yes", the default source will not switch.
>
> https://launchpadlibrarian.net/184417469/alsa2.txt
>
>
>
> ___
> pulseaudio-discuss mailing list
> pulseaudio-disc...@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1353675] Re: _NET_WM_FULLSCREEN_MONITORS not handled correctly

[Launchpad Bug Tracker]

This bug was fixed in the package compiz -
1:0.9.12+14.10.20140918-0ubuntu1

---
compiz (1:0.9.12+14.10.20140918-0ubuntu1) utopic; urgency=low

  [ Michael Thayer ]
  * Fix for LP #1353675: _NET_WM_FULLSCREEN_MONITORS not handled
correctly. An (x, y, w, h) (LP: #1353675)

  [ Alberts Muktupāvels ]
  * Port gtk-window-decorator to GTK+ 3.
  * Re-enable metacity theme support (LP: #1356981)
  * Remove/replace deprecated functions. (LP: #1356981)
 -- Ubuntu daily releaseThu, 18 Sep 2014 
11:01:08 +

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

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

Title:
  _NET_WM_FULLSCREEN_MONITORS not handled correctly

Status in Compiz:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  PrivateWindow::setFullscreenMonitors() contains the following:

  CompRect fsRect (screen->outputDevs ()[monitors->left].x1 (),
   screen->outputDevs ()[monitors->top].y1 (),
   screen->outputDevs ()[monitors->right].x2 (),
   screen->outputDevs ()[monitors->bottom].y2 ());

  However, the prototype is:

  CompRect::CompRect (int x, int y, int width, int height)

  This causes Compiz to miscalculate the dimensions of a full-screen
  window when the EWMH protocol _NET_WM_FULLSCREEN_MONITORS is used.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: compiz-core 1:0.9.11.2+14.04.20140714-0ubuntu1
  Uname: Linux 3.15.8-031508-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  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: Wed Aug  6 22:18:39 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05cb]
  InstallationDate: Installed on 2014-08-01 (5 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E7440
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.15.8-031508-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 drm.debug=0xe
  SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Aug  6 15:17:04 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id4413 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1353675/+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 1356981] Re: [FFe] Regression: wrong window decorator applied

[Launchpad Bug Tracker]

This bug was fixed in the package compiz -
1:0.9.12+14.10.20140918-0ubuntu1

---
compiz (1:0.9.12+14.10.20140918-0ubuntu1) utopic; urgency=low

  [ Michael Thayer ]
  * Fix for LP #1353675: _NET_WM_FULLSCREEN_MONITORS not handled
correctly. An (x, y, w, h) (LP: #1353675)

  [ Alberts Muktupāvels ]
  * Port gtk-window-decorator to GTK+ 3.
  * Re-enable metacity theme support (LP: #1356981)
  * Remove/replace deprecated functions. (LP: #1356981)
 -- Ubuntu daily releaseThu, 18 Sep 2014 
11:01:08 +

** Changed in: compiz (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  [FFe] Regression: wrong window decorator applied

Status in Compiz:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released

Bug description:
  The gtk-window-decorator needs updating to GTK+3.

  Support for Metacity theme support in Compiz was removed earlier in
  the Ubuntu 14.10 development cycle until deprecated function from
  GTK+2 could be replaced.  This has been done and a feature freeze
  exception is requested to re-enable Metacity support once again.

  The Gnome fallback session with Compiz is not generally usable without
  this support.

  Tested with Ubuntu and Gnome fallback sessions.  Please see the build
  log and changelog at https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/landing-016/+packages for review.

  -- original bug description --

  Windows have the wrong window decorator theme.
  This can be seen when using Compiz in the GNOME Flashback session (package: 
gnome-session-flashback).

  It does not respect the setting of 'gsettings get
  org.gnome.desktop.wm.preferences theme'.This is a regression.

  This worked fine in Compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 but is broken 
in 1:0.9.12+14.10.20140812-0ubuntu1 on 12 August.
  Perhaps due to the change by Alberts Muktupāvels?
   * Remove gconf from gtk-window-decorator.

  ProblemType: BugDistroRelease: Ubuntu 14.10
  Package: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
  Uname: Linux 3.16.0-7-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Aug 14 18:30:07 2014
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Device [1043:8534]
  InstallationDate: Installed on 2013-12-26 (230 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: ASUS All Series
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-7-generic.efi.signed 
root=UUID=31dc4488-28d4-4d2a-aa51-6733e237d5f8 ro quiet splash 
vt.handoff=7SourcePackage: compiz
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2005
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.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.:bvr2005:bd06/04/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Aug 14 18:26:08 2014
  xserver.configfile: default
  xserver.errors:
   intel: Failed to load module "dri3" (module does not exist, 0)
   intel: Failed to load module "present" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.

[Desktop-packages] [Bug 1373775] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1268257, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1268257
   nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed 
to build, with no obvious error [objdump: '... .tmp_nv.o': No such file]

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

Title:
  nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel
  module failed to build

Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Confirmed

Bug description:
  I got this error after distupgrade, however video seems to work well.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331-updates-uvm 331.89-0ubuntu5
  Uname: Linux 3.16.1-031601-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-17-generic
  Date: Thu Sep 25 10:08:21 2014
  InstallationDate: Installed on 2014-05-08 (139 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1373775/+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 1306513] Re: 计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Kylin live session

[Anthony Wong]

** Changed in: ubuntukylin
Milestone: utopic-beta2 => utopic-final

** Changed in: ubuntukylin
   Status: Confirmed => Triaged

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

Title:
  计算器-编辑&帮助下拉框汉化不全 - gnome-calculator menu is not translated under Kylin
  live session

Status in Ubuntu Translations:
  New
Status in Ubuntu Kylin:
  Triaged
Status in “gnome-calculator” package in Ubuntu:
  New

Bug description:
  系统测试版本：UK14.04-Daily-0410-i386
  计算器-编辑&帮助下拉框汉化不全。

  gnome-calculator menu is not translated under Kylin live session

  see screenshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1306513/+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 1374232] [NEW] [utopic] libunity-settings-daemon1 should not depend on libglib2.0-dev and libgtk-3-dev

[Jesse Sung]

Public bug reported:

Version: 14.04.0+14.10.20140922-0ubuntu1

Since the libunity-setting-daemon1 depends on libglib2.0-dev and
libgtk-3-dev, it pulls a lot of development related packages into a
normal desktop setup.

** Affects: unity-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [utopic] libunity-settings-daemon1 should not depend on libglib2.0-dev
  and libgtk-3-dev

Status in “unity-settings-daemon” package in Ubuntu:
  New

Bug description:
  Version: 14.04.0+14.10.20140922-0ubuntu1

  Since the libunity-setting-daemon1 depends on libglib2.0-dev and
  libgtk-3-dev, it pulls a lot of development related packages into a
  normal desktop setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1374232/+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 1372346] Re: [FFe] gnome-desktop 3.12 transition

[Tim]

ppa:darkxst/gnome-desktop

As mentioned on irc, gnome-session update was blocked due to > 3.9.90 crashing 
when running under gnome-desktop 3.8.
gnome-panel provides its own dialogs, however seems they are only used when 
clicking through the system menu. I can revert the dialogs for now, but would 
seem consistent if fallback sessions always used gnome-panel dialogs. 

re comment #5, the patch was there just the changelog entry was
incorrect.

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

Title:
  [FFe] gnome-desktop 3.12 transition

Status in “gnome-control-center” package in Ubuntu:
  New
Status in “gnome-desktop3” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  New

Bug description:
  We have been trying to land this transition for about 9 months now
  (well previously was 3.10, but that was largely the same). The big
  blocker was the removal of xrandr and idlemonitor code out of gnome-
  desktop. Robert Ancell has solved that issue see Bug 1372240 (however
  that still hasn't landed yet.

  There is a SONAME bump, however that only affects g-s-d/g-c-c (and
  u-s-d/u-c-c until above changes land). Mostly apps are using things
  like the thumbnailer etc, and these are not affected by api changes,
  so they just need to be rebuilt. gnome-session will need to be updated
  to latest 3.10 stable release.

  Full lost of r-depends:
  Reverse-Depends
  ===
  * cheese
  * eog
  * epiphany-browser
  * evince
  * gnome-clocks
  * gnome-contacts
  * gnome-control-center
  * gnome-documents
  * gnome-font-viewer
  * gnome-panel
  * gnome-photos
  * gnome-screensaver
  * gnome-session-bin
  * gnome-settings-daemon
  * gnome-shell-pomodoro
  * indicator-keyboard
  * evolution
  * mutter
  * nautilus
  * unity
  * unity-control-center
  * unity-settings-daemon

  I have debian merges ready to go for gnome-desktop, g-s-d and g-c-c
  3.12 (but using 3.10 power plugin/panel to untangle from upower 0.99).

  gnome-control-center update will also require a UIFe, Ubuntu GNOME
  slideshow has not yet been updated for utopic, so this shouldnt be a
  problem from our side. No other flavours use the UI part of gnome-
  control-center anymore, the shared-data (faces) are unchanged.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1372346/+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 807888] Re: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

[Bug Watch Updater]

** Changed in: gdm
   Status: Unknown => New

** Changed in: gdm
   Importance: Unknown => Low

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

Title:
  gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

Status in GDM: The Gnome Display Manager:
  New
Status in “gdm” package in Ubuntu:
  Confirmed

Bug description:
  don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gdm 3.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
  Uname: Linux 3.0-3-generic x86_64
  Architecture: amd64
  Date: Sat Jul  9 16:27:48 2011
  ExecutablePath: /usr/lib/gdm/gdm-session-worker
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  ProcCmdline: /usr/lib/gdm/gdm-session-worker
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9fd2d27530 :   movzbl 
0xac(%rdi),%eax
   PC (0x7f9fd2d27530) ok
   source "0xac(%rdi)" (0x00ac) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm
  StacktraceTop:
   act_user_is_loaded () from /usr/lib/libaccountsservice.so.0
   ?? ()
   ?? ()
   ?? ()
   pam_vprompt () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()
  UpgradeStatus: Upgraded to oneiric on 2011-07-09 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/807888/+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 1370376] Re: Can't receive MMS despite ability to send

[Bill Filler]

mms recv does work, but might be a carrier specific issue. Works for me
on At+t in US

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

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

** No longer affects: messaging-app (Ubuntu)

** Tags added: rtm14

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: nuntium (Ubuntu)
   Importance: Undecided => High

** Changed in: nuntium (Ubuntu)
 Assignee: (unassigned) => Sergio Schvezov (sergiusens)

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

Title:
  Can't receive MMS despite ability to send

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

Bug description:
  I can send MMS (and they actually come through to the recipient), but
  I can't receive MMS. I am not sure if this is an APN settings issue,
  but I would have thought it either worked both ways or not at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+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 1374093] Re: chromium-browse[2458]: segfault at 20 ip 00007f5937431d83 sp 00007fffd9fb73c0 error 4 in i965_dri.so[7f5937150000+50a000]

[Chad Miller]

i965_dri is in  libgl1-mesa-dri .

** Tags removed: patch

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

Title:
  chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp
  7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]

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

Bug description:
  dmesg:
  [   47.163002] chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp 
7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]
  [   47.822464] chromium-browse[2531]: segfault at 20 ip 7f9b0c284d83 sp 
7fff6e143f90 error 4 in i965_dri.so[7f9b0bfa3000+50a000]
  [   48.542861] chromium-browse[2548]: segfault at 20 ip 7f22a2675d83 sp 
7fff7dca8db0 error 4 in i965_dri.so[7f22a2394000+50a000]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 25 16:03:46 2014
  InstallationDate: Installed on 2014-09-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-25T10:51:09.836610

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1374093/+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 1299002] Re: gpu-manager xorg.conf inconsistency with AMD Catalyst (fglrx)

[alela1441]

Upgrade 19-09-14:

 - ubuntu-drivers-common (0.2.91.6, 0.2.91.7)
 - dh-modaliases (0.2.91.6, 0.2.91.7)
 - linux-firmware (1.127.5, 1.127.6)

alela@alela-X550DP:~$ aticonfig --initial --adapter=all --od-gettemperature
Found fglrx primary device section
Found fglrx primary device section
 Unable to find any supported Screen sections

Se hace obligatorio, pero esto no es satisfactorio:

$ aticonfig --initial -f --adapter=all --od-gettemperature

Al hacer:

$ sudo rm /etc/X11/xorg.conf*

Pero esto tampoco es satisfactorio.

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

Title:
  gpu-manager xorg.conf inconsistency with AMD Catalyst (fglrx)

Status in “ubuntu-drivers-common” package in Ubuntu:
  New

Bug description:
  This is a bug report against gpu-manager.c in ubuntu-drivers-common.

  ~/Documents/VC/ubu/ubuntu-drivers-common/share/hybrid$ bzr log
  
  revno: 56
  tags: 1:0.2.91.1
  author: Alberto Milone 
  committer: Package Import Robot
  branch nick: trusty-proposed
  timestamp: Fri 2014-03-21 20:03:20 +0100

  I'm submitting this now manually due to urgency to 14.04 release as
  ubuntu-bug crashes too ;(

  %sudo aticonfig --adapter=all --initial writes a xorg.conf which uses 
xorg.conf keywords in "text" fields searched by function
   static int check_vendor_bus_id_xorg_conf(struct device **devices, int 
cards_n,
   unsigned int vendor_id, char *driver)

  In line 1072 of gpu-manager.c

  "Driver" keyword is found from following lines xorg.conf written by aticonfig
  Section "Monitor"
Identifier   "aticonfig-Monitor[0]-0"
Option  "VendorName" "ATI Proprietary Driver"
Option  "ModelName" "Generic Autodetecting Monitor"
Option  "DPMS" "true"
  EndSection

  Section "Monitor"
Identifier   "aticonfig-Monitor[1]-0"
Option  "VendorName" "ATI Proprietary Driver"
Option  "ModelName" "Generic Autodetecting Monitor"
Option  "DPMS" "true"
  EndSection

  Line  1119 of gpu-manager.c 
  else if ((istrstr(line, "Driver") != NULL) &&
   (strstr(line, driver) == NULL)) {
  failure = 1;
  }
  Looks the xorg keyword "Driver" anywhere in the line and finds "ATI 
Proprietary Driver", but of course does not find correct drivername "fglrx" 
from the same line => Keywords should be searched from the beginning of the 
line, not all over.

  Second issue in same function the format "PCI:%d@%d:%d:%d" which is
  different to format  "PCI:%d:%d:%d" used by aticonfig, which causes
  misdetection of correct BusID in xorg.conf

  If routine "check_vendor_bus_id_xorg_conf()" reports "Check failed"
  completely valid xorg.conf is overwritten by gpu-manager.c in boot.

  Quick workaround for users is to correct the xorg.conf after installation of 
ATI Catalyst proprietary drivers taking these into account.
  --- 
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2014-03-27 (1 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140227)
  NonfreeKernelModules: wl fglrx
  Package: ubuntu-drivers-common 1:0.2.91.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Tags:  trusty
  Uname: Linux 3.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1299002/+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 1373225] Re: Unity Control Center icons in the dash don't point to the right section in the Control Center

[Gunnar Hjalmarsson]

What if you uninstall the gnome-control-center package?

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

Title:
  Unity Control Center icons in the dash don't point to the right
  section in the Control Center

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Won't Fix
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  - In the dash, open one of these applications: Notifications, Online
  Accounts, Privacy, Security, Sharing.

  
  **
  EXPECTED BEHAVIOUR
  **

  - Going to the right section in the Control Center.

  
  **
  REAL BEHAVIOUR
  **

  - You go to the main page in the Control Center.

  
  
  RELEVANT DETAILS
  

  - Old icons are still there, and should be removed too.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 06:43:11 2014
  InstallationDate: Installed on 2013-05-21 (490 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu15
   deja-dup 32.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1373225/+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 1263278] Re: Use FFmpeg instead of Libav

[Timothy Gu]

FYI, Debian has accepted ffmpeg to experimental. It is expected to go
into Ubuntu as well after the migration from experimental to unstable.

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

Title:
  Use FFmpeg instead of Libav

Status in “libav” package in Ubuntu:
  Won't Fix
Status in “libav” package in Debian:
  Fix Released

Bug description:
  Libav is supposed to be a drop-in replacement of FFmpeg.
  However, it isn't.
  For example, many software uses libswresample, it is simply missing in Libav.
  
http://stackoverflow.com/questions/12651816/libswresample-in-recent-ubuntu-version
  https://github.com/hrydgard/ppsspp/issues/2322

  BTW, the mindset of Libav is annoying at best.
  http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html
  
http://stackoverflow.com/questions/9477115/who-can-tell-me-the-difference-and-relation-between-ffmpeg-libav-and-avconv

  So I hope that Ubuntu can switch back to FFmpeg; let more software build.
  Debian's political preference, e.g., Iceweasel, shouldn't affect a lot of 
Ubuntu users out there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1263278/+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 388508] Re: Ctrl+Tab to change tab in Nautilus

[Bug Watch Updater]

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

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

Title:
  Ctrl+Tab to change tab in Nautilus

Status in GTK+ GUI Toolkit:
  Fix Released
Status in One Hundred Papercuts:
  Invalid
Status in Nautilus:
  Won't Fix
Status in “gtk+3.0” package in Ubuntu:
  Triaged
Status in “nautilus” package in Ubuntu:
  Won't Fix

Bug description:
  Ctrl+Tab = change tab in Nautilus like firefox. Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/388508/+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 1372006] Re: pci_devices does not terminate at computer shutdown

[ahau]

** Description changed:

  Shutdown does not halt on my Dell Precision 390
  the shutdown sequence prints on the console:
  
  mount: / is busy
  
  /etc/init.d/sendsigs does not terminate systemd-udevd
  
  Only solution: enable and use ALT-SYSREQ REISUB (to keep the root fs
  clean)
  
  I tried to change GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub  (+
  update-grub):
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash reboot=pci"  or
  GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash reboot=bios" or
  GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash acpi=force
  
  Shutdown still hangs with 'mount: / is busy'
  I even updated the BIOS from 2.0.4 to 2.06, no luck.
  
  When booting from a Knoppix 6.0.1 CD with a 2.6 kernel,  shutdown works
  and halts the system to poweroff state.
  
  Any ideas?
  
  Thanks
-   ahau
+   ahau
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  Date: Sun Sep 21 02:58:10 2014
  ExecutablePath: /usr/lib/pm-utils/power.d/pci_devices
  InstallationDate: Installed on 2014-09-19 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /bin/dash
  OmitPids: 11761 308 302 11767 723 714 11890 11767 723 714 11890
  PackageArchitecture: all
  ProcCmdline: /bin/sh /usr/lib/pm-utils/power.d/pci_devices false
  ProcEnviron:
-  LC_COLLATE=C
-  PATH=(custom, no user)
+  LC_COLLATE=C
+  PATH=(custom, no user)
  SourcePackage: pm-utils
  Title: pci_devices does not terminate at computer shutdown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  pci_devices does not terminate at computer shutdown

Status in “pm-utils” package in Ubuntu:
  New

Bug description:
  Shutdown does not halt on my Dell Precision 390
  the shutdown sequence prints on the console:

  mount: / is busy

  /etc/init.d/sendsigs does not terminate systemd-udevd

  Only solution: enable and use ALT-SYSREQ REISUB (to keep the root fs
  clean)

  I tried to change GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub  (+
  update-grub):

  GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash reboot=pci"  or
  GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash reboot=bios" or
  GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash acpi=force

  Shutdown still hangs with 'mount: / is busy'
  I even updated the BIOS from 2.0.4 to 2.06, no luck.

  When booting from a Knoppix 6.0.1 CD with a 2.6 kernel,  shutdown
  works and halts the system to poweroff state.

  Any ideas?

  Thanks
    ahau

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  Date: Sun Sep 21 02:58:10 2014
  ExecutablePath: /usr/lib/pm-utils/power.d/pci_devices
  InstallationDate: Installed on 2014-09-19 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  InterpreterPath: /bin/dash
  OmitPids: 11761 308 302 11767 723 714 11890 11767 723 714 11890
  PackageArchitecture: all
  ProcCmdline: /bin/sh /usr/lib/pm-utils/power.d/pci_devices false
  ProcEnviron:
   LC_COLLATE=C
   PATH=(custom, no user)
  SourcePackage: pm-utils
  Title: pci_devices does not terminate at computer shutdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1372006/+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 1373225] Re: Unity Control Center icons in the dash don't point to the right section in the Control Center

[Treviño]

I don't think it is an unity issue, but it might be unity-control-center
problem instead.

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

Title:
  Unity Control Center icons in the dash don't point to the right
  section in the Control Center

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Won't Fix
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  - In the dash, open one of these applications: Notifications, Online
  Accounts, Privacy, Security, Sharing.

  
  **
  EXPECTED BEHAVIOUR
  **

  - Going to the right section in the Control Center.

  
  **
  REAL BEHAVIOUR
  **

  - You go to the main page in the Control Center.

  
  
  RELEVANT DETAILS
  

  - Old icons are still there, and should be removed too.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 06:43:11 2014
  InstallationDate: Installed on 2013-05-21 (490 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu15
   deja-dup 32.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1373225/+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 807888] Re: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

[Ryan Tandy]

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

** Also affects: gdm via
   https://bugzilla.gnome.org/show_bug.cgi?id=737394
   Importance: Unknown
   Status: Unknown

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

Title:
  gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

Status in GDM: The Gnome Display Manager:
  Unknown
Status in “gdm” package in Ubuntu:
  Confirmed

Bug description:
  don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gdm 3.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
  Uname: Linux 3.0-3-generic x86_64
  Architecture: amd64
  Date: Sat Jul  9 16:27:48 2011
  ExecutablePath: /usr/lib/gdm/gdm-session-worker
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  ProcCmdline: /usr/lib/gdm/gdm-session-worker
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9fd2d27530 :   movzbl 
0xac(%rdi),%eax
   PC (0x7f9fd2d27530) ok
   source "0xac(%rdi)" (0x00ac) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm
  StacktraceTop:
   act_user_is_loaded () from /usr/lib/libaccountsservice.so.0
   ?? ()
   ?? ()
   ?? ()
   pam_vprompt () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()
  UpgradeStatus: Upgraded to oneiric on 2011-07-09 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/807888/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad

[bob justo]

I am using an ASUS X73S with intel i915 and nvidia GE GT 520M.
kernel 3.16.3 
using the nvidia only with nvidia-prime 
nvidia official drivers 343.22 (the last)
i don't use ubuntu but slackware and i have have also the bug , the freeze 
happens very often every hours.
 i had seen the trick suggested in post #18 works ! it's a good workout!
even if i lost the "two fingers" tracking , it's better than the CTRL + ALT+ F1 
trick.
and i can work all day long without be annoyed.

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

Title:
  [nvidia-prime]Freeze while using touchpad

Status in “nvidia-graphics-drivers-319” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Triaged
Status in “nvidia-graphics-drivers-343” package in Ubuntu:
  Triaged
Status in “nvidia-prime” package in Ubuntu:
  Triaged

Bug description:
  I'm using an Optimus laptop (Asus N43SL)
  nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is 
in use.

  Once in a while, my screen will freeze, only when I use my touchpad.
  This does not happen with my USB mouse.
  This does not happen either when I uninstall nvidia-prime and use my intel 
integrated graphics (HD3000).

  I can temporarily solve the issue by doing a VT switch.

  
  In the attached Xorg.0.log, you can see "synaptics: ETPS/2 Elantech Touchpad: 
touchpad found" each time I did a VT switch and regained control.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+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 807888] Re: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

[Ryan Tandy]

** Tags added: trusty utopic

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

Title:
  gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

Status in “gdm” package in Ubuntu:
  Confirmed

Bug description:
  don't know

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gdm 3.0.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
  Uname: Linux 3.0-3-generic x86_64
  Architecture: amd64
  Date: Sat Jul  9 16:27:48 2011
  ExecutablePath: /usr/lib/gdm/gdm-session-worker
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
  ProcCmdline: /usr/lib/gdm/gdm-session-worker
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f9fd2d27530 :   movzbl 
0xac(%rdi),%eax
   PC (0x7f9fd2d27530) ok
   source "0xac(%rdi)" (0x00ac) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm
  StacktraceTop:
   act_user_is_loaded () from /usr/lib/libaccountsservice.so.0
   ?? ()
   ?? ()
   ?? ()
   pam_vprompt () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()
  UpgradeStatus: Upgraded to oneiric on 2011-07-09 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/807888/+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 1332595] Re: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

[Ryan Tandy]

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

** This bug has been marked a duplicate of bug 807888
   gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

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

Title:
  gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()

Status in “gdm” package in Ubuntu:
  Invalid

Bug description:
  Not see image of user.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gdm 3.10.0.1-0ubuntu6
  Uname: Linux 3.16.0-031600rc1-lowlatency x86_64
  ApportVersion: 2.14.3-0ubuntu2
  Architecture: amd64
  Date: Fri Jun 20 11:40:03 2014
  ExecutablePath: /usr/lib/gdm/gdm-session-worker
  InstallationDate: Installed on 2014-04-27 (54 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: gdm-session-worker\ [pam/gdm-password]
  SegvAnalysis:
   Segfault happened at: 0x7f6f349388b0 :   movzbl 
0xe8(%rdi),%eax
   PC (0x7f6f349388b0) ok
   source "0xe8(%rdi)" (0x00e8) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm
  StacktraceTop:
   act_user_is_loaded () from /usr/lib/x86_64-linux-gnu/libaccountsservice.so.0
   ?? ()
   ?? ()
   ?? ()
   pam_vprompt () from /lib/x86_64-linux-gnu/libpam.so.0
  Title: gdm-session-worker crashed with SIGSEGV in act_user_is_loaded()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1332595/+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 1374182] Re: nautilus crashed with SIGSEGV in ffi_call_unix64()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1212601, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215494/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215496/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215497/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215498/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215499/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215500/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374182/+attachment/4215501/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1212601
   nautilus crashed with SIGSEGV in discovered_cb()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  nautilus crashed with SIGSEGV in ffi_call_unix64()

Status in “totem” package in Ubuntu:
  New

Bug description:
  Exactly like #1103658

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: totem 3.10.1-1ubuntu6
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 25 23:25:16 2014
  ExecutablePath: /usr/bin/nautilus
  InstallationDate: Installed on 2014-03-10 (199 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  ProcCmdline: nautilus -n
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/zsh
  SegvAnalysis:
   Segfault happened at: 0x7fe3f7fbfb9a:mov(%rcx),%rdi
   PC (0x7fe3f7fbfb9a) ok
   source "(%rcx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/nautilus/extensions-3.0/libtotem-properties-page.so
   ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
   g_cclosure_marshal_generic () from 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: nautilus crashed with SIGSEGV in ffi_call_unix64()
  UpgradeStatus: Upgraded to utopic on 2014-09-17 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1374182/+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 1374178] Re: gnome-contacts crashed with SIGSEGV in g_date_time_to_timezone()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1296317, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215485/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215487/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215489/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215490/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215491/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215492/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374178/+attachment/4215493/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1296317

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gnome-contacts crashed with SIGSEGV in g_date_time_to_timezone()

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

Bug description:
  I tried to close a window after I accidentally changed the birth date

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: gnome-contacts 3.8.3-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 25 23:33:29 2014
  ExecutablePath: /usr/bin/gnome-contacts
  InstallationDate: Installed on 2014-01-22 (246 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 
(20131017)
  ProcCmdline: gnome-contacts -i 333f470c57dca1a1cf931f03b032d65aa3437ea0
  SegvAnalysis:
   Segfault happened at: 0x7f76b5ae2bd4:mov0x10(%rdi),%esi
   PC (0x7f76b5ae2bd4) ok
   source "0x10(%rdi)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%esi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-contacts
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_date_time_to_timezone () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_date_time_to_utc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   contacts_contact_editor_properties_changed ()
   contacts_contact_pane_set_edit_mode ()
  Title: gnome-contacts crashed with SIGSEGV in g_date_time_to_timezone()
  UpgradeStatus: Upgraded to trusty on 2014-07-01 (86 days ago)
  UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-contacts/+bug/1374178/+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 1374185] Re: update-software-center crashed with AttributeError in __getattr__(): When using gi.repository you must not import static modules like "gobject". Please change all

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1367017, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-center (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374185/+attachment/4215503/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374185/+attachment/4215504/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 1367017

** Information type changed from Private to Public

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

Title:
  update-software-center crashed with AttributeError in __getattr__():
  When using gi.repository you must not import static modules like
  "gobject". Please change all occurrences of "import gobject" to "from
  gi.repository import GObject". See:
  https://bugzilla.gnome.org/show_bug.cgi?id=709183

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Problem reported on boot

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  Date: Thu Sep 25 22:37:03 2014
  ExecutablePath: /usr/share/software-center/update-software-center
  InstallationDate: Installed on 2014-02-28 (208 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/sbin/update-software-center --triggered 
/usr/share/locale-langpack
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/sbin/update-software-center', '--triggered', 
'/usr/share/locale-langpack']
  SourcePackage: software-center
  Title: update-software-center crashed with AttributeError in __getattr__(): 
When using gi.repository you must not import static modules like "gobject". 
Please change all occurrences of "import gobject" to "from gi.repository import 
GObject". See: https://bugzilla.gnome.org/show_bug.cgi?id=709183
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1374185/+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 1353157] Re: PCI/internal sound card not detected

[Justin Brash]

I got my sound card working by compiling kernel 3.16.2 and using that.
How do I find out if / when the ubuntu kernel is updated to support my
card?

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

Title:
  PCI/internal sound card not detected

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Asus Xonar Essesnce STX II sound card not detected by ALSA.  This is a
  fairly new sound card on the market.  I've tested the card I have
  under windows 8.1 with the drivers downloaded from Asus, and all works
  perfectly.  I'm 100% sure I've physically installed and connected the
  card correctly.  Unfortunately I've had no joy getting it detected by
  Ubuntu 14.04.1 64bit.  Please help!  I don't want to send the card
  back and I don't want to have to move to Windows!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  justin 2369 F pulseaudio
   /dev/snd/controlC1:  justin 2369 F pulseaudio
   /dev/snd/controlC0:  justin 2369 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  5 23:28:37 2014
  InstallationDate: Installed on 2014-04-28 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: SABERTOOTH 990FX R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1353157/+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 1374168] Re: compiz crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1371857, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1374168/+attachment/4215459/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374168/+attachment/4215468/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374168/+attachment/4215470/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1374168/+attachment/4215471/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374168/+attachment/4215472/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374168/+attachment/4215473/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1371857
   compiz crashed with SIGSEGV in g_closure_invoke()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  X doesn't start  on boot in virtualbox

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Sep 26 08:19:03 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2014-09-25 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcCmdline: compiz --replace
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-17-generic 
root=UUID=308d9fb7-8f51-4bb5-8f64-1e7ddd808eb7 ro quiet splash vt.handoff=7
  Renderer: Software
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xo

[Desktop-packages] [Bug 1350606] Re: goa-daemon crashed with SIGSEGV in g_mutex_lock()

[styro]

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

Commenting here as #1288983 is private and I can't see it. Is it
possible for that bug to be made public?

I regularly get the same goa-daemon crash in g_mutex_lock(). As far as I
can tell it seems to happen whenever I unlock my computer after my
kerberos ticket has expired.

I'm using Unity on 14.04 and my login account uses pam_winbind to
authenticate to Active Directory via Kerberos.

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

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

Status in “gnome-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Add account ownCloud.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-online-accounts 3.12.2-1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 30 19:34:16 2014
  ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
  InstallationDate: Installed on 2014-04-27 (94 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
  SegvAnalysis:
   Segfault happened at: 0x7ff083014807 :   mov
(%rdi),%rbx
   PC (0x7ff083014807) ok
   source "(%rdi)" (0x000c) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1350606/+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 1374131] Re: qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0

[Andy Whitcroft]

** Tags added: block-proposed blocks-proposed

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

Title:
  qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0

Status in “mesa” package in Ubuntu:
  New

Bug description:
  So, in the course of a unity8 package migration it got halted due to
  qtcreator-plugin autopkg test failing

  see here
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  which lead me to look at the jenkins run, note its only failling on amd64 arch
  and...you can see from here
  
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
  it started failing about 24 hrs ago with "can't init gxl"...almost certainly 
meaning it's unhappy with mesa.
  low and behold the difference between the pasing jenkins and failing is

  passing -> 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
  which uses
  mesa 10.2.6-1ubuntu3

  failing -> 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
  which uses 
  mesa 10.3.0-0ubuntu1

  So can we do a couple of things?
  - revert mesa and see if that fixes the autopkgtest to confirm
  - if so, please leave reverted until we find out why so we can actually 
continue landing our unity8/uitk/webbrowser stuff
  - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency 
to land a new mesa

  sorry for marking critical, but we're sunk until we get this sorted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374131/+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 1350606] Re: goa-daemon crashed with SIGSEGV in g_mutex_lock()

[Launchpad Bug Tracker]

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

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

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Confirmed

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

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

Status in “gnome-online-accounts” package in Ubuntu:
  Confirmed

Bug description:
  Add account ownCloud.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-online-accounts 3.12.2-1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Jul 30 19:34:16 2014
  ExecutablePath: /usr/lib/gnome-online-accounts/goa-daemon
  InstallationDate: Installed on 2014-04-27 (94 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  ProcCmdline: /usr/lib/gnome-online-accounts/goa-daemon
  SegvAnalysis:
   Segfault happened at: 0x7ff083014807 :   mov
(%rdi),%rbx
   PC (0x7ff083014807) ok
   source "(%rdi)" (0x000c) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gnome-online-accounts
  StacktraceTop:
   g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1
   g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1
  Title: goa-daemon crashed with SIGSEGV in g_mutex_lock()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1350606/+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 1373225] Re: Unity Control Center icons in the dash don't point to the right section in the Control Center

[Alberto Salvia Novella]

Why you decided not to fix this bug?

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

Title:
  Unity Control Center icons in the dash don't point to the right
  section in the Control Center

Status in One Hundred Papercuts:
  Triaged
Status in Unity:
  Won't Fix
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged

Bug description:
  
  HOW TO REPRODUCE
  

  - In the dash, open one of these applications: Notifications, Online
  Accounts, Privacy, Security, Sharing.

  
  **
  EXPECTED BEHAVIOUR
  **

  - Going to the right section in the Control Center.

  
  **
  REAL BEHAVIOUR
  **

  - You go to the main page in the Control Center.

  
  
  RELEVANT DETAILS
  

  - Old icons are still there, and should be removed too.

  **
  TECHNICAL INFO
  **

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity-control-center 14.10.0+14.10.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 24 06:43:11 2014
  InstallationDate: Installed on 2013-05-21 (490 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to utopic on 2014-09-24 (0 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu15
   deja-dup 32.0-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1373225/+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 1339016] Re: Initial sync of the calendar takes a prohibitive amount of time

[Bill Filler]

** Changed in: sync-monitor
   Status: New => Confirmed

** Changed in: evolution-data-server (Ubuntu)
   Status: New => Confirmed

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

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

Title:
  Initial sync of the calendar takes a prohibitive amount of time

Status in Sync monitor for Ubuntu Touch:
  Confirmed
Status in “evolution-data-server” package in Ubuntu:
  Confirmed
Status in “syncevolution” package in Ubuntu:
  Confirmed

Bug description:
  Mako running 116

  Initial sync of default google calendar ran continuously for 90 mins before I 
terminated it
  The ics file grew to 8MB

  I can see two major things from the log:
  - it syncs all past events (I would suggest starting with the current or 
previous month if necessary)
  - it adds recurring events repeatedly (is the query using the wrong API and 
receiving events by timeframe rather than as raw event data?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/sync-monitor/+bug/1339016/+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 1374146] Re: compiz crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1371857, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1374146/+attachment/4215414/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374146/+attachment/4215428/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374146/+attachment/4215430/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1374146/+attachment/4215431/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374146/+attachment/4215432/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374146/+attachment/4215433/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1371857
   compiz crashed with SIGSEGV in g_closure_invoke()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  I have a secondary display that is oriented to be counter-clockwise on
  the left of my primary monitor, this seemed to make compiz crash at
  login.

  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10

Installed: 1:0.9.12+14.10.20140812-0ubuntu1
Candidate: 1:0.9.12+14.10.20140812-0ubuntu1
Version table:
   *** 1:0.9.12+14.10.20140812-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  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: Thu Sep 25 15:36:32 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistUpgraded: 2014-09-21 21:51:51,194 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: utopic
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:060a]
  InstallationDate: Installed on 2014-09-04 (21 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. XPS13 9333
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-17-generic 
root=UUID=a58ae31a-d9e6-41cb-a3be-3944688fa6a8 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-22 (3 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0D13CR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12

[Desktop-packages] [Bug 1374093] Re: chromium-browse[2458]: segfault at 20 ip 00007f5937431d83 sp 00007fffd9fb73c0 error 4 in i965_dri.so[7f5937150000+50a000]

[Ubuntu Foundations Team Bug Bot]

The attachment "dmesg_3.16.0-17.23-generic.txt" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp
  7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]

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

Bug description:
  dmesg:
  [   47.163002] chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp 
7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]
  [   47.822464] chromium-browse[2531]: segfault at 20 ip 7f9b0c284d83 sp 
7fff6e143f90 error 4 in i965_dri.so[7f9b0bfa3000+50a000]
  [   48.542861] chromium-browse[2548]: segfault at 20 ip 7f22a2675d83 sp 
7fff7dca8db0 error 4 in i965_dri.so[7f22a2394000+50a000]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 25 16:03:46 2014
  InstallationDate: Installed on 2014-09-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-25T10:51:09.836610

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1374093/+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 1374133] Re: Mouse unusable when Plantronics W710 USB headset connected via USB

[Thomas Stearn]

penalvch,

I added you because you asked to be added for a similar bug report.

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/1006156

Post 15.

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

Title:
  Mouse unusable when Plantronics W710 USB headset connected via USB

Status in “xorg” package in Ubuntu:
  New

Bug description:
  If I plug in my Plantronics W710 USB headset to a USB port, the mouse
  can move on the screen, but, cannot click anything

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep 25 16:20:01 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Device [196e:0984]
  InstallationDate: Installed on 2014-06-10 (107 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=f6dcf642-7422-4950-8b4b-13cb4cc6e761 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20e
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20e:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Sep 25 07:31:13 2014
  xserver.configfile: default
  xserver.errors:
   [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
   [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
   [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
   [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Desktop-packages] [Bug 1374133] [NEW] Mouse unusable when Plantronics W710 USB headset connected via USB

[Thomas Stearn]

Public bug reported:

If I plug in my Plantronics W710 USB headset to a USB port, the mouse
can move on the screen, but, cannot click anything

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
Uname: Linux 3.13.0-36-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  331.38  Wed Jan  8 19:32:30 
PST 2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Sep 25 16:20:01 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Device [196e:0984]
InstallationDate: Installed on 2014-06-10 (107 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=f6dcf642-7422-4950-8b4b-13cb4cc6e761 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F20e
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77X-UD3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20e:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Sep 25 07:31:13 2014
xserver.configfile: default
xserver.errors:
 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
 [dix] Plantronics Plantronics Savi 7xx: unable to find touch point 0
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.1

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


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

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

Title:
  Mouse unusable when Plantronics W710 USB headset connected via USB

Status in “xorg” package in Ubuntu:
  New

Bug description:
  If I plug in my Plantronics W710 USB headset to a USB port, the mouse
  can move on the screen, but, cannot click anything

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driv

[Desktop-packages] [Bug 1374131] [NEW] qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0

[kevin gunn]

Public bug reported:

So, in the course of a unity8 package migration it got halted due to
qtcreator-plugin autopkg test failing

see here
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

which lead me to look at the jenkins run, note its only failling on amd64 arch
and...you can see from here
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
it started failing about 24 hrs ago with "can't init gxl"...almost certainly 
meaning it's unhappy with mesa.
low and behold the difference between the pasing jenkins and failing is

passing -> 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
which uses
mesa 10.2.6-1ubuntu3

failing -> 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
which uses 
mesa 10.3.0-0ubuntu1

So can we do a couple of things?
- revert mesa and see if that fixes the autopkgtest to confirm
- if so, please leave reverted until we find out why so we can actually 
continue landing our unity8/uitk/webbrowser stuff
- lastly, might be good to add qtcreator-plugin as an autopkgtest dependency to 
land a new mesa

sorry for marking critical, but we're sunk until we get this sorted

** Affects: mesa (Ubuntu)
 Importance: Critical
 Assignee: Maarten Lankhorst (mlankhorst)
 Status: New

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Critical

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Maarten Lankhorst (mlankhorst)

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

Title:
  qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0

Status in “mesa” package in Ubuntu:
  New

Bug description:
  So, in the course of a unity8 package migration it got halted due to
  qtcreator-plugin autopkg test failing

  see here
  
http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

  which lead me to look at the jenkins run, note its only failling on amd64 arch
  and...you can see from here
  
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/
  it started failing about 24 hrs ago with "can't init gxl"...almost certainly 
meaning it's unhappy with mesa.
  low and behold the difference between the pasing jenkins and failing is

  passing -> 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/266/console
  which uses
  mesa 10.2.6-1ubuntu3

  failing -> 
https://jenkins.qa.ubuntu.com/job/utopic-adt-qtcreator-plugin-ubuntu/ARCH=amd64,label=adt/267/console
  which uses 
  mesa 10.3.0-0ubuntu1

  So can we do a couple of things?
  - revert mesa and see if that fixes the autopkgtest to confirm
  - if so, please leave reverted until we find out why so we can actually 
continue landing our unity8/uitk/webbrowser stuff
  - lastly, might be good to add qtcreator-plugin as an autopkgtest dependency 
to land a new mesa

  sorry for marking critical, but we're sunk until we get this sorted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374131/+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 1373879] Re: unable to play mkv, avi, mpeg videos

[Seth Arnold]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. 

You appear to be running a release of Ubuntu that is no longer supported.
Please see https://wiki.ubuntu.com/Releases for information on our
currently supported releases; consider using one of the LTS releases,
as they will be supported for the longest amount of time.

Some additional information on upgrading can be found in our community
wiki, https://help.ubuntu.com/community/UpgradeNotes

Thanks


** Information type changed from Private Security to Public

** Changed in: gstreamer0.10 (Ubuntu)
   Status: New => Invalid

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

Title:
  unable to play mkv, avi, mpeg videos

Status in “gstreamer0.10” package in Ubuntu:
  Invalid

Bug description:
  unable to play most of the video formats including mkv, avi, mpeg,
  flv, 3gp, .mov, etc

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgstreamer0.10-0 0.10.30-1build2
  ProcVersionSignature: Ubuntu 2.6.35-31.63-generic-pae 2.6.35.13
  Uname: Linux 2.6.35-31-generic-pae i686
  NonfreeKernelModules: wl
  Architecture: i386
  CheckboxSubmission: 1833ab0837a5933f407575a07d42c9ff
  CheckboxSystem: d00f84de8a555815fa1c4660280da308
  Date: Thu Sep 25 16:44:29 2014
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-dell-maverick-une-20101010-0
  ExecutablePath: /usr/bin/totem
  InstallationMedia: Ubuntu 10.10 "Maverick" - Build i386 LIVE Binary 
20101010-01:50
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1373879/+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 328575] Re: [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-emulator) because of gconf error

[Bug Watch Updater]

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

** Changed in: dbus
   Importance: Critical => Medium

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

Title:
  [gnome-terminal SRU] Cannot start gnome-terminal (or x-terminal-
  emulator) because of gconf error

Status in D-Bus:
  Confirmed
Status in The GConf Registry System:
  New
Status in GNOME Terminal:
  Fix Released
Status in “gconf2” package in Ubuntu:
  Invalid
Status in “gnome-terminal” package in Ubuntu:
  Fix Released
Status in “gconf2” source package in Jaunty:
  Invalid
Status in “gnome-terminal” source package in Jaunty:
  Fix Released
Status in Debian GNU/Linux:
  Fix Released

Bug description:
  Binary package hint: gnome-terminal

  IMPACT: gnome-terminal will fail to launch under any circumstance
  where gconfd isn't already running. This can include `sudo gnome-
  terminal` (since no gconfd is running for root), or starting gnome-
  terminal under a non-GNOME window manager.

  DEVELOPMENT: The Debian maintainer added 02_let_gconf_autostart.patch
  in 2.26.2-2 to solve this issue (debbugs #531734). That version has
  been merged into Karmic.

  PATCH: Patch available at http://launchpadlibrarian.net/30671489
  /gnome-terminal_2.26.0-0ubuntu2.1.debdiff, with test builds in
  https://launchpad.net/~broder/+archive/ubuntu-tests. The upstream
  gnome-terminal maintainer rejected the patch used for
  02_let_gconf_autostart.patch, because it reintroduced gnome-bugs
  #561663. The attached patch instead cherry-picks the commit the
  maintainer added to fix this bug upstream.

  INSTRUCTIONS: Attempt to run `sudo gnome-terminal`. It will exit with
  "Failed to contact the GConf daemon; exiting."

  REGRESSION: Seems limited - this is a cherry-pick of an upstream
  change that only changes a handful of lines.

  
  Original bug description:

  I cannot start gnome-terminal.  If I open an xterm and start gnome-
  terminal from the command line, here is what I get:

  $ sudo gnome-terminal  
  Failed to contact the GConf daemon; exiting.
  (original report didn't have sudo in this command, but a later comment by the 
submitter amended this.)

  $ ps ax | grep gconf
   3956 pts/0R+ 0:00 grep gconf
   6643 ?S  0:00 /usr/lib/pulseaudio/pulse/gconf-helper
   6647 ?S  0:06 /usr/lib/libgconf2-4/gconfd-2

  This is in Jaunty Alpha 4 with all updates current as of 12 Feb.

   This bug is now understood.  Read all the comments (or at least try
  some text searches) before adding your own, because a lot of things
  have already been covered.

  summary of some stuff posted in comments:
   gnome-terminal on purpose refuses to start if it can't connect to gconfd to 
get its config settings.

   gconf clients now find the server using DBUS.  Starting gnome-
  terminal as root doesn't work even when you have all the gnome bits
  and pieces running under your account, because DBUS is per-user.

  executive of summary: We know what is going on.  Everything that
  doesn't work is a consequence of the design.  Everything is working as
  designed, although obviously there are problems with this design.
  Discussion about the design probably belongs on freedesktop-bugs
  #17970 (link in the remote bug sidebar).

   Workarounds to use until the bugs are fixed:
  for the gconfd-not-running case:
  start gconfd.  e.g. add /usr/bin/gnome-settings-daemon to your X session 
startup script, ahead of any gnome-terminal commands.  This applies whatever 
window manager you happen to be using.  (except if you're using Ubuntu's 
default GNOME desktop, which already starts gconfd itself.)

  multiple tabs over ssh:
  use screen(1)
  $ sudo aptitude install screen  screen-profiles # if you don't have it already
  The default config has unhelpful keybindings.  I'm used to ^t as the command 
key, and F11/F12 as next/previous tab (screen calls them "windows").  I set up 
my own .screenrc before screen-profiles was packaged, so I don't know if its 
examples and samples are good or not.
  If you insist on displaying a GUI over X11 over ssh, there are other terminal 
emulators with tabs, e.g. the lighter-weight mrxvt.  (be careful, though: it 
doesn't support UTF-8.)

   You might also investigate ssh -M for connection sharing.  As I
  understand it, this lets you tunnel multiple sessions over one SSH
  connection, so only one password prompt...  You could presumably get a
  local gnome-terminal going with ssh connections in each tab.

  root shells:
  You can use sudo inside a gnome terminal that's running under your own 
account.  sudo -s, sudo -i, sudo su, and sudo bash are all variations on 
getting a shell running as root.  If you don't know which to pick, use sudo -s. 
 Or, better, don't start a root shell, and simply use sudo or gksudo on the one 
or two commands that need it.

   This bug is partly t

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

[Elfy]

@apw - installed PPA to a clean install with the beta 2 image

drops to tty1 still

service lightdm status still reports stop/waiting

-- 
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:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged

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=
   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 1284635] Re: IBus does not support certain keyboard layouts

[Andrew Morris]

I may be a tad late in posting this, having only just found this bug report 
(25-Sep-14), but I fixed this situation in Lubuntu 14.04 on a first install 
just after it was released.
Go to:
Preferences>Keyboard Input Methods>Advanced
and under "Keyboard Layout" tick the "Use system keyboard layout" box. Then log 
out and back in.
"Keyboard Input Methods" menus are actually titled "IBus Preferences", so 
presumably are designed to control IBus.
What you will now see on the Task Bar is the code ID for your chosen system 
keyboard plus an adjacent small keyboard symbol which is the selector for the 
default US keyboard layout. There is a tab in the KIM for "Input Method" and 
from the wording at the bottom of the screen I presume that other keyboard 
layouts can be specified in this menu, which will then appear in the Task Bar 
selector (don't quote me, I haven't tried anything in this yet).

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

Title:
  IBus does not support certain keyboard layouts

Status in “ibus” package in Ubuntu:
  Triaged
Status in “ibus” source package in Trusty:
  Triaged

Bug description:
  installed trusty beta1 with keyboard layout set correctly during
  install

  install completes, login to new install - layout as set during install

  once logged in - layout set to US and keyboard layout set during
  install is missing from list

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic i686
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Tue Feb 25 12:55:56 2014
  InstallationDate: Installed on 2014-02-25 (0 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140225)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1284635/+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 1353951] Re: gnome online accounts require autentication on startup

[Sebastien Bacher]

@yazid, are you sure those issues were not there before the change? even
if the fix is not perfect if it improves things that's still worth
getting the update rolled out

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

Title:
  gnome online accounts require autentication on startup

Status in Evolution Data Server:
  Fix Released
Status in “evolution-data-server” package in Ubuntu:
  Fix Released
Status in “gnome-online-accounts” package in Ubuntu:
  Invalid
Status in “evolution-data-server” source package in Trusty:
  Fix Committed
Status in “gnome-online-accounts” source package in Trusty:
  Invalid

Bug description:
  [Impact] Google calendar integration is broken, and users are
  requested to re-enter their Google password everytime they log in, or
  everytime they enable/disable their Google account from the System
  Settings.

  [Test Case]
  1) open gnome-online-accounts
  2) click + and add a google account
  3) enter user name and password
  4) confirm permissions for gnome
  5) Black window pops up and asks for google password, but does not accept the 
correct password.
  Google Contacts are not available in Gnome or Thunderbird

  [Regression Potential] Minimal: the fix is a backport of a patch from
  the evolution-data-server code which is already in 14.10, and which
  only touches the calendar code (which is currently broken).


  

  Gnome online accounts requires autentication on startup, but even typing the 
correct password in the box, the program says the password is wrong. By the way 
evolution and other programs work well with online accounts. I'm using 
Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour.
  Just to be clear: online-accounts works well, just at startup it opens an 
"administration" window where it requires to insert the password for my google 
accounts; if I type the correct password it says that the password is wrong, 
the only way to close the window is to click on "discard" and then all works 
well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+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 1251281] Re: gnome-session-flashback fails to start without hardware acceleration in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

[Rüdiger Kupper]

Eugene:
> Now acceleration check is skipped automatically for flashback/fallback 
> sessions and still can be disabled explicitly.

How would I disable it explicitly?

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

Title:
  gnome-session-flashback fails to start without hardware acceleration
  in cloud/remote environments (Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting)

Status in The GNOME 2 Session Manager:
  New
Status in “gnome-session” package in Ubuntu:
  Triaged

Bug description:
  This bug will cause static grey or black screen instead of openning
  remote session using Forwarded-X/XRDP/VNC/NX/X2GO/Chromoting from
  x2goclient, rdpclient(reminna/vinagre/mstsc), SSH, VNC, NOMACHINE and
  etc.

  1) lsb_release -rd
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  2) apt-cache policy gnome-session
  gnome-session:
    Installed: 3.9.90-0ubuntu12
    Candidate: 3.9.90-0ubuntu12
    Version table:
   *** 3.9.90-0ubuntu12 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy gnome-session-fallback
  gnome-session-fallback:
    Installed: 1:3.8.0-1ubuntu12.1
    Candidate: 1:3.8.0-1ubuntu12.1
    Version table:
   *** 1:3.8.0-1ubuntu12.1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   1:3.8.0-1ubuntu11 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages

  apt-cache policy xrdp
  xrdp:
    Installed: 0.6.0-1
    Candidate: 0.6.0-1
    Version table:
   *** 0.6.0-1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  apt-cache policy remmina
  remmina:
    Installed: 1.0.0-4ubuntu3
    Candidate: 1.0.0-4ubuntu3
    Version table:
   *** 1.0.0-4ubuntu3 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy vinagre
  vinagre:
    Installed: 3.10.2-0ubuntu1
    Candidate: 3.10.2-0ubuntu1
    Version table:
   *** 3.10.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 
Packages
  100 /var/lib/dpkg/status

  3) What is expected to happen is when one installs xrdp on the host
  and attempts to use remmina or vinagre on a Ubuntu 14.04 client to RDP
  in, it works.

  4) What happens instead is it shows a gray static screen as per attached 
screenshot. This would appear an issue with gnome-session as per client log:
  cat .xsession-errors.old
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  init: indicator-application main process ended, respawning
  init: indicator-application main process ended, respawning
  init: indicator-application respawning too fast, stopped
  Xsession: X session started for  at Sun Jul 20 15:25:59 CDT 2014
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  localuser:moniker being added to access control list
  X Error of failed request:  BadValue (integer parameter out of range for 
operation)
    Major opcode of failed request:  109 (X_ChangeHosts)
    Value in failed request:  0x5
    Serial number of failed request:  6
    Current serial number in output stream:  8
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  Script for ibus started at run_im.
  Script for auto started at run_im.
  Script for default started at run_im.
  gnome-session-is-accelerated: No composite extension.
  gnome-session-check-accelerated: Helper exited with code 256
  gnome-session-is-accelerated: No composite extension.
  gnome-session-check-accelerated: Helper exited with code 256

  ** (process:2565): WARNING **: software acceleration check failed:
  Child process exited with code 1

  ** (x-session-manager:2565): CRITICAL **: We failed, but the fail
  whale is dead. Sorry

  The following is not a WORKAROUND, create /etc/xorg.conf :
  Section "Device"
     Identifier  "Intel Graphics"
     Driver  "Intel"
     Option  "DRI" "False"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-session 3.9.90-0ubuntu12
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jul 20 15:35:23 2014
  InstallationDate: Installed on 2014-06-22 (28 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: gnome-session
 

[Desktop-packages] [Bug 1374098] [NEW] asus n750jk internal speaker doesn't work realtek alc668

[Matteo Martinelli]

Public bug reported:

Internal speaker of my asus n750JK laptop doesn't work. Just the rear
speaker is working

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

** Description changed:

- Internal speaker of my asus n750JK laptot doesn't work
+ Internal speaker of my asus n750JK laptop doesn't work. Just the rear
+ speaker is working

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

Title:
  asus n750jk internal speaker doesn't work realtek alc668

Status in “alsa-driver” package in Ubuntu:
  New

Bug description:
  Internal speaker of my asus n750JK laptop doesn't work. Just the rear
  speaker is working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1374098/+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 1262068] Re: nvidia-prime should support gdm also

[Jean-Louis Jouannic]

Since a recent update on ubuntu-drivers-common and nvidia driver I am
unable to select the NVIDIA GPU through nvidia-settings. When I try to
do so, all I obtain is a blank dialog box with a forbidden sign and an
'OK' button.

Before this update I was using the packages provided by ppa:darkxst/gdm-
prime.

Reading the comments above, I have edited the /etc/init/gpu-manager.conf
file to add the 'or starting gdm' option but it did not change anything.

What can I do ?

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

Title:
  nvidia-prime should support gdm also

Status in Ubuntu GNOME:
  Triaged
Status in “gdm” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” package in Ubuntu:
  Fix Released
Status in “ubuntu-drivers-common” package in Ubuntu:
  Fix Released
Status in “nvidia-prime” source package in Precise:
  Fix Released
Status in “gdm” source package in Trusty:
  Confirmed
Status in “nvidia-prime” source package in Trusty:
  Confirmed
Status in “ubuntu-drivers-common” source package in Trusty:
  Confirmed

Bug description:
  On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends
  on lightdm. This means that

  1. Anyone installing nvidia binary drivers will pull in nvidia-prime and 
subsequently lightdm. As a consequence of this they are also going to get the 
potentially confusing dconf pop-up asking them to choose a DM.
  2. nvidia-prime probably won't work when using gdm

  I haven't looked to closely at how deeply integrated this is with
  lightdm, however we particularly don't want #1 happening, and it would
  be nice if #2 worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nvidia-prime (not installed)
  ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2
  Uname: Linux 3.12.0-5-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Dec 18 16:56:19 2013
  InstallationDate: Installed on 2012-09-23 (451 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  SourcePackage: nvidia-prime
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1262068/+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 1373929] Re: Diffie-Hellman error when not using Diffie-Hellman

[Stefan Smorra]

Sorry,
I was wrong. I was using Diffie-Hellman as cipher suite.
However, the problem still exists.

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

Title:
  Diffie-Hellman error when not using Diffie-Hellman

Status in “empathy” package in Ubuntu:
  New

Bug description:
  I'm getting an error
  gabbleconnection-DEBUG: 09/16/2014 12:20:54.62063: connector_error_disconnect 
(connection.c:1776): connection failed: 
WOCKY_CONNECTOR_ERROR_TLS_SESSION_FAILED (#7): TLS handshake error: -63: 
GNUTLS_E_DH_PRIME_UNACCEPTABLE

  when connecting to my XMPP server. However the certificate doesn't even use 
DH as cipher. It uses RSA.
  Other clients like Miranda IM or Pidgin can connect without problems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1373929/+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 1354924] Re: Networkmanager does not autoconnect to wireless network

[Søren Holm]

I reopened the bug since it's still present. My comment above is still
valid, but auto connecting stops working when suspending to ram or
rebooting. So basically the desired behavior can be obtained temporarily
by removing and adding the network in question.

** Changed in: network-manager (Ubuntu)
   Status: Invalid => 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/1354924

Title:
  Networkmanager does not autoconnect to wireless network

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

Bug description:
  When adding a net wireless network and enable "connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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 1374093] [NEW] chromium-browse[2458]: segfault at 20 ip 00007f5937431d83 sp 00007fffd9fb73c0 error 4 in i965_dri.so[7f5937150000+50a000]

[Cristian Aravena Romero]

Public bug reported:

dmesg:
[   47.163002] chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp 
7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]
[   47.822464] chromium-browse[2531]: segfault at 20 ip 7f9b0c284d83 sp 
7fff6e143f90 error 4 in i965_dri.so[7f9b0bfa3000+50a000]
[   48.542861] chromium-browse[2548]: segfault at 20 ip 7f22a2675d83 sp 
7fff7dca8db0 error 4 in i965_dri.so[7f22a2394000+50a000]

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
Uname: Linux 3.16.0-17-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Sep 25 16:03:46 2014
InstallationDate: Installed on 2014-09-25 (0 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-09-25T10:51:09.836610

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


** Tags: amd64 apport-bug utopic

** Patch added: "dmesg_3.16.0-17.23-generic.txt"
   
https://bugs.launchpad.net/bugs/1374093/+attachment/4215295/+files/dmesg_3.16.0-17.23-generic.txt

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

Title:
  chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp
  7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]

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

Bug description:
  dmesg:
  [   47.163002] chromium-browse[2458]: segfault at 20 ip 7f5937431d83 sp 
7fffd9fb73c0 error 4 in i965_dri.so[7f593715+50a000]
  [   47.822464] chromium-browse[2531]: segfault at 20 ip 7f9b0c284d83 sp 
7fff6e143f90 error 4 in i965_dri.so[7f9b0bfa3000+50a000]
  [   48.542861] chromium-browse[2548]: segfault at 20 ip 7f22a2675d83 sp 
7fff7dca8db0 error 4 in i965_dri.so[7f22a2394000+50a000]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Sep 25 16:03:46 2014
  InstallationDate: Installed on 2014-09-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-09-25T10:51:09.836610

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1374093/+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 1374092] Re: compiz crashed with SIGSEGV in g_closure_invoke()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1371857, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1374092/+attachment/4215266/+files/CoreDump.gz

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1374092/+attachment/4215280/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1374092/+attachment/4215282/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1374092/+attachment/4215283/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374092/+attachment/4215284/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1374092/+attachment/4215285/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1371857
   compiz crashed with SIGSEGV in g_closure_invoke()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  New

Bug description:
  happens on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  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
  CrashCounter: 1
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Sep 26 02:57:29 2014
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.16, 3.16.0-16-generic, x86_64: installed
   vboxhost, 4.3.16, 3.16.0-17-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1096]
  InstallationDate: Installed on 2012-09-19 (736 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
  MachineType: Micro-Star International Co., Ltd. U270 series
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-17-generic 
root=UUID=f480f570-b82d-4bc7-ba50-a5611d6d12b3 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: disk fuse libvirtd plex
  dmi.bios.date: 12/30/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1245AMS.10K
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1245
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: Ver 1.000
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1245AMS.10K:bd12/30/2011:svnMicro-StarInternationalCo.,Ltd.:pnU270series:pvrE1245AMS.10K:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1245:rvrVer1.000:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: U270 series
  dmi.product.version: E1245AMS.10K
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compi

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

[Andy Whitcroft]

@Lerico --- that looks to be a more comprensive version of the fix I
have applied.  We should likely use that.

-- 
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:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged

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=
   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 1373891] Re: compiz crashed with SIGSEGV in g_closure_invoke()

[Stephen M. Webb]

** Information type changed from Private to Public

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

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  compiz crashed with SIGSEGV in g_closure_invoke()

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140918-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
  Uname: Linux 3.16.0-5-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus,dbus,scale,expo,staticswitcher,dbus,scale,expo,staticswitcher]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 25 08:29:53 2014
  Disassembly: => 0x0:  Não é possível acessar a memória no endereço 0x0
  DistUpgraded: Fresh install
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.3.14, 3.16.0-5-generic, x86_64: installed
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:0037]
  InstallationDate: Installed on 2014-05-16 (131 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  LightdmGreeterLog:
   (lightdm-gtk-greeter:16672): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-cursor-blink is deprecated and shouldn't be used anymore. It 
will be removed in a future version.
   
   (lightdm-gtk-greeter:16672): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-cursor-blink-time is deprecated and shouldn't be used anymore. 
It will be removed in a future version.
   
   (lightdm-gtk-greeter:16672): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-cursor-blink-timeout is deprecated and shouldn't be used 
anymore. It will be removed in a future version.
  LightdmGreeterLogOld:
   (lightdm-gtk-greeter:23417): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-cursor-blink is deprecated and shouldn't be used anymore. It 
will be removed in a future version.
   
   (lightdm-gtk-greeter:23417): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-cursor-blink-time is deprecated and shouldn't be used anymore. 
It will be removed in a future version.
   
   (lightdm-gtk-greeter:23417): GLib-GObject-WARNING **: The property 
GtkSettings:gtk-cursor-blink-timeout is deprecated and shouldn't be used 
anymore. It will be removed in a future version.
  ProcCmdline: compiz
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-5-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M
  SegvAnalysis:
   Segfault happened at: 0x0:   Não é possível acessar a memória no endereço 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
   source "0x0" (0x) not located in a known VMA region (needed readable 
region)!
  SegvReason:
   executing NULL VMA
   reading NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 11/19/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: TCIBX10H.86A.0027.2009.1119.1517
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH55HC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE70933-502
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0027.2009.1119.1517:bd11/19/2009:svn:pn:pvr:rvnIntelCorporation:rnDH55HC:rvrAAE70933-502:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2

[Desktop-packages] [Bug 1224756] Re: Pulseaudio should integrate with trust-store

[Ricardo Salveti]

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Ricardo Salveti (rsalveti)

** Tags added: touch-2014-10-9

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

Title:
  Pulseaudio should integrate with trust-store

Status in “pulseaudio” package in Ubuntu:
  Triaged

Bug description:
  Currently the 'audio' policy group allows access to pulseaudio which
  allows apps to use the microphone and eavesdrop on the user.
  Pulseaudio needs to be modified to use trust-store, like location-
  service does. Integrating with trust-store means that when an app
  tries use the microphone via pulseaudio, pulseaudio will contact
  trust-store, the trust-store will prompt the user ("Foo wants to use
  the microphone. Is this ok? Yes|No"), optionally cache the result and
  return the result to pulseaudio. In this manner the user is given a
  contextual prompt at the time of access by the app. Using caching this
  decision can be remembered the next time. If caching is used, there
  should be a method to change the decision in settings.

  Targeting to T-Series for now, since the trust-store is not in a
  reusable form yet.

  Original description:
  David and the security team (inspired by an observation from Rick) discussed 
that when recording, pulseaudio should somehow unobtrusively show the user that 
it is recording. The easiest thing to do would be for pulseaudio to alert 
indicator-sound which would then turn its icon red (similar to 
indicator-message turning blue with new messages). Marking 'high' because apps 
with access to pulseaudio can currently eavedrop on users. If the app is 
allowed to do networking (the default for apps), then it can ship that 
information off to a server somewhere.

  Note 1, the alert to indicator-sound must happen via the out of
  process pulseaudio server and not the confined app itself to be
  effective.

  Note 2, we should consider how to enforce this for foreground apps
  only. Application lifecycle should probably handle this for 13.10
  (apps are suspended if not in foreground or if the screensaver is on),
  but we don't want an app on the converged device to record in the
  background when the user isn't paying attention. Example eavesdropping
  attack: start recording only when the screensaver is on (perhaps
  inhibiting the screensaver during recording would be enough).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1224756/+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 1307144] Re: 'unredirect fullscreen windows' causes tearing

[hans]

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

** No longer affects: compiz

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

Title:
  'unredirect fullscreen windows' causes tearing

Status in “compiz” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu release: 14.04
  Installed compiz version: 1:0.9.11+14.04.20140409-0ubuntu1

  The option 'unredirect fullscreen windows', which is enabled by
  default in Compiz, causes tearing in games and other fullscreen OpenGL
  applications, even with 'sync to vblank' options enabled in ccsm, in
  the GPU settings and in the game.

  With this option disabled, VSync works as fine as should with
  'unredirected fullscreen windows' enabled and there is no tearing (but
  this causes performance issues and the Unity panel shadow on top of
  the application).

  Tested with:
  - ASUS NVIDIA GTX 650-E-1GD5 with NVIDIA proprietary driver 331.38 (tested) 
(nvidia-331)
  - the same graphics card with NVIDIA proprietary driver 331.38 
(nvidia-331-updates)
  - the same graphics card with Nouveau open source driver 
(xserver-xorg-video-nouveau)
  - Intel HD 4000 iGPU with default open source drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1307144/+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

[Laércio de Sousa]

Is this related?

http://cgit.freedesktop.org/plymouth/commit/?id=84eb4381db85877a9a56b35994e6c10d43e46ebe

-- 
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:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged

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=
   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 1372847] Re: [SRU] New stable release 2.40.1

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/glib2.0

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

Title:
  [SRU] New stable release 2.40.1

Status in “glib2.0” package in Ubuntu:
  Fix Released
Status in “glib2.0” source package in Trusty:
  Fix Committed

Bug description:
  We'd like to update glib2.0 using the GNOME MRE.

  [ Description ]

  Upstream have released a new stable, fixing some bugs.

  glib2.0 (2.40.2-0ubuntu1) UNRELEASED; urgency=medium

* New upstream stable release, fixing bugs
  + gobject: try to link with -Wl,-z,nodelete to prevent unloading
  + g_file_copy: Don't set GError when we intend to ignore errors
  + gapplication-tool: ensure object paths are valid
  + gtlscertificate: fix certificate list parsing with trailing comments
  + g_str_has_prefix: improve efficiency with long strings
  + Added type check to GPermission public functions.
  + GApplication: Don't decrease use_count below 0
  + networkmonitornetlink: fix IPv6 issues on Android
  + gresolver: Ensure GThreadedResolver always sets an error if resolution
fails
  + gmacros.h: add G_GNUC_*_IGNORE_DEPRECATIONS macros for clang
  + networkaddress: fix parsing of uri with @ after authority
  + gvariant tests: workaround libc/compiler "issue"

   -- Iain Lane   Tue, 23 Sep 2014 10:27:17
  +0100

  [ QA ]

  Under the terms of the MRE, you can assume the bugs are fixed. I
  suggest installing the update and then using your system as normal for
  the 10 day verification time.

  [ Regression potential ]

  One of the fixes could be bad. This is the first stable in this series
  and is a new release, so hasn't had much testing on its own, even if
  all of the fixes are in the unstable release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1372847/+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 1308771] Re: Update Swedish spellcheck and hyphenation dictionaries

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/trusty-proposed/libreoffice-dictionaries

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

Title:
  Update Swedish spellcheck and hyphenation dictionaries

Status in “libreoffice-dictionaries” package in Ubuntu:
  Fix Released
Status in “openoffice.org-hyphenation” package in Ubuntu:
  Fix Released
Status in “libreoffice-dictionaries” source package in Trusty:
  Fix Committed
Status in “openoffice.org-hyphenation” source package in Trusty:
  Fix Committed

Bug description:
  trusty SRU request
  ==

  [Impact]
  While the libreoffice-dictionaries source package contains reasonably updated 
spell check dictionaries and hyphenation patterns for Swedish, it does 
currently not build hunspell-sv-se and hyphen-sv. In Utopic this has now been 
fixed, and the outdated hyphenation patterns for Swedish in 
openoffice.org-hyphenation have been dropped.

  It's desirable that it's fixed in Trusty as well, so Swedish 14.04
  users don't need to go hunting on the web for up-to-date writing aids.
  After all, LibreOffice is one of the core tools on the desktop.

  [Test Case]
  I haven't figured out specific examples of words or patterns that are 
currently missing and will be included with this SRU.

  [Regression Potential]
  Once it has been verified that the up-to-date dictionaries are installed 
correctly, and that spell checking and hyphenation works as expected in 
LibreOffice, the risk for regression ought to be limited to the risk that 
certain words or patterns, which are currently included, proves to have been 
dropped.

  [Other Info]
  I have attached an SRU patch for libreoffice-dictionaries. As regards 
openoffice.org-hyphenation, some encoding problem in one of the removed files 
prevented me from creating a patch that applies seamlessly. Instead I simply 
suggest that openoffice.org-hyphenation 0.8 is uploaded to trusty-proposed as 
version 0.7.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1308771/+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 1369894] Re: evince crashed with SIGSEGV in ev_window_title_sanitize_title()

[Bug Watch Updater]

** Changed in: evince
   Status: Unknown => Confirmed

** Changed in: evince
   Importance: Unknown => High

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

Title:
  evince crashed with SIGSEGV in ev_window_title_sanitize_title()

Status in Evince document viewer:
  Confirmed
Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Evince just crashed while it was open and idle.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: evince 3.13.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 16 09:24:16 2014
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2010-10-25 (1421 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x43984b:  mov(%rax),%rdi
   PC (0x0043984b) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke (closure=0x1f56320, return_value=0x0, n_param_values=2, 
param_values=0x7fff82bc6540, invocation_hint=0x7fff82bc64e0) at 
/build/buildd/glib2.0-2.41.4/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x1b12f30, detail=detail@entry=1242, 
instance=instance@entry=0x1c93aa0, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff82bc6540) at 
/build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3553
   g_signal_emit_valist (instance=, signal_id=, 
detail=, var_args=var_args@entry=0x7fff82bc66d0) at 
/build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3309
  Title: evince crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-15 (0 days ago)
  UserGroups: adm admin audio cdrom dialout kismet lp lpadmin plugdev 
sambashare video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1369894/+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 1369673] Re: LibreOffice kde file dialog integration broken (not working) in 14.04

[Björn Michaelsen]

note that 4.2.6 is a security update fixing:
http://www.libreoffice.org/about-us/security/advisories/cve-2014-3524/
http://www.libreoffice.org/about-us/security/advisories/cve-2014-3575/

At least one of those seems to affect Linux too.

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

Title:
  LibreOffice kde file dialog integration broken (not working) in 14.04

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Screenshot: http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-kde (not installed)
  Uname: Linux 3.16.2-031602-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Sep 15 19:17:48 2014
  InstallationDate: Installed on 2014-02-02 (224 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673/+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

[Andy Whitcroft]

This looks to be a bug in plymouth terminal handling.  Specifically it
appears that seat->terminal may be null and we should avoid attempting
to instantiate a text terminal on it in this case.

The attached patch gets us past this issue and up to lightdm.  I am
unsure if the splash is actually working correctly with it.

I have applied this patch for testing and pushed updated binaries to the
PPA below:

https://launchpad.net/~apw/+archive/ubuntu/lp1371651

If anyone affected by this could install these and test to see if they
resolve the issue.

** Attachment added: "PATCH"
   
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1371651/+attachment/4215190/+files/PATCH

-- 
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:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged

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=
   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 1372847] Re: [SRU] New stable release 2.40.1

[Brian Murray]

Hello Iain, or anyone else affected,

Accepted glib2.0 into trusty-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/glib2.0/2.40.2-0ubuntu1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: glib2.0 (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  [SRU] New stable release 2.40.1

Status in “glib2.0” package in Ubuntu:
  Fix Released
Status in “glib2.0” source package in Trusty:
  Fix Committed

Bug description:
  We'd like to update glib2.0 using the GNOME MRE.

  [ Description ]

  Upstream have released a new stable, fixing some bugs.

  glib2.0 (2.40.2-0ubuntu1) UNRELEASED; urgency=medium

* New upstream stable release, fixing bugs
  + gobject: try to link with -Wl,-z,nodelete to prevent unloading
  + g_file_copy: Don't set GError when we intend to ignore errors
  + gapplication-tool: ensure object paths are valid
  + gtlscertificate: fix certificate list parsing with trailing comments
  + g_str_has_prefix: improve efficiency with long strings
  + Added type check to GPermission public functions.
  + GApplication: Don't decrease use_count below 0
  + networkmonitornetlink: fix IPv6 issues on Android
  + gresolver: Ensure GThreadedResolver always sets an error if resolution
fails
  + gmacros.h: add G_GNUC_*_IGNORE_DEPRECATIONS macros for clang
  + networkaddress: fix parsing of uri with @ after authority
  + gvariant tests: workaround libc/compiler "issue"

   -- Iain Lane   Tue, 23 Sep 2014 10:27:17
  +0100

  [ QA ]

  Under the terms of the MRE, you can assume the bugs are fixed. I
  suggest installing the update and then using your system as normal for
  the 10 day verification time.

  [ Regression potential ]

  One of the fixes could be bad. This is the first stable in this series
  and is a new release, so hasn't had much testing on its own, even if
  all of the fixes are in the unstable release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1372847/+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 1328762] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvi

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd',
  which is also in package nvidia-opencl-icd-331 331.79-0ubuntu1

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Confirmed

Bug description:
  sound icon is gone on top bar

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-opencl-icd-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.15.0-5.10-lowlatency 3.15.0-rc8
  Uname: Linux 3.15.0-5-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 10 22:31:41 2014
  DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also 
in package nvidia-opencl-icd-331 331.79-0ubuntu1
  ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Alpha amd64 
(20140505)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1328762/+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 1072397] Re: [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] No sound at all

[Launchpad Bug Tracker]

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

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

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

Title:
  [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] No sound at
  all

Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  I am not able to hear sound sometimes. Please help me on this.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srinu  1880 F pulseaudio
   /dev/snd/pcmC0D1p:   srinu  1880 F...m pulseaudio
  Date: Sun Oct 28 13:14:18 2012
  InstallationDate: Installed on 2012-10-20 (7 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  srinu  1880 F pulseaudio
   /dev/snd/pcmC0D1p:   srinu  1880 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Dell System XPS L502X, Realtek ALC665, Speaker, Internal] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0YR8NN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1072397/+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 1328762] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvi

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd',
  which is also in package nvidia-opencl-icd-331 331.79-0ubuntu1

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Confirmed

Bug description:
  sound icon is gone on top bar

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-opencl-icd-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.15.0-5.10-lowlatency 3.15.0-rc8
  Uname: Linux 3.15.0-5-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 10 22:31:41 2014
  DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also 
in package nvidia-opencl-icd-331 331.79-0ubuntu1
  ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Alpha amd64 
(20140505)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1328762/+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 1328762] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvi

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-331 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd',
  which is also in package nvidia-opencl-icd-331 331.79-0ubuntu1

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Confirmed

Bug description:
  sound icon is gone on top bar

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-opencl-icd-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.15.0-5.10-lowlatency 3.15.0-rc8
  Uname: Linux 3.15.0-5-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 10 22:31:41 2014
  DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also 
in package nvidia-opencl-icd-331 331.79-0ubuntu1
  ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Alpha amd64 
(20140505)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1328762/+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 1328762] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvi

[Launchpad Bug Tracker]

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

** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty)
   Status: New => Confirmed

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

Title:
  package nvidia-opencl-icd-331-updates (not installed) failed to
  install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd',
  which is also in package nvidia-opencl-icd-331 331.79-0ubuntu1

Status in “nvidia-graphics-drivers-304” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu:
  Fix Released
Status in “nvidia-graphics-drivers-304” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-304-updates” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331” source package in Trusty:
  Confirmed
Status in “nvidia-graphics-drivers-331-updates” source package in Trusty:
  Confirmed

Bug description:
  sound icon is gone on top bar

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-opencl-icd-331-updates (not installed)
  ProcVersionSignature: Ubuntu 3.15.0-5.10-lowlatency 3.15.0-rc8
  Uname: Linux 3.15.0-5-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Tue Jun 10 22:31:41 2014
  DuplicateSignature: package:nvidia-opencl-icd-331-updates:(not 
installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also 
in package nvidia-opencl-icd-331 331.79-0ubuntu1
  ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  InstallationDate: Installed on 2014-06-10 (0 days ago)
  InstallationMedia: Ubuntu-Studio 14.10 "Utopic Unicorn" - Alpha amd64 
(20140505)
  SourcePackage: nvidia-graphics-drivers-331-updates
  Title: package nvidia-opencl-icd-331-updates (not installed) failed to 
install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is 
also in package nvidia-opencl-icd-331 331.79-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1328762/+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 493766] Re: Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

[Anders Kaseorg]

The different appearance of 0017-Further-improve-create_frame_xic-
patch.patch is due to the slightly different diff algorithms used by Git
and Bazaar (http://bramcohen.livejournal.com/37690.html); the actual
code change is identical.

If you want to sponsor a merge instead, the one already generated at
https://merges.ubuntu.com/e/emacs24/ has been working for me.

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

Title:
  Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Debian:
  Fix Released
Status in “emacs23” package in Fedora:
  Unknown

Bug description:
  Binary package hint: emacs23

  Ubuntu 9.10
  emacs23:
Installed: 23.1+1-4ubuntu3.1

  Using X with a configuration for SCIM input methods, environment
  variable XMODIFIERS then contains @im=SCIM

  Start emacs

  Hit Multi_key (aka Compose key, often bound to one of the Windows keys
  depending on keyboard layout and layout options) ' (single quote) e

  You should be getting é (e acute accent)

  Instead, emacs complains that  is undefined.

  Problem disappears if launching Emacs with XMODIFIERS="'

  ProblemType: Bug
  Architecture: i386
  Date: Mon Dec  7 21:56:37 2009
  DistroRelease: Ubuntu 9.10
  Package: emacs (not installed)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: emacs22
  Uname: Linux 2.6.31-16-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2548): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2537): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2536): Gdk-WARNING **: 
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a 
pixmap or window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/+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

[Andy Whitcroft]

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

** Changed in: plymouth (Ubuntu)
   Status: New => Triaged

** Changed in: plymouth (Ubuntu)
   Importance: Undecided => Critical

** Changed in: plymouth (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

-- 
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:
  Triaged
Status in “plymouth” package in Ubuntu:
  Triaged

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=
   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 1369673] Re: LibreOffice kde file dialog integration broken (not working) in 14.04

[Mads Bondo Dydensborg]

I have been able to downgrade my libreoffice installation to the
previous version, using these commands:

0) First, check all libreoffice related packages you have into a file:

dpkg -l  | grep libreoffice | tee libreoffice-packages

1) Then, purge all libreoffice packages

sudo apt-get remove --purge libreoffice-core libreoffice-common
libreoffice-style-oxygen

2) Then install the bulk of the previous version:

sudo apt-get install libreoffice-core=1:4.2.3~rc3-0ubuntu2 libreoffice-
common=1:4.2.3~rc3-0ubuntu2 libreoffice-style-
oxygen=1:4.2.3~rc3-0ubuntu2 libreoffice-kde=1:4.2.3~rc3-0ubuntu2
libreoffice=1:4.2.3~rc3-0ubuntu2 libreoffice-base=1:4.2.3~rc3-0ubuntu2
libreoffice-calc=1:4.2.3~rc3-0ubuntu2 libreoffice-
draw=1:4.2.3~rc3-0ubuntu2 libreoffice-impress=1:4.2.3~rc3-0ubuntu2
libreoffice-math=1:4.2.3~rc3-0ubuntu2 libreoffice-
writer=1:4.2.3~rc3-0ubuntu2 python3-uno=1:4.2.3~rc3-0ubuntu2
libreoffice-base-core=1:4.2.3~rc3-0ubuntu2 libreoffice-base-
drivers=1:4.2.3~rc3-0ubuntu2

3) Now, manually add as many of the packages that you had additionally
(check the contents of the libreoffice-packages file you created in the
0) step), as you can. In my case:

sudo apt-get install libreoffice-l10n-da=1:4.2.3~rc3-0ubuntu1
libreoffice-help-da=1:4.2.3~rc3-0ubuntu1 libreoffice-help-en-
us=1:4.2.3~rc3-0ubuntu1


I now have a working libreoffice installation that uses the KDE file dialog. 

One problem is left: that any apt-get upgrade will want to upgrade my
libreoffice installation, but I think you can mark them as "hold" for
the package system, if you want to avoid this. I'll handle it manually
for now.

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

Title:
  LibreOffice kde file dialog integration broken (not working) in 14.04

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Screenshot: http://www.dodaj.rs/f/22/pb/1Vu8cW0n/snapshot58.png

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libreoffice-kde (not installed)
  Uname: Linux 3.16.2-031602-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Sep 15 19:17:48 2014
  InstallationDate: Installed on 2014-02-02 (224 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1369673/+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 1247572] Re: Nokia Lumia 620 (WP8) fails to mount reliably via gvfs-mtp in nautilus

[Kiori]

another solution is to simply connect the device, ---then turn on the
pc. it worked for me. It still doesnt work with the pc already
on.(without workarounds)

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

Title:
  Nokia Lumia 620 (WP8) fails to mount reliably via gvfs-mtp in nautilus

Status in GVFS:
  Fix Released
Status in Nautilus:
  New
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “nautilus” package in Ubuntu:
  Invalid

Bug description:
  Summary: You have to run mtp-detect in terminal until you get output
  similar to the excerpt in the steps to reproduce section, then you can
  connect via nautilus as usual.

  -

  I just got a Nokia Lumia 620 as a backup phone. I'd say I can mount my
  Nexus 4 reliably with Ubuntu via nautilus using gvfs-mtp. Users with
  Android devices like the Nexus 4 still get error messages on a
  regularly basis of the device not being able to mount, but replugging
  the device mostly fixes the issue.

  However, the experience with the Lumia 620 is far worse (the desktop
  sometimes freezes) and the workaround I found to get the device to
  work very crude.

  I was prompted with a apport-collector window when nautilus froze
  during testing and send a report (this happend twice), but it didn't
  take me to Launchpad to open a report. I can also seen no bug
  regarding that topic that I am subscribed to.

  The Lumia 620 itself was added to libmtp with this report:
  http://sourceforge.net/p/libmtp/bugs/780/

  ## Steps to reproduce:

  1. Reboot (or cold boot) computer and phone. Login to computers destop and 
unlock the phone by entering PIN.
  2. Plug the phone via USB into the computer. (Cable works with Nexus 4 or 
another Android device.) The phone will give a signal that it is connected to 
the computer.
  3. Try to open the phone in Nautilus. My desktop either freezes (cold boot) 
here or nautilus hangs (reboot).

  3.a) If nautilus hangs: Open a terminal with Ctrl+Alt+T and kill nautilus 
with xkill.
  3.b) If your desktop froze: Go to a virtual terminal with Ctrl+Alt+F1.
  3.c) If you just get an error message: Open a terminal with Ctrl+Alt+T and go 
to step 4.

  4. Execute 'mtp-detect' (from mtp-tools package) from terminal (either
  via Dektop or virtual terminal). If you get one of the following
  messages wait a few seconds and try again.

    $ mtp-detect
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

    Listing raw device(s)
    Device 0 (VID=0421 and PID=0661) is a Nokia Nokia Lumia WP8.
   Found 1 device(s):
   Nokia: Nokia Lumia WP8 (0421:0661) @ bus 2, dev 22
    Attempting to connect device(s)
    ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, 
trying again after resetting USB interface
    LIBMTP libusb: Attempt to reset device
    LIBMTP PANIC: failed to open session on second attempt
    Unable to open raw device 0
    OK.

  ---

    $ mtp-detect
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

    Listing raw device(s)
    Device 0 (VID=0421 and PID=0661) is a Nokia Nokia Lumia WP8.
   Found 1 device(s):
   Nokia: Nokia Lumia WP8 (0421:0661) @ bus 2, dev 22
    Attempting to connect device(s)
    PTP_ERROR_IO: failed to open session, trying again after resetting USB 
interface
    LIBMTP libusb: Attempt to reset device
    LIBMTP PANIC: failed to open session on second attempt
    Unable to open raw device 0
    OK.

  ---

  Repeat this until you get a long list of scrolling text that ends with
  something similar to this:

    MTP-specific device properties:
   Friendly name: Windows Phone
   Synchronization partner: (NULL)
   Battery level 74 of 100 (74%)
    libmtp supported (playable) filetypes:
   Folder
   Text file
   ISO MPEG-1 Audio Layer 3
   Audio Video Interleave
   JPEG file
   Microsoft Windows Media Audio
   Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
   Microsoft Windows Media Video
   Abstract Album file
   Abstract Playlist file
   GIF bitmap file
   JFIF file
   Portable Network Graphics
   TIFF bitmap file
   BMP bitmap file
   MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
   MPEG-4 Part 14 Container Format (Audio Emphasis)
   DOC file
   XLS file
   PPT file
    OK.

  ---

  5. Go to a virtual terminal and do 'sudo service lightdm restart'.
  Login again, you hear the phone reconnecting to your computer and
  should now be able to open your phone in nautilus seeing the phones
  internal storage and the SD card (if there is) als sub devices.

  6. Unplug the phone from the computer and start with step 2 if you
  want to connect the phone again.

  ## Additional information

  $ lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  $ apt-cache policy 

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

[Andy Whitcroft]

Talking to the vbox startup "hangs" only, I have reproduced this locally
and we can see that plymouthd is SIGSEGVing during initialisation.  This
would most likley trigger the lack of events and prevent lightdm
startup.  Am investigating.

-- 
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=
   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 1369894] Re: evince crashed with SIGSEGV in ev_window_title_sanitize_title()

[Walter Garcia-Fontes]

** No longer affects: evince

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

** Also affects: evince via
   https://bugzilla.gnome.org/show_bug.cgi?id=737365
   Importance: Unknown
   Status: Unknown

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

Title:
  evince crashed with SIGSEGV in ev_window_title_sanitize_title()

Status in Evince document viewer:
  Unknown
Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Evince just crashed while it was open and idle.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: evince 3.13.91-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-14-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 16 09:24:16 2014
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2010-10-25 (1421 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=dadc68cb-c217-4aef-a751-ba0b61137c4a ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x43984b:  mov(%rax),%rdi
   PC (0x0043984b) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: evince
  StacktraceTop:
   ?? ()
   ?? ()
   g_closure_invoke (closure=0x1f56320, return_value=0x0, n_param_values=2, 
param_values=0x7fff82bc6540, invocation_hint=0x7fff82bc64e0) at 
/build/buildd/glib2.0-2.41.4/./gobject/gclosure.c:768
   signal_emit_unlocked_R (node=node@entry=0x1b12f30, detail=detail@entry=1242, 
instance=instance@entry=0x1c93aa0, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fff82bc6540) at 
/build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3553
   g_signal_emit_valist (instance=, signal_id=, 
detail=, var_args=var_args@entry=0x7fff82bc66d0) at 
/build/buildd/glib2.0-2.41.4/./gobject/gsignal.c:3309
  Title: evince crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-15 (0 days ago)
  UserGroups: adm admin audio cdrom dialout kismet lp lpadmin plugdev 
sambashare video www-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1369894/+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 1372494] Re: freezed screen at login next to suspension

[Savio Sosero]

Installing the drives owners nvidia 331,xx the problem has been solved

** Changed in: xdg-utils (Ubuntu)
 Assignee: (unassigned) => Savio Sosero (saviososero)

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

Title:
  freezed screen  at login next to suspension

Status in “xdg-utils” package in Ubuntu:
  New

Bug description:
  freezed screen  at login next to suspension

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1372494/+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 1289807] Re: User Accounts endless loop (never opens)

[Cecil Carpenter]

And one last apology.  I accidently hit the caps lock above.

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

Title:
  User Accounts endless loop (never opens)

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  Incomplete

Bug description:
  When I open the control center and click on User Accounts, the User Accounts 
never open.  It flashes and goes back to the control center screen.  The 
program then becomes unable to be closed.  I am required to kill the process 
manually.
  I cannot open any other options, after I click on the User Accounts option. 
  All options do the same thing... flash their screen and return to the control 
center, except the ones that launch an external application (U1, Language 
settings, etc...)
  Clicking on Time settings completely crashed the program, when it was in this 
state.
  Normally EVERY option just works as expected (other than the User Accounts)

  Obviously I am using Trusty (since this program just came into existence)
  Installed: 14.04.3+14.04.20140305.1-0ubuntu1
  Candidate: 14.04.3+14.04.20140305.1-0ubuntu1

  I can provide any more info, and testing needed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140305.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  8 09:54:01 2014
  InstallationDate: Installed on 2014-02-26 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140224)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1289807/+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 1289807] Re: User Accounts endless loop (never opens)

[Cecil Carpenter]

What a day.  I should have said I am running 14.04.1 x64 Gnome Flashback
(Metacity).

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

Title:
  User Accounts endless loop (never opens)

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  Incomplete

Bug description:
  When I open the control center and click on User Accounts, the User Accounts 
never open.  It flashes and goes back to the control center screen.  The 
program then becomes unable to be closed.  I am required to kill the process 
manually.
  I cannot open any other options, after I click on the User Accounts option. 
  All options do the same thing... flash their screen and return to the control 
center, except the ones that launch an external application (U1, Language 
settings, etc...)
  Clicking on Time settings completely crashed the program, when it was in this 
state.
  Normally EVERY option just works as expected (other than the User Accounts)

  Obviously I am using Trusty (since this program just came into existence)
  Installed: 14.04.3+14.04.20140305.1-0ubuntu1
  Candidate: 14.04.3+14.04.20140305.1-0ubuntu1

  I can provide any more info, and testing needed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140305.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  8 09:54:01 2014
  InstallationDate: Installed on 2014-02-26 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140224)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1289807/+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 1289807] Re: User Accounts endless loop (never opens)

[Cecil Carpenter]

Sorry about thaT, BUT THE AND FINALLY SHOULD BE FOLLWED WITH THIS.

dpkg -s libwayland0
Package: libwayland0
Status: install ok installed
Priority: extra
Section: oldlibs
Installed-Size: 28
Maintainer: Ubuntu Developers 
Architecture: all
Source: wayland
Version: 1.4.0-1ubuntu1
Depends: libwayland-client0, libwayland-server0dpkg -s libwayland0
Package: libwayland0
Status: install ok installed
Priority: extra
Section: oldlibs
Installed-Size: 28
Maintainer: Ubuntu Developers 
Architecture: all
Source: wayland
Version: 1.4.0-1ubuntu1
Depends: libwayland-client0, libwayland-server0
Description: transitional dummy package
 This transitional dummy package is safe to remove.
Original-Maintainer: Debian X Strike Force 
Homepage: http://wayland.freedesktop.org/
Description: transitional dummy package
 This transitional dummy package is safe to remove.
Original-Maintainer: Debian X Strike Force 
Homepage: http://wayland.freedesktop.org/

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

Title:
  User Accounts endless loop (never opens)

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  Incomplete

Bug description:
  When I open the control center and click on User Accounts, the User Accounts 
never open.  It flashes and goes back to the control center screen.  The 
program then becomes unable to be closed.  I am required to kill the process 
manually.
  I cannot open any other options, after I click on the User Accounts option. 
  All options do the same thing... flash their screen and return to the control 
center, except the ones that launch an external application (U1, Language 
settings, etc...)
  Clicking on Time settings completely crashed the program, when it was in this 
state.
  Normally EVERY option just works as expected (other than the User Accounts)

  Obviously I am using Trusty (since this program just came into existence)
  Installed: 14.04.3+14.04.20140305.1-0ubuntu1
  Candidate: 14.04.3+14.04.20140305.1-0ubuntu1

  I can provide any more info, and testing needed

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140305.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar  8 09:54:01 2014
  InstallationDate: Installed on 2014-02-26 (10 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140224)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu10
   deja-dup 29.5-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1289807/+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 445333] Re: remember password on printing to windows printers does not work

[Ubuntu Foundations Team Bug Bot]

The attachment "gtk+2.0_2.24.24-0ubuntu2.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff.  If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Triaged
Status in “gtk+3.0” package in Ubuntu:
  Fix Committed
Status in “gtk+2.0” source package in Trusty:
  Triaged
Status in “gtk+3.0” source package in Trusty:
  Triaged

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a "remember password" checkbox, but it keeps asking me when 
printing the next document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/445333/+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 1374030] [NEW] Dropbox crash on Ubuntu MATE Remix

[ ͡° ͜ʖ ͡°]

Public bug reported:

I'm getting "Attempt to unlock mutex that was not locked" and a segfault
when running Ubuntu MATE Remix 14.10.

It seems this bug is reported elsewhere in a number of other packages
and is a result of a change in GLib ≥ 2.41.

I am told this patch can fix it.

https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec

Bug 1346299 & bug 1344386 are related (similar issue, different app).

Note that as this is dropbox, we cannot easily fix there as it's
proprietary.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  I'm getting "Attempt to unlock mutex that was not locked" and a segfault
  when running Ubuntu MATE Remix 14.10.
  
  It seems this bug is reported elsewhere in a number of other packages
  and is a result of a change in GLib ≥ 2.41.
  
  I am told this patch can fix it.
  
  https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec
  
- Bug 1346299 is related (similar issue, different app).
+ Bug 1346299 & bug 1344386 are related (similar issue, different app).
  
  Note that as this is dropbox, we cannot easily fix there as it's
  proprietary.

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

Title:
  Dropbox crash on Ubuntu MATE Remix

Status in “gtk+3.0” package in Ubuntu:
  New

Bug description:
  I'm getting "Attempt to unlock mutex that was not locked" and a
  segfault when running Ubuntu MATE Remix 14.10.

  It seems this bug is reported elsewhere in a number of other packages
  and is a result of a change in GLib ≥ 2.41.

  I am told this patch can fix it.

  https://github.com/GNOME/gtk/commit/79c3ff3c4ed74bbcc820dac2d5180fa4d48d55ec

  Bug 1346299 & bug 1344386 are related (similar issue, different app).

  Note that as this is dropbox, we cannot easily fix there as it's
  proprietary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1374030/+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 493766] Re: Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

[Robie Basak]

17:14  If someone wants to sponsor emacs24 in bug 493766 it looks fine 
   to me but I've just noticed it's in main so I can't upload it.
17:14  (though a merge would be better)

Sorry! One minor note: Origin: backport would be more appropriate for
0017-Further-improve-create_frame_xic-patch.patch as it looks slightly
different to what was committed upstream. But I see that it is what went
into Debian too.

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

Title:
  Multi_key / compose does not work when XMODIFIERS="@im=SCIM"

Status in “emacs23” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Ubuntu:
  Confirmed
Status in “emacs24” package in Debian:
  Fix Released
Status in “emacs23” package in Fedora:
  Unknown

Bug description:
  Binary package hint: emacs23

  Ubuntu 9.10
  emacs23:
Installed: 23.1+1-4ubuntu3.1

  Using X with a configuration for SCIM input methods, environment
  variable XMODIFIERS then contains @im=SCIM

  Start emacs

  Hit Multi_key (aka Compose key, often bound to one of the Windows keys
  depending on keyboard layout and layout options) ' (single quote) e

  You should be getting é (e acute accent)

  Instead, emacs complains that  is undefined.

  Problem disappears if launching Emacs with XMODIFIERS="'

  ProblemType: Bug
  Architecture: i386
  Date: Mon Dec  7 21:56:37 2009
  DistroRelease: Ubuntu 9.10
  Package: emacs (not installed)
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
  SourcePackage: emacs22
  Uname: Linux 2.6.31-16-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2488): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2548): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2537): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (gnome-panel:2536): Gdk-WARNING **: 
/build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a 
pixmap or window

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/493766/+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 1289807] Re: User Accounts endless loop (never opens)

[Cecil Carpenter]

I have the same problem as originally described.  However, I have the
following message when running

unity-control-center user-accounts

in a terminal

My messages are

libwayland_ltst-client.so.0: cannot open shared object file: No such file or 
directory
Failed to load module: 
/usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libuser-accounts.so

In my case, libwayland_ltst-client.so.0 is not in my system.  In fact it
belongs to a the package libwayland-ltst-client0 that is a Precise
upgrade of the HWE to the Trusty stack.  I upgraded from 12.04.5 ->
14.04.1.  So I cannot understand why libwayland_ltst-client.so.0 is
being called.

If I open Applications>Systems Settings>any other applet, they work.
However, if I start User Accounts, the panel never comes up, and all
apps no longer work even though their tab appears.  If I try to kill the
process, I have to do it over and over.  I can also click the X on the
window multiple times, and the window will eventually close.

Here is what I get if I use the dpkg command:

dpkg -s libwayland-ltst-client0
Package: libwayland-ltst-client0
Status: deinstall ok config-files
Priority: optional
Section: libs
Installed-Size: 90
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: same
Source: wayland-lts-trusty
Version: 1.4.0-1ubuntu1~precise1
Config-Version: 1.4.0-1ubuntu1~precise1
Replaces: libwayland0-lts-trusty (<< 1.1.0-1)
Depends: libc6 (>= 2.14), libffi6 (>= 3.0.4)
Pre-Depends: multiarch-support
Conflicts: libwayland0-lts-trusty (<< 1.1.0-1)
Description: wayland compositor infrastructure - client library
 Wayland is a protocol for a compositor to talk to its clients as well
 as a C library implementation of that protocol. The compositor can be
 a standalone display server running on Linux kernel modesetting and
 evdev input devices, an X application, or a wayland client
 itself. The clients can be traditional applications, X servers
 (rootless or fullscreen) or other display servers.
 .
 This package ships the library that implements the client side of
 the Wayland protocol.
Homepage: http://wayland.freedesktop.org/
Original-Maintainer: Debian X Strike Force 

Here is dpkg for libwayland-client0.

dpkg -s libwayland-client0
Package: libwayland-client0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 90
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: same
Source: wayland
Version: 1.4.0-1ubuntu1
Replaces: libwayland0 (<< 1.1.0-1)
Depends: libc6 (>= 2.14), libffi6 (>= 3.0.4)
Pre-Depends: multiarch-support
Conflicts: libwayland0 (<< 1.1.0-1)
Description: wayland compositor infrastructure - client library
 Wayland is a protocol for a compositor to talk to its clients as well
 as a C library implementation of that protocol. The compositor can be
 a standalone display server running on Linux kernel modesetting and
 evdev input devices, an X application, or a wayland client
 itself. The clients can be traditional applications, X servers
 (rootless or fullscreen) or other display servers.
 .
 This package ships the library that implements the client side of
 the Wayland protocol.
Original-Maintainer: Debian X Strike Force 
Homepage: http://wayland.freedesktop.org/

And finally

dpkg -s libwayland-client0
Package: libwayland-client0
Status: install ok installed
Priority: optional
Section: libs
Installed-Size: 90
Maintainer: Ubuntu Developers 
Architecture: amd64
Multi-Arch: same
Source: wayland
Version: 1.4.0-1ubuntu1
Replaces: libwayland0 (<< 1.1.0-1)
Depends: libc6 (>= 2.14), libffi6 (>= 3.0.4)
Pre-Depends: multiarch-support
Conflicts: libwayland0 (<< 1.1.0-1)
Description: wayland compositor infrastructure - client library
 Wayland is a protocol for a compositor to talk to its clients as well
 as a C library implementation of that protocol. The compositor can be
 a standalone display server running on Linux kernel modesetting and
 evdev input devices, an X application, or a wayland client
 itself. The clients can be traditional applications, X servers
 (rootless or fullscreen) or other display servers.
 .
 This package ships the library that implements the client side of
 the Wayland protocol.
Original-Maintainer: Debian X Strike Force 
Homepage: http://wayland.freedesktop.org/

Fortunately, the command

users-admin

is still around.  I believe it would not have been there had I done a
clean install.  Perhaps I would not have had this problem if I had done
a clean install.  In any case, there is definitely something wrong if
the commnad

unity-control-center user-accounts

wants to load libwayland_ltst-client.so.0.

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

Title:
  User Accounts endless loop (never opens)

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New
Status in “unity-control-center” package in Ubuntu:
  Incomplete

Bug description:
  When I open

[Desktop-packages] [Bug 1302416] Re: deja-dup monitor was taking 6GB of memory

[R Lorentz]

Following up on the above, I went to Settings - Backups - Back Up Now to
manually start a backup and had the same result. Most of my memory was
consumed, never to be returned.

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

Title:
  deja-dup monitor was taking 6GB of memory

Status in “deja-dup” package in Ubuntu:
  Confirmed

Bug description:
  Booted fresh, computer started to be slow and after a while i realized
  deja-dup monitor was taking 6GB of memory. Haven't tried rebooted
  again. Will do so in a moment.

  Sorry can't provide more info :/

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: deja-dup 30.0-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr  4 09:40:07 2014
  InstallationDate: Installed on 2011-11-21 (864 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=ca_ES
   TERM=xterm
   PATH=(custom, no user)
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1302416/+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 1365769] Re: [pulseaudio-discuss] [V4 PATCH] module-switch-on-connect: add an argument for conditionally connecting

[Raymond]

>>
>> >
>> > On a machine without fixed connecting audio devices like internal
>> > microphone or internal speaker, and when there is no external audio
>> > devices plugging in, the default source/sink is alsa_input/alsa_output
>> > and there is no input devices/output devices listed in the gnome
>> > sound-setting.

https://launchpadlibrarian.net/184055917/PulseList.txt

Seem line in is active port when all ports are not available
Pulseaudio won't switch away from line in but gnome won't show line in
since it is not plugged

ports:
analog-input-microphone-front: Front Microphone (priority 8500, latency
offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-microphone-rear: Rear Microphone (priority 8200, latency
offset 0 usec, available: no)
properties:
device.icon_name = "audio-input-microphone"
analog-input-linein: Line In (priority 8100, latency offset 0 usec,
available: no)
properties:

active port: 

https://launchpadlibrarian.net/184417469/alsa2.txt

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

Title:
  [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  The problem is that the microphone is not detected after a reboot.  As
  a result, some applications cannot get sound from the microphone.

  The Input tab of the Sound window lists no device.

  I have a workround which is to disconnect and then connect the
  microphone after I have logged in.

  Interestingly, the audacity application can access the microphone when
  the system says that the device does not exist

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
  Uname: Linux 3.2.0-67-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep  5 00:12:39 2014
  InstallationDate: Installed on 2011-07-29 (1133 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tim2060 F pulseaudio
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: No sound at all
  Title: [G41MT-S2P, VIA VT2020, Pink Mic, Rear] No sound at all
  UpgradeStatus: Upgraded to trusty on 2014-08-15 (20 days ago)
  dmi.bios.date: 12/31/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: G41MT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2010:svnGigabyteTechnologyCo.,Ltd.:pnG41MT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41MT-S2P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41MT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1365769/+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 1264657] Re: No icon padding

[Jiří Podvolecký]

Second start of liveUSB. That's all. There is bug of this kind styl in
Utopic Beta 2.

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

Title:
  No icon padding

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  After 2nd root Ubuntu there is no icon padding. There is two icons on
  one place.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu7
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.336ubuntu1
  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
  CurrentDmesg:
   
  Date: Sat Dec 28 10:50:55 2013
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation NV43 [GeForce 6600] [10de:0141] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:9791]
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131228)
  Lsusb:
   Bus 001 Device 003: ID 13fe:3800 Kingston Technology Company Inc. Rage XT 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 045e:0083 Microsoft Corp. Basic Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-7100
  ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed 
boot=casper  quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz.efi
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/17/2005
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7100
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/17/2005:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7100:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7100:rvr1.0:cvn:ct3:cvr:
  dmi.product.name: MS-7100
  dmi.product.version: 1.0
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.50-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu1
  xserver.bootTime: Sat Dec 28 10:45:36 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputMicrosoft Basic Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1264657/+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

[Elfy]

bah - wishing you could edit comments

I wonder if there's another issue - eg I'm always trying to do this from
a vbox installed in a utopic install

-- 
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=
   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

[Chris J Arges]

@jamesodhunt
Disabling 'quiet splash' doesn't seem to reproduce the issue in the 20 reboots 
I attempted.

-- 
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=
   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

[Elfy]

@jamesodhunt - each and every time that I've tried since this bug
surfaced - I've not got anyway to sit here doing hundreds manually
obviously :)

-- 
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=
   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 1216059] Re: Firefox difficulties with https and IPv6 addresses

[Launchpad Bug Tracker]

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

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

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

Title:
  Firefox difficulties with https and IPv6 addresses

Status in The Dell PowerEdge project:
  Confirmed
Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  When a webserver uses an untrusted certificate (such as a self-signed
  certificate), Firefox encounters multiple bugs trying to use https
  over IPv6. The main upstream bug report is
   but
   also seems
  relevant.

  On Ubuntu 12.04 with firefox package 23.0+build2-0ubuntu0.12.04.1, I
  am not even prompted to add a security exception. I found that with
  Firefox on Ubuntu 10.04, I am prompted to add a security exception but
  have no way to click "add exception" (though we only care about Ubuntu
  12.04 for PowerEdge). This is problematic for Dell because iDRAC and
  CMC ship with self-signed certificates, so there is no way to reach
  the iDRAC or CMC web interface over IPv6 from Firefox. I see the same
  behavior whether entering an IPv6 address (e.g.
  https://[2001:DB8::1]/), when manually specifying the port (e.g.
  https://[2001:DB8::1]:443/) or when specifying a hostname with only an
   record (e.g. https://host-ipv6.example.com/). The same URLs work
  with Chromium.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1216059/+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