[Touch-packages] [Bug 1549507] Re: vim in xenial not compiled with python support
I just tried vim-nox (is that for "no X"?) and it seems Python 3 support
works there. I had to use the "let g:UltiSnipsUsePythonVersion = 3"
definition there because the autodetection did not work. For Powerline I
installed powerline and python3-powerline packages and used the
following configuration:
let powerlinecmd=substitute(system("which powerline"), '\n\+$', '', '')
if !empty(glob(powerlinecmd))
python3 from powerline.vim import setup as powerline_setup
python3 powerline_setup()
python3 del powerline_setup
endif
Also: vim-plug seems to be working in parallel mode with no
configuration needed. The default Python is still version 2 in Ubuntu so
version 3 needs to be defined manually.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1549507
Title:
vim in xenial not compiled with python support
Status in vim package in Ubuntu:
Fix Released
Bug description:
vim in xenial as of Feb 24, 2016 is missing python support. This has
been present in all previous builds of vim at least since 14.04. For
me, this makes the vundle-installed plugin ultisnips complain as
follows:
UltiSnips requires py >= 2.7 or py3
Press ENTER or type command to continue
I'm requesting that vim be modified to include python support
Ubuntu xenial snapshot:
vim --version |grep python
+cryptv +linebreak -python +viminfo
+cscope +lispindent -python3 +vreplace
Ubuntu 14.04
vim --version |grep pyth
+cryptv +linebreak +python +viminfo
+cscope +lispindent -python3 +vreplace
Linking: gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim
-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl
-L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil
-lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions
Ubuntu Xenial vim version complete details
root@ubuntu1604:/tmp # vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 11:55:21)
Included patches: 1-963
Modified by pkg-vim-maintain...@lists.alioth.debian.org
Compiled by pkg-vim-maintain...@lists.alioth.debian.org
Huge version without GUI. Features included (+) or not (-):
+acl +farsi +mouse_netterm +syntax
+arabic +file_in_path+mouse_sgr +tag_binary
+autocmd +find_in_path-mouse_sysmouse +tag_old_static
-balloon_eval+float +mouse_urxvt -tag_any_white
-browse +folding +mouse_xterm -tcl
++builtin_terms -footer +multi_byte +terminfo
+byte_offset +fork() +multi_lang +termresponse
+cindent +gettext -mzscheme+textobjects
-clientserver-hangul_input+netbeans_intg +title
-clipboard +iconv +path_extra -toolbar
+cmdline_compl +insert_expand -perl+user_commands
+cmdline_hist+jumplist+persistent_undo +vertsplit
+cmdline_info+keymap +postscript +virtualedit
+comments+langmap +printer +visual
+conceal +libcall +profile +visualextra
+cryptv +linebreak -python +viminfo
+cscope +lispindent -python3 +vreplace
+cursorbind +listcmds+quickfix+wildignore
+cursorshape +localmap+reltime +wildmenu
+dialog_con -lua +rightleft +windows
+diff+menu-ruby+writebackup
+digraphs+mksession +scrollbind -X11
-dnd +modify_fname+signs -xfontset
-ebcdic +mouse +smartindent -xim
+emacs_tags -mouseshape -sniff -xsmp
+eval+mouse_dec +startuptime -xterm_clipboard
+ex_extra+mouse_gpm +statusline -xterm_save
+extra_search-mouse_jsbterm -sun_workshop-xpm
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
2nd user vimrc file: "~/.vim/vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fPIE
-fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=1
Linking: gcc -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now
-Wl,--as-needed -o vim-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm
-ldl
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vim 2:7.4.963-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Wed Feb 24 22:15:56 2016
Ec2AMI: ami-ac3cdecc
Ec2AMIManifest: (unknown)
[Touch-packages] [Bug 1549507] Re: vim in xenial not compiled with python support
No Python support here (Ubuntu 16.04): VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 08 2016 11:38:28) Included patches: 1-1689 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +tag_binary +arabic +file_in_path+mouse_sgr +tag_old_static +autocmd +find_in_path-mouse_sysmouse -tag_any_white -balloon_eval+float +mouse_urxvt -tcl -browse +folding +mouse_xterm +terminfo ++builtin_terms -footer +multi_byte +termresponse +byte_offset +fork() +multi_lang +textobjects +channel +gettext -mzscheme+timers +cindent -hangul_input+netbeans_intg +title -clientserver+iconv +packages-toolbar -clipboard +insert_expand +path_extra +user_commands +cmdline_compl +job -perl+vertsplit +cmdline_hist+jumplist+persistent_undo +virtualedit +cmdline_info+keymap +postscript +visual +comments+langmap +printer +visualextra +conceal +libcall +profile +viminfo +cryptv +linebreak -python +vreplace +cscope +lispindent -python3 +wildignore +cursorbind +listcmds+quickfix+wildmenu +cursorshape +localmap+reltime +windows +dialog_con -lua +rightleft +writebackup +diff+menu-ruby-X11 +digraphs+mksession +scrollbind -xfontset -dnd +modify_fname+signs -xim -ebcdic +mouse +smartindent -xsmp +emacs_tags -mouseshape +startuptime -xterm_clipboard +eval+mouse_dec +statusline -xterm_save +ex_extra+mouse_gpm -sun_workshop-xpm +extra_search-mouse_jsbterm +syntax system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1549507 Title: vim in xenial not compiled with python support Status in vim package in Ubuntu: Fix Released Bug description: vim in xenial as of Feb 24, 2016 is missing python support. This has been present in all previous builds of vim at least since 14.04. For me, this makes the vundle-installed plugin ultisnips complain as follows: UltiSnips requires py >= 2.7 or py3 Press ENTER or type command to continue I'm requesting that vim be modified to include python support Ubuntu xenial snapshot: vim --version |grep python +cryptv +linebreak -python +viminfo +cscope +lispindent -python3 +vreplace Ubuntu 14.04 vim --version |grep pyth +cryptv +linebreak +python +viminfo +cscope +lispindent -python3 +vreplace Linking: gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions Ubuntu Xenial vim version complete details root@ubuntu1604:/tmp # vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 11:55:21) Included patches: 1-963 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +syntax +arabic +file_in_path+mouse_sgr +tag_binary +autocmd +find_in_path-mouse_sysmouse +tag_old_static -balloon_eval+float +mouse_urxvt -tag_any_white -browse +folding +mouse_xterm -tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme+textobjects -clientserver-hangul_input+netbeans_intg +title -clipboard +iconv +path_extra -toolbar +cmdline_compl +insert_expand -perl+user_commands +cmdline_hist
[Touch-packages] [Bug 1549507] Re: vim in xenial not compiled with python support
It seems vim-plug (junegunn) has regressed as well: it needs Python support for parallel plugin updating. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1549507 Title: vim in xenial not compiled with python support Status in vim package in Ubuntu: Confirmed Bug description: vim in xenial as of Feb 24, 2016 is missing python support. This has been present in all previous builds of vim at least since 14.04. For me, this makes the vundle-installed plugin ultisnips complain as follows: UltiSnips requires py >= 2.7 or py3 Press ENTER or type command to continue I'm requesting that vim be modified to include python support Ubuntu xenial snapshot: vim --version |grep python +cryptv +linebreak -python +viminfo +cscope +lispindent -python3 +vreplace Ubuntu 14.04 vim --version |grep pyth +cryptv +linebreak +python +viminfo +cscope +lispindent -python3 +vreplace Linking: gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions Ubuntu Xenial vim version complete details root@ubuntu1604:/tmp # vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 11:55:21) Included patches: 1-963 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +syntax +arabic +file_in_path+mouse_sgr +tag_binary +autocmd +find_in_path-mouse_sysmouse +tag_old_static -balloon_eval+float +mouse_urxvt -tag_any_white -browse +folding +mouse_xterm -tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme+textobjects -clientserver-hangul_input+netbeans_intg +title -clipboard +iconv +path_extra -toolbar +cmdline_compl +insert_expand -perl+user_commands +cmdline_hist+jumplist+persistent_undo +vertsplit +cmdline_info+keymap +postscript +virtualedit +comments+langmap +printer +visual +conceal +libcall +profile +visualextra +cryptv +linebreak -python +viminfo +cscope +lispindent -python3 +vreplace +cursorbind +listcmds+quickfix+wildignore +cursorshape +localmap+reltime +wildmenu +dialog_con -lua +rightleft +windows +diff+menu-ruby+writebackup +digraphs+mksession +scrollbind -X11 -dnd +modify_fname+signs -xfontset -ebcdic +mouse +smartindent -xim +emacs_tags -mouseshape -sniff -xsmp +eval+mouse_dec +startuptime -xterm_clipboard +ex_extra+mouse_gpm +statusline -xterm_save +extra_search-mouse_jsbterm -sun_workshop-xpm system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vim 2:7.4.963-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Feb 24 22:15:56 2016 Ec2AMI: ami-ac3cdecc Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: t2.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1549507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1549507] Re: vim in xenial not compiled with python support
Confirmed: UltiSnips and Powerline rendered useless after switch from Wily. Same problem in current beta2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1549507 Title: vim in xenial not compiled with python support Status in vim package in Ubuntu: Confirmed Bug description: vim in xenial as of Feb 24, 2016 is missing python support. This has been present in all previous builds of vim at least since 14.04. For me, this makes the vundle-installed plugin ultisnips complain as follows: UltiSnips requires py >= 2.7 or py3 Press ENTER or type command to continue I'm requesting that vim be modified to include python support Ubuntu xenial snapshot: vim --version |grep python +cryptv +linebreak -python +viminfo +cscope +lispindent -python3 +vreplace Ubuntu 14.04 vim --version |grep pyth +cryptv +linebreak +python +viminfo +cscope +lispindent -python3 +vreplace Linking: gcc -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -o vim -lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl -L/usr/lib/python2.7/config-x86_64-linux-gnu -lpython2.7 -lpthread -ldl -lutil -lm -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions Ubuntu Xenial vim version complete details root@ubuntu1604:/tmp # vim --version VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Feb 18 2016 11:55:21) Included patches: 1-963 Modified by pkg-vim-maintain...@lists.alioth.debian.org Compiled by pkg-vim-maintain...@lists.alioth.debian.org Huge version without GUI. Features included (+) or not (-): +acl +farsi +mouse_netterm +syntax +arabic +file_in_path+mouse_sgr +tag_binary +autocmd +find_in_path-mouse_sysmouse +tag_old_static -balloon_eval+float +mouse_urxvt -tag_any_white -browse +folding +mouse_xterm -tcl ++builtin_terms -footer +multi_byte +terminfo +byte_offset +fork() +multi_lang +termresponse +cindent +gettext -mzscheme+textobjects -clientserver-hangul_input+netbeans_intg +title -clipboard +iconv +path_extra -toolbar +cmdline_compl +insert_expand -perl+user_commands +cmdline_hist+jumplist+persistent_undo +vertsplit +cmdline_info+keymap +postscript +virtualedit +comments+langmap +printer +visual +conceal +libcall +profile +visualextra +cryptv +linebreak -python +viminfo +cscope +lispindent -python3 +vreplace +cursorbind +listcmds+quickfix+wildignore +cursorshape +localmap+reltime +wildmenu +dialog_con -lua +rightleft +windows +diff+menu-ruby+writebackup +digraphs+mksession +scrollbind -X11 -dnd +modify_fname+signs -xfontset -ebcdic +mouse +smartindent -xim +emacs_tags -mouseshape -sniff -xsmp +eval+mouse_dec +startuptime -xterm_clipboard +ex_extra+mouse_gpm +statusline -xterm_save +extra_search-mouse_jsbterm -sun_workshop-xpm system vimrc file: "$VIM/vimrc" user vimrc file: "$HOME/.vimrc" 2nd user vimrc file: "~/.vim/vimrc" user exrc file: "$HOME/.exrc" fall-back for $VIM: "/usr/share/vim" Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -Wdate-time -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 Linking: gcc -Wl,-Bsymbolic-functions -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o vim-lm -ltinfo -lnsl -lselinux -lacl -lattr -lgpm -ldl ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vim 2:7.4.963-1ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Wed Feb 24 22:15:56 2016 Ec2AMI: ami-ac3cdecc Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: t2.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1549507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 538673] Re: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down
Let's see... I actually scanned 41 files, totaling 1.5 GB. And saw the memory usage steadily growing as I scanned. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/538673 Title: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down Status in tracker package in Ubuntu: Confirmed Bug description: Binary package hint: tracker In normal operation of computer, very occasionally computer suddenly slows right down for about 45 seconds - mousepointer is very slow to respond to movement, and windows are too slow to respond to clicks. This has been hard to identify the cause because the computer is so slow to respond it's hard to get system monitor opened to see the offending process. Anyway I've finally managed to view system-monitor within the 45 seconds, and it seems to be "tracker-extract" program that is responsible, that was consuming over 1.5GB of RAM on my machine. It was hard to see though because the 45 seconds finished almost as soon as I'd viewed it, so it very quickly disappeared from the top of the process list when ranked by memory usage. So is "tracker-extract" the offending process? Can it be made a little less hungry of Memory (+ CPU) please? I'm using Ubuntu 9.10 (karmic) 64 bit version on a 2.9GB machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/538673/+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 538673] Re: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down
I just scanned 30 documents with Simple Scan in 600 dpi and saved them as png and got 2.1 gigabytes memory usage for tracker-extract (Ubuntu Gnome 15.10). The memory was never deallocated. Simple Scan is missing some usability features: it doesn't tell when it is actually processing the image; you have to wait several seconds for the "Saving image" notification to pop up. I don't know what the trigger case/root cause is or what Simple Scan is doing (however, I know I'm not going to try reproducing the scanning...). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/538673 Title: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down Status in tracker package in Ubuntu: Confirmed Bug description: Binary package hint: tracker In normal operation of computer, very occasionally computer suddenly slows right down for about 45 seconds - mousepointer is very slow to respond to movement, and windows are too slow to respond to clicks. This has been hard to identify the cause because the computer is so slow to respond it's hard to get system monitor opened to see the offending process. Anyway I've finally managed to view system-monitor within the 45 seconds, and it seems to be "tracker-extract" program that is responsible, that was consuming over 1.5GB of RAM on my machine. It was hard to see though because the 45 seconds finished almost as soon as I'd viewed it, so it very quickly disappeared from the top of the process list when ranked by memory usage. So is "tracker-extract" the offending process? Can it be made a little less hungry of Memory (+ CPU) please? I'm using Ubuntu 9.10 (karmic) 64 bit version on a 2.9GB machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/538673/+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 1448259] Re: Systemd does not send SIGTERM first on shutdown
Tested with Ubuntu Mate 15.04 in Raspberry Pi 2 (test.c, included here). It has systemd 219-7ubuntu5 package. After a reboot one can see that a file testing.txt is created but its size is zero, i.e. it was not given enough time to write the file contents. The fix is not working with two laptops and one desktop PC (testing.txt file is not created), Ubuntu 15.04. I currently have no access to development hardware so I can only test released changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd package in Debian: Fix Committed Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - Open a terminal, enter some commands, then run reboot. - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - With the updated package, the bash history should be intact. REGRESSION POTENTIAL: - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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 1448438] Re: Home directories created with invalid mode
I created this bug because of possible misconfiguration of Ubuntu. The umask should be set in /etc/login.defs and with no other magic umasks for the user. Please transfer this bug report for those who are resposible of Ubuntu's configuration, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1448438 Title: Home directories created with invalid mode Status in coreutils package in Ubuntu: Incomplete Bug description: When creating a new directory inside ~/ Ubuntu 15.04: Mode is 0775. Ubuntu 14.10: Mode is 0755. UMASK is 022 in both cases so the mode should be 0755. This bug is for Ubuntu 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1448438/+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 1448438] Re: Home directories created with invalid mode
What the umask should be in 15.04? There is UMASK defined (022) to
/etc/login.defs and /home/user is has been created with that as well
as all the /etc/user/{Documents,Downloads,Music,Pictures,Videos}
directories. I expect the umask to be the same for the rest of the
files.
mkdir test: drwxrwxr-x
mkdir (GNU coreutils) 8.23
ext4
0002
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1448438
Title:
Home directories created with invalid mode
Status in coreutils package in Ubuntu:
Incomplete
Bug description:
When creating a new directory inside ~/
Ubuntu 15.04: Mode is 0775.
Ubuntu 14.10: Mode is 0755.
UMASK is 022 in both cases so the mode should be 0755.
This bug is for Ubuntu 15.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1448438/+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 1448259] Re: Systemd does not send SIGTERM first on shutdown
When I compare the documentation I see that with systemd SIGTERM has been removed from it: Old behavior: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 Systemd behavior: http://man7.org/linux/man-pages/man8/shutdown.8.html Is it now that SIGTERM is sent in case-by-case basis to specific applications (based on error reports)? Should SIGTERM be mentioned in the documentation? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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 1448259] Re: Systemd does not send SIGTERM first on shutdown
I also tested tested the packages. The mosh case is now working but the included test.c tester still fails this case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: In Progress Status in systemd source package in Vivid: In Progress Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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 1448454] [NEW] Minimized windows are not accessible
Public bug reported: Steps to reproduce (Ubuntu 15.04): 1. Launch three windows/instances of the same program (ctrl+alt+t). 2. Notice the indicator next to the application icon in the Launcher now shows three tick marks. 3. Minimize the three launched programs. 4. Notice the indicator next to the application icon in the Launcher now shows one arrow. Now use Alt+Tab. One can access only one of the minimized programs. Also holding Alt will not let one to select any of the other instances of the same program. Using Alt+Section does not let one to select any of the other instances of the same program. This means one can access the minimized programs only by popping them visible, one by one, from the Launcher. This behaves differently than in Ubuntu 14.10, for example. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1448454 Title: Minimized windows are not accessible Status in unity package in Ubuntu: New Bug description: Steps to reproduce (Ubuntu 15.04): 1. Launch three windows/instances of the same program (ctrl+alt+t). 2. Notice the indicator next to the application icon in the Launcher now shows three tick marks. 3. Minimize the three launched programs. 4. Notice the indicator next to the application icon in the Launcher now shows one arrow. Now use Alt+Tab. One can access only one of the minimized programs. Also holding Alt will not let one to select any of the other instances of the same program. Using Alt+Section does not let one to select any of the other instances of the same program. This means one can access the minimized programs only by popping them visible, one by one, from the Launcher. This behaves differently than in Ubuntu 14.10, for example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448454/+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 1448259] [NEW] Systemd has wrong kill mode on shutdown
Public bug reported: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: Tester for missing SIGTERM https://bugs.launchpad.net/bugs/1448259/+attachment/4383242/+files/test.c ** Package changed: mosh (Ubuntu) = systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd has wrong kill mode on shutdown Status in systemd package in Ubuntu: New Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old BSD shutdown functionality. This report is for Ubuntu 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259/+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 1445405] Re: Bash history is not retained if 'reboot' command is used
See also: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1445405 Title: Bash history is not retained if 'reboot' command is used Status in systemd package in Ubuntu: Triaged Status in systemd package in Fedora: Unknown Bug description: In Ubuntu Vivid, using the 'reboot' command directly reboots the system in such a way that the bash_history is not retained. This bug has also been reported in Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=1170765 There it was found that the cause of this bug is to be found within Systemd, because systemd sends SIGKILL imediately after SIGTERM during shutdown: https://bugzilla.redhat.com/show_bug.cgi?id=1141137 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1445405/+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 1446982] Re: Wrong kill mode on shutdown
Just guessing, but let's select systemd. ** Package changed: ubuntu = systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown Status in systemd package in Ubuntu: New Bug description: I started to use mosh with Ubuntu 15.04 beta2. The packages are from today and updated. What happens with mosh is that I get Mosh: You have a detached Mosh session on this server (mosh [pid]) from the remote host after shutting down my computer and using mosh again with the same remote host. I can create this message only if I use kill -9 mosh-client-pid in the client host. If I use kill mosh-client-pid, I never get this error on the remote host. I also do not get this error from the remote host if I reboot the client host. I suspect in this case the kill mode is correct. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1446982/+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 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
Some status update: I enabled Don't wait for video sync and Force full screen redraws from compizconfig. I've not yet experienced the flickering problem. Before the compizconfig modification the problem was severe in gnome image viewer, right after rebooting. I have never seen problems as severe as in Robert's video: for me, the flickering never occurred between different windows. The flickering occurred mostly in gnome image viewer and gnome terminal: for example, when I exited vim, I could see the vim screen still there, painted over by the command line prompt and the flickering was the same rate as the cursor blink rate. It was worse in image viewer however, making it almost unusable. Even though the flickering happens inside window borders I would still rate this very severe bug, disabling common out-of-the-box media functionality. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in “xorg” package in Ubuntu: Confirmed Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau:
