Has winpdb been removed from the repository in Ubuntu 22.04?
This is what I have and what I want to achieve:
Current Partition Setup Current State Desired State
/dev/sda1 /BIOS
/dev/sda2 / Ubuntu18.04 Ubuntu18.04 I
/dev/sda3 empty none Ubuntu18.04 II
In want to install Ubuntu 18.04 II from my running installation Ubuntu 18.04. I.
- I have an ISO install file.
What else do I need and how do I do it?
There is a similar question, Is there a program to install Ubuntu from a Linux system? It uses debootstrap and targets minimal Ubuntu systems and text only installs. Its a very complex setup. I am looking for sth saving the time and effort to reboot.
The key point of my question is that I do not want to shut down or reboot my computer.
I want to boot into /dev/sda1 and start an application/a script/single commands or whatever. After that Ubuntu18.04 II should be installed in /dev/sda3. And I am still in my running install on /dev/sda1.
When trying to install Kicad 5.0.2 from PPA, as recommended in 18.04, with:
sudo add-apt-repository ppa:js-reynaud/kicad-5
sudo apt update
sudo apt install kicad
I see strange effects, none of which are discussed at the Launchpad page.
"Help/Getting started" gives an error. It is only available after running
sudo apt install kicad-doc-en.After that install, it will open the file manager with the file marked, but not Firefox as expected. How can I change that? The page opens fine by double-clicking it in the file manager.
The command
sudo apt install kicad-librariesshould install the symbol-, template- and footprint- libs. It did something, but they did not appear in the program. For example "File/New/Project from Template..." was empty. The templates appeared only after I installedsudo apt install kicad-templatesAfter
sudo apt install kicad-demothey can not be seen anywhere in the GUI. After a search I found them in/usr/share/kicad/demos. Is one really supposed tosudocopy them to the home directory and change all file permissions?
I crosschecked the Windows download for V5.0.3. There, everything installed, fully configured and ready to go. Why not in my Ubuntu? Tests were done on a fresh installation of Xubuntu 18.04.
I can restart my desktop from a console window (Ctrl+Alt+F1) with this command:
sudo service lightdm restart
This will present a fresh login screen and closes all programs running on the desktop. This it not what I want.
I want a command or a script that restarts the desktop from a console while keeping all applications running, so I can access their windows when I get back the desktop screen.
Background
I keep having problems with the desktop blacking out while the computer remains running fine. There are 9,286 posts with "black screen" with different causes. Some with solutions like this, some without. I am working with many Xubuntu computers and had it happen multiple times.
While causes differ, (in my cases) the symptom is often the same. It usually helped to restart lightdm, but I was losing my data and had to restart all applications. Now I had the problem when testing VGA matrix switches. Every time I reconnected my monitor, I had to reset lightdm. So I learned that what I need is a better workaround. Something analogous to restarting explorer.exe with the Windows Task Manager. This solves every hang up of the desktop but does not affect running programs (it basically restarts the desktop).
System: Xubuntu 16.04 64-bit, PC laptop
edit: after the first comment, I adapted the question
When adding a rule in GUFW/Advanced there are three choices for logging. From the man ufw page/sectin LOGGING i learned
- do not log - log nothing
- log - logs all blocked packets for that rule and maybe new/invalid packets. There is a rate limiting
- log-all - logs all packets with rate limit
As ufw has the log levels (off/low/medium/high/full) its not clear what the mapping is, but it seems sure that everything beside "off" should log all packets that are caught by the rule where log is set.
According to man ufw logging goes into the syslog together with a lot of other suff. So naturally I would expect the GUI Log page to show those log entries.
However, I did not manage to get any packet log entries listed in the Log pane. How can that be done?
I have a Xubunut16.04 install with 16GB RAM and a 20GB enrypted Swap.
When I start a large compilation with
configure
make -j
in a terminal, I can see in the panel load monitor
- all cores go to 100%
- memory goes up to 100% in about 20secs
- The Swap display remains at zero. As soon as the memory is a 100%, the whole PC freezes up. I can do nothig via keyboard/mouse. I can not got to another terminal. I can not login via ssh from another PC. The HDD light is on and the disk is spinning.
I can reproduce it every time. I have waited up to 5hrs, but there is no change (it does not revocer). I need to do a hard reset.
I read a lot in the forum and found hints on the Swap and cypttab. From the commands I could check before starting the complilation all is fine.
- The Swap setup is just the standard default. The UUID of the
blkidcommand and the content of/etc/fstabandetc/cypttabis consistent swap seems to be on
swapon --show
NAME..... TYPE.... SIZE USED PRIO
/dev/sm-0 partition 15.2G 0B ..... -1
Since the PC was Idle USED=0B seems ok. No Idea if PRIO=-1 is OK.
- cryptsetup seems to beworking cryptsetup status cryptswap1 /dev/nmapper/cryptswap1 is active and is in use [...]
I tried to set the values for vm.min_free_kbyptes and vm.swappiness
sudo nano
vm.swappiness 40
vm.min_free_kbyptes=240000
This is the syslog section of the crash
Sep 18 09:54:40 ford2 rtkit-daemon[1668]: Demoted 4 threads.
Sep 18 09:54:40 ford2 rtkit-daemon[1668]: The canary thread is apparently starving. Taking action.
Sep 18 09:54:40 ford2 rtkit-daemon[1668]: Demoting known real-time threads.
Sep 18 09:54:40 ford2 rtkit-daemon[1668]: Successfully demoted thread 1994 of process 1959 (n/a).
Sep 18 09:54:40 ford2 rtkit-daemon[1668]: Successfully demoted thread 1993 of process 1959 (n/a).
Sep 18 09:54:42 ford2 rtkit-daemon[1668]: Successfully demoted thread 1992 of process 1959 (n/a).
Sep 18 09:54:42 ford2 rtkit-daemon[1668]: Successfully demoted thread 1959 of process 1959 (n/a).
Sep 18 09:54:42 ford2 rtkit-daemon[1668]: Demoted 4 threads.
Sep 18 09:55:57 ford2 rtkit-daemon[1668]: The canary thread is apparently starving. Taking action.
Sep 18 09:55:57 ford2 rtkit-daemon[1668]: Demoting known real-time threads.
Sep 18 09:55:58 ford2 rtkit-daemon[1668]: Successfully demoted thread 1994 of process 1959 (n/a).
Sep 18 09:56:02 ford2 rtkit-daemon[1668]: Successfully demoted thread 1993 of process 1959 (n/a).
Sep 18 09:56:05 ford2 rtkit-daemon[1668]: Successfully demoted thread 1992 of process 1959 (n/a).
Sep 18 09:56:05 ford2 rtkit-daemon[1668]: Successfully demoted thread 1959 of process 1959 (n/a).
Sep 18 09:56:05 ford2 rtkit-daemon[1668]: Demoted 4 threads.
Sep 18 09:56:58 ford2 rtkit-daemon[1668]: The canary thread is apparently starving. Taking action.
Sep 18 09:57:23 ford2 rtkit-daemon[1668]: Demoting known real-time threads.
Sep 18 09:57:23 ford2 rtkit-daemon[1668]: Successfully demoted thread 1994 of process 1959 (n/a).
Sep 18 09:57:24 ford2 rtkit-daemon[1668]: Successfully demoted thread 1993 of process 1959 (n/a).
Sep 18 09:57:25 ford2 rtkit-daemon[1668]: Successfully demoted thread 1992 of process 1959 (n/a).
Sep 18 09:57:26 ford2 rtkit-daemon[1668]: Successfully demoted thread 1959 of process 1959 (n/a).
Sep 18 09:57:26 ford2 rtkit-daemon[1668]: Demoted 4 threads.
Sep 18 09:57:27 ford2 rtkit-daemon[1668]: The canary thread is apparently starving. Taking action.
Sep 18 09:58:12 ford2 kernel: [56168.624667] light-locker invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
Sep 18 09:58:12 ford2 kernel: [56168.624675] light-locker cpuset=/ mems_allowed=0
Sep 18 09:58:12 ford2 kernel: [56168.624687] CPU: 3 PID: 1966 Comm: light-locker Not tainted 4.4.0-124-generic #148-Ubuntu
Sep 18 09:58:12 ford2 kernel: [56168.624695] 0000000000000286 fed8977dd0b815dd ffff88021f0a39f8 ffffffff813ffb53
Sep 18 09:58:12 ford2 kernel: [56168.624701] ffff88021f0a3bb0 ffff8800cabd9980 ffff88021f0a3a68 ffffffff8120febe
Sep 18 09:58:12 ford2 kernel: [56168.624706] 0000000000000015 0000000000000000 ffff8800cdce8540 ffff8800cb060cc0
Sep 18 09:58:12 ford2 kernel: [56168.624711] Call Trace:
Sep 18 09:58:12 ford2 kernel: [56168.624723] [<ffffffff813ffb53>] dump_stack+0x63/0x90
Sep 18 09:58:12 ford2 kernel: [56168.624731] [<ffffffff8120febe>] dump_header+0x5a/0x1c5
Sep 18 09:58:12 ford2 kernel: [56168.624738] [<ffffffff81397b74>] ? apparmor_capable+0xc4/0x1b0
Sep 18 09:58:12 ford2 kernel: [56168.624744] [<ffffffff81196512>] oom_kill_process+0x202/0x3c0
Sep 18 09:58:12 ford2 kernel: [56168.624751] [<ffffffff81196939>] out_of_memory+0x219/0x460
Sep 18 09:58:12 ford2 kernel: [56168.624758] [<ffffffff8119c985>] __alloc_pages_slowpath.constprop.88+0x965/0xb00
Sep 18 09:58:12 ford2 kernel: [56168.624764] [<ffffffff8119cda8>] __alloc_pages_nodemask+0x288/0x2a0
Sep 18 09:58:12 ford2 kernel: [56168.624772] [<ffffffff811e699c>] alloc_pages_current+0x8c/0x110
Sep 18 09:58:12 ford2 kernel: [56168.624777] [<ffffffff81192a2b>] __page_cache_alloc+0xab/0xc0
Sep 18 09:58:12 ford2 kernel: [56168.624781] [<ffffffff81194fb0>] filemap_fault+0x150/0x400
Sep 18 09:58:12 ford2 kernel: [56168.624787] [<ffffffff812a80a6>] ext4_filemap_fault+0x36/0x50
Sep 18 09:58:12 ford2 kernel: [56168.624792] [<ffffffff811c1c66>] __do_fault+0x56/0xf0
Sep 18 09:58:12 ford2 kernel: [56168.624797] [<ffffffff811c5a55>] handle_mm_fault+0xfa5/0x1820
Sep 18 09:58:12 ford2 kernel: [56168.624803] [<ffffffff8106c7a1>] __do_page_fault+0x1a1/0x410
Sep 18 09:58:12 ford2 kernel: [56168.624808] [<ffffffff8106ca32>] do_page_fault+0x22/0x30
Sep 18 09:58:12 ford2 kernel: [56168.624814] [<ffffffff81852158>] page_fault+0x28/0x30
Sep 18 09:58:12 ford2 kernel: [56168.624849] Mem-Info:
Sep 18 09:58:12 ford2 kernel: [56168.624861] active_anon:1647527 inactive_anon:296577 isolated_anon:0
Sep 18 09:58:12 ford2 kernel: [56168.624861] active_file:1668 inactive_file:1450 isolated_file:0
Sep 18 09:58:12 ford2 kernel: [56168.624861] unevictable:57 dirty:0 writeback:19 unstable:0
Sep 18 09:58:17 ford2 kernel: [56168.624861] slab_reclaimable:7188 slab_unreclaimable:11454
Sep 18 09:58:17 ford2 kernel: [56168.624861] mapped:2157 shmem:1828 pagetables:29068 bounce:0
Sep 18 09:58:17 ford2 kernel: [56168.624861] free:25993 free_pcp:780 free_cma:0
Sep 18 09:58:17 ford2 kernel: [56168.624870] Node 0 DMA free:15864kB min:132kB low:164kB high:196kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15904kB mlocked:0kB dirty:0kB writeback:0kB mapped:0kB shmem:0kB slab_reclaimable:0kB slab_unreclaimable:8kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes
Sep 18 09:58:17 ford2 kernel: [56168.624883] lowmem_reserve[]: 0 3128 7863 7863 7863
Sep 18 09:58:26 ford2 kernel: [56168.624889] Node 0 DMA32 free:45676kB min:26832kB low:33540kB high:40248kB active_anon:2633248kB inactive_anon:526780kB active_file:412kB inactive_file:816kB unevictable:116kB isolated(anon):0kB isolated(file):0kB present:3391040kB managed:3310296kB mlocked:116kB dirty:0kB writeback:16kB mapped:852kB shmem:924kB slab_reclaimable:10092kB slab_unreclaimable:17304kB kernel_stack:6368kB pagetables:46868kB unstable:0kB bounce:0kB free_pcp:1888kB local_pcp:124kB free_cma:0kB writeback_tmp:0kB pages_scanned:7516 all_unreclaimable? yes
Sep 18 09:58:26 ford2 kernel: [56168.624902] lowmem_reserve[]: 0 0 4734 4734 4734
Sep 18 09:58:26 ford2 kernel: [56168.624907] Node 0 Normal free:42432kB min:40612kB low:50764kB high:60916kB active_anon:3956860kB inactive_anon:659528kB active_file:6260kB inactive_file:4984kB unevictable:112kB isolated(anon):0kB isolated(file):0kB present:4980736kB managed:4848744kB mlocked:112kB dirty:0kB writeback:60kB mapped:7776kB shmem:6388kB slab_reclaimable:18660kB slab_unreclaimable:28504kB kernel_stack:10384kB pagetables:69404kB unstable:0kB bounce:0kB free_pcp:1232kB local_pcp:140kB free_cma:0kB writeback_tmp:0kB pages_scanned:227604 all_unreclaimable? yes
Sep 18 09:58:26 ford2 kernel: [56168.624919] lowmem_reserve[]: 0 0 0 0 0
Sep 18 09:58:26 ford2 kernel: [56168.624924] Node 0 DMA: 0*4kB 1*8kB (U) 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 0*512kB 1*1024kB (U) 1*2048kB (M) 3*4096kB (M) = 15864kB
Sep 18 09:58:30 ford2 kernel: [56168.624946] Node 0 DMA32: 401*4kB (UE) 645*8kB (UME) 536*16kB (UME) 212*32kB (UME) 48*64kB (UME) 20*128kB (UME) 16*256kB (UE) 5*512kB (UE) 1*1024kB (E) 1*2048kB (M) 2*4096kB (U) = 45676kB
Sep 18 09:58:30 ford2 kernel: [56168.624970] Node 0 Normal: 772*4kB (UMEH) 1090*8kB (UMEH) 830*16kB (UMEH) 234*32kB (UMEH) 66*64kB (UEH) 22*128kB (UMEH) 7*256kB (UME) 2*512kB (EH) 0*1024kB 0*2048kB 0*4096kB = 42432kB
Sep 18 09:58:30 ford2 kernel: [56168.624994] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Sep 18 09:58:30 ford2 kernel: [56168.624998] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Sep 18 09:58:30 ford2 kernel: [56168.625000] 7717 total pagecache pages
Sep 18 09:58:35 ford2 kernel: [56168.625003] 2702 pages in swap cache
Sep 18 09:58:35 ford2 kernel: [56168.625007] Swap cache stats: add 14088781, delete 14086079, find 3056376/5582411
Sep 18 09:58:35 ford2 kernel: [56168.625009] Free swap = 0kB
Sep 18 09:58:35 ford2 kernel: [56168.625011] Total swap = 20510716kB
Sep 18 09:58:35 ford2 kernel: [56168.625014] 2096942 pages RAM
Sep 18 09:58:38 ford2 kernel: [56168.625016] 0 pages HighMem/MovableOnly
Sep 18 09:58:38 ford2 kernel: [56168.625019] 53206 pages reserved
Sep 18 09:58:38 ford2 kernel: [56168.625021] 0 pages cma reserved
Sep 18 09:58:38 ford2 kernel: [56168.625023] 0 pages hwpoisoned
Sep 18 09:58:38 ford2 kernel: [56168.625025] [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
Sep 18 09:58:38 ford2 kernel: [56168.625046] [ 1059] 0 1059 69355 99 38 3 112 0 accounts-daemon
Sep 18 09:58:48 ford2 kernel: [56168.625052] [ 1062] 0 1062 103381 67 68 3 387 0 ModemManager
Sep 18 09:58:48 ford2 kernel: [56168.625077] [ 1104] 0 1104 1099 0 8 3 50 0 acpid
Sep 18 09:58:55 ford2 kernel: [56168.625083] [ 1106] 111 1106 11195 27 27 3 68 0 avahi-daemon
Sep 18 09:58:55 ford2 kernel: [56168.625088] [ 1107] 0 1107 23850
[....]
Sep 18 10:00:44 ford2 kernel: [56168.627949] [ 3801] 1000 3801 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.627954] [ 3803] 1000 3803 48520 11667 93 3 21663 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.627959] [ 3804] 1000 3804 2441 0 11 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.627964] [ 3805] 1000 3805 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.627969] [ 3806] 1000 3806 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.627975] [ 3807] 1000 3807 46475 8719 89 3 22246 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.627980] [ 3808] 1000 3808 48535 11847 91 4 21548 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.627985] [ 3809] 1000 3809 2441 0 11 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.627990] [ 3810] 1000 3810 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.627995] [ 3811] 1000 3811 1127 0 9 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628001] [ 3812] 1000 3812 48022 11486 92 3 21376 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628006] [ 3813] 1000 3813 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628011] [ 3814] 1000 3814 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628017] [ 3815] 1000 3815 48533 11461 92 3 21706 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628022] [ 3816] 1000 3816 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628027] [ 3817] 1000 3817 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628032] [ 3818] 1000 3818 58765 15503 109 3 27247 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628038] [ 3819] 1000 3819 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628043] [ 3820] 1000 3820 1127 0 7 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628048] [ 3821] 1000 3821 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628173] [ 3846] 1000 3846 2441 0 11 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628179] [ 3848] 1000 3848 47513 9847 91 3 22204 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628184] [ 3849] 1000 3849 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628189] [ 3850] 1000 3850 48672 11175 92 3 22321 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628194] [ 3851] 1000 3851 1127 0 8 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628199] [ 3852] 1000 3852 1127 0 8 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628205] [ 3854] 1000 3854 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628210] [ 3855] 1000 3855 48538 11944 91 3 21768 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628215] [ 3856] 1000 3856 2441 0 9 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628221] [ 3857] 1000 3857 47512 10124 90 3 22093 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628241] [ 3864] 1000 3864 46486 9017 87 3 22082 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628247] [ 3865] 1000 3865 47509 10419 89 3 21974 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628252] [ 3867] 1000 3867 46997 9688 88 4 22206 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628257] [ 3868] 1000 3868 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628262] [ 3869] 1000 3869 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628268] [ 3874] 1000 3874 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628273] [ 3876] 1000 3876 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628278] [ 3877] 1000 3877 49072 12189 95 4 21509 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628283] [ 3880] 1000 3880 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628288] [ 3882] 1000 3882 46479 9303 88 4 22071 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628294] [ 3883] 1000 3883 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628299] [ 3884] 1000 3884 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628304] [ 3886] 1000 3886 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628310] [ 3887] 1000 3887 49075 12341 93 3 21515 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628315] [ 3888] 1000 3888 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628320] [ 3889] 1000 3889 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628325] [ 3891] 1000 3891 48010 10615 92 3 22011 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628331] [ 3893] 1000 3893 2440 0 10 3 44 0 gcc
Sep 18 10:00:44 ford2 kernel: [56168.628336] [ 3894] 1000 3894 48033 10792 92 3 21894 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628341] [ 3896] 1000 3896 1127 0 8 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628346] [ 3897] 1000 3897 21198 2969 44 4 6286 0 cc1
Sep 18 10:00:44 ford2 kernel: [56168.628351] [ 3898] 1000 3898 1127 0 8 4 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628357] [ 3900] 1000 3900 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628362] [ 3901] 1000 3901 1127 0 7 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628367] [ 3903] 1000 3903 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628373] [ 3905] 1000 3905 47073 11599 88 3 19226 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628378] [ 3906] 1000 3906 1127 0 8 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628383] [ 3907] 1000 3907 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628388] [ 3908] 1000 3908 1127 0 9 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628394] [ 3909] 1000 3909 47026 11122 87 3 19366 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628399] [ 3911] 1000 3911 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628404] [ 3912] 1000 3912 46519 9958 84 3 19861 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628409] [ 3913] 1000 3913 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628414] [ 3915] 1000 3915 46539 10833 86 3 19522 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628420] [ 3919] 1000 3919 59286 8869 111 4 33738 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628425] [ 3952] 1000 3952 1127 0 9 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628430] [ 3956] 1000 3956 1127 0 8 4 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628436] [ 3957] 1000 3957 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628441] [ 3960] 1000 3960 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628446] [ 3966] 1000 3966 59283 9602 113 3 33248 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628452] [ 3967] 1000 3967 59289 9509 111 3 33594 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628457] [ 3982] 1000 3982 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628462] [ 3984] 1000 3984 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628468] [ 3986] 1000 3986 1127 0 7 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628473] [ 3987] 1000 3987 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628478] [ 3990] 1000 3990 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628483] [ 3992] 1000 3992 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628488] [ 3993] 1000 3993 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628494] [ 3994] 1000 3994 59285 9008 111 3 33644 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628499] [ 3996] 1000 3996 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628504] [ 3999] 1000 3999 59301 9391 109 3 33475 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628510] [ 4001] 1000 4001 59281 8959 112 4 33768 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628515] [ 4004] 1000 4004 1127 0 9 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628520] [ 4005] 1000 4005 58777 8739 111 4 33915 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628526] [ 4011] 1000 4011 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628531] [ 4015] 1000 4015 58757 9086 109 3 33590 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628536] [ 4019] 1000 4019 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628542] [ 4025] 1000 4025 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628547] [ 4028] 1000 4028 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628552] [ 4029] 1000 4029 59811 11133 113 3 31966 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628558] [ 4032] 1000 4032 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628563] [ 4036] 1000 4036 58770 8511 109 3 33979 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628568] [ 4039] 1000 4039 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628573] [ 4041] 1000 4041 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628579] [ 4042] 1000 4042 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628584] [ 4045] 1000 4045 58779 8157 110 3 34222 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628589] [ 4046] 1000 4046 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628595] [ 4051] 1000 4051 59295 9425 109 3 33478 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628616] [ 4298] 1000 4298 1127 0 8 3 28 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628621] [ 4304] 1000 4304 2441 0 10 3 46 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628626] [ 4308] 1000 4308 48101 12883 89 3 18580 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628632] [ 4443] 1000 4443 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628637] [ 4446] 1000 4446 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628642] [ 4453] 1000 4453 57042 23488 105 3 17021 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628647] [ 4463] 1000 4463 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628652] [ 4464] 1000 4464 2441 0 11 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628658] [ 4465] 1000 4465 48102 13613 86 3 18375 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628663] [ 4490] 1000 4490 1127 0 8 3 29 0 bk-deps
Sep 18 10:00:44 ford2 kernel: [56168.628668] [ 4501] 1000 4501 2441 0 10 3 45 0 g++
Sep 18 10:00:44 ford2 kernel: [56168.628674] [ 4553] 1000 4553 67589 36699 126 3 14622 0 cc1plus
Sep 18 10:00:44 ford2 kernel: [56168.628679] [ 5426] 0 5426 10959 256 22 3 391 0 systemd-journal
Sep 18 10:00:44 ford2 kernel: [56168.628685] [ 6503] 0 6503 131354 2703 140 3 8 0 Xorg
Sep 18 10:00:44 ford2 kernel: [56168.628691] [ 6670] 0 6670 7160 104 19 3 0 0 systemd-logind
Sep 18 10:00:44 ford2 kernel: [56168.628697] [ 6672] 0 6672 11199 225 22 3 1 -1000 systemd-udevd
Sep 18 10:00:44 ford2 kernel: [56168.628702] [ 6693] 1000 6693 27988 4938 59 3 2 0 apt-check
Sep 18 10:00:44 ford2 kernel: [56168.628708] [ 6806] 0 6806 4317 47 14 3 0 0 anacron
Sep 18 10:00:44 ford2 kernel: [56168.628714] [ 6841] 0 6841 1126 17 8 3 0 0 sh
Sep 18 10:00:44 ford2 kernel: [56168.628719] [ 6842] 0 6842 1091 26 8 3 0 0 run-parts
Sep 18 10:00:44 ford2 kernel: [56168.628725] [ 7108] 121 7108 16869 111 25 3 0 0 pickup
Sep 18 10:00:44 ford2 kernel: [56168.628730] [ 7149] 0 7149 3513 53 12 3 0 0 mlocate
Sep 18 10:00:44 ford2 kernel: [56168.628736] [ 7158] 0 7158 3265 22 12 3 0 0 flock
Sep 18 10:00:44 ford2 kernel: [56168.628741] [ 7159] 0 7159 2209 48 10 3 0 0 updatedb.mlocat
Sep 18 10:00:44 ford2 kernel: [56168.628747] [ 7176] 0 7176 61164 233 54 3 0 0 lightdm
Sep 18 10:00:44 ford2 kernel: [56168.628752] [ 7215] 108 7215 1126 17 8 3 0 0 lightdm-greeter
Sep 18 10:00:44 ford2 kernel: [56168.628758] [ 7222] 108 7222 1549 10 7 3 0 0 dbus-launch
Sep 18 10:00:44 ford2 kernel: [56168.628762] Out of memory: Kill process 4553 (cc1plus) score 7 or sacrifice child
Sep 18 10:00:44 ford2 kernel: [56168.628777] Killed process 4553 (cc1plus) total-vm:270356kB, anon-rss:146796kB, file-rss:0kB
Sep 18 10:13:17 ford2 rtkit-daemon[1668]: Demoting known real-time threads.
Sep 18 10:18:09 ford2 kernel: [57377.534222] apport invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=0
Sep 18 10:18:22 ford2 kernel: [57377.534231] apport cpuset=/ mems_allowed=0
Sep 18 10:18:22 ford2 kernel: [57377.534242] CPU: 3 PID: 7237 Comm: apport Not tainted 4.4.0-124-generic #148-Ubuntu
Sep 18 10:18:22 ford2 kernel: [57377.534251] 0000000000000286 23f3f2bd8e876696 ffff88009fac79f8 ffffffff813ffb53
Sep 18 10:18:22 ford2 kernel: [57377.534257] ffff88009fac7bb0 ffff8801de91a640 ffff88009fac7a68 ffffffff8120febe
Sep 18 10:18:22 ford2 kernel: [57377.534262] 0000000000000015 0000000000000000 ffff8800cdce8540 ffff8800cb060cc0
Sep 18 10:18:22 ford2 kernel: [57377.534267] Call Trace:
Sep 18 10:18:22 ford2 kernel: [57377.534279] [<ffffffff813ffb53>] dump_stack+0x63/0x90
Sep 18 10:18:22 ford2 kernel: [57377.534287] [<ffffffff8120febe>] dump_header+0x5a/0x1c5
Sep 18 10:18:22 ford2 kernel: [57377.534294] [<ffffffff81397b74>] ? apparmor_capable+0xc4/0x1b0
Sep 18 10:18:22 ford2 kernel: [57377.534301] [<ffffffff81196512>] oom_kill_process+0x202/0x3c0
Sep 18 10:18:22 ford2 kernel: [57377.534306] [<ffffffff81196939>] out_of_memory+0x219/0x460
Sep 18 10:18:22 ford2 kernel: [57377.534313] [<ffffffff8119c985>] __alloc_pages_slowpath.constprop.88+0x965/0xb00
Sep 18 10:18:22 ford2 kernel: [57377.534320] [<ffffffff8119cda8>] __alloc_pages_nodemask+0x288/0x2a0
What can I do? Is this normal that one can crash an Ubuntu installation that easily? Crash it with user privileges?
I installed gnome maps (apt install gnome-maps) on Xubuntu 16.04. It is a great tool and running fine. The only problem is that I do not understand how to use the search function. When I enter a place in the search bar, I get a suggestion list with the correct city and country etc, but whatever I select or type nothing happens.
I would expect when I enter Paris,France and select it from the offered List, to tool centers Paris and put a cursor on it. I can not figure out how to do that. What am I missing?
I had been installing a paravirtualized (PV) guest with Xen on a Logical volume(LV). The installation has seen the LV as a normal hard disk and installed and ext4 and a swap partition on it.
The output of sudo fdisk -l|grep /dev is
Disk /dev/mapper/vg1/lv1: 40GB
/dev/mapper/vg1-lv1-part1 37G 83 Linux
/dev/mapper/vg1-lv1-part2 3 5 Extended
/dev/mapper/vg1-lv1-part3 3 82 swap
I can use fdisk to modify those partitions like that
sudo fdisk -l /dev/mapper/vg1-lv1
But did not manage to mount the partitions anywhere. I tried
sudo mount /dev/mapper/vg1-lv1-part1 /mnt/tmp // special device does not exist
sudo mount /dev/mapper/vg1-lv1 /mnt/tmp // wrong fs type error
sudo mount /dev/vg1/lv1/ /mnt/tmp // wrong fs type error
sudo mount /dev/vg1/lv1/part1 /mnt/tmp // special device does not exist
So how do I mount the /dev/mapper/vg1-lv1-part1 partition to /mnt/tmp?
I noted that apt-mirror does not copy the full repository. I would like to make it copy all of it. Any I idea how that can be done?
This is what is on the server for Xenial/Main
[DIR] binary-amd64/ 2016-04-21 19:39 -
[DIR] binary-i386/ 2016-04-21 19:39 -
[DIR] debian-installer/ 2015-12-02 22:22 -
[DIR] dep11/ 2016-04-21 13:13 -
[DIR] dist-upgrader-all/ 2016-04-16 18:13 -
[DIR] i18n/ 2016-04-21 19:39 -
[DIR] installer-amd64/ 2017-12-01 16:17 -
[DIR] installer-i386/ 2017-12-01 16:17 -
[DIR] source/ 2016-04-21 19:39 -
[DIR] uefi/ 2015-11-02 23:53 -
This is what I got
[DIR] binary-amd64/ 2016-04-21 19:39 -
[DIR] binary-i386/ 2016-04-21 19:39 -
[DIR] dep11/ 2016-04-21 13:13 -
[DIR] i18n/ 2016-04-21 19:39 -
[DIR] source/ 2016-04-21 19:39 -
Edit: one thing I already found out. To include the debian-installer/ section, add in the mirror.list file
deb http://archive.ubuntu.com/ubunut xenial main main/debian-installer restricted restricted/debian-installer universe multiverse
This works because apt-mirror finds a packages.gz file there. With other folders this does not work, e.g. installer-amd64.
Before downloading PPAs with apt-mirror I need to have the PPA GPG key installed in my key ring, e.g. by using the command
add-apt-repository ppa:something/ppa
After this (and editing mirror.list) apt-mirror downloads the PPA files to a local repository. Apt-mirror does not seem to include the keys into the local archive.
Are the PPA keys also required when installing directly from the lokal (mirrored) repository?
This question is related to this: apt-mirror: can't create /dir:/mirror directory at /usr/bin/apt-mirror line 342 But the answer there did not help, because the setup is a bit different.
I need to run apt-mirror to store onto an external USB HDD, NTFS formatted. Running apt-mirror runs into the same error as user Miphix in his post.
As given in the man page I am used
su - apt-mirror -c apt-mirror
and get this error
apt-mirror: can't create /media/usb/apt-mirror/mirror directory at /usr/bin/apt-mirror line 342
which is cause by trying to create a directory where there is a directory already.
The answer to run apt mirror as user apt-mirror does not work on an USB HDD with NFTS, because after mounting the drive chown apt-mirror:apt-mirror {dir} does nothing. This is according to Cannot chmode and chown on a ntfs usb drive, because on external USB drives with NTFS there is only a default ownership.I tried changing the mount directory, but it was converted to root:root after the mount.
Since a new download would be 130GB and would take several days, I need to use the existing repostory and just do an update. Also I can not copy it to the local hard drive, because not enough space.
Any ideas?
I looked at many posts about this problem, but I could not find one that solved mine.
After I suspend or sleep my computer, it wakes up. I know because CtrlAltF1 shows me a console. But my desktop screen remains black and is unresponsive.
How can I wake up my desktop from a working console on the same computer?
What I've tried:
- Running
set -display $DISPLAY dpms force ondid not work, but it did give meunable to open display "". Same thing when I tried to setDISPLAY=:0manually. sudo sysctrl unlock-session: nothing happened- I can't reproduce this yet, but twice I've gone to a graphical message like
your screen is locked. You will be forwarded to the unlock dialog(can't recall the exact wording). But the screen ends up going black again. startxon the F1 console started an empty desktop fine. So in principle, graphics capabilities are there.sudo system lightdm restartwakes that screen with a login dialog. Since it kills all running applications it's not really helping.- Found some other bounty question with references to
light-lockerandxscreensaver. Never heard of either before, but followed what I read there. So I purgedlight-lockerand installedxscreensaver xscreensaver-data xscreensaver-gl. After I logged in, I was asked to confirm to disable thelightlocker daemonwhich I did. But the problem remained. Maybe I need to do something else?.
Used Systems
- Xubuntu 16.04, latest update
- Desktop PCs, Atom CPU's /Intel on Board Graphics Cards
- the problem is with several motherboards
- Monitors: standard VGA noName TFTs
After looking at about some 50 posts about web radios I think my issue had not been asked yet.
Do you still know those shabby old transistor radios playing in some corner or window sill in offices or workshops? Their tuning wheels are so bad that nobody ever touches them again once a station had been tuned. Also the volume knob is cracking horribly, so they are plugged in in the mornings and unplugged by the last one leaving the office. That's exactly what I want.
Ideally, this would be a fixed On/Off Icon somewhere in the Panel bar. No window at all. Press it once and the configured web radio stream starts playing. Press again it stops. The radio station is defined by the http address of an m3u file for the stream.
I did not find a app that works like that. I hope I just overlooked the one that exactly fits what I want and you guys can point me to the right one.
Best I found so far was gnome mplayer, but I am not really happy with it.
Its a normal appication. It reduces to a small icon in the panel bar which is good. On/Off is, open the Icon then press Play/Stop - which would be ok. Not OK is that I can't make it to just play the last stream. Every time it starts I need to open File/Open Location and copy&paste the http address of the m3u file from a text file on the drive. It would be OK for me when there is a way to autostart it with the right stream automatically loaded but not playing. I had tried to put the stream address into a file and used "Open Recent". It say "start playing" but then stops. This is how the file looked like.
#EXTM3U
#EXTINF:-1, Web Radio
http://some-webradioaddress.com/streamfile.m3u
So Is there a tool that already does what I want? Is there a way to make mplayer behave like I need? If no, how to achieve that by other means using command line apps and scripts or whatever?
Thanks für your creative input, CatMan
Scenario
- I have 2 working Ubuntu partitions on my hard drive, let's call them A and B. They use a single swap partition.
- I have booted into A and logged into the desktop. Now I want to make partition A larger (there is enough space) without reboot.
Question
Can I use chroot to
- switch execution to B and then unmount partition A.
- Then from B start gparted and resize partition A.
- Then (in B) mount A into a /mnt/temp and use chroot to switch execution back to A?
Please comment or answer if you know whether or not that is possible at all. Even when you do not know the exact steps. It would already help me and is a lot better than no answer at all.
Of course more helpful would be a step by step command line procedure to go to B, unmount partition A and how to start the graphical gparted.
What I did
- I used chroot to switch from a live CD or other partition to fix grub. It was in text mode only. I used the standard procedure that is explained in many posts (mount other partition, mount --bind the virtual folders and then move with chroot to the mounted drive).
- I created a clone of A to a newly created partition B. The clone works fine and completely when booted from grub, so I know its fully functional. I did access the command line with chroot ('#' prompt) from A.
- I did not find a way to start a desktop in B, or fully switch over to work in B like if I would have rebooted the system into B.
- I did not see another post that contained that question
I use nemo file manager on Xubuntu 16.04.
I have connected several network shares. I have also bookmarked them. In nemo I can access all files. When I try to open a file with an application I do get a standard file open dialog that does not have those shares. There is "Other locations" but that only gives the mounted driver. No bookmarks, no network shares.
In essence, I do not know how to open any network file in Xubuntu with an application. Only workaround I see is to copy all files to home, open them there and when done store them back to a network share. I am sure there must be another way. Please help!
PS: I think this is not specific to Xubnutu desktop. Its the same when I select thunar as preferred file manager.
I have newly installed Xubuntu desktop on a computer. I need to work with files on a NAS store (using samba shares). Libre Office can not open them.
- I browse the network in Thunar and see all files. The are recognised as Open Office files (right icon).
- I can copy files to my desktop.
- I can open the files with gedit.
- On double click I see the Libre Office5 splash sceen then then nothing happens. I do not get any error message.
- When I open Libre Office I can browse to the file with the open dialog but after file selection, I am just back to the blank file.
- I can edit the file after copying it to my desktop.
After uncommemting
X-GIO-NoFuse=truein the config file I do get an error when trying to open the file:General input/output error while accessing run/user/1000/gvfs/smb-share:server=, share=".
- I have read about a bug to disable
/use/share/applications/libroffice-calc.desktopand comment out x-KDE prototocls, but that did not help. The question is Can't open files through the network.
I did not try to mount the network share with fstab, since I need to be able to work with temporary shares in the file manager.
Anyone else having that problem? How can I solve that?
Using Xubunutu 16.04, amd64, kernel 4.4.0.-64-generic.
EDIT: rewording to be not "opinion-based" any more.
What command line text editor in the Ubuntu repository has or can be set to allow the following behavior?
- first key presses do already start text entry.
- numpad keys are supported.
- Cursor keys to move in lines and between lines with Ctrl-right/left to move word-wise, and Ctrl-Up/DN to scroll the text up/dn on current position.
- Shift-cursor keys for marking text (letters,words,lines,multiple lines). Ctrl-Shift-Cursor, Shift-PageUn/Down accordingly
- Copy and paste with Ctrl-X/C/V
- Copy and paste with Shift-Del/Shift_Ins
- Working Ins, Del, Pos1, End, PageUp, PageDn keys like e.g. open office
- Alt-c to toggle column mode for marking. That is a very advanced function, so maybe optional.
- Tab key setting need to be definable on how many column it indents
- Ctrl-S to save
If an editor needs be configured to behave like that, it would help to know if you are aware if someone already tried/achieved something like this.
I have a local net with no internet and want to keep all computers in there time synced. I do not care about the absolute time, it should just be the same for all.
I found several posts about this. The most useful ones were:
server
I did setup the server with the IP 192.168.1.123 and it seems to be working ok: The deamon "ntpd" is running and I had been adding in etc/ntp.conf the lines
# this sets the source to local time
server 127.127.1.0
fudge 127.127.1.0 stratum 8
# this makes the ntpd deamon to send out its time on the local net.
broadcast 192.168.255.255
I verified it with the ntpq command:
ntpq -c lpeer
remote refid st t when poll reach delay offset jitter
==============================================================================
192.168.255.255 .BCST. 16 B - 64 0 0.000 0.000 0.000
"BCST" says its in broadcast more and the IP shows its broadcasting to all computers on the local net (a B class network, thus 2x 255).
client
On client side I also installed ntp, and used the default /etc/ntp.conf and added the lines
server 192.168.1.123 iburst
server 127.127.1.0
fudge 127.127.1.0 stratum 8
where 192.168.1.123 is the local IP of the server broadcasting and the other line should tell the client (a laptop) to use its own clock when the network connection is off. I restarted the service on the client and ran ntpq to check the connection
ntpq -c lpeer
remote refid st t when poll reach delay offset jitter
==============================================================================
192.168.1.123 .INIT. 16 u 1 64 0 0.000 0.000 0.000
LOCAL(0) .LOCL. 8 l 6 64 1 0.000 0.000 0.000
Repeating this command I can see the "when" column counting up both and starting with 0 again when reaching 64sec. I did expect after the 64 sec this would change to this:
ntpq -c lpeer
remote refid st t when poll reach delay offset jitter
==============================================================================
*192.168.1.123 .INIT. 16 u 1 64 0 0.000 0.000 0.000
LOCAL(0) .LOCL. 8 l 6 64 1 0.000 0.000 0.000
Note the "*" before the server IP. But it did not. What I got after about 1hr was
ntpq -c lpeer
remote refid st t when poll reach delay offset jitter
==============================================================================
192.168.1.123 .INIT. 16 u 1 64 0 0.000 0.000 0.000
*LOCAL(0) .LOCL. 8 l 63 64 377 0.000 0.000 0.000
I think this tells me, there are 2 sources for NTP configured, but as the remote source is not working/not available/whatever it is not used and the fallback case local clock is used, but I am not sure if that interpretation is correct.
what I tried
I waited more than 1hr, I restarted the ntpd serveral times with sudo /etc/init.d/ntp restart and I also rebooted. Further I commented out the local section clock so that the only server was server 192.168.1.123. I could not get that "*" to appear. Also I saw a section in the ntp.conf that said
#if you want to listen to time broadcasts on you local subnet,
#de-comment the next lines. Please do this only if you trust
#everybody on the network!
#disable auth
#broadcastclient
I tried un-commenting and restarting the service but still that star did not appear. I am wondering about the last section, though, because this section did turn up in any other post or internet result that I saw on the ntp configuration. There are several ones on local setups and most seem to be find with the server address alone. Ping from client to server is fine. There is not firewall etc.
question
I am out of ideas. I think I have a server with fully working ntp server which is sending out the time. But I do have a client which is failing to receive the time information from the server.
What can I do to get the client running?
On my command line in Ubuntu Server 16.04.1 , I would like to bind Ctrlup/down to the bash history incremental search function. I found some posts how to do it. They involve the ~/.bashrc and ~/.inputrc files.
Strange characters appearing when I use the Ctrl and Arrow keys to navigate says this works via the .inputrc file in the home directory. Why does ctrl + left arrow not skip words? contains comments about not using .inputrc, about using .zshrc and using .bashrc. I am still too new to not be confused.
I did not have any .inputrc in my fresh server install.
I do not understand those things:
- is .inputrc the right place to put in key bindings in 16.04?
- Is that the same for all different flavours als older version of ubunutu?
- it is normal to have no .inputrc file in my home directory?
- What is recommended : copy the /etc/input to home and edit or make a link in a new .inputrc and edit the file in etc?
I did not get it to work, too. I tried both copying the file from etc and rename it to .inputrc and also creating a new file in ~/ with:
touch .inputrc
nano .inputrc
The file content:
$include /etc/inputrc
Here is the what I put into the files.
# mappings for Ctrl-left-arrow and Ctrl-right-arrow for word moving
"\e[1;5C": forward-word
"\e[1;5D": backward-word
"\e[5C": forward-word
"\e[5D": backward-word
"\e\e[C": forward-word
"\e\e[D": backward-word
# ctrl up,down
"\e\e[A": history-search-backward
"\e\e[B": history-search-forward
Both do not work, Ctrl key is ignored. CTRLUp/down do not show the search and CTRLleft/right do not skip words. I think it matches the answer of the seconds post.
What could be the problem?
Re-edited to reflect latest findings:
Overview
My Atom D410 micro PC with Intel GMA3150 got a dual boot with Win7x64 and Ubuntu16.04. Ubuntu was installed second but does not fully boot. The PC has a single TFT Monitor, 1989x1020 resolution, connected via VGA and an USB keyboard and an USB mouse. Single 250GB HDD. Win7 runs stable without any graphics glitches for a few years on that machine.
Problem
Normal boot fails. Everything is fine until logging in on the desktop. Then I get a funny picture (see first image) for some 10-20sec, then the a black screen with mouse pointer only (second image). It flickers unevenly for about 30 secs. After that an empty standard background flickes in when I move the mouse the the screen edge or when I press keys. The system stays like that, no disk acitvity, no icons, no dock. I learned that Ubuntu has been installed to such systems sucessfully, so I hope there will be a sultion to it.
What I checked
- I can use the console to login and work there. It does not change the main screen
- I re-installed the driver xserver-xorg-video-intel, no change.
- the graphics driver for the GMA3150 ist correctly installed (thanks CelticWarrior)
I can fully boot via Grub's Recovery option in FailsafeX mode. System is very slow (software graphics emulation) and generic screen is low res. During recovery boot it hangs at one place and I need o use Ctrl-C to make it continue
Gtk-Message: gtkDialog mapped without a transient parent. This is discouraged/use/share/xdiagnose/failsaveXinit: line 177: return: zenity: numeric argument required
I installed Ubuntu twice, first time I upgraded to 16.10 and tried out the intel ungrade tool and other drivers suggested in various forum posts. I tried to change the screen resolution in failsafe with xrandr and cvt but got the error "Failed to get size of gamma for output default" where I did not find a solution in the forum.
- For the second time I did a clean reinstall, formatting the partitions. I ran a disk check on the installation usb. I booted the live mode and tested the system. It ran fast. It showed the right Intel graphics driver and it recognized the screen and set its 1980x1020 resolution. Only thing I noted was that it seemed to have an "build-in display" beside the external screen. But there is not build-in display and the system only has one VGA connector. I disabled that build-in display and everything was fine. Maybe thats a hint to whats wrong here? Then I installed it from the live desktop.
here is the output from "lspci -vnn|grep VGA -A 12"
00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a001] (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [105b:0d55] Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fea80000 (32-bit, non-prefetchable) [size=512K] I/O ports at dc00 [size=8] Memory at d0000000 (32-bit, prefetchable) [size=256M] Memory at fe900000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i91500:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition Audio Controller [8086:27d8] (rev 02)
I found two posts about flickering with intel i915 drivers. They suggested to add "i915.enable_psr=0" to thedefault grub boot options. I did that but nothing changed. I also added "/etc/modeprob.d/i915.conf" with the line
option i915 enable_rc6=6 enable_psr=2 enable_fbc_1 lvsd_downclock=1 semaphores=1
but there was no change, either.
Here the ouput from "sudo lshw -c display"
*-display description: VGA compatible controller product: Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 00 width: 32 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:27 memory:fea80000-feafffff ioport:dc00(size=8) memory:d0000000-dfffffff memory:fe900000-fe9fffffoutput from "lsb_release -a".
No ldb modules availableoutput from "xrandr". Shouldn't there be display outputs?
can't open display
Note the different overlaid bachground images above
Thanks in advance for any further suggestions.
CatMan
PS: the boot log was too long to enter here