[Desktop-packages] [Bug 778293] Re: [Upstream] Custom Animation not repeating

2016-03-02 Thread Maurice Clerc
Wrongly said to be fixed. I still have it:
Ubuntu 14.04
LibreOffice Impress 5.0.5.2

Is there a workaround?

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

Title:
  [Upstream] Custom Animation not repeating

Status in LibreOffice:
  Invalid
Status in OpenOffice:
  Confirmed
Status in libreoffice package in Ubuntu:
  Fix Released
Status in openoffice.org package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: libreoffice

  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-impress
  libreoffice-impress:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386
  Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen using Ubuntu 11.04, LibreOffice Impress
  via the Terminal:

  cd ~/Desktop && wget
  
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/778293/+attachment/2115970/+files/EffectTest_1.odp
  && loimpress -nologo EffectTest_1.odp

  click Slide 2 -> on the right under Tasks click Custom Animation ->
  secondary click Shape 1 -> primary click Effect Options... -> Timing
  tab -> notice Repeat combo box is 3 -> OK button -> F5 -> Space bar
  the diamond follows the custom animation path three times
  consecutively.

  4) What happens instead is the custom animation follows the path only
  once.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: libreoffice-core 1:3.3.2-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
  Uname: Linux 2.6.38-8-generic-pae i686
  Architecture: i386
  Date: Fri May  6 08:03:01 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  ProcEnviron:
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to natty on 2011-05-03 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/778293/+subscriptions

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


[Desktop-packages] [Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound

2016-03-02 Thread nour
hi Raymond,

What this means? shall I install anything else?

Thanks

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

Title:
  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuned  1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

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

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


[Desktop-packages] [Bug 1552584] [NEW] Cannot log in after fglrx update (15.201-0ubuntu0.14.04.1)

2016-03-02 Thread Otus
Public bug reported:

After updating to the newest version of the fglrx package
(15.201-0ubuntu0.14.04.1) I can no longer log in after a reboot. When I
type a password it takes a couple of seconds to throw me back into the
log in screen. Previous versions worked fine.

Removing fglrx to switch to the free drivers solved any log in problems.
Reinstalling fglrx introduced them again.

I haven't debugged beyond that, but I can in the next few days if given
instructions.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: fglrx (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
NonfreeKernelModules: fglrx
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.19
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  3 09:11:47 2016
DistUpgraded: 2014-04-19 10:59:27,275 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fglrx-core, 15.201, 3.19.0-51-generic, x86_64: installed
 virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed
 virtualbox, 4.3.36, 3.19.0-49-generic, x86_64: installed
 virtualbox, 4.3.36, 3.19.0-51-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 
250X] [1002:683d] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:0429]
InstallationDate: Installed on 2012-11-10 (1208 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: MSI MS-7798
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-51-generic 
root=UUID=1c693e72-bdec-48cc-9dc7-fc690466dc38 ro quiet splash zswap.enabled=1 
vt.handoff=7
Renderer: Software
SourcePackage: fglrx-installer
UpgradeStatus: Upgraded to trusty on 2014-04-19 (683 days ago)
dmi.bios.date: 09/30/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.9
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B75MA-P45 (MS-7798)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd09/30/2013:svnMSI:pnMS-7798:pvr1.0:rvnMSI:rnB75MA-P45(MS-7798):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7798
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Mar  3 09:11:03 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputRAPOO RAPOO 2.4G Wireless Device KEYBOARD, id 8
 inputRAPOO RAPOO 2.4G Wireless Device KEYBOARD, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.1-0ubuntu3.1~trusty1

** Affects: fglrx-installer (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Cannot log in after fglrx update (15.201-0ubuntu0.14.04.1)

Status in fglrx-installer package in Ubuntu:
  New

Bug description:
  After updating to the newest version of the fglrx package
  (15.201-0ubuntu0.14.04.1) I can no longer log in after a reboot. When
  I type a password it takes a couple of seconds to throw me back into
  the log in screen. Previous versions worked fine.

  Removing fglrx to switch to the free drivers solved any log in
  problems. Reinstalling fglrx introduced them again.

  I haven't debugged beyond that, but I can in the next few days if
  given instructions.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: fglrx (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
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CompizPlugins: No value set for 

[Desktop-packages] [Bug 1446689] Re: network-manager configured to use /usr/sbin/pppoe but does not recommend pppoe

2016-03-02 Thread Benoit Grégoire
I have the exact same problem as Rustom, after upgrading from vivid to
wily.  pppoe id not setting the default route.

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

Title:
  network-manager configured to use /usr/sbin/pppoe but does not
  recommend pppoe

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  networkmanager switched from using ppp to using pppoe binary for
  dsl/pppoe connections, I am using pppoe and I can't connect to the
  Internet unless I install "pppoe" package.

  From:
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-10=7955806a02db64b20079267743056d7d9d45af3b

  "for now, work around this by using the userland pppoe client rather
  than the kernel code"

  One way to fix it is to include pppoe
  Another way is to configure --with-pppoe=/usr/sbin/pppd.

  I think this is urgent as pppoe/dsl on all vivid machines will be
  broken out-of-the-box.

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

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


[Desktop-packages] [Bug 1184699] Re: Canon LIDE 110 can only scan once, then I need to replug the usb cable

2016-03-02 Thread Hua Zhang
Version 1.025-git is now working fine for me as well. Thanks!

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

Title:
  Canon LIDE 110 can only scan once, then I need to replug the usb cable

Status in Simple Scan:
  Invalid
Status in sane-backends package in Ubuntu:
  Fix Committed

Bug description:
  I have a Canon LIDE 110 scanner which works by default on ubuntu 13.04. 
  The problem is after first scan, I can not scan for second time. I need to 
reconnect the USB cable to use the scanner again.

  # TEST 1 : without reconnecting the usb cable
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I don't unplug plug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # FAIL
  scanimage: no SANE devices found

  # TEST 2 : reconnect usb cable between scan attempts
  francois@pc:~$ scanimage -v > test1.jpg # success
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total
  # I unplug and replug the usb cable.
  francois@pc:~$ scanimage -v > test2.jpg # SUCCESS
  scanimage: scanning image of size 636x885 pixels at 8 bits/pixel
  scanimage: acquiring gray frame
  scanimage: min/max graylevel value = 0/255
  scanimage: read 562860 bytes in total

  francois@pc:~$ dmesg # extract
  [  829.365158] usb 3-1: USB disconnect, device number 2
  [  834.935000] usb 3-1: new high-speed USB device number 4 using xhci_hcd
  [  834.952515] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [  834.952519] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [  834.952522] usb 3-1: Product: CanoScan
  [  834.952524] usb 3-1: Manufacturer: Canon
  [ 1623.738811] usb 3-1: USB disconnect, device number 4
  [ 1623.739072] xhci_hcd :00:14.0: Slot 3 endpoint 6 not removed from BW 
list!
  [ 1625.528827] usb 3-1: new high-speed USB device number 5 using xhci_hcd
  [ 1625.546327] usb 3-1: New USB device found, idVendor=04a9, idProduct=1909
  [ 1625.546331] usb 3-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 1625.546334] usb 3-1: Product: CanoScan
  [ 1625.546336] usb 3-1: Manufacturer: Canon

  francois@pc:~$ uname -a && cat /etc/issue
  Linux pc 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux
  Ubuntu 13.04 \n \l

  The problem was reported here by someone else :
  http://askubuntu.com/questions/278473/canon-lide-110-should-reconnect-
  usb-for-each-scan

  Thanks
  François

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

-- 
Mailing list: https://launchpad.net/~desktop-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

2016-03-02 Thread Lorn Potter
awe is currently working on getting the update to 1.2 working. Work is
ongoing, and needs a few more improvements and patches ported.

-- 
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:
  New

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 to access VPN service definitions.
  * New DHCP_FQDN key in ifcfg files to configure the full FQDN to be sent to
  the DHCP servers.
  * The timeout for DHCP requests can now be modified using the
  'ipv4.dhcp-timeout' property.
  * Added multicast_snooping option to BRIDGING_OPTS ifcfg key.
  * Added support for detecting 

[Desktop-packages] [Bug 1552554] [NEW] Right click ejecting USB drive from unity launcher causes momentary (1 sec or so) system hang

2016-03-02 Thread Jacob Killelea
Public bug reported:

Right click ejecting USB drive from unity launcher causes momentary (1
sec or so) system hang

Ubuntu 16.04
Unity desktop

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
Uname: Linux 4.4.0-040400-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar  2 22:35:14 2016
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'267'
 b'org.gnome.nautilus.window-state' b'geometry' b"'958x1027+960+24'"
 b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'date_modified']"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed']"
InstallationDate: Installed on 2015-12-24 (69 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nautilus (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 nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1552554

Title:
  Right click ejecting USB drive from unity launcher causes momentary (1
  sec or so) system hang

Status in nautilus package in Ubuntu:
  New

Bug description:
  Right click ejecting USB drive from unity launcher causes momentary (1
  sec or so) system hang

  Ubuntu 16.04
  Unity desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu2
  Uname: Linux 4.4.0-040400-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  2 22:35:14 2016
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'267'
   b'org.gnome.nautilus.window-state' b'geometry' b"'958x1027+960+24'"
   b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 
'size', 'type', 'owner', 'group', 'permissions', 'date_modified']"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed']"
  InstallationDate: Installed on 2015-12-24 (69 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1551283] Re: "Region & Language" settings should allow you to set keyboard input method system

2016-03-02 Thread Tim
we seed language-selector-common, since that provides the list of
packages that make up language packs (when installing from gnome-
control-center). im-config is on our images, seems like ibus pulls that
one in.

I wonder should be just switch to ibus by default? I am not really up to
date with the whole ibus vs fcitx for CJK statuses, but I do wonder how
broken is fcitx under gnome-shell, i.e. does layout switching even work
etc? or is it just the xim mode being set incorrectly causing the
issues?

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

Title:
  "Region & Language" settings should allow you to set keyboard input
  method system

Status in Ubuntu GNOME:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in im-config package in Ubuntu:
  Incomplete
Status in language-selector package in Ubuntu:
  Incomplete

Bug description:
  In the gnome-language-selector one is able to set the "Keyboard input
  method system". For instance on my system I can either set it to
  "none", "IBus", or "fcitx". However there is no such option in the
  gnome-control-center's Region & Language section, though I think that
  there should be.

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

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


[Desktop-packages] [Bug 1552417] Re: [X1100] Flickering after resume from RAM

2016-03-02 Thread Tommy Trussell
I believe I can do this, however it will take quite a bit more
preparation and effort (because of the radeon Xpress 1100 bug  I cannot
use the display on this laptop after any successful resume from suspend)
I am also testing from a live image with no persistent storage, so I
will need to do something different, so I will probably back up the
laptop's data, wipe the Trusty HWE kernel installation on it, install
Xenial, install openssh-server so I can ssh into it, etc. etc..

Before I get started, however I want to confirm my understanding of the
instructions linked above --

1) I need to be using an upstream kernel, not the daily xenial kernel in
the daily .iso

2) I need to log SIX resume trace cycles (steps 5, 6, 7, 8, 9 and 10)
and attach each to the bug report? Or do I need to log EIGHTEEN resume
trace cycles (a set of six resume trace cycles for each of the three
methods of invoking suspend)?

3) The "resume trace" that gets attached for each of the cycles is the
dmesg > dmesg.txt file.  Or is there a different trace file you need?

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

Title:
  [X1100] Flickering after resume from RAM

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce :
  - choose suspend
  - resume from ram
  => the screen will flicker while CPU activity is not high

  WORKAROUND: Launch an infinite loop that consume CPU :
  $ while true; do echo >/dev/null; done

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  2 20:00:24 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:009f]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  Lsusb:
   Bus 001 Device 002: ID 0951:160b Kingston Technology
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5100
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- BOOT_IMAGE=/casper/vmlinuz
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5100
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Mar  2 13:50:49 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1552537] Re: Lock screen bypassed by switching to console and then back to GUI

2016-03-02 Thread hussain
** Description changed:

