[Dx-packages] [Bug 1209106] Re: system tray icon is next to launcher
** Branch linked: lp:ubuntu/vivid-proposed/appmenu-qt5 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1209106 Title: system tray icon is next to launcher Status in Application menu for Qt5: In Progress Status in Qt: New Status in Qt StatusNotifierItem plugin: Confirmed Status in appmenu-qt5 package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Confirmed Bug description: The system tray icon is next to the launcher in the latest verion of Qt Creator. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1209106/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
@r0lf this is still happening in 14.10/Utopic should it be reopened there? -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1362341] Re: OneTime alarms are not automatically dismissed or delete after they are triggered
Fix committed into lp:ubuntu-clock-app at revision 188, scheduled for release in ubuntu-clock-app, milestone ota-1 ** Changed in: ubuntu-clock-app Status: In Progress = Fix Committed -- 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/1362341 Title: OneTime alarms are not automatically dismissed or delete after they are triggered Status in the base for Ubuntu mobile products: Fix Released Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Committed Status in indicator-datetime package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: New Status in indicator-datetime package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce: 1. Create a one time alarm to ring in a few minutes 2. Let the alarm ring 3. Dismiss the alarm What happens: The OneTime alarm is still shown as enabled and as a result shows the wrong status in the clock app. The alarm is no longer shown in the indicator-datetime. What should happen: The OneTime alarm is either disabled or deleted from the alarm model. The clock app cannot disable the alarm since most likely the clock app is not even open at the time the alarm is triggered. Since the alarm is no longer shown in the indicator-datetime, my intuition tells me that indicator-datetime and EDS did its job. Its now up to the SDK Alarms API to update the alarm model correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362341/+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 864478] Re: Window shading is broken
** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/864478 Title: Window shading is broken Status in Compiz: Fix Released Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Shading a window results in an invisible frame and rendering artefacts. Also, shading doesn't happen reliably (eg, pressing the keybinding will not shade some windows) Testcase edit /apps/gwd/titlebar_action to 'shade' scroll up on a window titlebar The window should not disappear To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/864478/+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 1075792] Re: Slow Unity 3D performance in 12.10 Quantal Quetzal
@micheleolivo The video is marked as private -- 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/1075792 Title: Slow Unity 3D performance in 12.10 Quantal Quetzal Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: My ThinkPad T43 works quite well with Ubuntu 12.04, but with a clean install of 12.10, Unity is slow (I can type in the Unity Dash Home and then count the seconds as my letters slowly appear in sequence), sometimes freezes (when I close an application, the icon becomes faded in the Dash but doesn't disappear, and the application window just stays on the screen but I can't interact with it), and text develops little lines through it after suspend and resume (this was also present in 12.04 and can be fixed with a modification to the xorg.conf... something about debug-wait... but it would be nice if I didn't have to make that change on the whole batch of T43's I'm going to sell). Help appreciated :-) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Tue Nov 6 18:10:30 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: IBM Device [1014:0582] Subsystem: IBM Device [1014:0582] InstallationDate: Installed on 2012-11-06 (0 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 1871W5G MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-18-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2007 dmi.bios.vendor: IBM dmi.bios.version: 70ET69WW (1.29 ) dmi.board.name: 1871W5G dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr70ET69WW(1.29):bd05/29/2007:svnIBM:pn1871W5G:pvrThinkPadT43:rvnIBM:rn1871W5G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 1871W5G dmi.product.version: ThinkPad T43 dmi.sys.vendor: IBM version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1075792/+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 963470] Re: [regression] Unity 5.8+Compiz 0.9.7.2: Pressing Super+Tab or Super+W works, but unity does not respond to when Super is released.
** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: unity (Ubuntu Precise) Status: New = Invalid -- 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/963470 Title: [regression] Unity 5.8+Compiz 0.9.7.2: Pressing Super+Tab or Super+W works, but unity does not respond to when Super is released. Status in Compiz Core: Fix Released Status in Unity: Fix Released Status in compiz package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in compiz source package in Precise: Fix Released Status in unity source package in Precise: Invalid Bug description: After upgrading to Unity 5.8, few minutes the Super + Tab does not work as intended. Expected Behaviour: Press Super+Tab and if you keep pressing Tab you can switch between applications. On releasing Super the currently selected application will be focused or opened. What actually happens: Press Super+Tab and if you keep pressing Tab you will see the switching happens (the white border keeps moving)..but then when you release the Super button, the white border is shown on the application but the application is not focussed or opened. The Launcher also now does not autohide. You have to switch workspace for the launcher to autohide. Attached a video screencast showing the behaviour. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 1.95-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,regex,imgpng,place,gnomecompat,grid,obs,mousepoll,snap,commands,move,resize,wall,session,animation,expo,workarounds,fade,ezoom,scale,unityshell] Date: Fri Mar 23 22:00:59 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120116.2) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/963470/+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 1027806] Re: Clicking home folder doesnt take there
This appears to me to just be called Files. Do you still see it as home folder? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1027806 Title: Clicking home folder doesnt take there Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: a) Click on the home folder from the side bar , it opens the home folder b) Browse through the some other folder (away from home) c) Click on the home folder from the side bar again , it activates the open folder window which is not home folder. Essentialy home folder is a misnormer. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1027806/+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 881106] Re: compiz crashed with SIGSEGV in nux::ROPropertystd::string::operator std::string()
** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/881106 Title: compiz crashed with SIGSEGV in nux::ROPropertystd::string::operator std::string() Status in Nux: Fix Released Status in Unity: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Opened the dashboard, started typing a search string, everything froze, then this crash. Happened twice in a row. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: libnux-1.0-0 1.14.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Mon Oct 24 14:11:22 2011 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz Signal: 11 SourcePackage: nux StacktraceTop: nux::ROPropertystd::string::operator std::string() const () from /usr/lib/compiz/libunityshell.so unity::dash::ResultViewGrid::OnOnKeyNavFocusChange(nux::Area*) () from /usr/lib/compiz/libunityshell.so sigc::internal::slot_call1sigc::bound_mem_functor1void, unity::dash::ResultViewGrid, nux::Area*, void, nux::Area*::call_it(sigc::internal::slot_rep*, nux::Area* const) () from /usr/lib/compiz/libunityshell.so sigc::internal::signal_emit1void, nux::Area*, sigc::nil::emit(sigc::internal::signal_impl*, nux::Area* const) () from /usr/lib/libnux-1.0.so.0 nux::WindowCompositor::SetKeyFocusArea(nux::InputArea*) () from /usr/lib/libnux-1.0.so.0 Title: compiz crashed with SIGSEGV in nux::ROPropertystd::string::operator std::string() UpgradeStatus: Upgraded to oneiric on 2011-10-16 (8 days ago) UserGroups: adm admin audio avahi avahi-autoipd bluetooth cdrom dialout dip fax freevo fuse lpadmin mysql mythtv netdev plugdev powerdev sambashare scanner vboxusers video voice wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/881106/+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 1175034] Re: I also have windows that move to the top of the screen when I change a window. I use 12.04
*** This bug is a duplicate of bug 942518 *** https://bugs.launchpad.net/bugs/942518 There's no need to open a new one bug if there is already one open. You can just mark it as affecting you at the top. Thanks! ** This bug has been marked a duplicate of bug 942518 terminal windows move to top of screen after switching workspaces -- 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/1175034 Title: I also have windows that move to the top of the screen when I change a window. I use 12.04 Status in Unity: New Status in unity package in Ubuntu: New Bug description: This bug appears already as #942518. My expertise in Ubuntu is limited. I have had aggravations ever since switching from 10.04 to 12.04. For future changes, I would vote for less artistry and more stable behavior. Description: Ubuntu 12.04.2 LTS Release: 12.04 My window system is GNOME Nautilus 3.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1175034/+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.
@Andrea, considering that this is a potential security bug where a
ubuntu desktop gets unlocked on its own, wouldn't it be recommended to
issue an update asap instead of with the next SRU?
--
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 Committed
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
Fix Released
Bug description:
I have a user reporting an incidence that trusty unity desktop got
unlocked on its own:
In the morning, after coming to my desk, I just pressed the space bar
on my desktop to get the monitors woken up. The monitors came up with
the locked screen and then after a while it got unlocked to my
surprise!
There was compiz crash file on his system at that time. However, I
don't have the right debug symbols to which file (or function) it
crashed into. Here is the top part of the stack trace when I ran
apport-retrace -s on his crash file:
---
--- stack trace ---
#0 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 in g_settings_backend_read (backend=optimized out,
key=key@entry=0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen,
expected_type=0x7ff1877135a0 g_variant_type_info_basic_chars,
default_value=default_value@entry=0) at
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
value = optimized out
#4 0x7ff17f401c7b in g_settings_read_from_backend
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920,
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0)
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
value = optimized out
fixup = optimized out
path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
#5 0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570,
key=0x2087618 disable-lock-screen) at
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c
disable-lock-screen, is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0
g_variant_type_info_basic_chars, minimum = 0x0, maximum = 0x0, default_value
= 0xb9c5b30, ref_count = 0}
value = optimized out
__FUNCTION__ = g_settings_get_value
-
The top part of the trash file when viewed in TextEdit has the information
:
-
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Dec 12 10:16:52 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1405349348
ProcCmdline: compiz
--
His system is Ubuntu trusty 14.04.1 LTS. Unity installed
7.2.3+14.04.20140826-0ubuntu1.0.1 .
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 1407709] Re: Google Maps and Here Maps should handle custom intent:// URLs
ok to land but not a prioirty ** Changed in: canonical-devices-system-image Importance: Undecided = Medium ** Changed in: canonical-devices-system-image Status: New = Confirmed ** Changed in: canonical-devices-system-image Milestone: None = ww05-2015 -- 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/1407709 Title: Google Maps and Here Maps should handle custom intent:// URLs Status in the base for Ubuntu mobile products: Confirmed Status in The Webapps-core project: In Progress Status in Web Browser App: In Progress Status in url-dispatcher package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Status in url-dispatcher package in Ubuntu RTM: In Progress Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: ubuntu-rtm image 184 The maps apps in the system should register and respond to appropriate urls from the browser (not sure of the format, map:// or directions:// - need to check) Steps to reproduce: 1) open browser 2) type Asai Belmont MA in the url bar and press enter 3) this will do a google search for the resturant 4) click on the Directions button Expected result: - One of the maps apps should open displaying directions for the resturant Actual results: - no app is launched To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407709/+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 1393624] Re: Lock screen rejects password on Ubuntu 14.04
Sorry folks, I totally missed both notifications for your questions. @bregma Yes, I have dual monitors. I'll let you know if this also happens with only one monitor attached. @andyrock I will provide this info as soon as I get back home. Note that so far this has only happened on *upgraded* Ubuntu 14.04, not on new installations. -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1393624/+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 1410874] Re: Alarm sounds vs Calendar sounds
** Branch linked: lp:~charlesk/indicator-datetime/rtm-14.09-lp-1410874 -alarm-sounds-vs-calendar-sounds -- 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/1410874 Title: Alarm sounds vs Calendar sounds Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: New Bug description: As discussed with rsalveti and pmcgowan in #phablet on 14 Jan There are two issues in the datetime notification code that need to be changed. 1. Right now we only set role=alarm if the sound is looping; ie if it's an alarm clock event rather than calendar event. Set calendar event role to alert 2. Calendar events shouldn't play in silent mode. We can test for silent mode on the bus, http://bazaar.launchpad.net/~phablet-team /telephony- service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has an example: getUserValue(com.ubuntu.touch.AccountsService.Sound, SilentMode); To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410874/+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 1410874] Re: Alarm sounds vs Calendar sounds
** Branch linked: lp:~charlesk/indicator-datetime/lp-1410874-alarm- sounds-vs-calendar-sounds -- 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/1410874 Title: Alarm sounds vs Calendar sounds Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: In Progress Status in indicator-datetime package in Ubuntu RTM: New Bug description: As discussed with rsalveti and pmcgowan in #phablet on 14 Jan There are two issues in the datetime notification code that need to be changed. 1. Right now we only set role=alarm if the sound is looping; ie if it's an alarm clock event rather than calendar event. Set calendar event role to alert 2. Calendar events shouldn't play in silent mode. We can test for silent mode on the bus, http://bazaar.launchpad.net/~phablet-team /telephony- service/trunk/view/head:/libtelephonyservice/greetercontacts.cpp has an example: getUserValue(com.ubuntu.touch.AccountsService.Sound, SilentMode); To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1410874/+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 1412060] Re: Indicator sound fails to start with Asus Xonar
Booting with a livesession of vivid - get the same. No sound indicator. Pulse is running. -- 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/1412060 Title: Indicator sound fails to start with Asus Xonar Status in indicator-sound package in Ubuntu: New Bug description: Replaced Audigy with Xonar. Clean installed to new drive and partition. sound indicator fails to start upstart --user --startup-event indicator-services-start tries to start indicator - space in indicators shows where it is, clicking and menu doesn't appear ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 17 21:37:27 2015 InstallationDate: Installed on 2015-01-09 (8 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1412060/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
If so we are waiting backport of fix to Trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1291359] Re: multiscreen spanning wallpaper does not span on lock screen
** Information type changed from Public Security to Public -- 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/1291359 Title: multiscreen spanning wallpaper does not span on lock screen Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: (It has same look as unity-greeter in lightdm but am given to believe lock screen is handled by gnome-screensaver; move if i'm wrong! lightdm seems to get it wrong a different way.) If, having made a wide wallpaper to span multiple monitors, and having set it as your wallpaper with type Span in Appearance settings, you then go to the new Lock screen... ... you will see that instead of that wide wallpaper spanning all monitors, you get the image scaled down to be shown whole on *each* monitor. As shown in screenshot attached. It needs to honour the appearance settings in this regard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 12 13:02:42 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291359/+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 1291359] Re: multiscreen spanning wallpaper does not span on lock screen
** Information type changed from Public to Public Security -- 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/1291359 Title: multiscreen spanning wallpaper does not span on lock screen Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: (It has same look as unity-greeter in lightdm but am given to believe lock screen is handled by gnome-screensaver; move if i'm wrong! lightdm seems to get it wrong a different way.) If, having made a wide wallpaper to span multiple monitors, and having set it as your wallpaper with type Span in Appearance settings, you then go to the new Lock screen... ... you will see that instead of that wide wallpaper spanning all monitors, you get the image scaled down to be shown whole on *each* monitor. As shown in screenshot attached. It needs to honour the appearance settings in this regard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 12 13:02:42 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291359/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
Lonnie - we don't update to newer versions of packages in stable releases, see https://wiki.ubuntu.com/StableReleaseUpdates ** Tags removed: upgrade-software-version -- 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/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in Unity: New Status in remmina package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 To reproduce this bug, you will have to Enable Workspaces In Ubuntu Unity, like this: System Settings Appearance Behavior Enable Workspaces Essentially, when using the Unity desktop (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. Also, I do use multiple monitors, but this too might be unrelated to the bug. I think the essential thing, is that I have Workspaces enabled. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1370014/+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
Re: [Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
The issue seems be resolved for me in Lubuntu 14.10. On Wed Jan 21 2015 at 2:01:06 PM Andy Somerville andy.somervi...@gmail.com wrote: @r0lf this is still happening in 14.10/Utopic should it be reopened there? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
You suggest that version 1.1.1 has this fixed so I had a look through the log to see what has changed. I *think* this may be the fix you need: https://github.com/FreeRDP/Remmina/commit/348e01d27869a577ad5df9bf6286f876b34a40c0 ** No longer affects: unity (Ubuntu) ** No longer affects: unity ** Changed in: remmina (Ubuntu) Status: Confirmed = Triaged ** Also affects: remmina (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: remmina (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: remmina (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: remmina (Ubuntu Precise) Status: New = Triaged ** Changed in: remmina (Ubuntu Trusty) Status: New = Triaged ** Changed in: remmina (Ubuntu Utopic) Status: New = Triaged ** Changed in: remmina (Ubuntu Utopic) Importance: Undecided = Medium ** Changed in: remmina (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: remmina (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: remmina (Ubuntu) Status: Triaged = Fix Released -- 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/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in remmina package in Ubuntu: Fix Released Status in remmina source package in Precise: Triaged Status in remmina source package in Trusty: Triaged Status in remmina source package in Utopic: Triaged Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 To reproduce this bug, you will have to Enable Workspaces In Ubuntu Unity, like this: System Settings Appearance Behavior Enable Workspaces Essentially, when using the Unity desktop (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. Also, I do use multiple monitors, but this too might be unrelated to the bug. I think the essential thing, is that I have Workspaces enabled. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1370014/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
As I understand it the sourceforge.net project is obsolete and Remmina is now developed on https://github.com/FreeRDP/Remmina. That will probably be why there is no response to your bug report. I think the current developers don't have access to the old project to remove it. -- 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/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in remmina package in Ubuntu: Fix Released Status in remmina source package in Precise: Triaged Status in remmina source package in Trusty: Triaged Status in remmina source package in Utopic: Triaged Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 To reproduce this bug, you will have to Enable Workspaces In Ubuntu Unity, like this: System Settings Appearance Behavior Enable Workspaces Essentially, when using the Unity desktop (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. Also, I do use multiple monitors, but this too might be unrelated to the bug. I think the essential thing, is that I have Workspaces enabled. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1370014/+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] [NEW] underscore in mounted drive name mishandled in menu
Public bug reported: 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. Ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 22 11:51:46 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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 unity package in Ubuntu: New Bug description: 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. Ubuntu 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jan 22 11:51:46 2015 InstallationDate: Installed on 2015-01-21 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) 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/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 1321309] Re: [Indicators] Missed calendar or alarm events need to be properly indicated
** Changed in: ubuntu-clock-app Milestone: ota-1 = ota-2 -- 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/1321309 Title: [Indicators] Missed calendar or alarm events need to be properly indicated Status in The Date and Time Indicator: Confirmed Status in Clock application for Ubuntu devices: Triaged Status in Themes for Ubuntu: New Status in Ubuntu UX bugs: Fix Committed Status in indicator-datetime package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Imagine a scenario where you have a calendar event or a clock alarm to go of at 10:00. If you get a call at the same time, then obviously the call gets the highest priority and the alarm or calendar audible notification is suppressed by the system. So a phone user can actually miss the event. This can be resolved by turning the alarm icon shown in the indicator to blue similar to messages to indicate that an alarm or event was missed by the user. --- Desired solution: The alarm icon turns its state to active like notification center/messages indicator as suggested in the bug description. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1321309/+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 1393624] Re: Lock screen rejects password on Ubuntu 14.04
@bregma It does happen regardless of how many monitors I have connected. @andyrock $ ls -l /etc/shadow -rw-r- 1 root root 1529 oct 15 22:20 /etc/shadow FWIW, password is hashed with CRYPT/SHA512 ($6$...), using default number of rounds. -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1393624/+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
Re: [Dx-packages] [Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04
The correct output should be: -rw-r- 1 root shadow 2823 Jan 21 21:02 /etc/shadow Please note that the group owner MUST be shadow. Not sure why it got changed during the update, for sure not a unity bug. Please try to change the group owner of that file and try to lock/unlock again. 2015-01-22 1:37 GMT+01:00 LexLythius 1393...@bugs.launchpad.net: @bregma It does happen regardless of how many monitors I have connected. @andyrock $ ls -l /etc/shadow -rw-r- 1 root root 1529 oct 15 22:20 /etc/shadow FWIW, password is hashed with CRYPT/SHA512 ($6$...), using default number of rounds. -- You received this bug notification because you are subscribed to Unity. https://bugs.launchpad.net/bugs/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1393624/+subscriptions -- Andrea Azzarone http://launchpad.net/~andyrock http://wiki.ubuntu.com/AndreaAzzarone -- 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/1393624 Title: Lock screen rejects password on Ubuntu 14.04 Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: Password is systematically rejected on the lock screen. However, if I click Switch account, the *greeter* does accept the same password. This issue is reproducible either by hitting the Ctrl+Alt+L shortcut key or by runnibg `gnome-screensaver-command -l` This happens after I upgraded from Ubuntu 12.04 to 14.04. I had ATI Radeon HD 3870 with open source drivers, now I have GeForce GTX 750 Ti with NVIDIA proprietary drivers. Same thing. Ubuntu 14.04.1 LTS Linux 3.13.0-39-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1393624/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
It same error here, based on my understanding it only fetch to the /etc/shadow not on the nscd cache (/var/cache/nscd/passwd) where pam_ldap is pointing with. But if I switch user, and login with the same user it will retain the previous desktop during the lock screen (even changing desktop say MATE, GNOME classic upon relogin). Tried with gnome-screensaver and with mate-screensaver same result. Sadly not on the Lock Screen as it generate the following log: Jan 22 17:14:35 ambotlang gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=104781 euid=104781 tty=:1.0 ruser= rhost= user=txunil Jan 22 17:14:44 ambotlang lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost= user=txunil -- 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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore
[Dx-packages] [Bug 1308540] Re: [lockscreen] the password entry is not shared between screens
I can confirm that the new version fixes the problem. Running 7.2.4+14.04.20141217-0ubuntu1 ** 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/1308540 Title: [lockscreen] the password entry is not shared between screens Status in Unity: Fix Committed 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] Using the Unity lockscreen on a multiple-screen session results in the password field being cleared every time different screen is focused. [Test Case] Using trusty candidate on a dual monitor config - log into unity - lock screen - start typing your password on one screen - move the pointer on the other screen - the entry is displayed empty Ideally the same entry would be move so you can keep typing even if you happened to have move the focus, that's what lightdm/unity-greeter is doing [Regression Potential] Any modification to the password dialogs could result in the inability to unlock the screen or make passwords available in cleartext. Care has been take to avoind introducing such situations with this change. [Other info] The Ubuntu 14.04 LTS SRU fix has been cherry-picked from the Ubuntu 14.10 release, where it has been in production use for a few months. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308540/+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 815996] Re: Desktop occasionally freezes/locks up when switching workspaces
On 14.04 the same: when I switch workspace in windows oftentimes it get stuck on workspace mode (where I see the 4 workspaces). The moust pointer becomes a hand and there is no way to switch back to normal mode. This seems to happen more if there are windows refreshing (e.g. a tail in some terminal window). I typically get out of this by kill -HUP compiz from Ctrl+Alt+F1 I could not get out of it disabling snapping windows because it said unity plugin requires. VGA driver is fglrx proprietary -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/815996 Title: Desktop occasionally freezes/locks up when switching workspaces Status in Compiz: Confirmed Status in Compiz Main Plugins: Confirmed Status in Compiz Desktop Wall Plugin: Confirmed Status in compiz package in Ubuntu: Confirmed Status in compiz-plugins-main package in Ubuntu: Confirmed Bug description: I'm assuming the issue is related to Compiz, but I'm not 100% sure. When I'm switching workspaces, it occasionally locks up (becoming more frequent). Most of the time, I'm going from the current one down (Ctrl+Alt+Down Arrow), and it freezes mid slide. Typically, I'm able to correct things by backing out to a terminal then returning (Ctrl+Alt+F1, pause, Alt+F7), but sometimes when I return the dual screen setup acts as one large screen (windows are stretched to the full width of both screens) and many of the windows collect on the first workspace. Ubuntu 11.04 (Classic) All packages up-to-date. If there are any logs/etc that would be helpful, let me know. --- Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,imgpng,snap,compiztoolbox,resize,place,regex,move,gnomecompat,animation,vpswitch,mousepoll,workarounds,session,expo,wall,ezoom,fade,switcher,scale] DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) InstallationMedia_: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) NonfreeKernelModules: nvidia Package: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty2 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 ProcVersionSignature_: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Tags: natty natty ubuntu Uname: Linux 2.6.38-10-generic x86_64 UnreportableReason: Please work this issue through technical support channels first. UpgradeStatus: Upgraded to natty on 2011-05-02 (84 days ago) UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/815996/+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 1408235] Re: Some icons in Dash are too big
** Changed in: ubuntukylin Milestone: vivid-alpha2 = vivid-beta1 -- 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/1408235 Title: Some icons in Dash are too big Status in Ubuntu Kylin: New Status in unity package in Ubuntu: New Bug description: Some icons in Dash are too big, like Updete Manager, Amazon Dash中有些图标太大 Steps: 1. Open Dash 2. Check icons in it --Failed. Some icons in Dash are too big Configuration: OS: Vivid x64 Daily Build 20150106 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1408235/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Also 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: New Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1412060] Re: Indicator sound fails to start with Asus Xonar
** Package changed: pulseaudio (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 https://bugs.launchpad.net/bugs/1412060 Title: Indicator sound fails to start with Asus Xonar Status in indicator-sound package in Ubuntu: New Bug description: Replaced Audigy with Xonar. Clean installed to new drive and partition. sound indicator fails to start upstart --user --startup-event indicator-services-start tries to start indicator - space in indicators shows where it is, clicking and menu doesn't appear ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20141105-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2 Uname: Linux 3.18.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jan 17 21:37:27 2015 InstallationDate: Installed on 2015-01-09 (8 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150108) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1412060/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (andyrock) ** Changed in: unity Importance: Undecided = High -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Branch linked: lp:~andyrock/unity/fix-1413165 -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
I already proposed a fix. Should land in 15.04 in few days. -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
I've already proposed a fix. Should land in 15.04 in few days. -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
Here is the output of the command on a vivid installation, that has not been updated since the middle of December 2014 and where the regression was not present yet: $ sudo apt-cache policy unity unity: Installed: 7.3.1+15.04.20141128-0ubuntu1 Candidate: 7.3.1+15.04.20150115-0ubuntu1 Version table: 7.3.1+15.04.20150115-0ubuntu1 0 500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages *** 7.3.1+15.04.20141128-0ubuntu1 0 100 /var/lib/dpkg/status And here the output of the command on my uptodate vivid installation having the regression: $ sudo apt-cache policy unity unity: Installed: 7.3.1+15.04.20150115-0ubuntu1 Candidate: 7.3.1+15.04.20150115-0ubuntu1 Version table: *** 7.3.1+15.04.20150115-0ubuntu1 0 500 http://ubuntu.mirror.root.lu/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status As far as I understand, the regression happened somewhere between the two versions. -- 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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
** Changed in: unity Milestone: None = 7.3.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/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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
