[Desktop-packages] [Bug 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.

[Launchpad Bug Tracker]

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

** Changed in: xdg-utils (Ubuntu)
   Status: New => Confirmed

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

Title:
  Shows "Chromium isn't your default browser" since 15.10.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xdg-utils package in Ubuntu:
  Confirmed

Bug description:
  Since the 15.10.  upgrade Chromium shows on every launch "Chromium
  isn't your default browser", even when i select "Set as default" or
  "Don't ask again".

  Chromium is set as default application for "Web" at System Settings ->
  Details -> Default Applications.

  Version 45.0.2454.101 Ubuntu 15.10 (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+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 1515031] Re: Release no-change rebuild for ocaml transition

[Martin Pitt]

Uploaded.

** Changed in: llvm-toolchain-3.6 (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Release no-change rebuild for ocaml transition

Status in llvm-toolchain-3.6 package in Ubuntu:
  Fix Committed

Bug description:
  Even though the package didn't explicitly fail to install due to
  ocaml, the build deps clearly say ocaml-nox. The package currently
  fails to install due to other, non-related installability issues but a
  rebuild against the new ocaml could be done anyway to make sure this
  doesn't get in our way later.

  Attaching debdiff.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.6/+bug/1515031/+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 1508177] Re: [SRU] Starting LibreOffice with an empty profile from the ISO creates a profile selecting galaxy, not human as theme

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:5.0.2-0ubuntu5

---
libreoffice (1:5.0.2-0ubuntu5) xenial; urgency=medium

  * No-change rebuild against libglew1.13.

 -- Steve Langasek   Thu, 12 Nov 2015
03:21:58 +

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Starting LibreOffice with an empty profile from the ISO creates
  a profile selecting galaxy, not human as theme

Status in Release Notes for Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Wily:
  New

Bug description:
  [Impact]
  Severely reduces the initial impression of LibreOffice on a fresh install 
from ISO.

  [Test Case]
  STEPS:
  1. Install the latest daily cd image
  2. Open libreoffice writer check the theme and close it

  EXPECTED:
  I expect the theme to always be human unless I explicitly change it

  ACTUAL:
  The default theme on a new install is galaxy, though human is installed.

  (Alternatively: Test what theme LibreOffice selects when
  ~/.config/libreoffice is rm-rfed and there are libreoffice-style-human
  and libreoffice-style-galaxy installed)

  [Regression Potential]
  Very low. No fallout expected from the change back to a better default theme: 
Trivial low risk two-line fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1508177/+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 1515767] Re: Nautilus does not follow HIDPI setting

[Alex Thompson]

My display is 2560x1440. I have the HIDPI setting at 1.75 to increase
text and icon sizes (giving an effective screen resolution of
~1463x883).

If the HIDPI setting is 1, text and icons are small in all applications.
When I increase the HIDPI setting (eg. to 1.75), font sizes and icons
increase in size, but nautilus does not change. I expect nautilus to
have an increased font size and icon size. I can attach screenshots to
clarify this, as I don't think my explanation is clear.

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

Title:
  Nautilus does not follow HIDPI setting

Status in nautilus package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading from 15.04 to 15.10, nautilus does not follow the
  HIDPI settings from System Settings -> Screen Display after
  boot/login. Restarting nautilus corrects corrects this and it follows
  the HIDPI settings.

  1) Ubuntu 15.10
  2 nautilus:
Installed: 1:3.14.2-0ubuntu13
Candidate: 1:3.14.2-0ubuntu13
Version table:
   *** 1:3.14.2-0ubuntu13 0
  500 http://archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:3.14.2-0ubuntu12 0
  500 http://archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

  3) I expect HIDPI settings to be followed on boot/login without restarting 
nautilus
  4) HIDPI settings are only followed after killing and restarting nautilus

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 12 20:25:50 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-11-14 (363 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to wily on 2015-11-04 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1515767/+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 1337898] Re: Invalid symlinks for libungif.so and libungif.a

[Launchpad Bug Tracker]

This bug was fixed in the package giflib - 5.1.1-0ubuntu1

---
giflib (5.1.1-0ubuntu1) xenial; urgency=medium

  * New upstream version.
  * Enable parallel builds.
  * Build-depend on xmlto.
  * Don't ship broken libungif symlinks. Closes: #732272. LP: #1337898.

 -- Matthias Klose   Wed, 21 Oct 2015 16:28:17 +0200

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

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

Title:
  Invalid symlinks for libungif.so and libungif.a

Status in giflib package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 14.04 LTS on x86_64 I am experiencing the following bug in
  libgif-dev 4.1.6-11:

  Symbol links for libungif.a, libungif.la, and libungif.so are created
  in /usr/lib that point to libgif.a, libgif.la and libgif.so.4.1.6
  respectively. However, these files are not in /usr/lib but in
  /usr/lib/x86_64-linux-gnu. Therefore, the symbol links are invalid.

  I suggest fixing this by placing the symbol links in the same
  directory as the target files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/giflib/+bug/1337898/+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 1506544] Re: Change default Theme for LibreOffice to Breeze for Ubuntu 16.04

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:5.0.2-0ubuntu5

---
libreoffice (1:5.0.2-0ubuntu5) xenial; urgency=medium

  * No-change rebuild against libglew1.13.

 -- Steve Langasek   Thu, 12 Nov 2015
03:21:58 +

** Changed in: libreoffice (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Change default Theme for LibreOffice to Breeze for Ubuntu 16.04

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  Breeze has a much more pleasing appearance and is better maintained
  than the human theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1506544/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

This bug probably targets on how to avoid this driver behavior's change.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1487148] Re: Please replace xfonts-mathml with fonts-stix in recommends

[Launchpad Bug Tracker]

This bug was fixed in the package libreoffice - 1:5.0.2-0ubuntu5

---
libreoffice (1:5.0.2-0ubuntu5) xenial; urgency=medium

  * No-change rebuild against libglew1.13.

 -- Steve Langasek   Thu, 12 Nov 2015
03:21:58 +

** Changed in: libreoffice (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Please replace xfonts-mathml with fonts-stix in recommends

Status in libreoffice package in Ubuntu:
  Fix Released

Bug description:
  The libreoffice-common package currently recommends xfonts-mathml,
  which was removed from Debian in 2014 with the rationale that it is
  superseded by fonts-stix (and that it has a license problem).  Please
  replace it with fonts-stix.

  Since xfonts-mathml is only a Recommends: rather than Depends:, I'm
  going to go ahead and remove xfonts-mathml from wily.  If for some
  reason fonts-stix is not a suitable replacement and xfonts-mathml is
  still needed, please feel free to reupload it to the archive and close
  this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1487148/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

Since Linux kernel v3.18-rc1, it contains

commit e6755fb78e8f20ecadf2a4080084121336624ad9
Author: Jani Nikula 
Date:   Tue Aug 12 17:11:42 2014 +0300

drm/i915: switch off backlight for backlight class 0 brightness

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1515972] [NEW] Xorg crash

[Hans-Christian Payer]

Public bug reported:

xorg randomly and quite often (once an hour) crashes back to loginscreen, when 
klicking on various buttons (you can never say which button).
ProblemType: Crash
Architecture: amd64
Date: Fri Nov 13 12:20:39 2015
DistroRelease: Ubuntu 15.10
ExecutablePath: /usr/bin/Xorg
ExecutableTimestamp: 1443604291
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Nov 13 12:34:50 2015
DistUpgraded: 2015-10-20 12:22:39,151 DEBUG enabling apt cron job
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.3.26: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:21da]
InstallationDate: Installed on 2014-06-29 (501 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 4291QS0
ProcEnviron:
 LANGUAGE=de_AT:de
 TERM=screen
 PATH=(custom, no user)
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to wily on 2015-10-20 (24 days ago)
dmi.bios.date: 08/02/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET51WW (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4291QS0
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8DET51WW(1.21):bd08/02/2011:svnLENOVO:pn4291QS0:pvrThinkPadX220:rvnLENOVO:rn4291QS0:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4291QS0
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Fri Nov 13 12:20:48 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 728 
 vendor LGD
xserver.version: 2:1.17.2-1ubuntu9

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


** Tags: amd64 apport-bug compiz-0.9 crash ubuntu wily

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  xorg randomly and quite often (once an hour) crashes back to loginscreen, 
when klicking on various buttons (you can never say which button).
  ProblemType: Crash
  Architecture: amd64
  Date: Fri Nov 13 12:20:39 2015
  DistroRelease: Ubuntu 15.10
  ExecutablePath: /usr/bin/Xorg
  ExecutableTimestamp: 1443604291
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Nov 13 12:34:50 2015
  DistUpgraded: 2015-10-20 12:22:39,151 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: vboxhost, 4.3.26: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller 

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Shih-Yuan Lee]

Reverting that commit can easily fix this issue or we need to fix all
userspace programs related to the brightness control.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1515909] [NEW] [Macmini7, 1, Cirrus Logic CS4208, Green Headphone Out, N/A] No sound at all

[Miro]

Public bug reported:

The sound is played from the internal speaker only.
Funny thing is that when I disconnect the jack the sound device in sound 
settings goes from Speakers to Headphones (which is the opposite) and the sound 
stops playing even from the internal speaker.

It looks like the output switch is reverted to the jack indicator.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  miro   2402 F pulseaudio
 /dev/snd/controlC1:  miro   2402 F pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 13 09:39:08 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-11-11 (1 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lightdm1971 F pulseaudio
  miro   2402 F pulseaudio
 /dev/snd/controlC1:  lightdm1971 F pulseaudio
  miro   2402 F pulseaudio
Symptom_Jack: Green Headphone Out, N/A
Symptom_Type: No sound at all
Title: [Macmini7,1, Cirrus Logic CS4208, Green Headphone Out, N/A] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MM71.88Z.0220.B06.1509081252
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-35C5E08120C7EEAF
dmi.board.vendor: Apple Inc.
dmi.board.version: Macmini7,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-35C5E08120C7EEAF
dmi.modalias: 
dmi:bvnAppleInc.:bvrMM71.88Z.0220.B06.1509081252:bd09/08/2015:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:
dmi.product.name: Macmini7,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug wily

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

Title:
  [Macmini7,1, Cirrus Logic CS4208, Green Headphone Out, N/A] No sound
  at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The sound is played from the internal speaker only.
  Funny thing is that when I disconnect the jack the sound device in sound 
settings goes from Speakers to Headphones (which is the opposite) and the sound 
stops playing even from the internal speaker.

  It looks like the output switch is reverted to the jack indicator.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  miro   2402 F pulseaudio
   /dev/snd/controlC1:  miro   2402 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 09:39:08 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-11 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lightdm1971 F pulseaudio
miro   2402 F pulseaudio
   /dev/snd/controlC1:  lightdm1971 F pulseaudio
miro   2402 F pulseaudio
  Symptom_Jack: Green Headphone Out, N/A
  Symptom_Type: No sound at all
  Title: [Macmini7,1, Cirrus Logic CS4208, Green Headphone Out, N/A] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MM71.88Z.0220.B06.1509081252
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C5E08120C7EEAF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: Macmini7,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C5E08120C7EEAF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMM71.88Z.0220.B06.1509081252:bd09/08/2015:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:
  dmi.product.name: Macmini7,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about 

[Desktop-packages] [Bug 1377546] Re: evince gets Gtk-CRITICAL errors

[Hao Hu]

I can confirm this still happens on 15.10 with any pdf file.

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

Title:
  evince gets Gtk-CRITICAL errors

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  evice alwas gets following errors when opening a PDF file:

  (evince:3932): GLib-GObject-WARNING **: The property GtkSettings:gtk-
  menu-images is deprecated and shouldn't be used anymore. It will be
  removed in a future version.

  (evince:3932): Gtk-CRITICAL **: gtk_widget_show: assertion
  'GTK_IS_WIDGET (widget)' failed

  (evince:3932): Gtk-CRITICAL **: gtk_widget_show: assertion
  'GTK_IS_WIDGET (widget)' failed

  Here is the release information:

  jchen@utopic:~$ lsb_release -rd
  Description:  Ubuntu Utopic Unicorn (development branch)
  Release:  14.10
  jchen@utopic:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: evince 3.14.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
  Uname: Linux 3.16.0-20-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  4 19:33:41 2014
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2014-10-03 (1 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1377546/+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 1509139] Re: Shows "Chromium isn't your default browser" since 15.10.

[Nikolai Kristiansen]

** Also affects: xdg-utils (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Shows "Chromium isn't your default browser" since 15.10.

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in xdg-utils package in Ubuntu:
  New

Bug description:
  Since the 15.10.  upgrade Chromium shows on every launch "Chromium
  isn't your default browser", even when i select "Set as default" or
  "Don't ask again".

  Chromium is set as default application for "Web" at System Settings ->
  Details -> Default Applications.

  Version 45.0.2454.101 Ubuntu 15.10 (64-bit)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1509139/+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 1515763] Re: Merge from debian 2.8.14-1.2

[Martin Pitt]

Uploaded, thanks!

** Changed in: gimp (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Merge from debian 2.8.14-1.2

Status in gimp package in Ubuntu:
  Fix Committed

Bug description:
  Merge from debian 2.8.14-1.2 
  Installs appstream data

  debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1515763/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Shih-Yuan Lee]

There is no gateway information in Network Manager.

** Attachment added: "ConnectionInformation.png"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1441095/+attachment/4518085/+files/ConnectionInformation.png

** Description changed:

  [Impact]
  
-  * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
+  * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.
  
  [Test Case]
  
-  * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
+  * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).
  
