[Bug 1579712] Re: Refresh hangs indefinitely, appstreamcli using 100% CPU
I'm running Ubuntu Gnome and the user experience is horrible with this bug when using the UI: "Software Updater" has "X" and "Stop" buttons: "Stop" button stays gray (inactive) during the update (what is the point of having gray Stop buttons?). It is even worse if the user (such as me) tried to change the repository, thinking there might be something wrong with that: "Software & Updates" -> "Ubuntu Software" -> "Download from:" [select your mirror] -> "Choose Server" -> "Close". Then there is the notification "The information about available software is out-of-date" -> "Reload". And the result: forever inactive window with no possibility to interfere. I don't know how this is handled by the UI in the regular Ubuntu but this case seems to be a good test case for user interaction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579712 Title: Refresh hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1579712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1549507
Title:
vim in xenial not compiled with python support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1549507/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549507 Title: vim in xenial not compiled with python support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1549507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549507 Title: vim in xenial not compiled with python support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1549507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1549507 Title: vim in xenial not compiled with python support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1549507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361207] Re: nvidia-graphics-drivers-* should recommend nvidia-modprobe
Ubuntu 15.10 status: Installing only nvidia-352 and nvidia-cuda-toolkit packages forces Blender 2.76 to be started as root for the CUDA option to be visible in Blender menus (no errors reported in Blender). Installing also nvidia-modprobe fixes this problem: Blender can be started as normal user. Starting Blender as root naturally saves the project files as root:root as well, possibly also other files, including user preferences. The nvidia-modprobe package installation seems more like a requirement in this use case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: nvidia-graphics-drivers-* should recommend nvidia-modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Seems like Ubuntu 16.04 (release date 2016-04-21) will have irqbalance 1.0.9-1. It is still the old one for 15.10. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Seems like Ubuntu 16.04 (release date 2016-04-21) will have irqbalance 1.0.9-1. It is still the old one for 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Raspberry updated to 15.10 Ubuntu Mate and 480 MB memory lost in irqbalance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Raspberry updated to 15.10 Ubuntu Mate and 480 MB memory lost in irqbalance. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1510838] [NEW] Language Support install fails ungracefully
Public bug reported: Preconditions: Install Ubuntu 15.10. Start some time consuming apt-get locking operation, for example "apt-get install texlive-full". Step 1: Open Language Support from System Settings. Notice it detects the apt-get is running and tells it is going to wait for the other apt- get to finish. Step 2: Wait for the other apt-get to finish. Step 3: Notice that Language Support detects the finishing of the other apt-get. What happens next is that Language Support fails with error message. However, the install is now broken and the user is not able to reinstall the previously failed language support packages. When the computer is booted there are also errors about broken language packages. ** Affects: localization-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510838 Title: Language Support install fails ungracefully To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/localization-config/+bug/1510838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510872] [NEW] Choppy sounds with GeForce GTX 750
Public bug reported: I have the following card: Asus GTX750-PHOC-1GD5 GeForce GTX 750 PH OC 1024 MB. I use its HDMI output and driver nvidia-352. The audio is choppy and sounds "like a broken record" from time to time (there is repetition of the same running audio 2-3 times for a second or two). This choppy audio bug happens with all programs I've tried (tested with VLC, Firefox, Chromium and others) and it also happens with Ubuntu Gnome 15.10 in addition to the regular Ubuntu 15.10. CPU usage when playing video in VLC is around 5%. I've previously used Ubuntu 15.04 and nvidia-346. The audio worked fine there all the time I was using Ubuntu 15.04: no choppy sounds at all. ** Affects: nvidia-graphics-drivers-352 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510872 Title: Choppy sounds with GeForce GTX 750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-352/+bug/1510872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/538673 Title: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/538673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/538673 Title: tracker-extract seems to briefly consume 1.5GB memory and slow computer right down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/538673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509411] Re: Weechat crashes when creating config files from Puppet
Crash log attached. ** Attachment added: "weechat_crash_20151023_1760.log" https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/1509411/+attachment/4503307/+files/weechat_crash_20151023_1760.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509411 Title: Weechat crashes when creating config files from Puppet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/1509411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509411] [NEW] Weechat crashes when creating config files from Puppet
Public bug reported: I am running command "weechat -r \"/quit\" -d /home/quetzal/.weechat" from Puppet configuration. The command is ran as user "quetzal", not root. I use that to create the "base" of default configuration and later apply my changes on top of those. What happens now is that weechat is crashing when running the command. It crashes when run by Puppet but not from the command line (it never crashed with weechat 1.1.1 in Ubuntu 15.04): Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** Very bad! WeeChat is crashing (SIGSEGV received) Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** Full crash dump was saved to /home/quetzal/.weechat/weechat_crash_20151023_1760.log file. Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** Please help WeeChat developers to fix this bug: Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** 1. If you have a core file, please run: gdb /path/to/weechat core Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** then issue command: "bt full" and send result to developers Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** (see user's guide for more info about report of crashes). Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** 2. Otherwise send backtrace (below), only if it is a complete trace. Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** Keep the crash log file, just in case developers ask you some info Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: *** (be careful, private info like passwords may be in this file). Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: === WeeChat backtrace === Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: (written by WeeChat 1.3, compiled on Aug 20 2015 05:29:31) Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: === End of backtrace === Notice: /Stage[main]/Weechat::Fror::Quetzal/Exec[weechat-confcreate-quetzal]/returns: Aborted (core dumped) ** Affects: weechat (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509411 Title: Weechat crashes when creating config files from Puppet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weechat/+bug/1509411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509218] [NEW] Garbled text in Wily installer with GeForce GTX750
Public bug reported: Just downloaded Wily final and tried to install it with the graphical installer. I see some garbled text: there are usually pieces of text missing (blocks) or text is replaced with white artifacts. I was barely able to go through the install by remembering the options. This is visible also after rebooting to the fresh install of Ubuntu 15.10. Installing nvidia-352 fixes this problem. Here is how the problem looks like in the installer: http://imgur.com/MdlBGUU ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509218 Title: Garbled text in Wily installer with GeForce GTX750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1509218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509218] Re: Garbled text in Wily installer with GeForce GTX750
The screenshot is from Ubuntu Gnome 15.10 but it is exactly the same in Ubuntu 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509218 Title: Garbled text in Wily installer with GeForce GTX750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1509218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
After 3 days memory usage is still the same 5 MB as reported previously. Is 5 MB within normal bounds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
After 3 days memory usage is still the same 5 MB as reported previously. Is 5 MB within normal bounds? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Memory usage with irqbalance 1.0.9-0ubuntu1~ppavv1 is 5 MB after 23 hours. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Memory usage with irqbalance 1.0.9-0ubuntu1~ppavv1 is 5 MB after 23 hours. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
The leak was around 60 MB/day. Now running irqbalance 1.0.9-0ubuntu1~ppavv1 from the ppa. I will report more later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
The leak was around 60 MB/day. Now running irqbalance 1.0.9-0ubuntu1~ppavv1 from the ppa. I will report more later. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Happens also with Raspberry Pi 2 and Ubuntu Mate 15.04. Irqbalance has 497 MB usage. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1247107] Re: Runaway irqbalance consuming CPU and Memory
Happens also with Raspberry Pi 2 and Ubuntu Mate 15.04. Irqbalance has 497 MB usage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247107 Title: Runaway irqbalance consuming CPU and Memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1247107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448438 Title: Home directories created with invalid mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1448438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448438
Title:
Home directories created with invalid mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1448438/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448903] Re: Remmina window not visible after launch
** Package changed: ubuntu = remmina (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448903 Title: Remmina window not visible after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1448903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448903] [NEW] Remmina window not visible after launch
Public bug reported: Steps to reproduce in Ubuntu 15.04: 1. Have one program open with visible window, for example Terminal. 2. Place Remmina Remote Desktop Client to the Launcher 3. Click on the Remmina Remote Desktop Client launcher. 4. Observe Remmina Remote Desktop Client appears behind the topmost window. I don't see this behavior with other programs I've tried. Remmina always starts behind the topmost window, causing awkward/clumsy user experience. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448903 Title: Remmina window not visible after launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448443] [NEW] Can't execute scripts from home
Public bug reported: I can't execute files anymore with Ubuntu 15.04's Files program (GUI). For example, I install IHMC CmapTools to some directory inside ~/. It installs a file named bin/CmapTools with sh shebang. This file always opens with gedit but it has execute bit on. However, if I start this from the command line with ./CmapTools, the execution succeeds. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448443 Title: Can't execute scripts from home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448454 Title: Minimized windows are not accessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448438] [NEW] Home directories created with invalid mode
Public bug reported: 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. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448438 Title: Home directories created with invalid mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448443] Re: Can't execute scripts from home
** Package changed: ubuntu = nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448443 Title: Can't execute scripts from home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448438] Re: Home directories created with invalid mode
It was with mkdir. Also see that g+w mode is set when I do touch to a file. So it is also for regular files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448438 Title: Home directories created with invalid mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1448438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
OK, I will try with strace later, hope it's sufficient proof. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Unfortunately strace didn't reveal much. However, I created a small program to show the signal. Using test.c I can see that when testing with Ubuntu 14.10 the program always creates the testing.txt file on restart. However, if I test with Ubuntu 15.04, that file is never created in the same use case. Contrary to my previous claim, it behaves the same way in reboot shutdown: Mosh gets the error on reconnect and test.c never creates the testing.txt file. SIGTERM is never received. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
** Attachment added: Tester for missing SIGTERM https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982/+attachment/4382943/+files/test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd has wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Thanks Keith for the summary. This bug can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445405 Title: Bash history is not retained if 'reboot' command is used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1445405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
New bug created: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1448259 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Are there any Ubuntu Mosh guys who take the full end-to-end responsibility of Mosh (or systemd) working correctly there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
(1) I am connecting from a machine running Ubuntu release 15.04 (mosh version 1.2.4a) to one Raspberry Pi machine running Raspbian Wheezy release (mosh version 1.2.3). After shutdown and restart of the machine running Ubuntu release 15.04 (mosh version 1.2.4a) I get this error from the Raspberry Pi machine after a reconnect with mosh from the same 15.04 machine (mosh version 1.2.4a). After restart I do *not* get the this error from the Raspbian machine (mosh version 1.2.3) when doing a reconnect with mosh (version 1.2.4a). (2) Connecting from the 14.10 machine (mosh version 1.2.4a) to the 15.04 machine (mosh version 1.2.4a). I did just a quick test with the 14.10 machine: shutdown only case (mosh version 1.2.4a). After shutdown and restart of the 14.10 machine (mosh version 1.2.4a) I do *not* get this error from the 14.10 machine when doing a reconnect with mosh (version version 1.2.4a). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
My kill -9 was a description of similar end result as to what happens on shutdown. Mosh behaves the same way. I'm not normally using kill directly, I just wish it behaves the same way on reboot and shutdown (i.e. normal kill). I don't even know is there kill (SIGTERM) done to mosh on shutdown. This was just a guess. Another option is that it's missing. I read somewhere that at least BSD /sbin/shutdown tries to first kill with SIGTERM and after that with SIGKILL. I don't actually know what the behavior should be on Ubuntu 15.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] Re: Wrong kill mode on shutdown
Just tried mosh from 14.10 - 15.04. This works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/mosh/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446982] [NEW] Wrong kill mode on shutdown
Public bug reported: 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. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: mosh systemd-boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446982 Title: Wrong kill mode on shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1446982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
This happens also for me. Ubuntu 14.10 Geforce GTX 750 and xorg edgers nvidia-346. But so far I've seen it only in Image Viewer and in gnome Terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 991040] Re: COMRESET failed (errno=-16) on Intel SSD
I experienced this issue after I added new SSD drive to an old desktop computer. I fixed this by removing the CD/DVD drive and changing SSD SATA cable from SATA 1 to SATA 0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/991040 Title: COMRESET failed (errno=-16) on Intel SSD To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/991040/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333959] [NEW] Window selection sends mouse click to tmux
Public bug reported: Precondtions: 1. Tmux having mouse support enabled (pane selector specific). 2. Tmux with a window open in a terminal having more than one pane. 3. Second terminal open. 4. Application specific window selector opened from Launcher. 5. First mouse button pressed for tmux window in the selector. What happens is that the mouse click is sent from the selector all the way down to the tmux window. What happens is that I have to press the mouse button again in the *same* pane for the selection to cancel (I see the yellow marking on the upper right corner of the old pane even when the green selector indicator has changed to a new pane). I never wanted to select that pane from the selector, I just wanted to select a window. I don't want the mouse click to be sent to the terminal. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333959 Title: Window selection sends mouse click to tmux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1333959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333959] Re: Window selection sends mouse click to tmux
This report is for Ubuntu 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333959 Title: Window selection sends mouse click to tmux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1333959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333191] [NEW] Inconsistent 256 color console experience
Public bug reported: I've been trying to make both vim and weechat work with 256 color support and the best is that I can make only either one work. Here is a list of test cases and their results. The best configuration leaves high intensity characters to show as low intensity. The result is the same with 0.4.2 weechat coming with Ubuntu 14.04 LTS and also with longterm ppa 0.4.3 weechat. All of the tests are with gnome-terminal: Let's say this is case 1: tmux new-session -s weechat And this is case 2: tmux new-session -s weechat weechat And this is case 3: weechat Let's say this is case 4: export TERM=xterm-256color in .bashrc, tput colors shows 256 colors. And this is case 5: export TERM=screen-256color in .bashrc, tput colors shows 256 colors. And this is case 6: No TERM= in .bashrc, tput colors shows 8 colors. Case 1 4: Broken lines (weechat FAQ 3.2 case) with missing high intensity text. Case 2 4: Complete lines with high intensity text. Case 3 4: Complete lines with missing high intensity text. Case 1 5: Complete lines with high intensity text. Case 2 5: Complete lines with high intensity text. Case 3 5: Complete lines with missing high intensity text. Case 1 6: Complete lines with high intensity text. Case 2 6: Complete lines with high intensity text. Case 3 6: Complete lines with high intensity text. Tests with no TERM= in .bashrc, xterm-256color in gnome-terminal settings and screen-256color in .tmux.conf: Case 1: Complete lines with missing high intensity text. Case 2: Complete lines with missing high intensity text. Case 3: Complete lines with missing high intensity text. Tests with no TERM= in .bashrc, xterm-256color in gnome-terminal settings and xterm-256color in .tmux.conf: Case 1: Broken lines (weechat FAQ 3.2 case) with missing high intensity text. Case 2: Broken lines (weechat FAQ 3.2 case) with missing high intensity text. Case 3: Complete lines with missing high intensity text. Tests with no TERM= in .bashrc, gnome-256color in gnome-terminal settings and screen-256color in .tmux.conf: Case 1: Complete lines with missing high intensity text. Case 2: Complete lines with missing high intensity text. Case 3: Complete lines with missing high intensity text. Tests with no TERM= in .bashrc, xterm-256color in gnome-terminal settings and gnome-256color in .tmux.conf: Case 1: Broken lines (weechat FAQ 3.2 case) with missing high intensity text. Case 2: Broken lines (weechat FAQ 3.2 case) with missing high intensity text. Case 3: Complete lines with missing high intensity text. Tests with no TERM= in .bashrc, no TERM in gnome-terminal settings and screen-256color in .tmux.conf: Case 1: Complete lines with high intensity text. Case 2: Complete lines with high intensity text. Case 3: Complete lines with high intensity text. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333191 Title: Inconsistent 256 color console experience To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1333191/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210785] Re: wpa_supplicant crashed with SIGSEGV
I had this crash also after a reboot of the same laptop as previously reported (laptop is Acer Aspire 5750). Here is the syslog of the part where it is going to suspend and crashes: Oct 21 23:44:14 elrond NetworkManager[789]: info sleep requested (sleeping: no enabled: yes) Oct 21 23:44:14 elrond NetworkManager[789]: info sleeping or disabling... Oct 21 23:44:14 elrond NetworkManager[789]: info (eth0): device state change: unavailable - unmanaged (reason 'sleeping') [20 10 37] Oct 21 23:44:14 elrond NetworkManager[789]: info (eth0): cleaning up... Oct 21 23:44:14 elrond NetworkManager[789]: info (eth0): taking down device. Oct 21 23:44:14 elrond kernel: [129974.141273] tg3 :02:00.0: System wakeup enabled by ACPI Oct 21 23:44:14 elrond NetworkManager[789]: info (wlan0): device state change: activated - unmanaged (reason 'sleeping') [100 10 37] Oct 21 23:44:14 elrond NetworkManager[789]: info (wlan0): deactivating device (reason 'sleeping') [37] Oct 21 23:44:14 elrond whoopsie[993]: offline Oct 21 23:44:14 elrond NetworkManager[789]: info (wlan0): canceled DHCP transaction, DHCP client pid 7414 Oct 21 23:44:14 elrond avahi-daemon[781]: Withdrawing address record for fe80::3a59:f9ff:feaf:73f2 on wlan0. Oct 21 23:44:14 elrond avahi-daemon[781]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::3a59:f9ff:feaf:73f2. Oct 21 23:44:14 elrond avahi-daemon[781]: Interface wlan0.IPv6 no longer relevant for mDNS. Oct 21 23:44:14 elrond kernel: [129974.358733] wlan0: deauthenticating from 00:25:9c:41:a0:db by local choice (reason=3) Oct 21 23:44:14 elrond wpa_supplicant[20620]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3 Oct 21 23:44:14 elrond kernel: [129974.366737] cfg80211: Calling CRDA to update world regulatory domain Oct 21 23:44:14 elrond avahi-daemon[781]: Withdrawing address record for 192.168.200.142 on wlan0. Oct 21 23:44:14 elrond avahi-daemon[781]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.200.142. Oct 21 23:44:14 elrond avahi-daemon[781]: Interface wlan0.IPv4 no longer relevant for mDNS. Oct 21 23:44:14 elrond NetworkManager[789]: warn DNS: plugin dnsmasq update failed Oct 21 23:44:14 elrond NetworkManager[789]: info Removing DNS information from /sbin/resolvconf Oct 21 23:44:14 elrond dnsmasq[1084]: setting upstream servers from DBus Oct 21 23:44:14 elrond kernel: [129974.371681] cfg80211: World regulatory domain updated: Oct 21 23:44:14 elrond kernel: [129974.371690] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Oct 21 23:44:14 elrond kernel: [129974.371696] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Oct 21 23:44:14 elrond kernel: [129974.371701] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Oct 21 23:44:14 elrond kernel: [129974.371706] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Oct 21 23:44:14 elrond kernel: [129974.371710] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) Oct 21 23:44:14 elrond kernel: [129974.371714] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Oct 21 23:44:14 elrond kernel: [129974.371949] wpa_supplicant[20620]: segfault at 26d ip 004b1795 sp 7fff0e9eb920 error 4 in wpa_supplicant[40+15f000] Oct 21 23:44:14 elrond NetworkManager[789]: info (wlan0): cleaning up... Oct 21 23:44:14 elrond NetworkManager[789]: info (wlan0): taking down device. Oct 21 23:44:14 elrond dbus[736]: [system] Activating service name='fi.w1.wpa_supplicant1' (using servicehelper) Oct 21 23:44:14 elrond NetworkManager[789]: info wpa_supplicant stopped Oct 21 23:44:14 elrond dbus[736]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) Oct 21 23:44:14 elrond dbus[736]: [system] Activating service name='org.freedesktop.systemd1' (using servicehelper) Oct 21 23:44:14 elrond dbus[736]: [system] Successfully activated service 'fi.w1.wpa_supplicant1' Oct 21 23:44:14 elrond NetworkManager[789]: info wpa_supplicant started Oct 21 23:44:14 elrond dbus[736]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Oct 21 23:44:14 elrond dbus[736]: [system] Successfully activated service 'org.freedesktop.systemd1' Oct 21 23:44:15 elrond anacron[25186]: Anacron 2.3 started on 2013-10-21 Oct 21 23:44:15 elrond anacron[25186]: Normal exit (0 jobs run) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210785 Title: wpa_supplicant crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1210785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210785] Re: wpa_supplicant crashed with SIGSEGV
It is possible that this problem is timing sensitive. I had about 5 suspend-wakeup cycles without a crash. After that it again started to crash. I think it may be caused by the fact that everything was cached to memory (this system has 8 GB ram and normally light usage). It is possible that this is harder to reproduce with systems which are capable of faster suspends. Just a guess: try the suspend with HDD, not SSD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210785 Title: wpa_supplicant crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1210785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1210785] Re: wpa_supplicant crashed with SIGSEGV
Steps to reproduce: wake up laptop from sleep. This crash occurs every second time for each wakeup. Crash might be timing related and probably something to do with timing of the interface takedown sequence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1210785 Title: wpa_supplicant crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1210785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173623] Re: Launcher - Two finger scrolling doesn't permit navigating through icons anymore
This is not just about two fingers. Mouse/trackball scrolling is also disabled in the Launcher. It was working in 12.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173623 Title: Launcher - Two finger scrolling doesn't permit navigating through icons anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1173623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174944] Re: Incorrect locale interpretation regression
Don't know about bug 1072019 but sounds similar. There has been a locale change in 13.04. From my locales (untouched): LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE=en_US.UTF-8 LC_NUMERIC=fi_FI.UTF-8 LC_TIME=fi_FI.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=fi_FI.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=fi_FI.UTF-8 LC_NAME=fi_FI.UTF-8 LC_ADDRESS=fi_FI.UTF-8 LC_TELEPHONE=fi_FI.UTF-8 LC_MEASUREMENT=fi_FI.UTF-8 LC_IDENTIFICATION=fi_FI.UTF-8 LC_ALL= Now the locale in 13.04 looks correct to me. Before it was incorrect (in 12.10). I don't know how many packages there are having this problem but it's probable now that full translation (if language is available) is done in several applications. Just checked the Regional options: Display numbers, dates and currency amounts in the usual format for:. It is clearly a bug if country specific setting here simply overwrites the language setting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174944 Title: Incorrect locale interpretation regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174944] Re: Incorrect locale interpretation regression
If we check the calendar (top right hand corner) in 13.04 with Finnish settings we see it says la touko (for Saturday and May). This is incorrect as both la and touko can be have the same meaning in English (abbreviated Sat and May). When we check the calendar itself we see that the week now starts from Monday, which is correct. Then we see translated dates for the week (ma ti ke to pe la su), which is incorrect. Then we again see lauantai, 4 toukokuu 2013 in the heading, which is incorrect. The correct would be as it is in regional settings, la 4. toukokuuta 2013. In Finland 4. actually means 4th, causing that you have use that ta ending for the month. There are regional ways to say full dates meaning you can't just pick numbers and say the same thing in different languages. I just see no reasoning why the calendar has to be in Finnish. Same problem can be seen with the ls -l command which simply truncates textual moths from English to Finnish but still leaving time format to incorrect 20:40, which is 20.40 in Finland. Either select US-only output or try to be consistent with outputs. But in any case the language should be correct if set in locales. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174944 Title: Incorrect locale interpretation regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174944] Re: Incorrect locale interpretation regression
Also ps command seems to be broken. It happily localizes just the month but follows no rule, i.e. time format in 00:00:00, touko02. Probably all coreutils programs are broken in the same way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174944 Title: Incorrect locale interpretation regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174944] [NEW] Incorrect locale interpretation regression
Public bug reported: I live in a country having one spoken language: Finnish. Many people in this country speak/understand other than Finnish. Most understand Swedish and/or English. The defaults have been changed for locale in 13.04, causing regression. Calendar is now in Finnish only but nothing suggest Finnish-only output in locales (upper right corner in UI settings). It seems also the ls command is broken, showing Finnish output for non-Finnish speakers. Just a guess this doesn't affect only Finland... This problem affects multiple software in Ubuntu and the Ubuntu configuration change has caused it. So multiple separate error reports are needed for this regression for each of the impacted packages. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: locale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174944 Title: Incorrect locale interpretation regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1174944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 825903] Re: Atheros AR9287 Wireles Very Very Slow
I reported success too fast for 12.04 beta 2. After some uptime and usage the transfer rate drops to 3..7 Mbit/s. After reboot the transfer rate is again at 18..19 Mbit/s. It gets worse very fast after the first boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/825903 Title: Atheros AR9287 Wireles Very Very Slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/825903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 825903] Re: Atheros AR9287 Wireles Very Very Slow
I can confirm that there was/is a problem with AR9287 in Onieric (11.10). There internet speed test reported 7 Mbit/s for Onieric and 802.11g (45 MBit/s for Ethernet). The same test reported 14..15 Mbit/s for a couple of older laptops and a phone. These tests were tried during the same hour (a few tests). Then I tried the new beta 2 of 12.04 and I get around 18.5 Mbit/s with that. No bursty transfers with that so it means something was probably fixed to the kernel. I am running Acer Aspire 5750 and lspci shows this: 03:00.0 Network controller: Atheros Communications Inc. AR9287 Wireless Network Adapter (PCI-Express) (rev 01) Subsystem: Foxconn International, Inc. Device e034 Nice and smooth sith beta 2 so far. Also the fan of the laptop is more silent with this version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/825903 Title: Atheros AR9287 Wireles Very Very Slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/825903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: [i915] Problem with 1080p resolution in Samsung LE-46B530 TV
I might try the next LTS (12.04) when it rolls out but won't patch that system. You can close this report if needed, it's not critical bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: [i915] Problem with 1080p resolution in Samsung LE-46B530 TV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/572139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
Maybe we can keep this error as the can't use 1080p mode. The other one (rebooting when screen not ON) could be reported in a separate report. Here is the video I made to show the problem: http://www.youtube.com/watch?v=PbFjy1Wf_CU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
About the youtube video: the fading effect when switching back from no signal state is caused by the camera. It's not visible on the screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
apport information ** Tags added: apport-collected ** Description changed: I'm running current release of Lucid Lynx desktop version and trying to use 1080p with this TV. This report includes description of the released official (non-RC) 10.04 LTS desktop version. BIOS is now the latest 0028 version. Two tests: 1. Connect HDMI from motherboard to Onkyo amplifier and from Onkyo amplifier to TV: Onkyo 7 text shown in display settings. 2. Connect HDMI from motherboard directly to TV: Samsung 7 text shown in display settings. The first setup is the one I'm planning to use. What happens is that in both tests 1 and 2 couple of centimeters (1 inch) is missing at least from top and bottom of the screen (probably also from left and right). I can't see any menus but they are there if I scroll the mouse outside the visible area and click there. A workaround to this problem is to use Screen Fit option in the TV, not 16:9. The Screen Fit option has to be used with both 1920 x 1080 (16:9) and 1280 x 720 (16:9) resolutions. The resolutions seem to be correct however: if I take a screenshot then it is exactly 1280 x 720. In summary, there are three problems with this TV: 1) Screen Fit option has to be selected. 2) Searching for Signals problem in 1920 x 1080: it starts when scrolling in Firefox or moving windows. 3) Flickering problem in 1920 x 1080: the picture tears, this may include problem 2. 4) No HDMI audio. There is only a faint click sound when trying to play audio. Scrolling in Firefox usually causes symptom 2 but the Searching for Signals text may disappear and the picture comes back if scrolling back. Flickering in problem 3 may disappear if moving the window back, but it starts again especially if window is on the border of the screen. Problems 2 and 3 do not occur with resolution 1280 x 720 so it is full HD specific. I also tried to install the latest PPA kernel (2.6.34-999). With this kernel problem 4 vanishes and the HDMI audio is played correctly. Also problem 3 is much less severe with the kernel update. Anyway even with the kernel update problems 1 and 2 remain. + + --- + Architecture: amd64 + DRM.card0.DisplayPort.1: + status: disconnected + enabled: disabled + dpms: On + modes: + edid-base64: + DRM.card0.DisplayPort.2: + status: disconnected + enabled: disabled + dpms: On + modes: + edid-base64: + DRM.card0.HDMI_Type_A.1: + status: connected + enabled: enabled + dpms: On + modes: 1280x720 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 + edid-base64: AP///wA9ywEAAf//AQOAEAl4Cu6Ro1RMmSYPUFS974BxT4EAgUCBgJUAlQ+zAKlAAR0AclHQHiBuKFUAoFoeAR0AvFLQHiC4KFVAoFoe/ABUWC1TUjY3NCAgICAg/QAYSxpRFwAKICAgICAgAYYCAy7xTpABAwQFEhMUDx4fICEiLwl/Bw8fBxcHODcHMD8HwINPAABmAwwAEgCAAR2AGHEcFiBYLCUAoFoAAACeAR2A0HIcFiAQLCWAoFoAAACeAjqAGHE4LUBYLEUAoFoe1gmAoCDgLRAIYCIAgOAhCAgY1A== + DRM.card0.HDMI_Type_A.2: + status: disconnected + enabled: disabled + dpms: On + modes: + edid-base64: + DRM.card0.VGA.1: + status: disconnected + enabled: disabled + dpms: On + modes: + edid-base64: + DistroRelease: Ubuntu 10.10 + InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) + Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5.1 + PackageArchitecture: amd64 + ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-23-generic root=UUID=f58ae567-8564-483f-a333-2e09fd73ebfa ro quiet splash + ProcEnviron: + LANG=en_US.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7 + Tags: maverick maverick + Uname: Linux 2.6.35-23-generic x86_64 + UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare + dmi.bios.date: 10/18/2010 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: TCIBX10H.86A.0040.2010.1018.1100 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: DH55HC + dmi.board.vendor: Intel Corporation + dmi.board.version: AAE70933-501 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrTCIBX10H.86A.0040.2010.1018.1100:bd10/18/2010:svn:pn:pvr:rvnIntelCorporation:rnDH55HC:rvrAAE70933-501:cvn:ct3:cvr: + glxinfo: Error: [Errno 2] No such file or directory + system: + distro: Ubuntu + codename: maverick + architecture: x86_64 + kernel: 2.6.35-23-generic ** Attachment added: BootDmesg.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770901/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770902/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770903/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770904/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770905/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] PciDisplay.txt
apport information ** Attachment added: PciDisplay.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770906/+files/PciDisplay.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770907/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770908/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770909/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770910/+files/RelatedPackageVersions.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770911/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] UdevLog.txt
apport information ** Attachment added: UdevLog.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770912/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] XorgLog.txt
apport information ** Attachment added: XorgLog.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770913/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] XorgLogOld.txt
apport information ** Attachment added: XorgLogOld.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770914/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Xrandr.txt
apport information ** Attachment added: Xrandr.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770915/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] peripherals.txt
apport information ** Attachment added: peripherals.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770916/+files/peripherals.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] setxkbmap.txt
apport information ** Attachment added: setxkbmap.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770917/+files/setxkbmap.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] xdpyinfo.txt
apport information ** Attachment added: xdpyinfo.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770918/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] xkbcomp.txt
apport information ** Attachment added: xkbcomp.txt https://bugs.edge.launchpad.net/bugs/572139/+attachment/1770919/+files/xkbcomp.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572139 Title: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
Any progress? Please check the xserver-xorg-input-evdev explanation: http://packages.ubuntu.com/maverick/xserver-xorg-input-evdev It is clearly keyboard/mouse INPUT -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
Do you need more information than the ones already provided? -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
When do I take these logs? When the screen is goes off in 1080p mode? Or do I take them in 720p mode? Does xserver-xorg-input-evdev do the HDMI out or why do we want to log that? -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
In Lucid I manually patched the kernel to make the sounds work. Now time has passed and I've moved to Maverick (and don't use Lucid). No patching needed in Maverick (the sounds work with Maverick's kernel). The Maverick is up-to-date and I've also updated the BIOS (it's 0038 now). The same 1080p mode problem still exists in Maverick. When this mode is on and I scroll down with Firefox, the screen goes OFF. When I scroll up the screen goes ON. The problem is the same as before and there are some flickering when pictures are being shown. 720p mode works without problems. The 1080p problem seems to be somehow related to either pictures or contrast differences because when some content is being shown in the browser, first starts the flickering and then screen goes OFF (or just goes OFF with no flickering). Seems there is now BIOS 0040 available. I will try that to see if it makes any difference. Note: OFF=no signal shown on screen, ON=content shown on screen. -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
BIOS updated to 0040. The no signal feature still exists with this version. -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
Just one more problem I'd like to mention. This is more like a nuisance so I can live with it (I don't know about others): 1. Watch etc. the TV. 2. Turn the TV off. 3. While maintaining the system remotely, notice that there are security updates. 4. Apply the security updates which require system restart. 5. Restart the box remotely. 6. Locally turn on the TV. Notice no signal text. Press ctrl-alt-del. 7. Notice Ubuntu logo (the exit logo with dots) starts to show with garbled palette. After the box has restarted the garbled palette is also in the BIOS (the part where it shows the boot logo). The BIOS garbled palette sets to normal only after Ubuntu has booted with the TV turned on. So this problem and the 1080p mode no signal problem are the current problems in Maverick. I have not tested this garbled palette BIOS problem with 0040, only with 0038. -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
Fabio: What I mean is: 1) I load Firefox. I set some web page with pictures below the visible area of the page. 2) I have now the web page loaded. 3) I press down arrow or PgDn. Screen starts to flicker when the pictures below start to appear. The flicker/tearing usually happens when scrolling with down arrow (when the pictures start to appear). But with both down arrow and PgDn the screen goes off (no signal) when the picture(s) fully appear. Then when the screen is in the no signal state I press up arrow or PgUp. The same thing happens but in reverse, i.e: flickering starts when part of the picture is shown and the flickering goes off when I scroll to an area containing no pictures. The same thing happens without Firefox. But in my test I use Firefox and the scrolling because it's the easiest way to recover from the no signal state. The Firefox setup is also easiest to reproduce because other cases need windows in certain places of the screen and certain content so it would be difficult to explain that setup in a bug report. -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599715] Re: HEST: Table is not found!
I see this HEST error string in my dmesg with the latest Ubuntu Maverick RC (updated to current today). Don't know what it causes and if that is non-issue after all... -- HEST: Table is not found! https://bugs.launchpad.net/bugs/599715 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636205] Re: RAID10 install with LVM doesn't work
It seems the installer remembers the previous setup. I was testing with RAID5, removed the RAID setup, removed LVM and freed the disks so that they show free space. This was not enough for the installer to detect it was not RAID5 anymore but RAID10 instead. I got this working by using the Lucid alternate install CD and reconfigure the RAID10 from scratch. Now both Maverick and Lucid can see it is a RAID10 configuration. I also managed to install it to this configuration and boot from it. This is probably not a big issue, you can close this report if you want. -- RAID10 install with LVM doesn't work https://bugs.launchpad.net/bugs/636205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636205] [NEW] RAID10 install with LVM doesn't work
Public bug reported: I tested the beta alternate Maverick (10.10) from CD and tried to create a RAID10 array with LVM. What happens is that the RAID10 array itself is correctly created and it shows the correct size ((N/2)*S). However when I try to create the LVM for this array it shows a size as if it were calculated from RAID5 size ((N-1)*S). So what the LVM shows is a *lot* bigger than the actual usable size for RAID10. I also tried to use this incorrect size and create the LVM. It caused a serious lockup of the partitioner for all subsequent install attempts. So I was forced to take the Live CD and repartition with Disk Utility (also GParted crashed with Live CD). I also tested RAID5. It worked correctly with correct sizes shown ((N-1)*S). Does the installer mix the RAID10 with RAID5? ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: - I tested the beta alternate Maverick (10.10) from CD and tried to create a RAID10 array with LVM. - What happens is that the RAID10 array itself is correctly created and it shows the correct size ((N/2)*S). - However when I try to create the LVM for this array it shows a size as if it were calculated from RAID5 size ((N-1)*S). - So what the LVM shows is a *lot* bigger than the actual usable size for RAID10. + I tested the beta alternate Maverick (10.10) from CD and tried to create + a RAID10 array with LVM. What happens is that the RAID10 array itself is + correctly created and it shows the correct size ((N/2)*S). However when + I try to create the LVM for this array it shows a size as if it were + calculated from RAID5 size ((N-1)*S). So what the LVM shows is a *lot* + bigger than the actual usable size for RAID10. I also tried to use this incorrect size and create the LVM. It caused a serious lockup of the partitioner for all subsequent install attempts. So I was forced to take the Live CD and repartition with Disk Utility (also GParted crashed with Live CD). I also tested RAID5. It worked correctly with correct sizes shown ((N-1)*S). Does the installer mix the RAID10 with RAID5? -- RAID10 install with LVM doesn't work https://bugs.launchpad.net/bugs/636205 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572139] Re: Samsung LE-46B530 TV does not work with Intel DH55HC motherboard
I will update the description after learning more about HDMI in Ubuntu. Old descriptions can be ignored. -- Samsung LE-46B530 TV does not work with Intel DH55HC motherboard https://bugs.launchpad.net/bugs/572139 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