- When I lock the screen I found that switching to console and then using 
ctrl+alt+F7 to switch back to GUI bypasses the lock screen without typing any 
password. even when I click on switch user after locking the screen if 
replicate the same process it takes me to the locked user account without 
prompting for password.
-  
+ When I lock the screen I found that switching to console and then using
+ ctrl+alt+F7 to switch back to GUI bypasses the lock screen without
+ typing any password. even when I click on switch user after locking the
+ screen if replicate the same process it takes me to the locked user
+ account without prompting for password.
+ 
+ steps to reproduce:
+ - Lock the screen either from the gui or even using a terminal command.
+ - switch to a tty i.e ctrl + alt + f4
+ - Switch back to gui ctrl + alt + F7
+ 
  ubuntu 15.10.
  unity desktop.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  3 07:19:08 2016
  InstallationDate: Installed on 2015-11-09 (114 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Lock screen bypassed by switching to console and then back to GUI

Status in lightdm package in Ubuntu:
  New

Bug description:
  When I lock the screen I found that switching to console and then
  using ctrl+alt+F7 to switch back to GUI bypasses the lock screen
  without typing any password. even when I click on switch user after
  locking the screen if replicate the same process it takes me to the
  locked user account without prompting for password.

  steps to reproduce:
  - Lock the screen either from the gui or even using a terminal command.
  - switch to a tty i.e ctrl + alt + f4
  - Switch back to gui ctrl + alt + F7

  ubuntu 15.10.
  unity desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  3 07:19:08 2016
  InstallationDate: Installed on 2015-11-09 (114 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1552537] [NEW] Lock screen bypassed by switching to console and then back to GUI

2016-03-02 Thread hussain
*** This bug is a security vulnerability ***

Public security bug reported:

When I lock the screen I found that switching to console and then using 
ctrl+alt+F7 to switch back to GUI bypasses the lock screen without typing any 
password. even when I click on switch user after locking the screen if 
replicate the same process it takes me to the locked user account without 
prompting for password.
 
ubuntu 15.10.
unity desktop.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.16.7-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
Uname: Linux 4.2.0-27-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar  3 07:19:08 2016
InstallationDate: Installed on 2015-11-09 (114 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

** Information type changed from Private Security to Public Security

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

Title:
  Lock screen bypassed by switching to console and then back to GUI

Status in lightdm package in Ubuntu:
  New

Bug description:
  When I lock the screen I found that switching to console and then using 
ctrl+alt+F7 to switch back to GUI bypasses the lock screen without typing any 
password. even when I click on switch user after locking the screen if 
replicate the same process it takes me to the locked user account without 
prompting for password.
   
  ubuntu 15.10.
  unity desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.7-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  Uname: Linux 4.2.0-27-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  3 07:19:08 2016
  InstallationDate: Installed on 2015-11-09 (114 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1551897] Re: Excessive CPU utilization

2016-03-02 Thread Casey Marshall
I ran pcscd as you suggested, capturing output. Made sure the smart card
was working by using my SSH key. I was then able to reproduce the 100%
cpu condition by plugging in my Logitech USB webcam.

Attached the output, but I redacted the hex dumps before posting here
because I'm not sure if they contain sensitive information. Let me know
if you need the original.

** Attachment added: "pcscd debug output (redacted)"
   
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4587143/+files/pcscd.log.redacted

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

Title:
  Excessive CPU utilization

Status in pcsc-lite package in Ubuntu:
  New

Bug description:
  In xenial, pcscd CPU utilization occasionally goes haywire:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   


  27404 root  20   0  384264   4992   2228 S 100.3  0.0  75:39.03 
/usr/sbin/pcscd --foreground --auto-exit
  

  I get this about once a day since installing xenial. I can't quite
  connect it to any specific event on the system, it just seems to
  happen sporadically -- fan turns on, I run top, and there it is again.

  Never had this issue on same hardware incl. smartcard with trusty.

  I wonder if it might be this? https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=718473

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

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


[Desktop-packages] [Bug 1541375] Re: totem crashed with SIGABRT in g_assertion_message()

2016-03-02 Thread fabianbur
** Information type changed from Private to Public

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

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

Title:
  totem crashed with SIGABRT in g_assertion_message()

Status in totem package in Ubuntu:
  Confirmed

Bug description:
  totem crashed with SIGABRT in g_assertion_message()

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: totem 3.18.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  2 21:47:34 2016
  ExecutablePath: /usr/bin/totem
  ProcCmdline: totem /home/fabianbur/home-servidoratom/torrents/Un\ Gelido\ 
Inverno\ -\ Winter's\ Bone\ (2010)\ 1080p\ BluRay\ Dts\ ITA\ ENG\ Subs\ x264.mkv
  ProcEnviron:
   PATH=(custom, no user)
   LANG=es_EC.UTF-8
   LANGUAGE=es_EC:es
   SHELL=/bin/bash
   TERM=unknown
  Signal: 6
  SourcePackage: totem
  StacktraceTop:
   g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstdvdspu.so
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstdvdspu.so
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstdvdspu.so
  Title: totem crashed with SIGABRT in g_assertion_message()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 902618] Re: Blender crashes when an object is selected

2016-03-02 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/blender/+bug/902618/comments/4
.

** No longer affects: mesa (Ubuntu)

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

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

Title:
  Blender crashes when an object is selected

Status in blender package in Ubuntu:
  Invalid

Bug description:
  Blender crashes nondeterministically, but when it occurs, it's
  immediately following a right-click on an object.  I can right-click
  an unpredictable number of times just fine, but then suddenly poof!
  Blender instantly vanishes and I'm looking at the command line.
  Sometimes the very first right-click after starting Blender will crash
  it.

  All Blender 2.5x and 2.6x show this crash, including a recent 2.6
  compiled from source.All versions of Blender were obtained as
  binaries in tarballs from the official Blender site, except source
  obtained through their svn (or was it git?) repository.  What about
  the official Ubuntu package for Blender?  Tried it too, and it
  crashes.

  I had been using ubuntu 11.04, with xubuntu-desktop added, when this
  problem started.   When 11.10 came out, I hoped it would fix the crash
  by updating some hypothetical buggy library or something, but no it
  didn't.

  It's a Heisenbug in that all attempts to create a small simple scene
  for testing don't lead to a  crash.  Apparently the bug senses when
  I'm doing serious work.  Scenes that do crash have meshes of only a
  few hundred quads, only 3 or 4 lights, and default textures.  There's
  plenty of CPU power and RAM.

  I suspect something other than Blender itself is the problem. Blender
  ran fine for hours at a time, but started crashing about three weeks
  ago.   Memory, disk check out ok, and all other complex software runs
  fine.   From years of experience with computers, software development
  and Linux, I get the impression it's a problem with some library or
  X11 version mismatch, maybe something with the windows manager or
  desktop system, or a misconfiguration of any of these.

  I will be happy to run any special debuggers or diagnostics to get to
  the bottom of this.

  Description:  Ubuntu 11.10
  Release:  11.10


  Strace and gdb running Blender don't reveal much. Here's a gdb run
  that crashed:

  (gdb) r
  Starting program: /home/darenw/SW/bin/blender
  [Thread debugging using libthread_db enabled]
  connect failed: No such file or directory
  ndof: spacenavd not found
  [New Thread 0x717ff700 (LWP 4659)]
  [Thread 0x717ff700 (LWP 4659) exited]
  [New Thread 0x717ff700 (LWP 4660)]
  [New Thread 0x7fffebfff700 (LWP 4661)]
  [New Thread 0x7fffeb7fe700 (LWP 4662)]
  [Thread 0x7fffeb7fe700 (LWP 4662) exited]
  found bundled python: 
/home/darenw/Blender/sw/blender-2.61rc-linux-glibc27-x86_64/2.60/python
  read blend: /home/darenw/proj/WiggleWave/anim/crash_dsw2727B.blend

  Program received signal SIGSEGV, Segmentation fault.
  0x77f1fed8 in ?? ()
  (gdb)

  
  and strace's dying gasp ends with:

  munmap(0x7f9e4a5ca000, 65536) = 0
  ioctl(8, 0x40086409, 0x7fffc51d23c0) = 0
  munmap(0x7f9e4a6ea000, 128) = 0
  ioctl(8, 0x40086409, 0x7fffc51d23c0) = 0
  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
  +++ killed by SIGSEGV +++
  Segmentation fault

  
  Oh yeah, there are debug symbols for the Ubuntu Blender package - let's try 
that:

  (gdb) bt
  #0  0x77ecbed8 in ?? ()
  #1  0x0008beff603e in ?? ()
  #2  0x0100 in ?? ()
  #3  0xffeaebe9 in ?? ()
  #4  0x in ?? ()
  (gdb)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: blender (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Sat Dec 10 11:29:35 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: blender
  UpgradeStatus: Upgraded to oneiric on 2011-10-28 (43 days ago)

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

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


[Desktop-packages] [Bug 1232057] Re: signon-ui crashed with SIGSEGV in malloc_consolidate()

2016-03-02 Thread intuitionist
I reset motorola surfboard sbg6580 wireless modem/router, after 20
seconds modem/router rebooted (I have it setup to search for updates
upon login), system was unable to retrieve updates (I backed up
configuration before resetting modem/router and restored after resetting
it.)  Now I changed prior mirror used gigenet.com to mit's mirror.  I am
starting using it right now.

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

Title:
  signon-ui crashed with SIGSEGV in malloc_consolidate()

Status in signon-ui package in Ubuntu:
  Confirmed

Bug description:
  Crash when logged in.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: signon-ui 0.15daily13.06.25-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  Date: Sat Sep 28 01:19:20 2013
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2013-01-22 (248 days ago)
  InstallationMedia: This
  MarkForUpload: True
  ProcCmdline: /usr/bin/signon-ui
  SegvAnalysis:
   Segfault happened at: 0x7fd3d72c5c0d :   mov
0x8(%r12),%r13
   PC (0x7fd3d72c5c0d) ok
   source "0x8(%r12)" (0xffa788005110) not located in a known VMA region 
(needed readable region)!
   destination "%r13" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: signon-ui
  StacktraceTop:
   malloc_consolidate (av=av@entry=0x7fd3c420) at malloc.c:4088
   _int_malloc (av=av@entry=0x7fd3c420, bytes=bytes@entry=2032) at 
malloc.c:3379
   __libc_calloc (n=, elem_size=) at malloc.c:3190
   g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: signon-ui crashed with SIGSEGV in malloc_consolidate()
  UpgradeStatus: Upgraded to saucy on 2013-07-04 (85 days ago)
  UserGroups: adm autopilot cdrom dialout dip lpadmin plugdev sambashare sudo 
vboxusers

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

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


[Desktop-packages] [Bug 1173787] Re: Delay selection in blender - ubuntu 13.04 - ati 4250

2016-03-02 Thread Christopher M. Penalver
Lucas Romero Di Benedetto, thank you for reporting this and helping make
Ubuntu better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on
January 27, 2014.

Is this reproducible in a supported release?

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

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

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

Title:
  Delay selection in blender - ubuntu 13.04 - ati 4250

Status in Mesa:
  Confirmed
Status in blender package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Delay selection in blender - ubuntu 13.04 - ati 4250

  When you select an object in Blender 2.66a, selection is slow. As if delay. 
No matter the complexity of the object, it is slow when selecting objects. 
(Blender installed from the ubuntu software center)
  My pc is an Acer Aspire 5552-6829 with integrated ATI HD4250 video with 
"Gallium 0.4 on AMD RS880" driver.

  This "error" occurs after installing Ubuntu 13.04 with Unity, but also
  occurs in Ubuntu GNOME 13.04. (all 64 bit) ... Previously not happen
  with Ubuntu 12.04 (kernel 3.2 / 5).

  Since there is an apparent problem or tangible and also am a newbie
  with this from the bugs, I would like to know what I have to analyze
  with "ubuntu-bug" I'm not sure it's the composer of windows or
  X.org.

  * Summary details:
  Ubuntu 13.04 64bit
  Blender 2.66a
  Ati HD4250
  Gallium 0.4 on AMD RS880

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

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


[Desktop-packages] [Bug 1540194] Re: OpenGL stutter and freeze when rotation = Counterclockwise

2016-03-02 Thread Christopher M. Penalver
Me, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1540194

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  OpenGL stutter and freeze when rotation = Counterclockwise

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  My PC is an Intel Core I3 and I use the built-in HD 4600 graphics. My
  display is 1680x1050, connected via DVI-D, Ubuntu version is 15.10
  64-bit.

  I do a fresh Ubuntu install and install and run glmark2. The horse
  spins smoothly.

  I set "System settings -> Displays -> Rotation" to "Counterclockwise",
  rotate my display and run glmark2 again. The horse totally stutters.

  When the rotation is "Counterclockwise" other OpenGL applications will
  even freeze.

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

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


[Desktop-packages] [Bug 1494402] Re: WebKitWebProcess WebKitGtk+ 2.4.8 uses memory without end when visiting some LinkedIn URL

2016-03-02 Thread Christopher M. Penalver
Andreas Gomez, thank you for taking the time to report this bug and
trying to help make Ubuntu better. However, the GNOME3 PPA is not a
software package provided by the official Ubuntu repositories. Because
of this the Ubuntu project can not support or fix your particular bug.
Also, as per https://wiki.ubuntu.com/Releases , Ubuntu 14.10 is EOL as
of July 23, 2015.

If this is reproducible in a supported release, please report this bug
to the provider of the software package. Thanks!

If you are interested in learning more about software repositories and
Ubuntu, check https://help.ubuntu.com/community/Repositories.

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

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

Title:
  WebKitWebProcess WebKitGtk+ 2.4.8 uses memory without end when
  visiting some LinkedIn URL

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.10 with GNOME3 PPA.

  I launch Web, GNOME's default browser and I log in into my LinkedIn
  profile.

  Then, from the top bar I place my pointer over the "Connections" menu so it 
is expanded, once expanded, I click on the "See all" link:
  
https://www.linkedin.com/people/pymk/hub?ref=global-nav=nav_utilities_invites_header

  Upon doing so, the browser freezes and I notice the HD of my computer
  starting to work hard. After checking with "top" the WebKitWebProcess
  is growing its used memory by the Gbs!!! and it doesn't seem to stop.

  This may not be a problem in WKGTK+ but the graphics driver since, after 
repeating the process with a GDB attached to the WebKitWebProcess, GDB states 
that the point in which it exits when manually killing the process is:
  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so

  However, I cannot reproduce with Chromium, FF (of course, the code
  path is completely different).

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

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


[Desktop-packages] [Bug 1544936] Re: PPC: no mpeg-2 video playback

2016-03-02 Thread Christopher M. Penalver
Max May, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1544936

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  PPC: no mpeg-2 video playback

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu Mate 16.04a2 on a PowerBook5,8 (15" G4, 2 GB RAM and
  ATI Radeon 9700 128 MB RAM) with latest updates.

  VLC (media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)) does
  not display video encoded with mpeg-2, only audio. The videos are not
  css-encrypted.

  Other formats like mpeg4, h.264 or h.265 work well with VLC!

  DVD playback with VLC failed too.

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

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


[Desktop-packages] [Bug 1479524] Re: Totem Crashes at launch from missing libwayland-egl

2016-03-02 Thread Christopher M. Penalver
** No longer affects: mesa (Ubuntu Vivid)

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

Title:
  Totem Crashes at launch from missing libwayland-egl

Status in System76:
  New
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in livecd-rootfs source package in Trusty:
  Fix Released
Status in mesa source package in Trusty:
  Invalid
Status in mesa-lts-vivid source package in Trusty:
  Confirmed
Status in livecd-rootfs source package in Wily:
  Invalid
Status in mesa source package in Wily:
  Confirmed

Bug description:
  When trying to open a video file from Ubuntu 14.04.3 Daily Image
  (2015-07-29), it will not open. If totem is manually run from the
  terminal, this error occurs:

  totem: error while loading shared libraries: libwayland-egl.so.1:
  cannot open shared object file: No such file or directory

  Using Ubuntu 14.04.3 LTS (Daily Image from: 2015-07-29) 64-bit
  Totem version: 3.10.1-1ubuntu4

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: totem 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 29 15:11:30 2015
  InstallationDate: Installed on 2015-07-29 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150729)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1547762] Re: "SSL Protocol Error" in Chromium for several Google web sites after installing Ubuntu Security Updates for libnss3

2016-03-02 Thread medina9000
Still a problem on Chromium Version 45.0.2454.101 Ubuntu 15.10 (64-bit)

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

Title:
  "SSL Protocol Error" in Chromium for several Google web sites after
  installing Ubuntu Security Updates for libnss3

Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  Scenario: Laptop computer running Ubuntu 12.04.5 LTS (64-bit)
  ("Precise Pangolin")

  Issue: In the Chromium web browser - "Version 37.0.2062.120 Ubuntu
  12.04 (281580) (64-bit)" - after having installed the Ubuntu security
  Updates that were available on Feb 18, 2016, I get the following error
  while trying to access some Google Web sites (e.g.
  https://www.google.com ; https://plus.google.com/ ;
  https://hangouts.google.com/ ):

    
  SSL connection error

  Unable to make a secure connection to the server. This may be a problem with 
the server, or it may be requiring a client authentication certificate that you 
don't have.  
  Error code: ERR_SSL_PROTOCOL_ERROR
  

  Those web sites still appear correctly in the same computer, using
  other web browsers, namely Google Chrome - "Version 48.0.2564.109
  (64-bit)" - or Mozilla Firefox - version "44.0.2"

  The updates installed on Feb 18, 2016 were the following:

  libnss3:amd64 (3.19.2.1-0ubuntu0.12.04.2, 3.21-0ubuntu0.12.04.1)  
  libnss3:i386 (3.19.2.1-0ubuntu0.12.04.2, 3.21-0ubuntu0.12.04.1)  
  libnss3-1d:amd64 (3.19.2.1-0ubuntu0.12.04.2, 3.21-0ubuntu0.12.04.1)

  "libnss3" is listed at
  http://packages.ubuntu.com/search?keywords=libnss3 as being the
  "Network Security Service libraries", so I believe it's possible that
  update may be related to this issue that I'm facing.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: chromium-browser 37.0.2062.120-0ubuntu0.12.04.1~pkg917
  ProcVersionSignature: Ubuntu 3.13.0-77.121~precise1-generic 3.13.11-ckt32
  Uname: Linux 3.13.0-77-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  Date: Sat Feb 20 03:37:51 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.chromium.browser: [deleted]

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

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


[Desktop-packages] [Bug 1552417] Re: [X1100] Flickering after resume from RAM

2016-03-02 Thread Christopher M. Penalver
Tommy Trussell, could you please provide the missing information from
https://wiki.ubuntu.com/DebuggingKernelSuspend ?

** Tags added: 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/1552417

Title:
  [X1100] Flickering after resume from RAM

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce :
  - choose suspend
  - resume from ram
  => the screen will flicker while CPU activity is not high

  WORKAROUND: Launch an infinite loop that consume CPU :
  $ while true; do echo >/dev/null; done

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  2 20:00:24 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:009f]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  Lsusb:
   Bus 001 Device 002: ID 0951:160b Kingston Technology
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5100
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- BOOT_IMAGE=/casper/vmlinuz
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5100
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Mar  2 13:50:49 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1454774] Re: r600_dri.so crashes with a Segmentation Fault (SIGSEGV)

2016-03-02 Thread Christopher M. Penalver
Jason Chagas, thank you for reporting this and helping make Ubuntu
better.

To see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: latest-bios-eqkt21aus

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

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

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

Title:
  r600_dri.so crashes with a Segmentation Fault (SIGSEGV)

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  r600_dri.so crashes with a Segmentation Fault (SIGSEGV). I noticed it
  usually happens when running the Firefox on the Google Maps website.
  It is inconsistent, however, and it may require a few tries before
  Firefox quits. Here is how I was able to trace the problem:

  1) Run firefox in debub mode:

  %  firefox -g   //launch firefox in debug mode
  (gdb) handle SIGPIPE nostop//disable GDB trapping of SIGPIPE messages
  (gdb) run 

  2) Access http://www.google.com/maps and entering addresses a few
  times until it crashes

  3) GDB backtrace:

  Program received signal SIGSEGV, Segmentation fault.
  0x7fff892a2a2f in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
  (gdb) bt
  #0  0x7fff892a2a2f in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
  #1  0x7fff8929ea27 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
  #2  0x7fff892a57ff in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
  #3  0x71e60446 in ?? () from /usr/lib/firefox/libxul.so
  #4  0x7240f36a in ?? () from /usr/lib/firefox/libxul.so
  #5  0x7242fc31 in ?? () from /usr/lib/firefox/libxul.so
  #6  0x7240f594 in ?? () from /usr/lib/firefox/libxul.so
  #7  0x723899fc in ?? () from /usr/lib/firefox/libxul.so
  #8  0x723f20fb in ?? () from /usr/lib/firefox/libxul.so
  #9  0x73404e58 in ?? () from /usr/lib/firefox/libxul.so
  #10 0x733ffa57 in ?? () from /usr/lib/firefox/libxul.so
  #11 0x73404a71 in ?? () from /usr/lib/firefox/libxul.so
  #12 0x73404cf6 in ?? () from /usr/lib/firefox/libxul.so
  #13 0x73405881 in ?? () from /usr/lib/firefox/libxul.so
  #14 0x731b266d in ?? () from /usr/lib/firefox/libxul.so
  #15 0x77fe75d0 in ?? ()
  #16 0x0602 in ?? ()
  #17 0x7fff8470 in ?? ()
  #18 0xfff9 in ?? ()
  #19 0x754a0a20 in ?? () from /usr/lib/firefox/libxul.so
  #20 0x7fffdea51a30 in ?? ()
  #21 0x7fffbe985a94 in ?? ()
  #22 0x0482 in ?? ()
  #23 0x7fff8510 in ?? ()
  #24 0x7fffb666b790 in ?? ()
  #25 0x0001 in ?? ()
  #26 0x7fff84b8 in ?? ()
  #27 0xfffc7fff73f8bf40 in ?? ()
  #28 0xfffc7fff73f7c7e0 in ?? ()
  #29 0xfff880004500 in ?? ()
  #30 0x7fff8550 in ?? ()
  #31 0x7fffb666b790 in ?? ()
  #32 0x7fffb8e18b08 in ?? ()
  #33 0x0681 in ?? ()
  #34 0xfff880004500 in ?? ()
  #35 0xfffc7fff73f7c7e0 in ?? ()
  #36 0xfffc7fff73f8bf40 in ?? ()
  #37 0xfffc7fffdf539f18 in ?? ()
  #38 0xfff98000 in ?? ()
  #39 0x7fffdea00b80 in ?? ()
  #40 0x0068 in ?? ()
  #41 0x7fff73f7c2e0 in ?? ()
  #42 0x7fffb8e14308 in ?? ()
  #43 0xfff98000 in ?? ()
  #44 0x in ?? ()
  (gdb) 

  

  I built mesa_10.1.3 with debug symbols, replaced /usr/lib/x86_64
  -linux-gnu/dri/r600_dri.so, ran Firefox again as described above and
  here is where it crashed:

  Program received signal SIGSEGV, Segmentation fault.
  0x0002 in ?? ()
  (gdb) bt
  #0  0x0002 in ?? ()
  #1  0x7fffaf5b7ac4 in pipe_sampler_view_reference (ptr=0x7fffaba98400, 
  view=0x0) at ../../src/gallium/auxiliary/util/u_inlines.h:151
  #2  0x7fffaf5b80e0 in st_get_texture_sampler_view_from_stobj (
  stObj=0x7fffaba98000, pipe=0x7fffb33ed000, samp=0x7fffaba98040, 
  format=PIPE_FORMAT_R8G8B8A8_UNORM) at state_tracker/st_atom_texture.c:209
  #3  0x7fffaf5b82cc in update_single_texture (st=0x7fffb4714000, 
  sampler_view=0x7fff69e8, texUnit=3)
  at state_tracker/st_atom_texture.c:272
  #4  0x7fffaf5b8372 in update_textures (st=0x7fffb4714000, shader_stage=1, 
  prog=0x7fffb555c800, max_units=16, sampler_views=0x7fffb4714990, 
  num_textures=0x7fffb4714b14) at state_tracker/st_atom_texture.c:305
  #5  0x7fffaf5b84ec in update_fragment_textures (st=0x7fffb4714000)
  at state_tracker/st_atom_texture.c:355
  #6  0x7fffaf5b1401 in st_validate_state (st=0x7fffb4714000)
  at state_tracker/st_atom.c:201
  #7  0x7fffaf5bddb3 in st_Clear (ctx=0x7fffb4f7c000, mask=304)
  at state_tracker/st_cb_clear.c:443
  #8  0x7fffaf42e1c3 in _mesa_Clear (mask=17664) at main/clear.c:206
  #9  0x71e60446 in ?? () from 

[Desktop-packages] [Bug 1552417] Re: [X1100] Flickering after resume from RAM

2016-03-02 Thread Tommy Trussell
I just booted from today's (02 March 2016) xenial-desktop-amd64.iso. I
had trouble getting the machine to suspend, but once it did and resumed
from suspend, it showed the same flickering screen behavior.

If you need an apport bug collection or any other data from this image,
it should work. Let me know

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

Title:
  [X1100] Flickering after resume from RAM

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce :
  - choose suspend
  - resume from ram
  => the screen will flicker while CPU activity is not high

  WORKAROUND: Launch an infinite loop that consume CPU :
  $ while true; do echo >/dev/null; done

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  2 20:00:24 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:009f]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  Lsusb:
   Bus 001 Device 002: ID 0951:160b Kingston Technology
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5100
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- BOOT_IMAGE=/casper/vmlinuz
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5100
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Mar  2 13:50:49 2016
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1079011] Re: stellarium assert failure: nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

2016-03-02 Thread Christopher M. Penalver
John Harrington, thank you for reporting this and helping make Ubuntu
better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 12.10 reached EOL on May
16, 2014.