-  * Insert the SIM, boot the Ubuntu system, and connect to Internet by
+  * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.
  
  [Regression Potential]
  
-  * No trivial regression so far.
+  * No trivial regression so far.
  
  [Other Info]
-  
-  * None
+ 
+  * There is no gateway information in Network Manager. (See the picture in 
comment #74)
+   * Some ISPs like TW Mobile in Taiwan don't need the gateway to connect to 
Internet.
+   * Some ISPs like Chunghwa Telecom in Taiwan do need the gateway to connect 
to Internet.
+   * We need to see the gateway information in Network Manager to cover all 
ISPs.
  
  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-branded
  modems, as we don't have MBIM support in the Novatel plugin.
  
  So, we should try to improve the probing in the Novatel, Sierra and MBM
  plugins, so that they probe also Dell devices, and we'll then try to
  match via AT-probing which plugin should be handling the Dell device.
  
  https://bugs.freedesktop.org/show_bug.cgi?id=86713
  
  Could we backport this patch  into trusty? Thanks!

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]

   * There is no gateway information in Network Manager. (See the picture in 
comment #74)
* Some ISPs like TW Mobile in Taiwan don't need the gateway to connect to 
Internet.
* Some ISPs like Chunghwa Telecom in Taiwan do need the gateway to connect 
to Internet.
* We need to see the gateway information in Network Manager to cover all 
ISPs.

  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmbim/+bug/1441095/+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 1515911] Re: unity-control-center is not fully translated

[Sebastien Bacher]

** Changed in: gnome-menus (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-menus (Ubuntu)
   Status: New => In Progress

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

Title:
  unity-control-center is not fully translated

Status in gnome-menus package in Ubuntu:
  In Progress

Bug description:
  unity-control-center is not fully translated
  see Personal ; Hardware ; System

  https://dl.dropboxusercontent.com/u/26959244/manque_traduction_unity-
  control-center.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1515911/+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 1515810] Re: Doesn't merge into unity panel when maximized

[Sebastien Bacher]

** Tags added: rls-x-incoming

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

Title:
  Doesn't merge into unity panel when maximized

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  In a ubuntu session open gedit, maximize.
  I guess because it doesn't use window deco (unity) when maximized you get 2 
sets of action buttons, one from gedit in toolbar, one from light-themes in 
unity panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 12 19:04:02 2015
  InstallationDate: Installed on 2015-10-25 (18 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1515810/+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 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->sta

[Ilya Kharin]

15.04 on every boot appears.

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

Title:
  colord-sane assert failure: colord-sane: simple-watch.c:454:
  avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT ||
  s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed.

Status in sane-backends package in Ubuntu:
  Confirmed

Bug description:
  Upgraded from 14.04 to 14.10 alpha.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: colord 1.2.1-1ubuntu1
  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-0ubuntu2
  Architecture: amd64
  AssertionMessage: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: 
Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state 
== STATE_FAILURE' failed.
  Date: Fri Aug  1 14:00:57 2014
  ExecutablePath: /usr/lib/colord/colord-sane
  InstallationDate: Installed on 2013-12-26 (217 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  ProcCmdline: /usr/lib/colord/colord-sane
  ProcEnviron:
   
  Signal: 6
  SourcePackage: colord
  StacktraceTop:
   __assert_fail_base (fmt=0x7fcda3d688b0 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x7fcd926f9fb0 "s->state == STATE_INIT 
|| s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", 
file=file@entry=0x7fcd926f9ee8 "simple-watch.c", line=line@entry=454, 
function=function@entry=0x7fcd926fa140 "avahi_simple_poll_prepare") at 
assert.c:92
   __GI___assert_fail (assertion=0x7fcd926f9fb0 "s->state == STATE_INIT || 
s->state == STATE_DISPATCHED || s->state == STATE_FAILURE", file=0x7fcd926f9ee8 
"simple-watch.c", line=454, function=0x7fcd926fa140 
"avahi_simple_poll_prepare") at assert.c:101
   avahi_simple_poll_prepare () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   avahi_simple_poll_iterate () from 
/usr/lib/x86_64-linux-gnu/libavahi-common.so.3
   ?? () from /usr/lib/x86_64-linux-gnu/sane/libsane-kodakaio.so.1
  Title: colord-sane assert failure: colord-sane: simple-watch.c:454: 
avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == 
STATE_DISPATCHED || s->state == STATE_FAILURE' failed.
  UpgradeStatus: Upgraded to utopic on 2014-07-31 (0 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+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 1512274] Re: Sync libvdpau 1.1.1-3 (main) from Debian sid (main)

[Martin Pitt]

This bug was fixed in the package libvdpau - 1.1.1-3
Sponsored for Oibaf (oibaf)

---
libvdpau (1.1.1-3) unstable; urgency=medium

  [ Luca Boccassi ]
  * Cherry-pick patch for DRI_PRIME crash. (Closes: #802625)
  * Upload to unstable.

 -- Andreas Beckmann   Thu, 29 Oct 2015 00:47:28 +0100

libvdpau (1.1.1-2) experimental; urgency=medium

  * Add vdpau-driver-all driver metapackage.  (Closes: #800657)
  * libvdpau1: Recommends: vdpau-driver-all | vdpau-driver.
  * Upload to experimental.

 -- Andreas Beckmann   Thu, 08 Oct 2015 10:15:00 +0200

libvdpau (1.1.1-1) unstable; urgency=medium

  [ Andreas Beckmann ]
  * simplify d/rules

  [ Luca Boccassi ]
  * New upstream release.
- Use secure_getenv(3) to improve security
  (CVE-2015-5198, CVE-2015-5199, CVE-2015-5200). Closes: #797895.
  * Do not check for pdftex, removed upstream
  * Add myself to Uploaders
  * Refresh dlopen-path patch, upstream changes
  * Refresh patch module-searchpath, upstream changes

 -- Luca Boccassi   Thu, 03 Sep 2015 23:31:59
+0100

** Changed in: libvdpau (Ubuntu)
   Status: Triaged => Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-5198

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-5199

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2015-5200

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

Title:
  Sync libvdpau 1.1.1-3 (main) from Debian sid (main)

Status in libvdpau package in Ubuntu:
  Fix Released

Bug description:
  Please sync libvdpau 1.1.1-3 (main) from Debian sid (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: privilege escalation when used in setuid or setgid
  applications
  - debian/patches/CVE-2015-5xxx.patch: use secure_getenv and protect
against directory traversal in configure.ac, src/Makefile.am,
src/mesa_dri2.c, src/util.h, src/vdpau_wrapper.c,
trace/vdpau_trace.cpp.
  - CVE-2015-5198
  - CVE-2015-5199
  - CVE-2015-5200
* SECURITY UPDATE: privilege escalation when used in setuid or setgid
  applications
  - debian/patches/CVE-2015-5xxx.patch: use secure_getenv and protect
against directory traversal in configure.ac, src/Makefile.am,
src/mesa_dri2.c, src/util.h, src/vdpau_wrapper.c,
trace/vdpau_trace.cpp.
  - CVE-2015-5198
  - CVE-2015-5199
  - CVE-2015-5200

  Debian package already include everything in the Ubuntu package.

  Changelog entries since current xenial version 1.1-1ubuntu1:

  libvdpau (1.1.1-3) unstable; urgency=medium

[ Luca Boccassi ]
* Cherry-pick patch for DRI_PRIME crash. (Closes: #802625)
* Upload to unstable.

   -- Andreas Beckmann   Thu, 29 Oct 2015 00:47:28
  +0100

  libvdpau (1.1.1-2) experimental; urgency=medium

* Add vdpau-driver-all driver metapackage.  (Closes: #800657)
* libvdpau1: Recommends: vdpau-driver-all | vdpau-driver.
* Upload to experimental.

   -- Andreas Beckmann   Thu, 08 Oct 2015 10:15:00
  +0200

  libvdpau (1.1.1-1) unstable; urgency=medium

[ Andreas Beckmann ]
* simplify d/rules

[ Luca Boccassi ]
* New upstream release.
  - Use secure_getenv(3) to improve security
(CVE-2015-5198, CVE-2015-5199, CVE-2015-5200). Closes: #797895.
* Do not check for pdftex, removed upstream
* Add myself to Uploaders
* Refresh dlopen-path patch, upstream changes
* Refresh patch module-searchpath, upstream changes

   -- Luca Boccassi   Thu, 03 Sep 2015 23:31:59
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1512274/+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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Launchpad Bug Tracker]

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  Triaged
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Michael Zanetti]

** Package changed: unity8 (Ubuntu RTM) => qtbase-opensource-src
(Ubuntu)

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

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  Triaged
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+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 1515749] Re: Merge 3.18.2 from debian

[Martin Pitt]

Jackson, can you please do debian-ubuntu debdiffs instead of, or in
addition to ubuntu-ubuntu ones? we want to review and minimize the delta
to debian. The attached deb.diff can't be applied to anything as it
involves a new upstream version, so it's a lot of manual work to apply
this (way more than just doing the merge by myself).

** Changed in: gnome-desktop3 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Merge 3.18.2 from debian

Status in gnome-desktop3 package in Ubuntu:
  Incomplete

Bug description:
  Merge 3.18.2 from debian
  debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1515749/+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 1515810] Re: Doesn't merge into unity panel when maximized

[Sebastien Bacher]

Indeed, joy of using GNOME client side decorations...

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

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

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

Title:
  Doesn't merge into unity panel when maximized

Status in gedit package in Ubuntu:
  Confirmed

Bug description:
  In a ubuntu session open gedit, maximize.
  I guess because it doesn't use window deco (unity) when maximized you get 2 
sets of action buttons, one from gedit in toolbar, one from light-themes in 
unity panel

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 12 19:04:02 2015
  InstallationDate: Installed on 2015-10-25 (18 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1515810/+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 1515911] Re: unity-control-center is not fully translated

[Olivier Febwin]

** Attachment added: "manque_traduction_unity-control-center.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1515911/+attachment/4518073/+files/manque_traduction_unity-control-center.png

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

Title:
  unity-control-center is not fully translated

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  unity-control-center is not fully translated
  see Personal ; Hardware ; System

  https://dl.dropboxusercontent.com/u/26959244/manque_traduction_unity-
  control-center.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1515911/+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 1515911] [NEW] unity-control-center is not fully translated

[Olivier Febwin]

Public bug reported:

unity-control-center is not fully translated
see Personal ; Hardware ; System

https://dl.dropboxusercontent.com/u/26959244/manque_traduction_unity-
control-center.png

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

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

Title:
  unity-control-center is not fully translated

Status in gnome-menus package in Ubuntu:
  New

Bug description:
  unity-control-center is not fully translated
  see Personal ; Hardware ; System

  https://dl.dropboxusercontent.com/u/26959244/manque_traduction_unity-
  control-center.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1515911/+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 1441095] Re: novatel: improve probing for Dell branded modems

[Shih-Yuan Lee]

@Brian,

I just added the information in [Other Info] for network-manager.
Please help to sponsor the patch for network-manager, thx.

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

Title:
  novatel: improve probing for Dell branded modems

Status in Libmbim:
  Fix Released
Status in ModemManager:
  Fix Released
Status in OEM Priority Project:
  In Progress
Status in OEM Priority Project trusty series:
  In Progress
Status in libmbim package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in libmbim source package in Trusty:
  Fix Committed
Status in modemmanager source package in Trusty:
  Fix Committed
Status in network-manager source package in Trusty:
  In Progress

Bug description:
  [Impact]

   * The users can not use the WWAN of Sierra DW5809e (EM7305) or Sierra
  DW5811e (EM7455) to connect to Internet.

  [Test Case]

   * Insert the WWAN of Sierra DW5809e (EM7305) or Sierra DW5811e
  (EM7455).

   * Insert the SIM, boot the Ubuntu system, and connect to Internet by
  NetworkManager.

  [Regression Potential]

   * No trivial regression so far.

  [Other Info]

   * There is no gateway information in Network Manager. (See the picture in 
comment #74)
* Some ISPs like TW Mobile in Taiwan don't need the gateway to connect to 
Internet.
* Some ISPs like Chunghwa Telecom in Taiwan do need the gateway to connect 
to Internet.
* We need to see the gateway information in Network Manager to cover all 
ISPs.

  Dell rebrands modems from different vendors, including Novatel, Sierra
  and Ericsson. Until now we defaulted to the Novatel plugin when a Dell
  device was found, but then we're breaking newer MBIM Sierra Dell-
  branded modems, as we don't have MBIM support in the Novatel plugin.

  So, we should try to improve the probing in the Novatel, Sierra and
  MBM plugins, so that they probe also Dell devices, and we'll then try
  to match via AT-probing which plugin should be handling the Dell
  device.

  https://bugs.freedesktop.org/show_bug.cgi?id=86713

  Could we backport this patch  into trusty? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmbim/+bug/1441095/+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 1509946] Re: Update to 3.18.0

[Martin Pitt]

Uploaded and source-NEWed, thanks!

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

** Changed in: gdm3 (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Update to 3.18.0

Status in Ubuntu GNOME:
  New
Status in gdm3 package in Ubuntu:
  Fix Committed

Bug description:
  Merge with debian and a rename of source package to gdm3 to cut down
  on the delta with debian. This will make life easier in the future.

  Includes migration code to adapt to the new paths etc.

  Test package at ppa:darkxst/gdm318

  I can't upload this, since its a new source package name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1509946/+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 1512290] Re: gnome-screenshot produces very low quality blurry screenshots

[Iain Lane]

** Changed in: gtk+3.0 (Ubuntu Wily)
   Status: Fix Committed => Triaged

** Changed in: gtk+3.0 (Ubuntu Wily)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Released => Triaged

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Lars Uebernickel (larsu)

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

Title:
  gnome-screenshot produces very low quality blurry screenshots

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 source package in Wily:
  Triaged

Bug description:
  I believe, this is because I am using a HiDPI display. Every time I
  take a screenshot, I get a blurry image. This is not what I want when
  making a screenshot. Everywhere else when I make a screenshot, I get a
  100% copy of my screen, pixel-perfect.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-screenshot 3.16.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Nov  2 13:11:55 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-10-22 (10 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1512290/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Kai-Heng Feng]

There are some scenarios make turning off brightness not desirable, e.g.
an AIO user changes brightness to the lowest level in unity-control-
center, he can't change it back if his keyboard does not have brightness
hotkey.

Since we can't ensure that all graphics driver have the same mechanism
and each one of them does not change, I think it's a better choice to
let userspace program controls a consistent policy.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Carla R.]

Xorg.0.log

[42.249] (II) config/udev: Adding input device Logitech Wireless Mouse M560 
(/dev/input/mouse1)
[42.249] (II) No input driver specified, ignoring this device.
[42.249] (II) This device may have been added with another device file.
[42.278] (II) config/udev: Adding input device Logitech Wireless Mouse M560 
(/dev/input/event14)
[42.278] (**) Logitech Wireless Mouse M560: Applying InputClass "evdev 
pointer catchall"
[42.278] (II) Using input driver 'evdev' for 'Logitech Wireless Mouse M560'
[42.278] (**) Logitech Wireless Mouse M560: always reports core events
[42.278] (**) evdev: Logitech Wireless Mouse M560: Device: 
"/dev/input/event14"
[42.278] (--) evdev: Logitech Wireless Mouse M560: Vendor 0x46d Product 
0x402d
[42.278] (--) evdev: Logitech Wireless Mouse M560: Found 11 mouse buttons
[42.278] (--) evdev: Logitech Wireless Mouse M560: Found scroll wheel(s)
[42.278] (--) evdev: Logitech Wireless Mouse M560: Found relative axes
[42.278] (--) evdev: Logitech Wireless Mouse M560: Found x and y relative 
axes
[42.278] (II) evdev: Logitech Wireless Mouse M560: Configuring as mouse
[42.278] (II) evdev: Logitech Wireless Mouse M560: Adding scrollwheel 
support
[42.278] (**) evdev: Logitech Wireless Mouse M560: YAxisMapping: buttons 4 
and 5
[42.278] (**) evdev: Logitech Wireless Mouse M560: EmulateWheelButton: 4, 
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[42.278] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.2/0003:046D:C52B.0003/0003:046D:402D.0004/input/input17/event14"
[42.278] (II) XINPUT: Adding extended input device "Logitech Wireless Mouse 
M560" (type: MOUSE, id 10)
[42.278] (II) evdev: Logitech Wireless Mouse M560: initialized for relative 
axes.
[42.279] (**) Logitech Wireless Mouse M560: (accel) keeping acceleration 
scheme 1
[42.279] (**) Logitech Wireless Mouse M560: (accel) acceleration profile 0
[42.279] (**) Logitech Wireless Mouse M560: (accel) acceleration factor: 
2.000
[42.279] (**) Logitech Wireless Mouse M560: (accel) acceleration threshold: 
4

** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+attachment/4518322/+files/Xorg.0.log

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+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 1516093] [NEW] Sound doesn't work.

