Hello List
am using Xfce : - in /var/log/warn : i see warning
" The gnome keyring socket is not owned with the same credentials as
the user login: /run/user/1000/keyring-4i77r7/control
2013-11-27T13:27:17.434100+02:00 su: gkr-pam: couldn't unlock the login
keyring "
...............
- any ideas how to fix ?
thanks
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Hi Folks,
There seems to be a flurry of IPv6 talk going on, maybe this is time
for me to bring up the rogue router problem again? I asked about
this a couple of times over the years but could never find anyone
to comment on it.
First, here's the RFC that describes the problem:
https://tools.ietf.org/html/rfc6104
Rogue routers have affected me personally at a customer's site.
This is a large, professionally managed, dual-stacked network with
a number of v4 class B addresses and thousands of hosts. Subnets
seem to be /20 CIDR in size, so there are plenty of "neighbors" on
any given subnet.
I've encountered the situation where misconfigured Windows systems
will advertise themselves as an IPv6 router. They then happily accept
traffic and drop it all silently on the floor. This problem doesn't seem
to bother other Windows boxes too much, but it absolutely kills SSH
connections. SSH preferentially tries IPv6 port 22, which when sent
to a dumb Windows box results in very long hangups and connection
failures. My workaround for my cohort of Linux desktops and servers
was to disable IPv6 for both ssh and sshd. This will work for as long
as the host network supports dual stacks, but eventually?
Then there's the issue of intentional MITM attacks using this vector.
If a bad actor has physical access to a subnet, or has compromised
a host on that subnet, your goose is cooked.
This link mentions some mitigations, but they're quite technical and
may require hardware support.
https://community.infoblox.com/t5/IPv6-Center-of-Excellence/Holding-IPv6-Ne…
So, what is the threat to a home IPv6 user who has WiFi and an Internet
of Things with minimal/non-existent security? I personally feel safer
behind a nice natted IPv4 firewall with ACL rules between my copper
and WiFi subnets. I just feel that I have more control of the situation
with a simpler network.
Has SUSE addressed this issue? Tell me I don't have to worry about it!
Regards,
Lew
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I simply can't find a suitable video editor that works.
My goal is to extract the interesting parts of a TV recording. Ie, mark
the start of the movie, the end, the commercials inside, and dump all
that into a single file, perhaps recoding.
One limitation is that movies here have two sound tracks, one in
Spanish, and the other one in the original language, typically English.
I want to keep both, obviously.
I don't need any transition or effect, just a simple editor that allows
me to remove unwanted sections.
I have tried:
pitivi - crashes on start
LiVES - works for an hour at 100% CPU and can't load the file.
dvbcut - says my mpeg file is not a video (and it certainly is!)
tragtor - can convert, but not edit.
openshot - almost. My video has two sound tracks, and this tool ignores
the second track.
cinelerra-cv - I can't make head or tails of it. I tell it to load a
video file, it does, but then I don't see how to do anything. It doesn't
even display the video. I may have to read the manual, but I dislike
having to read a manual for a GUI. Still...
kdenlive - Well... crashes too often. I can mark the cuts, but it does
not display what I'm cutting. And only one sound track.
HandBrake - no edit.
Avidemux - one sound track only.
Kino - abandonware.
Lightworks ??
Shotcut - Segmentation fault on start.
cer@Telcontar:~/Videos/Fusion/trabajo> shotcut
QSqlDatabase: QSQLITE driver not loaded
QSqlDatabase: available drivers: QMYSQL QMYSQL3
QSqlQuery::exec: database not open
QSqlQuery::exec: database not open
Database::Database(QObject*) Failed to get version.
QSqlQuery::exec: database not open
bool Database::upgradeVersion1() Failed to create thumbnails table.
Database version is 0
Segmentation fault
cer@Telcontar:~/Videos/Fusion/trabajo>
Flowblade ?? I don't understand the tool. May need some reading. At
least it runs.
I would like something that would produce a command line to ffmpeg in a
GUI. Then I could modify further the options. This would be ideal.
tragtor works this way, but has no editor.
- --
Cheers
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlbbJ80ACgkQtTMYHG2NR9UmagCeK8UbAAz5/lAjBvscdhzBuxtb
WUQAn2jmzoy7810hldN4WwVWQktgVp2g
=muqW
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
This website:
http://www.bbc.co.uk/html5
contains an html5 video. You have to be opted in to html5, it says if
you are on the right hand side.
This video wasn't working for me in seamonkey or firefox, until I
enabled the Packman repository and installed Mplayer. So I think there
are some dependencies which are not satisfied by installing firefox. But
I think I read that firefox downloads some things on the fly for html5,
so maybe it should check for libraries too?
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Not sure if this is a KDE or Solid (or other) issue . . . sorry for message
length but trying to include all relevant data I know of . . .
Digikam has worked great importing/deleting photos from iPhone 6S for a year,
working on 13.2. I recently upgraded 13.2 => 42.1 => 42.2 about a month ago.
I can't honestly say whether this problem arose with the Leap upgrade, or with
an update since.
When Digikam opens it displays the following error message:
The specified camera ("/org/kde/solid/udev/sys/devices/
pci0000:00/0000:00:12.2/usb1/1-1/1-1:4.2/net/eth2") is not supported.
~>lsusb shows the camera as:
Bus 001 Device 002: ID 05ac:12a8 Apple, Inc.
Switching to a different port , , ,
~>lsusb
Bus 004 Device 003: ID 05ac:12a8 Apple, Inc.
Digikam then throws this error when started:
The specified camera ("/org/kde/solid/udev/sys/devices/
pci0000:00/0000:00:13.2/usb4/4-2/4-2:4.2/net/eth1") is not supported.
Yet still Digikam (and other photo apps) autodetects the phone. It is shown
under the Import menu, and when Import for the phone is selected the second
Digikam windows opens. At bottom it shows the correct camera media capacity
and amount used, while under the Device menu it shows the phone is recognized
on the correct usb port. It shows that upload and delete are supported
functions. But it cannot see the photo files.
(It is seen as an "iPhone5 (PTP mode)"; gphoto2 --list-cameras does not show
iPhone6 but that was not a problem before; the udev hwdb shows the same phone
ID for both iPhone5 and iPhone6. Tested this with my wife's iPhone 5 and the
errors were the same.)
gphoto2:
--list-ports sees the correct port
--list-folders sees the "store_feedface" folder but no files.
--abilities shows iPhone 5 with USB support, file preview and upload = yes
When I try kio camera:/ in Dolphin I get:
camera:/Apple%2520iPhone%25205%2520(PTP%2520mode)@usb:001,002/
An "Apple iPhone 5 (PTP Model)" folder appears with the sub-folder
"store_feedface" but no DCIM folder nor any photos.
When I try gtkam it can see the iPhone "store-feedface" but not DCIM, no
files. Experimenting with this app I once got this error, too:
An error occurred in the io-library ('Could not claim the USB device'): Could
not claim interface 0 (Device or resource busy). Make sure no other program
(gvfs-gphoto2-volume-monitor) or kernel module (such as sdc2xx, stv680,
spca50x) is using the device and you have read/write access to the device.
Similarly, when I tried Shotwell it threw:
Unable to fetch previews from the camera:
Could not claim the USB device (-53)
But strangely, darktable uploads (and deletes) the iPhone files even though it
uses libgphoto2.so.6 just as all the other apps do.
Still works fine with my Canon A570.
Digikam Version 5.4.0
Using:
KDE Frameworks 5.26.0
Qt 5.6.1 (built against 5.6.1)
My suspicion is that the problem is connect to the error "could not claim USB
device", as I've seen that several times. Just a wild-ass guess.
I checked Bugzilla KDE and Solid, found multiple instances of PTP cameras
being recognized but files not retrievable over the last ~5 years. But
nothing recent. I did find a 2011 bug report on Ubuntu Launchpad which was
reported again in Dec claiming a regression in Digikam, but it wasn't
verified. (And that was Digikam4, not 5).
Any suggestions where to look further? Again, apologies for length.
TIA,
Dennis
P.S. KDE folks might want to note that the Device Notifier entry always
displays the camera twice rather than just once when it's attached, and when
the "Open with File Manager" option is chosen, the app errors on not finding
the KDE4 version of Dolphin:
KDEInit could not launch 'dolphin4':
Could not open library 'libkdeinit5_dolphin4'.
Cannot load library libkdeinit5_dolphin4: (libkdeinit5_dolphin4: cannot open
shared object file: No such file or directory)
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Dear listmembers,
dear openSUSE - maintainers,
I maintain about 5 to 6 PC running (openSUSE) linux. My own, my sisters my
friends ... Currently most of them are running with leap.
During the last month I had to reinstall _all_ of them. All with broken /
inconsitent / strange behaving root Btrfs file systems.
After 25 years of working with linux I'd consider myself kind of experienced
what regards linux problems.
And, if that had had happened once I would have said it has been my fault. I
do not think so any more. I consider Btrfs instable and inappropriate for
public usage.
I'd go further and would like to ask, *why* this is set as the default root fs
when installing. This is totally inunderstandable to me after my experiences.
I never ever experienced any bit of advantage in comparison with ext4. But I
experienced nights of work - just to restore a state that had had existed a
few days before.
So, please, think it over:
*take Btrfs out as default!*
Use stable and well known systems as the foundation of public systems.
Changing things only to change something is leading nowhere.
Besides, if there is a kind soul that can explain what was the reason for
making Btrfs the default I would highly appreciate. I cannot see any change
besides significantly improved stability when going back to ext4. The latter
being the most important thing IMHO.
My two cents
regards
Dieter Jurzitza
--
-----------------------------------------------------------
Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
$SUBJ says it all - I'm missing the hostname. When several PC are
connected via a kvm switch it's handy being able to tell where you are
logging in.
--
Per Jessen, Zürich (4.6°C)
http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I have two openSUSE machines that have joined the same Windows domain.
Both have done this via yast. The 12.3 machine has no trouble
verifying users against the domain. The Tumbleweed machine, however,
fails.
On the openSUSE 12.3 client where it works, I get something like this:
smbclient --user=roropq //os12p3/roger
WARNING: The "idmap gid" option is deprecated
WARNING: The "idmap uid" option is deprecated
Unknown parameter encountered: "mangle case"
Ignoring unknown parameter "mangle case"
Domain=[RAMBOLL] OS=[Unix] Server=[Samba 3.6.12-59.23.1-3256-SUSE-SL12.3-i386]
smb: \>
On the Tumbleweed machine, I see this:
smbclient --user=roropq //Tumblereed/roger
WARNING: The "idmap gid" option is deprecated
WARNING: The "idmap uid" option is deprecated
Unknown parameter encountered: "mangle case"
Ignoring unknown parameter "mangle case"
Domain=[RAMBOLL] OS=[Windows 6.1] Server=[Samba 4.5.3-0-SUSE-oS13.3-x86_64]
tree connect failed: NT_STATUS_ACCESS_DENIED
It is interesting that the 12.3 samba reports the OS as Unix, while
the Tumbleweed samba reports as Windows 6.1. The Server strings match
the installed Samba on each machine.
When yast checks that the machine is a member of the domain, it is
happy. And the domain admin sees both machine as expected (by him).
The two machines, as far as I can tell, have samba configured the
exact same way.
I see this in the samba logs:
[2017/02/09 13:42:51.306927, 0]
../source3/libads/kerberos_util.c:74(ads_kinit_password)
kerberos_kinit_password
STO-OPQ-SRC$(a)RAMBOLL.RAMBOLL-GROUP.GLOBAL.NETWORK failed: KDC has no
support for encryption type
I have googled this, but I cannot say that I have seen anything that
makes sense in the context of samba. This is a bit outside my
experience.
FYI, the configuration for both machines is:
[global]
workgroup = RAMBOLL
passdb backend = tdbsam
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
usershare allow guests = No
idmap gid = 10000-20000
idmap uid = 10000-20000
realm = RAMBOLL.RAMBOLL-GROUP.GLOBAL.NETWORK
security = ADS
template homedir = /home/%D/%U
template shell = /bin/bash
winbind refresh tickets = yes
mangled names = no
usershare max shares = 100
Where to start looking?
--
Roger Oberholtzer
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
any change to technology is a threat to your existing knowledge and skills and
should be rejected immediately. the more convoluted the existing technology is
the better, it gives you and edge over others, which you need to defend (eg
init).
here is an incomplete list of potential stratergies:
[1] divine truth: a useful prescript e.g. "a tool should do 1 thing and do it
well" is a divine truth. it is not subject time, context, evidence, data or
reasoning. [like the 10 commandments] (you can use divine truth to immediatly
dismiss systemd irespective of technical arguments).
[2] if the new technology doesnt work in the same way as the old, it is flawed.
since the new tech requires new knowledge, it is obviously more complex QED.
[be carefull not to apply this to windows vs linux]
[3] dismiss any new features as pointless and unneeded.
[4] faults: any shortcoming of new tech (be truth or hype) should be vocalised
extensively. try to frame an argument such that the old tech has no problems.
[5] avoid data, evidence, reasoning and context: rely on rumours, anecdotes,
fud, comments on reddit, appeals to emotion and truthiness.
[6] give the new tech whipping boy status: any problem for which a diagnosis
does not exist should be attributed to the new tech.
[7] condemn the new tech based on partial knowledge you havnt verified, and use
this to form an apparently rational conclusion (e.g. systemd timer
limitations)
lets take an example:
OP: "i had a problem, I dont know what it was, I used the wrong tools to
diagnose it, ignored any recommendations on how to fix it, did something i
didnt understand, and it still didnt work. whats more the same thing happened
on all 5 systems which is statistically impossible if considered as
independent (non correlated) failures"
you now have all the hard evidence you need, and can let rip:
[a] "the same thing happened to me - this is proof the system is rubbish"
[b] "how could you ship a system that allows such a thing to occur"
[c] "there is some fud on the internet from 5 years ago showing how bad the
system is, whats wrong with you people"
[d] "any tech that requires understanding is no good for home users" [ignoring
the fact that the linux ecosystem itself fails under the premisses of the
argument]
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org