[Desktop-packages] [Bug 1583666] Re: laggy PC

[Sami Senng]

I have similar configuration, HP notebook eliteBook 850 g3, VGA
compatible controller: Intel Corporation Sky Lake Integrated Graphics
(rev 07). Ubuntu in dual monitor system freezes after awakening from
suspending to ram.

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

Title:
  laggy PC

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have an HP envy 13 (6th gen core i5) that runs smoothly on windows.
  I really try using ubuntu as my main OS but lagginess doesn't help
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 19 10:34:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80df]
  InstallationDate: Installed on 2016-05-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=54673ec1-b654-4c3e-b021-29dcd078a702 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd02/18/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.59:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 19 06:48:29 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16730 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1583666/+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 1583666] Re: laggy PC

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

Title:
  laggy PC

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have an HP envy 13 (6th gen core i5) that runs smoothly on windows.
  I really try using ubuntu as my main OS but lagginess doesn't help
  that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 19 10:34:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80df]
  InstallationDate: Installed on 2016-05-18 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: HP HP ENVY Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=54673ec1-b654-4c3e-b021-29dcd078a702 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DF
  dmi.board.vendor: HP
  dmi.board.version: 87.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd02/18/2016:svnHP:pnHPENVYNotebook:pvrType1ProductConfigId:rvnHP:rn80DF:rvr87.59:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu May 19 06:48:29 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16730 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1583666/+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 1492443] Re: bluetooth-wizard cannot pair with a 1byone bluetooth keyboard (or possibly, any keyboard that requires a PIN code?)

[Kai-Heng Feng]

I can confirm that unity-control-center 15.04.0+16.04.20160413-0ubuntu3
in xenial-proposed fixes the issue.

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

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

Title:
  bluetooth-wizard cannot pair with a 1byone bluetooth keyboard (or
  possibly, any keyboard that requires a PIN code?)

Status in unity-control-center package in Ubuntu:
  Fix Released
Status in unity-control-center source package in Xenial:
  Fix Committed

Bug description:
  * Impact
  some bluetooth keyboards can't be paired

  * Test case
  If you own a keyboard requiring a pincode for pairing try to pair it, it 
should work

  * Regression potential
  limited, it's only adding new code to a callback function which was 