[Radu Stochitoiu]

Public bug reported:

In Sound Settings, there is no Output or Input device.
Sound doesn't work.

Description:Ubuntu 14.04.3 LTS
Release:14.04

Ubuntu Software Center
13.10

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: pulseaudio 1:4.0-0ubuntu11.1
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/by-path', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Fri Nov 13 19:04:07 2015
InstallationDate: Installed on 2015-10-13 (31 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2013
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.50
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: VG10S
dmi.board.vendor: TOSHIBA
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.50:bd11/18/2013:svnTOSHIBA:pnSATELLITEL50-A-1CE:pvrPSKK6E-02K063GR:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: SATELLITE L50-A-1CE
dmi.product.version: PSKK6E-02K063GR
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug trusty

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

Title:
  Sound doesn't work.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  In Sound Settings, there is no Output or Input device.
  Sound doesn't work.

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  Ubuntu Software Center
  13.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pulseaudio 1:4.0-0ubuntu11.1
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D0', 
'/dev/snd/by-path', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Fri Nov 13 19:04:07 2015
  InstallationDate: Installed on 2015-10-13 (31 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.50
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: VG10S
  dmi.board.vendor: TOSHIBA
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.50:bd11/18/2013:svnTOSHIBA:pnSATELLITEL50-A-1CE:pvrPSKK6E-02K063GR:rvnTOSHIBA:rnVG10S:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: SATELLITE L50-A-1CE
  dmi.product.version: PSKK6E-02K063GR
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1516093/+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 1480128] Re: The thumbnails of background images doesn't support HiDPI display.

[Sebastien Bacher]

** Changed in: unity-control-center (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  The thumbnails of background images doesn't support HiDPI display.

Status in unity-control-center package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 14.04.2

  Reproducible Steps:

  1. Login Unity desktop environment.
  2. Change the scale factor to 2 in Displays of System Settings.
  3. Open Appearance in System Settings.

  Expected Result:

  * The thumbnails of background images will be scaled up by 2 times.

  Actual Result:

  * The thumbnails of background images keep small.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1480128/+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 1286878] Re: Doesn't scale well on a hidpi display

[Sebastien Bacher]

** Also affects: unity-greeter (Ubuntu Xenial)
   Importance: Medium
 Assignee: Stephen M. Webb (bregma)
   Status: Triaged

** Also affects: unity-settings-daemon (Ubuntu Xenial)
   Importance: Undecided
   Status: Fix Released

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

Title:
  Doesn't scale well on a hidpi display

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in unity-greeter package in Ubuntu:
  Triaged
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-greeter source package in Xenial:
  Triaged
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  unity-greeter does not scale on hidpi diplays like the rest of unity
  does in trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1286878/+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 1509921] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all

[Raymond]

ports:
analog-input: Analog Input (priority 1, latency offset 0 
usec, available: unknown)
properties:

analog-input-microphone: Microphone (priority 8700, 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: 

it is strange that analog input is the active port when rear mic and
line in are not plugged

control.26 {
iface CARD
name 'Mic Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.27 {
iface CARD
name 'Line Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.28 {
iface CARD
name 'Line Out Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}
control.29 {
iface CARD
name 'Front Headphone Jack'
value false
comment {
access read
type BOOLEAN
count 1
}
}

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

Title:
  [HDA-Intel - HD-Audio Generic, recording] No sound at all

Status in HWE Next:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is a desktop box, with following ports:
  front jack: a single headset combo jack
  rear jacks: mic, speaker, line-in

  An "Analog Input" consistently show up even there is nothing plugged,
  but I'm not able to record via headset jack or rear mic jack, they all 
recorded with noises.

  00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:9840]
  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller [1022:780d] (rev 02)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 11:46:46 2015
  InstallationDate: Installed on 2015-10-23 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd05/21/2015:svnDellInc.:pnInspiron3655:pvr1.0.0:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3655
  dmi.product.version: 1.0.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1509921/+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 1516072] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1

[greg]

Public bug reported:

No problem noticed just a system problem detected notice, failed to
install or remove package.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjpeg-progs 8c-2ubuntu8
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
Date: Fri Nov 13 10:00:17 2015
DuplicateSignature:
 Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
  trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
InstallationDate: Installed on 2015-11-07 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151107)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.0.10.2ubuntu1
SourcePackage: libjpeg8-empty
Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libjpeg8-empty (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package need-duplicate-check package-conflict xenial

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package
  libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  New

Bug description:
  No problem noticed just a system problem detected notice, failed to
  install or remove package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 13 10:00:17 2015
  DuplicateSignature:
   Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151107)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1516072/+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 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Launchpad Bug Tracker]

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

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

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+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 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Carla R.]

kern.log

Nov 13 10:39:59 test-pc kernel: [6.636117] logitech-hidpp-device 
0003:046D:402D.0004: hidraw2: USB HID v1.11 Keyboard [Logitech M560] on 
usb-:00:1d.1-1:1
Nov 13 10:40:20 test-pc kernel: [   38.824043] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:20 test-pc kernel: [   38.832040] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:20 test-pc kernel: [   38.838038] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:20 test-pc kernel: [   38.842038] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.152044] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.154040] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.156040] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.172039] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.180047] logitech-hidpp-device 
0003:046D:402D.0004: HID++ 2.0 device connected.
Nov 13 10:40:24 test-pc kernel: [   42.188041] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.204041] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.220040] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.236041] logitech-hidpp-device 
0003:046D:402D.0004: error in parameter
Nov 13 10:40:24 test-pc kernel: [   42.244140] input: Logitech Wireless Mouse 
M560 as 
/devices/pci:00/:00:1d.1/usb6/6-1/6-1:1.2/0003:046D:C52B.0003/0003:046D:402D.0004/input/input17

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+attachment/4518328/+files/kern.log

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+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 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Carla R.]

test@test-pc:~$ xinput list
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech K400 id=9[slave  pointer  (2)]
⎜   ↳ Logitech Wireless Mouse M560  id=10   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ IR-receiver inside an USB DVB receiverid=8[slave  keyboard (3)]


test@test-pc:~$ xinput --list-props 10
Device 'Logitech Wireless Mouse M560':
Device Enabled (151):   1
Coordinate Transformation Matrix (153): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
Device Accel Profile (283): 0
Device Accel Constant Deceleration (284):   1.00
Device Accel Adaptive Deceleration (285):   1.00
Device Accel Velocity Scaling (286):10.00
Device Product ID (270):1133, 16429
Device Node (271):  "/dev/input/event14"
Evdev Axis Inversion (287): 0, 0
Evdev Axes Swap (289):  0
Axis Labels (290):  "Rel X" (161), "Rel Y" (162), "Rel Horiz Wheel" 
(280), "Rel Vert Wheel" (282)
Button Labels (291):"Button Left" (154), "Button Middle" (155), 
"Button Right" (156), "Button Wheel Up" (157), "Button Wheel Down" (158), 
"Button Horiz Wheel Left" (159), "Button Horiz Wheel Right" (160), "Button 
Unknown" (273), "Button Unknown" (273), "Button Forward" (277), "Button Back" 
(278), "Button Unknown" (273), "Button Unknown" (273), "Button Unknown" (273), 
"Button Unknown" (273)
Evdev Scrolling Distance (292): 1, 1, 1
Evdev Middle Button Emulation (293):0
Evdev Middle Button Timeout (294):  50
Evdev Third Button Emulation (295): 0
Evdev Third Button Emulation Timeout (296): 1000
Evdev Third Button Emulation Button (297):  3
Evdev Third Button Emulation Threshold (298):   20
Evdev Wheel Emulation (299):0
Evdev Wheel Emulation Axes (300):   0, 0, 4, 5
Evdev Wheel Emulation Inertia (301):10
Evdev Wheel Emulation Timeout (302):200
Evdev Wheel Emulation Button (303): 4
Evdev Drag Lock Buttons (304):  0

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+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 1516062] Re: Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Carla R.]

