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
Hi,
As announced in December¹, Leap 42.3 is already open for
submissions. We shouldn't expect big updates in 42.3, nevertheless
some went in already, like texlive 2016. Also, some packages that we
already know SLE will take from Factory also got updated like e.g.
YaST. So far the current state looks quite good in openQA² so the
adventurous may already zypper dup.
What's missing still is a roadmap for the release. SLE12SP3 aims for
a release in September. Due to the holiday season in August where
many developers are likely unavailable anyways development is
expected to be finished before. So my proposal would be to also
finish with Leap before and aim for a release at the last Wednesday
of July.
With regard to the release model I'd like to try something new.
Rather than having fixed milestones with fixed submission deadlines
every few weeks let's try to adopt a model similar to Tumbleweed's.
Ie have snapshots released automatically based on openQA results.
Nevertheless the closer we get to the release the stricter the rules
for updating packages have to be.
cu
Ludwig
[1] https://lists.opensuse.org/opensuse-factory/2016-12/msg00165.html
[2] https://openqa.opensuse.org/group_overview/28
--
(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,
I've built new package for openSUSE Tumbleweed. Akonadi resource agent for Microsoft Exchange using Exchange Web Services (EWS) protocol.
It's my first package so any test or help is appreciated.
https://build.opensuse.org/package/show/home:hlavki/akonadi-ews
thanks, m.
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
Dear Tumbleweed users and hackers,
What a week! Tumbleweed once again is the first (to my knowledge) to
ship the just released GNOME 3.24.0 as part of its main repository.
Being shipped to the users in less than 48 hours since the official
release announcement is something we can only do thanks to all the
automatic building and testing AND the efforts put into the packages!
If packagers would not be at the ball the whole time, this would not be
possible. Even though the week has seen ‘only’ 4 snapshots (0317, 0318,
0320 and 0322) the changes delivered to the user base is enormous.
The major changes this week were:
* GNOME 3.24.0 – Released on March 22nd, part of snapshot 0322
* The YaST Teams work regarding the desktop selection workflow [0]
* qemu 2.8.0
* Linux kernel 4.10.4
* Mozilla Firefox 52 – NOTE: no more support for NPAPI plugins
* GCC 7 is available as optional compiler (distro still built using
gcc6 though)
* More work to get the ‘system user’ situation changed, having
special packages creating the users [1]
One important note at this point: again there were users falling into
the trap with incomplete updated systems with snapshot 0322.
Important: """zypper up""" is NOT the right thing to keep your
Tumbleweed system running.
Use """zypper dup [--no-allow-vendor-change]"""
Things currently being prepared for you
* GCC7 as default compiler – this might still take a while, but it IS
coming
* KDE Plasma 5.9.4
* Linux kernel 4.10.5 – and beyond
* More python packages converted to singlespec
For the next three weeks, Tumbleweed will be given in the careful care
of Max and Ludwig, while I will be enjoying some time off. As is usual
when teams are running on lower resources, it is possible that
snapshots might be delayed a little bit, but I don’t fear to much for
that: you can continue submitting as you’re used to – just in case of
some delays, please show some understanding. I’m sure Max and Ludwig
will be there for you if you need any help. Also, in this period, I
will not provide the weekly reviews. I might try to do a recap once I’m
back, but no promises there.
Cheers,
Dominique
[0] https://lizards.opensuse.org/2017/02/20/highlights-of-yast-developm
ent-sprint-31/
[1] https://lists.opensuse.org/opensuse-packaging/2017-02/msg00022.html
--
Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org>
Hi,
Lenovo W520, Tumbleweed, nouveau driver, tried various combinations of
zypper up/dup/dup --no-allow-vendor-change to no avail.
Starting from the GUI (kdm, KDE) if I try to switch screens with
CTRL+ALT+F1/2/3/4/5/6 the GUI stays displayed but the mouse and keyboard
don't work until I do a CTRL+ALT+F7. This happens right from the login
page, before I've logged in.
If I boot to Runlevel 3 then it all switches properly as expected. init
5 to the GUI and it breaks and behaves as above. Back to Runlevel 3 and
we're good again.
An extra issue (probably related) is that if powersave kicks in and
blanks the screen, when I come back, I'm left with a blank screen and a
mouse pointer. I have to ssh in from somewhere else and systemctl
restart display-manager to get my desktop back.
I'm not sure when this started. It was a few updates ago. I'd been
hoping that a later update would fix this, but not so far.
Any ideas greatly appreciated.
Thanks,
Marcus.
Hi,
Am 20.03.2017 um 17:18 schrieb Marcus Meissner:
> Note that the openSUSE Leap 42 class of distributions is designed to be easily
> upgradable within minor versions, so Leap 42.1 to Leap 42.2 update should
> be easy and seemless.
and if they are not?
That list does not look too bad but it's just for the "Upgrade"
component. There may be others.
https://bugzilla.opensuse.org/buglist.cgi?classification=openSUSE&component…
What concerns me is that almost all are NEW.
At least one of them made me stop ugprading my remaining 42.1 systems at
least temporarily in the hope that there might be patches coming up.
Wolfgang
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org
HI!
After the last Tumbleweed update starting the VMs does not work anymore:
error: internal error: child reported: Kernel does not provide mount namespace:
Permission denied
Any clue how to work around that?
Ciao, Michael.
Hi,
42.2 is out of the door, time to relax and wait for the Christmas
holidays, right? Well, far from that. We have to prepare for the
next release.
So for the Leap 42 line that means 42.3 based on SLE12 SP3. In
anticipation of that OBS already has openSUSE:Leap:42.3 set up as
copy of 42.2. It already accepts submissions. Right now mostly to
directly integrate 42.2 maintenance updates.
With regard to the schedule SUSE plans to release SLE12 SP3 earlier
than the usual November date. It's beneficial for Leap if we get the
changes we need into SLE and therefore are able to share sources. So
I think it makes sense to follow suit and have our development phase
with SP3 too, ie move the release date earlier as well. Due to the
shortened development time I don't expect big changes in the base
system. 42.3 should keep the promise of continuing an LTS line and
mostly collect all 42.2 maintenance updates until then plus even
more packages and selected updates from Tumbleweed.
I'll propose a more concrete schedule when I know more about SP3.
cu
Ludwig
--
(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
I've just submitted libglvnd and Mesa making use of libglvnd to factory/TW.
Details about libglvnd:
https://github.com/NVIDIA/libglvnd
So basically it's an OpenGL dispatcher, which makes it easier to have various
OpenGL implementation like Mesa, NVIDIA and others installed at the same time.
Apart from runtime tests with Qemu(cirrus) and on real hardware (intel,
radeon, nouveau) - also with NVIDIA's binary driver, I've made bigger build
tests inside of X11:XOrg project, in which douzens of packages are sitting on
top of Mesa build-wise. Still builds of other packages may break with this
change. So, if you believe your package build fails due to this change, please
feel free to let me know. Worst case is reverting libglvnd build again by
changing one define in Mesa's specfile.
Thanks,
Stefan
Public Key available
------------------------------------------------------
Stefan Dirsch (Res. & Dev.) SUSE LINUX GmbH
Tel: 0911-740 53 0 Maxfeldstraße 5
FAX: 0911-740 53 479 D-90409 Nürnberg
http://www.suse.de Germany
---------------------------------------------------------------
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
The subject says almost everything. After updating to this snapshot, VirtualBox
will not run.
What needs to be in the VirtualBox spec file to cause an automatic rebuild when
the kernel changes?
Thanks,
Larry
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org