unimplemented

  

  I'm on wily.  I just got this keyboard, so I don't know if this is a
  regression or not with Bluez5.  I'm guessing it is though.

  I can pair via the console just fine (though connecting is another
  story -- bug 1492441):

  $ bluetoothctl
  [NEW] Device 08:73:00:13:CC:45 1byone Keyboard
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# pair 08:73:00:13:CC:45
  Attempting to pair with 08:73:00:13:CC:45
  [CHG] Device 08:73:00:13:CC:45 Connected: yes
  [agent] PIN code: 420005
  [CHG] Device 08:73:00:13:CC:45 Modalias: usb:v04E8p7021d011B
  [CHG] Device 08:73:00:13:CC:45 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 08:73:00:13:CC:45 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 08:73:00:13:CC:45 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 08:73:00:13:CC:45 Paired: yes
  Pairing successful
  [CHG] Device 08:73:00:13:CC:45 Connected: no

  But when using bluetooth-wizard, none of the "PIN options" options
  work for me.  I expected to be prompted to enter a random PIN code
  like I do when connecting it to my iPad or when connecting via the
  console above.  But it just spins for a while and says that pairing
  failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+15.10.20150818-0ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep  4 15:55:47 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20120703-2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-01-09 (967 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20120703-15:08
  SourcePackage: unity-control-center
  SystemImageInfo:
   current build number: 0
   device name:
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to wily on 2013-01-31 (945 days ago)

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

Re: [Desktop-packages] [Bug 1582213] Re: Bluetooth headset doesn't play any sound (regression)

[Luke Yelavich]

I know there has been some discussion upstream about bluez 5 and
different profiles, but I haven't followed it closely so not sure if
related.

Mary, could you please try and get a log from PulseAudio, as outlined at
https://wiki.ubuntu.com/PulseAudio/Log.

Thanks.

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

Title:
  Bluetooth headset doesn't play any sound (regression)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a Sennheiser MM 450-X headset.

  In 15.10, connection & playback was straightforward.

  In 16.04, the headset connects, and shows up as default playback
  device on `pavucontrol`, but there is no sound.

  A functional workaround is to, after having connected it, to go the
  `Configuration` tab, and in the `Profile` dropdown, to choose `...
  HSP/HFP`, which will make them play as expected (but in low quality),
  then switch to `... A2DP Sink` (they will play in high quality).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  saverio2936 F pulseaudio
   /dev/snd/controlC2:  saverio2936 F pulseaudio
   /dev/snd/controlC0:  saverio2936 F pulseaudio
  Date: Mon May 16 14:18:58 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-03-11 (66 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

Re: [Desktop-packages] [Bug 1582414] Re: No HDMI audio on Lenovo pro dock with T440s

[Luke Yelavich]

The best way to determine whether this is kernel related is to test a
recent daily trusty live image that has a newer kernel... I think newer
images have the xenial kernel on them, so this would be a good way to
determine where the problem is. A fair bit changed in pulse between
trusty and xenial, and same with the kernel.

Martin, please download the latest daily image from
http://cdimage.ubuntu.com/trusty/daily-live, put it onto a bootable
device or an optical disk, and boot from it. Try and use the dock's
DP/HDMI connection and report back.

Thanks.

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

Title:
  No HDMI audio on Lenovo pro dock with T440s

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  pavucontrol shows Display Port/HDMI output as "(unplugged)" and cannot
  be chosen as a sink.  This is only a problem with the dock; audio
  works when plugging HDMI through the laptop's DP input.

  The audio did work with the dock in Ubuntu 14.04.  Did something in
  jack detection change?  Anyway, my work around is to plug a 3.4mm
  audio cable into the dock and power the speakers that way, but it
  would be nice to use the HDMI audio again.

  I would love to have a work around.  I've attached the output from
  alsa-info.sh, just in case this is useful.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  weinberg   2221 F pulseaudio
   /dev/snd/controlC2:  weinberg   2221 F pulseaudio
   /dev/snd/controlC0:  weinberg   2221 F pulseaudio
   /dev/snd/controlC1:  weinberg   2221 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May 16 17:18:06 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-06 (10 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET74WW (2.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ARA0S100
  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:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ARA0S100
  dmi.product.version: ThinkPad T440s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1582414/+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 1586628] Re: Thunderbird should switch to GTK3

[Bug Watch Updater]

** Changed in: thunderbird
   Status: Unknown => Fix Released

** Changed in: thunderbird
   Importance: Unknown => Medium

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

Title:
  Thunderbird should switch to GTK3

Status in Mozilla Thunderbird:
  Fix Released
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  I think that it would be good if Thunderbird got up-to-date with its
  GTK look so it would be good if it upgraded from GTK2 to GTK3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1586628/+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 1542519] Re: Double menu bar

[rtimai]

New discovery in the VLC double menu syndrome:  Turning "Minimal
interface" on and off by pressing Ctl-H several times on my system seems
to reliably remove the menu in the Unity menubar, leaving the menu in
the window titlebar. This appears to be the behavior despite my Unity
System Settings > Appearance > Behavior settings for the menu to
integrate in the Unity menubar. But at least the cosmetic annoyance can
be fixed, at least persistently over several sessions, if not
permanently.

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

Title:
  Double menu bar

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  I currently get two menu bars in VLC on Xenial.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: vlc 2.2.2-3
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  5 23:31:41 2016
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1542519/+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 1584962] Re: [aisleriot][Klondike] Missing card

[Bug Watch Updater]

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

** Changed in: aisleriot
   Importance: Unknown => Medium

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

Title:
  [aisleriot][Klondike] Missing card

Status in Aisleriot:
  Confirmed
Status in aisleriot package in Ubuntu:
  New

Bug description:
  I just played, and almost win, until I realized that the third of spade was 
completely missing : it is nor in the stack nor a hidden card.
  In attachment, you will find a screenshot of my game.

  Version : 1:3.18.2-1ubuntu1

  So frustrating ! ^^

To manage notifications about this bug go to:
https://bugs.launchpad.net/aisleriot/+bug/1584962/+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 1586892] Re: package fonts-texgyre 2.004.2-4 failed to install/upgrade: package fonts-texgyre is already installed and configured

[dino99]

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

** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

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

Title:
  package fonts-texgyre 2.004.2-4 failed to install/upgrade: package
  fonts-texgyre is already installed and configured

Status in tex-gyre package in Ubuntu:
  New

Bug description:
  I was trying to install TEX package, during which the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fonts-texgyre 2.004.2-4
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Mon May 30 09:39:31 2016
  DuplicateSignature: package:fonts-texgyre:2.004.2-4:package fonts-texgyre is 
already installed and configured
  ErrorMessage: package fonts-texgyre is already installed and configured
  InstallationDate: Installed on 2016-05-16 (13 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: tex-gyre
  Title: package fonts-texgyre 2.004.2-4 failed to install/upgrade: package 
fonts-texgyre 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/tex-gyre/+bug/1586892/+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 1586892] [NEW] package fonts-texgyre 2.004.2-4 failed to install/upgrade: package fonts-texgyre is already installed and configured

[Pratik]

Public bug reported:

I was trying to install TEX package, during which the error occurred.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: fonts-texgyre 2.004.2-4
ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
Uname: Linux 3.16.0-71-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
AptdaemonVersion: 1.1.1-1ubuntu5.2
Architecture: amd64
Date: Mon May 30 09:39:31 2016
DuplicateSignature: package:fonts-texgyre:2.004.2-4:package fonts-texgyre is 
already installed and configured
ErrorMessage: package fonts-texgyre is already installed and configured
InstallationDate: Installed on 2016-05-16 (13 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.6
 apt  1.0.1ubuntu2.14
SourcePackage: tex-gyre
Title: package fonts-texgyre 2.004.2-4 failed to install/upgrade: package 
fonts-texgyre is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tex-gyre (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: already-installed amd64 apport-package need-duplicate-check trusty

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

Title:
  package fonts-texgyre 2.004.2-4 failed to install/upgrade: package
  fonts-texgyre is already installed and configured

Status in tex-gyre package in Ubuntu:
  New

Bug description:
  I was trying to install TEX package, during which the error occurred.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: fonts-texgyre 2.004.2-4
  ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27
  Uname: Linux 3.16.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  AptdaemonVersion: 1.1.1-1ubuntu5.2
  Architecture: amd64
  Date: Mon May 30 09:39:31 2016
  DuplicateSignature: package:fonts-texgyre:2.004.2-4:package fonts-texgyre is 
already installed and configured
  ErrorMessage: package fonts-texgyre is already installed and configured
  InstallationDate: Installed on 2016-05-16 (13 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.14
  SourcePackage: tex-gyre
  Title: package fonts-texgyre 2.004.2-4 failed to install/upgrade: package 
fonts-texgyre 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/tex-gyre/+bug/1586892/+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 1501972] Re: nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to build [/bin/sh: 1: cc: not found]

[Daniel van Vugt]

** Also affects: nvidia-graphics-drivers-352 (Ubuntu)
   Importance: Undecided
   Status: New

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

** Also affects: nvidia-graphics-drivers-352-updates (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to
  build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-346 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-352-updates package in Ubuntu:
  Confirmed

Bug description:
  I really have no idea of this issue, i just booted up and ubuntu
  notified me that there was a problem... hopefully ubuntu is self
  reporting enough information.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-346 346.96-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-65-generic
  Date: Thu Oct  1 18:17:00 2015
  InstallationDate: Installed on 2015-09-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 346.96-0ubuntu0.0.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: nvidia-graphics-drivers-346
  Title: nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.modprobe.d.nvidia.346.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-346/+bug/1501972/+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 1581739] Re: nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to build [/bin/sh: 1: cc: not found]

[Daniel van Vugt]

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

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


** Summary changed:

- nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to build
+ nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to build 
[/bin/sh: 1: cc: not found]

** This bug has been marked a duplicate of bug 1501972
   nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to build 
[/bin/sh: 1: cc: not found]

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

Title:
  nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to
  build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-352 package in Ubuntu:
  New

Bug description:
  This PC stop working after installing pycuda and others devices for it. The 
black screen of death appeared. The driver of nvidia stopped working after it. 
Now my screen can't go 1080p, because of Xserver driver. :)
  Thanks NVidia for screwing everything!
  P.S.: Screwing because i won't say the f-word here.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-352 (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-51-generic
  Date: Sat May 14 01:39:19 2016
  InstallationDate: Installed on 2016-03-01 (73 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 352.63-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: nvidia-graphics-drivers-352
  Title: nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2016-04-16 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1581739/+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 1581741] Re: nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to build [/bin/sh: 1: cc: not found]

[Daniel van Vugt]

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

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


** Summary changed:

- nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to build
+ nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to build 
[/bin/sh: 1: cc: not found]

** This bug has been marked a duplicate of bug 1501972
   nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to build 
[/bin/sh: 1: cc: not found]

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

Title:
  nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to
  build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-352 package in Ubuntu:
  New

Bug description:
  This PC stop working after installing pycuda and others devices for it. The 
black screen of death appeared. The driver of nvidia stopped working after it. 
Now my screen can't go 1080p, because of Xserver driver. :)
  Thanks NVidia for screwing everything!
  P.S.: Screwing because i won't say the f-word here.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-352 352.63-0ubuntu0.14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-51-generic
  Date: Sat May 14 01:39:19 2016
  InstallationDate: Installed on 2016-03-01 (73 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 352.63-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: nvidia-graphics-drivers-352
  Title: nvidia-352 352.63-0ubuntu0.14.04.1: nvidia-352 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2016-04-16 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1581741/+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 1581743] Re: nvidia-352-updates 352.63-0ubuntu0.14.04.1: nvidia-352-updates kernel module failed to build [/bin/sh: 1: cc: not found]

[Daniel van Vugt]

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

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


** Summary changed:

- nvidia-352-updates 352.63-0ubuntu0.14.04.1: nvidia-352-updates kernel module 
failed to build
+ nvidia-352-updates 352.63-0ubuntu0.14.04.1: nvidia-352-updates kernel module 
failed to build [/bin/sh: 1: cc: not found]

** This bug has been marked a duplicate of bug 1501972
   nvidia-346 346.96-0ubuntu0.0.1: nvidia-346 kernel module failed to build 
[/bin/sh: 1: cc: not found]

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

Title:
  nvidia-352-updates 352.63-0ubuntu0.14.04.1: nvidia-352-updates kernel
  module failed to build [/bin/sh: 1: cc: not found]

Status in nvidia-graphics-drivers-352-updates package in Ubuntu:
  New

Bug description:
  This PC stop working after installing pycuda and others devices for it. The 
black screen of death appeared. The driver of nvidia stopped working after it. 
Now my screen can't go 1080p, because of Xserver driver. :)
  Thanks NVidia for screwing everything!
  P.S.: Screwing because i won't say the f-word here.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-352-updates (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-25-generic
  Date: Sat May 14 02:12:02 2016
  InstallationDate: Installed on 2016-03-01 (73 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 352.63-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: nvidia-graphics-drivers-352-updates
  Title: nvidia-352-updates 352.63-0ubuntu0.14.04.1: nvidia-352-updates kernel 
module failed to build
  UpgradeStatus: Upgraded to trusty on 2016-04-16 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352-updates/+bug/1581743/+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 552286] Re: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Failed CC sanity check)

[Daniel van Vugt]

** Also affects: nvidia-graphics-drivers-304 (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  package nvidia-* failed to install/upgrade: nvidia-* kernel module
  failed to build (Failed CC sanity check)

Status in nvidia-graphics-drivers package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-173 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-96 package in Ubuntu:
  Confirmed

Bug description:
  [Problem]
  DKMS fails to build the nvidia driver if the C compiler is broken.

  
  DKMS make.log for nvidia-current-195.36.15 for kernel 2.6.31-20-generic (i686)
  Wed Mar 31 08:24:29 IST 2010

  The C compiler 'cc' does not appear to be able to
  create executables.  Please make sure you have 
  your Linux distribution's gcc and libc development
  packages installed.

  *** Failed CC sanity check. Bailing out! ***

  make: *** [select_makefile] Error 1

  [Original Report]
  Dud Beta upgrade using upgrade-distribution -d

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: nvidia-current 195.36.15-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-18-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Wed Mar 31 08:24:33 2010
  DkmsStatus:
   nvidia-current, 195.36.15: added
   bcmwl, 5.60.48.36+bdcom, 2.6.32-18-generic, i686: installed
   bcmwl, 5.60.48.36+bdcom, 2.6.31-20-generic, i686: installed
  ErrorMessage: nvidia-current kernel module failed to build
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  MachineType: Hewlett-Packard HP Pavilion tx1000 Notebook PC
  PackageVersion: 195.36.15-0ubuntu1
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-18-generic 
root=UUID=eff0c532-eecc-4408-8ad8-b2d4e60fdb8a ro quiet splash
  SourcePackage: nvidia-graphics-drivers
  Title: package nvidia-current 195.36.15-0ubuntu1 failed to install/upgrade: 
nvidia-current kernel module failed to build
  dmi.bios.date: 02/25/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1E
  dmi.board.name: 30BF
  dmi.board.vendor: Quanta
  dmi.board.version: 69.2C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1E:bd02/25/2008:svnHewlett-Packard:pnHPPaviliontx1000NotebookPC:pvrRev1:rvnQuanta:rn30BF:rvr69.2C:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion tx1000 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  system:
   distro: Ubuntu
   codename:   lucid
   architecture:   i686
   kernel: 2.6.32-18-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/552286/+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 1581742] Re: nvidia-304 304.131-0ubuntu0.14.04.1: nvidia-304 kernel module failed to build [The C compiler 'cc' does not appear to be able to create executables.]

[Daniel van Vugt]

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

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


** Summary changed:

- nvidia-304 304.131-0ubuntu0.14.04.1: nvidia-304 kernel module failed to build
+ nvidia-304 304.131-0ubuntu0.14.04.1: nvidia-304 kernel module failed to build 
[The C compiler 'cc' does not appear to be able to create executables.]

** This bug has been marked a duplicate of bug 552286
   package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to 
build (Failed CC sanity check)

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

Title:
  nvidia-304 304.131-0ubuntu0.14.04.1: nvidia-304 kernel module failed
  to build [The C compiler 'cc' does not appear to be able to create
  executables.]

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

Bug description:
  This PC stop working after installing pycuda and others devices for it. The 
black screen of death appeared. The driver of nvidia stopped working after it. 
Now my screen can't go 1080p, because of Xserver driver. :)
  Thanks NVidia for screwing everything!
  P.S.: Screwing because i won't say the f-word here.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-51.58~14.04.1-generic 3.19.8-ckt13
  Uname: Linux 3.19.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  DKMSKernelVersion: 3.19.0-51-generic
  Date: Sat May 14 01:42:23 2016
  InstallationDate: Installed on 2016-03-01 (73 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageVersion: 304.131-0ubuntu0.14.04.1
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: nvidia-graphics-drivers-304
  Title: nvidia-304 304.131-0ubuntu0.14.04.1: nvidia-304 kernel module failed 
to build
  UpgradeStatus: Upgraded to trusty on 2016-04-16 (27 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1581742/+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 1583410] Re: nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Daniel van Vugt]

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

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


** Summary changed:

- nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build
+ nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build [error: 
too many arguments to function ‘get_user_pages’]

** This bug has been marked a duplicate of bug 1573508
   nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build [error: 
too many arguments to function ‘get_user_pages’]

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

Title:
  nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build
  [error: too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  New

Bug description:
  Crashed with kernel 4.6 to the extent that my OS would not complete
  boot up and would reinitiate boot up again with no result. Removing
  kernel 4.6 for now.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-340 340.96-0ubuntu3
  Uname: Linux 4.5.4-040504-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  DKMSKernelVersion: 4.6.0-040600-generic
  Date: Wed May 18 21:49:17 2016
  DistUpgraded: 2016-04-21 20:34:37,163 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature: 
dkms:nvidia-340:340.96-0ubuntu3:/var/lib/dkms/nvidia-340/340.96/build/os-mlock.c:48:11:
 error: too many arguments to function ‘get_user_pages’
  GraphicsCard: NVIDIA Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2015-12-16 (154 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: ECS A740GM-M
  PackageVersion: 340.96-0ubuntu3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.5.4-040504-generic 
root=UUID=167cbfee-cc52-4cb3-a249-489c0324fa8d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-340
  Title: nvidia-340 340.96-0ubuntu3: nvidia-340 kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (27 days ago)
  dmi.bios.date: 05/07/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080014
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A740GM-M
  dmi.board.vendor: ECS
  dmi.board.version: 7.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: ECS
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080014:bd05/07/2010:svnECS:pnA740GM-M:pvr7.0:rvnECS:rnA740GM-M:rvr7.0:cvnECS:ct3:cvr:
  dmi.product.name: A740GM-M
  dmi.product.version: 7.0
  dmi.sys.vendor: ECS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: 

[Desktop-packages] [Bug 1012658] Re: thunderbird icon disappears from launcher

[Launchpad Bug Tracker]

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

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

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

Title:
  thunderbird icon disappears from launcher

Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  After starting up correctly from the dash, the thunderbird icon
  disappears after a short amount of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: thunderbird 14.0~b1+build2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0
  Uname: Linux 3.4.0-5-generic x86_64
  ApportVersion: 2.2.1-0ubuntu2
  Architecture: amd64
  Date: Wed Jun 13 14:01:26 2012
  SourcePackage: thunderbird
  UpgradeStatus: Upgraded to quantal on 2012-06-11 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1012658/+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 1582034] Re: Eye Of Gnome doesn't refresh automatically the image when it is edited in 16.04

[antonioni]

Link created in Gnome Bugzilla:

https://bugzilla.gnome.org/show_bug.cgi?id=767003

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

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

Title:
  Eye Of Gnome doesn't refresh automatically the image when it is edited
  in 16.04

Status in eog package in Ubuntu:
  New

Bug description:
  When a image is open in EOG and edited in a image editor (for example:
  Gimp), the image in EOG isn't refreshed. I must browse to next or
  previous image to refresh the edited image.

  But, when I do it, the image showed in EOG is the first image in the
  folder. When there is many images in the folder, the work becomes
  terrible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1582034/+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 1539597] Re: nvidia-304 fails to install properly causing unity-control-center to crash

[Erick Brunzell]

This has no longer been an issue since 16.04 final was released so
marking it invalid.

** Changed in: unity-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  nvidia-304 fails to install properly causing unity-control-center to
  crash

Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1540157] Re: Xenial: Mouse pointer disappears after release upgrade

[Andrew Todd]

Perhaps this was marked invalid because of this related bug?

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1568604

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

Title:
  Xenial: Mouse pointer disappears after release upgrade

Status in unity package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After release upgrade from Wily to Xenial, the mouse pointer is
  invisible.

  Reproduce:
  – Install Ubuntu Wily Werewolf desktop from the official Live CD.
  – Upgrade to Xenial Xerus with „do-release-upgrade -d”.

  Only had a chance to test it on KVM virtual machine, but it happened every 
time I upgraded a virtual machine to Xenial.
  Also, only tested via Wily -> Xenial upgrade, haven't tried Trusty -> Xenial.

  Nature Xenial install from the Xenial Live CD daily build right away
  doesn't have this issue, so I assume something goes wrong during the
  upgrade process.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20151218-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jan 31 22:45:19 2016
  DistUpgraded: 2016-01-31 21:18:14,758 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic 
root=/dev/mapper/wvg-root ro
  Renderer: Software
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-01-31 (0 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-vivid
  dmi.sys.vendor: QEMU
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  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.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sun Jan 31 22:44:03 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 9
   inputspice vdagent tablet TOUCHSCREEN, id 10
  xserver.errors:
   systemd-logind: failed to get session: PID 700 does not belong to any known 
session
   AIGLX: reverting to software rendering
   qxl(0): EXECBUFFER failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   Virtual-0   
Virtual-1   Virtual-2   Virtual-3
  xserver.version: 2:1.17.3-2ubuntu2
  xserver.video_driver: qxl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1540157/+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 1586835] Re: ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04

[Jean-Pierre Rupp]

I have located a way to disable ssh-agent by commenting out the use-ssh-
agent line from file "/etc/X11/Xsession.options". But even after doing
this it is not guaranteed that the $SSH_AUTH_SOCK variable will be set
when I open a new terminal, even while doing so several minutes after I
have logged into my GNOME session, presumably when all session programs
are running. Sometimes I open a terminal and see that $SSH_AUTH_SOCK is
set, then close it and open a new one a few minutes later, and there is
no $SSH_AUTH_SOCK anymore.

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

Title:
  ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Sometimes I open a terminal and try to login to a remote server, just
  to be greeted by a command-line-based prompt asking for my password.
  Whenever that happens, it is ssh-agent instead of gnome-keyring that
  is providing the SSH agent capabilities:

  $ echo $SSH_AUTH_SOCK 
  /tmp/ssh-qeG7CTbx4w7D/agent.4592
  $ ps -p 4592 -f
  UIDPID  PPID  C STIME TTY  TIME CMD
  xeno  4592  4576  0 20:53 tty3 00:00:00 
/usr/lib/gnome-session/gnome-session-binary --session=gnome
  $ ps -p $SSH_AGENT_PID -f
  UIDPID  PPID  C STIME TTY  TIME CMD
  xeno  4652  4592  0 20:53 ?00:00:00 /usr/bin/ssh-agent 
/usr/bin/im-launch gnome-session --session=gnome

  I usually close the GNOME Terminal and open a new one (sometimes I
  must do this more than once), and I eventually get the expected
  output:

  $ echo $SSH_AUTH_SOCK 
  /run/user/1000/keyring/ssh
  $ ps -p $SSH_AGENT_PID -f
  UIDPID  PPID  C STIME TTY  TIME CMD
  xeno  4652  4592  0 20:53 ?00:00:00 /usr/bin/ssh-agent 
/usr/bin/im-launch gnome-session --session=gnome

  Interestingly, the $SSH_AGENT_PID variable seems to continue pointing
  to the process where ssh-agent is running.

  Generally once I get the keyring socket in the $SSH_AUTH_SOCK
  environment variable, it will stay that way even when I close the
  terminal and launch a new one.

  This seems to be a weird conflict between two programs offering the
  ssh-agent service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1586835/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Chris Allen]

Same issue here. I have an Asus X540LA laptop with the same chipset and
the headset mic doesn't work.

[1.576056] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[1.612215] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[1.612220] snd_hda_codec_realtek hdaudioC1D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[1.612224] snd_hda_codec_realtek hdaudioC1D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[1.612226] snd_hda_codec_realtek hdaudioC1D0:mono: mono_out=0x0
[1.612228] snd_hda_codec_realtek hdaudioC1D0:inputs:
[1.612231] snd_hda_codec_realtek hdaudioC1D0:  Mic=0x1b

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

[Jason C Daniels]

I'm getting DOS'd about 20 times a day as a result of this issue.

Could a "band-aid" shell script be whipped up by anyone in the know, to
physically purge the expired lease files periodically, and posted here?

I would gladly set such a script to run as a "cleanup service" or even
run it manually, while the proper fix is implemented.

Thanks,
Jason

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1533631/+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 1540157] Re: Xenial: Mouse pointer disappears after release upgrade

[Andrew Todd]

I should add I am also using xserver-xorg-video-intel if there's a
belief of a connection.

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

Title:
  Xenial: Mouse pointer disappears after release upgrade

Status in unity package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After release upgrade from Wily to Xenial, the mouse pointer is
  invisible.

  Reproduce:
  – Install Ubuntu Wily Werewolf desktop from the official Live CD.
  – Upgrade to Xenial Xerus with „do-release-upgrade -d”.

  Only had a chance to test it on KVM virtual machine, but it happened every 
time I upgraded a virtual machine to Xenial.
  Also, only tested via Wily -> Xenial upgrade, haven't tried Trusty -> Xenial.

  Nature Xenial install from the Xenial Live CD daily build right away
  doesn't have this issue, so I assume something goes wrong during the
  upgrade process.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20151218-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jan 31 22:45:19 2016
  DistUpgraded: 2016-01-31 21:18:14,758 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic 
