[Desktop-packages] [Bug 1277343] Re: XMir starts with black screen ("std::exception::what: Invalid format for used output")
** Summary changed:
- xmir crashes on startup ("std::exception::what: Invalid format for used
output")
+ XMir starts with black screen ("std::exception::what: Invalid format for used
output")
** Summary changed:
- XMir starts with black screen ("std::exception::what: Invalid format for used
output")
+ XMir starts with black screen ("[xmir] Failed to set new display config: ...
std::exception::what: Invalid format for used output")
--
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/1277343
Title:
XMir starts with black screen ("[xmir] Failed to set new display
config: ... std::exception::what: Invalid format for used output")
Status in Mir:
Triaged
Status in XMir:
Triaged
Status in “mir” package in Ubuntu:
Triaged
Status in “xorg-server” package in Ubuntu:
Triaged
Bug description:
After the upgrade on Feb 5th my Trusty install failed to boot to
desktop. Using Recovery boot I can get a desktop, but the display
size/ratio is incorrect - 4:3 ratio instead of 1600x900.
Upgraded all packages on Feb 6th without curing the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 6 21:00:27 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device [104d:9035]
Subsystem: Sony Corporation Device [104d:9035]
InstallationDate: Installed on 2012-10-21 (473 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation VGN-FW235J
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic
root=UUID=24295ee0-c24c-4062-8898-f8e45805d805 ro recovery nomodeset
Renderer: Software
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR1100Y0:bd08/27/2009:svnSonyCorporation:pnVGN-FW235J:pvrC600SDMD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW235J
dmi.product.version: C600SDMD
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 6 20:17:52 2014
xserver.configfile: default
xserver.errors:
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
Screen 0 deleted because of no matching config section.
Screen 0 deleted because of no matching config section.
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.0-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277343] Re: XMir starts with black screen ("[xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output")
** Branch linked: lp:~vanvugt/mir/eliminate-configure-output
** Changed in: mir
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mir
Status: Triaged => In Progress
** Changed in: mir
Milestone: None => 0.1.6
--
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/1277343
Title:
XMir starts with black screen ("[xmir] Failed to set new display
config: ... std::exception::what: Invalid format for used output")
Status in Mir:
In Progress
Status in XMir:
Triaged
Status in “mir” package in Ubuntu:
Triaged
Status in “xorg-server” package in Ubuntu:
Triaged
Bug description:
After the upgrade on Feb 5th my Trusty install failed to boot to
desktop. Using Recovery boot I can get a desktop, but the display
size/ratio is incorrect - 4:3 ratio instead of 1600x900.
Upgraded all packages on Feb 6th without curing the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 6 21:00:27 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device [104d:9035]
Subsystem: Sony Corporation Device [104d:9035]
InstallationDate: Installed on 2012-10-21 (473 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation VGN-FW235J
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic
root=UUID=24295ee0-c24c-4062-8898-f8e45805d805 ro recovery nomodeset
Renderer: Software
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR1100Y0:bd08/27/2009:svnSonyCorporation:pnVGN-FW235J:pvrC600SDMD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW235J
dmi.product.version: C600SDMD
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 6 20:17:52 2014
xserver.configfile: default
xserver.errors:
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
Screen 0 deleted because of no matching config section.
Screen 0 deleted because of no matching config section.
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.0-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280956] Re: update-manager
*** This bug is a duplicate of bug 346386 *** https://bugs.launchpad.net/bugs/346386 Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your bug report it seems that you are experiencing bug 346386. This issue happens when you have tried to update your package information when you are a network that didn't return the right files. This issue can be cleaned up by using the following commands in a terminal: 1.) sudo rm /var/lib/apt/lists/* 2.) sudo apt-get update Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please reopen the bug task if it was incorrect.] ** This bug has been marked a duplicate of bug 346386 [MASTER] Update fails with invalid package files with "Encountered a section with no Package: header" ** Tags added: bot-comment -- 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/1280956 Title: update-manager Status in “software-center” package in Ubuntu: New Bug description: E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_precise- security_main_i18n_Translation-en, E:The package lists or status file could not be parsed or opened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1280956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280910] Re: package gnome-media 3.4.0-0ubuntu3.1 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/gnome/help/gnome-sound-recorder/el/figure
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: gnome-media (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-media (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1280910 Title: package gnome-media 3.4.0-0ubuntu3.1 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/gnome/help/gnome- sound-recorder/el/figures/grecord_window.png': Input/output error Status in “gnome-media” package in Ubuntu: Invalid Bug description: Luis Bueno ProblemType: Package DistroRelease: Ubuntu 12.10 Package: gnome-media 3.4.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-46.70-generic 3.5.7.27 Uname: Linux 3.5.0-46-generic i686 ApportVersion: 2.6.1-0ubuntu13 AptOrdering: gnome-media: Install gnome-media: Configure Architecture: i386 Date: Sun Feb 16 17:06:33 2014 DpkgTerminalLog: Preparing to replace gnome-media 3.4.0-0ubuntu3.1 (using .../gnome-media_3.4.0-0ubuntu4_i386.deb) ... Unpacking replacement gnome-media ... dpkg: error processing /var/cache/apt/archives/gnome-media_3.4.0-0ubuntu4_i386.deb (--unpack): failed to stat (dereference) existing symlink `/usr/share/gnome/help/gnome-sound-recorder/el/figures/grecord_window.png': Input/output error DuplicateSignature: package:gnome-media:3.4.0-0ubuntu3.1:failed to stat (dereference) existing symlink `/usr/share/gnome/help/gnome-sound-recorder/el/figures/grecord_window.png': Input/output error ErrorMessage: failed to stat (dereference) existing symlink `/usr/share/gnome/help/gnome-sound-recorder/el/figures/grecord_window.png': Input/output error InstallationDate: Installed on 2013-12-04 (74 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) MarkForUpload: True SourcePackage: gnome-media Title: package gnome-media 3.4.0-0ubuntu3.1 failed to install/upgrade: failed to stat (dereference) existing symlink `/usr/share/gnome/help/gnome-sound-recorder/el/figures/grecord_window.png': Input/output error UpgradeStatus: Upgraded to quantal on 2014-02-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-media/+bug/1280910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277343] Re: XMir starts with black screen ("[xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output")
OK, I just realized "eliminate-configure-output" doesn't fix the bug.
The branch itself has a bug which prevents this bug from manifesting
(which it still should).
** Branch unlinked: lp:~vanvugt/mir/eliminate-configure-output
--
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/1277343
Title:
XMir starts with black screen ("[xmir] Failed to set new display
config: ... std::exception::what: Invalid format for used output")
Status in Mir:
In Progress
Status in XMir:
Triaged
Status in “mir” package in Ubuntu:
Triaged
Status in “xorg-server” package in Ubuntu:
Triaged
Bug description:
After the upgrade on Feb 5th my Trusty install failed to boot to
desktop. Using Recovery boot I can get a desktop, but the display
size/ratio is incorrect - 4:3 ratio instead of 1600x900.
Upgraded all packages on Feb 6th without curing the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 6 21:00:27 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device [104d:9035]
Subsystem: Sony Corporation Device [104d:9035]
InstallationDate: Installed on 2012-10-21 (473 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation VGN-FW235J
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic
root=UUID=24295ee0-c24c-4062-8898-f8e45805d805 ro recovery nomodeset
Renderer: Software
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR1100Y0:bd08/27/2009:svnSonyCorporation:pnVGN-FW235J:pvrC600SDMD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW235J
dmi.product.version: C600SDMD
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 6 20:17:52 2014
xserver.configfile: default
xserver.errors:
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
Screen 0 deleted because of no matching config section.
Screen 0 deleted because of no matching config section.
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.0-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1272338] Re: Xorg memory leak on trusty
There are leaks all over the place (the one most often reported is in one of the KDE systray applets). This particular bug was particularly to the Intel driver. -- 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/1272338 Title: Xorg memory leak on trusty Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: After a few hours Xorg process was consuming a GB of RAM, after a day or so it was 2GB, now after 2 days it's over 4GB. I'd rather X wasn't eating all my RAM. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1710 root 20 0 5270636 4.300g 277872 S 14.2 27.6 229:09.97 Xorg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 24 13:36:48 2014 DistUpgraded: 2014-01-20 08:54:25,315 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2012-06-29 (573 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 4287CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=6088859e-4fc3-4ec8-903f-5b52cdc1d0eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-01-20 (4 days ago) dmi.bios.date: 12/05/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET67WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET67WW(1.37):bd12/05/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.51-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu11 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Wed Jan 22 12:54:42 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1272338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235991] Re: Can't “use system keyboard layout” in Saucy
Building on #David Cavaillini, here is the trick for those who want to type Japanese on a non-US keyboard: copy /usr/share/ibus-anthy/engine/default.xml to ~/.config/ibus-anthy/engines.xml change jp to fr -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy Status in “ibus” package in Ubuntu: Confirmed Bug description: In Saucy, ibus becomes more tightly integrated with the desktop. Configuring it via ibus-setup doesn't affect the instance run by ubuntu. And with the new system, there's no way to replicate the behaviour of the old “use system keyboard layout” option. When I use, for example, pinyin (Chinese) or anthy (Japanese), I want to type the letters in dvorak. I've been doing that for years, and now in Saucy it's impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1216973] Re: Bookmark button does not work in bookmark bar
This is a bug of the unity-menu-bar. See: http://askubuntu.com/questions/340432/can-i-get-the-bookmark-button-back-into-the-bookmarks-bar-in-firefox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1216973 Title: Bookmark button does not work in bookmark bar Status in “firefox” package in Ubuntu: New Bug description: Until Firefox 22, I used to have the bookmark menu button on the right side of my bookmarks bar. So I could add the regular used Bookmarks into the bookmark bar and select less often used ones from the menu button located in the bar. Since the update to Firefox 23 in Ubuntu, the bookmarks menu is not displayed anymore in the bookmark bar or when moved to the navigation bar. Although, I can see it in "edit mode" and it works when set into the add-on-bar. Firefox in Windows 7 does not show this behaviour, it still works as in Firefox 22. I did already reduce the numbers of bookmarks and folders in the bookmarks bar so the bookmarks menu fits into the bar. I also tries starting Firefox without any addons. The attached picture shows the bookmarks menu button in the bookmarks bar below the navigation bar with Add-Ons in edit mode (in german). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1216973/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281001] [NEW] personal file share GUI is misleading, doesn't say what packages are missing
Public bug reported: Personal file share GUI which comes pre-installed in Ubuntu is misleading. When the GUI is launched, it says certain packages are missing, but does not say which ones. This confuses people and does not help anyone who wants an easy way to share files. Either the complete package should be installed for the GUI or it should be completely removed. ** Affects: gnome-user-share (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Personal File Sharing" https://bugs.launchpad.net/bugs/1281001/+attachment/3983597/+files/Screenshot%20from%202014-02-17%2014%3A06%3A20.png ** Package changed: gnome-bluetooth (Ubuntu) => gnome-user-share (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1281001 Title: personal file share GUI is misleading, doesn't say what packages are missing Status in “gnome-user-share” package in Ubuntu: New Bug description: Personal file share GUI which comes pre-installed in Ubuntu is misleading. When the GUI is launched, it says certain packages are missing, but does not say which ones. This confuses people and does not help anyone who wants an easy way to share files. Either the complete package should be installed for the GUI or it should be completely removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1281001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281001] Re: personal file share GUI is misleading, doesn't say what packages are missing
** Summary changed: - personal file share option GUI is misleading, doesnt say what's missing + personal file share GUI is misleading, doesn't say what packages are missing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1281001 Title: personal file share GUI is misleading, doesn't say what packages are missing Status in “gnome-user-share” package in Ubuntu: New Bug description: Personal file share GUI which comes pre-installed in Ubuntu is misleading. When the GUI is launched, it says certain packages are missing, but does not say which ones. This confuses people and does not help anyone who wants an easy way to share files. Either the complete package should be installed for the GUI or it should be completely removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-share/+bug/1281001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278551] Re: No access to System Settings --> User Accounts
Could you also get a gdb backtrace of the hang? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1278551 Title: No access to System Settings --> User Accounts Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: When trying to access "User Accounts" (using any admin account) from "System Settings", system locks up for 30 seconds, greys out and on trying to exit System Settings window, dialogue box states: "The window "System Settings" is not responding." You then have to "Force Quit" to get out Ubuntu 13.10 Pentium(R) Dual-Core CPU E5800 @ 3.20GHz × 2 Intel® G41 Would be grateful if someone could tell me which log file to obtain any crash information from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274967] Re: No "paste" option available between different Nautilus Windows
Do you have write rights to that location? -- 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/1274967 Title: No "paste" option available between different Nautilus Windows Status in “nautilus” package in Ubuntu: New Bug description: *This is apparently #51043 all over again, but they suggested to file a new bug for Ubuntu 13.10 saucy salamander. So, here goes: I can 1. *copy* a file in one Nautilus (Files 3.8.2) window 2. Change to diffent folder in same window 3. Right click on empty space and choose *paste* What does not work 1. *copy* file in Nautilus_window_1 2. *paste* in Nautilus_window_2 The *paste* option is simply grayed out as unavailable. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Jan 31 16:50:44 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'788x550+65+321'" InstallationDate: Installed on 2013-09-10 (143 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-10-23 (100 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274967/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281009] [NEW] add out of the box file sharing support (samba) for Ubuntu with GUI
Public bug reported: File sharing between Ubuntu and Windows PCs is a bit of a struggle. One cannot get it up and running without searching online for a solution. Also there is always a bit of commandline involved in the process. It would be better, if the required GUI and the dependencies are installed by default for Ubuntu . Even if the dependencies are not involved, during setup of file share, the system should prompt for the required dependencies which can be installed from the Ubuntu Software Center. ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-user-share (Ubuntu) => samba (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1281009 Title: add out of the box file sharing support (samba) for Ubuntu with GUI Status in “samba” package in Ubuntu: New Bug description: File sharing between Ubuntu and Windows PCs is a bit of a struggle. One cannot get it up and running without searching online for a solution. Also there is always a bit of commandline involved in the process. It would be better, if the required GUI and the dependencies are installed by default for Ubuntu . Even if the dependencies are not involved, during setup of file share, the system should prompt for the required dependencies which can be installed from the Ubuntu Software Center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1281009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280794] Re: Can't change default "Open with" application
Thank you for your bug report. Is that working on a guest session? If you run "nautilus -q; nautilus" and try to do those change do you get any warning? It could be a wrong permission on some file or directory ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1280794 Title: Can't change default "Open with" application Status in “nautilus” package in Ubuntu: Incomplete Bug description: I am on Ubuntu 13.10 using nautilus 1:3.8.2-0ubuntu2.2. I am trying to change default application to open .avi files. I right- click an .avi file select "Properties", go to "Open With". There is a default application there (banshee) and recommended (VLC media player). I select VLC media player and click "Set as default" button, selection jumps back to banshee, "Set as default" button disabled and nothing else happens. Nautilus still opens .avi files with banshee. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 21:45:45 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1497x873+0+171'" InstallationDate: Installed on 2013-11-17 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-11-20T19:34:55.419627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280274] Re: The control panel includes a switch without description
It's obvious what "Bluetooth OFF/ON" does. But the other two examples demonstrate why I think Gnome designers have taken a wrong turn with this one-big-switch pattern. Often it isn't useful: Why would you want to turn Bluetooth Sharing *and* Personal File Sharing *and* Screen Sharing *and* Media Sharing *and* especially Remote Login off, all at once? Unless you're going into Flight Mode, which is presumably in a different panel and doesn't require you to toggle this switch anyway. And often it isn't understandable: What does it mean for "Search" as a whole to be "off"? Does that hide all search features throughout the OS, from the print dialog to the file manager? The label for the list below suggests (too late, layout-wise) that it's just the search field in the Activities Overview. But what is the point of turning that off anyway? Maybe that switch is useful, but it would need a label to explain why it is. Notwithstanding those problems, if Déjà Dup is used on non-Ubuntu Gnome systems, I understand that you might want to be consistent with those other panels. Meanwhile, though, I'm planning to put the search field in that spot of the window in System Settings for PC. So it's your choice which is more important: being consistent with Gnome on non-Ubuntu systems, or being consistent with the same panel in future Ubuntu versions. I respect your decision either way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1280274 Title: The control panel includes a switch without description Status in “deja-dup” package in Ubuntu: Incomplete Bug description: Using deja-dup in trusty: - open system-settings - click on the backup icon - look at the panel, there is a switch widget at the top right... but nothing that helps the user to understand what the control is doing Would it make sense to have a "Backup" label next to it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1280274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281019] [NEW] Brightness controls are not working nvidia-319 and nvidia-331
Public bug reported: Brightness controls are not working when the binary Nvidia drivers with version 319 or higher(for example 331). This running on my HP EliteBook 8560w with a Nvidia Quadro 2000M and a HP DreamColor2 screen. The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the brightness control window does show-up and changes, but the brightness of the screen itself does not. This is a bug which is a long standing one, and Nvidia seems to ignore it :( https://devtalk.nvidia.com/default/topic/539462/linux/-nvidia-319-12-brightness-controls-not-working-on-laptop-ubuntu-13-03-/2/ There is the bugreport at the official Nvidia forums. Also another bugreport here on Launchpad can be found here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1241745 Would be great if Nvidia did put some effort in this! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia appassure_vss .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Mon Feb 17 10:05:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: appassure-vss, 5.3.6, 3.11.0-15-generic, x86_64: installed nvidia-331, 331.38, 3.11.0-15-generic, x86_64: installed nvidia-331-uvm, 331.38, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=caf0bb2d-fbef-46ff-be64-0ec601243262 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 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.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt~saucy version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140210.5142d1ca-0ubuntu0sarvatt~saucy version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt xserver.bootTime: Mon Feb 17 10:03:57 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 nvidia-319 nvidia-331 saucy third-party-packages ubuntu xorg -- 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/1281019 Title: Brightness controls are not working nvidia-319 and nvidia-331 Status in “xorg” package in Ubuntu: New Bug description: Brightness controls are not working when the binary Nvidia drivers with version 319 or higher(for example 331). This running on my HP EliteBook 8560w with a Nvidia Quadro 2000M and a HP DreamColor2 screen. The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the
[Desktop-packages] [Bug 1255832] Re: [NVIDIA GT 640M][10de:0fd2] Unable to adjust the resolution with the proprietary driver
Is this really a bug in saucy then? if 12.04.4 works then saucy will work too.. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1255832 Title: [NVIDIA GT 640M][10de:0fd2] Unable to adjust the resolution with the proprietary driver Status in “nvidia-graphics-drivers” package in Ubuntu: Incomplete Bug description: CID: 201204-10924 Lenovo V480 The resolution cannot be adjusted with the NVIDIA proprietary driver installed. Steps: 1. Install 12.04.3 + update (3.8.0-33) + NVIDIA proprietary driver (nvidia-319-updates) 2. Boot to desktop 3. Try to adjust the display resolution with the "Display" applet 4. Try to adjust the display resolution with "xrandr" in a Terminal Expected result - Resolution could be adjusted. Actual result 1. When you try to adjust it via the "Display" applet, the following error message will pops-up: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.SettingsDaemon.XRANDR_2' on object at path /org/gnome/SettingsDaemon/XRANDR 2. When you're using xrandr to adjust it: xrandr --output LVDS-0 --mode 800x600 -r 60 --verbose Xorg will be killed and restarted, leads you to the Login screen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu17718 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf361 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa5002,00100202 HDA:80862806,80860101,0010' Controls : 29 Simple ctrls : 11 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Nov 27 20:49:56 2013 HibernationDevice: RESUME=UUID=0a4cd402-c938-4cc7-a55d-6230c539e25d InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 814TD01 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=6a396d09-0ad3-41a0-9d7d-18446b177e9d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.79.7 SourcePackage: linux-lts-raring StagingDrivers: keucr UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET73WW(1.16) dmi.board.asset.tag: Not Available dmi.board.name: 814TD01 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET73WW(1.16):bd04/10/2013:svnLENOVO:pn814TD01:pvrLenovoV480:rvnLENOVO:rn814TD01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814TD01 dmi.product.version: Lenovo V480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1255832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1241745] Re: 10de:0dfa [regression] Changing the screen brightness does not work anymore in 319.xx
@Christopher, Here is my new bugreport: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1241745 Title: 10de:0dfa [regression] Changing the screen brightness does not work anymore in 319.xx Status in “linux” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-319” package in Ubuntu: Triaged Bug description: Changing the screen brightness always used to work on my HP Elitebook 8560w -- both with the function keys and in the dialog "Brightness & Lock" in the system settings. The environment light sensor also used to work IIRC. Since the update to 13.10, this stopped working. Methods I have tried that didn't work for adapting the brightness are: * Adding GRUB_CMDLINE_LINUX="acpi_backlight=vendor" to /etc/default/grub * Adding GRUB_CMDLINE_LINUX=”acpi_osi="!Windows 2012" to /etc/default/grub Currently I am changing the brightness manually using xrandr --output LVDS-0 --brightness 0.9. However, AFAIK this does not really change the brightness, but only changes the contrast. WORKAROUND: Use nvidia-graphics-drivers-304. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 18 19:50:36 2013 DistUpgraded: 2013-10-17 17:20:47,580 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-319-updates, 319.60, 3.11.0-12-generic, x86_64: installed nvidia-319-updates, 319.60, 3.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] InstallationDate: Installed on 2013-01-06 (285 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Proprietary, Enabled, Not in use) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=53f83a14-cacc-48fd-bb4b-354d69eb7f0e ro quiet splash "acpi_osi=!Windows 2012" SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-17 (1 days ago) dmi.bios.date: 06/11/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.27 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.27:bd06/11/2012:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 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-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Oct 18 19:39:07 2013 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libgl
[Desktop-packages] [Bug 1278483] Re: Gnome language indicator displays wrong language
** Package changed: gnome-control-center (Ubuntu) => indicator-keyboard (Ubuntu) ** Changed in: indicator-keyboard (Ubuntu) Importance: Undecided => Low -- 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/1278483 Title: Gnome language indicator displays wrong language Status in “indicator-keyboard” package in Ubuntu: Incomplete Bug description: I have two languages in my system, English and Russian. Switching between them works fine, but keyboard indicator always shows wrong language. I can provide addtional debugging information if needed. It started to happen after upgrade to 13.10, on previous releases everything was ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1278483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268938] Re: Banding/dithering problem on Intel HD 4000
** Description changed: -- 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/1268938 Title: Banding/dithering problem on Intel HD 4000 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I'm running Ubuntu 13.04 on a Dell XPS 14 with integrated Intel HD 4000. The problem is that the coloring si really bad (in gradients, for example, bands of colors can be distinguished). It's like the color depth is not really 24bit. This issue is known, and Intel never fixed it in Windows drivers (https://communities.intel.com/thread/29420?start=0&tstart=0). I searched and the problem is probably due to HDMI different color range (16-235); when it's "scaled" in laptop's display standard "0-255" some colors are lost. I experienced the same issue in Ubuntu 13.10. The package version is 2:2.21.9-0ubuntu0~raring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1268938/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281019] Re: Brightness controls are not working nvidia-319 and nvidia-331
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1281019 Title: Brightness controls are not working nvidia-319 and nvidia-331 Status in “xorg” package in Ubuntu: Confirmed Bug description: Brightness controls are not working when the binary Nvidia drivers with version 319 or higher(for example 331). This running on my HP EliteBook 8560w with a Nvidia Quadro 2000M and a HP DreamColor2 screen. The Brightness keys (FN+F9 and FN+FN10) are doing 'something' in the right corner of the screen the brightness control window does show-up and changes, but the brightness of the screen itself does not. This is a bug which is a long standing one, and Nvidia seems to ignore it :( https://devtalk.nvidia.com/default/topic/539462/linux/-nvidia-319-12-brightness-controls-not-working-on-laptop-ubuntu-13-03-/2/ There is the bugreport at the official Nvidia forums. Also another bugreport here on Launchpad can be found here: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1241745 Would be great if Nvidia did put some effort in this! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia appassure_vss .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Mon Feb 17 10:05:44 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: appassure-vss, 5.3.6, 3.11.0-15-generic, x86_64: installed nvidia-331, 331.38, 3.11.0-15-generic, x86_64: installed nvidia-331-uvm, 331.38, 3.11.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=caf0bb2d-fbef-46ff-be64-0ec601243262 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.42 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.3D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.42:bd07/15/2013:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.3D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140215.1020d893-0ubuntu0sarvatt~saucy version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 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.3.99+git20140206.8de6f7b2-0ubuntu0sarvatt~saucy version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140210.5142d1ca-0ubuntu0sarvatt~saucy version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9+git20130730.300c5a32-0ubuntu0sarvatt xserver.bootTime: Mon Feb 17 10:03:57 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1281019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages Mor
[Desktop-packages] [Bug 1277343] Re: XMir starts with black screen ("[xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output")
** Branch linked: lp:~vanvugt/mir/fix-1277343
--
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/1277343
Title:
XMir starts with black screen ("[xmir] Failed to set new display
config: ... std::exception::what: Invalid format for used output")
Status in Mir:
In Progress
Status in XMir:
Triaged
Status in “mir” package in Ubuntu:
Triaged
Status in “xorg-server” package in Ubuntu:
Triaged
Bug description:
After the upgrade on Feb 5th my Trusty install failed to boot to
desktop. Using Recovery boot I can get a desktop, but the display
size/ratio is incorrect - 4:3 ratio instead of 1600x900.
Upgraded all packages on Feb 6th without curing the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 6 21:00:27 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device [104d:9035]
Subsystem: Sony Corporation Device [104d:9035]
InstallationDate: Installed on 2012-10-21 (473 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation VGN-FW235J
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic
root=UUID=24295ee0-c24c-4062-8898-f8e45805d805 ro recovery nomodeset
Renderer: Software
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR1100Y0:bd08/27/2009:svnSonyCorporation:pnVGN-FW235J:pvrC600SDMD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW235J
dmi.product.version: C600SDMD
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 6 20:17:52 2014
xserver.configfile: default
xserver.errors:
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
Screen 0 deleted because of no matching config section.
Screen 0 deleted because of no matching config section.
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.0-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280659] Re: 1002:983d [HP Pavilion TouchSmart 11-e010er Notebook PC] xserver crashes after suspend with radeonsi and glamor, poor 2d perfomance
I was not able to get Xorg working in Saucy. -- 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/1280659 Title: 1002:983d [HP Pavilion TouchSmart 11-e010er Notebook PC] xserver crashes after suspend with radeonsi and glamor, poor 2d perfomance Status in “xorg” package in Ubuntu: Incomplete Bug description: Glamor egl causes Xorg segfaults on resume from suspend and poor 2d performance. WORKAROUND: With "EXA" enabled instead of "glamor" everything is fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Feb 15 21:54:27 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Temash [Radeon HD 8250/8280G] [1002:983d] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2178] InstallationDate: Installed on 2014-01-29 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140111) LightdmGreeterLog: Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession LightdmGreeterLogOld: Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: Hewlett-Packard HP Pavilion TS 11 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic.efi.signed root=UUID=8dacae3b-19c4-42e8-8a7f-5d4ea76a0f47 ro quiet splash radeon.dpm=1 radeon.audio=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 2178 dmi.board.vendor: Hewlett-Packard dmi.board.version: 33.2F dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd12/06/2013:svnHewlett-Packard:pnHPPavilionTS11NotebookPC:pvr08901030590320100:rvnHewlett-Packard:rn2178:rvr33.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 11 Notebook PC dmi.product.version: 08901030590320100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 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-1ubuntu2 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: Sat Feb 15 21:53:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1280659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280155] Re: test for /usr/bin/xrandr when upgrading from lts
** Changed in: x11-xserver-utils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1280155 Title: test for /usr/bin/xrandr when upgrading from lts Status in Auto Upgrade Testing of Ubuntu and Flavors: Fix Released Status in “x11-xserver-utils” package in Ubuntu: Fix Released Status in “xorg-lts-transitional” package in Ubuntu: Fix Released Bug description: This is similar to the existing test for /usr/lib/protocol.txt /usr/bin/xrandr.orig should no longer exist after upgrade, while /usr/bin/xrandr should. To manage notifications about this bug go to: https://bugs.launchpad.net/auto-upgrade-testing/+bug/1280155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277343] Re: XMir starts with black screen ("[xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output")
** Changed in: xmir
Status: Triaged => Invalid
** Changed in: xorg-server (Ubuntu)
Status: Triaged => Invalid
--
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/1277343
Title:
XMir starts with black screen ("[xmir] Failed to set new display
config: ... std::exception::what: Invalid format for used output")
Status in Mir:
In Progress
Status in XMir:
Invalid
Status in “mir” package in Ubuntu:
Triaged
Status in “xorg-server” package in Ubuntu:
Invalid
Bug description:
After the upgrade on Feb 5th my Trusty install failed to boot to
desktop. Using Recovery boot I can get a desktop, but the display
size/ratio is incorrect - 4:3 ratio instead of 1600x900.
Upgraded all packages on Feb 6th without curing the problem.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
Uname: Linux 3.13.0-7-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 6 21:00:27 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Sony Corporation Device [104d:9035]
Subsystem: Sony Corporation Device [104d:9035]
InstallationDate: Installed on 2012-10-21 (473 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Sony Corporation VGN-FW235J
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic
root=UUID=24295ee0-c24c-4062-8898-f8e45805d805 ro recovery nomodeset
Renderer: Software
SourcePackage: xserver-xorg-video-intel
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/27/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R1100Y0
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrR1100Y0:bd08/27/2009:svnSonyCorporation:pnVGN-FW235J:pvrC600SDMD:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FW235J
dmi.product.version: C600SDMD
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 6 20:17:52 2014
xserver.configfile: default
xserver.errors:
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
Screen 0 deleted because of no matching config section.
Screen 0 deleted because of no matching config section.
AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.0-1ubuntu3
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1271710] Re: doesn't list compiz/unity keybindings
** Branch linked: lp:ubuntu/trusty-proposed/compiz -- 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/1271710 Title: doesn't list compiz/unity keybindings Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: Invalid Bug description: The unity-control-center keybinding dialog doesn't list things like the HUD control (seems like other sections are missing as well). Could it be that it's not looking in the right directory for those? (or do we need to migrate things shipping a custom .xml to install those in a new location?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1271710/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1191853] Re: gtk-window-decorator crashed with SIGSEGV in wnck_window_get_actions()
** Branch linked: lp:ubuntu/trusty-proposed/compiz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck in Ubuntu. https://bugs.launchpad.net/bugs/1191853 Title: gtk-window-decorator crashed with SIGSEGV in wnck_window_get_actions() Status in Compiz: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Status in “libwnck” package in Ubuntu: Fix Released Bug description: gtk-window-decorator crashes each time I close a firefox window in which I had a google hangout. TEST CASE: (Note: There is probably a shorter or more obvious test case, but that's how I reproduce it systematically on several systems) 1. Open a new tab in Firefox and start a Google hangout 2. Detach the tab to new window (right-click on the tab, and select "Move to new window" in the contextual menu) 3. Right-click to title bar of the newly open window and select "Always on top" and "Always on visible workspace" in the contextual menu. 4. Chat with your friends for a bit 5. Close the window ACTUAL RESULT This crash and windows decorations are gone. To recover the decoration, open a terminal and run "gtk-window-decorator &" then close the terminal with CTRL+D (not the close button of the terminal, that'd kill the decoration too) EXPECTED RESULT The window closes without crash ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: compiz-gnome 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-5.12-generic 3.9.5 Uname: Linux 3.9.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Mon Jun 17 17:43:36 2013 DistUpgraded: 2012-02-01 00:15:24,616 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.10, 3.9.0-2-generic, x86_64: installed virtualbox, 4.2.10, 3.9.0-3-generic, x86_64: installed virtualbox, 4.2.10, 3.9.0-4-generic, x86_64: installed virtualbox, 4.2.10, 3.9.0-5-generic, x86_64: installed virtualbox, 4.2.10, 3.9.0-6-generic, x86_64: installed ExecutablePath: /usr/bin/gtk-window-decorator GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device [174b:1482] MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H MarkForUpload: True ProcCmdline: /usr/bin/gtk-window-decorator ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.9.0-5-generic root=UUID=cf89ba34-108b-404d-9804-32d54a1df2ea ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7fd3396dbe56 : cmp %rax,(%rdx) PC (0x7fd3396dbe56) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: compiz StacktraceTop: wnck_window_get_actions () from /usr/lib/libwnck-1.so.22 ?? () from /usr/lib/libwnck-1.so.22 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gtk-window-decorator crashed with SIGSEGV in wnck_window_get_actions() UpgradeStatus: Upgraded to saucy on 2012-01-31 (502 days ago) UserGroups: adm admin cdrom dialout kvm libvirtd lpadmin plugdev sambashare sbuild vboxusers dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H 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.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology 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-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.3-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.3-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu12 version.xserver-xorg-input-evdev: xserver-xorg-input
[Desktop-packages] [Bug 1183852] Re: On Firefox facebook keeps opening sessions and asking if I want, "Ubuntu would like to post to your friends on your behalf."
*** This bug is a duplicate of bug 1180297 *** https://bugs.launchpad.net/bugs/1180297 ** Branch linked: lp:ubuntu/trusty-proposed/compiz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1183852 Title: On Firefox facebook keeps opening sessions and asking if I want, "Ubuntu would like to post to your friends on your behalf." Status in “compiz” package in Ubuntu: Fix Released Status in “signon” package in Ubuntu: New Bug description: Every few minutes firefox opens and new session for facebook with the Ubuntulogo that says, "Ubuntu would like to post to your friends on your behalf." Ubuntu 13.04 Even if Firefos is not open, it opens it and does the above. Please tell me how to make this stop. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 21.0+build2-0ubuntu0.13.04.2 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic i686 AddonCompatCheckDisabled: False ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kl 1965 F pulseaudio BuildID: 20130512193902 Channel: Unavailable Date: Fri May 24 10:45:35 2013 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-02 (51 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) IpRoute: default via 192.168.1.1 dev wlan0 proto static 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.12 metric 9 MarkForUpload: True PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=21.0/20130512193902 (In use) RelatedPackageVersions: totem-mozilla 3.6.3-0ubuntu6 rhythmbox-mozilla 2.98-0ubuntu5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to raring on 2013-05-03 (20 days ago) dmi.bios.date: 04/11/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd04/11/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1183852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 997370] Re: Totem does not use the va-api gstreamer backend
Thanks Ekimia. It is certainly frustrating not being able to use Totem with VA-API or VDPAU. According to Julius in comment #9, MPEG4 part2 (xvid) files will not decode with gst-launch and VA-API. This may be due to the support not landing until after his comment, or because it is not supported by his hardware. Julius - what hardware do you have and does it work now? -- 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/997370 Title: Totem does not use the va-api gstreamer backend Status in Totem Movie Player: Confirmed Status in “gstreamer-vaapi” package in Ubuntu: Confirmed Status in “totem” package in Ubuntu: Confirmed Bug description: installing gstreamer -vaapi from ubuntu repos breaks thumbnail generation in nautilus furthermore acceleration does not work in totem - cpu usage is as high as with software rendering. mplayer-vaapi works perfectly on the same system. gst-launch-0.10 -v filesrc location=~/test.mkv ! matroskademux ! vaapidecode ! vaapisink makes it possible to use vaapi via commandline i did not find a way to use vaapi for mpeg4 part 2 video streams. and i wasnt able to find proper values for gstreamer-properties that fix thumbnails and acceleration in totem. id like to share debug information. just tell me what you need. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/997370/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 890747] Re: Keyboard shortcut - Ctrl Alt Del doesn't do what most people typing it would expect
** Branch linked: lp:ubuntu/trusty-proposed/compiz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/890747 Title: Keyboard shortcut - Ctrl Alt Del doesn't do what most people typing it would expect Status in Ayatana Design: Fix Committed Status in Compiz: In Progress Status in Compiz 0.9.10 series: Fix Committed Status in “compiz” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Won't Fix Bug description: Ubuntu 11.10 1. Type Ctrl+Alt+Del. What happens: In Unity, a mutant version of the Log Out dialog appears. What should happen: The nearest equivalent to the Windows Task Manager appears. Currently, that is the "Processes" tab of System Monitor. (Implementing this probably would invalidate bug 485740.) See also bug 950882. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/890747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 850229] Re: Unread email count in thunderbird shown wrongly in messaging menu and launcher icon
Obviously not fixed. This should be changed to Triaged again. A workaround as mentioned https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/848774 , #5 comment: Open : "Tools -> Options -> Advanced -> General -> Config Editor (button)" Search for `extensions.messagingmenu.inboxOnly` set it to true and that's it. -- 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/850229 Title: Unread email count in thunderbird shown wrongly in messaging menu and launcher icon Status in Messaging Menu Thunderbird Extension: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “thunderbird” source package in Oneiric: Triaged Bug description: The number of unread emails is shown incorrectly in the messaging menu and unity launcher icon of thunderbird though thunderbird application shows the correct count. See the attached screenshot for the illustration. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 7.0~b2+build2+nobinonly1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guruprasad 1650 F pulseaudio BuildID: 20110906005012 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf840 irq 47' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,103c30cc,0013 HDA:10573055,10573055,00100700' Controls : 21 Simple ctrls : 13 Channel: default Date: Wed Sep 14 23:40:58 2011 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901) IpRoute: default via 192.168.1.1 dev wlan0 proto static 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.8 Profiles: Profile0 (Default) - LastVersion=7.0/20110906005012 (Running) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.59 dmi.board.name: 30CB dmi.board.vendor: Quanta dmi.board.version: 79.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.59:bd11/25/2008:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30CB:rvr79.2E:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv9700 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/messagingmenu-extension/+bug/850229/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278551] Re: No access to System Settings --> User Accounts
Thanks all. Now I'm armed with what to do I'll get this out to you ASAP. Just checked the bug again and its still valid so just waiting apport info to come through Regards Ian -- 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/1278551 Title: No access to System Settings --> User Accounts Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: When trying to access "User Accounts" (using any admin account) from "System Settings", system locks up for 30 seconds, greys out and on trying to exit System Settings window, dialogue box states: "The window "System Settings" is not responding." You then have to "Force Quit" to get out Ubuntu 13.10 Pentium(R) Dual-Core CPU E5800 @ 3.20GHz × 2 Intel® G41 Would be grateful if someone could tell me which log file to obtain any crash information from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1255832] Re: [NVIDIA GT 640M][10de:0fd2] Unable to adjust the resolution with the proprietary driver
I think maybe we can track this by nomiate Saucy? (mark it as fix-released) Not sure if this will be fix in raring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1255832 Title: [NVIDIA GT 640M][10de:0fd2] Unable to adjust the resolution with the proprietary driver Status in “nvidia-graphics-drivers” package in Ubuntu: Incomplete Bug description: CID: 201204-10924 Lenovo V480 The resolution cannot be adjusted with the NVIDIA proprietary driver installed. Steps: 1. Install 12.04.3 + update (3.8.0-33) + NVIDIA proprietary driver (nvidia-319-updates) 2. Boot to desktop 3. Try to adjust the display resolution with the "Display" applet 4. Try to adjust the display resolution with "xrandr" in a Terminal Expected result - Resolution could be adjusted. Actual result 1. When you try to adjust it via the "Display" applet, the following error message will pops-up: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.gnome.SettingsDaemon.XRANDR_2' on object at path /org/gnome/SettingsDaemon/XRANDR 2. When you're using xrandr to adjust it: xrandr --output LVDS-0 --mode 800x600 -r 60 --verbose Xorg will be killed and restarted, leads you to the Login screen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48~precise1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu17718 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf361 irq 47' Mixer name : 'Intel PantherPoint HDMI' Components : 'HDA:10ec0269,17aa5002,00100202 HDA:80862806,80860101,0010' Controls : 29 Simple ctrls : 11 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Wed Nov 27 20:49:56 2013 HibernationDevice: RESUME=UUID=0a4cd402-c938-4cc7-a55d-6230c539e25d InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: LENOVO 814TD01 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=6a396d09-0ad3-41a0-9d7d-18446b177e9d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.79.7 SourcePackage: linux-lts-raring StagingDrivers: keucr UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET73WW(1.16) dmi.board.asset.tag: Not Available dmi.board.name: 814TD01 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET73WW(1.16):bd04/10/2013:svnLENOVO:pn814TD01:pvrLenovoV480:rvnLENOVO:rn814TD01:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 814TD01 dmi.product.version: Lenovo V480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1255832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281053] [NEW] Unity application panel does not appear with mirrored screens on Intel graphics
Public bug reported: My setup I'm using Ubuntu 13.10 on a HP TM2 with hybrid graphics (vga- switcheroo): - integrated card: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) - discrete card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] (prog-if 00 [VGA controller]) Problem === I need to work using a mirrored screen setup, with an external screen connected to VGA (resolution: 1024x768). When using the integrated intel card the application/search panel does not appear when I click on the launcher icon or press the keyboard shortcut: there is just a slight shadow on the top left corner (see attached screenshot). However, if I switch to the discrete card (AMD/ATI) I have no problems at all (panel shows up in mirrored mode). In non-mirrored mode the panel shows up using both cards and works correctly on both screens. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Mon Feb 17 11:22:54 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1486] Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TouchSmart tm2-2050er discrete GPU (Mobility Radeon HD 5450) [103c:1486] InstallationDate: Installed on 2014-02-12 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=6dc4e5fd-db39-4985-8a85-8db30961e8c5 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2011 dmi.bios.vendor: Insyde dmi.bios.version: F.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1486 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.20 dmi.chassis.asset.tag: CNU03739VM dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr058A21242A1120100:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP TouchSmart tm2 Notebook PC dmi.product.version: 058A21242A1120100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 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-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Feb 17 11:20:41 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2~saucy1 xserver.video_driver: radeon ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy third-party-packages ubuntu ** Attachment added: "Application panel not showing up" https://bugs.launchpad.net/bugs/1281053/+attachment/3983776/+files/Schermata%20del%202014-02-17%2011%3A19%3A30.png -- 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/1281053 Title: Unity application panel does not appear with mirrored screens on Intel graphics Status in “unity” package in Ubuntu: New Bug description: My setup I'm using Ubuntu 13.10 on a HP TM2 with hybrid graphics (vga- switcheroo): - integrated card: 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) - discrete card: 01:00.0 VGA compatible co
[Desktop-packages] [Bug 1278551] Re: No access to System Settings --> User Accounts
While the apport info might be useful having the gdb backtrace is the most important part to debug the issue. Do you know how to get those? (https://wiki.ubuntu.com/Backtrace) -- 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/1278551 Title: No access to System Settings --> User Accounts Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: When trying to access "User Accounts" (using any admin account) from "System Settings", system locks up for 30 seconds, greys out and on trying to exit System Settings window, dialogue box states: "The window "System Settings" is not responding." You then have to "Force Quit" to get out Ubuntu 13.10 Pentium(R) Dual-Core CPU E5800 @ 3.20GHz × 2 Intel® G41 Would be grateful if someone could tell me which log file to obtain any crash information from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1278551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261733] Re: YouTube Videos does not work on Chromium BUT same video works on Firefox on the same system and machine
@Chad Miller Hi, kindly have a look at this thread if you haven't yet and also see this comment please: http://ubuntuforums.org/showthread.php?t=2194128&page=3&p=12931084#post12931084 Kindly change the status of this report so that it won't be expired. Thank you! -- 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/1261733 Title: YouTube Videos does not work on Chromium BUT same video works on Firefox on the same system and machine Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: More details here: http://ubuntuforums.org/showthread.php?t=2194128 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.12.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Dec 17 16:29:34 2013 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share DetectedPlugins: (no entry found in the Preferences file) Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1261733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281058] [NEW] The system shutdowns when multiple accounts are open
Public bug reported: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 11:49:48 2014 InstallationDate: Installed on 2013-06-17 (244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1281058 Title: The system shutdowns when multiple accounts are open Status in “unity” package in Ubuntu: New Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 11:49:48 2014 InstallationDate: Installed on 2013-06-17 (244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280110] Re: Compilation warning in bamf-application.c because of implicit cast of try_create_local_desktop_data return value
This bug was fixed in the package bamf - 0.5.1+14.04.20140214.1-0ubuntu1 --- bamf (0.5.1+14.04.20140214.1-0ubuntu1) trusty; urgency=low [ Michel Alexandre Salim ] * [Merge] Fix return value of try_create_local_desktop_data. (LP: #1280110) [ CI bot ] * Release trunk to Ubuntu [ Marco Trevisan (Treviño) ] * BamfLegacyScreen: When in Unity monitor for compiz ClientMessage's to show action menu If we get a _COMPIZ_TOOLKIT_ACTION client message with the internal value _COMPIZ_TOOLKIT_ACTION_WINDOW_MENU, then we are requested by compiz to show the window action menu, and thus let's ask the proper BamfLegacyWindow to do that, thanks to libwnck. (LP: #1280042) -- Ubuntu daily releaseFri, 14 Feb 2014 22:58:48 + ** Changed in: bamf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1280110 Title: Compilation warning in bamf-application.c because of implicit cast of try_create_local_desktop_data return value Status in BAMF Application Matching Framework: Fix Committed Status in “bamf” package in Ubuntu: Fix Released Bug description: try_create_local_desktop_data contains an invocation of the g_return_val_if_fail macro, which in case of failure returns NULL instead of a gboolean value (the return type signature of the try_... function). This is wrong on two different counts: - implicit cast warning, which when warnings are treated as errors cause compilation failure - if NULL is explicitly cast to gboolean, it yields another error as a pointer has differing size as a gboolean (even though in this case it's all-zero) The correct fix is to have g_return_val_if_fail return FALSE instead of NULL. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1280110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280042] Re: Window action menu is not visible with new decorations
This bug was fixed in the package bamf - 0.5.1+14.04.20140214.1-0ubuntu1 --- bamf (0.5.1+14.04.20140214.1-0ubuntu1) trusty; urgency=low [ Michel Alexandre Salim ] * [Merge] Fix return value of try_create_local_desktop_data. (LP: #1280110) [ CI bot ] * Release trunk to Ubuntu [ Marco Trevisan (Treviño) ] * BamfLegacyScreen: When in Unity monitor for compiz ClientMessage's to show action menu If we get a _COMPIZ_TOOLKIT_ACTION client message with the internal value _COMPIZ_TOOLKIT_ACTION_WINDOW_MENU, then we are requested by compiz to show the window action menu, and thus let's ask the proper BamfLegacyWindow to do that, thanks to libwnck. (LP: #1280042) -- Ubuntu daily releaseFri, 14 Feb 2014 22:58:48 + ** Changed in: bamf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1280042 Title: Window action menu is not visible with new decorations Status in BAMF Application Matching Framework: Fix Committed Status in Unity: In Progress Status in “bamf” package in Ubuntu: Fix Released Bug description: Right clicking over the decorations of a window, or pressing Alt+Space should show the windows action menu. This is not working anymore with new unity decorations To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1280042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1267625] Re: User accounts automatic login button is not accessible in Tab order when using Gnome Orca
I'm not sure to understand the issue exactly there. Luke, could you have a look if there is an actual bug we need to fix in that ui? ** Package changed: gnome-control-center (Ubuntu) => unity-control- center (Ubuntu) ** Changed in: unity-control-center (Ubuntu) Status: Incomplete => New ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Luke Yelavich (themuso) -- 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/1267625 Title: User accounts automatic login button is not accessible in Tab order when using Gnome Orca Status in “unity-control-center” package in Ubuntu: New Bug description: After selecting your username in User accounts the automatic login button is not accessible when tabbing through available options using Gnome Orca, the expected behaviour once your account has been selected is to be able to select the button for automatic login. Currently is to edit configuration files. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu50 ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6 Uname: Linux 3.12.0-8-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 10 09:18:42 2014 InstallationDate: Installed on 2013-11-14 (56 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131113) SourcePackage: gnome-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/1267625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1266763] Re: Race condition between status and backup
Bug created to SRU trusty's fix to Precise & Saucy https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1281066 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1266763 Title: Race condition between status and backup Status in Duplicity - Bandwidth Efficient Encrypted Backup: Fix Released Status in “duplicity” package in Ubuntu: In Progress Status in “duplicity” source package in Precise: In Progress Status in “duplicity” source package in Quantal: In Progress Status in “duplicity” source package in Raring: In Progress Status in “duplicity” source package in Saucy: In Progress Status in “duplicity” source package in Trusty: In Progress Bug description: SRU justification : Race condition exist when two instances of duplicity run in the same cache directory (.cache/duplicity) Impact : Potential corruption of the local cache Fix : Add a lockfile in the local cache & prevent execution of a second instance in the case of the presence of the lockfile Test Case : 1) Run one instance of duplicity : $ sudo mkdir /tmp/backup $ sudo duplicity --exclude=/proc --exclude=/sys --exclude=/tmp / file:///tmp/backup While this command is running execute the following in a separate console : $ sudo duplicity collection-status file:///tmp/backup With the new locking mechanism you will see the following : $ sudo duplicity collection-status file:///tmp/backup Another instance is already running with this archive directory If you are sure that this is the only instance running you may delete the following lockfile and run the command again : /home/ubuntu/.cache/duplicity/3fe07cc0f71075f95f411fb55ec60120/lockfile.lock Regression : In the case of spurrious interruption of duplicity, the lockfile will remain in .cache/duplicity which can prevent future use of duplicity. The cache directory will have to be cleaned as outlined in the error message Original description of the problem : When runnining "duply X status" while running "duply X backup" (sorry, I don't know which duplicity commands are created by duply) due to a race-condition the code of 'sync_archive' might happend to append newly created meta-data files to 'local_spurious' and subsequently delete them. This delete seems to have been the reason that triggered bug 1216921. The race condition is that the backup command constantly creates meta- data files while the status command queries the list of local and remote files independently over a larger time span. This means that a local file might already been remote but the status command did not see it a few seconds ago. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1266763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281066] [NEW] Needs to backport trusty's fix to handle duplicity's lockfile
Public bug reported: SRU justification : Duplicity implements a new lockfile that impacts deja-dup functionality. A fix to remove the lockfile is already commited upstream and in Trusty. The SRU is to make the fix available before duplicity's SRU is completed Impact : Without this SRU, duplicity's SRU for LP: #1266763 cannot be completed or it may result in regression issues Fix : Remove the lockfile since concurrency is handled in DBUS in deja-dup Test Case : TBD Regression : None expected as it remove a file that is only present with newer versions of duplicity Description of the problem : See justification ** Affects: deja-dup (Ubuntu) Importance: Medium Status: Confirmed ** Changed in: deja-dup (Ubuntu) Status: New => Confirmed ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1281066 Title: Needs to backport trusty's fix to handle duplicity's lockfile Status in “deja-dup” package in Ubuntu: Confirmed Bug description: SRU justification : Duplicity implements a new lockfile that impacts deja-dup functionality. A fix to remove the lockfile is already commited upstream and in Trusty. The SRU is to make the fix available before duplicity's SRU is completed Impact : Without this SRU, duplicity's SRU for LP: #1266763 cannot be completed or it may result in regression issues Fix : Remove the lockfile since concurrency is handled in DBUS in deja-dup Test Case : TBD Regression : None expected as it remove a file that is only present with newer versions of duplicity Description of the problem : See justification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1281066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1279918] Re: package xserver-common-lts-saucy 3:4 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-lts-transitional (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1279918 Title: package xserver-common-lts-saucy 3:4 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück Status in “xorg-lts-transitional” package in Ubuntu: Confirmed Bug description: I tryed tu upgrage from Ubuntu 12.04 to Ubuntu 12.10. During the process several Error messages occured. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: xserver-common-lts-saucy 3:4 ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 Date: Thu Feb 13 18:20:21 2014 DuplicateSignature: package:xserver-common-lts-saucy:3:4:ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück ErrorMessage: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück InstallationDate: Installed on 2013-02-10 (368 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) PackageArchitecture: all SourcePackage: xorg-lts-transitional Title: package xserver-common-lts-saucy 3:4 failed to install/upgrade: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to trusty on 2014-02-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1279918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1279192] Re: package libgl1-mesa-dri 9.2.1-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl
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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1279192 Title: package libgl1-mesa-dri 9.2.1-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64. Is causing problems installing FGLRX driver as well as long delay between log in and desktop display Status in “mesa” package in Ubuntu: Confirmed Bug description: Is causing problems installing FGLRX driver, as well as long delay between log in and desktop display. I also get a CLI login prompt that disappears after 20 seconds or so then a graphical login prompt appears I'm assuming this is related ProblemType: Package DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-dri 9.2.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl fglrx .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Tue Feb 11 06:33:09 2014 DistUpgraded: 2014-02-08 20:45:06,400 DEBUG failed to SystemUnLock() (E:Not locked) DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-15-generic, x86_64: installed fglrx, 13.350, 3.11.0-15-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-15-generic, x86_64: installed virtualbox, 4.2.16, 3.5.0-45-generic, x86_64: installed DpkgTerminalLog: Preparing to replace libgl1-mesa-dri:amd64 9.2.1-1ubuntu3 (using .../libgl1-mesa-dri_9.2.1-1ubuntu3_amd64.deb) ... Unpacking replacement libgl1-mesa-dri:amd64 ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-dri_9.2.1-1ubuntu3_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 DuplicateSignature: package:libgl1-mesa-dri:9.2.1-1ubuntu3:trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9649] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:169b] InstallationDate: Installed on 2012-10-25 (474 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=124123b2-547f-45fa-bc5a-f90c094e444f ro quiet splash vt.handoff=7 SourcePackage: mesa Title: package libgl1-mesa-dri 9.2.1-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: Upgraded to saucy on 2014-02-09 (2 days ago) dmi.bios.date: 12/25/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 169B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 18.1A dmi.chassis.asset.tag: 5CG2031372 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.49:bd12/25/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901320461620100:rvnHewlett-Packard:rn169B:rvrKBCVersion18.1A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 06901320461620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 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-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Feb 11 07:38:28 2014 xserver.conf
[Desktop-packages] [Bug 1279080] Re: package libgnome2-common 2.32.1-2ubuntu3 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgnome (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnome in Ubuntu. https://bugs.launchpad.net/bugs/1279080 Title: package libgnome2-common 2.32.1-2ubuntu3 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in “libgnome” package in Ubuntu: Confirmed Bug description: The package is called "libgnome2-common" in Ubuntu 12.10 ProblemType: Package DistroRelease: Ubuntu 12.10 Package: libgnome2-common 2.32.1-2ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu13 Architecture: i386 Date: Sat Feb 8 22:22:20 2014 DuplicateSignature: package:libgnome2-common:2.32.1-2ubuntu3:Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2014-02-04 (7 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release i386(20121018) MarkForUpload: True PackageArchitecture: all SourcePackage: libgnome Title: package libgnome2-common 2.32.1-2ubuntu3 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sound.events.gnome.2.soundlist: [deleted] modified.conffile..etc.sound.events.gtk.events.2.soundlist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnome/+bug/1279080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1279380] Re: [14.04] [Gnome-Settings-Daemon] unable to save default audio output device
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1279380 Title: [14.04] [Gnome-Settings-Daemon] unable to save default audio output device Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: When more than one audio output source are available, gnome-settings usually picks the 1st one on the list. There is no way to save any alternate choice. For example I have: HDMI/DisplayPort2 Built-in Audio Digital Output (S/PDIF) Built-in Audio Analog Output Built-in Audio. The default output each time the system boots is set to HDMI/DisplayPort2 Built-in Audio and I have to manually change it to Analog Output Built-in Audio to which my PC speakers are connected. There is no "save this as default" option on this screen. So, I have do this each time I boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon 3.8.6.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 12 09:18:30 2014 InstallationDate: Installed on 2013-04-10 (308 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-02-08 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1279380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278623] Re: package flashplugin-installer 11.2.202.336ubuntu0.13.10.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurüc
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: flashplugin-nonfree (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1278623 Title: package flashplugin-installer 11.2.202.336ubuntu0.13.10.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in “flashplugin-nonfree” package in Ubuntu: Confirmed Bug description: Happened on background update ProblemType: Package DistroRelease: Ubuntu 13.10 Package: flashplugin-installer 11.2.202.336ubuntu0.13.10.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Feb 6 20:39:10 2014 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2012-09-17 (511 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905) MarkForUpload: True SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 11.2.202.336ubuntu0.13.10.1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to saucy on 2014-01-13 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1278623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276960] Re: Ubuntu 13.10 upgrade broke click-and-drag
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1276960 Title: Ubuntu 13.10 upgrade broke click-and-drag Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10, click-and-drag no longer works correctly (system-wide). Steps to reproduce: * Open a window where you can highlight text * Move the cursor to the start of the text you want to select, using the touchpad * Press the right-click button and immediately start dragging using the touchpad * Eventually let go of the button and stop dragging On Ubuntu 13.04 this worked fine. After upgrading to 13.10, however, click events are only registered with a large delay. So doing the steps above actually causes the following event sequence. * The mouse moves along the drag path * The button-down event registers long way into the drag (or maybe at the end of the drag path) * The remainder of the mouse motion events then happen * The button-up event triggers (I verified the event order using `xinput test`) Workaround is to wait (maybe about a second) between pressing the right mouse button and starting to drag. Needless to say, this makes using Ubuntu pretty annoying. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Feb 6 00:43:39 2014 DistUpgraded: 2014-02-01 11:51:02,949 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu InstallationDate: Installed on 2013-01-11 (391 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: FUJITSU LIFEBOOK T901 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=1ce784cf-72d2-4312-bf02-c5e72148ff90 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2014-02-01 (4 days ago) dmi.bios.date: 06/08/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.08 dmi.board.name: FJNB228 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: AOK331E5123F2005 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.08:bd06/08/2011:svnFUJITSU:pnLIFEBOOKT901:pvr:rvnFUJITSU:rnFJNB228:rvr:cvnAOK331E5123F2005:ct10:cvr: dmi.product.name: LIFEBOOK T901 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 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-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Feb 1 21:33:26 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2600 vendor BOE xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1276960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277366] Re: Mouse tracking issue
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1277366 Title: Mouse tracking issue Status in “xorg” package in Ubuntu: Confirmed Bug description: I am using a usb mouse on ubuntu 12.10. Everything was working fine but today when i turned on my computer the mouse isn't working. The red light under mouse is on but neither the cursor moves nor the buttons work. I am also using a usb keyboard but it is working fine. i have changed the mouse but the other mouse also doesn't work where as it works completely fine on another computer (windows 7). Thank you haider Jafree ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-45.68-generic 3.5.7.26 Uname: Linux 3.5.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 25.024613] tg3 :03:00.0: eth0: Flow control is on for TX and on for RX [ 25.024837] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 1102.200044] hub 6-0:1.0: unable to enumerate USB device on port 1 Date: Fri Feb 7 11:59:48 2014 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 82Q963/Q965 Integrated Graphics Controller [8086:2992] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:100d] InstallationDate: Installed on 2006-08-02 (2746 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 8808Y98 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-45-generic root=UUID=41af7abb-28d5-4fa3-907a-6c1696a0ad45 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 2JKT30AUS dmi.board.name: LENOVO dmi.board.vendor: LENOVO dmi.chassis.asset.tag: 57094 dmi.chassis.type: 4 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8808Y98:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct4:cvr: dmi.product.name: 8808Y98 dmi.product.version: ThinkCentre M55 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu0.0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.3-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278043] Re: No Arabic support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: speech-dispatcher (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1278043 Title: No Arabic support Status in “speech-dispatcher” package in Ubuntu: Confirmed Bug description: Hello, Thank you very much for your efforts, but Orca doesn't support Arabic. I really hope that Orca support it, many people will benefit so much. These applications support Arabic - they are for windows - maybe they have what Orca developers need to support Arabic vocalizer, nvda, jaws I found this link https://vocalizer-nvda.com/downloads It has Arabic packages, which I hope help. * I have reported this but to Orca, but an Orca developer said that I should report it to speech dispatcher More info 1- I use Ubuntu 12.10 32-Bit 2- speech-dispatcher: Installed: 0.7.1-6.1ubuntu2 Candidate: 0.7.1-6.1ubuntu2 Version table: *** 0.7.1-6.1ubuntu2 0 500 http://eg.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages 100 /var/lib/dpkg/status 3- Orca's version is 3.7.0.94 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1278043/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249022] Re: Please backport indicator-weather 13.7.1 to saucy
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-weather (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/1249022 Title: Please backport indicator-weather 13.7.1 to saucy Status in Indicator-Weather: New Status in “indicator-weather” package in Ubuntu: Confirmed Bug description: The default version in saucy is error prone and buggy. The ppa version 13.7.1 is stable and accurate. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-weather 13.7.1 [origin: LP-PPA-weather-indicator-team] ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CrashDB: indicator_weather Date: Thu Nov 7 16:52:15 2013 InstallationDate: Installed on 2012-09-18 (415 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120918.1) MarkForUpload: True PackageArchitecture: all SourcePackage: indicator-weather ThirdParty: True UpgradeStatus: Upgraded to saucy on 2013-07-02 (128 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/1249022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280905] Re: firefox on ubuntu 14.04 does not play mp4 files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1280905 Title: firefox on ubuntu 14.04 does not play mp4 files Status in “firefox” package in Ubuntu: Confirmed Bug description: On xubuntu 14.04 the package gstreamer0.10-ffmpeg_0.10.13-5_amd64.deb is not available, so I could not use mp4 h264 files in html5 tags. I used the .deb package from ubuntu 13.10 and after an apt-get -f install everything works fine. I don't know why the gstreamer0.10-ffmpeg package is not available anymore, it looks like firefox could use gstreamer1.0-libav. I don't know if the h264 decoder is enabled in gstreamer1.0-libav package. I hope that this bug report will help people get html5 video working. Tested with firefox 25 and 29. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1280905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281058] Re: The system shutdowns when multiple accounts are open
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1281058 Title: The system shutdowns when multiple accounts are open Status in “systemd” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Create a second account in the system 2) While the first account is open, open a session with the second one 3) Try to shutdown the system Expected results: The system logs out instead of shutting down (ideally with a warning on why it did that) Actual results: The system shutdowns and unsaved data on session1 is lost ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Feb 17 11:49:48 2014 InstallationDate: Installed on 2013-06-17 (244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-20 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1281058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087763] Re: VGA is blank/black on P4M900
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-openchrome (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1087763 Title: VGA is blank/black on P4M900 Status in openchrome: New Status in “xserver-xorg-video-openchrome” package in Ubuntu: Confirmed Bug description: VGA is blank/black on P4M900 when monitor/tft is switched on *after* booting linux. To manage notifications about this bug go to: https://bugs.launchpad.net/openchrome/+bug/1087763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1271467] Re: radio stream playback blocks the screensaver
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rhythmbox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1271467 Title: radio stream playback blocks the screensaver Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Whenever I play a radio stream on rhythmbox, the display does not blank after the screensaver timeout. Playing stuff from the music library does not do the same. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.1-1ubuntu8 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 22 11:44:48 2014 InstallationDate: Installed on 2012-11-07 (440 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2014-01-07 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1271467/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274239] Re: texlive-luatex : lua2dox_lua missing in Saucy - /usr/bin/lua2dox_filter is dangling symbolic link
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: texlive-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1274239 Title: texlive-luatex : lua2dox_lua missing in Saucy - /usr/bin/lua2dox_filter is dangling symbolic link Status in “texlive-base” package in Ubuntu: Confirmed Bug description: PRETTY_NAME="Ubuntu 13.10" VERSION="13.10, Saucy Salamander" Package: texlive-luatex Section: tex Origin: Ubuntu Maintainer: Ubuntu Developers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Architecture: all Source: texlive-base Version: 2013.20130722-1 Upon installation of texlive-luatex, a dangling symbolic link is created 0 lrwxrwxrwx 1 root root 11 2013-07-25 13:19 /usr/bin/lua2dox_filter -> lua2dox_lua According to apt-file search, no package contains lua2dox_lua so this file is missing from this package. In the earlier Ubuntu 12.10 "Quantal Quetzal" texlive-luatex 2012.20120611-4 version, neither the symbolic link lua2dox_filter (nor lua2dox_lua its-self) was present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1274239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087763] Re: VGA is blank/black on P4M900
I can confirm this problem with P4M900 which is built in on the Gigabyte GA-VM900M. Maybe about a year ago I installed 12.04 LTS (may have been 12.04-1 or 12.04-2) and it worked fine with this video card. This time I used the updated 12.04-4 and it couldn't start X. I'm going to try installing 12.04-4 but reverting to an older version of xserver-xorg- video-openchrome from the CLI. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1087763 Title: VGA is blank/black on P4M900 Status in openchrome: New Status in “xserver-xorg-video-openchrome” package in Ubuntu: Confirmed Bug description: VGA is blank/black on P4M900 when monitor/tft is switched on *after* booting linux. To manage notifications about this bug go to: https://bugs.launchpad.net/openchrome/+bug/1087763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280077] Re: Text in the top panel is escaped while it's not needed
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1279499] Re: Input interactions in the Switcher has random behavior
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1274985] Re: Hud icon states are incorrect when displaying Hud on a monitor with no Launcher
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1277265] Re: Clicking a menu entry doesn't always show the drop down menu the first time
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1263775] Re: Icon won't wiggle at defined intervals if it's been urgent before
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1267902] Re: The unity-autopilot package should depend on mesa-utils
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1274554] Re: Panel should show a dropdown menu if the menu entries doesn't fit in the available horizontal space
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1252760] Re: Alt-Tab arrow keys doesn't work when the switcher is opened when the dash is opened
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1271710] Re: doesn't list compiz/unity keybindings
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1267210] Re: Dash/Hud stealing focus from fullscreen windows
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1267888] Re: Using mouse scrollwheel on unfocused/inactive Launcher icons should not focus that app
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1279904] Re: Launcher drag icon background flickers for a second after start dragging
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1255241] Re: [regression] Clicking the Hud icon does not close the Hud
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1253740] Re: Active blur for Quicklists/Tooltips no longer working after committing performance updates to Unity
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1251275] Re: UnityScreen::nuxPrologue / UnityScreen::nuxEpilogue are unnecessary expensive
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1244704] Re: Some test_hud tests fail on trusty desktop
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1227131] Re: Add suport for 3D points TypeID
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1170508] Re: Alt-Tab, shutdown dialog and shortcut overlay should not be transparent in Low GFX Mode
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1098419] Re: Panel should be right-clickable when window is maximised with global menu enabled
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1173219] Re: error building with GTK 3.9: gtk_widget_get_state is deprecated
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1080947] Re: damageScreen() in UnityScreen::nuxDamageCompiz() severely hurts Unity performance
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1179210] Re: unity_low_gfx_mode + auto hide launcher causes visual artifacts
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1206582] Re: [regression] pressing and holding the alt key in a GTK app does not show the menu bar
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 691817] Re: Framing around window decorations on windows and panel should be identical.
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 830709] Re: Keyboard shortcut - Unity should also use Super-L to lock screen by default
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 834777] Re: static blur does not show what was on the desktop before the dash opened
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 961890] Re: Keyboard shortcuts - dash home does not minimize with ctrl-super-D
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1175669] Re: fcitx often fails to work in dash with Unity
This bug was fixed in the package nux - 4.0.5+14.04.20140214-0ubuntu1
---
nux (4.0.5+14.04.20140214-0ubuntu1) trusty; urgency=low
[ Brandon Schaefer ]
* Add XIM preedit support
* Bump version to 4.0.5
* We need to check if the XIC client is synced up with the xevents
coming in. If someone changes the focus window and our XIC hasn't
been updated, we need to make sure we stay synced. Otherwise XIM
fails to work. (LP: #1175669)
[ CI bot ]
* Flush trunk to Ubuntu
[ Chris Townsend ]
* Need to add version 1.10 of lcov to the supported versions so the
Debian package build can succeed.
[ Eleni Maria Stea ]
* added virtual destructors where missing (fixing static analysis
errors).
* small fixes based on clang errors and warnings.
* fixed syntax error in macro.
* minor fixes (static analyzer errors and warnings).
[ Albert Astals ]
* Kill declared but not implemented functions.
nux (4.0.4-0ubuntu1) UNRELEASED; urgency=low
[ Sam Spilsbury ]
* Bump version to 4.0.4.
-- Ubuntu daily releaseFri, 14 Feb 2014
23:11:31 +
** Changed in: nux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1175669
Title:
fcitx often fails to work in dash with Unity
Status in Nux:
Fix Committed
Status in Unity:
Invalid
Status in “nux” package in Ubuntu:
Fix Released
Status in “unity” package in Ubuntu:
Invalid
Status in “nux” source package in Saucy:
New
Bug description:
The input method "fcitx' is supposed to work with Unity dash in raring,but it
is not working well.
This happens *only* when I set the launcher to hide as default.
When I press Super to open the dash and begin to type characters into dash or
HUD display (by pressing left alt),sometimes I can activate the input method.In
more cases,there aren't any response when pressing "ctrl+space".Sometimes I
can't type anything into dash.
I've asked a developer of fcitx ("csslayer") but he said he knew
nothing about it.He said it could be a bug of unity and suggested me
to report the bug here.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu May 2 23:51:07 2013
InstallationDate: Installed on 2012-05-01 (365 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
(20120423)
MarkForUpload: True
SourcePackage: unity
UpgradeStatus: Upgraded to raring on 2013-04-03 (28 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nux/+bug/1175669/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 827537] Re: Decorations needs to support anti aliased rounded corners
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1113008] Re: F10 or Alt+ opens the window menus within the window
This bug was fixed in the package unity -
7.1.2+14.04.20140214.1-0ubuntu1
---
unity (7.1.2+14.04.20140214.1-0ubuntu1) trusty; urgency=low
[ Sebastien Bacher ]
* use unity-control-center by default.
* lists keybinding in unity-control-center. (LP: #1271710)
[ Brandon Schaefer ]
* Bump to new libnux from this branch:
https://code.launchpad.net/~brandontschaefer/nux/xim-preedit-
support.
* Adds Super+L to lock the screen, while keeping the older shortcut
around in g-s-d (Ctrl+Alt+L). (LP: #830709)
* Do not open the dash/hud on a monitor with a top most window that is
fullscreen. (LP: #1267210)
* Implement an EMConveter. This way with default settings such that
DPI = 96.0f, and font_size = system font size. We can get the
correct EM value for any pixel size. Once we have the correct EM
value for any pixel size, the DPI value can be adjusted to the
current logical one. From here, you can now get the correct pixel
size based from of the EM value for the logical DPI of the screen.
* Refactor EMConverter API. Now all thats needed is int
ConvertPixels(int pixel); This will calculate the correct pixel size
based on the DPI and font size.
* Testing that the ibus anthy tests could possibly be causing strange
issues on the nvidia machine. So skipping them to test if tihs is
the source of the error.
* Add Pt to Px function to em converter.
* Move EMConverter over to unity settings.
* Add multi monitor support for EMConverter in unity settings. Now you
can grab a specific converter per monitor.
* Simple RawPixel class. It adds 2 define literals, ex: 10_em,
10.0_em. From there it turns them into raw pixels. RawPixels have CP
(CovertPixel) function which takes in an EMConverter that allows you
to use a converter specific to a monitor to convert the raw pixel to
the correct value.
[ Marco Trevisan (Treviño) ]
* Don't re-present all of our windows on every frame. Only do that if
damage intersects it. Use the new APIs exposed by compiz and nux to
intelligently determine which windows need to be presented per-frame
and only register damage for those windows. This fixes two things:
1. BaseWindows being redrawn from scratch every time damage was
registered over them. That was incorrect and should only be done in
the case of background blurs. 2. BaseWindows being drawn to the
screen on every frame, regardless of whether or not they needed to
be. Now they will only be drawn if some damage intersects beneath
them. Note that unity will expand the damage region to accomadate
the base window since nux does not support geometry clipping. So if
there is a partial intersection of the launcher for example, the
area of the screen which contains the launcher will be re-painted
(but the launcher itself won't be redrawn, just its texture) (LP:
#1080947). (LP: #1080947)
* Convert compiz regions / rects to nux::Geometry's and back easily.
* UnityScreen: remove the useless and expensive gl{Push,Pop}Attrib
calls For some reasons this code was copied by the opengl plugin as
a workaround to fix the state of our screen after that nux has
drawn. Actually this is not needed, the only thing we really need to
do is to fix the current Viewport, because nux seems to leave it in
a bad state which would lead to flickering menus, fullscreen
windows, tooltip and missing windows thumbnails in switcher. Thanks
to Sam Spilsbury for his precious support. (LP: #1251275)
* Unity: always prefer passing [this] to lambdas than [&].
* Introspectable: use IntrospectionData class for collecting data from
children Now each introspectable object is called with an
IntrospectionData parameter and calling one of its methods it's the
only way to fill introspection data into unity. As bonus point,
remove all the unneeded UnityCore/Variant.cpp inclusions. (LP:
#1227131)
* DebugDBusInterface: add local::xpathselect::NodeSelector to use the
dloaded lib.
* BackgroundEffectHelper: Specify the required blur area before
drawing so selectively copy it at paint time This means that we
don't have to waste fragment bandwidth copying the entire backbuffer
when we could just do parts of it. Now BackgroundEffectHelper
listens to windows and views geometry changes and updates a list of
blurred regions that might be copied to the backup texture at every
repaint that affects them. This avoids to copy large regions
(especially when using big resolutions or multiple monitors), but
only the ones we really need to blur.
* SwitcherView: define a custom GeometryGetterFunc and notify helper
on changes Thanks to this the switcher won't make
BackgroundEffectHelper to create a blurred area as big as the
current monitor (with just a small padding), but an area big enough
to draw its background. This get updated automagic
[Desktop-packages] [Bug 1280114] Re: "pydoc -k ." hangs
** Description changed:
I have noticed that "pydoc -k ." hangs on my system.
This method is used by vim-ref (https://github.com/thinca/vim-ref/) to
get a list of all entries.
+
+ Stepping thorugh it via "ipdb", it hangs at:
+
+ > /usr/lib/python2.7/dist-packages/gi/module.py(171)__getattr__()
+ 170 elif isinstance(info, RegisteredTypeInfo):
+ --> 171 g_type = info.get_g_type()
+ 172
+
With `strace -f`, this is where it hangs:
[pid 14429] access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
[pid 14429] open("/usr/lib/x86_64-linux-gnu/libatspi.so.0",
O_RDONLY|O_CLOEXEC) = 17
[pid 14429] read(17,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\20\332\0\0\0\0\0\0"..., 832) =
832
[pid 14429] fstat(17, {st_mode=S_IFREG|0644, st_size=178328, ...}) = 0
[pid 14429] mmap(NULL, 2274208, PROT_READ|PROT_EXEC,
MAP_PRIVATE|MAP_DENYWRITE, 17, 0) = 0x7f6ebbbcc000
[pid 14429] mprotect(0x7f6ebbbf4000, 2097152, PROT_NONE) = 0
[pid 14429] mmap(0x7f6ebbdf4000, 16384, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 17, 0x28000) = 0x7f6ebbdf4000
[pid 14429] close(17) = 0
[pid 14429] mprotect(0x7f6ebbdf4000, 12288, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ec05eb000, 8192, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ebbffb000, 4096, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ec03cd000, 81920, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ec0816000, 4096, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ec0a1f000, 8192, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ec0cb1000, 16384, PROT_READ) = 0
[pid 14429] mprotect(0x7f6ec137d000, 32768, PROT_READ) = 0
[pid 14429] munmap(0x7f6ee9dd, 183571) = 0
[pid 14429] stat("libgdk-3.so.0", 0x7fff3ac35030) = -1 ENOENT (No such file
or directory)
[pid 14429] stat("libgdk-3.so.0.so", 0x7fff3ac35030) = -1 ENOENT (No such
file or directory)
[pid 14429] stat("libgdk-3.so.0.la", 0x7fff3ac35030) = -1 ENOENT (No such
file or directory)
[pid 14429] openat(AT_FDCWD, "/usr/lib/girepository-1.0",
O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 17
[pid 14429] getdents(17, /* 117 entries */, 32768) = 4952
[pid 14429] open("/usr/lib/girepository-1.0/Atk-1.0.typelib", O_RDONLY) = 18
[pid 14429] fstat(18, {st_mode=S_IFREG|0644, st_size=65276, ...}) = 0
[pid 14429] mmap(NULL, 65276, PROT_READ, MAP_PRIVATE, 18, 0) = 0x7f6ee9ded000
[pid 14429] close(18) = 0
[pid 14429] getdents(17, /* 0 entries */, 32768) = 0
[pid 14429] close(17) = 0
[pid 14429] munmap(0x7f6ee9ded000, 65276) = 0
[pid 14429] stat("/usr/lib/python2.7/dist-packages/gi/overrides/Atk",
0x7fff3ac32ee0) = -1 ENOENT (No such file or directory)
[pid 14429]
open("/usr/lib/python2.7/dist-packages/gi/overrides/Atk.x86_64-linux-gnu.so",
O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 14429] open("/usr/lib/python2.7/dist-packages/gi/overrides/Atk.so",
O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 14429]
open("/usr/lib/python2.7/dist-packages/gi/overrides/Atkmodule.so", O_RDONLY) =
-1 ENOENT (No such file or directory)
[pid 14429] open("/usr/lib/python2.7/dist-packages/gi/overrides/Atk.py",
O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 14429] open("/usr/lib/python2.7/dist-packages/gi/overrides/Atk.pyc",
O_RDONLY) = -1 ENOENT (No such file or directory)
[pid 14429] stat("libatk-1.0.so.0", 0x7fff3ac34030) = -1 ENOENT (No such file
or directory)
[pid 14429] stat("libatk-1.0.so.0.so", 0x7fff3ac34030) = -1 ENOENT (No such
file or directory)
[pid 14429] stat("libatk-1.0.so.0.la", 0x7fff3ac34030) = -1 ENOENT (No such
file or directory)
[pid 14429] futex(0x42ff0a4, FUTEX_WAIT_PRIVATE, 1, NULL
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: python2.7 2.7.5-8ubuntu3
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
Date: Fri Feb 14 08:11:08 2014
InstallationDate: Installed on 2012-05-28 (626 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
SourcePackage: python2.7
UpgradeStatus: Upgraded to saucy on 2013-10-08 (128 days ago)
** Also affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I have noticed that "pydoc -k ." hangs on my system.
This method is used by vim-ref (https://github.com/thinca/vim-ref/) to
get a list of all entries.
Stepping thorugh it via "ipdb", it hangs at:
> /usr/lib/python2.7/dist-packages/gi/module.py(171)__getattr__()
- 170 elif isinstance(info, RegisteredTypeInfo):
+ 170 elif isinstance(info, RegisteredTypeInfo):
--> 171 g_type = info.get_g_type()
- 172
+ 172
+ Upgrading python-gi to 3.11.5-0ubuntu1 (from 3.10.0-1ubuntu1) fixed this
+ particular issue. Now `pydoc -k .` segfaults instead (later on).
[Desktop-packages] [Bug 1281084] [NEW] UnicodeDecodeError in is_closing_session
Public bug reported:
>From apport.log:
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: called for pid 11135,
signal 11, core limit 18446744073709551615
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: ignoring implausibly big
core limit, treating as unlimited
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: script: /usr/bin/pydoc2.7,
interpreted by /usr/bin/python2.7 (command line "/usr/bin/python2.7
/usr/bin/pydoc -k .")
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 373, in
if is_closing_session(pid, pidstat.st_uid):
File "/usr/share/apport/apport", line 214, in is_closing_session
env = e.read().split('\0')
File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9786:
ordinal not in range(128)
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: pid: 11229, uid: 1000, gid:
1000, euid: 0, egid: 0
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: environment: environ({})
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: apport 2.12.5-0ubuntu2.2
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CrashReports:
640:1000:114:120104180:2014-02-13 00:58:41.677010970 +0100:2014-02-13
00:57:20.989009053 +0100:/var/crash/_opt_firefox_firefox.1000.crash
640:1000:114:63870076:2014-02-13 00:00:35.972928127 +0100:2014-02-12
23:59:49.260927017 +0100:/var/crash/_usr_lib_firefox_firefox.1000.crash
640:1000:114:14175879:2014-02-09 10:23:03.104148831 +0100:2014-02-09
10:22:57.576148699 +0100:/var/crash/_usr_bin_nautilus.1000.crash
Date: Mon Feb 17 13:27:00 2014
InstallationDate: Installed on 2012-05-28 (629 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to saucy on 2013-10-08 (131 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2014-02-13T00:58:07.609010
** Affects: apport (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug saucy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1281084
Title:
UnicodeDecodeError in is_closing_session
Status in “apport” package in Ubuntu:
New
Bug description:
From apport.log:
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: called for pid 11135,
signal 11, core limit 18446744073709551615
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: ignoring implausibly big
core limit, treating as unlimited
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: script:
/usr/bin/pydoc2.7, interpreted by /usr/bin/python2.7 (command line
"/usr/bin/python2.7 /usr/bin/pydoc -k .")
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: Unhandled exception:
Traceback (most recent call last):
File "/usr/share/apport/apport", line 373, in
if is_closing_session(pid, pidstat.st_uid):
File "/usr/share/apport/apport", line 214, in is_closing_session
env = e.read().split('\0')
File "/usr/lib/python3.3/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 9786:
ordinal not in range(128)
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: pid: 11229, uid: 1000,
gid: 1000, euid: 0, egid: 0
ERROR: apport (pid 11229) Mon Feb 17 13:26:22 2014: environment: environ({})
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: apport 2.12.5-0ubuntu2.2
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CrashReports:
640:1000:114:120104180:2014-02-13 00:58:41.677010970 +0100:2014-02-13
00:57:20.989009053 +0100:/var/crash/_opt_firefox_firefox.1000.crash
640:1000:114:63870076:2014-02-13 00:00:35.972928127 +0100:2014-02-12
23:59:49.260927017 +0100:/var/crash/_usr_lib_firefox_firefox.1000.crash
640:1000:114:14175879:2014-02-09 10:23:03.104148831 +0100:2014-02-09
10:22:57.576148699 +0100:/var/crash/_usr_bin_nautilus.1000.crash
Date: Mon Feb 17 13:27:00 2014
InstallationDate: Installed on 2012-05-28 (629 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to saucy on 2013-10-08 (131 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2014-02-13T00:58:07.609010
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1281084/+su
[Desktop-packages] [Bug 1280794] Re: Can't change default "Open with" application
No bug in guest session. When I do "nautilus -q; nautilus" I immediately get: Initializing nautilus-dropbox 1.6.1 (nautilus:499): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed (nautilus:499): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed (nautilus:499): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed (nautilus:499): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed Initializing nautilus-dropbox 1.6.1 (nautilus:508): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed (nautilus:508): GLib-GObject-CRITICAL **: g_object_set: assertion 'G_IS_OBJECT (object)' failed Nautilus starts I do my thing and get these new lines: (nautilus:508): Gtk-CRITICAL **: gtk_widget_show: assertion 'GTK_IS_WIDGET (widget)' failed (nautilus:508): Gtk-CRITICAL **: gtk_spinner_start: assertion 'GTK_IS_SPINNER (spinner)' failed -- 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/1280794 Title: Can't change default "Open with" application Status in “nautilus” package in Ubuntu: Incomplete Bug description: I am on Ubuntu 13.10 using nautilus 1:3.8.2-0ubuntu2.2. I am trying to change default application to open .avi files. I right- click an .avi file select "Properties", go to "Open With". There is a default application there (banshee) and recommended (VLC media player). I select VLC media player and click "Set as default" button, selection jumps back to banshee, "Set as default" button disabled and nothing else happens. Nautilus still opens .avi files with banshee. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 21:45:45 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1497x873+0+171'" InstallationDate: Installed on 2013-11-17 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-11-20T19:34:55.419627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132570] Re: gvfsd-smb crashed with SIGSEGV in smbc_free_context()
Just had the same crash while accessing a Samba share on local network. -- 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/1132570 Title: gvfsd-smb crashed with SIGSEGV in smbc_free_context() Status in “gvfs” package in Ubuntu: Confirmed Bug description: Sorry i have not been able to reproduce this error ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gvfs-backends 1.15.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Sun Feb 24 22:29:02 2013 ExecutablePath: /usr/lib/gvfs/gvfsd-smb InstallationDate: Installed on 2013-01-15 (40 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcCmdline: /usr/lib/gvfs/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/13 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0d61804e6c : mov 0x430(%rax),%rbx PC (0x7f0d61804e6c) ok source "0x430(%rax)" (0x05a0) not located in a known VMA region (needed readable region)! destination "%rbx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: smbc_free_context () from /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so g_vfs_job_run () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so ?? () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so Title: gvfsd-smb crashed with SIGSEGV in smbc_free_context() UpgradeStatus: Upgraded to raring on 2013-02-10 (13 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1132570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995330]
I did some research on this bug while thinking of a resolution for #74416. Currently the KDE4 backend works like this: * Get a control request * Generate a QImage with the requested size * Fill image with the QPalette::Window color * Draw the control with the theme style to the QImage * Blit / copy the image to the actual target This results in this - actually unstyled - dropdown menus. So for a test I changed the menu generation to a more Gtk+ backend approach: * Get the control request from vcl * Create a QMenu object * Resize the menu to the requested size * Copy the QMenu to a QImage using QImage(QPixmap::grabWidget(...).toImage()) * Draw the control with the theme style to the QImage * Blit / copy the image to the actual target This generates the correct background (yeah); but now I realized (to my increasing frustration), that the highlighting is actually drawn based on the background image with a different color. Probably just the opaque value is adapted - I didn't actually check the Oxygen code. To make the KDE theming using VCL even harder, Oxygen uses some kind of animation to fade the highlighting to the correct color, which won't work using the QImage based copy approach (and I also don't know how this actually works in the Oxygen Qt style engine). Additionally the QPixmap::toImage() call has additional drawbacks: "Note that for the moment, alpha masks on monochrome images are ignored." (http://qt-project.org/doc/qt-4.8/qpixmap.html#toImage) >From my current point of understanding of all the interaction, the only realistic way to fix the styling problems is to draw LO native widgets using a real Qt widgets stack and let LO draw it's specific objects. I guess this will result in a complete rewrite of the KDE4 backend based on a new architecture - if this is possible using VCL. And there is already an abstraction for (popup) menus, which uses the same approach (SalMenu). Now I need to get some feedback, if this approach is implementable at all. I would start a kde4v2 backend, but this is a lot more work then I have currently time for: GSoC 2014 anyone? -- 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/995330 Title: [Upstream] Libreoffice has no border on menus (KDE) Status in LibreOffice Productivity Suite: In Progress Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Libreoffice has no border on menus, with a bad appearance. Image attached to show the problem. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-kde 1:3.5.2-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 5 23:37:27 2012 InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120228.1) ProcEnviron: LANGUAGE=pt_BR:pt:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/995330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281090] [NEW] Gio doesn't support automatic proxy configuration
Public bug reported: I ran into this bug when trying to configure the Rhythmbox music player to work with Last.fm. When using automatic proxy configuration, it attempted to connect directly to the target server. When I switched ot manual proxy configuration, it used the system proxy settings. It appears that the problem is in gio proxy resolution system, which doesn't support automatic proxy configuration through PAC files as demonstrated by the test program at: https://gist.github.com/tazle/9049829. For me, program prints "direct://" if automatic proxy configuration is enabled and the correct proxy address if I switch to manual configuration with our external WWW proxy address. The same problem has been originally reported for gnome-vfs aeons ago at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=289357 and https://bugzilla.gnome.org/show_bug.cgi?id=123900. Perhaps now, almost 10 years later, it would be possible to resolve this issue? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libglib2.0-0 2.32.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-44.67~precise1-generic 3.5.7.25 Uname: Linux 3.5.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Feb 17 14:45:29 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1281090 Title: Gio doesn't support automatic proxy configuration Status in “glib2.0” package in Ubuntu: New Bug description: I ran into this bug when trying to configure the Rhythmbox music player to work with Last.fm. When using automatic proxy configuration, it attempted to connect directly to the target server. When I switched ot manual proxy configuration, it used the system proxy settings. It appears that the problem is in gio proxy resolution system, which doesn't support automatic proxy configuration through PAC files as demonstrated by the test program at: https://gist.github.com/tazle/9049829. For me, program prints "direct://" if automatic proxy configuration is enabled and the correct proxy address if I switch to manual configuration with our external WWW proxy address. The same problem has been originally reported for gnome-vfs aeons ago at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=289357 and https://bugzilla.gnome.org/show_bug.cgi?id=123900. Perhaps now, almost 10 years later, it would be possible to resolve this issue? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libglib2.0-0 2.32.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-44.67~precise1-generic 3.5.7.25 Uname: Linux 3.5.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Feb 17 14:45:29 2014 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) MarkForUpload: True SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1281090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280794] Re: Can't change default "Open with" application
What about "ls -ld ~/.local/share/applications" and the files in that directory? -- 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/1280794 Title: Can't change default "Open with" application Status in “nautilus” package in Ubuntu: Incomplete Bug description: I am on Ubuntu 13.10 using nautilus 1:3.8.2-0ubuntu2.2. I am trying to change default application to open .avi files. I right- click an .avi file select "Properties", go to "Open With". There is a default application there (banshee) and recommended (VLC media player). I select VLC media player and click "Set as default" button, selection jumps back to banshee, "Set as default" button disabled and nothing else happens. Nautilus still opens .avi files with banshee. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 21:45:45 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1497x873+0+171'" InstallationDate: Installed on 2013-11-17 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-11-20T19:34:55.419627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281086] [NEW] Crash in os.environ.clear() with empty environment key
Public bug reported: % ubuntu-bug apport Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 590, in app.run_argv() File "/usr/lib/python3/dist-packages/apport/ui.py", line 654, in run_argv return self.run_report_bug() File "/usr/lib/python3/dist-packages/apport/ui.py", line 456, in run_report_bug self.collect_info(symptom_script) File "/usr/lib/python3/dist-packages/apport/ui.py", line 1031, in collect_info os.environ.clear() File "/usr/lib/python3.3/collections/abc.py", line 553, in clear self.popitem() File "/usr/lib/python3.3/collections/abc.py", line 546, in popitem del self[key] File "/usr/lib/python3.3/os.py", line 687, in __delitem__ self.unsetenv(encodedkey) OSError: [Errno 22] Invalid argument Looking at the output of `os.environ`, there is a odd entry (key ''). os.environ.clear() fails both with python2.7 and python3: In [1]: import os In [2]: os.environ[''] = '' In [3]: os.environ.clear() --- OSError Traceback (most recent call last) in () > 1 os.environ.clear() /usr/lib/python3.3/collections/abc.py in clear(self) 551 try: 552 while True: --> 553 self.popitem() 554 except KeyError: 555 pass /usr/lib/python3.3/collections/abc.py in popitem(self) 544 raise KeyError 545 value = self[key] --> 546 del self[key] 547 return key, value 548 /usr/lib/python3.3/os.py in __delitem__(self, key) 685 def __delitem__(self, key): 686 encodedkey = self.encodekey(key) --> 687 self.unsetenv(encodedkey) 688 try: 689 del self._data[encodedkey] OSError: [Errno 22] Invalid argument While this looks like a bug to be fixed in Python also, apport should handle it gracefully, and not crash/abort on it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CrashReports: 640:1000:114:120104180:2014-02-13 00:58:41.677010970 +0100:2014-02-13 00:57:20.989009053 +0100:/var/crash/_opt_firefox_firefox.1000.crash 640:1000:114:63870076:2014-02-13 00:00:35.972928127 +0100:2014-02-12 23:59:49.260927017 +0100:/var/crash/_usr_lib_firefox_firefox.1000.crash 640:1000:114:14175879:2014-02-09 10:23:03.104148831 +0100:2014-02-09 10:22:57.576148699 +0100:/var/crash/_usr_bin_nautilus.1000.crash Date: Mon Feb 17 13:41:48 2014 InstallationDate: Installed on 2012-05-28 (629 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-10-08 (131 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2014-02-13T00:58:07.609010 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Affects: python3.3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: - % ubuntu-bug apport + % ubuntu-bug apport Traceback (most recent call last): - File "/usr/share/apport/apport-gtk", line 590, in - app.run_argv() - File "/usr/lib/python3/dist-packages/apport/ui.py", line 654, in run_argv - return self.run_report_bug() - File "/usr/lib/python3/dist-packages/apport/ui.py", line 456, in run_report_bug - self.collect_info(symptom_script) - File "/usr/lib/python3/dist-packages/apport/ui.py", line 1031, in collect_info - os.environ.clear() - File "/usr/lib/python3.3/collections/abc.py", line 553, in clear - self.popitem() - File "/usr/lib/python3.3/collections/abc.py", line 546, in popitem - del self[key] - File "/usr/lib/python3.3/os.py", line 687, in __delitem__ - self.unsetenv(encodedkey) + File "/usr/share/apport/apport-gtk", line 590, in + app.run_argv() + File "/usr/lib/python3/dist-packages/apport/ui.py", line 654, in run_argv + return self.run_report_bug() + File "/usr/lib/python3/dist-packages/apport/ui.py", line 456, in run_report_bug + self.collect_info(symptom_script) + File "/usr/lib/python3/dist-packages/apport/ui.py", line 1031, in collect_info + os.environ.clear() + File "/usr/lib/python3.3/collections/abc.py", line 553, in clear + self.popitem() + File "/usr/lib/python3.3/collections/abc.py", line 546, in popitem + del self[key] + File "/usr/lib/python3.3/os.py", line 687, in __delitem__ + self.unsetenv(encodedkey) OSError: [Errno 22] Invalid argument Looking at the output of `os.environ`, there is a odd entry (key ''). + + os.environ.clear() fails both with python2
[Desktop-packages] [Bug 1280794] Re: Can't change default "Open with" application
Looks like it's something wrong with my "~/.local/share/applications/mimeapps.list" config. After removing it I am able to change associations back and forth. Attaching my old broken mimeapps.list. ** Attachment added: "mimeapps.list.copy" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+attachment/3983873/+files/mimeapps.list.copy -- 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/1280794 Title: Can't change default "Open with" application Status in “nautilus” package in Ubuntu: Incomplete Bug description: I am on Ubuntu 13.10 using nautilus 1:3.8.2-0ubuntu2.2. I am trying to change default application to open .avi files. I right- click an .avi file select "Properties", go to "Open With". There is a default application there (banshee) and recommended (VLC media player). I select VLC media player and click "Set as default" button, selection jumps back to banshee, "Set as default" button disabled and nothing else happens. Nautilus still opens .avi files with banshee. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 21:45:45 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1497x873+0+171'" InstallationDate: Installed on 2013-11-17 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-11-20T19:34:55.419627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262990] Re: Negative unread counts without rhyme or reason
It's not just that, sometimes the messages from 'negative' count are not showing at all in message window, you have to read them from conversation history, which means you need history window opened on daily basics. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1262990 Title: Negative unread counts without rhyme or reason Status in “empathy” package in Ubuntu: Confirmed Bug description: When I open up chat windows after seeing them in the message bar I see negative unread counts in the message list. Screenshot is attached. Might be related to #1262980 (duplicate entries for chats in the message list) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 20 01:34:12 2013 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationDate: Installed on 2013-03-18 (277 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) SourcePackage: empathy UpgradeStatus: Upgraded to trusty on 2013-11-23 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1262990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280794] Re: Can't change default "Open with" application
I managed to break it again. Here are the steps: 1. Delete "~/.local/share/applications/mimeapps.list". 2. Set VLC as default player for .avi files through nautilus. 3. Goto System Settings -> Details -> Default applications and set VLC player to open video files. 4. Go back to nautilus and try to change default application for .avi files. Get the bug. It's worth noting that "~/.local/share/applications/mimeapps.list" is updated in step 4, but changes do not work. -- 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/1280794 Title: Can't change default "Open with" application Status in “nautilus” package in Ubuntu: Incomplete Bug description: I am on Ubuntu 13.10 using nautilus 1:3.8.2-0ubuntu2.2. I am trying to change default application to open .avi files. I right- click an .avi file select "Properties", go to "Open With". There is a default application there (banshee) and recommended (VLC media player). I select VLC media player and click "Set as default" button, selection jumps back to banshee, "Set as default" button disabled and nothing else happens. Nautilus still opens .avi files with banshee. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 21:45:45 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1497x873+0+171'" InstallationDate: Installed on 2013-11-17 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-11-20T19:34:55.419627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