Is this reproducible with a supported release?

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

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

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

Title:
  stellarium assert failure:  nv10_state_fb.c:50: get_rt_format:
  Assertion `0' failed.

Status in flightgear package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete
Status in stellarium package in Ubuntu:
  Invalid

Bug description:
  Stellarium crashes a few seconds after displaying the startup screen
  with this message in terminal:

  nv10_state_fb.c:50: get_rt_format: Assertion `0' failed.

  I have an nvidia GeForce4 MX 4000 video card, and have installed
  libgl1-mesa-dri and libgl1-mesa-dri-experimental, version
  9.0-0ubuntu1.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: stellarium 0.11.3-1
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic i686
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: i386
  Date: Wed Nov 14 22:52:36 2012
  InstallationDate: Installed on 2012-04-05 (224 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stellarium
  UpgradeStatus: Upgraded to quantal on 2012-10-20 (25 days ago)

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

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


[Desktop-packages] [Bug 1429137] Re: Chrome crash on startup, after Kubuntu 14.04.2 fresh install, may be related to bug 1424263, which also affects me

2016-03-02 Thread Christopher M. Penalver
brancoliticus, thank you for reporting this and helping make Ubuntu
better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1429137

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  Chrome crash on startup, after Kubuntu 14.04.2 fresh install, may be
  related to bug 1424263, which also affects me

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  I downloaded and installed Google Chrome 64 bit official deb, and when
  I get this blowout in the command line:

  $ google-chrome-stable
  [1:1:0306/095859:ERROR:image_metadata_extractor.cc(111)] Couldn't load 
libexif.
  [7748:7748:0306/095859:ERROR:browser_main_loop.cc(198)] GTK theme error: 
Unable to locate theme engine in module_path: "oxygen-gtk",
  [7748:7748:0306/095859:ERROR:browser_main_loop.cc(198)] GTK theme error: 
Unable to locate theme engine in module_path: "oxygen-gtk",
  Aborted (core dumped)

  Since I have not found the problem reported somewhere else in Google
  Chrome's product forum, I posted a bug report:
  https://productforums.google.com/forum/#!category-
  topic/chrome/report-a-problem-and-get-troubleshooting-
  help/linux/Stable/LniyR9bsfus, but then I also tried to install Steam
  and ended up on the page with the bug number 1424263:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424263.

  I guess the two bugs may be related in the sense that the update of
  the Kubuntu install disk may have triggered them both.

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

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


[Desktop-packages] [Bug 1407623] Re: Font rendering issue with Mesa 10.5-dev

2016-03-02 Thread Christopher M. Penalver
Alexander, thank you for reporting this and helping make Ubuntu better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 14.10 reached EOL on
July 23, 2015.

Is this reproducible in a supported release?

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

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

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

Title:
  Font rendering issue with Mesa 10.5-dev

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  I have a font rendering issue in a Firefox 34. Using Ubuntu 14.10
  (kernel 3.18.1), Mesa 10.5-dev
  (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) and R9
  270 videocard.

  Here's detailed report from another person:
  https://bbs.archlinux.org/viewtopic.php?id=187100

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

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


[Desktop-packages] [Bug 1468027] Re: change default CJK fonts to Noto CJK

2016-03-02 Thread tomoe_musashi
Just played with the config file for fonts-noto-cjk that @Gunnar posted above.
Its works great in non-Chinese locale, but it lacks monospace font support.
this should be added:

 monospace
 
 Noto Sans Mono CJK SC
 Noto Sans Mono CJK TC
 
 

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

Title:
  change default CJK fonts to Noto CJK

Status in fonts-noto-cjk package in Ubuntu:
  Fix Committed
Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  just realize that fonts-noto-cjk is available in the repository, finally its 
packaged.
  i don't really know about korean community.
  But for Chinese and Japanese community, i think that the answer is clear.
  noto-cjk is definitely better what we had before, like fonts- wqy and 
fonts-droid.
  Android community had received these complains for years, finally they got 
them fixed on lollipop.
  Fedora also set it as default chinese font start from F21.
  and of course, i still hope that ubuntu could drop those 69-language-selector 
fontconfig files, just like what F13 did.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1468027/+subscriptions

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


[Desktop-packages] [Bug 1388349] Re: Crashes X when viewing certain websites

2016-03-02 Thread Christopher M. Penalver
m, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1388349

** No longer affects: chromium-browser (Ubuntu)

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

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

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

Title:
  Crashes X when viewing certain websites

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Just visiting some URLs will crash X and bring down the whole system
  without warning. Reproducible example: visit http://ello.co/jondcook
  in Chromium and the GPU will crash.

  Ubuntu 12.04.5 LTS

  [75195.004056] [drm] stuck on render ring
  [75195.004067] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [75195.004071] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [75195.004075] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [75195.004078] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [75195.004082] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [75195.005398] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo 
(0x2088000 ctx 0) at 0x2089954
  [75195.512106] [drm:i915_reset] *ERROR* Failed to reset chip.
  [75200.348321] Watchdog[5421]: segfault at 0 ip aff4a4c8 sp ad0c4cf0 error 6 
in libcontent.so[af72f000+11ee000]
  [75205.036042] [drm:i915_gem_wait_for_error] *ERROR* Timed out waiting for 
the gpu reset to complete
  [75205.092053] [drm] GMBUS [i915 gmbus vga] timed out, falling back to bit 
banging on pin 2
  [75205.119530] [ cut here ]
  [75205.119593] WARNING: CPU: 0 PID: 1931 at 
/build/buildd/linux-lts-trusty-3.13.0/drivers/gpu/drm/i915/intel_display.c:922 
assert_pll+0x7a/0x80 [i915]()
  [75205.119597] PLL state assertion failure (expected on, current off)
  [75205.119600] Modules linked in: usb_storage nls_iso8859_1 serpent_sse2_i586 
ablk_helper cryptd glue_helper lrw serpent_generic twofish_generic twofish_i586 
twofish_common xts gf128mul hidp hid nvram pci_stub vboxpci(OX) vboxnetadp(OX) 
vboxnetflt(OX) vboxdrv(OX) ctr ccm vsock zram(C) bnep rfcomm parport_pc ppdev 
binfmt_misc dm_crypt joydev xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 
btusb bluetooth ipt_REJECT xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_state ip6table_filter ip6_tables 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat 
nf_conntrack_ftp nf_conntrack iptable_filter snd_hda_codec_si3054 
snd_hda_codec_realtek ip_tables x_tables snd_hda_intel hp_wmi snd_hda_codec 
sparse_keymap snd_hwdep arc4 snd_pcm r852 snd_seq_midi snd_rawmidi 
snd_seq_midi_event iwl3945 sm_common nand iwlegacy mtd snd_seq nand_ids 
nand_bch snd_timer bch r592 mac80211 nand_ecc psmouse memstick lpc_ich 
serio_raw snd_seq_device cfg80211 snd soun
 dcore snd_page_alloc mac_hid coretemp lp parport i915 firewire_ohci 
drm_kms_helper firewire_core drm ahci crc_itu_t libahci i2c_algo_bit r8169 
sdhci_pci sdhci mii video wmi
  [75205.119720] CPU: 0 PID: 1931 Comm: upowerd Tainted: G C OX 
3.13.0-39-generic #66~precise1-Ubuntu
  [75205.119724] Hardware name: Hewlett-Packard Presario V6500 Notebook PC  
  /30CC, BIOS F.5A  03/22/2010
  [75205.119727]    ee449c50 c1683110 f89adb0c ee449c80 
c1059c54 f89afb04
  [75205.119737]  ee449cac 078b f89adb0c 039a f895e0fa f895e0fa 
0001 0001
  [75205.119746]  0001 ee449c98 c1059d13 0009 ee449c90 f89afb04 
ee449cac ee449cbc
  [75205.119755] Call Trace:
  [75205.119766]  [] dump_stack+0x41/0x52
  [75205.119776]  [] warn_slowpath_common+0x84/0xa0
  [75205.119813]  [] ? assert_pll+0x7a/0x80 [i915]
  [75205.119847]  [] ? assert_pll+0x7a/0x80 [i915]
  [75205.119852]  [] warn_slowpath_fmt+0x33/0x40
  [75205.119887]  [] assert_pll+0x7a/0x80 [i915]
  [75205.119928]  [] intel_crtc_load_lut+0x194/0x1a0 [i915]
  [75205.119961]  [] ? i9xx_enable_pll+0x11c/0x190 [i915]
  [75205.119994]  [] i9xx_crtc_enable+0xa8/0x150 [i915]
  [75205.120059]  [] __intel_set_mode+0x244/0x2f0 [i915]
  [75205.120106]  [] ? 
intel_framebuffer_create_for_mode.constprop.57+0xa3/0xb0 [i915]
  [75205.120150]  [] intel_set_mode+0x27/0x40 [i915]
  [75205.120189]  [] intel_get_load_detect_pipe+0x21d/0x300 [i915]
  [75205.120237]  [] intel_tv_detect+0x125/0x230 [i915]
  [75205.120252]  [] ? lockref_get_not_dead+0x11/0x40
  [75205.120280]  [] status_show+0x3d/0x80 [drm]
  [75205.120286]  [] ? __kmalloc+0xa4/0x210
  [75205.120310]  [] ? dpms_show+0x60/0x60 [drm]
  

[Desktop-packages] [Bug 1388612] Re: [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

2016-03-02 Thread Christopher M. Penalver
Andrea Bini, thank you for reporting this and helping make Ubuntu
better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 14.10 reached EOL on
July 23, 2015.

Is this reproducible on a supported release?

** Tags added: latest-bios-a15

** Changed in: mesa (Ubuntu)
   Importance: High => Medium

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

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

Title:
  [GM965] GPU lockup running OpenGL applications on Dell Vostro 1510

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Hello, I'm suffering a GPU lockup problem with Ubuntu 14.10 64-bit on
  a Dell Vostro 1510 laptop with Intel graphics. The problem used to
  arise also with Ubuntu 14.04 and is always reproducible with glmark2
  on the LiveCD. Just to run the "ideas" benchmark of glmark2 to trigger
  the lockup in few seconds (glmark2 -b ideas). Other OpenGL
  applications also causes the lockup (e.g. FooBillard++, my self-made
  SDL applications). Memory test passed, BIOS at the latest version.
  Don't know if the following is a good point but I think that the
  problem is not caused by a failing hardware because it works fine on
  Windows. I tried with the latest Intel upstream kernel
  (http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-
  next/current/) and upstream X.org (https://launchpad.net/~xorg-
  edgers/+archive/ubuntu/ppa), no change.

  [Personal Notes]
  I'm new to Ubuntu's world, I hope I've done things right, if not please tell 
me and I will resend the report or supply more information. I've created the 
bug report with "ubuntu-bug xorg --save" from another machine via SSH while the 
sick machine was frozen. It seemed to me more logical than using ubuntu-bug 
directly when the system is working fine. I've collected other information via 
SSH during the same lockup: dmesg, Xorg.0.log, i915_error_state. The latter was 
added as attachment.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sun Nov  2 19:24:31 2014
  DistUpgraded: 2014-10-25 12:05:51,479 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.13.0-37-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.16.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0273]
 Subsystem: Dell Device [1028:0273]
  InstallationDate: Installed on 2014-10-11 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Vostro1510
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic 
root=UUID=9b3612b7-c4bf-4840-885b-9fae75d6342c ro splash quiet vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to utopic on 2014-10-25 (8 days ago)
  dmi.bios.date: 03/18/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0M277C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd03/18/2009:svnDellInc.:pnVostro1510:pvrNull:rvnDellInc.:rn0M277C:rvr:cvnDellInc.:ct8:cvrN/A:
  dmi.product.name: Vostro1510
  dmi.product.version: Null
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Sun Nov  2 18:41:51 2014
  xserver.configfile: default
  xserver.errors:
   intel(0): Detected a hung GPU, disabling acceleration.
   intel(0): When reporting this, please include /sys/class/drm/card0/error and 
the full dmesg.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   15873 
   vendor   

[Desktop-packages] [Bug 1538596] Re: touchpad stops on acer 131t

2016-03-02 Thread bhikkhu subhuti
This bug is caused by the bios being in "advanced mode"
Windows needs Advanced mode and installs a driver.  The bios says, "you need 
this driver or it may not work"
Perhaps this driver should be added to the kernal?

I still think this is a bug, because people will install ubuntu and
think this is a piece of junk (like I did, but I am more patient)

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

Title:
  touchpad stops on acer 131t

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

Bug description:
  Hello,
  I have a new laptop.  Very new model.  acer 131t c1yf model 32 gb hard drive 
and 2 gb ram.
  Often the touchpad whimps out.  Sometimes I can start it again by going into 
the mouse applet.  Sometimes not.  
  Sometimes if I plug in the mouse and unplug it, then it helps to get it back 
up.  
  Sometimes it does not work and reboot is needed.

  Note.  This is a touch pad model too.
  I have no idea on how to find the package at fault for this, so I picked the 
mouse applet.

  Bhikkhu Subhuti

  I hope this helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity-control-center 15.04.0+15.10.20150923-0ubuntu1
  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 Jan 27 21:31:27 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-01-25 (2 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1293281] Re: when creating a hidden folder it is created but also creates untitled folder

2016-03-02 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Confirmed => Fix Released

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

Title:
  when creating a hidden folder it is created but also creates untitled
  folder

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  When I create a new hidden folder like ".icons"  In a folder that is
  currently not set to show hidden folders it is created but also
  creates an "Untitled Folder" and that is all the user sees, and to
  some it may appear as if it did not work until they look with hidden
  folders viewable. It doesn't create the untitled one if hidden folders
  are viewable when you create the hidden folder.

  On Ubuntu 14.04 64-bit updated to 3/16/2014

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

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


[Desktop-packages] [Bug 1382987] Re: Firefox crashes when accessing Google Maps, likely related to graphics driver

2016-03-02 Thread Christopher M. Penalver
Fabrizio Gennari, thank you for reporting this and helping make Ubuntu
better.

To see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: bios-outdated-11.b

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

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

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

Title:
   Firefox crashes when accessing Google Maps, likely related to
  graphics driver

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu 14.04 and Firefox 33.0.

  When accessing the new Google Maps at https://www.google.com/maps/ the
  second time in a session, Firefox crashes. From the crash report, the
  crash occurs in the graphics driver r600_dri.so.

  This is a call stack, taken from Mozilla's crash report

  1 r600_dri.so r600_dri.so@0x168a34
  2 libgallium.so.0.0.0 libgallium.so.0.0.0@0x327e3 
  3 r600_dri.so r600_dri.so@0x5cba3f
  4 r600_dri.so r600_dri.so@0x5cbaa7
  5 r600_dri.so r600_dri.so@0x164a26
  6 r600_dri.so r600_dri.so@0x16b7fe
  7 r600_dri.so r600_dri.so@0xf73f3

  The bug is also open upstream as
  https://bugs.freedesktop.org/show_bug.cgi?id=82109

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,move,place,vpswitch,regex,resize,gnomecompat,mousepoll,session,grid,animation,workarounds,unitymtgrabhandles,wall,wobbly,fade,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Oct 19 17:17:28 2014
  DistUpgraded: 2014-04-25 22:33:51,162 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:]
  InstallationDate: Installed on 2010-11-07 (1442 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  MachineType: MSI MS-7623
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=10b9da6b-d735-48a7-bc45-2c1fc81183dd ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to trusty on 2014-04-25 (176 days ago)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V11.5
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 880GM-E41 (MS-7623)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV11.5:bd08/10/2010:svnMSI:pnMS-7623:pvr2.0:rvnMSI:rn880GM-E41(MS-7623):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7623
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Oct 19 10:01:46 2014
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputspca561  KEYBOARD, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputImPS/2 Generic Wheel Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.1
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1376687] Re: Google Chrome crashes in i965_dri.so

2016-03-02 Thread Christopher M. Penalver
Kostya Vasilyev, thank you for reporting this and helping make Ubuntu
better. However, your crash report is manually attached.

Please follow these instructions to have apport report a new bug about your 
crash that can be dealt with by the automatic retracer. First, execute at a 
terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y 
dist-upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in 
/etc/default/apport and restart. Now reproduce the crash, then open a terminal, 
navigate to your /var/crash directory and file your report with:
sudo ubuntu-bug /var/crash/_my_crash_report.crash

where _my_crash_report.crash is the crash you would like to report. By
default, this sends the crash to the Ubuntu Error Tracker
infrastructure, which is different than Launchpad. For more on this,
please see https://wiki.ubuntu.com/ErrorTracker .

However, if after doing this you would still like to have a crash report posted 
to Launchpad, for example to ease triage and add others to your report, one 
would need to open the following file via a terminal:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and file the crash report via:
sudo ubuntu-bug /var/crash/FILENAME.crash

Where FILENAME is the actual name of the file found in the folder.

However, this report is being closed since the process outlined above
will deal with this issue more efficiently.

Also, please do not attach your crash report manually to this report and
reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

** Attachment removed: "01_opt_google_chrome_chrome.1000.crash.nocore"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1376687/+attachment/466/+files/01_opt_google_chrome_chrome.1000.crash.nocore

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

Title:
  Google Chrome crashes in i965_dri.so

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Since installing the Ubuntu 14.10 beta update, I see Google Chrome
  crash on startup.

  This happens about 1/3 of the time.

  The issue doesn't exist with same Chrome version, on same hardware, in
  Fedora 20 -- and did not exist prior to updating to Ubuntu 14.10 beta
  (i.e. 14.04).

  There have been a few large Ubuntu updates since I installed the beta,
  but the issue continues to happen.

  Hardware: Intel 4770 with built-in video, dual monitor, 16 GB RAM,
  SSDs, 64-bit mode.

  Software: XUbuntu

  A detailed crash report is attached.

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

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