I've posted the output from xev:

#Tilt left:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4068416, (33,23), root:(2104,410),
state 0x0, button 6, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4068416, (33,23), root:(2104,410),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 0


#Tilt right:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4084046, (20,18), root:(2091,405),
state 0x0, button 7, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4084046, (20,18), root:(2091,405),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 0


#Middle:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4137233, (56,49), root:(2127,436),
state 0x0, button 2, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4137233, (56,49), root:(2127,436),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 512


#Back:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4173824, (44,49), root:(2115,436),
state 0x0, button 11, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4173824, (44,49), root:(2115,436),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 0


#Forward:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4192478, (38,46), root:(2109,433),
state 0x0, button 10, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4192478, (38,46), root:(2109,433),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 0


#Button Left:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4212584, (38,45), root:(2109,432),
state 0x0, button 1, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4212585, (38,45), root:(2109,432),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 256


#Button Right:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4228085, (41,53), root:(2112,440),
state 0x0, button 3, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4228085, (41,53), root:(2112,440),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 1024


#Button Wheel Up:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4244461, (29,53), root:(2100,440),
state 0x0, button 4, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4244462, (29,53), root:(2100,440),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 2048


#Button Wheel Down:
ButtonPress event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x162, time 4267902, (31,49), root:(2102,436),
state 0x0, button 5, same_screen YES

EnterNotify event, serial 37, synthetic NO, window 0x161,
root 0x298, subw 0x0, time 4267902, (31,49), root:(2102,436),
mode NotifyGrab, detail NotifyInferior, same_screen YES,
focus YES, state 4096

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Martin Pitt]

So if you run into that situation, discovering that this is configurable
and changing the configuration seems equally hard (or harder). I can
understand the heuristics what was done upstream in gnome-settings-
daemon (see linked bug) to generally clam the brightness to >= 1 if
there are many steps. That will work without configuration, does not
need to be discovered, and keeps the path open for a better fix in the
future as this doesn't set/affect any user config or other permanent
state on disk. We could use that approach in unity-settings-daemon too?

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1510824]

[Dariusz Gadomski]

Miroslav, thanks for taking a look.

Sure, I can improve the patch. I'll attach the new version as soon as
it's done.

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Confirmed
Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1510824]

[Dariusz Gadomski]

Created attachment 119643
Refactoring to use send_to_helper

I have refactored the code to make use of send_to_helper instead of
duplicating the code.

I've chosen to apply it on top of the previous change to keep 2
different actions (escaping PAM_TEXT_INFO and refactoring) on the same
step.

I have done sanity testing to make sure everything works as expected.

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Confirmed
Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1510824]

[Dariusz Gadomski]

Typo, what I've meant in the above comment is that I wanted to avoid
doing 2 different actions in the same commit.

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Confirmed
Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1292282] Re: background transparency is not working on gnome terminal

[m...@papersolve.com]

bug still occurs on gnome 3.16 w/ gnome-terminal 3.16
transparency can be enabled by editing the profile preferences and changing the 
slider a bit
my preferred fix is ... use Konsole :)

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

Title:
  background  transparency is not working on gnome terminal

Status in GNOME Terminal:
  Invalid
Status in One Hundred Papercuts:
  Fix Released
Status in gnome-terminal package in Ubuntu:
  Fix Released

Bug description:
  The "transparent background" option of the gnome terminal is not
  working properly, the screen background turns black instead of
  transparent when a solid color is used as backgoround and if an image
  is being used it will only be visible when the bar is set to none,
  otherwise it will return to the last solid color selected. I'll attach
  scrrens on both cases.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-terminal 3.6.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
  Uname: Linux 3.13.0-17-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 13 14:14:17 2014
  InstallationDate: Installed on 2014-03-04 (9 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140301)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1292282/+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 1381625] Re: Adjust brightness to lowest value caused screen whole black

[Kai-Heng Feng]

Yes, we can use that approach on unity-settings-daemon, with some minor
modification to make xbacklight works.

My intention to make it configurable is because there was a Braswell
laptop with a cheap panel, which needs at least 5% max brightness to
make it barely visible. For OEM projects, to solve problems like that, a
minimum brightness setting can be a generic and convenient way to make
preloaded Ubuntu more polished.

That being said, most panel works just fine with brightness value 1 in
my experience.

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

Title:
  Adjust brightness to lowest value caused screen whole black

Status in HWE Next:
  Confirmed
Status in Unity Settings Daemon:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Won't Fix

Bug description:
  [Impact]

  When adjusting screen brightness to lowest value, it turns screen
  backlight off.

  [Test Case]

  1. Install Image
  2. Press System's brightness hotkey to adjust the brightness level to the 
lowest or
  3. Go to System "Settings" -> "Brightness & Lock" to adjust brightness level 
to the lowest
  4. Check if the screen display still has backlight

  Expected results: There is still screen backlight

  Actual results: Sceen backlight is turned off

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1381625/+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 1516078] [NEW] pulseaudio fails to load modules

[Mathieu Trudel-Lapierre]

Public bug reported:

Pulseaudio 1:7.1-1ubuntu1 in xenial is unable to load some of its
modules, more importantly at least the bluez module and the cli module:

Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: 
Impossible d'ouvrir le module module-bluez5-device.so : 
module-bluez5-device.so: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type
Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to open 
module "module-bluez5-device".
Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] 
module-bluez5-discover.c: Failed to load module for device 
/org/bluez/hci0/dev_30_22_04_06_16_46
Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: 
Impossible d'ouvrir le module module-cli-protocol-unix.so : 
module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type
Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to open 
module "module-cli-protocol-unix".
Nov 13 10:16:11 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: 
Impossible d'ouvrir le module module-cli-protocol-unix.so : 
module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type

Using the version of pulseaudio from wily; things appear to work as
expected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:6.0-0ubuntu13
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.2-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  mtrudel   12148 F pulseaudio
 /dev/snd/pcmC0D0p:   mtrudel   12148 F...m pulseaudio
 /dev/snd/controlC0:  mtrudel   12148 F pulseaudio
 /dev/snd/controlC1:  mtrudel   12148 F pulseaudio
CurrentDesktop: Unity
Date: Fri Nov 13 11:17:34 2015
InstallationDate: Installed on 2015-03-30 (228 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-M 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.:bvr0603:bd11/03/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z68-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug xenial

** Description changed:

- Pulseaudio 7.1 in xenial is unable to load some of its modules, more
- importantly at least the bluez module and the cli module:
+ Pulseaudio 1:7.1-1ubuntu1 in xenial is unable to load some of its
+ modules, more importantly at least the bluez module and the cli module:
  
  Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: 
Impossible d'ouvrir le module module-bluez5-device.so : 
module-bluez5-device.so: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type
  Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to 
open module "module-bluez5-device".
  Nov 13 10:14:15 demeter pulseaudio[3467]: [pulseaudio] 
module-bluez5-discover.c: Failed to load module for device 
/org/bluez/hci0/dev_30_22_04_06_16_46
  Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: 
Impossible d'ouvrir le module module-cli-protocol-unix.so : 
module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type
  Nov 13 10:16:10 demeter pulseaudio[3467]: [pulseaudio] module.c: Failed to 
open module "module-cli-protocol-unix".
  Nov 13 10:16:11 demeter pulseaudio[3467]: [pulseaudio] ltdl-bind-now.c: 
Impossible d'ouvrir le module module-cli-protocol-unix.so : 
module-cli-protocol-unix.so: Ne peut ouvrir le fichier d'objet partagé: Aucun 
fichier ou dossier de ce type
  
  Using the version of pulseaudio from wily; things appear to work as
  expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.2-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  mtrudel   12148 F pulseaudio
-  /dev/snd/pcmC0D0p:   mtrudel   12148 F...m pulseaudio
-  /dev/snd/controlC0:  mtrudel   12148 F pulseaudio
-  /dev/snd/controlC1:  mtrudel   12148 F pulseaudio
+  USERPID ACCESS COMMAND
+  

[Desktop-packages] [Bug 976114] Re: Changing resolution in Displays settings completly messes up desktop

[gaurav singh]

** Changed in: fglrx-installer (Ubuntu)
 Assignee: (unassigned) => gaurav singh (gauravkumarsingh322)

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

Title:
  Changing resolution in Displays settings completly messes up desktop

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  I have a monitor and a projector connected to my system. I'm testing
  12.04 64-bit with all current updates and I'm using AMD catalyst
  drivers. Monitor is 1900x1200, and max resolution for projector is
  1400x1050. if I try to change the resolution from Displays settings to
  1400x1050, to be able to use Mirror mode, complete desktop gets messed
  up (see screenshot), and only logout/login could help. Windows loose
  theri borders and titlebars and their content isn't rendered as it
  should anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/976114/+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 1509921] Re: [HDA-Intel - HD-Audio Generic, recording] No sound at all

[Raymond]

080122] SKU: Nid=0x1d sku_cfg=0x4054c601
[   10.080128] SKU: port_connectivity=0x1
[   10.080130] SKU: enable_pcbeep=0x1
[   10.080132] SKU: check_sum=0x0004
[   10.080133] SKU: customization=0x00c6
[   10.080134] SKU: external_amp=0x0
[   10.080136] SKU: platform_type=0x0
[   10.080137] SKU: swap=0x0
[   10.080138] SKU: override=0x1
[   10.080329] autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:line
[   10.080331]speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[   10.080333]hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
[   10.080335]mono: mono_out=0x0
[   10.080336]inputs:
[   10.080338]  Mic=0x18
[   10.080339]  Line=0x1a
[   10.080341] realtek: No valid SSID, checking pincfg 0x4054c601 for NID 0x1d
[   10.080343] realtek: Enabling init ASM_ID=0xc601 CODEC_ID=10ec0662
[   10.090186] input: HD-Audio Generic Front Headphone as 
/devices/pci:00/:00:14.2/sound/card1/input13
[   10.090327] input: HD-Audio Generic Line Out as 
/devices/pci:00/:00:14.2/sound/card1/input12
[   10.090441] input: HD-Audio Generic Line as 
/devices/pci:00/:00:14.2/sound/card1/input11
[   10.090528] input: HD-Audio Generic Mic as 
/devices/pci:00/:00:14.2/sound/card1/input10


do rear mic and line in works ?


the headset mic should be one of the remaining unconnected pin complex

try hdajackretask to change one of the remaining node to mic (e.g. node
0x19,...

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

Title:
  [HDA-Intel - HD-Audio Generic, recording] No sound at all

Status in HWE Next:
  New
Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is a desktop box, with following ports:
  front jack: a single headset combo jack
  rear jacks: mic, speaker, line-in

  An "Analog Input" consistently show up even there is nothing plugged,
  but I'm not able to record via headset jack or rear mic jack, they all 
recorded with noises.

  00:01.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device 
[1002:9840]
  00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia 
Controller [1022:780d] (rev 02)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 11:46:46 2015
  InstallationDate: Installed on 2015-10-23 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic_1 failed
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1824 F pulseaudio
   /dev/snd/controlC0:  u  1824 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd05/21/2015:svnDellInc.:pnInspiron3655:pvr1.0.0:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3655
  dmi.product.version: 1.0.0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1509921/+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 1308105] Re: Xfce resets TV mode to NULL when power cycled

[Ivan Kozik]