root=/dev/mapper/wvg-root ro
  Renderer: Software
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-01-31 (0 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-vivid
  dmi.sys.vendor: QEMU
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  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.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sun Jan 31 22:44:03 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 9
   inputspice vdagent tablet TOUCHSCREEN, id 10
  xserver.errors:
   systemd-logind: failed to get session: PID 700 does not belong to any known 
session
   AIGLX: reverting to software rendering
   qxl(0): EXECBUFFER failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   Virtual-0   
Virtual-1   Virtual-2   Virtual-3
  xserver.version: 2:1.17.3-2ubuntu2
  xserver.video_driver: qxl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1540157/+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 1540157] Re: Xenial: Mouse pointer disappears after release upgrade

[Andrew Todd]

Agreed, this is not invalid -- I just experienced this same problem
after upgrade to Lubuntu Xenial from Wily, and although intermittent, it
is very real. Logging out seems to solve the issue, at least
temporarily.

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

Title:
  Xenial: Mouse pointer disappears after release upgrade

Status in unity package in Ubuntu:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  After release upgrade from Wily to Xenial, the mouse pointer is
  invisible.

  Reproduce:
  – Install Ubuntu Wily Werewolf desktop from the official Live CD.
  – Upgrade to Xenial Xerus with „do-release-upgrade -d”.

  Only had a chance to test it on KVM virtual machine, but it happened every 
time I upgraded a virtual machine to Xenial.
  Also, only tested via Wily -> Xenial upgrade, haven't tried Trusty -> Xenial.

  Nature Xenial install from the Xenial Live CD daily build right away
  doesn't have this issue, so I assume something goes wrong during the
  upgrade process.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20151218-0ubuntu2
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jan 31 22:45:19 2016
  DistUpgraded: 2016-01-31 21:18:14,758 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2016-01-31 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.3.0-7-generic 
root=/dev/mapper/wvg-root ro
  Renderer: Software
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-01-31 (0 days ago)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-vivid
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-vivid:cvnQEMU:ct1:cvrpc-i440fx-vivid:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-vivid
  dmi.sys.vendor: QEMU
  version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.66-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
  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.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151217-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Sun Jan 31 22:44:03 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputAT Translated Set 2 keyboard KEYBOARD, id 7
   inputVirtualPS/2 VMware VMMouse MOUSE, id 8
   inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 9
   inputspice vdagent tablet TOUCHSCREEN, id 10
  xserver.errors:
   systemd-logind: failed to get session: PID 700 does not belong to any known 
session
   AIGLX: reverting to software rendering
   qxl(0): EXECBUFFER failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output   Virtual-0   
Virtual-1   Virtual-2   Virtual-3
  xserver.version: 2:1.17.3-2ubuntu2
  xserver.video_driver: qxl

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1540157/+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 1290217] Re: The overwriting error message was: Key file does not have group 'connectivity'

[Eric Wright]

I can confirm that sfbanjo's solution worked for me.

sfbanjo (sfbanjo) wrote on 2016-02-03:  #22
The solution is here:

http://askubuntu.com/a/727462

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

Title:
  The overwriting error message was: Key file does not have group
  'connectivity'

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Looking at /var/log/upstart/network-manager.log, that error is
  written:

  
  (NetworkManager:969): GLib-WARNING **: GError set over the top of a previous 
GError or uninitialized memory.
  This indicates a bug in someone's code. You must ensure an error is NULL 
before it's set.
  The overwriting error message was: Key file does not have group 'connectivity'

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5
  Uname: Linux 3.13.0-16-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Mar 10 07:02:37 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-25 (135 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1)
  IpRoute:
   default via 192.168.1.1 dev eth0  proto static 
   192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.3  metric 1
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
   
   eth1  no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2013-12-25T13:58:11.169010
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 17cca4ae1-9b74-45ac-bc15-7b1757516613   
802-3-ethernet1394431189   Mon 10 Mar 2014 06:59:49 CET   yes   
no /org/freedesktop/NetworkManager/Settings/1
   Connexion filaire 2   2f951ef2-14cf-4fb5-a89a-b83bdae4731d   
802-3-ethernet1389770221   Wed 15 Jan 2014 08:17:01 CET   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth1   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1290217/+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 1586835] [NEW] ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04

[Jean-Pierre Rupp]

Public bug reported:

Sometimes I open a terminal and try to login to a remote server, just to
be greeted by a command-line-based prompt asking for my password.
Whenever that happens, it is ssh-agent instead of gnome-keyring that is
providing the SSH agent capabilities:

$ echo $SSH_AUTH_SOCK 
/tmp/ssh-qeG7CTbx4w7D/agent.4592
$ ps -p 4592 -f
UIDPID  PPID  C STIME TTY  TIME CMD
xeno  4592  4576  0 20:53 tty3 00:00:00 
/usr/lib/gnome-session/gnome-session-binary --session=gnome
$ ps -p $SSH_AGENT_PID -f
UIDPID  PPID  C STIME TTY  TIME CMD
xeno  4652  4592  0 20:53 ?00:00:00 /usr/bin/ssh-agent 
/usr/bin/im-launch gnome-session --session=gnome

I usually close the GNOME Terminal and open a new one (sometimes I must
do this more than once), and I eventually get the expected output:

$ echo $SSH_AUTH_SOCK 
/run/user/1000/keyring/ssh
$ ps -p $SSH_AGENT_PID -f
UIDPID  PPID  C STIME TTY  TIME CMD
xeno  4652  4592  0 20:53 ?00:00:00 /usr/bin/ssh-agent 
/usr/bin/im-launch gnome-session --session=gnome

Interestingly, the $SSH_AGENT_PID variable seems to continue pointing to
the process where ssh-agent is running.

Generally once I get the keyring socket in the $SSH_AUTH_SOCK
environment variable, it will stay that way even when I close the
terminal and launch a new one.

This seems to be a weird conflict between two programs offering the ssh-
agent service.

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

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

Title:
  ssh-agent fighting gnome-keyring on Ubuntu Gnome 16.04

Status in gnome-keyring package in Ubuntu:
  New

Bug description:
  Sometimes I open a terminal and try to login to a remote server, just
  to be greeted by a command-line-based prompt asking for my password.
  Whenever that happens, it is ssh-agent instead of gnome-keyring that
  is providing the SSH agent capabilities:

  $ echo $SSH_AUTH_SOCK 
  /tmp/ssh-qeG7CTbx4w7D/agent.4592
  $ ps -p 4592 -f
  UIDPID  PPID  C STIME TTY  TIME CMD
  xeno  4592  4576  0 20:53 tty3 00:00:00 
/usr/lib/gnome-session/gnome-session-binary --session=gnome
  $ ps -p $SSH_AGENT_PID -f
  UIDPID  PPID  C STIME TTY  TIME CMD
  xeno  4652  4592  0 20:53 ?00:00:00 /usr/bin/ssh-agent 
/usr/bin/im-launch gnome-session --session=gnome

  I usually close the GNOME Terminal and open a new one (sometimes I
  must do this more than once), and I eventually get the expected
  output:

  $ echo $SSH_AUTH_SOCK 
  /run/user/1000/keyring/ssh
  $ ps -p $SSH_AGENT_PID -f
  UIDPID  PPID  C STIME TTY  TIME CMD
  xeno  4652  4592  0 20:53 ?00:00:00 /usr/bin/ssh-agent 
/usr/bin/im-launch gnome-session --session=gnome

  Interestingly, the $SSH_AGENT_PID variable seems to continue pointing
  to the process where ssh-agent is running.

  Generally once I get the keyring socket in the $SSH_AUTH_SOCK
  environment variable, it will stay that way even when I close the
  terminal and launch a new one.

  This seems to be a weird conflict between two programs offering the
  ssh-agent service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1586835/+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 363108] Re: The first IM message from a buddy does not launch a notification bubble

[Ubuntu Foundations Team Bug Bot]

The attachment "first-message-regression.diff" seems to be a patch.  If
it isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

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

** Tags added: patch

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

Title:
  The first IM message from a buddy does not launch a notification
  bubble

Status in notify-osd package in Ubuntu:
  Invalid
Status in pidgin-libnotify package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pidgin

  The first IM message from a buddy (i.e. the message which starts a new
  conversation) does not launch a notify-OSD notification bubble.
  However, the subsequent messages correctly triggers notifications.
  This is annoying, illogical and incoherent.

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

[Anton Eliasson]

I tried installing Gnome Color Manager as well, and while colord no
longer seems to crash on every boot, it still sometimes crashes after
waking from suspend on the same failed assertion.

-- 
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 1586826] [NEW] VPN authentication steals focus on login screen.

[mark johnson]

Public bug reported:

Steps to reproduce:
Set up a VPN connection in network manager using password authentication, and 
store the password.
Set up a Wireless network to connect automaticall, and to automatically connect 
to the configured VPN.
Confirm that the network and VPN connect without prompting you for the password.
Log out or reboot to the login screen.
Wait for the wireless network to connect.  The VPN authentication dialog 
appears, and prevents you from typing in the login form.  The dialogue can be 
cancelled, but it reappears shortly after, making it difficult to log in.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun May 29 20:38:50 2016
EcryptfsInUse: Yes
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-08-31 (272 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-04-22 (36 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-09-02T20:13:30.618545
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 tun0tun   connected  /org/freedesktop/NetworkManager/Devices/2  tun0   
 1d00cd2d-9244-4385-a7b6-0272cd616049  
/org/freedesktop/NetworkManager/ActiveConnection/10 
 wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  MJ_JF  
 bfecb4ab-406c-4cd1-bcdf-913b4973f119  
/org/freedesktop/NetworkManager/ActiveConnection/8  
 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 xenial

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

Title:
  VPN authentication steals focus on login screen.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  Set up a VPN connection in network manager using password authentication, and 
store the password.
  Set up a Wireless network to connect automaticall, and to automatically 
connect to the configured VPN.
  Confirm that the network and VPN connect without prompting you for the 
password.
  Log out or reboot to the login screen.
  Wait for the wireless network to connect.  The VPN authentication dialog 
appears, and prevents you from typing in the login form.  The dialogue can be 
cancelled, but it reappears shortly after, making it difficult to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 29 20:38:50 2016
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-08-31 (272 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (36 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-09-02T20:13:30.618545
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   tun0tun   connected  /org/freedesktop/NetworkManager/Devices/2  tun0 
   1d00cd2d-9244-4385-a7b6-0272cd616049  
/org/freedesktop/NetworkManager/ActiveConnection/10 
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/0  
MJ_JF   bfecb4ab-406c-4cd1-bcdf-913b4973f119  
/org/freedesktop/NetworkManager/ActiveConnection/8  
   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:

[Desktop-packages] [Bug 1586824] [NEW] gvfs-afc does not mount the normal volume

[Rosen Penev]

Public bug reported:

The offending commit is this:
https://git.gnome.org/browse/gvfs/commit/?id=0b68656de4cca842aa9170a62b6b4884a05f6705

Can you guys revert it? The commit is somewhat useful for newer devices
but completely worthless for old ones.

On 16.04. 1.27 does not have the problem. 1.28 does.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gvfs-common 1.28.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun May 29 12:33:00 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-05-03 (26 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  gvfs-afc does not mount the normal volume

Status in gvfs package in Ubuntu:
  New

Bug description:
  The offending commit is this:
  
https://git.gnome.org/browse/gvfs/commit/?id=0b68656de4cca842aa9170a62b6b4884a05f6705

  Can you guys revert it? The commit is somewhat useful for newer
  devices but completely worthless for old ones.

  On 16.04. 1.27 does not have the problem. 1.28 does.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gvfs-common 1.28.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun May 29 12:33:00 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-03 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1586824/+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 1586822] [NEW] Ability to set default save destination for new bookmarks

[Nikita Yerenkov-Scott]

Public bug reported:

Though I can understand the rationale for making all new bookmarks go
into an "Unsorted Bookmarks" area, I think that it would be good if
Firefox provided an option to allow the user to change the default save
location for new bookmarks, because I for one don't want to have to move
every new bookmark I make to the "Bookmarks Toolbar", I would like to be
able to have them just go there automatically, but I can't currently so
it would be good if there were an option to change the default save
location of bookmarks.

** Affects: firefox
 Importance: Unknown
 Status: Unknown

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


** Tags: xenial

** Summary changed:

- Ability to set default destination for new bookmarks
+ Ability to set default save destination for new bookmarks

** Bug watch added: Mozilla Bugzilla #1276519
   https://bugzilla.mozilla.org/show_bug.cgi?id=1276519

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1276519
   Importance: Unknown
   Status: Unknown

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

Title:
  Ability to set default save destination for new bookmarks

Status in Mozilla Firefox:
  Unknown
Status in firefox package in Ubuntu:
  New

Bug description:
  Though I can understand the rationale for making all new bookmarks go
  into an "Unsorted Bookmarks" area, I think that it would be good if
  Firefox provided an option to allow the user to change the default
  save location for new bookmarks, because I for one don't want to have
  to move every new bookmark I make to the "Bookmarks Toolbar", I would
  like to be able to have them just go there automatically, but I can't
  currently so it would be good if there were an option to change the
  default save location of bookmarks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1586822/+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 1586820] [NEW] cc

[Bruno]

Public bug reported:

hhfd

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Sun May 29 20:44:44 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation Trinity [Radeon HD 7480D] [1849:9993]
InstallationDate: Installed on 2016-02-11 (108 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=es_ES
 PATH=(custom, no user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=7c6fe621-bcf7-4dc7-9655-fd6cd9050be9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.00
dmi.board.name: FM2A58M-VG3+ R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd05/11/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A58M-VG3+R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun May 29 13:12:18 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: radeon

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


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

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

Title:
  cc

Status in xorg package in Ubuntu:
  New

Bug description:
  hhfd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Sun May 29 20:44:44 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Trinity [Radeon HD 7480D] [1849:9993]
  InstallationDate: Installed on 2016-02-11 (108 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=7c6fe621-bcf7-4dc7-9655-fd6cd9050be9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.00
  dmi.board.name: FM2A58M-VG3+ R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled 

[Desktop-packages] [Bug 1483276] Re: Unable to launch xdiagnose through the Activities Overview in the normal way

[Nikita Yerenkov-Scott]

I still experience this issue with Ubuntu GNOME 16.04 with GNOME 3.20.

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

Title:
  Unable to launch xdiagnose through the Activities Overview in the
  normal way

Status in gnome-shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in xdiagnose package in Ubuntu:
  Confirmed

Bug description:
  I am in need of doing some diagnostics work with "xdiagnose", however
  when searching for it in the Activities Overview, and then clicking on
  it, absolutely nothing happens, when in the past it would ask me for
  my password so that I could run it as root.

  I looked further into the issue and when trying to run it through
  Terminal:

  xdiagnose

  This was the output I got:

  Error: Must run as superuser

  But when running it in Terminal like so:

  pkexec xdiagnose

  It prompted for the password as it normally would and should (so
  pkexec is not the issue).

  There was also no output from the command:

  grep -r 'xdiagnose' ~/.local/share/applications

  And the output of this command "grep -r 'xdiagnose'
  /usr/share/applications" was:

  /usr/share/applications/xdiagnose.desktop:Name=xdiagnose
  /usr/share/applications/xdiagnose.desktop:Exec=pkexec xdiagnose
  
/usr/share/applications/xdiagnose.desktop:Icon=/usr/share/xdiagnose/icons/microscope.svg
  
/usr/share/applications/xdiagnose.desktop:X-Ubuntu-Gettext-Domain=xdiagnose

  The contents of the file is this:

  [Desktop Entry]
  Name=xdiagnose
  GenericName=Diagnose Graphics Issues
  Comment=X.org Diagnostic and Repair Utility
  Exec=pkexec xdiagnose
  Icon=/usr/share/xdiagnose/icons/microscope.svg
  Terminal=false
  Type=Application
  Categories=System;Settings;
  X-Ubuntu-Gettext-Domain=xdiagnose

  I have reinstalled it with "sudo apt-get install --reinstall
  xdiagnose", however this seems to have made no difference at all to
  anything.

  I have also attempted to launch another application via the Activities
  Overview that uses 'pkexec' to start, and it works fine as normal.

  I initially experienced this issue on Ubuntu GNOME 15.04 with GNOME
  3.16, then on Ubuntu GNOME 15.10 with GNOME 3.18, and now on Ubuntu
  GNOME 16.04 with GNOME 3.20. Though I remember a time when this issue
  wasn't present (probably when I was running Ubuntu GNOME 15.04 with
  GNOME 3.14).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1483276/+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 1483276] Re: Unable to launch xdiagnose through the Activities Overview in the normal way

[Nikita Yerenkov-Scott]

I still experience this issue with Ubutnu GNOME 16.04 with GNOME 3.20.

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

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

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

** Description changed:

  I am in need of doing some diagnostics work with "xdiagnose", however
  when searching for it in the Activities Overview, and then clicking on
  it, absolutely nothing happens, when in the past it would ask me for my
  password so that I could run it as root.
  
  I looked further into the issue and when trying to run it through
  Terminal:
  
  xdiagnose
  
  This was the output I got:
  
  Error: Must run as superuser
  
  But when running it in Terminal like so:
  
  pkexec xdiagnose
  
  It prompted for the password as it normally would and should (so pkexec
  is not the issue).
  
  There was also no output from the command:
  
  grep -r 'xdiagnose' ~/.local/share/applications
  
  And the output of this command "grep -r 'xdiagnose'
  /usr/share/applications" was:
  
  /usr/share/applications/xdiagnose.desktop:Name=xdiagnose
  /usr/share/applications/xdiagnose.desktop:Exec=pkexec xdiagnose
  
/usr/share/applications/xdiagnose.desktop:Icon=/usr/share/xdiagnose/icons/microscope.svg
  
/usr/share/applications/xdiagnose.desktop:X-Ubuntu-Gettext-Domain=xdiagnose
  
  The contents of the file is this:
  
  [Desktop Entry]
  Name=xdiagnose
  GenericName=Diagnose Graphics Issues
  Comment=X.org Diagnostic and Repair Utility
  Exec=pkexec xdiagnose
  Icon=/usr/share/xdiagnose/icons/microscope.svg
  Terminal=false
  Type=Application
  Categories=System;Settings;
  X-Ubuntu-Gettext-Domain=xdiagnose
  
  I have reinstalled it with "sudo apt-get install --reinstall xdiagnose",
  however this seems to have made no difference at all to anything.
  
  I have also attempted to launch another application via the Activities
  Overview that uses 'pkexec' to start, and it works fine as normal.
  
  I initially experienced this issue on Ubuntu GNOME 15.04 with GNOME
  3.16, then on Ubuntu GNOME 15.10 with GNOME 3.18, and now on Ubuntu
- GNOME 16.04 with GNOME 3.19. Though I remember a time when this issue
+ GNOME 16.04 with GNOME 3.20. Though I remember a time when this issue
  wasn't present (probably when I was running Ubuntu GNOME 15.04 with
  GNOME 3.14).

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

Title:
  Unable to launch xdiagnose through the Activities Overview in the
  normal way

Status in gnome-shell:
  Confirmed
Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in xdiagnose package in Ubuntu:
  Confirmed

Bug description:
  I am in need of doing some diagnostics work with "xdiagnose", however
  when searching for it in the Activities Overview, and then clicking on
  it, absolutely nothing happens, when in the past it would ask me for
  my password so that I could run it as root.

  I looked further into the issue and when trying to run it through
  Terminal:

  xdiagnose

  This was the output I got:

  Error: Must run as superuser

  But when running it in Terminal like so:

  pkexec xdiagnose

  It prompted for the password as it normally would and should (so
  pkexec is not the issue).

  There was also no output from the command:

  grep -r 'xdiagnose' ~/.local/share/applications

  And the output of this command "grep -r 'xdiagnose'
  /usr/share/applications" was:

  /usr/share/applications/xdiagnose.desktop:Name=xdiagnose
  /usr/share/applications/xdiagnose.desktop:Exec=pkexec xdiagnose
  
/usr/share/applications/xdiagnose.desktop:Icon=/usr/share/xdiagnose/icons/microscope.svg
  
/usr/share/applications/xdiagnose.desktop:X-Ubuntu-Gettext-Domain=xdiagnose

  The contents of the file is this:

  [Desktop Entry]
  Name=xdiagnose
  GenericName=Diagnose Graphics Issues
  Comment=X.org Diagnostic and Repair Utility
  Exec=pkexec xdiagnose
  Icon=/usr/share/xdiagnose/icons/microscope.svg
  Terminal=false
  Type=Application
  Categories=System;Settings;
  X-Ubuntu-Gettext-Domain=xdiagnose

  I have reinstalled it with "sudo apt-get install --reinstall
  xdiagnose", however this seems to have made no difference at all to
  anything.

  I have also attempted to launch another application via the Activities
  Overview that uses 'pkexec' to start, and it works fine as normal.

  I initially experienced this issue on Ubuntu GNOME 15.04 with GNOME
  3.16, then on Ubuntu GNOME 15.10 with GNOME 3.18, and now on Ubuntu
  GNOME 16.04 with GNOME 3.20. Though I remember a time when this issue
  wasn't present (probably when I was running Ubuntu GNOME 15.04 with
  GNOME 3.14).

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1586813] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: Trigger bilden eine Schleife, aufgegeben

[Ady Ayala]

Public bug reported:

when trying to upgrade from ubuntu 15.10 to ubuntu 16.04

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: hicolor-icon-theme 0.15-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
Uname: Linux 4.2.0-36-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
Date: Sun May 29 20:12:39 2016
Dependencies:
 
DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:Trigger bilden 
eine Schleife, aufgegeben
ErrorMessage: Trigger bilden eine Schleife, aufgegeben
InstallationDate: Installed on 2014-06-10 (718 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: hicolor-icon-theme
Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: hicolor-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade:
  Trigger bilden eine Schleife, aufgegeben

Status in hicolor-icon-theme package in Ubuntu:
  New

Bug description:
  when trying to upgrade from ubuntu 15.10 to ubuntu 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: hicolor-icon-theme 0.15-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
  Uname: Linux 4.2.0-36-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  Date: Sun May 29 20:12:39 2016
  Dependencies:
   
  DuplicateSignature: package:hicolor-icon-theme:0.15-0ubuntu1:Trigger bilden 
eine Schleife, aufgegeben
  ErrorMessage: Trigger bilden eine Schleife, aufgegeben
  InstallationDate: Installed on 2014-06-10 (718 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 
(20130820.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: 
Trigger bilden eine Schleife, aufgegeben
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1586813/+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 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

[Uqbar]

I choose to get just the IP address and set my own DNS servers.
I expect to see those addresses appear somewhere, usually /etc/resolve.conf, 
the standard resolver configuration file.

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

Title:
  NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Setup a network with DHCP address, gateway and DNS.
  2. Connect to that network.
  3. Check the resolver configured in /etc/resolv.conf

  Expected result:
  To find "nameserver" set to the DNS addresses provided by the external DHCP 
server

  Actual result:
  "nameserver=127.0.1.1" in any case.

  This related to https://bugs.launchpad.net/bugs/1577720

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  3 12:42:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e9840ddc04  proto static  metric 600 
   169.254.0.0/16 dev wlxc4e9840ddc04  scope link  metric 1000 
   192.168.1.0/24 dev wlxc4e9840ddc04  proto kernel  scope link  src 
192.168.1.95  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlxc4e9840ddc04wifi  connected 
/org/freedesktop/NetworkManager/Devices/0  SIGKILL 
2986445c-d935-4b58-b3ca-da614dd4  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   C0:EE:FB:44:15:8A  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   enp3s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  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/1577724/+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 1549455] Re: Unity8-dash on Intel Atom graphics crashes and restarts continuously [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) == EGL_TRUE"]

[Emanuele Antonio Faraone]

@Gerry, have you tested it on pineview hardware?

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

Title:
  Unity8-dash on Intel Atom graphics crashes and restarts continuously
  [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, EglContext) ==
  EGL_TRUE"]

Status in Mir:
  Invalid
Status in qtubuntu:
  In Progress
Status in mesa package in Ubuntu:
  Invalid
Status in mir package in Ubuntu:
  Invalid
Status in qtdeclarative package in Ubuntu:
  Confirmed
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Qt clients are failing to create an egl context when running on Intel
  Pineview systems under Mir.

  eglCreateContext fails with a EGL_BAD_MATCH error code.

  When it fails, Qt tries to delete & recreate the context, which then
  crashes the client (bug 1580118)

  
  === Original bug description ===
  This bug Makes the pc UNUSABLE
  when I try to launch Unity 8 and Mir, after writing the password on the login 
(in the image attached) the bar to enter the password disappears and my 
computer screen stays stuck without them let me do anything. the connection 
begins to separate and reattach alone and I can only move the cursor. it makes 
the computer unusable and I am forced to restart forced to then enter into 
Unity 7. represented in the screenshot is the lock status after entering the 
password.
  Version: unity8.12+16.04.201604.01.1
  Version of Mir : 0.21

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1549455/+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 363108] Re: The first IM message from a buddy does not launch a notification bubble

[Robert Hollencamp]

this issue was introduced in ubuntu_notify_support.patch. find attached
a patch to fix this regression

** Patch added: "first-message-regression.diff"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/363108/+attachment/4672378/+files/first-message-regression.diff

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

Title:
  The first IM message from a buddy does not launch a notification
  bubble

Status in notify-osd package in Ubuntu:
  Invalid
Status in pidgin-libnotify package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pidgin

  The first IM message from a buddy (i.e. the message which starts a new
  conversation) does not launch a notify-OSD notification bubble.
  However, the subsequent messages correctly triggers notifications.
  This is annoying, illogical and incoherent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/363108/+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 1584538] Re: locales are missing - menu entries and messages only in English

[H.-Dirk Schmitt]

The version released to xenial-proposed is fixing the issue

evolution (3.18.5.2-0ubuntu3) xenial; urgency=medium

  * debian/control: 
- remove the X-Ubuntu-Use-Langpack line rather than commenting it
  due pkgstriptranslations not understanding the # (being fixed, 
  but meanwhile let's get that SRU working)

 -- Sebastien Bacher   Wed, 25 May 2016 08:19:06
+0200


** Changed in: evolution (Ubuntu)
   Status: New => Fix Released

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

Title:
  locales are missing - menu entries and messages only in English

Status in evolution package in Ubuntu:
  Fix Released

Bug description:
  The UI is in English and not localized as the rest (here in german).
  So it is hard to understand for users without Englisch language capabilities.

  The localization is missing in evolution-common.
  e.g. the file /usr/share/locale/de/LC_MESSAGES/evolution-3.18.mo

  The debian version in stretch contain this file.
  Comparing the file size of the packages between debian and ubuntu show also 
that a huge part of files are missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: evolution-common 3.18.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 22 23:23:11 2016
  PackageArchitecture: all
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1584538/+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 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume

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

Title:
  Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on
  resume

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  dmesg shows issues with being able to use the discrete graphics card
  (relevant dmesg lines attached).

  Grub does pass "radeon.modeset=1" but it doesn't seem to make a
  difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to
  the kernel, then it does not error (except for the VCE error -110,
  which is probably harmless).

  Running `DRI_PRIME=1 glxgears`:
  - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black 
window with a visible top bar.
  - with just "radeon.modeset=1", error (attached as 'glxgears').

  Results are similar on Ubuntu GNOME 16.04, except with
  "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of
  screen tearing.

  Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be
  attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR:

  [   22.916285] [drm] ring test on 0 succeeded in 2 usecs
  [   22.916289] [drm] ring test on 1 succeeded in 1 usecs
  [   22.916292] [drm] ring test on 2 succeeded in 1 usecs
  [   22.916299] [drm] ring test on 3 succeeded in 3 usecs
  [   22.916304] [drm] ring test on 4 succeeded in 3 usecs
  [   23.092271] [drm] ring test on 5 succeeded in 2 usecs
  [   23.092276] [drm] UVD initialized successfully.
  [   23.092311] [drm] ib test on ring 0 succeeded in 0 usecs
  [   23.092349] [drm] ib test on ring 1 succeeded in 0 usecs
  [   23.092375] [drm] ib test on ring 2 succeeded in 0 usecs
  [   23.092392] [drm] ib test on ring 3 succeeded in 0 usecs
  [   23.092407] [drm] ib test on ring 4 succeeded in 0 usecs
  [   33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait 
failed (-35).
  [   33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed 
testing IB on ring 5 (-35).

  lsb_release -rd:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu May 12 20:43:03 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0e6]
     Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] 
[144d:c0e6]
  InstallationDate: Installed on 2016-05-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P05ADH.017.140421.SH
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP680Z5E-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 870Z5E/880Z5E/680Z5E
  dmi.product.version: P05ADH
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Desktop-packages] [Bug 1582687] Re: workbench crashes metacity on ubuntu 16.04