[Desktop-packages] [Bug 1540372] Re: [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or crackling sound

2016-03-02 Thread Raymond
Linux 3.19.0-47-generic x86_64

Seem different from 16.04.4 kernel 4.x

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

Title:
  [Intel DP35DP, SigmaTel STAC9271D, Green Speaker, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  I cant record or play on my sound card ubuntu 14.04.1

  Alsa is detecting the sound card
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: STAC9271D Analog [STAC9271D Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: Intel [HDA Intel], device 1: STAC9271D Digital [STAC9271D Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0

  
  but PulseAudio is not detecting the card 

  attached the log file

  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-47.53~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-47-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tuned  1851 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb  1 15:09:35 2016
  InstallationDate: Installed on 2015-10-26 (98 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Green Speaker, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [, SigmaTel STAC9271D, Green Speaker, Rear] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DP35DP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD81073-207
  dmi.chassis.type: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0293.2007.1002.1519:bd10/02/2007:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-207:cvn:ct2:cvr:
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-01-29T17:09:52.179523

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

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


[Desktop-packages] [Bug 1338248] Re: bluez-test-device fails

2016-03-02 Thread Christopher M. Penalver
** Package changed: mesa (Ubuntu) => bluez (Ubuntu)

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

Title:
  bluez-test-device fails

Status in bluez package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 14.04 64 bit on dell xps13 (Sputnik) with intel i7 and 
Intel® Dual Band Wireless-AC 7260 + Bluetooth 4.0.
  I enter "sudo bluez-test-device trusted E8:2A:EA:5C:23:66 yes"  
  then I get the error messages attached below.

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

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


[Desktop-packages] [Bug 1322589] Re: Screen flickers when running game Sins of a Solar Empire

2016-03-02 Thread Christopher M. Penalver
Carl Englund, thank you for reporting this and helping make Ubuntu
better.

To see if this is resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: latest-bios-1.19

** Tags added: utopic

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

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

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

Title:
  Screen flickers when running game Sins of a Solar Empire

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Problem appeared after update from Ubuntu 13.10 to 14.04. Game worked
  fine in Saucy with both radeon and fglrx. Now in Trusty only works
  with fglrx. Using radeon driver gives heavy flickering (about 0,5s
  intervals) when running the game (through PlayOnLinux/WINE). I expect
  some other games of other users will have the same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libegl1-mesa 10.1.0-4ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,regex,animation,workarounds,vpswitch,move,imgpng,expo,compiztoolbox,snap,unitymtgrabhandles,mousepoll,resize,grid,wall,fade,gnomecompat,place,ezoom,session,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri May 23 14:36:12 2014
  DistUpgraded: 2014-04-19 17:11:14,002 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 14.03.01, 3.11.0-19-generic, x86_64: installed
   fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
   vboxhost, 4.3.12, 3.13.0-24-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobility Radeon HD 5650 [1025:0364]
  InstallationDate: Installed on 2010-06-07 (1445 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  MachineType: Acer Aspire 3820
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=8b7cae99-dae3-4d14-bbd3-24f82a9e0b57 ro quiet splash 
rootflags=data=writeback acpi_osi=Linux vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (33 days ago)
  dmi.bios.date: 10/27/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.19
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: JM31_CP
  dmi.board.vendor: Acer
  dmi.board.version: V1.19
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.19
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd10/27/2010:svnAcer:pnAspire3820:pvrV1.19:rvnAcer:rnJM31_CP:rvrV1.19:cvnAcer:ct10:cvrV1.19:
  dmi.product.name: Aspire 3820
  dmi.product.version: V1.19
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri May 23 13:44:19 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1334721] Re: Multicore rendering causes performance issues

2016-03-02 Thread Christopher M. Penalver
Patrik Bubák, thank you for reporting this and helping make Ubuntu
better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1334721

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  Multicore rendering causes performance issues

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  https://github.com/ValveSoftware/Source-1-Games/issues/1739

  I've had an issue on my system with most games with the Multicore
  Rendering feature, even though disabled in most cases the performance
  for the same game on Windows 7 was significantly lower, the game was
  unplayable.

  The current version I'm running is 10.1.3 on Ubuntu 14.04 x64.

  I'll provide the necessary logs just post the commands for them. It
  was difficult for me to trace the exact package via "ubuntu-bug".

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

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


[Desktop-packages] [Bug 1303906] Re: mesa 10 (and 9) has problems with KDE and intel video

2016-03-02 Thread Christopher M. Penalver
Tommy_CZ, thank you for reporting this and helping make Ubuntu better.

To see if this is already resolved, could you please test Kubuntu 15.10
via https://www.kubuntu.org/getkubuntu/ and advise to the results?

** Tags added: latest-bios-elkt31aus

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

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

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

Title:
  mesa 10 (and 9) has problems with KDE and intel video

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Hi, I can see white stripes corruption, sometimes it totally break
  (fragments of windows are all over the desktop), in Ubuntu 12.04
  downgrade to mesa 8 helped, here in 14.04 I cannot do that.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libegl1-mesa 10.1.0-4ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: kwin
  CurrentDesktop: KDE
  Date: Mon Apr  7 18:33:56 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: kubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:365e]
  InstallationDate: Installed on 2014-04-07 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140406)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic 
root=UUID=abd146fd-217f-4f15-956c-cb4123798539 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr  7 18:24:16 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8192 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

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

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


[Desktop-packages] [Bug 1551385] Re: No sound on ASUS Xonar DGX Soundcard (16.04)

2016-03-02 Thread Raymond
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa?id=527078523815587bfd021bc1d10782403e9b3e84

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

Title:
  No sound on ASUS Xonar DGX Soundcard (16.04)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  On Ubuntu 16.04 LTS (Alpha), with the latest package updates (28/02/2015), 
Linux 4.4 and PulseAudio 8.0, I can't play any sound on my ASUS Xonar DGX. 
Tested with the app to test speakers, Firefox, VLC, and checked with 
pavucontrol, the progress bar indicate that a sound is played on the card, but 
no sound on the speakers.

  I report this bug because it works on the same version with the
  integrated card of my motherboard. (ASUS H87-PLUS)

  On Ubuntu 14.04 (PulseAudio 4.0), the sound work correctly (with all
  defaults params)

  The speakers connected are the Logitech Z9600 (by 3 jacks), and I
  precise that they are correctly plugged in, etc..., it works when I
  connect it to the integrated sound card of my motherboard (and if I
  use Ubuntu 14.04 LTS)

  I don't know if it's a normal development bug, but in doubt I report it.
  Thank you,
  Valentin Crône

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

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


[Desktop-packages] [Bug 1275042] Re: Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC

2016-03-02 Thread Christopher M. Penalver
Christian Zigotzky, thank you for reporting this and helping make Ubuntu
better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1275042

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

Title:
  Wrong colors with Mesa 9.2 and Mesa 10.0 on Lubuntu 14.04 PowerPC

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and
  on Lubuntu 14.04. Unfortunately all have issued false colors in games.
  They appear to be ABGR instead of RGBA, thus blue becomes green, red
  becomes alpha etc.

  Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem.

  The transitional solution is to install the old Mesa 8.0.X with "Force
  Version" with the Synaptic package manager on new distributions.

  We had a problem with wrong colors in SuperTuxKart 0.8 last year. The
  Irrlicht guys have released a little hack for Irrlicht on Linux PPC
  (http://irrlicht.sourceforge.net/forum/viewtopic.php?f=7=48577).
  They told me that is a driver bug, and that workaround costs
  performance and RAM. Unfortunately this workaround isn't suitable for
  Mesa 9.2 and higher. At this time we have to install Mesa 9.1.X and
  lower on new Linux distributions like Lubuntu 13.10, Lubuntu 14.04,
  Debian Sid etc. It would be nice to solve this issue because we don't
  need the workaround in the future.

  Hardware:

  AmigaOne X1000 (Nemo)
  PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU
  "Xena" 500MHz XMOS XS1-L2 124
  8GB DDR2 SDRAM
  HIS Radeon HD 6870, 1 GB RAM
  OCZ600MXSP 600 Switching power supply
  RTL 8139/8139C/8139C+ network card
  TSSTcorp CDDVDW SH-224BB dvd drive
  ATA ST2000DM001-9YN1 SEAGATE HD
  ATA ESA 3SF1240GB HD

  More information:

  http://en.wikipedia.org/wiki/AmigaOne_X1000
  http://www.supertuxkart-amiga.de/amiga/x1000.html

  Rgds,
  Christian

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

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


[Desktop-packages] [Bug 1303101] Re: Stellarium + Trusty 14.04 : white screen

2016-03-02 Thread Christopher M. Penalver
*** This bug is a duplicate of bug 1286516 ***
https://bugs.launchpad.net/bugs/1286516

** This bug has been marked a duplicate of bug 1286516
   [gen2 regression mesa ] Stellarium + Trusty 14.04: white screen

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

Title:
  Stellarium + Trusty 14.04 : white screen

Status in mesa package in Ubuntu:
  New

Bug description:
  Hello,

  The bug is with OpenGL (mesa), it is stated here:

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

  Thanks.

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

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


[Desktop-packages] [Bug 1283820] Re: content of windows (and desktop) appear black when using kwin, but not with kwin_gles - intel graphics

2016-03-02 Thread Christopher M. Penalver
avlas, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p mesa 1283820

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

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

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

Title:
  content of windows (and desktop) appear black when using kwin, but not
  with kwin_gles - intel graphics

Status in KDE Base Workspace:
  Unknown
Status in kde-workspace package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  
  When I start a session all my windows appear in black as well as my desktop 
if using kwin. This behavior is not entirely deterministic, it occurs about 75% 
of the times. I have an intel graphic card, and same thing happens no matter 
sna or uxa is used.

  This doesn't happen if using kwin_gles instead (but I don't use it
  because then the blur effect doesn't work). Please let me know if I
  should fill a bug in kde as well...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: kde-window-manager 4:4.11.6-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Feb 23 15:51:23 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-07-27 (942 days ago)
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  ProcEnviron:
   LANGUAGE=ca:ca@valencia:en_US:en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: kde-workspace
  UpgradeStatus: Upgraded to trusty on 2014-02-17 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/1283820/+subscriptions

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


[Desktop-packages] [Bug 1223332] Re: [snb mesa blorp] False GPU lockup IPEHR: 0x7a000002

2016-03-02 Thread Christopher M. Penalver
** Project changed: xserver-xorg-video-intel => mesa (Ubuntu)

** No longer affects: mesa (Ubuntu)

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

Title:
  [snb mesa blorp] False GPU lockup  IPEHR: 0x7a02

Status in XMir:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  [snb mesa blorp] False GPU lockup IPEHR: 0x7a02

  ORIGINAL REPORT:
  i have not seen this bug. i don't recall a lockup in the last two weeks. i 
see the report a bug window when i log in, but login was fast and smooth.

  however, you might notice that there are no capitol letters in the
  report. after logging back in the shift key appears to be a menu key.
  when i press shift to make a capitol letter, the application and
  indicator menus appear.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  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 Sep  8 11:32:22 2013
  DistUpgraded: 2013-08-11 14:46:21,966 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   applesmc, 0.18.2, 3.11.0-4-generic, x86_64: installed
   applesmc, 0.18.2, 3.11.0-5-generic, x86_64: installed
   bcmwl, 6.30.223.30+bdcom, 3.11.0-4-generic, x86_64: installed
   bcmwl, 6.30.223.30+bdcom, 3.11.0-5-generic, x86_64: installed
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x7a02 Ubuntu 
13.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00eb]
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir4,2
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=be18758e-a70e-4fbd-b26b-0cab706d92f0 ro quiet splash 
i915.i915_enable_rc6=1 resume=/dev/sda6 vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu5
   libdrm2  2.4.46-1
   xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] False GPU lockup  IPEHR: 0x7a02
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (29 days ago)
  UserGroups:

  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B0F.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-742912EFDBEE19B3
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir4,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-742912EFDBEE19B3
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
  dmi.product.name: MacBookAir4,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Tue Sep 10 08:32:22 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40159
   vendor APP
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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


[Desktop-packages] [Bug 1223332] Re: [snb mesa blorp] False GPU lockup IPEHR: 0x7a000002

2016-03-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  [snb mesa blorp] False GPU lockup  IPEHR: 0x7a02

Status in XMir:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  [snb mesa blorp] False GPU lockup IPEHR: 0x7a02

  ORIGINAL REPORT:
  i have not seen this bug. i don't recall a lockup in the last two weeks. i 
see the report a bug window when i log in, but login was fast and smooth.

  however, you might notice that there are no capitol letters in the
  report. after logging back in the shift key appears to be a menu key.
  when i press shift to make a capitol letter, the application and
  indicator menus appear.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  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 Sep  8 11:32:22 2013
  DistUpgraded: 2013-08-11 14:46:21,966 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   applesmc, 0.18.2, 3.11.0-4-generic, x86_64: installed
   applesmc, 0.18.2, 3.11.0-5-generic, x86_64: installed
   bcmwl, 6.30.223.30+bdcom, 3.11.0-4-generic, x86_64: installed
   bcmwl, 6.30.223.30+bdcom, 3.11.0-5-generic, x86_64: installed
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x7a02 Ubuntu 
13.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00eb]
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir4,2
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=be18758e-a70e-4fbd-b26b-0cab706d92f0 ro quiet splash 
i915.i915_enable_rc6=1 resume=/dev/sda6 vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu5
   libdrm2  2.4.46-1
   xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] False GPU lockup  IPEHR: 0x7a02
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (29 days ago)
  UserGroups:

  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B0F.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-742912EFDBEE19B3
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir4,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-742912EFDBEE19B3
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
  dmi.product.name: MacBookAir4,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Tue Sep 10 08:32:22 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40159
   vendor APP
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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

[Desktop-packages] [Bug 1267893] Re: Shutdown crash due to possible mesa race at startup

2016-03-02 Thread Christopher M. Penalver
** Changed in: mesa (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Shutdown crash due to possible mesa race at startup

Status in Oxide:
  Fix Released
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  When running the oxide test suite, I saw this crash:

  #0  glx_display_free (priv=priv@entry=0x0) at ../../../../src/glx/glxext.c:226
  #1  0x2e215305 in __glXCloseDisplay (dpy=0x624970, codes=) at ../../../../src/glx/glxext.c:272
  #2  0x2eee44f2 in XCloseDisplay (dpy=0x624970) at 
../../src/ClDisplay.c:65
  #3  0x2aaab3ac8c3a in QXcbConnection::~QXcbConnection (this=0x6245d0, 
__in_chrg=) at qxcbconnection.cpp:382
  #4  0x2aaab3ac8f89 in QXcbConnection::~QXcbConnection (this=0x6245d0, 
__in_chrg=) at qxcbconnection.cpp:388
  #5  0x2aaab3accfd6 in qDeleteAll::const_iterator> 
(end=..., begin=...) at 
../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:321
  #6  qDeleteAll > (c=...) at 
../../../../include/QtCore/../../src/corelib/tools/qalgorithms.h:329
  #7  QXcbIntegration::~QXcbIntegration (this=0x61a7d0, __in_chrg=) at qxcbintegration.cpp:127
  #8  0x2aaab3acd1e9 in QXcbIntegration::~QXcbIntegration (this=0x61a7d0, 
__in_chrg=) at qxcbintegration.cpp:128
  #9  0x2afa82f6 in QGuiApplicationPrivate::~QGuiApplicationPrivate 
(this=0x6183d0, __in_chrg=) at kernel/qguiapplication.cpp:1067
  #10 0x2afa8469 in QGuiApplicationPrivate::~QGuiApplicationPrivate 
(this=0x6183d0, __in_chrg=) at kernel/qguiapplication.cpp:1070
  #11 0x2c7d0b66 in cleanup (pointer=) at 
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:63
  #12 ~QScopedPointer (this=0x7fffd568, __in_chrg=) at 
../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:99
  #13 QObject::~QObject (this=0x7fffd560, __in_chrg=) at 
kernel/qobject.cpp:750
  #14 0x2afa814c in QGuiApplication::~QGuiApplication 
(this=0x7fffd560, __in_chrg=) at 
kernel/qguiapplication.cpp:387
  #15 0x0040080d in main (argc=3, argv=0x7fffd668) at 
tst_qmltests.cc:34

  What's happening is that __glXCloseDisplay() is being called twice,
  because the glx extension seems to be registered twice on the Display
  handle.

  This appears to be happening because of a race in __glXInitialize()
  between the main thread and Chromium's GPU thread. The main thread
  calls it for the first time from here:

  #0  __glXInitialize (dpy=dpy@entry=0x624970) at 
../../../../src/glx/glxext.c:798
  #1  0x2e211a27 in glXGetFBConfigs (dpy=0x624970, screen=0, 
nelements=nelements@entry=0x7fffce7c) at ../../../../src/glx/glxcmds.c:1663
  #2  0x2e2124e3 in glXChooseFBConfig (dpy=, 
screen=, attribList=0x68a388, nitems=0x7fffcfec) at 
../../../../src/glx/glxcmds.c:1623
  #3  0x2aaab3ae928f in qglx_findConfig (display=display@entry=0x624970, 
screen=screen@entry=0, format=..., drawableBit=drawableBit@entry=1) at 
glxconvenience/qglxconvenience.cpp:126
  #4  0x2aaab3ae93dc in qglx_findVisualInfo (display=0x624970, screen=0, 
format=format@entry=0x6f3fc8) at glxconvenience/qglxconvenience.cpp:171
  #5  0x2aaab3ad978d in QXcbWindow::create (this=0x6f3f70) at 
qxcbwindow.cpp:271
  #6  0x2aaab3accd11 in QXcbIntegration::createPlatformWindow 
(this=, window=0x64b950) at qxcbintegration.cpp:132
  #7  0x2afb259e in QWindow::create (this=this@entry=0x64b950) at 
kernel/qwindow.cpp:323
  #8  0x2afb2e58 in QWindow::setVisible (this=this@entry=0x64b950, 
visible=visible@entry=true) at kernel/qwindow.cpp:269
  #9  0x2afb3429 in QWindow::showNormal (this=this@entry=0x64b950) at 
kernel/qwindow.cpp:1524
  #10 0x2afb344e in QWindow::show (this=this@entry=0x64b950) at 
kernel/qwindow.cpp:1455
  #11 0x2acdbf37 in quick_test_main (argc=, 
argv=argv@entry=0x7fffd668, name=name@entry=0x400a00 "qmltests", 
  sourceDir=sourceDir@entry=0x4009c8 
"/home/chr1s/src/oxide/oxide/qt/tests/qmltests/data") at quicktest.cpp:341
  #12 0x00400801 in main (argc=3, argv=0x7fffd668) at 
tst_qmltests.cc:34

  ... and Chromium's GPU thread calls it for the first time from here:

  #0  __glXInitialize (dpy=0x624970) at ../../../../src/glx/glxext.c:798
  #1  0x2e211851 in glXQueryVersion (dpy=, 
major=0x2aaaed43d7ec, minor=0x2aaaed43d7f0) at ../../../../src/glx/glxcmds.c:487
  #2  0x2aaac606b74b in gfx::GLXApiBase::glXQueryVersionFn 
(this=0x2aab1c008480, dpy=0x624970, maj=0x2aaaed43d7ec, min=0x2aaaed43d7f0)
  at 
/home/chr1s/src/oxide/oxide/chromium/src/out/Debug/obj/gen/ui/gl/gl_bindings_autogen_glx.cc:724
  #3  0x2aaac6061c11 in gfx::GLSurfaceGLX::InitializeOneOff () at 
chromium/src/ui/gl/gl_surface_glx.cc:407
  #4  0x2aaac601b4ac in gfx::GLSurface::InitializeOneOffInternal 

[Desktop-packages] [Bug 1223332] Re: [snb mesa blorp] False GPU lockup IPEHR: 0x7a000002

2016-03-02 Thread Christopher M. Penalver
** No longer affects: mesa (Ubuntu)

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

Title:
  [snb mesa blorp] False GPU lockup  IPEHR: 0x7a02

