[Touch-packages] [Bug 1010909] Re: permission denied: /usr/bin/{mktexpk, mktextfm}
This fix is already a few months old but still not pushed to Vivid
(which still has buggy 2.9.1). Did the vivid update fall between the
cracks or are there no plans to fix vivid?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1010909
Title:
permission denied: /usr/bin/{mktexpk,mktextfm}
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
[impact]
This bug prevents viewing dvi files with evince while confined by
apparmor.
[steps to reproduce]
1) install evince, ensure evince apparmor policy is enabled
2) view a dvi with evince
3) with the fix applied, evince should be able to display the dvi
document and should not generate apparmor rejections in syslog
[regression potential]
The change in the patch for this bug is a loosening of the apparmor
policy for the sanitized helpers of evince. The risk of an introduced
regression is small.
[original description]
1) lsb_release -rd
Description: Ubuntu Vivid Vervet (development branch)
Release: 15.04
2) apt-cache policy evince apparmor texlive
evince:
Installed: 3.14.1-0ubuntu1
Candidate: 3.14.1-0ubuntu1
Version table:
*** 3.14.1-0ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
apparmor:
Installed: 2.8.98-0ubuntu4
Candidate: 2.8.98-0ubuntu4
Version table:
*** 2.8.98-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
texlive:
Installed: 2014.20141024-1ubuntu1
Candidate: 2014.20141024-1ubuntu1
Version table:
*** 2014.20141024-1ubuntu1 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3) What is expected to happen is when one attempts to open
https://bugs.launchpad.net/ubuntu/+source/texlive-
bin/+bug/1010909/+attachment/4282336/+files/example.dvi it does so
successfully.
4) What happens instead is it hangs indefinitely, as per output of running
evince via a terminal
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+attachment/4282345/+files/error.txt
. This would appear to be due to apparmor as per:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1010909/+attachment/4282344/+files/kern.log
However, attempting to disable the offending profile fails:
sudo aa-complain /usr/bin/evince//sanitized_helper
/usr/bin/evince//sanitized_helper does not exist, please double-check the
path.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: texlive-binaries 2009-11ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Sat Jun 9 17:05:03 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=de_DE.UTF-8
SHELL=/bin/zsh
SourcePackage: texlive-bin
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1010909/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 971147] Re: xdotool and wmctrl don't move and resize windows after they are (semi)maximized
i have the same experience as dave and KSSG, although on 14.04. My suspicion is it happens only with nvidia driver, not the intel one. but are not 100% sure .. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/971147 Title: xdotool and wmctrl don't move and resize windows after they are (semi)maximized Status in unity package in Ubuntu: Expired Bug description: The command /usr/bin/xdotool windowmove `/usr/bin/xdotool getwindowfocus` 0 0 is supposed to move currenly selected window to the top left corner. It works fine on clean start, but after I maximize (or half-maximize) and then restore some window, it becomes broken, and this command silently do nothing with it. The same holds for appropriate wmctrl command like wmctrl -i -r `/usr/bin/xdotool getwindowfocus` -e 10,0,0,-1,-1 This affects Unity desktop, but does NOT affect Gnome shell desktop, so I believe it's a bug somewhere in Unity. The same issue is discussed in the following thread: http://ubuntuforums.org/showthread.php?t=1414155page=2 It seems to affect both 11.10 and 12.04 (but I checked only 12.04). user@xennie:~$ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 user@xennie:~$ apt-cache policy unity unity: Installed: 5.8.0-0ubuntu2 Candidate: 5.8.0-0ubuntu2 Version table: *** 5.8.0-0ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status user@xennie:~$ apt-cache policy xdotool xdotool: Installed: 1:2.20110530.1-3ubuntu1 Candidate: 1:2.20110530.1-3ubuntu1 Version table: *** 1:2.20110530.1-3ubuntu1 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status user@xennie:~$ apt-cache policy compiz compiz: Installed: 1:0.9.7.2-0ubuntu4 Candidate: 1:0.9.7.2-0ubuntu4 Version table: *** 1:0.9.7.2-0ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status user@xennie:~$ apt-cache policy xorg xorg: Installed: 1:7.6+12ubuntu1 Candidate: 1:7.6+12ubuntu1 Version table: *** 1:7.6+12ubuntu1 0 500 http://ru.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13 Uname: Linux 3.2.0-21-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Apr 2 02:50:17 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-03-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/971147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325462] Re: NetworkManager killing dispatched scripts too quickly
Any plans to upgrade to 0.9.9 which now at least waits 20 seconds and/or
at least backport that change? As admitted by NM maintainer's, 3 seconds
was unreasonably short ..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1325462
Title:
NetworkManager killing dispatched scripts too quickly
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
/usr/lib/NetworkManager/nm-dispatcher.action has an undocumented and
unconfigurable feature of killing scripts after 3 seconds. For a
number of settings this is too short. It is unclear why this killing
really has to happen but for sure it would be good to give a bit more
time. Find below a patch which gives a bit more lee-way.
See similar issue in fedora where it was recently fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=909577.
--- network-manager-0.9.8.8/callouts/nm-dispatcher-action.c 2014-06-02
10:31:45.317526574 +0530
+++ network-manager-0.9.8.8/callouts/nm-dispatcher-action.c.orig
2014-06-02 10:38:09.0 +0530
@@ -246,7 +246,6 @@
next_script (script-request);
}
-#define SCRIPT_TIMEOUT 60
static gboolean
script_timeout_cb (gpointer user_data)
{
@@ -256,7 +255,7 @@
script-request-script_watch_id = 0;
script-request-script_timeout_id = 0;
- g_warning (Script '%s' took too long (%d); killing it.,
script-script, SCRIPT_TIMEOUT);
+ g_warning (Script '%s' took too long; killing it., script-script);
if (kill (script-pid, 0) == 0)
kill (script-pid, SIGKILL);
@@ -351,7 +350,7 @@
if (g_spawn_async (/, argv, request-envp, G_SPAWN_DO_NOT_REAP_CHILD,
child_setup, request, script-pid, error)) {
request-script_watch_id = g_child_watch_add (script-pid,
(GChildWatchFunc) script_watch_cb, script);
- request-script_timeout_id = g_timeout_add_seconds
(SCRIPT_TIMEOUT, script_timeout_cb, script);
+ request-script_timeout_id = g_timeout_add_seconds (3,
script_timeout_cb, script);
} else {
g_warning (Failed to execute script '%s': (%d) %s,
script-script, error-code, error-message);
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1325462/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04)
I see it also on 14.04 (32-bit) but only very recently. And it happened always right away after boot and log in. A workaround (a bit more elegant that the killall one mentioned above) was for me to just start the service in a shell as ... /usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime- service ... which i copy/pasted from /etc/xdg/autostart/indicator- datetime.desktop. Looking in log-files in /var/log and in ~/.xsession- error i didn't find any errors, so not sure whether it crashed or simply didn't get started (e.g., whether above xdg autostart was ignored?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04) Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in indicator-datetime package in Ubuntu: Triaged Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