[Dmitry Shachnev]

Oops, I just got my LibreOffice crash again with the new Metacity :(

So maybe my bug was actually different (though similar). Attaching the
full stacktrace (with --sync enabled).

** Attachment added: "stacktrace.txt"
   
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+attachment/4672363/+files/stacktrace.txt

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

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+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 1508718] Re: NetworkManager - error initialzing editor

[Prahlad Yeri]

@Mörgæs - I don't think this issue appears at all in 16.04. Since I
upgraded to 16.04LTS today, this issue has got resolved. I noticed that
the network-manager package was updated too during the upgrade, so the
fix might have come from there.

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

Title:
  NetworkManager - error initialzing editor

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Error initializing editor
  settings/nm-settings-connection.c.995 - Connection didn't have requested 
setting 'ppp'

  Error occurs when attempting to edit existing mobile broadband connection.
  Editing existing Ethernet connections succeeds without error.

  This broke between 1.0.4-0ubuntu3 and 1.0.4-0ubuntu5

  The connection still functions correctly but its properties can no
  longer be edited with gui.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager-gnome 0.9.10.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 23:14:57 2015
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (21 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IpRoute:
   default via 10.109.83.190 dev wwan0  proto static  metric 750 
   10.109.83.188/30 dev wwan0  proto kernel  scope link  src 10.109.83.189  
metric 750 
   169.254.0.0/16 dev wwan0  scope link  metric 1000
  IwConfig:
   wwan0 no wireless extensions.
   
   eno1  no wireless extensions.
   
   lono wireless extensions.
  JournalErrors:
   No journal files were found.
   -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   cdc-wdm0  gsm   connected /org/freedesktop/NetworkManager/Devices/2  
att_stick   d13a7207-c11a-47ad-8876-ee62c3ccb5b2  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   eno1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   loloopback  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-applet/+bug/1508718/+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 1051625] Re: nautilus crashed with signal 5 in _XEventsQueued()

[Helio]

Happened in 16.04 and Nautilus 3.14.3

I don't know if this is important, but my wallpaper is not the default
one.

1. I pressed [ + ] and selected the "show desktop" icon on the window 
switcher.
2. My desktop appeared empty and with the default wallpaper (not the one I 
have).
3. I right-clicked on the middle of the desktop.
4. The desktop went black.
5. I opened Nautilus in a window to see if my files were intact.
6. The desktop flickered and appeared the custom wallpaper and the files.
7. Apport shown its dialog.

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

Title:
  nautilus crashed with signal 5 in _XEventsQueued()

Status in nautilus package in Ubuntu:
  Confirmed
Status in nemo package in Ubuntu:
  Confirmed

Bug description:
  Bug report prompt appeared when printing in Libreoffice Calc. Not sure
  about the actual cause.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.19-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 17 00:02:19 2012
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' 
b"'800x550+478+220'"
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcCmdline: nautilus trash://
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: nautilus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: nautilus crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to quantal on 2012-09-08 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1051625/+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 1572244] Re: Kubuntu 16.04 requires that the wifi password be entered twice before wifi can be used

[Saurav Sengupta]

It asked for the password twice even on a freshly installed system, not
just in a live session.

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

Title:
  Kubuntu 16.04 requires that the wifi password be entered twice before
  wifi can be used

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Kubuntu 16.04 ISO number 20160417.1 Xenial Final
  Bug reported against network-manager 
  Every time I tried the live Kubuntu 16.04 image on a Lenovo t420 laptop it 
requires to enter the wifi password twice before I can use the wifi. Once from 
the network icon panel, then second time a prompt on the desktop to enter the 
wifi password.

  I do not know if this is typical behavior of Kubuntu since I usually use GTK 
base desktops.
  I guess network-manager is the right package to file this report against.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.373
  CurrentDesktop: KDE
  Date: Tue Apr 19 16:48:02 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.77.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.77.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.77.128  
metric 600
  LiveMediaBuild: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
   KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  802-11-wireless  
1461084315  Tue 19 Apr 2016 04:45:15 PM UTC  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/3 
   Wired connection 1  4957fbd0-8ffa-4de8-aa18-275e6dfdcd9e  802-3-ethernet   
1461077415  Tue 19 Apr 2016 02:50:15 PM UTC  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  no  --  --
 --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0   wifi  connected/org/freedesktop/NetworkManager/Devices/0  
KNOPPIX adfb3f1c-39c2-4410-b1dc-ca553326da52  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
--  ----
  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/1572244/+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 1315328] Re: Black icons on dark grey background in right click menu of title bar when using Ambiance theme

[Paul White]

** Package changed: ubuntu => light-themes (Ubuntu)

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

Title:
  Black icons on dark grey background in right click menu of title bar
  when using Ambiance theme

Status in light-themes package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 14.04 LTS.
  I am using the default Ubuntu Ambiance theme.
  I enabled "menus-have-icons" in dconf-editor under 
"org.gnome.desktop.interface" so that menu icons are shown.
  When I right click the title bar of a window, the icons (for Minimize, 
Maximize and Close) are black on a dark grey background, so they are not very 
visible. I suppose they should be light grey instead, as is the menu text.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1315328/+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 1012211] Re: NetworkManager mishandles multiple interfaces on same subnet

[Launchpad Bug Tracker]

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

** Changed in: network-manager (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/1012211

Title:
  NetworkManager mishandles multiple interfaces on same subnet

Status in Linux Mint:
  New
Status in network-manager package in Ubuntu:
  New
Status in Debian:
  New
Status in Fedora:
  Unknown

Bug description:
  1) The version and edition of Linux Mint you are using (if you are not
  sure, open a terminal and run "mintwelcome").

  Release: 1 (debian)
  Edition: Debian 64-bit

  2) What you did for the problem to happen, and how to reproduce it.

  In NetworkManager, I configured both wired and wireless network
  interfaces to connect to the same network. I set both interfaces to
  "Off" in NetworkManager. I then turned on and connected the wireless
  interface. After the wireless interface was connected, I turned on and
  connected the wired interface.

  3) What happened.

  When only the wireless network was connected, both the local subnet
  route and default route went over the wireless connect, the only one
  available. Upon connection of the wired interface, NetworkManager
  properly prioritizes the wired interface for the default route, but
  left the wireless network prioritized for the local subnet route. Here
  is an example of the improper routing table, notice that the route for
  wlan0 appears above the route for eth0:

  default via 192.168.77.254 dev eth0  proto static 
  192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 
  192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 

  This is due to the order of the routes in the routing table that
  results from the order that the network connects were enabled. If the
  order of connection is reversed, so are the local subnet routes,
  correcting the issue.

  4) What you expected to happen instead.

  I expected the wired network to be prioritized for both the default
  route and local subnet route, producing a routing table something like
  this:

  default via 192.168.77.254 dev eth0  proto static 
  192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 metric 
1
  192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 metric 0

  5) If the problem happened once, sometimes, or always.

  This problem always happens. At some point in the past the network
  routes were handled properly, producing a routing table that looked
  like this:

  default via 192.168.77.254 dev wlan0  proto static metric 1
  default via 192.168.77.254 dev eth0  proto static metric 0
  192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 metric 
1
  192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 metric 0

  6) Possible relevant reference.

  I found a NetworkManager a couple of bugs about this issue that indicates 
this is a problem with libnl3. Here is the NetworkManager bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=659983
  https://bugzilla.gnome.org/show_bug.cgi?id=659984

  The second NetworkManager bug (659984) references a libnl mailing list 
message indicating a fix to the issue. Here is that post:
  http://lists.infradead.org/pipermail/libnl/2011-October/000360.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1012211/+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 1012211] Re: NetworkManager mishandles multiple interfaces on same subnet

[Paul White]

** Package changed: ubuntu => network-manager (Ubuntu)

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

Title:
  NetworkManager mishandles multiple interfaces on same subnet

Status in Linux Mint:
  New
Status in network-manager package in Ubuntu:
  New
Status in Debian:
  New
Status in Fedora:
  Unknown

Bug description:
  1) The version and edition of Linux Mint you are using (if you are not
  sure, open a terminal and run "mintwelcome").

  Release: 1 (debian)
  Edition: Debian 64-bit

  2) What you did for the problem to happen, and how to reproduce it.

  In NetworkManager, I configured both wired and wireless network
  interfaces to connect to the same network. I set both interfaces to
  "Off" in NetworkManager. I then turned on and connected the wireless
  interface. After the wireless interface was connected, I turned on and
  connected the wired interface.

  3) What happened.

  When only the wireless network was connected, both the local subnet
  route and default route went over the wireless connect, the only one
  available. Upon connection of the wired interface, NetworkManager
  properly prioritizes the wired interface for the default route, but
  left the wireless network prioritized for the local subnet route. Here
  is an example of the improper routing table, notice that the route for
  wlan0 appears above the route for eth0:

  default via 192.168.77.254 dev eth0  proto static 
  192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 
  192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 

  This is due to the order of the routes in the routing table that
  results from the order that the network connects were enabled. If the
  order of connection is reversed, so are the local subnet routes,
  correcting the issue.

  4) What you expected to happen instead.

  I expected the wired network to be prioritized for both the default
  route and local subnet route, producing a routing table something like
  this:

  default via 192.168.77.254 dev eth0  proto static 
  192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 metric 
1
  192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 metric 0

  5) If the problem happened once, sometimes, or always.

  This problem always happens. At some point in the past the network
  routes were handled properly, producing a routing table that looked
  like this:

  default via 192.168.77.254 dev wlan0  proto static metric 1
  default via 192.168.77.254 dev eth0  proto static metric 0
  192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 metric 
1
  192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 metric 0

  6) Possible relevant reference.

  I found a NetworkManager a couple of bugs about this issue that indicates 
this is a problem with libnl3. Here is the NetworkManager bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=659983
  https://bugzilla.gnome.org/show_bug.cgi?id=659984

  The second NetworkManager bug (659984) references a libnl mailing list 
message indicating a fix to the issue. Here is that post:
  http://lists.infradead.org/pipermail/libnl/2011-October/000360.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1012211/+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 1315328] [NEW] Black icons on dark grey background in right click menu of title bar when using Ambiance theme

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I am running Ubuntu 14.04 LTS.
I am using the default Ubuntu Ambiance theme.
I enabled "menus-have-icons" in dconf-editor under 
"org.gnome.desktop.interface" so that menu icons are shown.
When I right click the title bar of a window, the icons (for Minimize, Maximize 
and Close) are black on a dark grey background, so they are not very visible. I 
suppose they should be light grey instead, as is the menu text.

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


** Tags: bot-comment
-- 
Black icons on dark grey background in right click menu of title bar when using 
Ambiance theme
https://bugs.launchpad.net/bugs/1315328
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to light-themes in Ubuntu.

-- 
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 1012211] [NEW] NetworkManager mishandles multiple interfaces on same subnet

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

1) The version and edition of Linux Mint you are using (if you are not
sure, open a terminal and run "mintwelcome").

Release: 1 (debian)
Edition: Debian 64-bit

2) What you did for the problem to happen, and how to reproduce it.

In NetworkManager, I configured both wired and wireless network
interfaces to connect to the same network. I set both interfaces to
"Off" in NetworkManager. I then turned on and connected the wireless
interface. After the wireless interface was connected, I turned on and
connected the wired interface.

3) What happened.

When only the wireless network was connected, both the local subnet
route and default route went over the wireless connect, the only one
available. Upon connection of the wired interface, NetworkManager
properly prioritizes the wired interface for the default route, but left
the wireless network prioritized for the local subnet route. Here is an
example of the improper routing table, notice that the route for wlan0
appears above the route for eth0:

default via 192.168.77.254 dev eth0  proto static 
192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 
192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 

This is due to the order of the routes in the routing table that results
from the order that the network connects were enabled. If the order of
connection is reversed, so are the local subnet routes, correcting the
issue.

4) What you expected to happen instead.

I expected the wired network to be prioritized for both the default
route and local subnet route, producing a routing table something like
this:

default via 192.168.77.254 dev eth0  proto static 
192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 metric 1
192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 metric 0

5) If the problem happened once, sometimes, or always.

This problem always happens. At some point in the past the network
routes were handled properly, producing a routing table that looked like
this:

default via 192.168.77.254 dev wlan0  proto static metric 1
default via 192.168.77.254 dev eth0  proto static metric 0
192.168.77.0/24 dev wlan0  proto kernel  scope link  src 192.168.77.41 metric 1
192.168.77.0/24 dev eth0  proto kernel  scope link  src 192.168.77.40 metric 0

6) Possible relevant reference.

I found a NetworkManager a couple of bugs about this issue that indicates this 
is a problem with libnl3. Here is the NetworkManager bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=659983
https://bugzilla.gnome.org/show_bug.cgi?id=659984

The second NetworkManager bug (659984) references a libnl mailing list message 
indicating a fix to the issue. Here is that post:
http://lists.infradead.org/pipermail/libnl/2011-October/000360.html

** Affects: linuxmint
 Importance: Undecided
 Status: New

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

** Affects: debian
 Importance: Undecided
 Status: New

** Affects: fedora
 Importance: Unknown
 Status: Unknown

-- 
NetworkManager mishandles multiple interfaces on same subnet
https://bugs.launchpad.net/bugs/1012211
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to network-manager in Ubuntu.

-- 
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 1561795] Re: Fullscreen Crash Intel GPU since Ubuntu 15.10

[Michael Kasprzak]

My apologies. I didn't get around to trying it, but I did eventually
upgrade to Ubuntu 16.04, and have been unable to reproduce the problem.
So consider it closed.

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