I have a Viewsonic VX2475Smhl-4K attached with a DisplayPort cable to a
Gigabyte GTX 970 (nvidia-358 driver, ASUS Z97-A, UEFI boot with CSM
disabled), and it requires `xrandr --auto` after being power cycled.
That's easy to set to a keyboard shortcut when logged in, but harder in
xflock4.  Even less amusing, Linux text VTs don't work until an `xrandr
--auto` in an X session.

There were reports that non-VESA-compliant DisplayPort cables that wire
pin 20 (DP_PWR) cause this problem, but I checked my Cable Matters cable
with a multimeter and it does not wire pin 20.

Microsoft has a page about this problem: https://support.microsoft.com
/en-us/kb/2625567

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

Title:
  Xfce resets TV mode to NULL when power cycled

Status in Mythbuntu:
  Confirmed
Status in xfce4-settings:
  Confirmed
Status in nvidia-graphics-drivers package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-331 package in Ubuntu:
  Invalid
Status in xfce4-settings package in Ubuntu:
  Confirmed

Bug description:
  I had an HTPC with Mythbuntu 12.04 installed.  Upon upgrading a new
  behavior that if the TV is power cycled it no longer detects a link
  with the HTPC.

  When this happens I can find in the xorg log that there is an
  accompanying log item:

  [ 39829.509] (II) NVIDIA(0): Setting mode "NULL"

  After debugging with NVIDIA at
  https://devtalk.nvidia.com/default/topic/729955/linux/tv-stops-being-
  detected/ we've deteremined it's a X client that reacts to the RANDR
  events causing the mode to be set to NULL.

  Working through the list in an Xfce environment, the culprit is
  xfsettingsd.  If xfsettingsd is running, it causes the TV to come up
  in a NULL mode.  If it's killed, it remains in the mode it was
  previously running in.

  
  Until this is fixed, this behavior can be worked around with a simple shell 
script:
  ==
  #!/bin/sh
  #Fix TV state when HDMI link is lost.
  #By Mario Limonciello 

  OUTPUT="HDMI-0"
  BAD_MODE="1280x720"
  GOOD_MODE="1920x1080"

  for MODE in $BAD_MODE $GOOD_MODE; do
   DISPLAY=:0 xrandr --output $OUTPUT --mode $MODE
   sleep 2
  done
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1516062] [NEW] Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

[Carla R.]

Public bug reported:

Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left and
Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock kernel
4.2.x.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Nov 13 15:32:28 2015
InstallationDate: Installed on 2015-11-12 (0 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Logitech Wireless Mouse M560 buttons Back, Forward, Horiz Wheel Left
  and Horiz Wheel Right don't work on Ubuntu/Xubuntu 15.10 with stock
  kernel 4.2.x.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Nov 13 15:32:28 2015
  InstallationDate: Installed on 2015-11-12 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516062/+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 1515461] Re: Open menu dropdown is 'compressed' & unintelligible

[Launchpad Bug Tracker]

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

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

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

Title:
  Open menu dropdown is 'compressed' & unintelligible

Status in gedit package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  Did not happen with initial upgrade to gedit-3.18 but showed up with some 
subsequent updates of other packages.
  (may be able to track down by manually parsing synaptic's history logs
  Please see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gedit 3.18.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Nov 11 21:05:08 2015
  InstallationDate: Installed on 2015-10-25 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Jvanek]

ITW provides little fall back in form of "javaws -html some.html.page.url" 
But yes, it have to much cases when it is useless.

Long story short, there is no plan for PPAPI.

If you wont one. Please contribute!

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

Title:
  Chromium doesn't use Icedtea Java NPAPI plugin

Status in Iced Tea:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in icedtea-web package in Ubuntu:
  Won't Fix

Bug description:
  I've installed openjdk-7-jre and icedtea-7-plugin, but chromium can't launch 
java applets. Java doesn't show in about:plugins.
  How to reproduce:
  1) Install openjdk-7-jre and icedtea-7-plugin
  2) Open chromium
  3) Go to about:plugins and look for java or icedtea, or try to run an applet
  What happens: the plugin is not listed, applets won't run
  What is expected: the plugin is listed and applets work

  Note: Firefox detects the plugin and applets work in Firefox, which
  means the plugin is properly installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 14:42:43 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda5  
ext4   47G  7,3G   38G  17% /\nnone   tmpfs 4,0K 0  4,0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1,9G  4,0K  1,9G   1% /dev\ntmpfs   
   tmpfs 381M  1,2M  380M   1% /run\nnone   tmpfs 5,0M 
0  5,0M   0% /run/lock\nnone   tmpfs 1,9G  7,9M  1,9G   1% 
/run/shm\nnone   tmpfs 100M  100K  100M   1% /run/user\n/dev/sda6   
   ext4  160G  110G   43G  73% /home\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda53,0M  
285K  2,8M   10% /\nnone 476K 2  476K1% 
/sys/fs/cgroup\nudev 474K   524  473K1% /dev\ntmpfs
476K   534  476K1% /run\nnone 476K 3  476K1% 
/run/lock\nnone 476K13  476K1% /run/shm\nnone 
476K46  476K1% /run/user\n/dev/sda6 11M  517K  9,7M5% 
/home\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140215)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-18T13:16:04.211524

To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/1309508/+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 1325940] CurrentDmesg.txt

[Jan Rathmann]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518414/+files/CurrentDmesg.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0

[Desktop-packages] [Bug 1325940] ProcInterrupts.txt

[Jan Rathmann]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518423/+files/ProcInterrupts.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 

[Desktop-packages] [Bug 1325940] Lspci.txt

[Jan Rathmann]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1325940/+attachment/4518419/+files/Lspci.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] XorgLogOld.txt

[Jan Rathmann]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518428/+files/XorgLogOld.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] UdevLog.txt

[Jan Rathmann]

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518426/+files/UdevLog.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] ProcModules.txt

[Jan Rathmann]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518424/+files/ProcModules.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Anoop Karollil]

Dejavu - I have done this before - disabling sna. I will give it a go,
thanks. I had two crashes yesterday.

Linux akarollil-desktop 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8
15:35:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] clocksource: Switched to clocksource tsc
  [2.652818] systemd[1]: Failed to insert module 'kdbus': Function not 
implemented
  [2.658814] systemd[1]: systemd 225 running in system mode. (+PAM +AUDIT 
+SELINUX +IMA +APPARMOR +SMACK 

[Desktop-packages] [Bug 1516072] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3

[Launchpad Bug Tracker]

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

** Changed in: libjpeg8-empty (Ubuntu)
   Status: New => Confirmed

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package
  libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  No problem noticed just a system problem detected notice, failed to
  install or remove package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 13 10:00:17 2015
  DuplicateSignature:
   Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151107)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1516072/+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 1510824] Re: PolkitAgentSession incorrectly handles multiline output (as observed with pam_vas)

[Bug Watch Updater]

** Changed in: policykit-1
   Status: Incomplete => Confirmed

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

Title:
  PolkitAgentSession incorrectly handles multiline output (as observed
  with pam_vas)

Status in PolicyKit:
  Confirmed
Status in policykit-1 package in Ubuntu:
  New
Status in policykit-1 source package in Trusty:
  New
Status in policykit-1 source package in Vivid:
  New
Status in policykit-1 source package in Wily:
  New

Bug description:
  There is an error observed when Ubuntu is configured to perform
  authentication via pam_vas (Vintela Authentication Services by Dell)
  in a disconnected mode (using cached authentication).

  Steps to reproduce:
  1. Configure pam_vas client authenticating to a remote server.
  2. Perform authentication to cache the credentials.
  3. Disconnect from the network where the server is reachable (to force using 
cached information).
  4. Perform an action requiring polkit authentication.

  Expected result:
  Authentication succeeds accompanied by the following message "You have logged 
in using cached account information.  Some network services will be 
unavailable".

  Actual result:
  Authentication fails accompanied by the following message "You have logged in 
using cached account information.  Some network services will be unavailable".

  Probable cause:
  The PolkitAgentSession part of polkit is designed to interpret only 1-line 
output, while interaction with pam_vas in the above scenario triggers helper to 
produce the following 2-line output:
  PAM_TEXT_INFO You have logged in using cached account information.  Some 
network services
  will be unavailable.

  The 'will be unavailable.' part is interpreted as an unknown message
  and causes failed authorization.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: policykit-1 0.105-4ubuntu2.14.04.1
  ProcVersionSignature: Ubuntu 3.16.0-52.71~14.04.1-generic 3.16.7-ckt18
  Uname: Linux 3.16.0-52-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 28 09:01:37 2015
  InstallationDate: Installed on 2015-04-13 (197 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: policykit-1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1510824/+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 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android

[Kevin DuBois]

my spike branch that averts the problem is here, based on 0.17.1:
lp:~kdub/mir/0.17.1-fix-1406725 
This branch doesnt have unit tests, and needs a bit more work on the new 
internal interfaces, so I'll probably have to rework the branch to get it to 
land in lp:mir.

** Branch linked: lp:~kdub/mir/0.17.1-fix-1406725

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

Title:
  Severe graphical corruption (mostly horizontal streaks/lines) running
  software clients (including Xmir) on android

Status in canonical-pocket-desktop:
  In Progress
Status in Mir:
  In Progress
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  I'm seeing severe graphical corruption running mir_demo_client_flicker
  on mako.

  Start a few instances of the client (or just one flicker and some
  other clients) and you'll see the mir_demo_client_flicker window
  contains significant corruption.

  I don't think it's an overlays issue. The problem occurs even without
  overlays.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+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 1510970] Re: Intel driver crashes on Ubuntu 15.10

[Anoop Karollil]

Seems to be working, for people running Ubuntu 15.10, the location of
the file (20-intel.conf) with the contents that Georgi mentions above is
/usr/share/X11/xorg.conf.d (rather than /etc/X11).

You can check if SNA is enabled by:

cat /var/log/Xorg.0.log | grep SNA

If you see it in the log, reboot after creating 20-intel.conf file as
described above and you shouldn't. And hopefully the crashes will go
away. Initial testing seems to indicate it fixes it for me.

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

Title:
  Intel driver crashes on Ubuntu 15.10

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  The Xserver crashes randomly after upgrading to Ubuntu 15.10. Before
  the update everything was stable.

  The problem occured mostly while using Thunderbird but also once while
  using Firefox.

  The Xserver crashes and I'm logged out. It takes about 10 seconds
  until gdm fires up again and I'm able to login again.

  The last part of /var/log/Xorg.0.log says:
  [ 19778.602] (II) intel(0): resizing framebuffer to 3000x1920
  [ 19778.617] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI2 using pipe 
1, position (0, 0), rotation left, reflection none
  [ 19778.623] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 406), rotation normal, reflection none
  [ 19798.610] (II) intel(0): switch to mode 1920x1080@60.0 on HDMI1 using pipe 
0, position (1080, 502), rotation normal, reflection none
  [ 20012.432] (EE) 
  [ 20012.432] (EE) Backtrace:
  [ 20012.433] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55cab7c8f62e]
  [ 20012.433] (EE) 1: /usr/bin/X (0x55cab7adb000+0x1b8999) [0x55cab7c93999]
  [ 20012.433] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fe7c651d000+0x352f0) 
[0x7fe7c65522f0]
  [ 20012.433] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x24f18) [0x7fe7c2918f18]
  [ 20012.433] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x26157) [0x7fe7c291a157]
  [ 20012.433] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x2b4b1) [0x7fe7c291f4b1]
  [ 20012.433] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x804e4) [0x7fe7c29744e4]
  [ 20012.433] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x80e2c) [0x7fe7c2974e2c]
  [ 20012.433] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x82e1a) [0x7fe7c2976e1a]
  [ 20012.433] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x4197c) [0x7fe7c293597c]
  [ 20012.433] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fe7c28f4000+0x59906) [0x7fe7c294d906]
  [ 20012.433] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55cab7b38654]
  [ 20012.433] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55cab7c93274]
  [ 20012.433] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55cab7b3e502]
  [ 20012.433] (EE) 14: /usr/bin/X (0x55cab7adb000+0xf495a) [0x55cab7bcf95a]
  [ 20012.433] (EE) 15: /usr/bin/X (0x55cab7adb000+0xf5ef5) [0x55cab7bd0ef5]
  [ 20012.433] (EE) 16: /usr/bin/X (0x55cab7adb000+0x5818f) [0x55cab7b3318f]
  [ 20012.433] (EE) 17: /usr/bin/X (0x55cab7adb000+0x5c34b) [0x55cab7b3734b]
  [ 20012.433] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fe7c653da40]
  [ 20012.433] (EE) 19: /usr/bin/X (_start+0x29) [0x55cab7b216c9]
  [ 20012.433] (EE) 
  [ 20012.433] (EE) Segmentation fault at address 0x0
  [ 20012.433] (EE) 
  Fatal server error:
  [ 20012.433] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 20012.433] (EE) 
  [ 20012.433] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 20012.433] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [ 20012.433] (EE) 
  [ 20012.433] (II) AIGLX: Suspending AIGLX clients for VT switch
  [ 20012.456] (EE) Server terminated with error (1). Closing log file.

  These parts of dmesg might be interesting:
  [1.661760] input: Logitech USB Keyboard as 
/devices/pci:00/:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:046D:C31C.0003/input/input8
  [1.714657] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 
Device [Logitech USB Keyboard] on usb-:00:1a.0-1.6/input1
  [2.530993] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.531006] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun
  [2.531018] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder B
  [2.531026] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder B FIFO underrun
  [2.561370] EXT4-fs (sda6): mounted filesystem with ordered data mode. 
Opts: (null)
  [2.586624] 

[Desktop-packages] [Bug 1516072] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3

[Tony C.]

dpkg: warning: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/exifautotran.1.gz', 
which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/jpegtran.1.gz', which 
is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/cjpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/jpegexiforient.1.gz', 
which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/rdjpgcom.1.gz', which 
is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/share/man/man1/wrjpgcom.1.gz', which 
is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/bin/rdjpgcom', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/bin/wrjpgcom', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/bin/djpeg', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/bin/exifautotran', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/bin/cjpeg', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
dpkg: warning: trying to overwrite '/usr/bin/jpegtran', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2 
dpkg: warning: trying to overwrite '/usr/bin/jpegexiforient', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2

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

Title:
  package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to
  overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package
  libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg8-empty package in Ubuntu:
  Confirmed

Bug description:
  No problem noticed just a system problem detected notice, failed to
  install or remove package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 8c-2ubuntu8
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 13 10:00:17 2015
  DuplicateSignature:
   Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151107)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg8-empty
  Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to 
overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1516072/+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 1325940] Re: Desktop sometimes comes up with undisplayable screen resolution

[Jan Rathmann]

apport information

** Tags added: apport-collected ubuntu

** Description changed:

  Hello,
  
  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to matter).
  In the failure case the following happens:
  
  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it looks
  a bit like a CRT Television with low signal.
  
  - When the desktop is loaded (via autologin), one can see short glimpses
  of its wallpaper, but after a few second the screen becomes black and
  remains that way. The monitor _does_ seem to receive a signal though.
  
  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.
  
  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or 1683x1050,
  which is 1-3 pixel bigger than the native horizontal resolution of the
  22" LCD screen.
  
  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.
  
  This does not happen on every boot, only in ~10-15% of the cases. I was
  not able to find any pattern so far in the occurence of this bug. The
  only thing I observed is that it _never_ happens when Windows XP is
  started, thus my assumption is that the bug is related to the xserver-
  xorg-video-radeon driver.
  
  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.
  
  The monitor is connected via DVI.
  
  Below is a video attached that tries to show how the TTYs look when this
  bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.
  
  Kind regards,
  Jan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.14.1-0ubuntu3.18
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: trusty
+ DistroRelease: Ubuntu 14.04
+ DistroVariant: ubuntu
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
+Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
+Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
+ InstallationDate: Installed on 2014-04-22 (570 days ago)
+ InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
+ LightdmGreeterLog:
+  ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
+  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
+ LightdmGreeterLogOld:
+  ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
+  g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
+ MachineType: MSI MS-6741
+ Package: xorg 1:7.7+1ubuntu8.1
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
+ Tags:  trusty ubuntu
+ Uname: Linux 3.13.0-63-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/02/01
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: Version 07.00T
+ dmi.board.name: MS-6741
+ dmi.board.vendor: MSI
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: 0123ABC
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Uknown Chassis Manufacture
+ dmi.chassis.version: Version 1.00
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6741:pvr1.0:rvnMSI:rnMS-6741:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00:
+ dmi.product.name: MS-6741
+ 

[Desktop-packages] [Bug 1325940] BootLog.txt

[Jan Rathmann]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518413/+files/BootLog.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] ProcCpuinfo.txt

[Jan Rathmann]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518421/+files/ProcCpuinfo.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] LightdmDisplayLog.txt

[Jan Rathmann]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518417/+files/LightdmDisplayLog.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  

[Desktop-packages] [Bug 1325940] Lsusb.txt

[Jan Rathmann]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1325940/+attachment/4518420/+files/Lsusb.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] xserver.outputs.txt

[Jan Rathmann]

apport information

** Attachment added: "xserver.outputs.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518431/+files/xserver.outputs.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  

[Desktop-packages] [Bug 1325940] Xrandr.txt

[Jan Rathmann]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1325940/+attachment/4518429/+files/Xrandr.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] DpkgLog.txt

[Jan Rathmann]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518416/+files/DpkgLog.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1482411] Re: Pulseaudio set Kodi sount to 1% each time I change video

[Launchpad Bug Tracker]

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

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

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

Title:
  Pulseaudio set Kodi sount to 1% each time I change video

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in kodi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is the bug :

  Each time Kodi change the video playing (like coming to next TV show
  episode), Pulseaudio set Kodi sound level to 1% and I need to go back
  to pavucontrol to upgrade to 100% each time !

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kevin 10243 F pulseaudio
   /dev/snd/controlC1:  kevin 10243 F pulseaudio
   /dev/snd/pcmC0D1p:   kevin 10243 F...m pulseaudio
   /dev/snd/controlC0:  kevin 10243 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  7 00:34:05 2015
  InstallationDate: Installed on 2015-07-14 (23 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interne - HDA ATI SB
  Symptom_Jack: Grey SPDIF Out, Rear Panel
  Symptom_Type: Sound works for a while, then breaks
  Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77TD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1482411/+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 1325940] LightdmLog.txt

[Jan Rathmann]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518418/+files/LightdmLog.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] XorgLog.txt

[Jan Rathmann]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518427/+files/XorgLog.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] xdpyinfo.txt

[Jan Rathmann]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518430/+files/xdpyinfo.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1516126] [NEW] apport-retrace fails unless apport is also installed (/etc/apport/crashdb.conf)

[Steve Langasek]

Public bug reported:

Attempting to run apport-retrace in a chroot, it fails with the
following traceback:

Traceback (most recent call last):
  File "/usr/bin/apport-retrace", line 217, in 
crashdb = get_crashdb(options.auth)
  File "/usr/lib/python2.7/dist-packages/apport/crashdb.py", line 822, in 
get_crashdb
with open(conf) as f:
IOError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf'

/etc/apport/crashdb.conf is part of the apport package; and apport-
retrace does not depend on apport.

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

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

Title:
  apport-retrace fails unless apport is also installed
  (/etc/apport/crashdb.conf)

Status in apport package in Ubuntu:
  New

Bug description:
  Attempting to run apport-retrace in a chroot, it fails with the
  following traceback:

  Traceback (most recent call last):
File "/usr/bin/apport-retrace", line 217, in 
  crashdb = get_crashdb(options.auth)
File "/usr/lib/python2.7/dist-packages/apport/crashdb.py", line 822, in 
get_crashdb
  with open(conf) as f:
  IOError: [Errno 2] No such file or directory: '/etc/apport/crashdb.conf'

  /etc/apport/crashdb.conf is part of the apport package; and apport-
  retrace does not depend on apport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1516126/+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 1325940] ProcEnviron.txt

[Jan Rathmann]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518422/+files/ProcEnviron.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1325940] Dependencies.txt

[Jan Rathmann]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1325940/+attachment/4518415/+files/Dependencies.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0

[Desktop-packages] [Bug 1325940] UdevDb.txt

[Jan Rathmann]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1325940/+attachment/4518425/+files/UdevDb.txt

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

Title:
  Desktop sometimes comes up with undisplayable screen resolution

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  the PC from which I'm sending this report sometimes fails to boot into
  the desktop properly (which desktop environment doesn't seem to
  matter). In the failure case the following happens:

  - The Plymouth Ubuntu splash gets displayed, but it looks distorted.
  Flickering horizontal artifacts are shown all over the screen, it
  looks a bit like a CRT Television with low signal.

  - When the desktop is loaded (via autologin), one can see short
  glimpses of its wallpaper, but after a few second the screen becomes
  black and remains that way. The monitor _does_ seem to receive a
  signal though.

  - It is possible to switch to TTYs and to use them, but they show
  similar artifacts like the Plymouth logo.

  - If I query the display information on the monitor's OSD when the
  screen is distorted, it reports a resolution of 1681x1050 or
  1683x1050, which is 1-3 pixel bigger than the native horizontal
  resolution of the 22" LCD screen.

  Switching between different resolutions via entering 'xrandr --size
  1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the
  native resolution properly.

  This does not happen on every boot, only in ~10-15% of the cases. I
  was not able to find any pattern so far in the occurence of this bug.
  The only thing I observed is that it _never_ happens when Windows XP
  is started, thus my assumption is that the bug is related to the
  xserver-xorg-video-radeon driver.

  I tried to specify the correct resolution explicitly on the kernel
  command line(adding video=DVI-I-1:1680x1050 ) but this has no positive
  effect.

  The monitor is connected via DVI.

  Below is a video attached that tries to show how the TTYs look when
  this bug occurs. Notice the abnormal blue lines, which are constantly
  flickering.

  Kind regards,
  Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
  Uname: Linux 3.13.0-27-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jun  3 13:23:38 2014
  InstallationDate: Installed on 2014-04-22 (41 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: xserver-xorg-video-ati
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroRelease: Ubuntu 14.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a]
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b]
  InstallationDate: Installed on 2014-04-22 (570 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld:
   ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei 
»/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht 
gefunden
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  MachineType: MSI MS-6741
  Package: xorg 1:7.7+1ubuntu8.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Tags:  trusty ubuntu
  Uname: Linux 3.13.0-63-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 04/02/01
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Version 07.00T
  dmi.board.name: MS-6741
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  

[Desktop-packages] [Bug 1482411] Re: Pulseaudio set Kodi sount to 1% each time I change video

[Danial Behzadi]

It starts with no audio every time.

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

Title:
  Pulseaudio set Kodi sount to 1% each time I change video

Status in alsa-driver package in Ubuntu:
  Incomplete
Status in kodi package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is the bug :

  Each time Kodi change the video playing (like coming to next TV show
  episode), Pulseaudio set Kodi sound level to 1% and I need to go back
  to pavucontrol to upgrade to 100% each time !

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kevin 10243 F pulseaudio
   /dev/snd/controlC1:  kevin 10243 F pulseaudio
   /dev/snd/pcmC0D1p:   kevin 10243 F...m pulseaudio
   /dev/snd/controlC0:  kevin 10243 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Aug  7 00:34:05 2015
  InstallationDate: Installed on 2015-07-14 (23 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Audio interne - HDA ATI SB
  Symptom_Jack: Grey SPDIF Out, Rear Panel
  Symptom_Type: Sound works for a while, then breaks
  Title: [System Product Name, VIA VT1708S, Grey SPDIF Out, Rear Panel] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0702
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77TD PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0702:bd08/13/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77TDPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1482411/+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 1309508]

[Alberto Salvia Novella]

Plug-ings will be dropped from both Chromium and Firefox, so fixing this
bug won't have any impact in medium term.

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

Title:
  Chromium doesn't use Icedtea Java NPAPI plugin

Status in Iced Tea:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in icedtea-web package in Ubuntu:
  Won't Fix

Bug description:
  I've installed openjdk-7-jre and icedtea-7-plugin, but chromium can't launch 
java applets. Java doesn't show in about:plugins.
  How to reproduce:
  1) Install openjdk-7-jre and icedtea-7-plugin
  2) Open chromium
  3) Go to about:plugins and look for java or icedtea, or try to run an applet
  What happens: the plugin is not listed, applets won't run
  What is expected: the plugin is listed and applets work

  Note: Firefox detects the plugin and applets work in Firefox, which
  means the plugin is properly installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 14:42:43 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda5  
ext4   47G  7,3G   38G  17% /\nnone   tmpfs 4,0K 0  4,0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1,9G  4,0K  1,9G   1% /dev\ntmpfs   
   tmpfs 381M  1,2M  380M   1% /run\nnone   tmpfs 5,0M 
0  5,0M   0% /run/lock\nnone   tmpfs 1,9G  7,9M  1,9G   1% 
/run/shm\nnone   tmpfs 100M  100K  100M   1% /run/user\n/dev/sda6   
   ext4  160G  110G   43G  73% /home\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda53,0M  
285K  2,8M   10% /\nnone 476K 2  476K1% 
/sys/fs/cgroup\nudev 474K   524  473K1% /dev\ntmpfs
476K   534  476K1% /run\nnone 476K 3  476K1% 
/run/lock\nnone 476K13  476K1% /run/shm\nnone 
476K46  476K1% /run/user\n/dev/sda6 11M  517K  9,7M5% 
/home\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140215)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-18T13:16:04.211524

To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/1309508/+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 1309508] Re: Chromium doesn't use Icedtea Java NPAPI plugin

[Bug Watch Updater]

** Changed in: icedtea
   Status: Confirmed => Won't Fix

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

Title:
  Chromium doesn't use Icedtea Java NPAPI plugin

Status in Iced Tea:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in icedtea-web package in Ubuntu:
  Won't Fix

Bug description:
  I've installed openjdk-7-jre and icedtea-7-plugin, but chromium can't launch 
java applets. Java doesn't show in about:plugins.
  How to reproduce:
  1) Install openjdk-7-jre and icedtea-7-plugin
  2) Open chromium
  3) Go to about:plugins and look for java or icedtea, or try to run an applet
  What happens: the plugin is not listed, applets won't run
  What is expected: the plugin is listed and applets work

  Note: Firefox detects the plugin and applets work in Firefox, which
  means the plugin is properly installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 14:42:43 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda5  
ext4   47G  7,3G   38G  17% /\nnone   tmpfs 4,0K 0  4,0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1,9G  4,0K  1,9G   1% /dev\ntmpfs   
   tmpfs 381M  1,2M  380M   1% /run\nnone   tmpfs 5,0M 
0  5,0M   0% /run/lock\nnone   tmpfs 1,9G  7,9M  1,9G   1% 
/run/shm\nnone   tmpfs 100M  100K  100M   1% /run/user\n/dev/sda6   
   ext4  160G  110G   43G  73% /home\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda53,0M  
285K  2,8M   10% /\nnone 476K 2  476K1% 
/sys/fs/cgroup\nudev 474K   524  473K1% /dev\ntmpfs
476K   534  476K1% /run\nnone 476K 3  476K1% 
/run/lock\nnone 476K13  476K1% /run/shm\nnone 
476K46  476K1% /run/user\n/dev/sda6 11M  517K  9,7M5% 
/home\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140215)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-18T13:16:04.211524

To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/1309508/+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 193325] Re: "unknown media type" during update

[SeijiSensei]

Installing new packages today still reports those missing media types
during "Processing triggers for shared-mime-info."  Are you ever going
to fix this?  For that matter, are you ever going to reply to my
postings?  This bug has persisted for years now.  It's about time you
resolve it.

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

Title:
  "unknown media type" during update

Status in Nautilus:
  Confirmed
Status in shared-mime-info:
  Fix Released
Status in shared-mime-info package in Ubuntu:
  Fix Released

Bug description:
  Messages below seen during the latest round of updates. The messages
  from several packages seem to be mixed around, so I'm not sure which
  one triggered them. I suspect nautilus.

  Setting up shared-mime-info (0.23-3) ...
  Unknown media type in type 'x-content/video-vcd'

  Unknown media type in type 'x-content/video-svcd'

  Unknown media type in type 'x-content/video-dvd'

  Unknown media type in type 'x-content/image-dcf'

  Unknown media type in type 'x-content/audio-cdda'

  Unknown media type in type 'x-content/blank-cd'

  Unknown media type in type 'x-content/blank-dvd'

  Unknown media type in type 'x-content/blank-bd'

  Unknown media type in type 'x-content/blank-hddvd'

  Unknown media type in type 'x-content/audio-dvd'

  Unknown media type in type 'x-content/video-bluray'

  Unknown media type in type 'x-content/video-hddvd'

  Unknown media type in type 'x-content/image-picturecd'

  Unknown media type in type 'x-content/audio-player'

  Unknown media type in type 'x-content/software'

  Setting up ucf (3.004-0ubuntu3) ...

  Setting up seahorse (2.21.91-0ubuntu3) ...
  Unknown media type in type 'x-content/video-vcd'

  Unknown media type in type 'x-content/video-svcd'

  Unknown media type in type 'x-content/video-dvd'

  Unknown media type in type 'x-content/image-dcf'

  Unknown media type in type 'x-content/audio-cdda'

  Unknown media type in type 'x-content/blank-cd'

  Unknown media type in type 'x-content/blank-dvd'

  Unknown media type in type 'x-content/blank-bd'

  Unknown media type in type 'x-content/blank-hddvd'

  Unknown media type in type 'x-content/audio-dvd'

  Unknown media type in type 'x-content/video-bluray'

  Unknown media type in type 'x-content/video-hddvd'

  Unknown media type in type 'x-content/image-picturecd'

  Unknown media type in type 'x-content/audio-player'

  Unknown media type in type 'x-content/software'

  Setting up ubuntu-gdm-themes (0.24) ...
  Setting up linux-restricted-modules-common (2.6.24.9-8.25) ...

  Setting up nautilus-data (1:2.21.91-0ubuntu3) ...
  Unknown media type in type 'x-content/video-vcd'

  Unknown media type in type 'x-content/video-svcd'

  Unknown media type in type 'x-content/video-dvd'

  Unknown media type in type 'x-content/image-dcf'

  Unknown media type in type 'x-content/audio-cdda'

  Unknown media type in type 'x-content/blank-cd'

  Unknown media type in type 'x-content/blank-dvd'

  Unknown media type in type 'x-content/blank-bd'

  Unknown media type in type 'x-content/blank-hddvd'

  Unknown media type in type 'x-content/audio-dvd'

  Unknown media type in type 'x-content/video-bluray'

  Unknown media type in type 'x-content/video-hddvd'

  Unknown media type in type 'x-content/image-picturecd'

  Unknown media type in type 'x-content/audio-player'

  Unknown media type in type 'x-content/software'

  Setting up compiz-core (1:0.7.0-0ubuntu3) ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/193325/+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 1516133] [NEW] package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el subproceso script pre-removal nuevo devolvió el código de salida de error 1

[manukleart]

Public bug reported:

I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too.
Actually Libre Office Writter doesn't work.

Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed
and sometimes say don't find hard disk
 sometimes thunderbird fails
and sometimes i can't write any file.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apport 2.14.1-0ubuntu3.18
ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-33-generic i686
ApportLog:

ApportVersion: 2.14.1-0ubuntu3.18
Architecture: i386
Date: Fri Nov 13 20:38:45 2015
DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
InstallationDate: Installed on 2015-11-01 (12 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: apport
Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 need-duplicate-check trusty

** Description changed:

- I have a lot of problems in my laptop with ubuntu 14.03 LTS and 15.10 too.
+ I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too.
  Actually Libre Office Writter doesn't work.
  
  Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed
  and sometimes say don't find hard disk
-  sometimes thunderbird fails 
+  sometimes thunderbird fails
  and sometimes i can't write any file.
  
  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.18
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic i686
  ApportLog:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  Date: Fri Nov 13 20:38:45 2015
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2015-11-01 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
-  dpkg 1.17.5ubuntu5.4
-  apt  1.0.1ubuntu2.10
+  dpkg 1.17.5ubuntu5.4
+  apt  1.0.1ubuntu2.10
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1516133

Title:
  package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el
  subproceso script pre-removal nuevo devolvió el código de salida de
  error 1

Status in apport package in Ubuntu:
  New

Bug description:
  I have a lot of problems in my laptop with ubuntu 14.04.3 LTS and 15.10 too.
  Actually Libre Office Writter doesn't work.

  Sometimes it depends when i put in on my laptop appairs ACPI PCC Probe failed
  and sometimes say don't find hard disk
   sometimes thunderbird fails
  and sometimes i can't write any file.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: apport 2.14.1-0ubuntu3.18
  ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic i686
  ApportLog:

  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  Date: Fri Nov 13 20:38:45 2015
  DuplicateSignature: package:apport:2.14.1-0ubuntu3.18:el subproceso script 
pre-removal nuevo devolvió el código de salida de error 1
  ErrorMessage: el subproceso script pre-removal nuevo devolvió el código de 
salida de error 1
  InstallationDate: Installed on 2015-11-01 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: apport
  Title: package apport 2.14.1-0ubuntu3.18 failed to install/upgrade: el 
subproceso script pre-removal nuevo devolvió el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[David Lenz]

Fair enough. Thanks.

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

Title:
  Chromium doesn't use Icedtea Java NPAPI plugin

Status in Iced Tea:
  Won't Fix
Status in chromium-browser package in Ubuntu:
  Won't Fix
Status in icedtea-web package in Ubuntu:
  Won't Fix

Bug description:
  I've installed openjdk-7-jre and icedtea-7-plugin, but chromium can't launch 
java applets. Java doesn't show in about:plugins.
  How to reproduce:
  1) Install openjdk-7-jre and icedtea-7-plugin
  2) Open chromium
  3) Go to about:plugins and look for java or icedtea, or try to run an applet
  What happens: the plugin is not listed, applets won't run
  What is expected: the plugin is listed and applets work

  Note: Firefox detects the plugin and applets work in Firefox, which
  means the plugin is properly installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: chromium-browser 34.0.1847.116-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 18 14:42:43 2014
  Desktop-Session:
   DESKTOP_SESSION = ubuntu
   XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg
   XDG_DATA_DIRS = 
/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
  DetectedPlugins:
   
  DiskUsage:
   b'Filesystem Type  Size  Used Avail Use% Mounted on\n/dev/sda5  
ext4   47G  7,3G   38G  17% /\nnone   tmpfs 4,0K 0  4,0K   
0% /sys/fs/cgroup\nudev   devtmpfs  1,9G  4,0K  1,9G   1% /dev\ntmpfs   
   tmpfs 381M  1,2M  380M   1% /run\nnone   tmpfs 5,0M 
0  5,0M   0% /run/lock\nnone   tmpfs 1,9G  7,9M  1,9G   1% 
/run/shm\nnone   tmpfs 100M  100K  100M   1% /run/user\n/dev/sda6   
   ext4  160G  110G   43G  73% /home\n'
   
   Inodes:
   b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sda53,0M  
285K  2,8M   10% /\nnone 476K 2  476K1% 
/sys/fs/cgroup\nudev 474K   524  473K1% /dev\ntmpfs
476K   534  476K1% /run\nnone 476K 3  476K1% 
/run/lock\nnone 476K13  476K1% /run/shm\nnone 
476K46  476K1% /run/user\n/dev/sda6 11M  517K  9,7M5% 
/home\n'
  Env:
   MOZ_PLUGIN_PATH = None
   LD_LIBRARY_PATH = None
  InstallationDate: Installed on 2014-04-18 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140215)
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
  modified.conffile..etc.default.chromium.browser: [deleted]
  mtime.conffile..etc.chromium.browser.default: 2014-04-18T13:16:04.211524

To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/1309508/+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 1315928] Re: Xorg. Unknown header type 7f AMD/Intel

[Launchpad Bug Tracker]

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

** Changed in: fglrx-installer-updates (Ubuntu)
   Status: New => Confirmed

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

Title:
  Xorg. Unknown header type 7f AMD/Intel

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed
Status in fglrx-pxpress package in Ubuntu:
  Confirmed

Bug description:
  When I try to install the fglrx on ubuntu 14.04, the last message said that 
the card is not recognize.
  The lspci -vv:
   VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Seymour 
[Radeon HD 6400M/7400M Series] (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1315928/+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 1516165] [NEW] package nvidia-current 304.128-0ubuntu1 failed to install/upgrade: package nvidia-current is already installed and configured

[Vanja Öst]

Public bug reported:

NVIDIA problem, last time i tried, my xserver shutdown and wouldn't
start, this time it just failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-current 304.128-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
ApportVersion: 2.19.2-0ubuntu5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Nov 13 23:11:58 2015
DuplicateSignature:
 Processing triggers for man-db (2.7.5-1) ...
 dpkg: error processing package libcuda1-304 (--configure):
  package libcuda1-304 is already installed and configured
ErrorMessage: package nvidia-current is already installed and configured
InstallationDate: Installed on 2015-11-04 (9 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageVersions:
 dpkg 1.18.3ubuntu1
 apt  1.0.10.2ubuntu1
SourcePackage: nvidia-graphics-drivers-304
Title: package nvidia-current 304.128-0ubuntu1 failed to install/upgrade: 
package nvidia-current is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package need-duplicate-check 
third-party-packages xenial

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

Title:
  package nvidia-current 304.128-0ubuntu1 failed to install/upgrade:
  package nvidia-current is already installed and configured

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

Bug description:
  NVIDIA problem, last time i tried, my xserver shutdown and wouldn't
  start, this time it just failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-current 304.128-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.2-0ubuntu5
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Nov 13 23:11:58 2015
  DuplicateSignature:
   Processing triggers for man-db (2.7.5-1) ...
   dpkg: error processing package libcuda1-304 (--configure):
package libcuda1-304 is already installed and configured
  ErrorMessage: package nvidia-current is already installed and configured
  InstallationDate: Installed on 2015-11-04 (9 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: nvidia-graphics-drivers-304
  Title: package nvidia-current 304.128-0ubuntu1 failed to install/upgrade: 
package nvidia-current is already installed and configured
  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/1516165/+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 1308800] Re: Unity doesn't respawn all the times on crashes

[Mathew Hodson]

** Changed in: gnome-session (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Unity doesn't respawn all the times on crashes

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

Bug description:
  [Impact]
  Killing compiz repeatedly doesn't make unity to reload all the times.

  This is caused by the fact that due to a regression unity7 is not
  loaded anymore by upstart (but by gnome-session) and thus it seems
  that sometimes it doesn't properly gets restarted.

  This is also a security issue, because if the session was locked, and
  unity is not reloaded the session won't be locked anymore.

  [Test Case]
  From a terminal run killall -9 compiz multiple times, it should always 
reload, but it fails after a couple of times.

  [Regression Potential]
  The fix is about always making unity to be launched by upstart.
  Regression potential is low, since upstart is now used by most ubuntu desktop 
applications, and it ensures compiz will run properly anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1308800/+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 1433013] Re: Super -> exec vs Alt-F2 -> exec have different environment

[Mathew Hodson]

** No longer affects: unity-lens-applications (Ubuntu)

** Project changed: unity => ubuntu-translations

** No longer affects: ubuntu-translations

** No longer affects: unity (Ubuntu)

** Changed in: upstart (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu Utopic)
   Importance: Undecided => Medium

** Changed in: upstart (Ubuntu Vivid)
   Importance: Undecided => Medium

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

Title:
  Super -> exec vs Alt-F2 -> exec have different environment

Status in upstart package in Ubuntu:
  Confirmed
Status in upstart source package in Trusty:
  Confirmed
Status in upstart source package in Utopic:
  Confirmed
Status in upstart source package in Vivid:
  Confirmed

Bug description:
  upstart in user session manages environmental variables and most
  things have them, however Alt-f2 started proccesses lack them.

  to test

  Super Key -> "xterm" -> Enter -> env | grep SSH

  vs

  Alt+F2 -> "xterm" -> Enter -> env | grep SSH

  via Super Key -> the environment is correct

  via Alt-F2 -> it is not

  
  I believe Alt+F2 code path should call into upstart dbus api to "list-env" 
and import that environment before executing the search result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1433013/+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 1515749] Re: Merge 3.18.2 from debian

[Jackson Doak]

** Patch added: "deb.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1515749/+attachment/4518507/+files/deb.diff

** Changed in: gnome-desktop3 (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Merge 3.18.2 from debian

Status in gnome-desktop3 package in Ubuntu:
  Triaged

Bug description:
  Merge 3.18.2 from debian
  debdiff attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1515749/+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 1510587] Re: Nautilus crashes when delete a file in a folder which is a symbolic link to another filesystem

[petersaints]

I don't think that this is nautilus specific. I have just tried to
reproduce this on other file managers (e.g., nemo and thunar) and they
also crash. The problem seems to be related with glib. So any file
manager that relies on it will crash.

Can anyone confirm if my assertion is correct?

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

Title:
  Nautilus crashes when delete a file in a folder which is a symbolic
  link to another filesystem

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Nautilus crashes with an "assertion error" whenever accessing a
  folder, which is a symbolic link to a folder in another filesystem,
  and then deleting any file inside that folder (the file is not
  deleted).

  Steps I used to reproduce de problem in my machine:

  1) /dev/sda1 partition mounted on root folder with XFS filesystem;
  2) /dev/sda2 partition mounted on /mnt/data folder partition with EXT4 
filesystem;
  3) create a folder "/mnt/data/test" and the empty text file 
"/mnt/data/test/file.txt";
  4) in your home folder, create a symbolic to the "test" folder above with "ln 
-s /mnt/data/test";
  5) open the symbolic link folder with "nautilus /test";
  6) delete the "file.txt" file (pressing the delete button) and watch nautilus 
crashing with the following error:

  nautilus: malloc.c:2909: __libc_malloc: Assertion `!victim || 
