[Dx-packages] [Bug 1483888] [NEW] Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones plugged
Public bug reported: Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones are plugged. This I consider a bug, since user cannot depend on the such a device with hearing calls / being woken up in the morning. Typical scenario: listening to music/watching movies during the night and falling asleep. It already happened several times to me that I did not get awakened by the phone in the morning, since headphones were plugged into the device and all the sounds could be heard only in headphones. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483888 Title: Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones plugged Status in indicator-power package in Ubuntu: New Bug description: Aquaris E5: Ringtone + buzzer cannot be heard when jack/headphones are plugged. This I consider a bug, since user cannot depend on the such a device with hearing calls / being woken up in the morning. Typical scenario: listening to music/watching movies during the night and falling asleep. It already happened several times to me that I did not get awakened by the phone in the morning, since headphones were plugged into the device and all the sounds could be heard only in headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483888/+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 1396553] Re: No rating and 0 reviews shown for all applications in the dash
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/1396553 Title: No rating and 0 reviews shown for all applications in the dash Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: When viewing the preview of any application in the dash (installed or not) by right-clicking it, the displayed number of reviews is always 0 (zero) and the rating is always empty. This used to work in previous Ubuntu versions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Nov 26 11:08:57 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-13 (43 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1396553/+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 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
funny, this bug was fixed for the 4.5 a while ago, seems the vegeta also needs the same fix of the brightness xml file. ** Summary changed: - Possible to manually set display brightness to 0 on Ubuntu Touch + Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+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 1476292] Re: Replying to a message from the indicator should mark it read in Messages also
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-messages (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1476292 Title: Replying to a message from the indicator should mark it read in Messages also Status in indicator-messages package in Ubuntu: Confirmed Bug description: After replying to a message in the indicator. I later find I have an unread message in Messages. It turns out to be the same message. This is a little confusing and laborious, so I would suggest not duplicating the work for the user and mark the message read when a reply is sent from the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1476292/+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 1313248] Re: Ctrl+[Key] Shortcuts Assigned in QtCreator Do Not Work
This bug is *still* not fixed. This way qt5 applications, like texmaker, are almost not usable! See for example https://code.google.com/p/texmaker/issues/detail?id=1301 for this bug being reported for texmaker (which is wrong, it is a bug of the qt5 version shipped by ubuntu) The only workaround for this (from the user perspective, not the app developer perspective ) seems to be to recompile qt5. This should not be the default solution for this problem! ** Bug watch added: code.google.com/p/texmaker/issues #1301 http://code.google.com/p/texmaker/issues/detail?id=1301 -- 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/1313248 Title: Ctrl+[Key] Shortcuts Assigned in QtCreator Do Not Work Status in appmenu-qt5 package in Ubuntu: Confirmed Bug description: I recompiled one of my Qt applications tonight on Ubuntu 14.04. This application uses QActions that are are set up in the mainwindow.ui file. (I originally did this with QtDesigner some two year ago, but have updated the application for Qt 5 in the mean time.) When appmenu-qt5 is installed, the Ctrl+[key] shortcuts of the actions on the main menubar do not work. If I remove appment-qt5, they do work as expected. Oddly enough, the edit actions on the edit dialog do work, but they are disabled and enabled multiple times. I tried disabling and enabling the actions on the main menubar in code which didn't help. I also tried assigning the short cut keys via code and that did not help. I am using 14.04 LTS, appmenu-qt5 0.3.0+14.04.20140415-0ubuntu1, and the Qt program found at https://github.com/Dyrcona/omiquji To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1313248/+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 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Tim, is this still happening? I cannot reproduce it in Trusty ** Changed in: oem-priority Status: Triaged = 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/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Won't Fix Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press super on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) 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/oem-priority/+bug/1310518/+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 1481913] Re: UI volume warnings need revision
** Branch linked: lp:~charlesk/indicator-sound/lp-1481913-integrate- settings-and-clamp-volume -- 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/1481913 Title: UI volume warnings need revision Status in Canonical System Image: Fix Committed Status in indicator-sound package in Ubuntu: Fix Released Bug description: As raised in OEM bug #1474364 (the title there is poor), the warning scheme used by Ubuntu does not currently follow the letter of the EU regulations for mobile devices (it seems to follow the spirit). Design have now reviewed the regulations (bug #1480912), and propose: https://wiki.ubuntu.com/Sound#limits This is the diff: https://wiki.ubuntu.com/Sound?action=diffrev2=146rev1=145 The UI notification scheme needs to be updated to match the new design. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481913/+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 1457276] Re: Drop-down sound menu has no delay
*** This bug is a duplicate of bug 552920 *** https://bugs.launchpad.net/bugs/552920 ** This bug has been marked a duplicate of bug 552920 Moving diagonally from narrow menu title often opens adjacent menu -- 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/1457276 Title: Drop-down sound menu has no delay Status in Unity: In Progress Status in unity package in Ubuntu: In Progress Bug description: It's seems it is not kind of bug but very nice-to-have feature. When I'm going to decrease sound level I always face the problem that Calendar opens. It happens because mouse cursor goes through the calendar area (see screenshot in the attachment). It is a bit annoying. Also, see explanation here: https://css-tricks.com/dropdown-menus-with-more-forgiving-mouse-movement-paths/ To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1457276/+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 552920] Re: Moving diagonally from narrow menu title often opens adjacent menu
** Branch linked: lp:~azzar1/unity/lp-552920 -- 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/552920 Title: Moving diagonally from narrow menu title often opens adjacent menu Status in One Hundred Papercuts: Triaged Status in Unity: In Progress Status in gtk+2.0 package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: In Progress Bug description: gtk 2.22, Ubuntu 10.10 1. Click on the volume control to open the sound menu. 2. Move the pointer diagonally to click on the maximum volume button. https://launchpadlibrarian.net/42732636/Why_autoexpanding_indicators_are_a_bad_idea.png What often happens: The sound menu closes, and the menu next to it opens. Screencast: https://www.youtube.com/watch?v=lVUokjAlREs Example in an informal usability test: https://www.youtube.com/watch?feature=player_detailpagev=PgGbZfR6Vec#t=13m55s What should happen: The sound menu stays open. One solution would be to make the volume slider vertical. But this would not work for other menus (like the Bluetooth menu), and would look awkward with other items in the menu. Another solution would be to use a timer for closing the current menu and opening a new one. This is what Windows does for submenus. But it has the drawback of slowing down browsing, which would be worse for top-level menus than for submenus. GTK already has a more sophisticated solution for submenus, similar to Mac OS: a triangle based on the corners of the submenu and its parent item, in which there is a much longer delay for closing the submenu and changing the menu selection. http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/HierarchicalMenus.html Discussion of the invisible triangle for submenus in GTK: http://mail.gnome.org/archives/gtk-devel-list/2000-May/msg00118.html However, this feature in Gtk+ has been broken since July 2013. https://bugzilla.gnome.org/show_bug.cgi?id=710388 The code, once fixed, should be applied to menu titles as well. More information: http://thomaspark.co/2011/10/making-menus- escapable/ To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/552920/+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 552920] Re: Moving diagonally from narrow menu title often opens adjacent menu
** Tags added: 16.04-hit-list ** Changed in: unity Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (azzar1) ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (azzar1) ** 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/552920 Title: Moving diagonally from narrow menu title often opens adjacent menu Status in One Hundred Papercuts: Triaged Status in Unity: In Progress Status in gtk+2.0 package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: In Progress Bug description: gtk 2.22, Ubuntu 10.10 1. Click on the volume control to open the sound menu. 2. Move the pointer diagonally to click on the maximum volume button. https://launchpadlibrarian.net/42732636/Why_autoexpanding_indicators_are_a_bad_idea.png What often happens: The sound menu closes, and the menu next to it opens. Screencast: https://www.youtube.com/watch?v=lVUokjAlREs Example in an informal usability test: https://www.youtube.com/watch?feature=player_detailpagev=PgGbZfR6Vec#t=13m55s What should happen: The sound menu stays open. One solution would be to make the volume slider vertical. But this would not work for other menus (like the Bluetooth menu), and would look awkward with other items in the menu. Another solution would be to use a timer for closing the current menu and opening a new one. This is what Windows does for submenus. But it has the drawback of slowing down browsing, which would be worse for top-level menus than for submenus. GTK already has a more sophisticated solution for submenus, similar to Mac OS: a triangle based on the corners of the submenu and its parent item, in which there is a much longer delay for closing the submenu and changing the menu selection. http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/HierarchicalMenus.html Discussion of the invisible triangle for submenus in GTK: http://mail.gnome.org/archives/gtk-devel-list/2000-May/msg00118.html However, this feature in Gtk+ has been broken since July 2013. https://bugzilla.gnome.org/show_bug.cgi?id=710388 The code, once fixed, should be applied to menu titles as well. More information: http://thomaspark.co/2011/10/making-menus- escapable/ To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/552920/+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 1483855] Re: Getting assertion 'db != NULL' failed when using the url dispatcher
*** This bug is a duplicate of bug 1483854 *** https://bugs.launchpad.net/bugs/1483854 ** This bug has been marked a duplicate of bug 1483854 Getting assertion 'db != NULL' failed when using the url dispatcher -- 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/1483855 Title: Getting assertion 'db != NULL' failed when using the url dispatcher Status in url-dispatcher package in Ubuntu: New Bug description: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1483855/+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 1483854] [NEW] Getting assertion 'db != NULL' failed when using the url dispatcher
Public bug reported: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New -- 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/1483854 Title: Getting assertion 'db != NULL' failed when using the url dispatcher Status in url-dispatcher package in Ubuntu: New Bug description: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1483854/+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 1483855] [NEW] Getting assertion 'db != NULL' failed when using the url dispatcher
Public bug reported: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. ** Affects: url-dispatcher (Ubuntu) Importance: Undecided Status: New -- 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/1483855 Title: Getting assertion 'db != NULL' failed when using the url dispatcher Status in url-dispatcher package in Ubuntu: New Bug description: Trying to use the url dispatcher I got this error when trying to go to this url and other too: ** (process:31929): WARNING **: Unable to dispatch url 'scope://com.canonical.scopes.photos_photos':GDBus.Error:com.canonical.URLDispatcher.BadURL: URL 'scope://com.canonical.scopes.photos_photos' is not handleable by the URL Dispatcher then in the log I found this: ** (process:2011): WARNING **: Unable to create tables: database is locked ** (process:2011): CRITICAL **: url_db_find_url: assertion 'db != NULL' failed After all, ted suggested that restarting the url dispatcher would work and it did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1483855/+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 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
** Changed in: nux Status: In Progress = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) Status in Compiz: Invalid Status in Nux: Fix Committed Status in Unity: Invalid Status in nux package in Ubuntu: In Progress Bug description: (Using the Terminal window as an example) 1. Open a Terminal window 2. Maximise a window fully so that its title bar and menu share the top Unity panel 3. Click the View menu (the menu opens) 4. Click the Search menu (the View menu closes) 5. Click anywhere on the title bar 6. The window restores to non-maximised size It shouldn't do this, only a double-click should restore the window. Alternative ways to trigger it: 3. Click the Terminal menu 4. Click the Reset option 5. Click anywhere on the title bar 3. Click the Terminal menu 4. Click inside the main area of the application 5. Click anywhere on the title bar It looks like something is going wrong with the double-click detection when a menu is opened and then closed. Version: Ubuntu 14.04.1 unity 7.2.2+14.04.20140714-0ubuntu1.1 xorg 1:7.7+1ubuntu8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+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 1474847] Re: udev devices are redundantly listed in unity sidebar and overwrite appearance settings
** Changed in: unity (Ubuntu) Assignee: (unassigned) = Andrea Azzarone (azzar1) ** Changed in: unity Assignee: (unassigned) = Andrea Azzarone (azzar1) ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Importance: Undecided = Medium -- 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/1474847 Title: udev devices are redundantly listed in unity sidebar and overwrite appearance settings Status in Unity: New Status in unity package in Ubuntu: New Bug description: If `/dev/` is mounted with `--bind` (like it is common for `chroot` environments) device in `/etc/fstab` in the `chroot` appear in the `unity` sidebar no matter whether they have been removed from it previously. After a reboot the initial appearance settings are overwritten (at least previously removed devices are displayed again). `unity` should not care about `chroot` setups and not overwrite settings without asking. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 Uname: Linux 4.1.1-040101-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CurrentDesktop: Unity Date: Wed Jul 15 14:39:43 2015 InstallationDate: Installed on 2015-06-08 (37 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-06-09 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1474847/+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 552920] Re: Moving diagonally from narrow menu title often opens adjacent menu
** Tags added: rls-w-incoming -- 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/552920 Title: Moving diagonally from narrow menu title often opens adjacent menu Status in One Hundred Papercuts: Triaged Status in Unity: In Progress Status in gtk+2.0 package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: In Progress Bug description: gtk 2.22, Ubuntu 10.10 1. Click on the volume control to open the sound menu. 2. Move the pointer diagonally to click on the maximum volume button. https://launchpadlibrarian.net/42732636/Why_autoexpanding_indicators_are_a_bad_idea.png What often happens: The sound menu closes, and the menu next to it opens. Screencast: https://www.youtube.com/watch?v=lVUokjAlREs Example in an informal usability test: https://www.youtube.com/watch?feature=player_detailpagev=PgGbZfR6Vec#t=13m55s What should happen: The sound menu stays open. One solution would be to make the volume slider vertical. But this would not work for other menus (like the Bluetooth menu), and would look awkward with other items in the menu. Another solution would be to use a timer for closing the current menu and opening a new one. This is what Windows does for submenus. But it has the drawback of slowing down browsing, which would be worse for top-level menus than for submenus. GTK already has a more sophisticated solution for submenus, similar to Mac OS: a triangle based on the corners of the submenu and its parent item, in which there is a much longer delay for closing the submenu and changing the menu selection. http://www.quinn.echidna.id.au/Quinn/WWW/HISubtleties/HierarchicalMenus.html Discussion of the invisible triangle for submenus in GTK: http://mail.gnome.org/archives/gtk-devel-list/2000-May/msg00118.html However, this feature in Gtk+ has been broken since July 2013. https://bugzilla.gnome.org/show_bug.cgi?id=710388 The code, once fixed, should be applied to menu titles as well. More information: http://thomaspark.co/2011/10/making-menus- escapable/ To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/552920/+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 1454200] Re: qimpanel window position wrong on high-dpi screen
** Package changed: fcitx-qimpanel (Ubuntu) = fcitx (Ubuntu) -- 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/1454200 Title: qimpanel window position wrong on high-dpi screen Status in Unity: New Status in fcitx package in Ubuntu: Triaged Status in unity package in Ubuntu: New Bug description: When using qimpanel on a high-dpi screen, its window position is ½ of the position of the insertion point. It uses device and UI coordinates incorrectly. When you edit text in the center of the screen, qimpanel will appear offset to the top left; when you edit in the bottom right corner of the screen, qimpanel will appear in the center. Ibus-pinyin does not have such a window position problem, but it seems not to be shipped anymore by default in 15.04. Ubuntu offers the ability to develop for and test this (= set the UI scaling factor to 2.0) since already before 14.04. Ubuntu version: ubuntu-15.04-desktop-amd64.iso package version: default version of qimpanel on the disk image To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1454200/+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
