[Desktop-packages] [Bug 1395387] Re: package fglrx-updates 2:14.201-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2015-01-25 Thread Dudytz
*** This bug is a duplicate of bug 1370270 ***
https://bugs.launchpad.net/bugs/1370270

** This bug has been marked a duplicate of bug 1370270
   package fglrx-updates-core 2:14.201-0ubuntu1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2

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

Title:
  package fglrx-updates 2:14.201-0ubuntu2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 2

Status in fglrx-installer-updates package in Ubuntu:
  Confirmed

Bug description:
  Setting up fglrx-updates (2:14.201-0ubuntu2) ...
  update-alternatives: warning: forcing reinstallation of alternative 
/usr/lib/x86  
_64-linux-gnu/mesa/ld.so.conf because link group x86_64-linux-gnu_gl_conf is 
bro  ken
  update-alternatives: error: unable to remove '/etc/ati': Is a directory
  dpkg: error processing package fglrx-updates (--configure):
   subprocess installed post-installation script returned error exit status 2
  dpkg: dependency problems prevent configuration of fglrx-amdcccle-updates:
   fglrx-amdcccle-updates depends on fglrx-updates; however:
Package fglrx-updates is not configured yet.

  dpkg: error processing package fglrx-amdcccle-updates (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered while processing:
   fglrx-updates
   fglrx-amdcccle-updates

  Upgrade complete

  The upgrade has completed but there were errors during the upgrade
  process.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: fglrx-updates 2:14.201-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  Date: Sun Nov 23 01:32:16 2014
  DistUpgraded: 2014-11-23 01:40:52,272 ERROR SystemError from cache.commit(): 
installArchives() failed
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 14.201, 3.13.0-39-generic, x86_64: installed
   fglrx-updates-core, 14.201, 3.16.0-24-generic, x86_64: installed
  DuplicateSignature: package:fglrx-updates:2:14.201-0ubuntu2:subprocess 
installed post-installation script returned error exit status 2
  EcryptfsInUse: Yes
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Device [1682:303a]
  InstallationDate: Installed on 2014-10-15 (38 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. OptiPlex 360
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
vt.handoff=7
  SourcePackage: fglrx-installer-updates
  Title: package fglrx-updates 2:14.201-0ubuntu2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 2
  UpgradeStatus: Upgraded to utopic on 2014-11-22 (0 days ago)
  dmi.bios.date: 07/02/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0T656F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd07/02/2009:svnDellInc.:pnOptiPlex360:pvr:rvnDellInc.:rn0T656F:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 360
  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.58+git20141120.4f44ecc6-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
10.5.0~git20141120.5e37a2a4-0ubuntu0ricotz4~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
10.5.0~git20141120.5e37a2a4-0ubuntu0ricotz4~trusty
  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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.916+git20141120.0f15b8b4-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
  xserver.bootTime: Sat Nov 22 15:24:24 2014
  xserver.configfile: default
  

[Desktop-packages] [Bug 1308922] Re: There is no way to change the bluetooth system name from the standard GUI

2014-12-07 Thread Dudytz
Whe are 107 people that confirmed this bug. I have exactly the problem
that Hans describes in #4. Please, change this bug to medium or high to
priorise the resolution, thanks!

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

Title:
  There is no way to change the bluetooth system name from the standard
  GUI

Status in Unity Control Center:
  Invalid
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  The built-in bluetooth adapter of my laptop (running 14.04 Trusty
  Tahr, upgraded from 13.10 Saucy Salamander) appears with the default
  name ubuntu-0. I could not find a way to change this name through
  the GUI tools (eg. System Settings-Bluetooth Settings or System
  Settings-Details-Overview-Device name)).  This seems to be related
  to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/989817 and
  probably caused by
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/644198 as my
  hostname is properly configured.

  The explanation of the source of the problem in
  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/989817/comments/12
  seems to match the situation and so appears to be correct. The Device
  name in System Settings-Details-Overview is the proper hostname,
  and it is also greyed-out, so I can't make any modifications there.
  Unfortunately, short of editing manually
  /var/lib/bluetooth/[$ADDR]/config or creating /etc/machine-info I
  couldn't find a way to solve the problem. /etc/bluetooth/main.conf
  contains the default Name = %h-%d.

  I'm not completely sure how this could be solved - either there should
  be a way to set the name through System Settings  if it has been
  stored already in /var/lib/bluetooth/[$ADDR]/config or ubiquity
  package should replace ubuntu-0 with the hostname during the post-
  installation phase, after a proper hostname has been configured.

  Please, feel free to reassign this bug to one of the other packages if
  you think that it should be solved there.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 11:23:21 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2013-12-19 (119 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to trusty on 2014-04-03 (13 days ago)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu13
   deja-dup 30.0-0ubuntu4
   gnome-control-center 1:3.6.3-0ubuntu56

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

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


[Desktop-packages] [Bug 986991] Re: Hostname left to ubuntu-0 in Bluetooth settings after install from live cd

2014-09-26 Thread Dudytz
*** This bug is a duplicate of bug 1308922 ***
https://bugs.launchpad.net/bugs/1308922

** This bug is no longer a duplicate of bug 989817
   Cannot change bluetooth device name
** This bug has been marked a duplicate of bug 1308922
   There is no way to change the bluetooth system name from the standard GUI

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

Title:
  Hostname left to ubuntu-0 in Bluetooth settings after install from
  live cd

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

Bug description:
  After installing from a live-cd session when given a hostname to the
  machine, the hostname is applied, but for some reason the live cd
  hostname ubuntu-0 is being shown in the bluetooth settings instead
  of the user's chosen hostname.

  Also: the name gets reset to ubuntu-0 after reboots when you change
  it manually with hciconfig

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
  Uname: Linux 3.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.0.1-0ubuntu5
  Architecture: amd64
  Date: Sun Apr 22 22:04:32 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120417)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3
   deja-dup22.0-0ubuntu2
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

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

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


[Desktop-packages] [Bug 1242112] Re: Shutdown/restart dialogue is not working if Cairo-Dock and its Launcher-API-Deamon are running or if another app is registered to LauncherEntry interface of Unity

2014-09-19 Thread Dudytz
** Changed in: plank
   Status: Invalid = Confirmed

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

Title:
  Shutdown/restart dialogue is not working if Cairo-Dock and its
  Launcher-API-Deamon are running or if another app is registered to
  LauncherEntry interface of Unity DBus

Status in Cairo-Dock : Core:
  Invalid
Status in DockbarX:
  Invalid
Status in Plank:
  Confirmed
Status in Unity:
  Confirmed
Status in “cairo-dock” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Confirmed
Status in “cairo-dock” source package in Trusty:
  Invalid
Status in “unity” source package in Trusty:
  Confirmed
Status in “cairo-dock” source package in Utopic:
  Invalid
Status in “unity” source package in Utopic:
  Confirmed

Bug description:
  Unity's shutdown/restart dialogue is not working when another application is 
registered to LauncherEntry interface of Unity DBus.
  It seems we have this bug when Cairo-Dock (and its Launcher-API-Deamon), 
DockbarX or Plank are launched before Unity.

  [How to reproduce this bug]
  Simply launch this script at startup (launched before Unity). It will watch 
'com.canonical.Unity.LauncherEntry' bus interface: 
https://bazaar.launchpad.net/~cairo-dock-team/cairo-dock-plug-ins/plug-ins/view/head:/Dbus/data/cairo-dock-launcher-API-daemon.py

  [Original description]
  Using latest stable release (3.3.1). Just upgraded to Saucy Salamander in 
Ubuntu. When cairo dock is set to automatically run at boot up the options to 
shutdown/restart do not work from the top menu panel next to the clock. When 
run manually after boot the shutdown/restart works fine. The shutdown/restart 
options do work fine from cairo dock/terminal but just mess up the 
shutdown/restart from the top menu panel

To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo-dock-core/+bug/1242112/+subscriptions

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


[Desktop-packages] [Bug 994612] Re: gnome-screensaver-preferences missing

2014-02-14 Thread Dudytz
Confirmed in Ubuntu GNOME 13.10

** Tags added: 13.10

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

Title:
  gnome-screensaver-preferences missing

Status in “gnome-screensaver” package in Ubuntu:
  Confirmed

Bug description:
  There is no user-friendly way to configure gnome-screensaver. And
  there was one, I know.

  P.S.
  Please don't tell me that one has to use xscreensaver instead. It does not 
have:
  * DBus  support
  * user-switching support
  * keyboard layout indicator

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

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