[Dx-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher
Could someone make me a summary of the final design or abut what it's been decided? -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings > Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1412937] Re: Config option to set UNITY_LOW_GFX_MODE=1
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1412937 Title: Config option to set UNITY_LOW_GFX_MODE=1 Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Right now the procedure to turn on low_gfx_mode is https://bugs.launchpad.net/compiz/+bug/1293384/comments/15 "sudo -H gedit /usr/share/gnome-session/sessions/ubuntu.session Remove "compiz" from the RequiredComponents list sudo -H gedit /usr/share/upstart/sessions/unity7.conf: Add these lines after "export COMPIZ_CONFIG_PROFILE": env UNITY_LOW_GFX_MODE="1" export UNITY_LOW_GFX_MODE" We should add a config option (preferably system wide) to tell Compiz/Unity to go to the LOW_GFX mode regardless of what the hardware says it can do. This will make it easier to setup items like terminal services using Unity. This procedure has helped in at least one case for me, (a machine used by several users remotely using Unity). I can imagine it would also help in multiseat scenarios, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1412937/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher
** Changed in: canonical-devices-system-image Milestone: ww13-2015 => None -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: In Progress Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings > Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363630] Re: Since revision 446.1.3, Zenity backend is broken
Run 'sudo apt-get install indicator-session' to update only the indicator-session package. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, &error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to "exit_status != 0". Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as "OK" buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select "Shutdown" from indicator-session menu. * In the popped up dialog select "Cancel". Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1403349] Re: Right click items in Launcher, pop up a menu, the menu will disappear after move the mouse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1403349 Title: Right click items in Launcher, pop up a menu, the menu will disappear after move the mouse Status in Ubuntu Kylin: New Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Right click items in Launcher, pop up a menu, the menu will disappear after move the mouse. This problem only exists in vivid x32 system. 右键点击启动栏的项目，弹出一个小菜单。移动鼠标后，小菜单消失。该问题只在vivid32位系统上发现 Steps: 1. Install the latest OS(Vivid x32 Daily Build 20141214) 2. Log in the system, right click the items in Launcher 3. After a menu pop up, move the mouse -->Failed. The menu disappear Configuration: OS: Vivid x32 Daily Build 20141214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1403349/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441914] Re: lua:socket settimeout does not work
It works correctly in Ubuntu 12.04, using packages:
liblua5.1-socket2 2.0.2-6
lua5.1
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1441914
Title:
lua:socket settimeout does not work
Status in unity package in Ubuntu:
New
Bug description:
Ubuntu Version: Ubuntu 14.04.2 LTS
package lua-socket:i386 3.0~rc1-3
On Ubuntu 14.04, lua socket settimeout does not work as expected. On a tcp
socket, it causes the next receive to close the connection immediately.
It works correctly on Ubuntu 12.04 and debian 7.
To reproduce:
install packages lua5.1 and lua-socket
Take the echo server example from the introduction to luasocket:
http://w3.impa.br/~diego/software/luasocket/introduction.html
Put it in a file echo.lua and run it with "lua echo.lua"
From another window, use telnet localhost {port} to connect to the echo server
Result: Immediately after connecting, the server closes the connection.
Expected Result: The server should wait 10 seconds for input, then close the
connection.
package version that works correctly in debian 7: lua-socket:i386 2.0.2-8
-
A copy of the example (echo.lua):
-- load namespace
local socket = require("socket")
-- create a TCP socket and bind it to the local host, at any port
local server = assert(socket.bind("*", 0))
-- find out which port the OS chose for us
local ip, port = server:getsockname()
-- print a message informing what's up
print("Please telnet to localhost on port " .. port)
print("After connecting, you have 10s to enter a line to be echoed")
-- loop forever waiting for clients
while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. "\n") end
-- done with client, close the object
client:close()
end
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441914/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441914] Re: lua:socket settimeout does not work
It is also broken with lua5.2 (on ubuntu 14.04).
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1441914
Title:
lua:socket settimeout does not work
Status in unity package in Ubuntu:
New
Bug description:
Ubuntu Version: Ubuntu 14.04.2 LTS
package lua-socket:i386 3.0~rc1-3
On Ubuntu 14.04, lua socket settimeout does not work as expected. On a tcp
socket, it causes the next receive to close the connection immediately.
It works correctly on Ubuntu 12.04 and debian 7.
To reproduce:
install packages lua5.1 and lua-socket
Take the echo server example from the introduction to luasocket:
http://w3.impa.br/~diego/software/luasocket/introduction.html
Put it in a file echo.lua and run it with "lua echo.lua"
From another window, use telnet localhost {port} to connect to the echo server
Result: Immediately after connecting, the server closes the connection.
Expected Result: The server should wait 10 seconds for input, then close the
connection.
package version that works correctly in debian 7: lua-socket:i386 2.0.2-8
-
A copy of the example (echo.lua):
-- load namespace
local socket = require("socket")
-- create a TCP socket and bind it to the local host, at any port
local server = assert(socket.bind("*", 0))
-- find out which port the OS chose for us
local ip, port = server:getsockname()
-- print a message informing what's up
print("Please telnet to localhost on port " .. port)
print("After connecting, you have 10s to enter a line to be echoed")
-- loop forever waiting for clients
while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. "\n") end
-- done with client, close the object
client:close()
end
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441914/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441914] [NEW] lua:socket settimeout does not work
Public bug reported:
Ubuntu Version: Ubuntu 14.04.2 LTS
package lua-socket:i386 3.0~rc1-3
On Ubuntu 14.04, lua socket settimeout does not work as expected. On a tcp
socket, it causes the next receive to close the connection immediately.
It works correctly on Ubuntu 12.04 and debian 7.
To reproduce:
install packages lua5.1 and lua-socket
Take the echo server example from the introduction to luasocket:
http://w3.impa.br/~diego/software/luasocket/introduction.html
Put it in a file echo.lua and run it with "lua echo.lua"
>From another window, use telnet localhost {port} to connect to the echo server
Result: Immediately after connecting, the server closes the connection.
Expected Result: The server should wait 10 seconds for input, then close the
connection.
package version that works correctly in debian 7: lua-socket:i386 2.0.2-8
-
A copy of the example (echo.lua):
-- load namespace
local socket = require("socket")
-- create a TCP socket and bind it to the local host, at any port
local server = assert(socket.bind("*", 0))
-- find out which port the OS chose for us
local ip, port = server:getsockname()
-- print a message informing what's up
print("Please telnet to localhost on port " .. port)
print("After connecting, you have 10s to enter a line to be echoed")
-- loop forever waiting for clients
while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. "\n") end
-- done with client, close the object
client:close()
end
** Affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1441914
Title:
lua:socket settimeout does not work
Status in unity package in Ubuntu:
New
Bug description:
Ubuntu Version: Ubuntu 14.04.2 LTS
package lua-socket:i386 3.0~rc1-3
On Ubuntu 14.04, lua socket settimeout does not work as expected. On a tcp
socket, it causes the next receive to close the connection immediately.
It works correctly on Ubuntu 12.04 and debian 7.
To reproduce:
install packages lua5.1 and lua-socket
Take the echo server example from the introduction to luasocket:
http://w3.impa.br/~diego/software/luasocket/introduction.html
Put it in a file echo.lua and run it with "lua echo.lua"
From another window, use telnet localhost {port} to connect to the echo server
Result: Immediately after connecting, the server closes the connection.
Expected Result: The server should wait 10 seconds for input, then close the
connection.
package version that works correctly in debian 7: lua-socket:i386 2.0.2-8
-
A copy of the example (echo.lua):
-- load namespace
local socket = require("socket")
-- create a TCP socket and bind it to the local host, at any port
local server = assert(socket.bind("*", 0))
-- find out which port the OS chose for us
local ip, port = server:getsockname()
-- print a message informing what's up
print("Please telnet to localhost on port " .. port)
print("After connecting, you have 10s to enter a line to be echoed")
-- loop forever waiting for clients
while 1 do
-- wait for a connection from any client
local client = server:accept()
-- make sure we don't block waiting for this client's line
client:settimeout(10)
-- receive the line
local line, err = client:receive()
-- if there was no error, send it back to the client
if not err then client:send(line .. "\n") end
-- done with client, close the object
client:close()
end
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441914/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363630] Re: Since revision 446.1.3, Zenity backend is broken
OK - so I was able to add the proposed item to my .list file, but 1) the sudo apt-get upgrade -s listed a boatload of items (so I guess there is an issue with the /etc/apt/preferences.d/proposed-updates file I created and 2) even if that file was correct, I'm clueless as to how to install this patch to test it... A little help, please... Tom -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, &error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to "exit_status != 0". Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as "OK" buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select "Shutdown" from indicator-session menu. * In the popped up dialog select "Cancel". Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1437652] Re: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore
** No longer affects: ubuntuphone -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1437652 Title: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: If the bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate it still will be the same after entering and subsequent leaving the air plane mode. contrariwise: The bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate, in the next step we will enter air plain mode and shut down the phone. After boot up we will deactivate the air plane mode, then mobile radio and bluetooth is activated even if bluetooth was deactivated before entering the air plane mode. If bluetooth was deactivated before entering the air plane mode is should also be deactivated after leaving the air plane mode even if the telephone was shut down meanwhile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1437652/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1437652] Re: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore
** Changed in: ubuntuphone Status: Confirmed => Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1437652 Title: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore Status in Usability Bugs in Ubuntu Phone: Invalid Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: If the bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate it still will be the same after entering and subsequent leaving the air plane mode. contrariwise: The bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate, in the next step we will enter air plain mode and shut down the phone. After boot up we will deactivate the air plane mode, then mobile radio and bluetooth is activated even if bluetooth was deactivated before entering the air plane mode. If bluetooth was deactivated before entering the air plane mode is should also be deactivated after leaving the air plane mode even if the telephone was shut down meanwhile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1437652/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441819] Re: The unity sound settings is a bit cluttered
** Package changed: unity (Ubuntu) => indicator-sound (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1441819 Title: The unity sound settings is a bit cluttered Status in indicator-sound package in Ubuntu: Confirmed Bug description: The best is to view the added screen-shot, in the attachmentst, and my proposed 'fix'. This is an revised image of the one in the attachment: http://i.stack.imgur.com/o0Jd1.png Please ignore the one in the attachments, its slightly off, of what I meant ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .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.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 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: Wed Apr 8 21:12:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2015-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=e4df7d74-dffc-4deb-9ea1-b7653d90c4c6 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 8 19:32:08 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1441819/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1437652] Re: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore
I want to describe the bug myself: I have bluetooth disable. I enable Airplane mode. I disable Airplane mode. And in the next 2-3 seconds I see a little color changing in bluetooth indicators like something have been changed: and if I click bluetooth indicator i found bluetooth activated, inspite of the thing that I dont use bluetooth at all. Please ask me any question if this could help. I have Terminal and Logviwer installed if this could help you in solving this bug ** Changed in: ubuntuphone Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1437652 Title: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore Status in Usability Bugs in Ubuntu Phone: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: If the bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate it still will be the same after entering and subsequent leaving the air plane mode. contrariwise: The bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate, in the next step we will enter air plain mode and shut down the phone. After boot up we will deactivate the air plane mode, then mobile radio and bluetooth is activated even if bluetooth was deactivated before entering the air plane mode. If bluetooth was deactivated before entering the air plane mode is should also be deactivated after leaving the air plane mode even if the telephone was shut down meanwhile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1437652/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1437652] Re: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1437652 Title: Bluetooth is enabled after leaving air plane mode even if it was deaktivated bevore Status in Usability Bugs in Ubuntu Phone: Confirmed Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: If the bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate it still will be the same after entering and subsequent leaving the air plane mode. contrariwise: The bq Ubuntu Phone is running and mobile radio is activated while bluetooth is deactivate, in the next step we will enter air plain mode and shut down the phone. After boot up we will deactivate the air plane mode, then mobile radio and bluetooth is activated even if bluetooth was deactivated before entering the air plane mode. If bluetooth was deactivated before entering the air plane mode is should also be deactivated after leaving the air plane mode even if the telephone was shut down meanwhile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1437652/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441819] Re: The unity sound settings is a bit cluttered
** Description changed: - The best is to view the added screen-sho, in the attachmentst, and my + The best is to view the added screen-shot, in the attachmentst, and my proposed 'fix'. - alternatively one can view: http://i.stack.imgur.com/dYUcG.png + This is an revised image of the one in the attachment: + http://i.stack.imgur.com/o0Jd1.png + + Please ignore the one in the attachments, its slightly off, of what I + meant ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .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.113 Mon Dec 1 21:08:13 PST 2014 - GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 + GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: - + ApportVersion: 2.14.1-0ubuntu3.8 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: Wed Apr 8 21:12:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: - bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed - nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed - nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed - vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed + bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed + nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed + nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed + vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:124d] -Subsystem: ASUSTeK Computer Inc. Device [1043:124d] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:124d] + Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2015-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=e4df7d74-dffc-4deb-9ea1-b7653d90c4c6 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 8 19:32:08 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: - NVIDIA(0): Failed to initiate mode change. - NVIDIA(0): Failed to complete mode change + NVIDIA(0): Failed to initiate mode change. + NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - product id 927 - vendor LGD + product id 927 + vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu
[Dx-packages] [Bug 1441819] Re: The unity sound settings is a bit cluttered
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441819 Title: The unity sound settings is a bit cluttered Status in unity package in Ubuntu: Confirmed Bug description: The best is to view the added screen-sho, in the attachmentst, and my proposed 'fix'. alternatively one can view: http://i.stack.imgur.com/dYUcG.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .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.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 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: Wed Apr 8 21:12:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2015-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=e4df7d74-dffc-4deb-9ea1-b7653d90c4c6 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 8 19:32:08 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441819/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441819] [NEW] The unity sound settings is a bit cluttered
Public bug reported: The best is to view the added screen-sho, in the attachmentst, and my proposed 'fix'. alternatively one can view: http://i.stack.imgur.com/dYUcG.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .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.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 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: Wed Apr 8 21:12:36 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-uvm, 331.113, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.26, 3.16.0-33-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:124d] Subsystem: ASUSTeK Computer Inc. Device [1043:124d] InstallationDate: Installed on 2015-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X550CC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic root=UUID=e4df7d74-dffc-4deb-9ea1-b7653d90c4c6 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 8 19:32:08 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 927 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages trusty ubuntu ** Attachment added: "Proposed sound settings fix" https://bugs.launchpad.net/bugs/1441819/+attachment/4369717/+files/proposed-sound-settings.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441819 Title: The unity sound settings is a bit cluttered Status in unity package in Ubuntu: New Bug description: The best is to view the added screen-sho, in the attachmentst, and my proposed 'fix'. alternatively one can view: http://i.stack.imgur.com/dYUcG.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 NonfreeKernelModules: nvidia .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.113 Mon Dec 1 21:08:13 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.
[Dx-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
The same fix for bug #729979 is used for this bug in Trusty. Since that bug was verified, then I'm marking this bug as verified-done as well. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441751] [NEW] minimizing a maximized window and then restoring it
Public bug reported: To experience the bug do as follows: 1. Maximize a window 2. Click on the minimize button 3. Without selecting another window, click on the icon of the minimized window on the launcher 4. Look at the panel The panel should contain the buttons on the left and windowtitle/appmenu but it doesn't. This bug might be related to the fact, that after minimizing the active window, not other window gets focus. Shouldn't the last active window get the focus? ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441751 Title: minimizing a maximized window and then restoring it Status in unity package in Ubuntu: New Bug description: To experience the bug do as follows: 1. Maximize a window 2. Click on the minimize button 3. Without selecting another window, click on the icon of the minimized window on the launcher 4. Look at the panel The panel should contain the buttons on the left and windowtitle/appmenu but it doesn't. This bug might be related to the fact, that after minimizing the active window, not other window gets focus. Shouldn't the last active window get the focus? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441751/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363630] Re: Since revision 446.1.3, Zenity backend is broken
Hello, Works for me on Ubuntu 14.04 i386. It allows me to cancel Shutdown, Reboot and Close session. FYI, close the session then log in allows this change to take effect. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, &error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to "exit_status != 0". Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as "OK" buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select "Shutdown" from indicator-session menu. * In the popped up dialog select "Cancel". Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1436069] Re: a date in the calendar app is ringing only once
This ticket is partially affected by the fix that just landed for bug #1419001, because indicator-datetime now honors the ical trigger property and there can be multiple reminders for an event. However, I agree -- these notifications are just too easy to miss in their current transient form. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1436069 Title: a date in the calendar app is ringing only once Status in Usability Bugs in Ubuntu Phone: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: A date in the calendar app is ringing only once. Then it disappears... If you are in a noisy environment you will miss the date. The date should ring until it is confirmed. or The LED should flash after the ring tone has stopped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuphone/+bug/1436069/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1440825] Re: dnd_is_screensaver_inhibited no longer works
** Patch removed: "notify-osd_dnd.patch"
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+attachment/4368321/+files/notify-osd_dnd.patch
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1440825
Title:
dnd_is_screensaver_inhibited no longer works
Status in notify-osd package in Ubuntu:
New
Bug description:
Notifications are still shown even if the system inhibits
screensaver(expecting dnd_is_screensaver_inhibited state).
The code seems to expect "GetInhibitors" method is in
"org.gnome.ScreenSaver", but the method is no longer there. The
equivalent is "IsInhibited" method in org.gnome.SessionManager.
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
## unit32:8 = (Inhibit the session being marked as idle)
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
method return sender=:1.24 -> dest=:1.284 reply_serial=2
boolean true
[src/dnd.c]
100 static DBusGProxy*
101 get_screensaver_proxy (void)
102 {
103 if (gsmgr == NULL)
104 {
105 DBusGConnection *connection = dbus_get_connection ();
106 gsmgr = dbus_g_proxy_new_for_name (connection,
107
"org.gnome.ScreenSaver",
108
"/org/gnome/ScreenSaver",
109
"org.gnome.ScreenSaver");
110 }
111
112 return gsmgr;
113 }
114
115 gboolean
116 dnd_is_screensaver_inhibited ()
117 {
118 GError *error = NULL;
119 gboolean inhibited = FALSE;
120 char **list;
121
122 if (! get_screensaver_proxy ())
123 return FALSE;
124
125 if (dbus_g_proxy_call_with_timeout (
126 gsmgr, "GetInhibitors", 2000, &error,
127 G_TYPE_INVALID,
128 G_TYPE_STRV, &list,
129 G_TYPE_INVALID))
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 7 01:49:02 2015
DesktopSession: 'ubuntu'
EcryptfsInUse: Yes
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2015-02-28 (37 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
MachineType: FUJITSU FMVS54KR
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
xserver-xorg 1:7.7+7ubuntu4
libgl1-mesa-glx 10.5.2-0ubuntu1
libdrm2 2.4.59-0ubuntu1
xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
xserver-xorg-video-ati 1:7.5.0-1ubuntu2
SourcePackage: notify-osd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.06
dmi.board.name: FJNB24F
dmi.board.vendor: FUJITSU
dmi.board.version: D2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
dmi.product.name: FMVS54KR
dmi.sys.vendor: FUJITSU
glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1440825] Re: dnd_is_screensaver_inhibited no longer works
** Branch linked: lp:~nobuto/notify-osd/fix_dnd_is_screensaver_inhibited
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1440825
Title:
dnd_is_screensaver_inhibited no longer works
Status in notify-osd package in Ubuntu:
New
Bug description:
Notifications are still shown even if the system inhibits
screensaver(expecting dnd_is_screensaver_inhibited state).
The code seems to expect "GetInhibitors" method is in
"org.gnome.ScreenSaver", but the method is no longer there. The
equivalent is "IsInhibited" method in org.gnome.SessionManager.
https://people.gnome.org/~mccann/gnome-session/docs/gnome-session.html#org.gnome.SessionManager.IsInhibited
## unit32:8 = (Inhibit the session being marked as idle)
$ dbus-send --print-reply --dest=org.gnome.SessionManager
/org/gnome/SessionManager org.gnome.SessionManager.IsInhibited uint32:8
method return sender=:1.24 -> dest=:1.284 reply_serial=2
boolean true
[src/dnd.c]
100 static DBusGProxy*
101 get_screensaver_proxy (void)
102 {
103 if (gsmgr == NULL)
104 {
105 DBusGConnection *connection = dbus_get_connection ();
106 gsmgr = dbus_g_proxy_new_for_name (connection,
107
"org.gnome.ScreenSaver",
108
"/org/gnome/ScreenSaver",
109
"org.gnome.ScreenSaver");
110 }
111
112 return gsmgr;
113 }
114
115 gboolean
116 dnd_is_screensaver_inhibited ()
117 {
118 GError *error = NULL;
119 gboolean inhibited = FALSE;
120 char **list;
121
122 if (! get_screensaver_proxy ())
123 return FALSE;
124
125 if (dbus_g_proxy_call_with_timeout (
126 gsmgr, "GetInhibitors", 2000, &error,
127 G_TYPE_INVALID,
128 G_TYPE_STRV, &list,
129 G_TYPE_INVALID))
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: notify-osd 0.9.35+15.04.20150126-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 7 01:49:02 2015
DesktopSession: 'ubuntu'
EcryptfsInUse: Yes
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2015-02-28 (37 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150228)
MachineType: FUJITSU FMVS54KR
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
xserver-xorg 1:7.7+7ubuntu4
libgl1-mesa-glx 10.5.2-0ubuntu1
libdrm2 2.4.59-0ubuntu1
xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
xserver-xorg-video-ati 1:7.5.0-1ubuntu2
SourcePackage: notify-osd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.06
dmi.board.name: FJNB24F
dmi.board.vendor: FUJITSU
dmi.board.version: D2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.06:bd01/07/2013:svnFUJITSU:pnFMVS54KR:pvr:rvnFUJITSU:rnFJNB24F:rvrD2:cvnFUJITSU:ct10:cvr:
dmi.product.name: FMVS54KR
dmi.sys.vendor: FUJITSU
glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1440825/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1412709] Re: Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme'
** Changed in: notify-osd (Ubuntu) Status: In Progress => Fix Released ** Changed in: telephony-service (Ubuntu) Assignee: Iain Lane (laney) => (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1412709 Title: Error: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme' Status in notify-osd package in Ubuntu: Fix Released Status in notify-osd-icons package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: In Progress Bug description: I am seeing the following warning with notify-osd when changing the volume: loading icon 'notification-notification-audio-volume-medium' caused error: 'Icon 'notification-notification-audio-volume-medium' not present in theme' This happens also when running it manually (as in src/send-test- notification.sh): notify-send "Volume" -i notification-audio-volume-medium -h int:value:75 -h string:x-canonical-private-synchronous: When leaving out the "notification-" prefix there's no error: notify-send "Volume" -i audio-volume-medium -h int:value:75 -h string:x-canonical-private-synchronous: ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.10.20140819-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jan 20 10:41:03 2015 DesktopSession: 'ubuntu' GtkTheme: 'Numix' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2012-05-28 (966 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: LENOVO 42992PG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-44-generic root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.3-0ubuntu0.2 libdrm2 2.4.56-1~ubuntu1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 SourcePackage: notify-osd UpgradeStatus: Upgraded to trusty on 2015-01-17 (2 days ago) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG 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:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1412709/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441700] Re: notification-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1421821 *** https://bugs.launchpad.net/bugs/1421821 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1421821, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1441700/+attachment/4369526/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1441700/+attachment/4369528/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1441700/+attachment/4369530/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1441700/+attachment/4369531/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1441700/+attachment/4369532/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1441700/+attachment/4369533/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1441700/+attachment/4369534/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1421821 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441700 Title: notification-daemon crashed with SIGABRT in g_assertion_message() Status in notification-daemon package in Ubuntu: New Bug description: Happened at login ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: notification-daemon 3.14.1-1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed Apr 8 17:39:36 2015 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-07 (455 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=da PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: notification-daemon StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to vivid on 2015-02-09 (57 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1441700/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441700] [NEW] notification-daemon crashed with SIGABRT in g_assertion_message()
Public bug reported: Happened at login ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: notification-daemon 3.14.1-1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed Apr 8 17:39:36 2015 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-07 (455 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=da PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: notification-daemon StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to vivid on 2015-02-09 (57 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: notification-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441700 Title: notification-daemon crashed with SIGABRT in g_assertion_message() Status in notification-daemon package in Ubuntu: New Bug description: Happened at login ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: notification-daemon 3.14.1-1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed Apr 8 17:39:36 2015 ExecutablePath: /usr/lib/notification-daemon/notification-daemon InstallationDate: Installed on 2014-01-07 (455 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANGUAGE=da PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: notification-daemon StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to vivid on 2015-02-09 (57 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/1441700/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1439236] Re: When minimizing window, the icon from the hidden Launcher doesn't reveal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1439236 Title: When minimizing window, the icon from the hidden Launcher doesn't reveal Status in unity package in Ubuntu: Confirmed Bug description: When the launcher is hidden and one minimizes an application window, the icon of that application shows up for a moment, hinting where is locatad. This doesn't happen after updating to 15.04. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CurrentDesktop: Unity Date: Wed Apr 1 16:33:01 2015 InstallationDate: Installed on 2013-05-03 (697 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-31 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1439236/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441626] [NEW] Opening a Quicklist while in Spread can sometimes render the Quicklist and Launcher unusable
Public bug reported: When opening a Quicklist while in Spread, the Quicklist and Launcher can sometimes be unusable. The Quicklist will be open, but it doesn't accept clicks nor does the Launcher. In order to clear out this condition, I enter keynav mode for the Launcher. ** Affects: unity Importance: Low Status: Confirmed ** Affects: unity (Ubuntu) Importance: Low Status: Confirmed ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New => Confirmed ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Changed in: unity Importance: Undecided => Low ** Changed in: unity (Ubuntu) Importance: Undecided => Low ** Changed in: unity Milestone: None => 7.3.3 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441626 Title: Opening a Quicklist while in Spread can sometimes render the Quicklist and Launcher unusable Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When opening a Quicklist while in Spread, the Quicklist and Launcher can sometimes be unusable. The Quicklist will be open, but it doesn't accept clicks nor does the Launcher. In order to clear out this condition, I enter keynav mode for the Launcher. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1441626/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1412001] Re: alt+backtick doesn't focus on selected one of many windows previously clicked
** Branch linked: lp:~3v1n0/unity/switcher-terminates-spread ** Changed in: unity Assignee: Christopher Townsend (townsend) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Assignee: Christopher Townsend (townsend) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New => Confirmed ** Changed in: unity/7.2 Importance: Undecided => Low ** Changed in: unity/7.2 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity/7.2 Milestone: None => 7.2.5 -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1412001 Title: alt+backtick doesn't focus on selected one of many windows previously clicked Status in Unity: In Progress Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: In Progress Bug description: This a user experience issue and easily reproducible. Open multiple instances of your favorite application. Then click on Unity's icon for the app when you are already focused on one instance of it. This opens up a tile of the instances of the application which you can select from with the mouse. Now while that tile is shown, use ATL+backtick to select the window you want instead of clicking with the mouse. The result is that the tile window doesn't go away. If you use ALT+backtick and switch to ALT+tab (or start from ALT+tab from the start) and select another kind of application, then the tile goes away correctly and the other application comes in the front. I can verify that the window you would select with ALT+backtick does actually get to the top of the view and is marked as the "last visited instance", because if you switch to another application (using ALT+tab) and click back on the group of the original application you would see the one you previously selected with ALT+backtick. --- Here are step-by-step instructions. - Open a couple of terminals - Open firefox - Click on the terminal icon * This should open a tile showing the various terminal windows you have open * If that doesn't happen, click again (you were not on a terminal window before) - Use ALT+backtick to select one of the terminal windows Expected behavior: The tile of terminals goes away and the selected terminal is focused Observed behavior: The tile of terminals stays on the screen ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,place,grid,mousepoll,compiztoolbox,vpswitch,regex,gnomecompat,imgpng,snap,move,unitymtgrabhandles,resize,session,wall,animation,workarounds,fade,expo,scale,ezoom,unityshell] CurrentDesktop: Unity Date: Sat Jan 17 16:32:05 2015 ExecutablePath: /usr/bin/compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-01 (76 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1412001/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363630] Re: Since revision 446.1.3, Zenity backend is broken
@ Dmitry Shachnev, I performed verification testing and all is fine with one minor caveat. An initial restart is required before the change takes effect, so should we add a "System restart required" warning after 'indicator-session' upgrades? Otherwise all is fine, and I also cross-tested with the shutdown and restart buttons displayed by the main menu button. So other than the above mentioned caveat this could be marked verification-done. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, &error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to "exit_status != 0". Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as "OK" buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select "Shutdown" from indicator-session menu. * In the popped up dialog select "Cancel". Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441487] Re: Running any Java program produces messages in the terminal
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441487 Title: Running any Java program produces messages in the terminal Status in unity package in Ubuntu: Confirmed Bug description: I just installed Ubuntu 15.04 and was surprised to discover that when running a Java based program from the terminal in Unity, the following message appears: "Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar". I tried several programs and it is all the same. Some Java programs with enabled Java security produce even some error messages and crash. If I press Ctrl+Alt+F1 to start a new terminal session without a GUI and run a Java program (without a GUI), I don't experience this problem. Back in Unity, if I unset JAVA_TOOL_OPTIONS in the terminal and run a Java program, it works fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 10:11:10 2015 InstallationDate: Installed on 2015-03-30 (9 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441487/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441592] [NEW] Unity restart broken (Vivid)
Public bug reported: Restarting Unity no longer works properly in Ubuntu 15.04 Vivid Vervet. Steps to reproduce: press ALT + F2, type Unity and press ENTER. What should occur: Unity should be restarted without logging out the user. What actually occurs: the LightDM login screen greeter shows up (so the user is logged out) instead of just restarting Unity. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 14:50:13 2015 InstallationDate: Installed on 2015-03-11 (28 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441592 Title: Unity restart broken (Vivid) Status in unity package in Ubuntu: New Bug description: Restarting Unity no longer works properly in Ubuntu 15.04 Vivid Vervet. Steps to reproduce: press ALT + F2, type Unity and press ENTER. What should occur: Unity should be restarted without logging out the user. What actually occurs: the LightDM login screen greeter shows up (so the user is logged out) instead of just restarting Unity. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 14:50:13 2015 InstallationDate: Installed on 2015-03-11 (28 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441592/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 935750] Re: [dash] Search field not common to lenses
Marking as won't fix because this bug is assigned to the Unity8 project where it is not relevant. ** Changed in: ubuntu-ux Status: Triaged => Won't Fix ** Changed in: ubuntu-ux Importance: Medium => Undecided -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/935750 Title: [dash] Search field not common to lenses Status in Ubuntu UX bugs: Won't Fix Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: After typing in the home lens's search field and seeing no results, I figured I was using the wrong lens so I switched to another one. Because the search field is specific to the lens, I had to retype my search terms. I didn't realize until I started this report that the home lens search would search all the lenses. (Or, I'm assuming that's what it does now, based on a different search which produced results.) - UPDATE: This is a bug for the desktop, Unity7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/935750/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1367818] Re: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state.
** Changed in: ubuntu-ux Assignee: Matthew Paul Thomas (mpt) => Paty Davila (dizzypaty) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1367818 Title: [indicator] + [dialog] Silent Mode causes no indication of a change in [icon] state. Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Bug description: - "When the sound is muted, the volume icon to the left of the volume slider should have a red "/" running through it." - "Add an explicit "Mute" button to the sound indicator menu." - "Pressing and holding the icon to the left of the volume slider should mute volume straight away." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1367818/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1080107] Re: auto log-in doesn't function after logout
Bug 1396824 "X server crash from autologin session returns to greeter, not autologin session" is related. If the VNC server should survive a login or a logout it needs to run as root. Solutions are shown on http://askubuntu.com/questions/229989/how- to-setup-x11vnc-to-access-with-graphical-login-screen/528469#528469 and on http://wiki.ubuntuusers.de/VNC#x11vnc . -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1080107 Title: auto log-in doesn't function after logout Status in Light Display Manager: Incomplete Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Enabling auto log-in for a user causes a ubuntu unity session to be started when the operating system is booted. The session has a "Log Out..." item on the pull-down menu item in the upper right corner. When this command is used, the session is logged out, but there is no subsequent auto log-in. Consequently, remote access by VNC (vinagre/vino) ceases. This problem has been around for several releases, but is definately present for the one below: lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1080107/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363630] Re: Since revision 446.1.3, Zenity backend is broken
** Branch linked: lp:ubuntu/trusty-proposed/indicator-session -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, &error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to "exit_status != 0". Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as "OK" buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select "Shutdown" from indicator-session menu. * In the popped up dialog select "Cancel". Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
** Branch linked: lp:ubuntu/trusty-proposed/compiz -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1419001] Re: Reminders trigger at the time of the event and not before by default
This bug was fixed in the package indicator-datetime - 13.10.0+15.04.20150406-0ubuntu1 --- indicator-datetime (13.10.0+15.04.20150406-0ubuntu1) vivid; urgency=medium [ Charles Kerr ] * Improve valarm support to honor calendar events' valarm triggers. (LP: #1419001) -- CI Train BotMon, 06 Apr 2015 23:35:46 + ** Changed in: indicator-datetime (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1419001 Title: Reminders trigger at the time of the event and not before by default Status in the base for Ubuntu mobile products: Confirmed Status in Calendar application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: Fix Released Status in qtorganizer5-eds package in Ubuntu: Invalid Bug description: Sync of google calendar. The Google calendar setting is set by default to notify 10 min prior to all meetings. Is it possible to get this default notification time from google with the sync? or can we add a setting for a default notification time in the calendar app? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1419001/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363630] Re: Since revision 446.1.3, Zenity backend is broken
Hello Dmitry, or anyone else affected, Accepted indicator-session into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/indicator- session/12.10.5+14.04.20150404-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: indicator-session (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363630 Title: Since revision 446.1.3, Zenity backend is broken Status in Ubuntu GNOME Flashback: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Committed Bug description: Currently the code in zenity_question() looks like: if (!g_spawn_check_exit_status (exit_status, &error)) confirmed = TRUE; else confirmed = exit_status == 0; However !g_spawn_check_exit_status() call is mostly equivalent to "exit_status != 0". Thus, confirmed will be *always* set to TRUE, even if the user cancelled the dialog. I have prepared a branch to fix this. == Impact == The Cancel buttons in shutdown/end session dialogs are not working, and do the same as "OK" buttons. This may lead to data loss due to unsaved documents/etc. == Test Case == * Log in to GNOME Flashback session. * Select "Shutdown" from indicator-session menu. * In the popped up dialog select "Cancel". Expected result: the dialog will close, the machine won't shut down. == Development / Stable Fix == Please see the attached branches. == Regression Potential == The fix is part of 14.10 release and was confirmed to work fine. So no regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome-flashback/+bug/1363630/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1072206] Re: [nvidia] Window content is black or transparent
Hello ZeXx86, or anyone else affected, Accepted compiz into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/compiz/1:0.9.11.3+14.04.20150313-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: compiz (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1072206 Title: [nvidia] Window content is black or transparent Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in NVIDIA Drivers Ubuntu: Invalid Status in Unity: Invalid Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Trusty: Fix Committed Bug description: [ Impact ] With nVidia hardware from time to time window content is rendered black or transparent. The problem manifests more frequently as session uptime increases. Apparently the problem was caused by textures being cached and not freed, resulting in memory exhaustion conditions. It turns out the texture caching is unnecessary anyway. [ Test Case ] Verification requires an nVidia GPU with proprietary drivers. The problem can not be reproduced at will, only after some time (depending on resident GPU memory and usage) and even then only randomly and unreliably. [ Regression Potential ] It is unlikely this change has the potential to introduce new regressions. [ Other Info ] Fix was cherry-picked from the Ubuntu "Vivid Vervet" dev relase where it has been in use for some weeks without problem. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1072206/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 955193] Re: Menu bar - add option for the global menu to make it always visible
Hello John, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/955193 Title: Menu bar - add option for the global menu to make it always visible Status in Ayatana Design: Triaged Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [ Impact ] [Test Case] (1) enable menus in the window title bar System Settings > Appearance > Behavior > Show the menus for a window > In the menu bar (2) run "gsettings set com.canonical.Unity always-show-menus true" in a terminal (3) move the mouse around between windows The menus should remain displayed [Regression Potential] Any change to the menu functionality has the potential to cause volunteer functionality in menu behaviour. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time with no apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/955193/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 860970] Re: Dash called with super key above fullscreen app is not interactive or does not show up at all.
Hello Aurélien, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/860970 Title: Dash called with super key above fullscreen app is not interactive or does not show up at all. Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Precise: Triaged Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] The Dash was rendered underneath fullscreen windows so it was invisible, although it grabs keyboard input. [TEST CASE] - Launch an application in fullscreen (Firefox, Totem). - Hit the Super key to call the dash. - The Dash should appear. - Keyboard input should be directed to the Dash. - Clicking anywhere on the full screen application should close the Dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/860970/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1312137] Re: Local menus broken for Qt apps after opening dialog
Hello CraigD, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1312137 Title: Local menus broken for Qt apps after opening dialog Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] I have selected to have window menus in the window's title bar. This works great, except for Qt apps. After selecting a menu item in a Qt app that produces a dialog, the menu is no longer accessible. The only way to get the menu back, is to switch to another window, and then back to the affected app. [Test Case] 1. Start qtcreator 2. Resize window so that it is not maximised 3. Select 'Help' -> 'About Qt Creator' 4. Dismiss 'About Qt Creator' dialog 5. Move mouse over window titlebar. [Regression Potential] It's possible other menu interaction bugs may have been introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry-picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312137/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363534] Re: Wrong keyboard shortcuts for Workspaces in Dash overlay
Hello Mario, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1363534 Title: Wrong keyboard shortcuts for Workspaces in Dash overlay Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] The Shortcuts displays the wrong key sequence for switching workspaces. [Test Case] (1) Enable workspaces (System Settings > Appearance > Behavior > Enable Workspaces). (2) Hold down the Super key until the Shortcuts window appears. (3) Under Workspaces it should display "Shift + Ctrl + Alt + Arrow Keys" and not "Shift + Ctrl + Alt + Left + Arrow Keys". [Regression Potential] Unlikely. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu "Vivi Vervet" dev release where it has been in production use for some time without regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1363534/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1302955] Re: upstart user session leaks all the dbus events it receives
Hello Michael, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1302955 Title: upstart user session leaks all the dbus events it receives Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in unity source package in Trusty: Fix Committed Bug description: [Impact] The unity-panel-service process has been caching D-Bus messages sent from upstart, effectively leaking memory. The solution replaces the offending code with a single upstart event emission. [Test Case] 0. Make sure there is a user session job with a dbus rule (eg unity-greeter-session-broadcast) 1. Install and run system-load-indicator (indicator-multiload) 2. Set the update interval to 100ms 3. Now watch the memory use of init --user increase by 100kb per second 4. Also open up upstart-monitor to see all the dbus messages being sent [Regression Potential] Some kind of hidden functionality depending on upstart events sent through D-Bus to the unity-panel-service may have become disconnected. Unlikely. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in regular use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1302955/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1374942] Re: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog
Hello Michael, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1374942 Title: compiz crashed with signal 5 in _XReply() from unity::decoration::ForceQuitDialog::ForceQuitDialog Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] An invalid line of code would occasionally cause Unity to crash. [Test Case] (1) Download and run the attached Python script test-1374942 to create a candidate application. (2) Press the close button and wait for the Force Quit dialog to come up. (3) Choose the "Force Quit" button. The desktop shell should not crash. [Regression Potential] The fix for this bug involves converting an integer into a string and appending it to an error message instead of adding the integer value to the address of the error message. There is unlikely to be a regression from this. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been under daily use for some time without apparent regressioon. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1374942/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1390562] Re: Moving the mouse out from the decoration hides the LIMs when Alt is pressed
Hello Marco, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390562 Title: Moving the mouse out from the decoration hides the LIMs when Alt is pressed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Pressing the Alt key while a locally integrated menu is open causes the menu to hide. [Test Case] Prerequisite: from Appearance -> Behavior -> Set menu visible in window titlebar 1. Open a window with menus 2. Press and keep pressed the Alt key 3. Menus will show 4. Move the mouse over the window decoration 5. Move the mouse out from the window decoration Incorrect behavior: 6. Menus hides, also if the Alt key is pressed. Expected: 6. Menus should stay visible until the Alt key is released. [Regression Potential] Additional incorrect menu behaviour may be introduced. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1390562/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1398287] Re: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen
Hello Franz, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1398287 Title: Unity 14.04 Lock button sometimes takes 30~60s to enter lock screen Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] When the power button is pressed, the shutdown dialog will be displayed. Then clicks the 'Lock' button in the shutdown dialog and it sometimes takes about 30~60s to lock screen. This happens on many Intel-only platforms. PS: If user moves the cursor out of the dialog window after clicking the 'Lock' button, it will switch to lock screen immediately. [Test Case] See description under "Impact' above. [Regression Potential] The fix for this problem involves releasing the grab on the input devices earlier in the sequence, allowing the animation sequence to begin immediately without a grab-release timeout. It is unlikely that this could introduce any regressions. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu "Vivid Vervet" dev release where it has been in test for some time without incident. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1398287/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1401911] Re: When the screen is locked edge barriers should be deactivated.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1401911 Title: When the screen is locked edge barriers should be deactivated. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] If the screen is locked, launcher/panel edge barriers at the moment are active. [Test Case] In a multi-monitor environment, lock the screen and move the mouse between monitors. There should be no "sticky" edge between the monitors. [Regression Potential] Code in the paths that handle the edge barriers was changed. Potentially this could impact the reveal of a hidden Launcher if there were errors introduced in these code paths. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1401911/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
Hello Jennifer, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1410582 Title: [Trusty / Unity] Desktop got unlocked on its own. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Certain code paths may cause the Unity lockscreen to crash, which can allow the screen to be unlocked without a password entry. [Test Case] Unfortunately this bug only appears under certain race conditions and is not reliably reproduce able. [Regression Potential] The change in the code simply assumes that if a screen is already locked, then it is lockable this avoiding certain operations that are inherently racy. It is possible that this fix does not avoid all possible crash conditions in the lockscreen and there may still be unaccounted-for crashes in the lockscreen. [Other Info] This fix was cherry picked for Ubuntu 14.04 LTS from the Ubuntu "Vivid Vervet" dev release where it has been in testing for some time. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1410582/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1413773] Re: [Regressions] Dash dnd icons rendered behind dash.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413773 Title: [Regressions] Dash dnd icons rendered behind dash. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Dragged icons are rendered behind dash. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413773/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413790 Title: It's possible to bypasss lockscreen if user is in nopasswdlogin group. Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] A user is presented with a password dialog even if a member of the nopasswdlogin group (and may not have a password). [TEST CASE] (1) Create a test user. (2) Add the test user to the nopasswdlogin group. (3) Log in to a Unity session using that acocunt. (4) Lock the screen. (5) Attempt to unlock the screen: no password prompt should be presented. [REGRESSION POTENTIAL] Conceivably allowing a login with no authentication could present unexpected vulnerabilities in which unforseen code paths also exercise this function. Care has been taken by the developer to avoid such cases. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413790/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1404486] Re: Session dialog does not show up over fullscreen windows.
Hello Andrea, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1404486 Title: Session dialog does not show up over fullscreen windows. Status in Unity: Triaged Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Unity session dialog does not show up over a fullscreen window if you press the hardware button. [TEST CASE] (1) open an application (eg. Firefix) and make it fullscreen (F11) (2) press the power button or choose Shut Down... from the Session indicator menu. (3) The Session (shutdown/restart) dialog should appear and be interactive. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1404486/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1413411] Re: underscore in mounted drive name mishandled in menu
Hello Carl, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1413411 Title: underscore in mounted drive name mishandled in menu Status in One Hundred Papercuts: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] If you have a mounted drive with an underscore in it's name (e.g. host_S), then, when you right-click on the drive icon in the sidebar, the menu interprets the underscore as a keyboard-shortcut indicator, so shows the name as hostS (with S underlined). Hovering over the drive results in the correct "host_S" name; the bug is only in the right-click menu. Note that right-clicking on the "Files" icon will show a menu that includes the correct mounted disk names. It is only right-clicking on the drive-icons themselves that shows the incorrect name. [Test Case] (1) Create a mountable device with an underscore in its volume name (eg. host_S). (2) Right click on the icon for tha drive in the Launcher. It should display the underscore character correctly as a part of the drive name, and not as an underline. [Regression Potential] None. [Other Info] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1413411/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1066157] Re: dash +orca does not speak the names of application icons
Hello Alan, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1066157 Title: dash +orca does not speak the names of application icons Status in OEM Priority Project: New Status in Unity: Fix Released Status in Unity 5.0 series: New Status in Unity 6.0 series: Won't Fix Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] Screen reader support for dynamic content in the Dash is enabled. [Test Case] (1) Enable Screen Reader (System Settings > Universal Access > Screen Reader) (2) Press Super + A to bring up the Applications lens of the Dash (3) Navigate displayed content (4) Choose an application for preview (5) Press Esc until the Dash is closed, repeat steps 2 to 4 You should hear the application description and preview description. [Regression Potential] Some new code deals with processing pointers: the usual problem potential of dealing with pointers in C code applies. [Other Info] This patch for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in public use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1066157/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1159249] Re: HUD does not show up over fullscreen window
Hello Ben, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1159249 Title: HUD does not show up over fullscreen window Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [Impact] The HUD was not being rendered above fullscreen windows although it would grab the keyboard. [TEST CASE] 1. Open some site in firefox 2. Go to fullscreen mode (F11) 3. Press "Alt" once. 4 The HUD should appear and you should be able to interact with it. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1159249/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1241757] Re: Unity Launcher always assumes default background is active for a couple of seconds
Hello Sadi, or anyone else affected, Accepted unity into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/unity/7.2.4+14.04.20150316-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: unity (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1241757 Title: Unity Launcher always assumes default background is active for a couple of seconds Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Committed Bug description: [IMPACT] Every time the computer boots and autologins to my desktop, I see the default background only behind the Unity Launcher for a couple of seconds, and then it is replaced with the current wallpaper. [TEST CASE] (1) Configure the desktop to use a non-default wallpaper. (2) Log in to a Unity session and observe the area behind the Launcher. [REGRESSION POTENTIAL] The solution to this problem was to eliminate the animation of the BFB icon on initial startup. Potentially this could cause the animation to not run at other times, although even if this did occur, it is unlikely to be noticed. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1241757/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1441487] [NEW] Running any Java program produces messages in the terminal
Public bug reported: I just installed Ubuntu 15.04 and was surprised to discover that when running a Java based program from the terminal in Unity, the following message appears: "Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar". I tried several programs and it is all the same. Some Java programs with enabled Java security produce even some error messages and crash. If I press Ctrl+Alt+F1 to start a new terminal session without a GUI and run a Java program (without a GUI), I don't experience this problem. Back in Unity, if I unset JAVA_TOOL_OPTIONS in the terminal and run a Java program, it works fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 10:11:10 2015 InstallationDate: Installed on 2015-03-30 (9 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1441487 Title: Running any Java program produces messages in the terminal Status in unity package in Ubuntu: New Bug description: I just installed Ubuntu 15.04 and was surprised to discover that when running a Java based program from the terminal in Unity, the following message appears: "Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar". I tried several programs and it is all the same. Some Java programs with enabled Java security produce even some error messages and crash. If I press Ctrl+Alt+F1 to start a new terminal session without a GUI and run a Java program (without a GUI), I don't experience this problem. Back in Unity, if I unset JAVA_TOOL_OPTIONS in the terminal and run a Java program, it works fine. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Apr 8 10:11:10 2015 InstallationDate: Installed on 2015-03-30 (9 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1441487/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
