Some months ago it was possible to receive files via bluetooth with TW.
But since some weeks that fails for me. I waited for GNOME 3.20 and the
new bluez in the hope it will fix itself, but the failure remains:
Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff)
Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0x0)
Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), (null)(0xffffffff)
Apr 05 18:01:32 probook obexd[3042]: open(/home/olaf/.cache/obexd/GSIBFY): No such file or directory (2)
Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), NOT_FOUND(0x44)
Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff)
Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20)
Apr 05 18:01:32 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
Apr 05 18:01:32 probook obexd[3042]: disconnected: Transport got disconnected
Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff)
Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0x0)
Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), (null)(0xffffffff)
Apr 05 18:02:42 probook obexd[3042]: open(/home/olaf/.cache/obexd/1OLQFY): Operation not permitted (1)
Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), FORBIDDEN(0x43)
Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff)
Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20)
Apr 05 18:02:42 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107)
Apr 05 18:02:42 probook obexd[3042]: disconnected: Transport got disconnected
First I tried to remove /home/olaf/.cache/obexd, but nothing seems to
feel responsible to create this dir as seen with the first error. Then I
created it with mkdir -m07777, and that just gives the EPERM error as
before. strace shows that it gets some "forbidden" from dbus.
Is receiving files working for anyone else?
Also the rfkill thing does not work reliable. NetworkManager finds the
device according to syslog, but the GNOME bluetooth thing finds nothing.
Something softblocks it:
root@probook:~ # hciconfig -a hci0 reset
Can't init device hci0: Operation not possible due to RF-kill (132)
root@probook:~ # rfkill list all
0: hp-wifi: Wireless LAN
Soft blocked: no
Hard blocked: yes
1: hp-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Need to run 'rfkill unblock 4' manually to get it going. Once that it
done its appearently possible to use the UMTS, and sending a file works
as well.
Olaf
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Unlike rsync, or KDE Connect, there is no option to automatically allow the
Calibre ebook manager to open ports so external devices can connect to it. So
far, my solution has been to disable the firewall before connecting my device
to Calibre via the Calibre Companion app on Android.
For those unfamiliar with the process, Calibre Companion can sync ebooks from
the desktop's library to the Android device's library, thus eliminating the
need for wires and further organization of books.
If I know I am using port 9090 for Calibre, is there a way to allow this
connection in the Firewall? Has anyone else attempted this setup?
Running netstat shows this additional parameter enabled when my tablet is
connected to the computer.
tcp 0 0 10.42.0.1%2457529:39858 10.42.0.250%328:sesi-lm
ESTABLISHED
More than 3 years ago upstream said enough is enough and pulled the
plug on gst-0_10 branch, and ever since then we the gnome-maintainers
have been carrying around the abandoned packages, both because we care
and at the time of upstreams kill-off point we had a lot of packages
depending on them.
Since then we have quietly been porting the ones we care about or
dropping them from Tumbleweed.
We have however now reached a point where we can not in good conscious
say that we care for gst-0_10 at all anymore, and would as a result
offer up maintainership of said packages for those that still depend on
them / want them to stay in Tumbleweed.
Currently osc whatdependson openSUSE:Factory gstreamer-0_10 standard
x86_64 gives this list [see end of email] of depending packages.
If you as a maintainer are affected, please consider stepping up and
requesting maintainer via obs or email.
The above said, maintenance burden is not very high currently, so don't
fear taking responsibility, it mainly consists of tweaking packages to
ensure their continued build.
As a maintainer though I'd prefer that we could drop gst-0_10 from TW
all the way, but acknowledge that this is not currently possible, but
if everyone who have packages still depend on gst-0_10* do a real push
to port or drop packages still dependent we could perhaps take the easy
route out and just drop gstreamer-0_10.
//Bjørn - on behalf of openSUSE GNOME maintainers.
LIST:
osc whatdependson openSUSE:Factory gstreamer-0_10 standard x86_64
gstreamer-0_10 :
aegisub
audacity
boinc-client
codelite
e17
e_dbus
echievements
elementary
elemines
emotion-generic-players
enlightenment
eperiodique
epymc
erlang
espeakedit
etrophy
evas-generic-loaders
filezilla
fityk
flamerobin
freqtweak
gcompris
gnuplot
gnuradio
gstreamer-0_10-plugin-crystalhd
gstreamer-0_10-plugins-bad
gstreamer-0_10-plugins-base
gstreamer-0_10-plugins-gl
gstreamer-0_10-plugins-good
gstreamer-0_10-plugins-ugly
hugin
ignuit
kde3-amarok
kde3-kaffeine
kdemultimedia3
kicad
lekha
libucil
mathgl
meson
moodbar
morituri
perl-Alien-wxWidgets
perl-Wx
pgadmin3
plplot
poedit
presage
psi+-plugins-psimediaplugin
python-efl
python-gstreamer-0_10
python-matplotlib
python-wxWidgets
python-wxWidgets-3_0
rage
sffview
shellementary
terminology
tintii
urbanlightscape
usbprog
wammu
wxGTK3-3_0
wxMaxima
wxWidgets
wxWidgets-3_0
wxWidgets-ansi
wxWidgets-wxcontainer
wxWidgets-wxcontainer24c
wxhexeditor
xchm
xfce4-mixer
xfce4-volumed
xylib
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
You may have noticed that GCC 6 packages appeared in Factory (but gcc
used for building packages still points to GCC 5). Somewhen in
January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
to build packages. The status of that is that it depends on the
glibc update pending in Staging:B and it still requires fixing a few
packages, mostly -Werror related. There was a point in time where
openQA was green for x86_64 (and Minimal-X).
Once Staging:B has been accepted I'll formally submit an update
to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
That staging can nevertheless be used to look at the current FAILs
which are
build failed
cluster-glue failed
elfutils failed
espeak failed
gdb failed
jack failed
libyui failed
llvm failed
mozilla-nss failed
pesign failed
python3-base failed
xen failed
and can also be caused by the glibc update which I pulled into
Staging:Gcc6.
Any help is appreciated.
Richard.
--
Richard Biener <rguenther(a)suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hello to all!
I'd like to open a submit request with jgrep package to openSUSE Factory.
It is a command-line grep-like utility written in Java. It supports Java
regular expressions, RE2J, POSIX options (excluding -E and -G), most GNU
grep(1) options, options -O, -2 and -8.
However packaging is a bit tricky. 1) jgrep normally requires maven at
build time but there are no maven at openSUSE Factory. 2) Maven requires
about *teen plugins for jgrep and no one is packaged at all. That is why
upstream and I decided to let maintainer make jar file and invoke it at
%prep stage.
Is *.jar bundling allowed at OBS? openSUSE Factory?
[0] https://github.com/cheusov/jgrep
[1] http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/textproc/jgrep # NetBSD
package
[2]
https://build.opensuse.org/package/show/home:DarkSS:branches:devel:tools:bu…
--
Best regards,
Dmitriy Perlow
R&D chemical engineer
Lekpharm JLLC
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi,
Time flies, so let's start planning the schedule for Leap 42.2. The
current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be
based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of
May which means we'll get the package sources in OBS then. That in
turn will allow us to start building Leap on top.
My plan would be to have a first Alpha end of May based on 42.1
sources with the SLE bits updated to SP2. The next snapshot should
be before OSC in June and another one in July.
I'd aim for the the first Beta last week of August, followed by
Beta2 around September 21st. RC1 would then be Oct 6, followed by
RC2 Oct 18. GM Oct 27 so we can release November 2nd.
cu
Ludwig
[1] https://en.opensuse.org/Portal:42.1
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Hi there,
something in advance: I'm a long time mutt user. Therefore I'm used to
shuffle through the list of folders containing new/unread messages using
the 'c' followed by 'space' key sequence. This doesn't work anymore in
current Tumbleweed snapshots. I narrowed it down to the configure option
"--enable-sidebar", which enables some pseudo graphical functionality
for - I guess - mutt newbies. Rebuilding the otherwise unchanged
package with "--disable-sidebar" produces a normally working mutt
again. I strongly recommend to disable this code until it gets fixed.
<https://bugzilla.opensuse.org/show_bug.cgi?id=982129>
Hope this helps some otherwise potentially frustrated mutt users ;)
Thx, cheers.
l8er
manfred
Hi,
I installed Tumbleweed snapshot20160520 on our laptop, as a fresh
install, but with the existing /home dir's. Beforehand it ran 42.1,
which I had to re-install or upgrade.
Somehow I'm unable to reach websites. The (wifi)-network is running, I
can ping external addresses (e.g. 8.8.8.8, which I set up as first
nameserver), but I cannot access websites. Not as normal user, not as
root (destination host is unreachable).
Firewall is disabled, and using our phones I do get access, so it
doesn't seem a router problem to me.
I tried both networkmanager and wicked. Networkmanager keeps on asking
for the password of the router, wicked gives a working wifi-connection,
but no access to url's.
Using that laptop, with webaccess, is crucial to my wife's work, so I'm
rather desperate to get it up...
Anyone an idea?
Regards, Jogchum
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org