mchunkptr)((char*)(victim) - 2*(sizeof(size_t)->size & 0x2) || ar_ptr 
== (mchunkptr)((char*)(victim) - 2*(sizeof(size_t)->size & 0x4) ? 
((heap_info *) ((unsigned long) (((mchunkptr)((char*)(victim) - 
2*(sizeof(size_t) & ~((2 * (4 * 1024 * 1024 * sizeof(long))) - 1)))->ar_ptr 
: _arena)' failed.
  Abortado

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: nautilus 1:3.14.2-0ubuntu12
  ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Oct 27 12:59:23 2015
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2015-10-23 (3 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1510587/+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 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Launchpad Bug Tracker]

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

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => Confirmed

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

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  Triaged
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+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 1509622] Re: Xorg crash

[Vindicator]

OK, I was going to publish a new bug report last night after it happened
again with Kodi (bios update didn't fix it), but I got a notice of new
updates which included a kernel 4.2-19 and display manager update, so
hopefully it is a known issue that was fixed there.

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This is the full apport data from the crash reported as bug #1507461.
  It occurred whilst watching a full-screen Flash video in Google
  Chrome.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Oct 24 18:04:11 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21fa]
  MachineType: LENOVO CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/peleg0-lv01 ro splash quiet nomdmonddf nomdmonisw vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET33WW (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET33WW(1.13):bd07/24/2012:svnLENOVO:pnCTO:pvrThinkPadX230:rvnLENOVO:rnCTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Oct 24 17:58:31 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509622/+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 1494095] Re: Dell U3414W screen not turning on in 3440 x 1440 mode

[Travis Reeder]

Disabled DP 1.2 on my monitor and it started working for me too.

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

Title:
  Dell U3414W screen not turning on in 3440 x 1440 mode

Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  Following on from https://answers.launchpad.net/ubuntu/+source
  /xserver-xorg-video-intel/+question/270926

  When I plug a Dell U3414W screen into my Dell XPS 13 9343 display port
  the screen does not turn on when I enable it's native 3440 x 1440 in
  the display settings.

  Lower resolutions correctly work such as:
  2560 x 1080
  1560 x 1440

  I also found these messages in the dmesg log:
  [ 308.637781] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe B FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.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: Thu Sep 10 11:56:31 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.19.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-25-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0665]
  InstallationDate: Installed on 2015-06-20 (82 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed 
root=UUID=b9c575ed-3fa1-4890-b4f2-b57441e8337d ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
  xserver.bootTime: Wed Sep  9 13:12:40 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41126 
   vendor DEL
  xserver.version: 2:1.17.1-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1494095/+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 548886] Re: KDE won't start with fglrx drivers in Lucid

[Flames_in_Paradise]

corr.: status eq. "incomplete" allows bug-report to expire in 60 days.

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

Title:
  KDE won't start with fglrx drivers in Lucid

Status in fglrx-installer package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu lucid (development branch)
  Release:10.04

  KDE won't start with fglrx drivers.
  GNOME works properly.  KDE works with installed (vesa?) driver.  

  Upon attempting to log in to a KDE desktop session from KDM, the KDE
  splash screen comes up and the 4 fuzzy icons can be dimly seen.  They
  never solidify as they normally do.

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Mar 26 08:13:08 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100225)
  NonfreeKernelModules: fglrx
  Package: kubuntu-desktop 1.165
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  SourcePackage: kubuntu-meta
  Uname: Linux 2.6.32-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/548886/+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 548886] Re: KDE won't start with fglrx drivers in Lucid

[Flames_in_Paradise]

Setting the bug status to "invalid" as this edition of Ubuntu has
reached End-of-life-cycle.

If you experience a similar symptom on a  supported version please file
a new bug.

If you are not satisfied with the solution please feel free to reopen
the bug-report.

Thanks for reporting and apologies for any inconveniences.

** Tags added: eol

** Changed in: fglrx-installer (Ubuntu)
   Status: New => Incomplete

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

Title:
  KDE won't start with fglrx drivers in Lucid

Status in fglrx-installer package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu lucid (development branch)
  Release:10.04

  KDE won't start with fglrx drivers.
  GNOME works properly.  KDE works with installed (vesa?) driver.  

  Upon attempting to log in to a KDE desktop session from KDM, the KDE
  splash screen comes up and the 4 fuzzy icons can be dimly seen.  They
  never solidify as they normally do.

  ProblemType: Bug
  Architecture: amd64
  Date: Fri Mar 26 08:13:08 2010
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Kubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100225)
  NonfreeKernelModules: fglrx
  Package: kubuntu-desktop 1.165
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
  SourcePackage: kubuntu-meta
  Uname: Linux 2.6.32-17-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/548886/+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 1387303] Re: regression: gnome-keyring components can't be disabled anymore