Title:
  Fullscreen Crash Intel GPU since Ubuntu 15.10

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Ever since I upgraded to Ubuntu 15.10, I haven't been able to exit
  fullscreen without video crashing. There are rare cases when I've been
  able to safely exit, but more times than not, it doesn't. This is
  typically when I'm using Chrome to watch YouTube or Twitch video
  streams. The only way out is switch over and do a "killall -u myname".

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  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 Mar 24 19:57:24 2016
  DistUpgraded: 2015-10-25 04:02:46,508 DEBUG enabling apt cron job
  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:2203]
  InstallationDate: Installed on 2015-01-03 (446 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 343522U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic 
root=UUID=a630eb7a-a0ab-49aa-bdb6-8221ae278346 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-25 (151 days ago)
  dmi.bios.date: 09/12/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA0WW (2.60 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 343522U
  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:bvrGCETA0WW(2.60):bd09/12/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 343522U
  dmi.product.version: ThinkPad X230 Tablet
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65-3
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  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: Thu Mar 24 19:14:03 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 728 
   vendor LGD
  xserver.version: 2:1.17.2-1ubuntu9.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1561795/+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 1586787] Re: Wrong colors on external TV

[Alin Hanghiuc]

** Attachment added: "result of "xrandr --verbose" from the Mint live DVD, 
while the screen was mirrored and with the colors looking fine"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586787/+attachment/4672312/+files/xrandrmint.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/1586787

Title:
  Wrong colors on external TV

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and
  integrated graphics, when using a Samsung UE40J5200AW 40in TV with a
  DisplayPort to HDMI adapter and an HDMI cable, the colors are very
  wrong on the TV.

  This happens on a brand new Ubuntu 16.04 installation made from
  scratch, and it does not happen when I boot from a Linux Mint 17.3
  "Rosa" Cinnamon 64-bit live DVD. So same laptop, same adapter, same
  cable, same TV, and the colors are fine on the TV in this case (Mint
  live DVD). Also, when switching the laptop with a Dell running Windows
  8.1 (so the same adapter, cable, and TV are used), the colors are
  again fine.

  I have attached a picture that shows the laptop screen in front of the
  TV screen with the display mirrored. So both screens should look the
  same in the picture. But it looks like only the white color is the
  same, while the rest of the colors are very different.

  Thanks for your help,
  Alin.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Sun May 29 17:47:11 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
  InstallationDate: Installed on 2016-05-06 (22 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 4236BH1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236BH1
  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:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236BH1:pvrThinkPadT420:rvnLENOVO:rn4236BH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4236BH1
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun May 29 17:45:29 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 738 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586787/+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 1580852] Re: Xonar DSX AV200 not adjustable sound level

[Www]

wtf?

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

Title:
  Xonar DSX AV200 not adjustable sound level

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  sound card asus Xonar DSX AV200
  integrated sound card disable in bios

  tested bug ubuntu 16.04 and kubuntu 16.04 wich update 12.05.2016
  ubuntu 15.10 everything worked correctly

  changing the volume level in the gui, but it will not change

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: plasma-workspace 4:5.5.5.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 12 11:23:28 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/plasmashell
  InstallationDate: Installed on 2016-04-24 (17 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: plasma-workspace
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (process:3737): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:1876): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:4369): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:16310): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed
   (process:22292): GLib-CRITICAL **: g_slice_set_config: assertion 
'sys_page_size == 0' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580852/+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 1586787] [NEW] Wrong colors on external TV

[Alin Hanghiuc]

Public bug reported:

Hi,

On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and
integrated graphics, when using a Samsung UE40J5200AW 40in TV with a
DisplayPort to HDMI adapter and an HDMI cable, the colors are very wrong
on the TV.

This happens on a brand new Ubuntu 16.04 installation made from scratch,
and it does not happen when I boot from a Linux Mint 17.3 "Rosa"
Cinnamon 64-bit live DVD. So same laptop, same adapter, same cable, same
TV, and the colors are fine on the TV in this case (Mint live DVD).
Also, when switching the laptop with a Dell running Windows 8.1 (so the
same adapter, cable, and TV are used), the colors are again fine.

I have attached a picture that shows the laptop screen in front of the
TV screen with the display mirrored. So both screens should look the
same in the picture. But it looks like only the white color is the same,
while the rest of the colors are very different.