Status in XMir:
  Invalid
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  [snb mesa blorp] False GPU lockup IPEHR: 0x7a02

  ORIGINAL REPORT:
  i have not seen this bug. i don't recall a lockup in the last two weeks. i 
see the report a bug window when i log in, but login was fast and smooth.

  however, you might notice that there are no capitol letters in the
  report. after logging back in the shift key appears to be a menu key.
  when i press shift to make a capitol letter, the application and
  indicator menus appear.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  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 Sep  8 11:32:22 2013
  DistUpgraded: 2013-08-11 14:46:21,966 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   applesmc, 0.18.2, 3.11.0-4-generic, x86_64: installed
   applesmc, 0.18.2, 3.11.0-5-generic, x86_64: installed
   bcmwl, 6.30.223.30+bdcom, 3.11.0-4-generic, x86_64: installed
   bcmwl, 6.30.223.30+bdcom, 3.11.0-5-generic, x86_64: installed
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x7a02 Ubuntu 
13.10
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Apple Inc. Device [106b:00eb]
  InterpreterPath: /usr/bin/python3.3
  MachineType: Apple Inc. MacBookAir4,2
  MarkForUpload: True
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic 
root=UUID=be18758e-a70e-4fbd-b26b-0cab706d92f0 ro quiet splash 
i915.i915_enable_rc6=1 resume=/dev/sda6 vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu5
   libdrm2  2.4.46-1
   xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] False GPU lockup  IPEHR: 0x7a02
  UpgradeStatus: Upgraded to saucy on 2013-08-11 (29 days ago)
  UserGroups:

  dmi.bios.date: 01/24/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA41.88Z.0077.B0F.1201241549
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-742912EFDBEE19B3
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir4,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-742912EFDBEE19B3
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B0F.1201241549:bd01/24/2012:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3:
  dmi.product.name: MacBookAir4,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Tue Sep 10 08:32:22 2013
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40159
   vendor APP
  xserver.version: 2:1.14.2.901-2ubuntu4

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

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


[Desktop-packages] [Bug 1245508] Re: Unity slow in 13.10 Nvidia

2016-03-02 Thread Christopher M. Penalver
Alen Masic, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p xorg 1245508

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

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

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

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

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

Title:
  Unity slow in 13.10 Nvidia

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Unity dash is slow when searching for applications in Dash. When I
  find application and press Enter to launch it, it takes around 2-3
  seconds before Dash dissappear and application is triggered. This
  never happened in 13.04.

  Graphics: NVidia GeForce 6100 nForce 410
  CPU: 2.6 GHz
  RAM: 2Gb DDR2

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

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


[Desktop-packages] [Bug 1237545] Re: check_gl_texture_size crashed with SIGSEGV in scalarEqual()

2016-03-02 Thread Christopher M. Penalver
Not reproducible in Xenial.

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

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

Title:
  check_gl_texture_size crashed with SIGSEGV in scalarEqual()

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Just happened after starting Ubuntu 13.10 on 09.10.2013 in VirtualBox.
  (All packages up-to-date).

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libgnome-desktop-3-7 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
  Uname: Linux 3.11.0-11-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  Date: Wed Oct  9 19:17:38 2013
  Disassembly: => 0x7ff19d6c6b20:   Cannot access memory at address 
0x7ff19d6c6b20
  ExecutablePath: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  InstallationDate: Installed on 2013-10-08 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7ff19d6c6b20:Cannot access memory at address 
0x7ff19d6c6b20
   PC (0x7ff19d6c6b20) in non-executable VMA region: 
0x7ff19d69a000-0x7ff19d89a000 ---p /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  SegvReason: executing non-writable VMA 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Signal: 11
  SourcePackage: gnome-desktop3
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   glXChooseVisual () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  Title: check_gl_texture_size crashed with SIGSEGV in glXChooseVisual()
  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/mesa/+bug/1237545/+subscriptions

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


[Desktop-packages] [Bug 1233617] Re: check_gl_texture_size crashed with SIGSEGV in dl_new_hash()

2016-03-02 Thread Christopher M. Penalver
Dennis Jensen, thank you for reporting this and helping make Ubuntu
better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 13.10 is EOL as of July
17, 2014.

Is this reproducible in a supported release?

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

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

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

Title:
  check_gl_texture_size crashed with SIGSEGV in dl_new_hash()

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  booted up,

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libgnome-desktop-3-7 3.8.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1
  Uname: Linux 3.11.0-7-generic x86_64
  ApportVersion: 2.12.5-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Oct  1 13:24:51 2013
  Disassembly: => 0x7f6332ce2b20:   Cannot access memory at address 
0x7f6332ce2b20
  ExecutablePath: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  InstallationDate: Installed on 2013-09-06 (24 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130906)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7f6332ce2b20:Cannot access memory at address 
0x7f6332ce2b20
   PC (0x7f6332ce2b20) in non-executable VMA region: 
0x7f6332cb6000-0x7f6332eb6000 ---p /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  SegvReason: executing non-writable VMA 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Signal: 11
  SourcePackage: gnome-desktop3
  StacktraceTop:
   dl_new_hash (s=0x7f632fc2c3b1 "_ZTISt8messagesIwE") at dl-lookup.c:477
   _dl_lookup_symbol_x (undef_name=0x7f632fc2998f "_ZNSt7collateIwED1Ev", 
undef_map=undef_map@entry=0xcbdf20, ref=ref@entry=0x7fffb2044820, 
symbol_scope=symbol_scope@entry=0xcbe278, version=0xcbf360, type_class=0, 
flags=flags@entry=1, skip_map=skip_map@entry=0x0) at dl-lookup.c:717
   elf_machine_rela (version=, sym=0x7f632fc10dd8, skip_ifunc=0, 
reloc_addr_arg=0x7f632fee0e90 +16>, 
map=0xcbdf20, reloc=) at ../sysdeps/x86_64/dl-machine.h:276
   elf_dynamic_do_Rela (skip_ifunc=0, lazy=, 
nrelative=, relsize=, reladdr=, 
map=0xcbdf20) at do-rel.h:137
   _dl_relocate_object (scope=0xcbe278, reloc_mode=reloc_mode@entry=0, 
consider_profiling=consider_profiling@entry=0) at dl-reloc.c:265
  Title: check_gl_texture_size crashed with SIGSEGV in dl_new_hash()
  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/mesa/+bug/1233617/+subscriptions

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


[Desktop-packages] [Bug 1239861] Re: Basic OpenGL+X11 build on a 32 bits system craches X11 when ruing on a 64 bits system

2016-03-02 Thread Christopher M. Penalver
Guilhem de Wailly, thank you for reporting this and helping make Ubuntu
better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p xorg 1239861

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** Tags removed: crash mesa x11
** Tags added: precise raring

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

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

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

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

Title:
  Basic OpenGL+X11 build on a 32 bits system craches X11 when ruing on a
  64 bits system

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  A customer of us has report that our application www.caniviz.com
  crashes when working on a Ubunty 12.05 LTS machine...

  After investigation, we found that every OpenGL applications build in
  32 bits seems to crash X11 when running on a 64 bits host; crashing
  X11 means that the session of the user that has run the opengl
  application is killed.

  The next program can be found at
  http://www.opengl.org/wiki/Tutorial:_OpenGL_3.0_Context_Creation_(GLX).
  The build instructions are also in the link...

  We have tries with Ubuntu 13.04 32 and 64bits and 12.05 32 and 64bits:
  every time the 32 bits application is run in a 64 bits, there is the
  crash...

  Guilhem

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

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


[Desktop-packages] [Bug 1224940] Re: [r600] unity_support_test crashed with SIGSEGV in do_winsys_init()

2016-03-02 Thread Christopher M. Penalver
** Tags added: bios-outdated-2.28

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

Title:
  [r600] unity_support_test crashed with SIGSEGV in do_winsys_init()

Status in mesa package in Ubuntu:
  Triaged

Bug description:
  Upgraded from 13.04 to 13.10.  Running on Xen 4.2 with Openswitch.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: nux-tools 4.0.2+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.12.1-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist:
   (process:5483): dconf-CRITICAL **: unable to create file 
'/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied.  dconf will 
not work properly.
   
   (process:5483): dconf-CRITICAL **: unable to create file 
'/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied.  dconf will 
not work properly.
   '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW:
   (process:5481): dconf-CRITICAL **: unable to create file 
'/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied.  dconf will 
not work properly.
   
   (process:5481): dconf-CRITICAL **: unable to create file 
'/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied.  dconf will 
not work properly.
   true
  CrashCounter: 1
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Fri Sep 13 08:03:06 2013
  DistUpgraded: 2013-04-01 12:10:36,712 DEBUG enabling apt cron job
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus:
   blktap, 2.0.93, 3.11.0-7-generic, x86_64: installed
   blktap, 2.0.93, 3.8.0-26-generic, x86_64: installed
   blktap, 2.0.93, 3.8.0-27-generic, x86_64: installed
   blktap, 2.0.93, 3.8.0-30-generic, x86_64: installed
   openvswitch, 1.10.2: added
  ExecutablePath: /usr/lib/nux/unity_support_test
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126]
  InstallationDate: Installed on 2013-04-01 (164 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC
  MarkForUpload: True
  ProcCmdline: /usr/lib/nux/unity_support_test
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: placeholder root=/dev/mapper/ubuntu-root ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x7f70f6d32549 : mov
(%rax),%r8d
   PC (0x7f70f6d32549) ok
   source "(%rax)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%r8d" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nux
  StacktraceTop:
   radeon_drm_winsys_create () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  Title: unity_support_test crashed with SIGSEGV in radeon_drm_winsys_create()
  UpgradeStatus: Upgraded to saucy on 2013-04-01 (164 days ago)
  UserGroups: sudo
  XsessionErrors:
   (process:3487): dconf-CRITICAL **: unable to create file 
'/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied.  dconf will 
not work properly.
   (process:3487): dconf-CRITICAL **: unable to create file 
'/home/FREEDOMFORUM/sbrown/.cache/dconf/user': Permission denied.  dconf will 
not work properly.
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: J01 v02.15
  dmi.board.asset.tag: 2UA125069Q
  dmi.board.name: 1495
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: 2UA125069Q
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq 8200 Elite SFF PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Desktop-packages] [Bug 1228991] Re: compiz crashed with SIGSEGV in _swrast_map_texture()

2016-03-02 Thread Christopher M. Penalver
As per
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1228991/comments/6 .

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

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

Title:
  compiz crashed with SIGSEGV in _swrast_map_texture()

Status in Unity:
  Won't Fix
Status in mesa package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  Won't Fix

Bug description:
  Saucy updated just updated to 3.11.0-8 from -7.  Ran for a while then
  external monitor froze.  Normally have built-in netbook screen off.
  Systems settings displays said external monitor "unknown display" and
  wouldn't run it.  Normally reports it as Coby electronics co. ltd 40"
  (?) max resolution 19201080x1080 I run it at 1360x768, 15.5" diagonal.

  Rebooted later without external monitor, plugged it back in and
  running normally now.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.0+13.10.20130920-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
  Uname: Linux 3.11.0-8-generic x86_64
  ApportVersion: 2.12.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Sun Sep 22 12:26:38 2013
  ExecutablePath: /usr/bin/compiz
  InstallationDate: Installed on 2013-09-09 (14 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130907)
  MarkForUpload: True
  ProcCmdline: compiz
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f8c9b978d11 <_swrast_map_texture+241>:  cmpq   
$0x0,(%rax,%rbp,8)
   PC (0x7f8c9b978d11) ok
   source "$0x0" ok
   destination "(%rax,%rbp,8)" (0x) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: unity
  StacktraceTop:
   _swrast_map_texture () from /usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
   _swrast_map_textures () from /usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
   _swrast_span_render_start () from 
/usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
   _swrast_render_start () from /usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
  Title: compiz crashed with SIGSEGV in _swrast_map_texture()
  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/unity/+bug/1228991/+subscriptions

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


[Desktop-packages] [Bug 1221041] Re: Xorg crashed with SIGABRT in _mesa_GenTextures()

2016-03-02 Thread Christopher M. Penalver
Misha Bazanov / Anton Sudak, thank you for reporting this and helping
make Ubuntu better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 13.10 reached EOL on
July 17, 2014.

Is this reproducible with a supported release?

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

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

Title:
  Xorg crashed with SIGABRT in _mesa_GenTextures()

Status in Mesa:
  Won't Fix
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Opensource radeon driver crash every time i try to run FTL: Faster
  Then Light.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep  5 12:18:18 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.16, 3.11.0-4-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] 
[1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03da]
  InstallationDate: Installed on 2013-08-12 (24 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130630)
  MachineType: Gigabyte Technology Co., Ltd. EG41MF-US2H
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=74c6d537-9a52-45a2-a434-ecde1217e8d1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   _mesa_GenTextures () from /usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
   ?? () from /usr/lib/xorg/modules/extensions/libglx.so
   ?? () from /usr/lib/xorg/modules/extensions/libglx.so
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT in _mesa_GenTextures()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/22/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: EG41MF-US2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/22/2010:svnGigabyteTechnologyCo.,Ltd.:pnEG41MF-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG41MF-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EG41MF-US2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Thu Sep  5 12:18:26 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.2.901-2ubuntu4
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1225681] Re: Launching 'FTL: Faster Than Light' with r600g driver crashes xorg

2016-03-02 Thread Christopher M. Penalver
rtrevor, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect -p xorg 1225681

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** This bug is no longer a duplicate of bug 1221041
   Xorg crashed with SIGABRT in _mesa_GenTextures()

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

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

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

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

Title:
  Launching 'FTL: Faster Than Light' with r600g driver crashes xorg

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using open source r600g driver on amd64 architecture, trying to
  launch FTL: Faster Than Light game in Steam completely crashes the
  xorg server. lightdm then restarts taking you back to the login
  screen.

  FTL: Faster Than Light is part of the current Humble Bundle 9 set of
  games.

  More info here: https://bugs.freedesktop.org/show_bug.cgi?id=66955

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

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


[Desktop-packages] [Bug 1221041] Re: Xorg crashed with SIGABRT in _mesa_GenTextures()

2016-03-02 Thread Christopher M. Penalver
** Tags added: latest-bios-f5

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

Title:
  Xorg crashed with SIGABRT in _mesa_GenTextures()

Status in Mesa:
  Won't Fix
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Opensource radeon driver crash every time i try to run FTL: Faster
  Then Light.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Sep  5 12:18:18 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 4.2.16, 3.11.0-4-generic, x86_64: installed
  ExecutablePath: /usr/bin/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450] 
[1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:03da]
  InstallationDate: Installed on 2013-08-12 (24 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130630)
  MachineType: Gigabyte Technology Co., Ltd. EG41MF-US2H
  MarkForUpload: True
  ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-4-generic 
root=UUID=74c6d537-9a52-45a2-a434-ecde1217e8d1 ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   _mesa_GenTextures () from /usr/lib/x86_64-linux-gnu/libdricore9.2.0.so.1
   ?? () from /usr/lib/xorg/modules/extensions/libglx.so
   ?? () from /usr/lib/xorg/modules/extensions/libglx.so
   ?? ()
   ?? ()
  Title: Xorg crashed with SIGABRT in _mesa_GenTextures()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/22/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: EG41MF-US2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd04/22/2010:svnGigabyteTechnologyCo.,Ltd.:pnEG41MF-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG41MF-US2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: EG41MF-US2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Thu Sep  5 12:18:26 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.2.901-2ubuntu4
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1538524] Re: Update to 1.6.3

2016-03-02 Thread Flames_in_Paradise
Tested all of these packages on Wily (Kubuntu). Absolutely no problems
at all.. Thanks.

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

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

Title:
  Update to 1.6.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-base1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-good1.0 source package in Wily:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Wily:
  Fix Committed
Status in gstreamer1.0 source package in Wily:
  Fix Committed

Bug description:
  [ Description ]

  We should stick with upstream's stable bugfix releases in 15.10

  [ Test plan & QA ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  This is a pure bugfix release, but there is always a chance that one
  of the fixes could be wrong.

  [ Development release ]

  Xenial is on a different 1.7 series and will be on 1.8 by release. All
  commits to the stable branch should come from the master branches that
  1.7 releases are made from, although there might be slight differences
  in release timing that means one is released before the other.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1538524/+subscriptions

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


[Desktop-packages] [Bug 1225681] [NEW] Launching 'FTL: Faster Than Light' with r600g driver crashes xorg

2016-03-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When using open source r600g driver on amd64 architecture, trying to
launch FTL: Faster Than Light game in Steam completely crashes the xorg
server. lightdm then restarts taking you back to the login screen.

FTL: Faster Than Light is part of the current Humble Bundle 9 set of
games.

More info here: https://bugs.freedesktop.org/show_bug.cgi?id=66955

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete

-- 
Launching 'FTL: Faster Than Light' with r600g driver crashes xorg
https://bugs.launchpad.net/bugs/1225681
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to xorg 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 1200932] Re: Using an intel GMA 3150 without opengl 2.1 support

2016-03-02 Thread Christopher M. Penalver
Jacopo Remondina, thank you for reporting this and helping make Ubuntu
better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on
July 17, 2014.

Is this reproducible in a supported release?

** Tags added: bios-outdated-1202

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

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

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

Title:
  Using an intel GMA 3150 without opengl 2.1 support

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  On intel website I read that my video card (an integrated intel GMA
  3150) should support opengl 2.0 on linux, but in my reports (glxinfo)
  it seem that only opengl 1.4 is supported. It also seem that also
  others users seems to have the same problem. Could you fix it?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 13 16:09:02 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  DkmsStatus: sl-modem, 2.9.11~20110321: added
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a011] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
 Subsystem: ASUSTeK Computer Inc. Device [1043:83ac]
  InstallationDate: Installed on 2013-05-05 (68 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  LightdmGreeterLog: ** (lightdm-gtk-greeter:1867): WARNING **: Failed to open 
sessions directory: Errore nell'aprire la directory 
"/usr/share/lightdm/remote-sessions": File o directory non esistente
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1912): WARNING **: Failed to 
open sessions directory: Errore nell'aprire la directory 
"/usr/share/lightdm/remote-sessions": File o directory non esistente
  MachineType: ASUSTeK Computer INC. 1015PE
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=it:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic 
root=UUID=5ca263c2-6d64-469f-a58d-d38a234c241d ro quiet splash vt.handoff=7
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0308
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 1015PE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: 0x
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer INC.
  dmi.chassis.version: x.x
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0308:bd04/26/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
  dmi.product.name: 1015PE
  dmi.product.version: x.x
  dmi.sys.vendor: ASUSTeK Computer INC.
  version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1
  version.libdrm2: libdrm2 2.4.43-0ubuntu1.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7-0ubuntu1
  xserver.bootTime: Sat Jul 13 15:55:07 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu6
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1210381] Re: An endless loop in the libglu

2016-03-02 Thread Christopher M. Penalver
** Tags added: quantal

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

Title:
  An endless loop in the libglu

Status in mesa package in Ubuntu:
  New