[Mathew Hodson]

** Changed in: gnome-keyring (Ubuntu Trusty)
   Importance: Undecided => Wishlist

** Changed in: gnome-keyring (Ubuntu Utopic)
   Importance: Undecided => Wishlist

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

Title:
  regression: gnome-keyring components can't be disabled anymore

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Trusty:
  Fix Released
Status in gnome-keyring source package in Utopic:
  Fix Released
Status in gnome-keyring source package in Vivid:
  Fix Released

Bug description:
  To disable gnome-keyring ssh agent,
   - disable gnome keyring ssh in startup applications

  To disable gnome-keyring gpg agent,
   - disable gnome keyring gpg in startup applications

  If above are disabled, stock ssh-agent & gpg-agent upstart jobs are
  used instead.

  =
  SRU tests

  By default environment should have SSH & GPG agent variables pointing
  at gnome-keyring provided ones.

  Disabling gpg or ssh gnome keyring desktop files in "Startup
  Applications" upon next login stock gpg/ssh agent's will be used. (No
  gnome-keyring name in the SSH/GPG agent variable values)

  Similarly, disabling upstart jobs for ssh or gpg agent also enables
  stock ssh/gpg agents. (e.g. echo manual > ~/.config/upstart/gnome-
  keyring-ssh.override)

  =

  GNOME Keyring is by default a rather invasive service, which meddles
  with security sensitive processes invasively. This may or may not be
  wise depending on a users situation.

  One particular case is GNOME Keyring's gpg-agent implementation, which
  is incomplete and therefore doesn't support GPG's OpenPGP smartcard
  support. gpg simply fails (with smartcards) when GNOME Keyring is
  impersonating gpg-agent...

  So to be able to use OpenPGP smartcards on Ubuntu, one needs to
  disable GNOME Keyring from impersonating gpg-agent, which for quite
  some time now has been trivial to effectively do:

  echo 'X-GNOME-Autostart-enabled=false' >> /etc/xdg/autostart/gnome-
  keyring-gpg.desktop

  With GNOME Keyring's recent update (3.10.1-1ubuntu4.1) in Trusty, this
  seems to have been broken by the addition of:

  /usr/share/upstart/sessions/gnome-keyring.conf

  So it seems the /etc/xdg/autostart/gnome-keyring files are either
  being ignored, or the started process is supplanted by the process
  started by the upstart session config.

  What is unclear to me is what the upstart session configuration is
  supposed to achieve? And if it is meant to supplant the xdg/autostart
  files, those should probably have been removed to prevent them from
  causing any confusion as to how gnome-keyring is started/managed.

  Presuming the upstart session is meant to stay, I would suggest to
  remove the /etc/xdg/autostart/gnome-keyring-*.desktop files to prevent
  confusion as mentioned above. And in my opinion a mechanism should be
  provided so users can control which gnome-keyring components '--
  components=pkcs11,secrets,ssh,gpg' are activated using some
  configuration file in /etc, as files in /usr aren't meant to be user
  edited.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 29 18:14:57 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-07 (205 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.xdg.autostart.gnome.keyring.gpg.desktop: 
2014-04-09T19:49:03.884840

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1387303/+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 1516153] [NEW] Wifi does not work after suspending.

