[Desktop-packages] [Bug 1349661] Re: Scripts context menu option not showing unless an object is chosen
This regression is still there in Ubuntu 16.04 / Gnome Files 3.14.3. While it still works as expected in Nemo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1349661 Title: Scripts context menu option not showing unless an object is chosen Status in nautilus package in Ubuntu: Confirmed Bug description: When right clicking in a directory the "scripts" option should always appear. When right clicking in a directory the "scripts" option does not appear unless a file is chosen first. In past versions of Ubuntu the "Scripts" context menu option would appear when one or more scripts were executable in the proper location. Now, the "Scripts" context menu option only appears if the scriptsis executable, in the proper location AND the user chooses a file or directory before right click. The "Scripts" context menu option cannot be used "in" a directory now, but must be preformed "on" a file. This is counter-intuitive for operations like "Open foo here..." or "Browse as root..." since those are "in" operations, not "on" operations. I do understand the new location is ~/local/share/nautilus/scripts and they must be executable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.3 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 28 20:29:17 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-07-29 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1349661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1512027] Re: open of device pixma:MX7600_... failed: invalid argument
Same for my new Canon Pixma MG2980.
So I upgraded to libsane 1.0.26-gitxxx ppa package (from Rolf Bensch),
and now wireless works fine for both printing *and* scanning without any
proprietary package from Canon, which is really nice!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1512027
Title:
open of device pixma:MX7600_... failed: invalid argument
Status in sane-backends package in Ubuntu:
Confirmed
Bug description:
Up until recently, I've been able to scan fine with my Canon Pixma
MX7600. Then I upgraded to Ubuntu Wily and I've started getting:
$ scanimage
scanimage: open of device pixma:MX7600_192.168.2.107 failed: Invalid argument
The device pings and I can get to its HTTP port. Everything appears
OK.
If I run
strace -f -s 256 -o /tmp/trace.txt scanimage
the relevant output appears to be:
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 204
connect(204, {sa_family=AF_INET, sin_port=htons(8612),
sin_addr=inet_addr("192.168.2.107")}, 16) = 0
sendto(204, "BJNP\2\1\0\0\0\0\0\0\0\0\0\0", 16, 0, NULL, 0) = 16
select(205, [204], NULL, NULL, {4, 0}) = 1 (in [204], left {3, 998257})
recvfrom(204,
"BJNP\202\1\0\0\0\0\0\0\0\0\0\20\0\1\10\0\6\4\0\0\205\316\356\343\300\250\2k",
2048, 0, NULL, N
ULL) = 32
close(204)
write(2, "scanimage: open of device pixma:MX7600_192.168.2.107 failed:
Invalid argument\n", 78) = 78
It appears to me that the scanner is responding but the driver doesn't
like the response. I'm running sane 1.0.14-11 and sane-utils
1.0.25+git201505.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1512027/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1235991] Re: Can't “use system keyboard layout” in Saucy
Hi, Same for me: the pinyin inputs always use the us keyboard layout even whatever the option for system keyboard in ibus-setup. I used the following workaround to have the proper azerty (French) keyboard layout configured for pinyin IBus methods: Choose the right file according to the pinyin solution: /usr/share/ibus/component/pinyin.xml /usr/share/ibus/component/sunpinyin.xml /usr/share/ibus/component/googlepinyin.xml Edit the layout tag: change layoutus/layout to layoutfr/layout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1235991 Title: Can't “use system keyboard layout” in Saucy Status in “ibus” package in Ubuntu: Confirmed Bug description: In Saucy, ibus becomes more tightly integrated with the desktop. Configuring it via ibus-setup doesn't affect the instance run by ubuntu. And with the new system, there's no way to replicate the behaviour of the old “use system keyboard layout” option. When I use, for example, pinyin (Chinese) or anthy (Japanese), I want to type the letters in dvorak. I've been doing that for years, and now in Saucy it's impossible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