Bug description:
  This library contain function GotoState() in the
  src/glu/sgi/libtess/tess.c file. It is possible to enter an endless
  loop in this function due to incorrect usage of libglu functions
  because switch() statements in this function doesn't check for all
  possible values and there is no error processing under "default"
  labels. I've encountered this bug by using some Windows applications
  running under wine 1.6.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libglu1-mesa 8.0.4-0ubuntu0.6
  Uname: Linux 3.6.6-030606-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Fri Aug  9 10:21:12 2013
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
  MarkForUpload: True
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1203833] Re: check_gl_texture_size crashed with SIGSEGV in driIndexConfigAttrib()

2016-03-02 Thread Christopher M. Penalver
Not reproducible in Xenial.

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

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

Title:
  check_gl_texture_size crashed with SIGSEGV in driIndexConfigAttrib()

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I installed the daily build of Ubuntu 13.10 in virtual box version
  4.2.16 r86992 with guest extensions installed.  I was on the desktop
  when this error appeared.

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: libgnome-desktop-3-7 3.8.3-0ubuntu1
  ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
  Uname: Linux 3.10.0-4-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Mon Jul 22 13:55:33 2013
  Disassembly: => 0x7fda519d5b20:   Cannot access memory at address 
0x7fda519d5b20
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  InstallationDate: Installed on 2013-07-22 (0 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130722)
  MarkForUpload: True
  ProcCmdline: /usr/lib/libgnome-desktop-3-7/check_gl_texture_size
  ProcEnviron:
   
  SegvAnalysis:
   Segfault happened at: 0x7fda519d5b20:Cannot access memory at address 
0x7fda519d5b20
   PC (0x7fda519d5b20) in non-executable VMA region: 
0x7fda518a9000-0x7fda51aa9000 ---p /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  SegvReason: executing non-writable VMA 
/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
  Signal: 11
  SourcePackage: gnome-desktop3
  StacktraceTop:
   driIndexConfigAttrib () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
   ?? () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
  Title: check_gl_texture_size crashed with SIGSEGV in driIndexConfigAttrib()
  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/mesa/+bug/1203833/+subscriptions

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


[Desktop-packages] [Bug 1552467] [NEW] hat computer to this. Copied the dropbox folder from bad disk to this. Had problems installing DB. Looks ok now.

2016-03-02 Thread Denis
*** This bug is a duplicate of bug 1544270 ***
https://bugs.launchpad.net/bugs/1544270

Public bug reported:

I had a hard drive crash. I replaced it with this hard drive being used
in another computer. I copied the drop box folder from the defective
hard drive to this hard drive. Then I decided to install drop box. It
wouldn't install from app grid. It wouldn't install from Drop box
download. I was able to install from the command line.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lightdm 1.17.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
AptOrdering:
 nautilus-dropbox: Install
 lightdm: Configure
 ubuntu-mate-core: Configure
 nautilus-dropbox: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Mar  2 18:16:21 2016
DpkgHistoryLog:
 Start-Date: 2016-03-02  18:16:17
 Commandline: aptdaemon role='role-commit-packages' sender=':1.85'
 Install: nautilus-dropbox:amd64 (2.10.0-2)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-02-21 (10 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.3
SourcePackage: lightdm
Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  hat computer to this. Copied the dropbox folder from bad disk to this.
  Had problems installing  DB. Looks ok now.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I had a hard drive crash. I replaced it with this hard drive being
  used in another computer. I copied the drop box folder from the
  defective hard drive to this hard drive. Then I decided to install
  drop box. It wouldn't install from app grid. It wouldn't install from
  Drop box download. I was able to install from the command line.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  AptOrdering:
   nautilus-dropbox: Install
   lightdm: Configure
   ubuntu-mate-core: Configure
   nautilus-dropbox: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar  2 18:16:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-03-02  18:16:17
   Commandline: aptdaemon role='role-commit-packages' sender=':1.85'
   Install: nautilus-dropbox:amd64 (2.10.0-2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1196307] Re: Xorg crashed with SIGABRT in __GI_raise()

2016-03-02 Thread Christopher M. Penalver
gepas, thank you for reporting this and helping make Ubuntu better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 13.10 is EOL as of July
17, 2014.

Is this reproducible in a supported release?

** Tags added: latest-bios-1.23

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

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

Title:
  Xorg crashed with SIGABRT in __GI_raise()

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-core 2:1.13.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
  Uname: Linux 3.10.0-1-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jun 27 23:18:11 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/Xorg
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0362]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:0362]
  InstallationDate: Installed on 2013-06-20 (10 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
  MachineType: Acer Aspire 5553G
  MarkForUpload: True
  ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-1-generic 
root=UUID=4e94aec6-90bb-42c9-83a8-2971e742e96d ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  Stacktrace:
   #0  0x7fb85d4bf037 in raise () from /lib/x86_64-linux-gnu/libc.so.6
   No symbol table info available.
   Cannot access memory at address 0x7fffc39d81f8
  StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6
  Title: Xorg crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 04/25/2011
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.23
  dmi.board.name: JV51_DN
  dmi.board.vendor: Acer
  dmi.board.version: Not Applicable
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.23:bd04/25/2011:svnAcer:pnAspire5553G:pvrNotApplicable:rvnAcer:rnJV51_DN:rvrNotApplicable:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5553G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.45-2ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu13
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.8-0ubuntu1
  xserver.bootTime: Sun Jun 30 21:21:22 2013
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.13.3-0ubuntu13
  xserver.video_driver: radeon

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

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


[Desktop-packages] [Bug 1552467] Re: hat computer to this. Copied the dropbox folder from bad disk to this. Had problems installing DB. Looks ok now.

2016-03-02 Thread Apport retracing service
*** This bug is a duplicate of bug 1544270 ***
https://bugs.launchpad.net/bugs/1544270

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

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 1544270
   package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  hat computer to this. Copied the dropbox folder from bad disk to this.
  Had problems installing  DB. Looks ok now.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I had a hard drive crash. I replaced it with this hard drive being
  used in another computer. I copied the drop box folder from the
  defective hard drive to this hard drive. Then I decided to install
  drop box. It wouldn't install from app grid. It wouldn't install from
  Drop box download. I was able to install from the command line.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  AptOrdering:
   nautilus-dropbox: Install
   lightdm: Configure
   ubuntu-mate-core: Configure
   nautilus-dropbox: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar  2 18:16:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-03-02  18:16:17
   Commandline: aptdaemon role='role-commit-packages' sender=':1.85'
   Install: nautilus-dropbox:amd64 (2.10.0-2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1551949] Re: Printing to PDF file loses URLs/links

2016-03-02 Thread Bug Watch Updater
** Changed in: thunderbird
   Status: New => Invalid

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

Title:
  Printing to PDF file loses URLs/links

Status in Mozilla Thunderbird:
  Invalid
Status in thunderbird package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. File -> Print...
  2. Select "Print to File".
  3. Enter the file name.
  4. Enter the save-to folder.
  5. Leave the output format as-is, or select PDF if it's not the default.
  6. Hit the Print button.
  7. Open the resulting PDF in any PDF viewer.

  
  Actual results:

  The URLs within the document are not actually hyperlinks.  They are
  simply text, coloured blue and underlined.

  
  Expected results:

  Any clickable links on the original e-mail message should be retained
  when converting the document to PDF format.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: thunderbird 1:38.5.1+build2-0ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colan  2383 F pulseaudio
   /dev/snd/controlC0:  colan  2383 F pulseaudio
  BuildID: 20160106101030
  Channel: Unavailable
  CurrentDesktop: Unity
  Date: Tue Mar  1 15:53:53 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/lib/thunderbird/thunderbird
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 600 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.140  
metric 600
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-1abc004a-043e-4a15-bdc0-45ade2150908
  Plugins:
   Google Talk Plugin Video Renderer - /opt/google/talkplugin/libnpo1d.so 
(google-talkplugin)
   Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so 
(google-talkplugin)
   iTunes Application Detector - 
/usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so 
(rhythmbox-mozilla)
   Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so 
(adobe-flashplugin)
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/zsh
  Profiles: Profile0 (Default) - LastVersion=38.5.1/20160106101030 (In use)
  RelatedPackageVersions:
   google-talkplugin 5.41.0.0-1
   rhythmbox-mozilla 3.2.1-1ubuntu3.1
   adobe-flashplugin 1:20160209.1-0ubuntu0.15.10.1
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  SubmittedCrashIDs:
   bp-1abc004a-043e-4a15-bdc0-45ade2150908
   bp-c8c94f9f-0c39-42d2-97ac-f2c7d2150713
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to wily on 2015-11-30 (92 days ago)
  dmi.bios.date: 07/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Galago UltraPro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: galu1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: System76, Inc,
  dmi.chassis.version: galu1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/09/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnSystem76,Inc.:rnGalagoUltraPro:rvrgalu1:cvnSystem76,Inc,:ct9:cvrgalu1:
  dmi.product.name: Galago UltraPro
  dmi.product.version: galu1
  dmi.sys.vendor: System76, Inc.

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

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


[Desktop-packages] [Bug 1316634] Re: Does not automatically reconnect to hidden WiFi network

2016-03-02 Thread Michael Mess
Next steps:
 - 1) Check the file /var/lib/NetworkManager/NetworkManager.state when the 
problem occurs next time.

With connected network it looks like:

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true

 - 2) Check the files in /var/lib/NetworkManager/ for their contents.
Probably this might help to track down the problem.

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

Title:
  Does not automatically reconnect to hidden WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running Lubuntu 14.04 32-bit on a Lenovo 3000 C200 laptop with an
  integrated Broadcom network adapter, I installed
  firmware-b43-installer and then successfully connected to my hidden
  (SSID not broadcast) WiFi net.

  But I see that it will not automatically reconnect.  I don't have to
  re-enter the password, but I do have to click the nm-applet indicator,
  choose 'Connect to Hidden Wi-Fi Network' and then choose my already-
  defined connection, which indeed has been saved but not used to
  automatically reconnect.

  If I edit the connection, I see that on the General tab it is already
  set to 'Automatically connect to this network when it is available.'

  The only way I can get automatic reconnection is to enable SSID
  Broadcast.

  And a similar effect: If I am connected to the network while SSID
  Broadcast is in effect and then disable SSID Broadcast, network-
  manager immediately loses the connection.

  Someone suggested that network-manager would find the hidden network
  if I just waited, but after waiting 15 minutes it had still not
  connected.

  Dual-booting this same laptop with Windows Vista, I see that Windows
  knows how to automatically reconnect to the hidden net.

  I see that https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/295796 describes similar behavior, but that was reported
  back in 2008 and I'm imagining that there should be a separate report
  for the new release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue May  6 10:24:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-25 (10 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.118  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1ac7ba941-660f-40c5-9b1f-4d24accc6225   
802-3-ethernet1399385892   Tue 06 May 2014 10:18:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   PRP   d25473c0-98d8-4d93-ab37-3dd070bbd34b   
802-11-wireless   1399386192   Tue 06 May 2014 10:23:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/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/1316634/+subscriptions

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


[Desktop-packages] [Bug 1316634] Re: Does not automatically reconnect to hidden WiFi network

2016-03-02 Thread Michael Mess
Now I have done further tests.
Sometimes calling network-manager restart once will suffice to get connected, 
but sometimes not. Then you can try again and again without getting a 
connection. 
Then networking restart and then network-manager restart will do it.

michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[sudo] password for michael: 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ sudo /etc/init.d/network restart 
networking   network-manager  
michael@thinkpad:~$ sudo /etc/init.d/networking restart 
[ ok ] Restarting networking (via systemctl): networking.service.
michael@thinkpad:~$ sudo /etc/init.d/network-manager restart 
[ ok ] Restarting network-manager (via systemctl): network-manager.service.
michael@thinkpad:~$ 

Thus it seems that sometimes on a failed connect something gets broken so that 
it prevents you from getting a connection and  that can be repaired by doing a 
networking restart.
I hope that this is useful to find the cause of this bug.

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

Title:
  Does not automatically reconnect to hidden WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running Lubuntu 14.04 32-bit on a Lenovo 3000 C200 laptop with an
  integrated Broadcom network adapter, I installed
  firmware-b43-installer and then successfully connected to my hidden
  (SSID not broadcast) WiFi net.

  But I see that it will not automatically reconnect.  I don't have to
  re-enter the password, but I do have to click the nm-applet indicator,
  choose 'Connect to Hidden Wi-Fi Network' and then choose my already-
  defined connection, which indeed has been saved but not used to
  automatically reconnect.

  If I edit the connection, I see that on the General tab it is already
  set to 'Automatically connect to this network when it is available.'

  The only way I can get automatic reconnection is to enable SSID
  Broadcast.

  And a similar effect: If I am connected to the network while SSID
  Broadcast is in effect and then disable SSID Broadcast, network-
  manager immediately loses the connection.

  Someone suggested that network-manager would find the hidden network
  if I just waited, but after waiting 15 minutes it had still not
  connected.

  Dual-booting this same laptop with Windows Vista, I see that Windows
  knows how to automatically reconnect to the hidden net.

  I see that https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/295796 describes similar behavior, but that was reported
  back in 2008 and I'm imagining that there should be a separate report
  for the new release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue May  6 10:24:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-25 (10 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.118  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1ac7ba941-660f-40c5-9b1f-4d24accc6225   
802-3-ethernet  

[Desktop-packages] [Bug 1552452] [NEW] /usr/bin/nm-applet:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_string_sized_new:g_string_new

2016-03-02 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding network-manager-applet.  This problem was most recently seen
with version 0.9.10.1-0ubuntu7, the problem page at
https://errors.ubuntu.com/problem/5145bafd3d088186ed436781fc6107f561ddd101
contains more details.

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


** Tags: precise saucy trusty vivid wily

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

Title:
  /usr/bin/nm-
  
applet:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_string_sized_new:g_string_new

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager-applet.  This problem was most recently seen
  with version 0.9.10.1-0ubuntu7, the problem page at
  https://errors.ubuntu.com/problem/5145bafd3d088186ed436781fc6107f561ddd101
  contains more details.

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

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


[Desktop-packages] [Bug 1550325] Re: gnome-language-selector is not MATE compatible [debdiff attached]

2016-03-02 Thread Martin Wimpress
** Changed in: ubuntu-mate
   Status: New => Fix Released

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

Title:
  gnome-language-selector is not MATE compatible [debdiff attached]

Status in ubuntu-mate:
  Fix Released
Status in im-config package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  The gnome-language-selector fallback input method is 'xim', which is
  not compatible with some applications when running under MATE. For
  example:

* https://bugs.launchpad.net/synapse-project/+bug/1219314

  gnome-language-selector should use the same defaults for MATE as it
  does for Unity.

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

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


[Desktop-packages] [Bug 1190907] Re: Compiz don't work

2016-03-02 Thread Christopher M. Penalver
Laszlo Arany, thank you for reporting this and helping make Ubuntu
better.

As per https://wiki.ubuntu.com/Releases, Ubuntu 13.04 reached EOL on
January 27, 2014.

Is this reproducible on a supported release?

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

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

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

Title:
  Compiz don't work

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  In 13.04 i install MATE, that is working fine, but Compiz dosn't. If i
  login with "ubuntu" session, Compiz is fine!

  In "dconf editor" hasn't "compiz-1" record, only "compiz".

  If i get "compiz --replace" in terminal, go away the windows borders.
  I open "Compiz config editor" i clik to "windowsdecoration" and
  nothing happens...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: xorg 1:7.7+1ubuntu4
  Uname: Linux 3.9.0-030900-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jun 14 10:08:35 2013
  DistUpgraded: Fresh install
  DistroCodename: raring
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0571]
 Subsystem: Micro-Star International Co., Ltd. Device [1462:0571]
  InstallationDate: Installed on 2013-05-31 (13 days ago)
  InstallationMedia: Ubuntu  "Raring" - Build amd64 LIVE Binary 20130425-23:39
  MachineType: MICRO-STAR INT'L CO.,LTD. MS-1057
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-030900-generic 
root=UUID=f57ce9bf-d1aa-41f6-8dab-e74035ca9bfe ro quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A1057IMS V7.08
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: MICRO-STAR INT'L CO.,LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA1057IMSV7.08:bd08/27/2007:svnMICRO-STARINT'LCO.,LTD.:pnMS-1057:pvr0571:cvnMICRO-STARINT'LCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: MS-1057
  dmi.product.version: 0571
  dmi.sys.vendor: MICRO-STAR INT'L CO.,LTD.
  version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.45+git20130607.a0178c00-0ubuntu0sarvatt~raring
  version.libgl1-mesa-dri: libgl1-mesa-dri 
9.2.0~git20130612.adf324ad-0ubuntu0sarvatt~raring
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
9.2.0~git20130612.adf324ad-0ubuntu0sarvatt~raring
  version.xserver-xorg-core: xserver-xorg-core 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.1.99+git20130531.bd2557ea-0ubuntu0sarvatt~raring
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.21.9+git20130612.1f180b89-0ubuntu0sarvatt~raring
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.7+git20130516.bf72ae1f-0ubuntu0sarvatt~raring
  xserver.bootTime: Fri Jun 14 09:48:14 2013
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 
2:1.13.4~git20130508+server-1.13-branch.10c42f57-0ubuntu0ricotz~raring
  xserver.video_driver: intel

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

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


[Desktop-packages] [Bug 1552417] Re: [X1100] Flickering after resume from RAM

2016-03-02 Thread Christopher M. Penalver
Tommy Trussell, thank you for reporting this and helping make Ubuntu
better.

To see if this is already resolved, could you please test
http://cdimage.ubuntu.com/daily-live/current/ (x64, not 32-bit) and
advise to the results?

** Description changed:

- Same defect as old Bug #318325 
- same hardware as Bug #1333697
- 
- System : Ubuntu 15.10 "wily"
- GPU : ATI express X1100
- Video driver : radeon
- 
  Steps to reproduce :
  - choose suspend
  - resume from ram
  => the screen will flicker while CPU activity is not high
  
- workaround :
- - launch an infinite loop that consume CPU : $ while true; do echo 
>/dev/null; done
- => the screen won't flicker while the CPU is busy
- 
- Launching this old laptop from a live "wily" 15.10 desktop image, but it
- was running up-to-date "trusty" 14.04. I even updated to the latest HWE
- kernel & packages just in case there's been some change but it still has
- the bug.
- 
- [On a lark I found a git repository for hacking the radeon driver but I
- don't even know C so I would need a lot of assistance to figure THAT
- out.]
+ WORKAROUND: Launch an infinite loop that consume CPU :
+ $ while true; do echo >/dev/null; done
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: i386
  CasperVersion: 1.365
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Mar  2 20:00:24 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
-Subsystem: Acer Incorporated [ALI] Device [1025:009f]
+  Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
+    Subsystem: Acer Incorporated [ALI] Device [1025:009f]
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
  Lsusb:
-  Bus 001 Device 002: ID 0951:160b Kingston Technology 
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 002: ID 0951:160b Kingston Technology
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5100
  PccardctlIdent:
-  Socket 0:
-no product info available
+  Socket 0:
+    no product info available
  PccardctlStatus:
-  Socket 0:
-no card
+  Socket 0:
+    no card
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- BOOT_IMAGE=/casper/vmlinuz
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.13
  dmi.board.name: Navarro
  dmi.board.vendor: Acer
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
  dmi.product.name: Aspire 5100
  dmi.product.version: V3.13
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Mar  2 13:50:49 2016
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9
  xserver.video_driver: radeon

** Tags added: 

[Desktop-packages] [Bug 955277] Re: screen flickering with RevengeOfTheTitans

2016-03-02 Thread Christopher M. Penalver
Achim, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/955277/comments/9
regarding you no longer have the hardware. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

** No longer affects: mesa (Ubuntu)

** Project changed: mesa => mesa (Ubuntu)

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

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

** Changed in: mesa (Ubuntu)
 Remote watch: freedesktop.org Bugzilla #47455 => None

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

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

Title:
  screen flickering with RevengeOfTheTitans

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  I have attached a video which shows the problem.
  As it seems something is going wrong with rendering in RevengeOfTheTitans and 
other apps.
  I also noticed the problem with WorldOfGoo for example.

  The flickering always happens not only in fullscreen mode.
  It also happens in unity2d.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgl1-mesa-dri 8.0.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  .tmp.unity.support.test.0:

  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Wed Mar 14 18:09:16 2012
  DistUpgraded: Log time: 2012-03-12 17:17:59.131744
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:01bd]
     Subsystem: Dell Device [1028:01bd]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MachineType: Dell Inc. MM061
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=cc1d049b-4ada-452b-a801-0f99d6874b3c ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to precise on 2012-03-12 (2 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Desktop-packages] [Bug 1552435] [NEW] white line on progress line