[Jeroen Mathon]

Public bug reported:

After resuming from a suspend, sometimes(very often) the wifi does not show any 
connections.
Even if i uncheck and recheck the Enable wifi checkbox it still does not show 
any connections.

I am using Ubuntu 15.10.
NetworkManager is at version 1.0.4.

My hardware is a Asus X750J.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
Date: Fri Nov 13 22:07:24 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-10-27 (17 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection/4 
 tun0tun   connected /org/freedesktop/NetworkManager/Devices/3  
tun08a335ba2-ebce-4e08-9431-d8a4322cfa26  
/org/freedesktop/NetworkManager/ActiveConnection/5 
 wlp2s0  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  --  
----
 
 lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  --  
----
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug wily

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

Title:
  Wifi does not work after suspending.

Status in network-manager package in Ubuntu:
  New

Bug description:
  After resuming from a suspend, sometimes(very often) the wifi does not show 
any connections.
  Even if i uncheck and recheck the Enable wifi checkbox it still does not show 
any connections.

  I am using Ubuntu 15.10.
  NetworkManager is at version 1.0.4.

  My hardware is a Asus X750J.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  Date: Fri Nov 13 22:07:24 2015
  ExecutablePath: /usr/sbin/NetworkManager
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-10-27 (17 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp3s0  ethernet  connected /org/freedesktop/NetworkManager/Devices/0  
Wired connection 1  a6283be3-2692-4d49-87d6-4c2f7cf00e2f  
/org/freedesktop/NetworkManager/ActiveConnection/4 
   tun0tun   connected /org/freedesktop/NetworkManager/Devices/3  
tun08a335ba2-ebce-4e08-9431-d8a4322cfa26  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   wlp2s0  wifi  disconnected  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo  loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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