Thanks for your help,
Alin.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
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: Sun May 29 17:47:11 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21ce]
InstallationDate: Installed on 2016-05-06 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 4236BH1
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 83ET76WW (1.46 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4236BH1
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:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236BH1:pvrThinkPadT420:rvnLENOVO:rn4236BH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4236BH1
dmi.product.version: ThinkPad T420
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun May 29 17:45:29 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 738 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2

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


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

** Attachment added: "Picture with the laptop screen in front of the TV with 
the screen mirrored"
   
https://bugs.launchpad.net/bugs/1586787/+attachment/4672279/+files/IMG_20160529_172202.jpg

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

Title:
  Wrong colors on external TV

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and
  integrated graphics, when using a Samsung UE40J5200AW 40in TV with a
  DisplayPort to HDMI adapter and an HDMI cable, the colors are very
  wrong on the TV.

  This happens on a brand new Ubuntu 16.04 installation made from
  scratch, and it does not happen when I boot from a Linux Mint 17.3
  "Rosa" Cinnamon 64-bit live DVD. So same laptop, same adapter, same
  cable, same TV, and the colors are fine on the TV in this case (Mint
  live DVD). Also, when switching the laptop with a Dell running Windows
  8.1 (so the same adapter, cable, and TV are used), the colors are
  again fine.

  I have 

[Desktop-packages] [Bug 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

[Saikrishna Arcot]

If you choose to only get the IP address from DHCP and you don't specify
and DNS servers to use, then there won't be any DNS servers configured
(besides 127.0.1.1).

What will happen is that a DNS request will be sent to 127.0.1.1
(dnsmasq). dnsmasq doesn't have any upstream servers configured, so
unless the IP address for the domain is statically set somewhere in the
configuration file, DNS won't work.

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

Title:
  NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Setup a network with DHCP address, gateway and DNS.
  2. Connect to that network.
  3. Check the resolver configured in /etc/resolv.conf

  Expected result:
  To find "nameserver" set to the DNS addresses provided by the external DHCP 
server

  Actual result:
  "nameserver=127.0.1.1" in any case.

  This related to https://bugs.launchpad.net/bugs/1577720

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  3 12:42:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e9840ddc04  proto static  metric 600 
   169.254.0.0/16 dev wlxc4e9840ddc04  scope link  metric 1000 
   192.168.1.0/24 dev wlxc4e9840ddc04  proto kernel  scope link  src 
192.168.1.95  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlxc4e9840ddc04wifi  connected 
/org/freedesktop/NetworkManager/Devices/0  SIGKILL 
2986445c-d935-4b58-b3ca-da614dd4  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   C0:EE:FB:44:15:8A  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   enp3s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  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/1577724/+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 1552424] Re: [FFE] NetworkManager 1.2-beta

[Amr Ibrahim]

Oops! iodine is not fix released! It's still 1.1.0.

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

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-iodine package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-pptp package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 link-local support.
  * Support for event logging via audit subsystem has been added.
  * Support for native logging via systemd-journald has been added taking
  advantage of its structured logging.
  * Live reconfiguration of IP configuration after changing the settings without
  reactivation of the device with "nmcli device reapply" command and via
  D-Bus API.
  * The API for VPN plugins now supports multiple simultaneous connections.
  Most popular VPN plugins have been updated to support this functionality.
  * The libnm library now provides API 

[Desktop-packages] [Bug 1552424] Re: [FFE] NetworkManager 1.2-beta

[Amr Ibrahim]

Fixed in yakkety.

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager-applet (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager-openconnect (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager-openvpn (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager-pptp (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager-vpnc (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: network-manager-iodine (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  [FFE] NetworkManager 1.2-beta

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released
Status in network-manager-iodine package in Ubuntu:
  Fix Released
Status in network-manager-openconnect package in Ubuntu:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager-pptp package in Ubuntu:
  Fix Released
Status in network-manager-vpnc package in Ubuntu:
  Fix Released

Bug description:
  We really should update NetworkManager to 1.2 (or some other updated
  stable release) for the LTS, this will allow us to better deal with
  any bugs that might come up post-release.

  This new release will also much improve interop with LXC, which has
  recently been an issue.

  Other FFEs will be opened for NM VPN plugins and for NetworkManager-
  applet.

  
  
  
  NetworkManager-1.2
  Overview of changes since NetworkManager-1.0
  

  This is a new stable release of NetworkManager.  Notable changes
  include:

  * Added an option to enable use of random MAC addresses for Wi-Fi access
  point scanning (defaults to disabled).  Controlled with
  'wifi.mac-address-randomization' property (MAC_ADDRESS_RANDOMIZATION key 
in
  ifcfg files).
  * Wi-Fi scanning now utilizes wpa_supplicant's AP list.
  * Added support for Wi-Fi powersave, configured with POWERSAVE key in ifcfg
  files.
  * Added support for creation of more types of software devices: tun & tap,
  macvlan, vxlan and ip tunnels (ipip, gre, sit, ip6ip6 and ipip6).
  * The software devices (bond, bridge, vlan, team, ...) can now be stacked
  arbitrarily.  The nmcli interface for creating master-slave relationships
  has been significantly improved by the use of 'master' argument to
  all link types.
  * RFC7217 stable privacy addressing is now used by default to protect from
  address-based host tracking. The IPv6 addressing mode is configured with
  IPV6_ADDR_GEN_MODE key in ifcfg files.
  * Improved route management code to avoid clashes between conflicting
  routes in multiple connections.
  * Refactored platform code resulting in more robust interface to platform,
  less overhead and reduced memory footprint.
  * Improved interoperability with other network management tools.  The
  externally created software devices are not managed until they're
  activated.
  * The Device instances now exist for all software connections and the platform
  devices are now only created when the device is activated.  This makes it
  possible for connections with device of same name not to clash unless
  they're activated concurrently.  The links are now not unnecessarily 
present
  unless the connection is active, avoiding pollution of the link namespace.
  * NetworkManager now correctly manages connectivity in namespace-based
  containers such as LXC and Docker.
  * Support for configuring ethernet Wake-On-Lan has been added.
  * Added LLDP listener functionality and related CLI client commands. Enabled 
via
  LLDP option in ifcfg files.
  * CLI secret agent has been extended with support for VPN secrets.
  * The command line client now utilizes colors for its output.
  * The command line client now sorts the devices and properties for better
  clarity.
  * Numerous improvements to Bash command completion for nmcli.
  * NetworkManager relies on less external libraries.  The use of dbus-glib
  has been replaced with gio's native D-Bus support and libnl-route is no
  longer used.
  * Dependency on avahi-autoipd has been dropped.  Native IPv4 link-local
  addressing configuration based on systemd network library is now used
  instead.
  * Hostname is now managed via systemd-hostnamed on systemd-based systems.
  * Management of resolv.conf management can be changed at runtime, private
  resolv.conf is always written in /run.
  * NetworkManager can now write DNS options to resolv.conf.
  * Updated version of systemd network library used for internal DHCP and
  IPv4 

[Desktop-packages] [Bug 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

[Uqbar]

What about when I choose to only get the address from DHCP and not the DNS?
Is tcpdump (and the likes) the only way to know which DNSes have been 
configured?

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

Title:
  NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Setup a network with DHCP address, gateway and DNS.
  2. Connect to that network.
  3. Check the resolver configured in /etc/resolv.conf

  Expected result:
  To find "nameserver" set to the DNS addresses provided by the external DHCP 
server

  Actual result:
  "nameserver=127.0.1.1" in any case.

  This related to https://bugs.launchpad.net/bugs/1577720

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  3 12:42:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e9840ddc04  proto static  metric 600 
   169.254.0.0/16 dev wlxc4e9840ddc04  scope link  metric 1000 
   192.168.1.0/24 dev wlxc4e9840ddc04  proto kernel  scope link  src 
192.168.1.95  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlxc4e9840ddc04wifi  connected 
/org/freedesktop/NetworkManager/Devices/0  SIGKILL 
2986445c-d935-4b58-b3ca-da614dd4  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   C0:EE:FB:44:15:8A  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   enp3s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  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/1577724/+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 1574079] Re: USB audio device is not recognized after startup in 16.04

[Mario Limonciello]

** No longer affects: alsa-driver (Ubuntu)

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx: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/fwupd/+bug/1574079/+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 1586771] [NEW] unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.

[Ajay]

Public bug reported:

Previously Wifi was in working condition By adding extra packages from
software updates -> Additional Drivers. But now I can not able to
connect with wifi. It only shows in Air Plane mode.

I am using Laptop Thinkpad T520 
OS = ubuntu gnome 16.04 
Network card = Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] 
(Centrino Advanced-N 6205 AGN)
Kernel version = 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun May 29 18:26:15 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-16 (42 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 192.168.1.1 dev enp0s25  proto static  metric 100 
 169.254.0.0/16 dev enp0s25  scope link  metric 1000 
 192.168.1.0/24 dev enp0s25  proto kernel  scope link  src 192.168.1.105  
metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp0s25  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
enp0s25 dacd31ad-8949-42a6-8115-142800960f1c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 wlp3s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  --  
----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  --  
----
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 xenial

** Summary changed:

- Main issue is I am unable to start wifi in ubuntu gnome 16.04. 
+ unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.

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

Title:
  unable to On wifi (Air plane mode always ON) in ubuntu gnome 16.04.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Previously Wifi was in working condition By adding extra packages from
  software updates -> Additional Drivers. But now I can not able to
  connect with wifi. It only shows in Air Plane mode.

  I am using Laptop Thinkpad T520 
  OS = ubuntu gnome 16.04 
  Network card = Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] 
(Centrino Advanced-N 6205 AGN)
  Kernel version = 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 29 18:26:15 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-16 (42 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  IpRoute:
   default via 192.168.1.1 dev enp0s25  proto static  metric 100 
   169.254.0.0/16 dev enp0s25  scope link  metric 1000 
   192.168.1.0/24 dev enp0s25  proto kernel  scope link  src 192.168.1.105  
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s25  ethernet  connected/org/freedesktop/NetworkManager/Devices/1  
enp0s25 dacd31ad-8949-42a6-8115-142800960f1c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   wlp3s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  
-- 

[Desktop-packages] [Bug 1133477] Re: cut-n-paste move files got stuck forever

[xeddo]

Same issue here. Ubuntu 16.04.
Moving 500 images (totalling only 130mb) takes >5 minutes and only shows the 
"preparing to move" dialogue.
Exact same thing in Thunar takes only a few (~3) seconds!

Tested on a SATA III connected Samsung 840 SSD.
I experienced the same issue across multiple devices with different storage 
media.

Also it does not matter if it is Drag and Droped or copy and pasted.

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

Title:
  cut-n-paste move files got stuck forever

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  With Nautilus, I navigated to a folder that contained about 2,000 gif files.
  I selected all of them
  I cut with Ctrl+X
  I navigated to another folder
  I pasted with Ctrl+V

  => A popup window appeared saying "Preparing to move N files", and it got 
stuck there forever.
  Nautilus stopped responding. I waited half an hour, then I had to kill it.

  Actually some of the files were moved. Which is the worst thing that
  could happen.

  I tried again with the remaining files and it happened again!! It's
  systematic!!

  I suspect it has to do with displaying the previews of a big number of
  files. Nautilus becomes completely unmanageable whenever you open
  folders with lots of files. Maximum priority should be given to the UI
  and actual operations; displaying of the previews should be done in
  the background and should never, ever slow down user operations the
  slightest bit. Seems pretty obvious.

  Also note that 2000 is not even that much. Actually it's very few
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: nautilus 1:3.5.90.really.3.4.2-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
  Uname: Linux 3.5.0-25-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Feb 26 18:23:52 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'1312x713+64+71'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'180'
   b'org.gnome.nautilus.window-state' b'start-with-status-bar' b'true'
  InstallationDate: Installed on 2010-06-23 (979 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to quantal on 2013-01-13 (44 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1133477/+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 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

[Saikrishna Arcot]

Alternatively, you can create a file (choose any file name) in
/etc/NetworkManager/conf.d/ with the following in it:

[main]
dns=default

This should have NetworkManager not use dnsmasq and update resolv.conf.

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

Title:
  NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Setup a network with DHCP address, gateway and DNS.
  2. Connect to that network.
  3. Check the resolver configured in /etc/resolv.conf

  Expected result:
  To find "nameserver" set to the DNS addresses provided by the external DHCP 
server

  Actual result:
  "nameserver=127.0.1.1" in any case.

  This related to https://bugs.launchpad.net/bugs/1577720

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  3 12:42:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e9840ddc04  proto static  metric 600 
   169.254.0.0/16 dev wlxc4e9840ddc04  scope link  metric 1000 
   192.168.1.0/24 dev wlxc4e9840ddc04  proto kernel  scope link  src 
192.168.1.95  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlxc4e9840ddc04wifi  connected 
/org/freedesktop/NetworkManager/Devices/0  SIGKILL 
2986445c-d935-4b58-b3ca-da614dd4  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   C0:EE:FB:44:15:8A  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   enp3s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  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/1577724/+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 1577724] Re: NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

[Saikrishna Arcot]

I believe this is by design. NetworkManager starts up a dnsmasq instance
that then uses the DNS servers provided by the DHCP server to resolve
queries. This is so that dnsmasq acts as a DNS caching application.

If you run tcpdump or wireshark to log DNS queries made, you should see
that the DNS servers provided by the DHCP server are used.

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

Title:
  NM doesn't sets the DNS properly, forces local dnsmasq as a resolver

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  1. Setup a network with DHCP address, gateway and DNS.
  2. Connect to that network.
  3. Check the resolver configured in /etc/resolv.conf

  Expected result:
  To find "nameserver" set to the DNS addresses provided by the external DHCP 
server

  Actual result:
  "nameserver=127.0.1.1" in any case.

  This related to https://bugs.launchpad.net/bugs/1577720

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue May  3 12:42:19 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlxc4e9840ddc04  proto static  metric 600 
   169.254.0.0/16 dev wlxc4e9840ddc04  scope link  metric 1000 
   192.168.1.0/24 dev wlxc4e9840ddc04  proto kernel  scope link  src 
192.168.1.95  metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
  
   wlxc4e9840ddc04wifi  connected 
/org/freedesktop/NetworkManager/Devices/0  SIGKILL 
2986445c-d935-4b58-b3ca-da614dd4  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   C0:EE:FB:44:15:8A  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
   enp3s0 ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/2  --  --   
 --
  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/1577724/+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 1586528] Re: Avahi-daemon withdraws address record

[Trent Lloyd]

Avahi is not the one actively withdrawing the address, this log message
is a reaction to the address record being removed from the system.. it
withdraws the mDNS "record" for this address.

Most likely theory for this is that DHCP is deciding to drop the address
for some reason (lease expired and couldn't renew) or something else
like that.  In any case issue will be Network Manager related more than
Avahi.

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

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

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1562342] Re: unity-control-center crashed with SIGSEGV in gtk_widget_get_scale_factor()

[Launchpad Bug Tracker]

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

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

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

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

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

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

Bug description:
  Ubuntu 16.04 beta2

  Change theme from radiance to ambiance. And now unity-control-center
  dont work.

  
  ubuntu@ubuntu:~$ unity-control-center 

  (unity-control-center:4621): GLib-CRITICAL **: g_strsplit: assertion 'string 
!= NULL' failed
  Ошибка сегментирования (сделан дамп памяти)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.368
  CurrentDesktop: Unity
  Date: Sat Mar 26 22:52:01 2016
  ExecutablePath: /usr/bin/unity-control-center
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  ProcCmdline: unity-control-center datetime
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=ru_RU.UTF-8
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7ff0603ddf57 :  
mov0xc0(%rdx),%rax
   PC (0x7ff0603ddf57) ok
   source "0xc0(%rdx)" (0x00c0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   gtk_widget_get_scale_factor () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: unity-control-center crashed with SIGSEGV in 
gtk_widget_get_scale_factor()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1562342/+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 60448] Re: .xsession-errors file grows out of control & saturates disk space

[Lanoxx]

I just stumbled across this bug report, while searching for xsession-
errors. There are currently 3330 bugs involving xsession-errors:

https://launchpad.net/+search?field.text=xession-errors

I wonder how its possible to even find any useful information in such an
amount of open bugs. Since Ubuntu is moving to the systemd journal its
probably best to close most of those bugs?

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

Title:
  .xsession-errors file grows out of control & saturates disk space

Status in gdm package in Ubuntu:
  Triaged
Status in kdebase package in Ubuntu:
  Confirmed
Status in xinit source package in Dapper:
  Won't Fix

Bug description:
  Hi,

  I'm running Kubuntu Dapper, freshly dist-upgraded, on a Compaq
  Presario V2610CA laptop, with no particular esoteric configuration.

  In the past 2 weeks, my disk space has been saturated **TWICE**, i.e.
  up to 100% occ. on a 60 GB disk with 40 GB previously free, as
  reported by the "df -h" command (in fact app. 10 MB was still
  available, just enough to be able to boot/login!).  The cause of these
  events is what seems an ever-growing .xsession-errors file in one user
  directory. i.e. /home/user.  After a quick search on Google, I've
  found 2 similar reports (one concerning Dapper, the other OpenSuse):

  http://www.nabble.com/X-error-log-t1364627.html

  http://lists.opensuse.org/opensuse/2005-10/msg00044.html

  
  However, I didn't find anything related to this problem on Launchpad...

  It 's quite possible that something is going wrong with my system and
  is filling the .xsession-errors file with various reports.  I did not
  have the chance to pinpoint what's going wrong since my only concern
  was to prevent my system from completely crashing.  That's why I
  deleted the file without trying to look at its content (my system was
  saturated to a point that I could not receive one simple e-mail, Kmail
  complaining about the lack of disk space...).  The only thing I know
  is that since 2 weeks, I use more frequently Skype and I have created
  a second user account for my wife to be able to manger her e-mails
  with Kmail and browse the Web with Konqueror a little bit.  Nothing so
  complex or heavy...

  Anyway, this report is not about what's going wrong with my system,
  but instead about the fact that an error-log file, like .xsession-
  errors, that is supposed to be useful to track problems, should not be
  the cause of a major critical problem like the lack of disk space!  I
  don't know what would be a satifying solution, but in my case I've set
  up a script to erase this file in root and all users directory at each
  hour, by putting an executable file with this content in
  /etc/cron.hourly:

  rm /home/*/.xsession-errors*
  rm /root/.xsession-errors*

  Thanks for your attention.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/60448/+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 1584853] Re: Shotwell crashes on startup / Crash in exiv2 due to assertion when setting rating on jpg with a Casio makernote

[Launchpad Bug Tracker]

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

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

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

Title:
  Shotwell crashes on startup / Crash in exiv2 due to assertion when
  setting rating on jpg with a Casio makernote

Status in exiv2 package in Ubuntu:
  Confirmed
Status in exiv2 package in Debian:
  Fix Released

Bug description:
  Starting from the command line, this can be seen:

  shotwell: tiffcomposite.cpp:749: virtual Exiv2::Internal::TiffComponent* 
Exiv2::Internal::TiffMnEntry::doAddPath(uint16_t, Exiv2::Internal::TiffPath&, 
Exiv2::Internal::TiffComponent*, Exiv2::Internal::TiffComponent::AutoPtr): 
Assertion `mn_' failed.
  Aborted (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: shotwell 0.22.0+git20160108.r1.f2fb1f7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May 23 08:48:32 2016
  InstallationDate: Installed on 2015-09-20 (245 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: shotwell
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (31 days ago)
  shotwell.log:
   L 24280 2016-05-23 08:46:56 [MSG] main.vala:385: Shotwell Photo Manager 
0.22.0
   L 24280 2016-05-23 08:46:56 [MSG] main.vala:43: Verifying database ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1584853/+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 1586761] Re: White text on white backgrounds on most sites with 3.20 and Firefox

[Nikita Yerenkov-Scott]

** Summary changed:

- White text on white backgrounds on most sites with 3.20
+ White text on white backgrounds on most sites with 3.20 and Firefox

** Description changed:

  When running GNOME 3.18 on Ubuntu GNOME 16.04 I found that on some sites
  the text was black on black so I could only see it through highlighting,
  on other sites like YouTube for instance though I found that the text
  was very light grey on white background, still hard to see, but better
  than having the same colour for the background and the text. But now
  after upgrading to GNOME 3.20 I have found that with all themes that on
  YouTube and many other sites the text is white on white background
  meaning the only way to see it is to highlight it, but in a search box
- this is very annoying as you can imagine.
+ this is very annoying as you can imagine. I am running Firefox version
+ 46.0.1 and have linked a possibly related upstream bug.

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

** Bug watch added: Mozilla Bugzilla #1158076
   https://bugzilla.mozilla.org/show_bug.cgi?id=1158076

** Also affects: firefox via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1158076
   Importance: Unknown
   Status: Unknown

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

Title:
  White text on white backgrounds on most sites with 3.20 and Firefox

Status in Mozilla Firefox:
  Unknown
Status in Ubuntu GNOME:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  When running GNOME 3.18 on Ubuntu GNOME 16.04 I found that on some
  sites the text was black on black so I could only see it through
  highlighting, on other sites like YouTube for instance though I found
  that the text was very light grey on white background, still hard to
  see, but better than having the same colour for the background and the
  text. But now after upgrading to GNOME 3.20 I have found that with all
  themes that on YouTube and many other sites the text is white on white
  background meaning the only way to see it is to highlight it, but in a
  search box this is very annoying as you can imagine. I am running
  Firefox version 46.0.1 and have linked a possibly related upstream
  bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1586761/+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 1586764] [NEW] Screen corruption on Asus Zenbook UX31E occurring after some time or after hibernation

[datenhalde]

Public bug reported:

The problem occurred after upgrade to Xenial. After a (re)boot
everything is normal but after using the machine for some time or
especially after wakeup from hibernation (e.g. opening display) the
lower part of the screen (below the position of the mouse pointer)
starts to flicker, especially when moving the mouse. I'm experiencing
this on an Asus Zenbook UX31E, using Intel i915 video.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun May 29 13:46:06 2016
DistUpgraded: 2016-04-28 19:48:07,277 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1427]
InstallationDate: Installed on 2015-12-30 (150 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK Computer Inc. UX31E
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=d89498dd-61fb-4eee-835a-5fc3cfc9f91a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-04-28 (30 days ago)
dmi.bios.date: 11/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.215
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.215:bd11/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Apr  4 07:20:36 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id6107 
 vendor COR
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug corruption ubuntu wayland-session xenial

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

Title:
  Screen corruption on Asus Zenbook UX31E occurring after some time or
  after hibernation

Status in xorg package in Ubuntu:
  New

Bug description:
  The problem occurred after upgrade to Xenial. After a (re)boot
  everything is normal but after using the machine for some time or
  especially after wakeup from hibernation (e.g. opening display) the
  lower part of the screen (below the position of the mouse pointer)
  starts to flicker, especially when moving the mouse. I'm experiencing
  this on an Asus Zenbook UX31E, using Intel i915 video.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun May 29 13:46:06 2016
  DistUpgraded: 2016-04-28 19:48:07,277 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])

[Desktop-packages] [Bug 1562381] Re: Typing special characters with non-US layout get repeated indefinitely

[marmuta]

Me neither, thanks for testing. Typing emoji and various diacritics
seems a lot more reliable too. I have yet to find a key that doesn't
work. Also, I can't reproduce bug #1352549 anymore.

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

Title:
  Typing special characters with non-US layout get repeated indefinitely

Status in Onboard:
  Fix Committed
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Typing special characters like .,:;-()"@# (and other) or numbers with
  non-US keyboard layout get repeated indefinitely, like this:

  
тест...

  This will continue to happen untl other symbol is entered or other
  button is pressed. Reproducible with GTK and Xinput. Testng was done
  on Ubuntu Gnome 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: onboard 1.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 27 02:29:05 2016
  InstallationDate: Installed on 2016-03-19 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160319)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1562381/+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 1582687] Re: workbench crashes metacity on ubuntu 16.04

[Alberts Muktupāvels]

For metacity you need install metacity-dbg package.

If you again have reproducible crashes with metacity it might be good idea to 
reproduce crash when running metacity with --sync commandline option:
metacity --sync --replace

sync option will ensure that stacktrace shows correct functon where it crashes:
ftp://www.x.org/pub/current/doc/libX11/libX11/libX11.html#Enabling_or_Disabling_Synchronization

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

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+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 1582687] Re: workbench crashes metacity on ubuntu 16.04

[Alberts Muktupāvels]

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

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

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+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 1216600] Re: rythmbox freezes randomly when playing song

[Merlijn Sebrechts]

Haven't stumbled upon this bug anymore, so marking this as fix released.

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

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

Title:
  rythmbox freezes randomly when playing song

Status in gstreamer0.10 package in Ubuntu:
  Fix Released

Bug description:
  While playing a .wav song, rythmbox suddenly skips over some parts and
  then freezes. If i close rythmbox, open it again and play the same
  song, it plays it until the end, and then stops.

  I tried it one more time; now plays normally and at the end, it goes
  to the next song, but it still shows like it is playing the first
  song.

  I know this is a very strange bug report, if you need more/more clear
  information, ask me.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: libgstreamer0.10-0 0.10.36-1ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sun Aug 25 17:34:25 2013
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/rhythmbox
  InstallationDate: Installed on 2013-05-31 (85 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: gstreamer0.10
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1216600/+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 1352549] Re: layout reverts to default after inserting unicode character via long press on a key

[marmuta]

Fixed in trunk, I believe. The changes for Bug #1562381 help here too.
Sorry it took so long.

** Changed in: onboard
   Status: Confirmed => Fix Committed

** Changed in: onboard
   Importance: Undecided => High

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

Title:
  layout reverts to default after inserting unicode character via long
  press on a key

Status in Onboard:
  Fix Committed
Status in onboard package in Ubuntu:
  New

Bug description:
  I use onboard with 2 layouts. The english one (default) and the greek one 
(secondary). I change layouts via Ctrl+Space.
  When I use the greek layout, if I long press on a key and insert a unicode 
char, then while the greek layout is still visible (as it should be), pressing 
on a button results to the corresponding english char!
  For example, in greek layout I long press "ε" to insert "έ". After that, if I 
press again "ε" it results to "e".
  So while I still see the greek layout, pressing the keys results to the 
corresponding english chars. Obviously it should result to the greek chars

  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04

  onboard:
Installed: 1.0.0-0ubuntu4
Candidate: 1.0.0-0ubuntu4
Version table:
   *** 1.0.0-0ubuntu4 0
  500 http://gr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/onboard/+bug/1352549/+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 1574090] Re: Brasero not translated at all on ubuntu 16.04

[Сергей]

Fully confirms the words of Olivier Febwin (febcrash). The problem can
be considered solved.

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

Title:
  Brasero not translated at all on ubuntu 16.04

Status in Brasero:
  Unknown
Status in brasero package in Ubuntu:
  Fix Released
Status in brasero source package in Xenial:
  Fix Committed

Bug description:
  To the sponsor: Please use the same patch for Xenial, changing the
  version to 3.12.1-1ubuntu2.1.

  [Impact]

  Translations are not enabled. The attached patch fixes it.

  [Test Case]

  1. Install some other language but english and make it the display
  language.

  2. Start brasero and find that it's still displayed in English.

  [Regression Potential]

  Neglectable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/brasero/+bug/1574090/+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 1508718] Re: NetworkManager - error initialzing editor

[Mörgæs]

Does this bug also appear in a fresh install of 16.04?

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

Title:
  NetworkManager - error initialzing editor

Status in network-manager-applet package in Ubuntu:
  Confirmed

Bug description:
  Error initializing editor
  settings/nm-settings-connection.c.995 - Connection didn't have requested 
setting 'ppp'

  Error occurs when attempting to edit existing mobile broadband connection.
  Editing existing Ethernet connections succeeds without error.

  This broke between 1.0.4-0ubuntu3 and 1.0.4-0ubuntu5

  The connection still functions correctly but its properties can no
  longer be edited with gui.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager-gnome 0.9.10.1-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Oct 21 23:14:57 2015
  ExecutablePath: /usr/bin/nm-connection-editor
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-09-30 (21 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  IpRoute:
   default via 10.109.83.190 dev wwan0  proto static  metric 750 
   10.109.83.188/30 dev wwan0  proto kernel  scope link  src 10.109.83.189  
metric 750 
   169.254.0.0/16 dev wwan0  scope link  metric 1000
  IwConfig:
   wwan0 no wireless extensions.
   
   eno1  no wireless extensions.
   
   lono wireless extensions.
  JournalErrors:
   No journal files were found.
   -- No entries --
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   cdc-wdm0  gsm   connected /org/freedesktop/NetworkManager/Devices/2  
att_stick   d13a7207-c11a-47ad-8876-ee62c3ccb5b2  
/org/freedesktop/NetworkManager/ActiveConnection/7 
   eno1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/0  
--  ----
 
   loloopback  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-applet/+bug/1508718/+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 1586641] Re: PCI/internal sound card not detected

[mart1oeil]

The sound card is a Realtek ALC3235 cf :
http://www.dell.com/support/manuals/us/en/19/latitude-e7470-ultrabook/Late_E7470_OM
/Audio-specifications?guid=GUID-EE1BF4E5-7FF1-4415-A32D-
B8FE54B2D639=en-us

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My sound card is not even detected and alsamixer do nothing.

  I tried oem-audio-hda-daily-lts-xenial-dkms -
  0.201605271732~ubuntu16.04.1 https://code.launchpad.net/~ubuntu-audio-
  dev/+archive/ubuntu/alsa-daily/+packages like it was described here
  https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS but it didn't worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May 28 15:20:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-05-27 (1 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.0
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.0:bd02/14/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586641/+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 1573052] Re: [packaging] gnome-software provides a broken symlink of /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so on Ubuntu 16.04

[Miguel]

** Changed in: gnome-software (Ubuntu Xenial)
   Status: Confirmed => Fix Released

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

Title:
  [packaging] gnome-software provides a broken symlink of /usr/lib/gs-
  plugins-9/libgs_plugin_xdg_app_reviews.so on Ubuntu 16.04

Status in GNOME Software:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Xenial:
  Fix Released

Bug description:
  ```
  $ file /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so
  /usr/lib/gs-plugins-9/libgs_plugin_xdg_app_reviews.so: broken symbolic link 
to libgs_plugin_xdg_app_reviews.so.0.0.0
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2
  Uname: Linux 4.5.0-buo-ren-vanilla-intel-ivybridge-optimized x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 21 21:44:09 2016
  InstallationDate: Installed on 2016-01-07 (104 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1573052/+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 1582687] Re: workbench crashes metacity on ubuntu 16.04

[Dantali0n]

I installed Metacity 1:3.18.4-0ubuntu0.2 and mysql-workbench now fully
works again.

I would like to be able to help more when encountering bugs and even help 
fixing them.
As you can see from my stacktrace I am not really up to skill yet and was 
hoping one of you could supply me with information about: getting all the 
packages with debug symbols and properly making gdb write stacktraces to log 
files. But please feel free to ignore this if you find it will take to much of 
your time.

Thanks for repairing this package which I use in my daily live.

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

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+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 1582687] Re: workbench crashes metacity on ubuntu 16.04

[Dantali0n]

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

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

Title:
  workbench crashes metacity on ubuntu 16.04

Status in metacity package in Ubuntu:
  Fix Released
Status in metacity source package in Xenial:
  Fix Committed
Status in metacity source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Metacity can crash with XError (BadRegion) sometimes when closing windows.

  This, in turn, can lead gnome-session to forcefully stop the session.

  [Test Case 1]
  Described in comment #3.

  [Test Case 2]
  * Launch LibreOffice Writer.
  * Add a table to a document.
  * Open "Border Style" popup window from the table toolbar.
  * Wait for the window to appear and then quickly close it.
  * If Metacity does not crash, repeat the process several times.

  [Regression Potential]
  The fix is small (just adding an error trap) and will not cause any 
regressions.

  -

  I installed mysql-workbench and gnome-session-flashback on ubuntu
  16.04 and whenever I start mysql-workbench metacity or X11 but I think
  metacity crashes and I am returned to the login screen after a few
  seconds.

  I am uncertain if mysql-workbench works in the default unity
  configuration as after installing gnome-session-flashback I can no
  longer login to the default unity experience.

  My mysql-workbench logs where not really helpfull but if you would
  really like them I could include them.

  I also tried to compile mysql-workbench from source but the gtk2
  version included with ubuntu 16.04 seems to be incompatible due to the
  deprecation of a data type: GdkPixBuf

  ubuntu version - 16.04
  package - mysql-workbench 6.3.6 amd64
  what i expected - open mysql workbench
  what happened - black screen and returned to login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1582687/+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 1576977] Re: Lots of GEGL-gegl-operation.c-WARNING on starting gimp

[snapy]

I also have these warnings.

Maybe this is unrelated but for me sometimes when Gimp starts it's
incredibly slow and it only seems to work again when I kill it and
restart it. (Note that I have a fast machine and 8 GiB of memory.)

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

Title:
  Lots of GEGL-gegl-operation.c-WARNING on starting gimp

Status in gimp package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04
  gimp: 2.8.16-1ubuntu1

  rm ~/.gimp-2.8/
  LANG=en gimp

  
  (gimp:413): GLib-GObject-WARNING **: g_object_set_valist: object class 
'GeglConfig' has no property named 'cache-size'

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A3410 from "gimp:point-layer-mode" to "gimp
  :dissolve-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A39B0 from "gimp:point-layer-mode" to "gimp
  :behind-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4090 from "gimp:point-layer-mode" to "gimp
  :multiply-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A43A0 from "gimp:point-layer-mode" to "gimp
  :screen-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4790 from "gimp:point-layer-mode" to "gimp
  :overlay-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A4BC0 from "gimp:point-layer-mode" to "gimp
  :difference-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5800 from "gimp:point-layer-mode" to "gimp
  :addition-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5BC0 from "gimp:point-layer-mode" to "gimp
  :subtract-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A5F80 from "gimp:point-layer-mode" to "gimp
  :darken-only-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A63D0 from "gimp:point-layer-mode" to "gimp
  :lighten-only-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A68E0 from "gimp:point-layer-mode" to "gimp:hue-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A6B40 from "gimp:point-layer-mode" to "gimp
  :saturation-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A6F70 from "gimp:point-layer-mode" to "gimp:color-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A73E0 from "gimp:point-layer-mode" to "gimp:value-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7760 from "gimp:point-layer-mode" to "gimp
  :divide-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7BE0 from "gimp:point-layer-mode" to "gimp:dodge-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A7F50 from "gimp:point-layer-mode" to "gimp:burn-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A83A0 from "gimp:point-layer-mode" to "gimp
  :hardlight-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A8740 from "gimp:point-layer-mode" to "gimp
  :softlight-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A8B40 from "gimp:point-layer-mode" to "gimp:grain-
  extract-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A90A0 from "gimp:point-layer-mode" to "gimp:grain-
  merge-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A93C0 from "gimp:point-layer-mode" to "gimp:color-
  erase-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20A9730 from "gimp:point-layer-mode" to "gimp:erase-
  mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20AA080 from "gimp:point-layer-mode" to "gimp
  :replace-mode"

  (gimp:413): GEGL-gegl-operation.c-WARNING **: Cannot change name of
  operation class 0x20AA450 from "gimp:point-layer-mode" to "gimp:anti-
  erase-mode"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1576977/+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 1574079] Re: USB audio device is not recognized after startup in 16.04

[TheBigW]

output form my 2nd machine where occasionally the RME Fireface UCX is
not recognized:

Bus 001 Device 004: ID 1058:0730 Western Digital Technologies, Inc. My Passport 
Essential (WDBACY)
Bus 001 Device 003: ID 0424:3fb9 Standard Microsystems Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

mhh - I did not see it at all it seems, but aplay -l gives me perfectly:

Karte 0: UCX23660989 [Fireface UCX (23660989)], Gerät 0: USB Audio [USB Audio]
  Sub-Geräte: 0/1
  Sub-Gerät #0: subdevice #0
Karte 1: Intel [HDA Intel], Gerät 0: ALC861-VD Analog [ALC861-VD Analog]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0
Karte 1: Intel [HDA Intel], Gerät 6: Si3054 Modem [Si3054 Modem]
  Sub-Geräte: 1/1
  Sub-Gerät #0: subdevice #0

and at the moment it works as expected

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

Title:
  USB audio device is not recognized after startup in 16.04

Status in alsa-driver package in Ubuntu:
  Invalid
Status in fwupd package in Ubuntu:
  Confirmed

Bug description:
  Hi @all,

  I used the same USB audio device in all previous Ubuntu versions
  (Focusrite Scarlet 2i2). It is supposed to be class compliant and
  works an all distros flawless (even RPI2 and OSMC). After upgrading
  from 15.10 to 16.04 it stopped to work: after start-up it does not
  show up as an audio device at all (also not recognized by aplay -l). I
  can workaround this by unplugging it and plugging it in again after
  Ubuntu booted up (strangely 2 times unplug/re-plug). After 2nd time
  plugging it in again it shows up and works great without any further
  issues until next restart.

  Maybe worth to note that I recognized today that fwupd uses
  continuously 100% CPU load, so I just killed it today. My Hardware
  (Main-board/CPU) is a bit older (Intel E8400), so could probably be
  some compatibility issue...

  regards,
  Tobias

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic i686
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   tobias 1553 F...m pulseaudio
   /dev/snd/controlC1:  tobias 1553 F pulseaudio
   /dev/snd/controlC0:  tobias 1553 F pulseaudio
   /dev/snd/controlC2:  tobias 1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 23 20:09:04 2016
  InstallationDate: Installed on 2015-09-19 (217 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)
  dmi.bios.date: 09/30/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1238
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5B-Deluxe
  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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx: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/1574079/+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 1562381] Re: Typing special characters with non-US layout get repeated indefinitely

[RussianNeuroMancer]

So far I wasn't able to reproduce this issue with Revision 2152.

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

Title:
  Typing special characters with non-US layout get repeated indefinitely

Status in Onboard:
  Fix Committed
Status in onboard package in Ubuntu:
  Confirmed

Bug description:
  Typing special characters like .,:;-()"@# (and other) or numbers with
  non-US keyboard layout get repeated indefinitely, like this:

  
тест...

  This will continue to happen untl other symbol is entered or other
  button is pressed. Reproducible with GTK and Xinput. Testng was done
  on Ubuntu Gnome 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: onboard 1.2.0-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 27 02:29:05 2016
  InstallationDate: Installed on 2016-03-19 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160319)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: onboard
  UpgradeStatus: No upgrade log present (probably fresh install)

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