2016-03-02 Thread GDGooD
Public bug reported:

Description:Ubuntu Xenial Xerus (development branch)
Release:16.04

transmission-gtk:
  Installed: 2.84-3ubuntu1
  Candidate: 2.84-3ubuntu1
  Version table:
 *** 2.84-3ubuntu1 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

White line on progress line

Screenshot included

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: transmission-gtk 2.84-3ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
Uname: Linux 4.4.0-9-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Mar  3 00:13:02 2016
SourcePackage: transmission
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "snapshot332.png"
   
https://bugs.launchpad.net/bugs/1552435/+attachment/4587017/+files/snapshot332.png

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

Title:
  white line on progress line

Status in transmission package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  transmission-gtk:
Installed: 2.84-3ubuntu1
Candidate: 2.84-3ubuntu1
Version table:
   *** 2.84-3ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  White line on progress line

  Screenshot included

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: transmission-gtk 2.84-3ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  3 00:13:02 2016
  SourcePackage: transmission
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1550896] Re: Move GConf depends to a seperate binary

2016-03-02 Thread Julien Lavergne
Thanks for the answer. Here is my comments for the different solutions :

- New dh_gconf : it's seem a bit overkill, especially if pidgin is the
only one to use it. And I don't know dh enough to make this change in
the near future :-)

- hack on debian/rules : probably a good idea, but I don't think I can
make it clean with cdbs

- don't use misc:Depends : yes, it feels wrong. If something else use
this feature in the future, it will not be obvious to re-enable it in
the package (most of packages have misc:Depends).

- Considering it's seems broken, and used for a very limited use cases,
I think it's safe to just remove it. I attached the updated debdiff.


** Patch added: "pidgin_2.10.12-0ubuntu3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1550896/+attachment/4587016/+files/pidgin_2.10.12-0ubuntu3.debdiff

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

Title:
  Move GConf depends to a seperate binary

Status in pidgin package in Ubuntu:
  New
Status in pidgin package in Debian:
  New

Bug description:
  Currently, gconf on pidgin is only used to retrieve proxy settings
  from GNOME. It puts an hard depends on gconf, even if pidgin is used
  on a non-gnome environment. Also, it seems that this feature may be
  broken (see LP #878032 and https://developer.pidgin.im/ticket/13867).

  The included debdiff move away the gconf files to a pidgin-gnome
  binary, so people not using GNOME can remove the gconf depends.

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

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


[Desktop-packages] [Bug 955277] [NEW] screen flickering with RevengeOfTheTitans

2016-03-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have attached a video which shows the problem.
As it seems something is going wrong with rendering in RevengeOfTheTitans and 
other apps.
I also noticed the problem with WorldOfGoo for example.

The flickering always happens not only in fullscreen mode.
It also happens in unity2d.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libgl1-mesa-dri 8.0.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
.tmp.unity.support.test.0:

ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
Date: Wed Mar 14 18:09:16 2012
DistUpgraded: Log time: 2012-03-12 17:17:59.131744
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:01bd]
   Subsystem: Dell Device [1028:01bd]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
MachineType: Dell Inc. MM061
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=cc1d049b-4ada-452b-a801-0f99d6874b3c ro quiet splash vt.handoff=7
SourcePackage: mesa
UpgradeStatus: Upgraded to precise on 2012-03-12 (2 days ago)
dmi.bios.date: 06/13/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0KD882
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: MM061
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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


** Tags: apport-bug compiz-0.9 i386 precise regression-release 
single-occurrence ubuntu
-- 
screen flickering with RevengeOfTheTitans
https://bugs.launchpad.net/bugs/955277
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to mesa 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 1552424] Re: [FFE] NetworkManager 1.2-beta

2016-03-02 Thread Mathieu Trudel-Lapierre
It's not out yet; I'm trying to find out the roadmap but given that it's
beta right now, I expect it to be ready in time for release.

Our delta against Debian is limitted to some specific decisions we've
made (priority of devices, enabling some feature or another), and the
addition of support for oFono.

Indeed, it's not a risk-free update given the scope and the impact on
desktop and our users, it will need to be very much tested.

-- 
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:
  New

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 to access VPN service 

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

2016-03-02 Thread Stéphane Graber
Is Network Manager 1.2 out yet? I don't seem to remember seeing an
announcement.

If not, when is it expected to be out?

Also, can you comment on our existing delta (phone & others) and give
some more details on how those will be updated and tested?


Overall, I absolutely support us moving to 1.2, it does fix a lot of pain 
points that I've encountered in the past and I'm sure it would greatly benefit 
our users. But we need to make sure landing this won't cause regressions and 
that we'll ship with a properly supported NM by release time.

-- 
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:
  New

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 

[Desktop-packages] [Bug 1552424] [NEW] [FFE] NetworkManager 1.2-beta

2016-03-02 Thread Mathieu Trudel-Lapierre
Public bug reported:

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 to access VPN service definitions.
* New DHCP_FQDN key in ifcfg files to configure the full FQDN to be sent to
the DHCP servers.
* The timeout for DHCP requests can now be modified using the
'ipv4.dhcp-timeout' property.
* Added multicast_snooping option to BRIDGING_OPTS ifcfg key.
* Added support for detecting duplicate IPv4 addresses, with a timeout
configurable through the ipv4.dad-timeout connection property.
* Fixed a race condition that could potentially lead to unauthorized access
to connection secrets (CVE-2016-0764).
* dnsmasq configuration for shared connections can now be extended by
placing custom files in /etc/NetworkManager/dnsmasq-shared.d/.
* Generic devices are no longer assumed unless explicitly requested by
user.
* The reorder-header VLAN flag setting is now honored; to keep backwards
compatibility in behavior, an existing 

[Desktop-packages] [Bug 1552417] [NEW] [X1100] Flickering after resume from RAM

2016-03-02 Thread Tommy Trussell
Public bug reported:

Same defect as old Bug #318325 
same hardware as Bug #1333697

System : Ubuntu 15.10 "wily"
GPU : ATI express X1100
Video driver : radeon

Steps to reproduce :
- choose suspend
- resume from ram
=> the screen will flicker while CPU activity is not high

workaround :
- launch an infinite loop that consume CPU : $ while true; do echo >/dev/null; 
done
=> the screen won't flicker while the CPU is busy

Launching this old laptop from a live "wily" 15.10 desktop image, but it
was running up-to-date "trusty" 14.04. I even updated to the latest HWE
kernel & packages just in case there's been some change but it still has
the bug.

[On a lark I found a git repository for hacking the radeon driver but I
don't even know C so I would need a lot of assistance to figure THAT
out.]

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
CasperVersion: 1.365
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Mar  2 20:00:24 2016
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] 
[1002:5975] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:009f]
LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
Lsusb:
 Bus 001 Device 002: ID 0951:160b Kingston Technology 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer Aspire 5100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --- BOOT_IMAGE=/casper/vmlinuz
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2008
dmi.bios.vendor: Acer
dmi.bios.version: V3.13
dmi.board.name: Navarro
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5100
dmi.product.version: V3.13
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Mar  2 13:50:49 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: radeon

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


** Tags: apport-bug compiz-0.9 i386 radeon resume trusty ubuntu wily

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

Title:
  [X1100] Flickering after resume from RAM

Status in xorg package in Ubuntu:
  New

Bug description:
  Same defect as old Bug #318325 
  same hardware as Bug #1333697

  System : Ubuntu 15.10 "wily"
  GPU : ATI express X1100
  Video driver : radeon

  Steps to reproduce :
  - choose suspend
  - resume from ram
  => the screen will flicker while CPU activity is not high

  workaround :
  - launch an infinite loop that consume CPU : $ while true; do echo 
