Using an Ubuntu linux, what is the best/easiest way to print multiple images per page?
The global number of images and pages and the requested number of images per page should be dynamically chosen.
On my Ubuntu 20.04.1 tablet I try to get WWAN working.
But after insert of the SIM card, there is no prompt for the SIM PIN. Therefore, the ttyHS2 device is "not available", I assume (if this may be a different problem, please advise! :) ).
I know that network manager always was dense in asking for the SIM PIN. Therefore, I tried to do this via CLI. But the new network manager cli utility has a complete new syntax, which is why 99% of search machine founds does not help!
$ nmcli --version
nmcli-Werkzeug, Version 1.22.10
The complete man page of nmcli does not contain the phrase "pin" (as own word). Does anyone know how this is possible??
Of course: I made thousands of restarts, reinserted the SIM card many times, enabled/disabled the whole network stuff multiple times via UI.
When setting GRUB_DEFAULT to:
Ubuntu 18.04.1 LTS (18.04) (auf /dev/nvme0n1p2)
update-grub emits a warning (3 times) that I should not use this "old title", but should use one of the following, depending on my "version".
For versions pre 2.00:
Advanced options for Ubuntu 18.04.1 LTS (18.04) (auf /dev/nvme0n1p2)>Ubuntu 18.04.1 LTS (18.04) (auf /dev/nvme0n1p2)
For versions 2.00 or higher:
gnulinux-advanced-c40111ac-c9cb-43b2-b72b-e6d86975cd57>gnulinux---c40111ac-c9cb-43b2-b72b-e6d86975cd57
I assumed that this warning means the grub version with "version". So I picked the latter format, as my grub is 2.02-2ubuntu8.
But it didn't worked. When changing back to the "old title" it works again.
Warnung: Bitte verwenden Sie nicht den alten Titel »Ubuntu 18.04.1 LTS (18.04) (auf /dev/nvme0n1p2)« für GRUB_DEFAULT, verwenden Sie »Advanced options for Ubuntu 18.04.1 LTS (18.04) (auf /dev/nvme0n1p2)>Ubuntu 18.04.1 LTS (18.04) (auf /dev/nvme0n1p2)« (für Versionen vor 2.00) oder »gnulinux-advanced-c40111ac-c9cb-43b2-b72b-e6d86975cd57>gnulinux---c40111ac-c9cb-43b2-b72b-e6d86975cd57« (für 2.00 oder neuer)
Why shouldn't I use the normal "old" title and what would be the correct title then? Or should I ignore this message?
System informations:
Linux htpc7even3 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
I tried to set up automated processing of imported pictures and videos from the digicam.
Custom Script
me@mymachine ~ $ ll /home/me/scripts/autorename-avmedia-exif.sh
-rwxr-xr-x 1 me me 603 Aug 7 22:50 /home/me/scripts/autorename-avmedia-exif.sh*
Contents:
#!/bin/bash
# Argument
if [ $# -eq 1 ] ; then
# Only one argument
file=$1
else
# No argument
echo "Usage: $0 target-file"
exit 1
fi
/bin/echo "$0 started" > /home/me/tmp/autorename.log
exiftool -overwrite_original_in_place -P '-filename<CreateDate' -d "%Y-%m-%d %H-%M-%S%%-c.%%le" "$file"
echo "exiftool returned: $?" >> /home/me/tmp/autorename.log
Incron Permissions:
me@mymachine ~ $ sudo cat /etc/incron.allow
me
root
Incron Watch:
me@mymachine ~ $ incrontab -l
/home/me/Bilder/Import IN_CLOSE_WRITE /bin/bash /home/me/scripts/autorename-avmedia-exif.sh "$@/$#" > /home/me/tmp/autorename-avmedia-exif.log
Syslog:
Aug 7 22:36:26 mymachine incrond[1391]: (me) CMD (/bin/bash /home/me/scripts/autorename-avmedia-exif.sh "/home/me/Bilder/Import/DSC01037.JPG" > /home/me/tmp/autorename-avmedia-exif.log)
Problem: Nothing happens. The script is not executed.
When copy past'ing the line from syslog into a terminal, the script works without a problem.
Replacing the script call with touch /home/me/tmp/test.incron works and the test file is created.
So this has to be an environmental problem, but I already prefixed the script call with /bin/bash and added full paths. What else is missing?
Is there a possibility to define a monitor area within/over an arbitrary application window that is in background?
The content of this area either should be displayed somewhere else (always on top). Alternatively a notification should be made on any (pixel) change within the monitored area.
The monitor area should:
- be a free selection
- stick to the window, even/especially if it is in background
- ideally be saved and automatically be reapplied, based on the same window title
The notification should be:
- positioned independently from the source monitor area
- able to be configured always on top
- able to handle multiple monitor area feeds
Similar implementations:
- Compiz window previews in scale plugin
- Cairo dock window previews
- RecordMyDesktop free selection of recording area
Summary: The ideal solution should combine the above mentioned implementations in a new way: free selection of a monitor area (from RecordMyDesktop), live monitor of windows in background (from Compiz scale plugin) and completely different target display of monitored content (from Cairo window previews)
Partially related:
I just found the following comment in /etc/login.defs:
# Enable setting of the umask group bits to be the same as owner bits
# (examples: 022 -> 002, 077 -> 007) for non-root users, if the uid is
# the same as gid, and username is the same as the primary group name.
This sounds cool, but it doesn't behave like that on my system:
me@mysystem ~ $ id
uid=1000(me) gid=1000(me) Gruppen=1000(me),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),113(lpadmin),130(sambashare),133(roccat)
me@mysystem ~ $ touch test
me@mysystem ~ $ ll test
-rw-r--r-- 1 me me 0 Aug 17 20:02 test
me@mysystem ~ $ rm test
me@mysystem ~ $
(following replacements were made (nothing else): my_real_user_and_groupname => me, my_real_hostname => mysystem)
My primary group is my personal group (as the group assignment of the test file shows), but I don't know a CLI command to check this. I checked it via GUI instead.
Anyone knows why the behaviour described in this comment does not affect my environment?
Or cleaner: why is test created with -rw-r--r-- instead of -rw-rw-r-- on my system?
Update:
me@mysystem ~ $ cat .bashrc | grep -e umask -e UMASK
me@mysystem ~ $ cat .profile | grep -e umask -e UMASK
# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022
me@mysystem ~ $ cat /etc/profile | grep -e umask -e UMASK
me@mysystem ~ $ cat /etc/bash.bashrc | grep -e umask -e UMASK
me@mysystem ~ $ umask
0022
me@mysystem ~ $
Update 2
me@mysystem / $ grep -r 'umask [0-9]' /etc/ 2> /dev/null
/etc/init/ssh.conf:umask 022
/etc/ppp/ip-down.d/0dns-down:umask 022
/etc/ppp/ip-up.d/0dns-up:umask 022
/etc/dhcp/dhclient-enter-hooks.d/samba: umask 022
/etc/init.d/umountfs:umask 022
/etc/init.d/ssh:umask 022
/etc/init.d/resolvconf: umask 022
/etc/init.d/urandom: umask 077
/etc/init.d/urandom: umask 022
/etc/init.d/urandom: umask 077
/etc/init.d/rc:umask 022
/etc/skel/.profile:#umask 022
/etc/X11/Xsession:if (umask 077 && touch "$ERRFILE") 2> /dev/null && [ -w "$ERRFILE" ] &&
me@mysystem / $
recently I encountered that on my system our german IPTV RTP streams don't work anymore. It still works on other systems in the same network.
VLC error:
Ihre Eingabe konnte nicht geöffnet werden:
VLC kann die Medienadresse 'rtp://@239.35.20.59:10000' nicht öffnen. Für Details bitte im Fehlerprotokoll nachsehen.
VLC error log:
-- logger module started --
core: VLC wird mit dem Standard-Interface ausgeführt. Benutzen Sie 'cvlc', um VLC ohne Interface zu verwenden.
core error: socket bind error: Address already in use
core error: open of `rtp://@239.35.20.59:10000' failed
smplayer error:
Playing rtp://@239.35.20.59:10000.
STREAM_RTP, URL: rtp://@239.35.20.59:10000
Failed to connect to server
rtp_streaming_start failed
No stream found to handle url rtp://@239.35.20.59:10000
System properties:
me@mysystem ~ $ uname -a
Linux sesta10 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
me@mysystem ~ $ lsb_release -a
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: LinuxMint
Description: Linux Mint 18.3 Sylvia
Release: 18.3
Codename: sylvia
me@mysystem ~ $
System where it works:
me@othersystem:~$ uname -a
Linux server7even3 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 GNU/Linux
me@othersystem:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 9.4 (stretch)
Release: 9.4
Codename: stretch
me@othersystem:~$
I really don't understand the error message of vlc, as to my understanding the remote address is a multicast (or something like that?), and cannot be in use therefore. Does it mean the local socket instead? But why should vlc choose a local socket that is in use already?
The smplayer error simply is wrong, because it works on other systems.
Any help, hint or different media player to try?
I am sorry if this question has an answer already somewhere, but as it is highly specific, all my search queries returned standard questions/answers corresponding to the backup topic in general.
What I am not asking for:
- How to backup data
- How to backup the system
- General backup tools and their features
My question:
What is the most efficient way to backup an entire harddisk, having multiple partitions, to an identical harddisk (mirror disk) that is kept offline and powered on manually only to update its content?
Definition of efficient for this question: least performance implication on the system (CPU, I/O load on source harddisk), no requirement for manual interaction (no UI application) and reliable mechanism (don't want to fix sync errors all the time)
My ideas:
The following alternative commands should be started automatically, as soon as the mirror disk is powered on. Displaying a progress via e. g. desktop notification is minor.
- Run rsync for each partition
- Pros:
- Default tool for tasks like this
- Should be quite efficient
- Supports incremental updates (sync)
- Cons:
- Has to be set up for each partition/updated on partition changes
- Overhead of working on filesystem level?
- Pros:
- Run command (dd?) for the whole disk
- Is there a tool on disk level that supports "syncing" differences to a mirror disk only?
- Will operations on disk level be more performant than rsync on filesystem level?
- Use raid 1
- Will a raid 1 setup operate reliably if one of the disks is offline most of the time?
- Are there unwanted side effects of the permanent degraded raid 1 array in normal operation?
- Is raid 1 able to sync differences efficently (or is it designed to rather sync securely)?
- May there be problems if the differences grow too large?
- There are both, hardware and software raid 1 options for my system - do they have different behaviours regardings the points above and this unusual use case in general?
- Is there another option?
At first glance, I favoured the raid 1 solution, cause the content mirroring requirement is exactly what raid 1s are made for. But as raid arrays are meant to work with online devices and the offline use case (device failure) should occur rarely only, I wonder if this solution is the most efficient approach for me.
Update: Partition/data characteristics
Partition characteristics (that may affect the performance comparisions):
- One partition will contain a linux operating system (75 GB)
- One is a swap partition (that may be omitted in the filesystem approach; but it is rarely used, so this should not be taken into account) (43 GB)
- One partition is designed for arbitrary data (may be big sized files, e. g. virtual machine disk files) (107 GB)
- The major partition (5,7 TB) is a luks encrypted container
- Filesystem is ext4 for all appropriate partitions
Update 2018-04-28:
As it turned out here that it is a non-trivial question to compare these different mechanisms, the best approach would be to try it out and measure the performance.
But in the meantime I realized that there is no need for an additional backup of all of the partitions except the luks partition (no need to backup the operating system partition, as it already is a backup of the real operating system on a SSD, no need to backup swap obviously and finally no need to backup the partition with arbitrary data). Therefore it was easy now to decide to go with the rsync approach, to just mirror the luks partition. The remaining space on the "mirror disk" is defined now as partition for manual backups - e. g. for data from foreign systems, which is a valuable additional "feature".
I am sorry to not having analyzed/answered the original question now, because technically it is quite interesting.
My new TV device is here with only HDMI inputs. But when connecting my Mythbuntu 12.04 box, the screen turns on for a second only. Then it is black for a while, then it displays "no signal" and after about a minute it turns on for a second again! (and so on) This even seem to be persistent behavior when rebooting the mythbuntu system!
But I found a hack: connect the DVI output of the mythbuntu system to my old TV device - works - disconnect it - connect the new TV via HDMI to DVI adapter to the DVI output the old TV device was connected before - voilà, the new TV turns on and shows the mythbuntu screen persistently!
The downside (besides the fact that I don't want to do this every time): the resolution is still the lower native resolution of the old tv and not the higher native resolution of the new tv.
When adjusting the resolution at this stage, everything starts from the beginning again. Connecting the old tv device via HDMI works without a problem, though. Therefore I am unable to blame a device, interface or protocol...
Nevertheless it seems that the new tv device has some protocol issues with the mythbuntu box and when connecting it via dvi to the old tv prior, the mythbuntu system seems to simply proceed with outputting the video signal - which can be connected to the new tv device then.
The xrandr output supports this theory:
htpc@htpc7even:~$ xrandr
Screen 0: minimum 320 x 200, current 1360 x 768, maximum 8192 x 8192
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1360x768+0+0 (normal left inverted right x axis y axis) 1280mm x 720mm
1920x1080 60.0 + 50.0 24.0
1600x1200 60.0
1680x1050 60.0
1400x1050 60.0
1280x1024 60.0
1440x900 59.9
1280x960 60.0
1280x800 59.8
1024x768 60.0
800x600 60.3
640x480 60.0
HDMI2 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
1360x768 (0x46) 85.5MHz
h: width 1360 start 1424 end 1536 total 1792 skew 0 clock 47.7KHz
v: height 768 start 771 end 776 total 795 clock 60.0Hz
htpc@htpc7even:~$
The new tv device supports up to 1920x1080
The old tv device supports up to 1360x768
The latter is the exact resolution for the signal informations at the bottom of the xrandr output which is not assigned to any of the output devices; so even xrandr seems to not know where this signal is send to.
Assuming, this is a complex issue, I request a two-step answer:
Workaround: is it possible to get the above described state without connecting the old tv device (or any other device) prior?
Final solution: well, how can I solve my issue?
Thanks in advance!
Mythbuntu system data:
Mainboard: Asus P7H55D-M EVO
Graphics: using onboard Clarkdale graphics!
System: Ubuntu 12.04.5 LTS
uname: 3.2.0-68-generic #102-Ubuntu SMP Tue Aug 12 22:02:15 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Desktop environment: standard Mythbuntu XFCE
Update
I booted my htpc machine with Ubuntu 14.04.1 via usb and this live environment was able to turn on my new tv persistently without a problem.
Because I wondered if XFCE may be the problem, I installed Gnome on the mythbuntu system, but this failed the same way as XFCE.
Additionally, I noticed that when booted up the mythbuntu system with both tvs connected (the old one via DVI and the new one via HDMI), the XFCE display settings dialog got confused and swapped the supported resolutions lists so that I am unable to adjust correct resolutions. For the old tv the name was assigned wrongly as well and the other name did not appeared and the entry was named "HDMI1" only. Previously I saw all kinds of informations there: HDMI1, HDMI2, name of the new tv, name of the old tv. Even xrandr listed the wrong resolutions per HDMI output.
Now I am not sure if this behavior was/is reproducible as I am logged into Gnome currently which listed the supported resolutions correctly and named the tv devices correctly.
After a full system backup I make a release upgrade just now to see if Ubuntu 14.04.1 solves the issue as the live system did.
this is a fresh install of Ubuntu 14.04, using Gnome Flashback Mode. Synaptic made problems from the beginning, directly after its installation.
Ubuntu 12.04, which is installed in parallel, never had problems with Synaptic.
After starting synaptic, the left list is populated while the loading bar is displayed at the bottom. After the loading bar disappears, nothing changes (still not enabled/"clickable") and after a while the synaptic window becomes grey. One CPU is at 100% load then with the synaptic process.
Then I have to kill it and remove the /var/lib/dpkg/lock file prior to being able to use apt or the software center.
Those other two tools work without a problem. Interesting: sometimes synaptic works! I can not identify why.
I have no clue on how to debug or solve this.
There is nothing in syslog and no error when called via command line.
As requested, some hardware informations:
- Samsung XE700T Slate PC (tablet style)
- Intel Core i5 2467M
- 4 GB RAM
- 64 GB SSD
I have the following problem: when scaling a window to the bottom of the screen, it gets automatically maximised vertically. This is very annoying as I want to decide how to scale my windows!
I found no option that triggers this.
The compiz plugin grid is disabled. Everything I find when searching for my problem, are references to grid ...
My System:
Ubuntu 14.04.1 LTS
Kernel 3.13.0-32-generic
Compiz 0.9.11.2
Gnome 3.8+4ubuntu3
Using Gnome Fallback Mode
On my tablet I use a fresh install of trusty with gnome flashback compiz session. At login screen gnome provides an own on-screen keyboard which is kind of ok.
Within the session I use onboard in normal mode and I enabled it for the unlock screen as well. There it is a little bit too small and I found no way to increase its height.
Adjusting the docked height of onboard does not affect the appearance within the lock screen (where it is docked automatically with no option to change this).
Is there a possibility to increase the dock styled height of onboard at gnome lock screen?
If not, is it possible to display onboard normally (not docked) at gnome lock screen?
If none of them, I am open for proposals of onboard alternatives.
Thanks in advance,
Nicolas
Okay guys, this is an experimental question warning!
I often confuse cat and ls when quickly working on the console. Not because I forget their meanings, no. Just because I type without deeply thinking about the command - it just comes automatically. I am sure everyone knows what I am trying to explain: you don't have to think what to type if your task is to list, say, a text file - or a directory.
Now, why two different commands? Things would be more fluently if there was a command that lists a directory if the target is a directory and that lists the content of a file if the target is a file.
Does such a command exist?
I know there are editors (e. g. vim) with the ability to list a directory. But this is not what I want, as I want to stay on the console. Second, after opening a file through the vim directory listing there is no way back - at least none that I know.
If there is no out-of-the-box solution I will try to make a small bash script (wrapper) to cat and ls. But this is not preferred, because when working with many different systems it has to be placed on each of them...