[Dx-packages] [Bug 1492174] Re: Notebook does not shutdown when battery is critically low
** Changed in: d-conf (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1492174 Title: Notebook does not shutdown when battery is critically low Status in d-conf package in Ubuntu: Confirmed Bug description: After discharging the battery completely, my notebook suspends instead of shutting down. To prevent the battery from getting damaged, it is important that the machine shuts down. This happens in ubuntu 15.04, power behavior was correct in 14.04 and in 14.10. In ubuntu 14.04 default gsettings for critical-battery-action are set to 'suspend'. In ubuntu 15.04 default gsettings for critical-battery-action are set to 'shutdown'. In ubuntu 15.10 default gsettings for critical-battery-action are set to 'suspend' back again. So the critical-battery-action setting has to be 'suspend' to shutdown notebooks completely! This seems to be a little bug in gsettings, as 'suspend' setting performs 'shutdown' action. It leads to unwanted behavior of machines when users change power settings by executing: "gsettings set org.gnome.settings-daemon.plugins.power critical-battery-action shutdown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1492174/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
This bug was fixed in the package nux - 4.0.8+17.04.20170213-0ubuntu1
---
nux (4.0.8+17.04.20170213-0ubuntu1) zesty; urgency=medium
* TextEntry: Make sure Ctr+{C,V,X,A} work with caps-lock on (LP:
#1664205)
-- Marco Trevisan (Treviño) Mon, 13 Feb 2017 13:22:38
+
** Changed in: nux (Ubuntu)
Status: In Progress => Fix Released
--
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/1664205
Title:
Copy-paste and text selection doesn't work when caps-lock is on
Status in nux package in Ubuntu:
Fix Released
Bug description:
0) Set Caps-Lock on in your keyboard
1) Open dash, and write something
2) Ctrl+A should select all the text, Ctrl+C should copy,
Ctrl+V should paste and Ctrl+X should cut
Currently they don't work unless caps-lock is turned off
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 775434] Re: Keyboard shortcut - Make Unity keyboard shortcuts configurable
Any news about this bug? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/775434 Title: Keyboard shortcut - Make Unity keyboard shortcuts configurable Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in unity-2d: Won't Fix Status in unity package in Ubuntu: Triaged Status in unity-2d package in Ubuntu: Won't Fix Bug description: Currently Unity provides about two dozen keyboard shortcuts which are completely hardcoded. It is essenetial from a productivity standpoint for the user to be able to configure any of those. It was possible with Metacity / Compiz through the Keyboard Shortcuts window. The same interface could be used for Unity for updating its configuration and possibly featuring few Unity-specific keybindings. Desired resolution: - All the unity keyboard shortcuts (defined in the following document, https://docs.google.com/a/canonical.com/document/d/1jqeKtIJwqLtl58Wk_fqjr9Rrgxn9zsouCYOo-cZsLSE/edit?hl=en_GB ) should be present and configurable using the 'Keyboard/Shortcuts' panel in 'System Settings' - Any keyboard shortcuts that are not supported by Unity should be removed. Review the following keyboard shortcut bugs before fixing this bug: - F10 shortcut is used to show menu and this is wrong (bug #878492) - Ctrl Alt Del doesn't do what most people typing it would expect (bug #890747) - Unity window placement shortcuts require a numpad (bug #751050) - Add keyboard shortcut hint overlay that is displayed when a user presses and holds the Super key (bug #855532) - The grid keybindings are behaving inconsistently (bug #878820) - Make Unity keyboard shortcuts configurable (bug #775434) - Shortcuts need to updated as part of the 12.04 upgrade (bug #891757) - Unity should also use Super-L to lock screen by default (bug #830709) - Improvements to Launcher reveal when Super is pressed behaviour (bug #905342) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/775434/+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 1664346] Re: Missing translatable strings in translation template
** Branch linked: lp:~dobey/indicator-datetime/fix-gsettings -- 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/1664346 Title: Missing translatable strings in translation template Status in indicator-datetime package in Ubuntu: In Progress Bug description: Some of the translatable strings in indicator-datetime, particularly the strings from the GSettings schema file, and utils.c, are missing from the translation template. This is likely the reason for some of the existing issues related to time formats being wrong in some locales. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1664346/+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 1664346] [NEW] Missing translatable strings in translation template
Public bug reported: Some of the translatable strings in indicator-datetime, particularly the strings from the GSettings schema file, and utils.c, are missing from the translation template. This is likely the reason for some of the existing issues related to time formats being wrong in some locales. ** Affects: indicator-datetime (Ubuntu) Importance: High Assignee: Rodney Dawes (dobey) Status: In Progress -- 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/1664346 Title: Missing translatable strings in translation template Status in indicator-datetime package in Ubuntu: In Progress Bug description: Some of the translatable strings in indicator-datetime, particularly the strings from the GSettings schema file, and utils.c, are missing from the translation template. This is likely the reason for some of the existing issues related to time formats being wrong in some locales. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1664346/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Branch linked: lp:~ci-train-bot/appmenu-qt5/appmenu-qt5-ubuntu- xenial-2467 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Branch linked: lp:~3v1n0/appmenu-qt5/xenial-sru2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1574699] Re: All QSystemTrayIcon have the same icon, and QSystemTrayIcon::isSystemTrayAvailable remove all QSystemTrayIcon
** Branch linked: lp:appmenu-qt5/16.04
--
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/1574699
Title:
All QSystemTrayIcon have the same icon, and
QSystemTrayIcon::isSystemTrayAvailable remove all QSystemTrayIcon
Status in appmenu-qt5:
New
Status in appmenu-qt5 package in Ubuntu:
Fix Released
Status in appmenu-qt5 source package in Xenial:
Fix Released
Bug description:
# Impact
This affects all Qt applications that use
QSystemTrayIcon::isSystemTrayAvailable, in Unity environment. Confirmed
examples are owncloud-client and keepassxc, but there may be more applications.
# Test Case
See the original description below for the test case in C++.
# Proposed Fix
The proposed fix is identical to what was uploaded to Yakkety as version
0.3.0+16.10.20160628.1-0ubuntu1. The fix is using unique connections for all
AppMenuPlatformSystemTrayIcon instances.
# Regression Potential
The fix is in Yakkety since June and in Zesty, and nobody complained so far.
So it should not cause any regressions.
-
in appmenu-qt5 in ubuntu 16.04, the AppMenuPlatformSystemTrayIcon assumes
there is only one instance of a QPlatformSystemTrayIcon: it register the same
dbus name for all the instances. In fact, there is one instance of
QPlatformSystemTrayIcon per instance of QSystemTrayIcon, and one temporary is
created for QSystemTrayIcon::isSystemTrayAvailable.
This breaks the owncloud client [issue
https://github.com/owncloud/client/issues/4693 ]
This example reproduces the problem:
```
#include
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
QImage img(64,64, QImage::Format_ARGB32);
img.fill(Qt::red);
QSystemTrayIcon sti(QIcon(QPixmap::fromImage(img)));
sti.show();
QSystemTrayIcon::isSystemTrayAvailable(); // with this line, the
QSystemTrayIcon does not appear
// comment the previous line to see that the QSystemTrayIcon works and
that there is a bug in that line
return a.exec();
}
```
This testcase shows that the
AppMenuPlatformSystemTrayIcon::~AppMenuPlatformSystemTrayIcon called
by the temporary object created inside
QSystemTrayIcon::isSystemTrayAvailable unregisters the icon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/appmenu-qt5/+bug/1574699/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Description changed: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml - in any folder you want + in any folder you want * Run: - - snapcraft prime - - sudo snap try prime - - snap run gtk3-appindicator + - snapcraft prime + - sudo snap try prime + - snap run gtk3-appindicator - An indicator should open (with proper icon), then if you select "Custom - Themed Icon" from its menu, you should see a proper icon. + An indicator should open (with proper icon), then if you select "Set + icon with Full Path" and/or "Enable Local Theme" from its menu, you + should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Qt: In Progress Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1600136/+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 1664230] Re: systemd-logind[]: Failed to stop user service: Unknown unit: user@.service
** Changed in: systemd-shim (Ubuntu) Status: New => Invalid -- 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/1664230 Title: systemd-logind[]: Failed to stop user service: Unknown unit: user@.service Status in systemd-shim package in Ubuntu: Invalid Bug description: pad.lv/1654241 reverted a change in dbus which now causes the following messages to appear when logging into a xenial/upstart system: login: [ 284.753970] systemd-logind[1493]: Failed to start user service, ignoring: Unknown unit: usere [ 637.682127] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@111.service [ 637.691262] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service [ 637.701000] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@1000.service [ 637.711167] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@111.service [ 637.722544] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service If the following patch is reverse-applied things work correctly again: https://launchpadlibrarian.net/302225938/dbus_1.10.6-1ubuntu3.2_1.10.6-1ubuntu3.3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1664230/+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 1664230] [NEW] systemd-logind[]: Failed to stop user service: Unknown unit: user@.service
Public bug reported: pad.lv/1654241 reverted a change in dbus which now causes the following messages to appear when logging into a xenial/upstart system: login: [ 284.753970] systemd-logind[1493]: Failed to start user service, ignoring: Unknown unit: usere [ 637.682127] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@111.service [ 637.691262] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service [ 637.701000] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@1000.service [ 637.711167] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@111.service [ 637.722544] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service If the following patch is reverse-applied things work correctly again: https://launchpadlibrarian.net/302225938/dbus_1.10.6-1ubuntu3.2_1.10.6-1ubuntu3.3.diff.gz ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: Invalid -- 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/1664230 Title: systemd-logind[]: Failed to stop user service: Unknown unit: user@.service Status in systemd-shim package in Ubuntu: Invalid Bug description: pad.lv/1654241 reverted a change in dbus which now causes the following messages to appear when logging into a xenial/upstart system: login: [ 284.753970] systemd-logind[1493]: Failed to start user service, ignoring: Unknown unit: usere [ 637.682127] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@111.service [ 637.691262] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service [ 637.701000] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@1000.service [ 637.711167] systemd-logind[7596]: Failed to start user service, ignoring: Unknown unit: user@111.service [ 637.722544] systemd-logind[7596]: Failed to stop user service: Unknown unit: user@1000.service If the following patch is reverse-applied things work correctly again: https://launchpadlibrarian.net/302225938/dbus_1.10.6-1ubuntu3.2_1.10.6-1ubuntu3.3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1664230/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
** Branch linked: lp:~3v1n0/nux/caps-lock-shortcuts-fix -- 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/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: In Progress Bug description: 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1664205] [NEW] Copy-paste and text selection doesn't work when caps-lock is on
Public bug reported: 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off ** Affects: nux (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: In Progress Bug description: 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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