>/dev/null; done
  => the screen won't flicker while the CPU is busy

  Launching this old laptop from a live "wily" 15.10 desktop image, but
  it was running up-to-date "trusty" 14.04. I even updated to the latest
  HWE kernel & packages just in case there's been some change but it
  still has the bug.

  [On a lark I found a git repository for hacking the radeon driver but
  I don't even know 

[Desktop-packages] [Bug 1514229] Re: ZTE WCDMA modem not identified correctly

2016-03-02 Thread Mathieu Trudel-Lapierre
nov 10 00:55:25 sstefan-aluNovo ModemManager[977]:   Modem 
/org/freedesktop/ModemManager1/Modem/2: state changed (enabling -> registered)
nov 10 00:55:25 sstefan-aluNovo NetworkManager[1007]:   (ttyUSB1): modem 
state changed, 'enabling' --> 'registered' (reason: user-requested)
nov 10 00:55:25 sstefan-aluNovo NetworkManager[1007]:   (ttyUSB1): device 
state change: unavailable -> disconnected (reason 'modem-available') [20 30 58]
nov 10 00:55:25 sstefan-aluNovo NetworkManager[1007]:   Device 'ttyUSB1' 
has no connection; scheduling activate_check in 5 seconds.

Is there more than one modem connected? The above logs, from comment #7
seem to indicate that the modem is correctly found, and succesfully
registered to the network. Does it show up in the network manager
indicator?

** Changed in: usb-modeswitch (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  ZTE WCDMA modem not identified correctly

Status in usb-modeswitch package in Ubuntu:
  Incomplete

Bug description:
  Connecting a ZTE WCDMA Modem does not allow broad band internet
  connection. The modem is identified not as a modem.

  Nov  8 19:46:48 v5 usb_modeswitch[8043]: usb_modeswitch: switched to 
19d2:1514 on 1/11
  Nov  8 19:46:49 v5 usb_modeswitch_dispatcher[8043]: Unable to open bind list 
file: No such file or directory
  Nov  8 19:46:49 v5 usb_modeswitch[8043]: usb_modeswitch: add device ID 
19d2:1514 to driver option
  Nov  8 19:46:49 v5 usb_modeswitch[8043]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Nov  8 19:46:56 v5 systemd[1]: Started USB_ModeSwitch_1-3.

  
  $ lsusb
  Bus 003 Device 002: ID 8087:8000 Intel Corp. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd 
  Bus 001 Device 002: ID 04ca:2004 Lite-On Technology Corp. Bluetooth 4.0 
[Broadcom BCM20702A0]
  Bus 001 Device 011: ID 19d2:1514 ZTE WCDMA Technologies MSM 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  8 19:46:31 2015
  InstallationDate: Installed on 2015-08-18 (82 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to wily on 2015-11-08 (0 days ago)

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

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


[Desktop-packages] [Bug 1483257] Re: Huawei E3372 (& other hilink dongles?) cannot be used for connecting to the internet

2016-03-02 Thread Mathieu Trudel-Lapierre
Please reproduce the problem and then attach the complete file
/var/log/syslog from the system. The previous JournalErrors doesn't
appear to include the important data from usb-modeswitch or
NetworkManager/ModemManager.

Also, lxcbr0 is not related in any way to the modem; its IP address is
set up automatically, and all of it comes from lxc, a container
management tool that is apparently installed on your system.

** Changed in: usb-modeswitch (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Huawei E3372 (& other hilink dongles?) cannot be used for connecting
  to the internet

Status in usb-modeswitch package in Ubuntu:
  Incomplete

Bug description:
  I have Huawei E3372 which works directly when I plug it in Windows 10,
  but on Ubuntu I cannot use it for connecting to the internet. It's
  light is cyan which means it's connected to 4G network, but it does
  nothing.

  It appears in lsusb: `Bus 001 Device 003: ID 12d1:1f01 Huawei
  Technologies Co., Ltd. E353/E3131 (Mass storage mode)`

  And it also appears in ifconfig:

  ```
  lxcbr0Link encap:Ethernet  HWaddr FILTERED  
inet addr:10.0.3.1  Bcast:0.0.0.0  Mask:255.255.255.0
inet6 addr: fe80::FILTERED/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0 
RX bytes:0 (0.0 B)  TX bytes:8993 (8.9 KB)
  ```

  I also don't understand where the address 10.0.3.1 comes from as in
  Windows the control panel was in 192.168.8.1 or something like it.

  I also found another bug report,
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1424181 but I
  don't think this is a dupicate as from the title it looks like it
  doesn't appear in lsusb and that bug has expired. This package also
  seems to have bug reports for other dongles.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: usb-modeswitch 2.2.3+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop:
   
  Date: Mon Aug 10 16:11:00 2015
  InstallationDate: Installed on 2015-07-31 (10 days ago)
  InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Alpha amd64 (20150729)
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1514231] Re: Huawei Broadband stick not recognized

2016-03-02 Thread Mathieu Trudel-Lapierre
I don't know, looks to me like the modem was switched correctly:

Bus 001 Device 012: ID 12d1:1446 Huawei Technologies Co., Ltd. Broadband
stick (modem on)

Please attach the whole of /var/log/syslog (after checking that there is
no sensitive information) to this bug report; we'll need it to make sure
any steps happening after the initial detection are running correctly.

** Changed in: usb-modeswitch (Ubuntu)
   Status: New => Incomplete

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

Title:
  Huawei Broadband stick not recognized

Status in usb-modeswitch package in Ubuntu:
  Incomplete

Bug description:
  USB Huawei broadband USB modem not recognized as modem but only as
  storage

  Nov  8 19:53:04 v5 usb_modeswitch_dispatcher[8223]: message repeated 3 times: 
[ Could not read attribute: No such file or directory]
  Nov  8 19:53:05 v5 usb_modeswitch[8223]: usb_modeswitch: use overriden config 
12d1:1446 from collection /etc/usb_modeswitch.d; make sure this is intended
  Nov  8 19:53:05 v5 usb_modeswitch[8223]: usb_modeswitch: please report any 
new or corrected settings; otherwise, check for outdated files
  Nov  8 19:53:05 v5 usb_modeswitch: switch device 12d1:1446 on 001/012
  Nov  8 19:53:06 v5 usb_modeswitch_dispatcher[8223]: Could not read attribute: 
No such file or directory
  Nov  8 19:53:06 v5 usb_modeswitch[8223]: usb_modeswitch: switched to 
12d1:1446 on 1/12
  Nov  8 19:53:07 v5 usb_modeswitch_dispatcher[8223]: Unable to open bind list 
file: No such file or directory
  Nov  8 19:53:07 v5 usb_modeswitch[8223]: usb_modeswitch: add device ID 
12d1:1446 to driver option
  Nov  8 19:53:07 v5 usb_modeswitch[8223]: usb_modeswitch: please report the 
device ID to the Linux USB developers!
  Nov  8 19:53:14 v5 systemd[1]: Started USB_ModeSwitch_1-3:1.0.

  
  $ lsusb
  Bus 003 Device 002: ID 8087:8000 Intel Corp. 
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd 
  Bus 001 Device 002: ID 04ca:2004 Lite-On Technology Corp. Bluetooth 4.0 
[Broadcom BCM20702A0]
  Bus 001 Device 012: ID 12d1:1446 Huawei Technologies Co., Ltd. Broadband 
stick (modem on)
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: usb-modeswitch 2.2.5+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  8 19:53:21 2015
  InstallationDate: Installed on 2015-08-18 (82 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to wily on 2015-11-08 (0 days ago)

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

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


[Desktop-packages] [Bug 1552298] Re: chromium-browser should depend on kmod

2016-03-02 Thread Christopher Townsend
I should add that nothing fails when lsmod is not present, but i915
detection will not work properly without it.

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

Title:
  chromium-browser should depend on kmod

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The chromium-browser package should depend on the kmod package due to
  the following workaround in /usr/bin/chromium-browser:

  lsmod |grep ^i915\  >/dev/null && export LIBGL_DRI3_DISABLE=1

  There are situations in which chromium-browser can be installed
  without kmod already being installed such as in a container for
  Libertine (the convergence container for phones/tablets/future
  desktop).

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

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


[Desktop-packages] [Bug 1552301] Re: The lsmod workround in /usr/bin/chromium-browser should catch lsmod errors

2016-03-02 Thread Christopher Townsend
After looking at this further, I don't think this is really an issue.  I
think something else is causing the failure we are seeing, so I'm going
to mark this Invalid.

** Changed in: chromium-browser (Ubuntu)
   Status: New => Invalid

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

Title:
  The lsmod workround in /usr/bin/chromium-browser should catch lsmod
  errors

Status in chromium-browser package in Ubuntu:
  Invalid

Bug description:
  When trying to use Chromium on a Freiza tablet, /proc/modules does not
  exist, thus the following workaround fails:

  lsmod |grep ^i915\  >/dev/null && export LIBGL_DRI3_DISABLE=1

  and causes /usr/bin/chromium-browser to fail.

  That line should catch any errors from lsmod, assume there is no i915,
  and move along instead of bailing.

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

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


[Desktop-packages] [Bug 1542028] Re: xapp window should reflect app name rather than "Xmir root window"

2016-03-02 Thread Christopher Townsend
** Changed in: libertine/trunk
   Status: Triaged => In Progress

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

Title:
  xapp window should reflect app name rather than "Xmir root window"

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  In Progress
Status in libertine package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Launching xapp on ubuntu-pd in windowed mode, results in a window title of 
"root xmir"
  It should reflect the app name in the container.

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

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


[Desktop-packages] [Bug 1542028] Re: xapp window should reflect app name rather than "Xmir root window"

2016-03-02 Thread Launchpad Bug Tracker
** Branch linked: lp:~townsend/libertine/0.99.11-release

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

Title:
  xapp window should reflect app name rather than "Xmir root window"

Status in Canonical System Image:
  Confirmed
Status in Canonical Pocket Desktop:
  New
Status in Libertine:
  Fix Committed
Status in Libertine devel series:
  Fix Committed
Status in Libertine trunk series:
  In Progress
Status in libertine package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  Launching xapp on ubuntu-pd in windowed mode, results in a window title of 
"root xmir"
  It should reflect the app name in the container.

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

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


[Desktop-packages] [Bug 955277] Re: screen flickering with RevengeOfTheTitans

2016-03-02 Thread Achim
Christopher, I am sorry I don't have the hardware any more. This bug-
report is simply to old. If you like you can close it.

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

Title:
  screen flickering with RevengeOfTheTitans

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  I have attached a video which shows the problem.
  As it seems something is going wrong with rendering in RevengeOfTheTitans and 
other apps.
  I also noticed the problem with WorldOfGoo for example.

  The flickering always happens not only in fullscreen mode.
  It also happens in unity2d.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgl1-mesa-dri 8.0.1-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
  Uname: Linux 3.2.0-18-generic-pae i686
  .tmp.unity.support.test.0:

  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Wed Mar 14 18:09:16 2012
  DistUpgraded: Log time: 2012-03-12 17:17:59.131744
  DistroCodename: precise
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:01bd]
     Subsystem: Dell Device [1028:01bd]
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MachineType: Dell Inc. MM061
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae 
root=UUID=cc1d049b-4ada-452b-a801-0f99d6874b3c ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: Upgraded to precise on 2012-03-12 (2 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0KD882
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0KD882:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.0+bzr3035-0ubuntu1
  version.libdrm2: libdrm2 2.4.30-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 
1:2.6.99.901+git20120126-0ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20111219.aacbd629-0ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20111201+b5534a1-1build2

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

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


[Desktop-packages] [Bug 1507769] Re: App store does not display images

2016-03-02 Thread Pat McGowan
The fix from comment #26 will be in ota 10, now in proposed.

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

Title:
  App store does not display images

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in thumbnailer package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  On both mako and arale using latest rc-proposed
  No images are loaded in the app store view
  I noticed free showed less than 100MB available on the mako
  Closing a few apps and refreshing loaded the images, as did  a reboot on the 
arale.

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

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


[Desktop-packages] [Bug 1552380] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

2016-03-02 Thread Apport retracing service
*** This bug is a duplicate of bug 1546641 ***
https://bugs.launchpad.net/bugs/1546641

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  unity-settings-daemon crashed with SIGSEGV in
  up_exported_daemon_get_lid_is_closed()

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

Bug description:
  Happened when the system first logged in.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-settings-daemon 15.04.1+16.04.20160209-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-7-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb 29 14:20:17 2016
  ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
  InstallationDate: Installed on 2016-01-17 (45 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160116)
  ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fbd3dd4be69 
:   mov(%rbx),%rdi
   PC (0x7fbd3dd4be69) ok
   source "(%rbx)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%rdi" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-settings-daemon
  StacktraceTop:
   up_exported_daemon_get_lid_is_closed () from 
/usr/lib/x86_64-linux-gnu/libupower-glib.so.3
   gsd_power_manager_start () from 
/usr/lib/unity-settings-daemon-1.0/libpower.so
   ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
   gnome_settings_plugin_info_activate ()
   ?? ()
  Title: unity-settings-daemon crashed with SIGSEGV in 
up_exported_daemon_get_lid_is_closed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Desktop-packages] [Bug 1552385] [NEW] Libreoffice Applications erased and not possible to re-install

2016-03-02 Thread Aymerico69
Public bug reported:

Hello,

Since 1 week, I have no access to Libreoffice Application and I can't install 
the package.
I have this message too appears at the same time when I enter a sudo command: 
sudo: unable to resolve host "user"

Here, the message which appears when I try to install libreoffice:
sudo apt-get install libreoffice-common
sudo: unable to resolve host aymerico_7010
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies.
 libreoffice-common : Depends: ure but it is not going to be installed
  Recommends: python3-uno (>= 4.4.0~beta2) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.

Thank in advance for help.
Bye

** Affects: software-center (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Libreoffice Applications erased and not possible to re-install

Status in software-center package in Ubuntu:
  New

Bug description:
  Hello,

  Since 1 week, I have no access to Libreoffice Application and I can't install 
the package.
  I have this message too appears at the same time when I enter a sudo command: 
sudo: unable to resolve host "user"

  Here, the message which appears when I try to install libreoffice:
  sudo apt-get install libreoffice-common
  sudo: unable to resolve host aymerico_7010
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   libreoffice-common : Depends: ure but it is not going to be installed
Recommends: python3-uno (>= 4.4.0~beta2) but it is not 
going to be installed
  E: Unable to correct problems, you have held broken packages.

  Thank in advance for help.
  Bye

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

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


[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

2016-03-02 Thread Jeff Lane
H... ok.  I didn't realize there was a second pulseaudio config.

I have no idea how it got there, nor where it came from, and I do not
recall ever setting it, but sure enough:

### Make some devices default
#set-default-sink output
set-default-source 2
set-source-mute 2 0

So this is likely cruft left over from an older version... to build this
machine, I did a fresh Xenial install and then installed a backup of
/home/$USER via rsync.

However, I do not ever remember configuring this file at any point in
the past, AND this worked just fine in Trusty, and also worked fine in
Xenial until it stopped working, then it started working, then it
stopped working.

Is there some sort of race condition where ~/.pulse/default.pa may or
may not be the default.pa Pulse uses?

Anyway, I'm removing the file and restarting to see what happens.

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  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/1547585/+subscriptions

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


[Desktop-packages] [Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

2016-03-02 Thread Frogs Hair
Ubuntu 16.04 beta 1 also affected

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

Title:
  gvfsd-metadata causes 100% CPU usage

Status in gvfs:
  Fix Released
Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Precise:
  Fix Released
Status in gvfs source package in Trusty:
  Fix Released
Status in gvfs source package in Utopic:
  Fix Released
Status in gvfs source package in Vivid:
  Fix Released
Status in gvfs package in Debian:
  Fix Released

Bug description:
  Binary package hint: gvfs

  Failure to write metadata results in an infinite loop that keeps
  trying to write, thousands of times per second.

  Steps to reproduce:
  1. Open Firefox
  2. Save a data: URL (URL that contains the content, with several thousands 
bytes, often generated by webapps or extensions) as file

  (There are other ways to run into this problem, e.g. disk full or
  other error situations. data: URLs are just the easiest way to
  reproduce.)

  Actual result:
  - File is saved
  - 100% CPU
  - Extremely high number of file operations by gvfs - billions
  - Never stops

  Expected result:
  Failure to write metadata should just fail, not try again

  Fix:
  Patch available and accepted by GNOME
  https://bugzilla.gnome.org/show_bug.cgi?id=637095

  --- Original description ---
  After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or 
Gnome-commander take several minutes when there are many files in it e.g. 
10.000. Interestingly Midnight-commander does not have this problem. Opening 
such folders does not hang with MC.
  Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill 
it the computer stops "hanging". I am using the 32bit version of Karmic too and 
there is no such Problem (although tested on a different computer).

  Please fix this because it is highly annyoing. Right now i am killing
  it every 20s with the watch command to be able to work at all.

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

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


[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

2016-03-02 Thread Jeff Lane
et viola, it's working.

Still, no idea where that second, edited version came from :/

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  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/1547585/+subscriptions

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


[Desktop-packages] [Bug 1547585] Re: Pulseaudio stopped working but sound still works at the low level (can be controlled with alsamixer)

2016-03-02 Thread David Henningsson
Hmm, but the log shows exactly what happens if someone changes the last
lines of /etc/pulse/default.pa from the below (this is the original):

### Make some devices default
#set-default-sink output
#set-default-source input

to this:

### Make some devices default
#set-default-sink output
set-default-source 2

...notice how they should be commented out by default.

Or if it loads a copy of default.pa in ~/.config/pulse or ~/.pulse where
this change has been done?

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

Title:
  Pulseaudio stopped working but sound still works at the low level (can
  be controlled with alsamixer)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Not sure if it was an update or what that broke, but I suddenly have
  no ability to control sound.

  Sound settings no longer show any output devices and syslog is flooded
  with pulseaudio messages.

  Haven't tried a reboot, that's next.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   bladernr   2773 F...m chrome
   /dev/snd/pcmC0D0p:   bladernr   2773 F...m chrome
   /dev/snd/controlC0:  bladernr   2773 F chrome
   /dev/snd/timer:  bladernr   2773 f chrome
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:10:11 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170MX-Gaming 5
  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: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd10/16/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170MX-Gaming5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170MX-Gaming5:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170MX-Gaming 5
  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/1547585/+subscriptions

-- 
Mailing list: https://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 1041790]

2016-03-02 Thread fjgaude
Please take me off too.

frank

On 03/02/2016 03:33 AM, Jani-nikula wrote:
> (In reply to Sander Eikelenboom from comment #250)
>> Is there a way to get off the CC-list of this slightly depressing kind of
>> "catch-all" bug ?
> CC list is at the top right corner. Choose the address, tick "Remove
> selected CCs", and hit Save Changes.
>
> I've done this for you now.
>

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

Title:
  [snb] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
  i915.semaphores=0

Status in xf86-video-intel:
  In Progress
Status in linux package in Ubuntu:
  Incomplete
Status in sandybridge-meta package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Triaged

Bug description:
  X locks up periodically for a 2 to ten seconds at a time and this
  crash log gets generated. It's significantly more than several times a
  day but not quite continuous. If you indeed have this bug, that should
  stop the lockups from happening. Irrespective, please file a new bug
  report so your hardware may be tracked.

  WORKAROUND: Edit your /etc/default/grub from:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

  to:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0"

  run the following and reboot:
  sudo update-grub

  The side effects of this is rendering throughput is dropped by 10%
  with SNA, or as much as 3x with UXA. OpenGL performance is likely to
  be reduced by about 30%. More CPU time is spent waiting for the GPU
  with rc6 disabled, so increased power consumption.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
  ApportVersion: 2.5.1-0ubuntu2
  Architecture: amd64
  Chipset: sandybridge-m-gt2
  Date: Sun Aug 26 16:06:32 2012
  DistroCodename: quantal
  DistroVariant: ubuntu
  DuplicateSignature: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 
0x0b140001 Ubuntu 12.10
  EcryptfsInUse: Yes
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GpuHangFrequency: Continuously
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
  InterpreterPath: /usr/bin/python3.2mu
  MachineType: Dell Inc. Dell System XPS L502X
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 
root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   xserver-xorg 1:7.7+1ubuntu3
   libdrm2  2.4.38-0ubuntu2
   xserver-xorg-video-intel 2:2.20.3-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: [sandybridge-m-gt2] GPU lockup  IPEHR: 0x0b160001 IPEHR: 0x0b140001
  UdevDb: Error: [Errno 2] No such file or directory: 'udevadm'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 05/29/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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


[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2016-03-02 Thread Christopher M. Penalver
LeoRochael, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

2016-03-02 Thread LeoRochael
What information is needed to remove the "incomplete" mark from this
issue? It seems that the steps for reproduction are really clear cut:

 - Use two videocards with two monitors.

Or:

 - Setup and connect a DisplayLink device to a USB port and configure it
for use.

Then:

See mouse flickering on one of the monitors, usually the primary.

On my case, with a DisplayLink device on 14.04, the flickering is so bad
that the mouse is nearly invisible most of the time if it's positioned
in the bottom two thirds of the primary display.

I'd love to have a workaround in the form of a software drawn cursor,
but the `SWCursor` option in the `Device` section of my intel board on
Xorg.conf makes no difference.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1548273] Re: Periodic crashes

2016-03-02 Thread gonssal
I can't, because I'm not 100% sure. I don't write down the exact date
everytime my system crashes.

You can wait for the next crash if you want, but it hasn't happened for
the last 3 work-days. If it happens again, I'll notice the time and
check /var/crash.

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

Title:
  Periodic crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system periodically freezes and I have to do a hard reboot. Very
  unpleasant expercience so far with ubuntu.

  .xsession-errors after reboot:

  Failed to open BO for returned DRI2 buffer (1919x18, dri2 back buffer, named 
20).
  This is likely a bug in the X Server that will lead to a crash soon.
  Failed to open BO for returned DRI2 buffer (1919x18, dri2 back buffer, named 
20).
  This is likely a bug in the X Server that will lead to a crash soon.
  Failed to open BO for returned DRI2 buffer (1919x18, dri2 back buffer, named 
24).
  This is likely a bug in the X Server that will lead to a crash soon.

  Processor: i5-5200U
  SNA drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Feb 22 12:02:26 2016
  InstallationDate: Installed on 2016-02-01 (20 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda1: clean, 644191/6815744 files, 17918892/27238400 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:b096]
  InstallationDate: Installed on 2016-02-01 (29 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B09611
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic 
root=UUID=a9a99c43-83be-462e-b4d8-c29e611ed395 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  Tags:  wily kubuntu
  UdevLog: Error: [Errno 2] El fitxer o directori no existeix: '/var/log/udev'
  Uname: Linux 4.2.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EB096IMS V1.4
  dmi.board.name: MS-B0961
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 13
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEB096IMSV1.4:bd09/07/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B09611:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-B0961:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct13:cvr1.0:
  dmi.product.name: MS-B09611
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.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: Tue Mar  1 10:40:00 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post 

[Desktop-packages] [Bug 1129409] Re: [SRU] Nvidia and AMD graphics drivers should indicate whether they provide libcuda.so.1, libOpenCL.so.1, etc.

2016-03-02 Thread Graham Inggs
@oriolpont: when you install wine, nvidia-libopencl1-* should be removed and 
ocl-icd-libopencl1 should be installed, nvidia-opencl-icd-* should remain in 
place.
You can have multiple OpenCL ICDs installed, but only one OpenCL ICD Loader 
(libOpenCL.so).

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

Title:
  [SRU] Nvidia and AMD graphics drivers should indicate whether they
  provide libcuda.so.1, libOpenCL.so.1, etc.

Status in boinc package in Ubuntu:
  Fix Released
Status in fglrx-installer package in Ubuntu:
  Fix Released
Status in fglrx-installer-updates package in Ubuntu:
  Fix Released
Status in nvidia-cuda-toolkit package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-304-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-310-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-313-updates package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-319 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-319-updates package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in pycuda package in Ubuntu:
  Fix Released
Status in pyopencl package in Ubuntu:
  Fix Released
Status in starpu-contrib package in Ubuntu:
  Fix Released
Status in viennacl package in Ubuntu:
  Invalid
Status in boinc source package in Trusty:
  Invalid
Status in fglrx-installer source package in Trusty:
  Fix Released
Status in fglrx-installer-updates source package in Trusty:
  Fix Released
Status in nvidia-cuda-toolkit source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Invalid
Status in pycuda source package in Trusty:
  Invalid
Status in pyopencl source package in Trusty:
  Invalid
Status in starpu-contrib source package in Trusty:
  Invalid
Status in viennacl source package in Trusty:
  Invalid
Status in boinc source package in Utopic:
  Invalid
Status in fglrx-installer source package in Utopic:
  Fix Released
Status in fglrx-installer-updates source package in Utopic:
  Fix Released
Status in nvidia-cuda-toolkit source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-304-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-310-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-313-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319 source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-319-updates source package in Utopic:
  Invalid
Status in nvidia-graphics-drivers-340 source package in Utopic:
  Invalid
Status in pycuda source package in Utopic:
  Invalid
Status in pyopencl source package in Utopic:
  Invalid
Status in starpu-contrib source package in Utopic:
  Invalid
Status in viennacl source package in Utopic:
  Invalid
Status in nvidia-cuda-toolkit package in Debian:
  Fix Released

Bug description:
  [Impact]

  * wine and fglrx are not coinstallable.

  [Test Case]

   * try to install them
   * there is a conflict with libopencl1 in control file, preventing 
coinstallation.

  The nvidia-cuda-toolkit package needs to depend on a minimum version of the 
CUDA library included in nvidia-graphics-drivers.
  The current Debian version of nvidia-cuda-toolkit (5.0.35-4) does this on 
Debian systems by checking the version of libcuda1 and on Ubuntu systems by 
checking the version of nvidia-current, nvidia-curent-updates, 
nvidia-experimental-304 or nvidia-experimental-310.

  It would greatly simplify maintenance of packages building against
  libcuda.so.1 and libOpenCL.so.1 if the nvidia-graphics drivers could
  provide virtual packages that reflect the API level, for example,
  libcuda-5.0-1 and libopencl-1.2-1.

  It was decided that the nvidia drivers packages will provide libcuda-5.0-1, 
libopencl1 and opencl-icd (LP: #763457) virtual packages. Additionally, 
nvidia-*.shlibs would contain:
  libOpenCL  1 libopencl1
  libcuda1 libcuda-5.0-1
  libGL 1 libgl1

  Similarly, the amd drivers package will provide libopencl1 and opencl-icd 
virtual packages, as well as an .shlibs containing:
  libOpenCL  1 libopencl1
  libGL 1 libgl1

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1548273] Re: Periodic crashes

2016-03-02 Thread Christopher M. Penalver
gonssal, to advise, I need to know if they are or aren't, as it does
matter here.

Hence, could you please adjust the wording to advise precisely one way
or the other?

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

Title:
  Periodic crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system periodically freezes and I have to do a hard reboot. Very
  unpleasant expercience so far with ubuntu.

  .xsession-errors after reboot:

  Failed to open BO for returned DRI2 buffer (1919x18, dri2 back buffer, named 
20).
  This is likely a bug in the X Server that will lead to a crash soon.
  Failed to open BO for returned DRI2 buffer (1919x18, dri2 back buffer, named 
20).
  This is likely a bug in the X Server that will lead to a crash soon.
  Failed to open BO for returned DRI2 buffer (1919x18, dri2 back buffer, named 
24).
  This is likely a bug in the X Server that will lead to a crash soon.

  Processor: i5-5200U
  SNA drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Feb 22 12:02:26 2016
  InstallationDate: Installed on 2016-02-01 (20 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   fsck from util-linux 2.26.2
   /dev/sda1: clean, 644191/6815744 files, 17918892/27238400 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: kubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:b096]
  InstallationDate: Installed on 2016-02-01 (29 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: MICRO-STAR INTERNATIONAL CO., LTD MS-B09611
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic 
root=UUID=a9a99c43-83be-462e-b4d8-c29e611ed395 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4
  Tags:  wily kubuntu
  UdevLog: Error: [Errno 2] El fitxer o directori no existeix: '/var/log/udev'
  Uname: Linux 4.2.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/07/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: EB096IMS V1.4
  dmi.board.name: MS-B0961
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 13
  dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrEB096IMSV1.4:bd09/07/2015:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-B09611:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-B0961:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct13:cvr1.0:
  dmi.product.name: MS-B09611
  dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.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: Tue Mar  1 10:40:00 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

  1   2   >