I can easily reproduce the message e.g. by setting
GTK3_MODULE=xapp-gtk3-module while not having libxapp-gtk3-module
installed. The package's configuration file
/etc/X11/Xsession.d/80xapp-gtk3-module also sets that for the Xsession.
However... i) I can influence the message independent of
Hi Marc,
blueman-manager works fine for me without that package and blueman does
not have anything to do with xapp.
Could it be that you're referring to the module in
~/.config/gtk-3.0/settings.ini or similar? Do other GTK 3 apps work fine?
Cheers
those protocols are completely run by the audio server, which in your
case seems to be PipeWire. blueman does not have any stake in it.
Hi Christopher,
does that also apply to the creation of these missing nodes as reported
back to bluetoothctl after the second connect command?
[Hama
Hi Michael,
sorry for the late reply.
Unfortunately blueman 2.1 has a buggy PIN database built-in that
probably leads to a random 4-digit PIN getting provided in this case
instead of the that the device expects.
However, the database is not part of blueman 2.3 anymore, so I would
Hi Alf,
those protocols are completely run by the audio server, which in your
case seems to be PipeWire. blueman does not have any stake in it.
Regards
You do have a working IP connection but fail to reach any Internet
targets, also by IP address. Is that correct?
Please check (with sudo or similar):
iptables -t nat -L POSTROUTING
iptables -t filter -L FORWARD
cat /proc/sys/net/ipv4/ip_forward
ls /proc/sys/net/ipv4/conf/*/forwarding
cat
Still no decorations (with Gtk.MessageDialog(decorated=True).show()
followed by Gtk.main())
So you cannot even force decorations? Wow, weird.
Okay, so this is probably some sort of GTK / Xfce4 problem? Should I
report it against some other package (which?), or reassign this report?
Well,
Alright, so...
according to your first test and as expected a notification daemon does
not seem to be available. According to your report, you do have
notification-daemon installed, so running
/usr/lib/notification-daemon/notification-daemon in your desktop session
should solve that. Desktop
Shouldn't
there be some sort of "Okay" button, or some window decoration that
allows them to be closed?
Yes, window decorations are expected if those are the fallback windows.
They are GTK MessageDialogs which by default shall get decorated by the
window manager.
Another possibility would
Those popup windows are a fallback for when the required
notification-daemon does not work. blueman is intended to be used with a
running notification-daemon.
Hi Thomas,
I just created https://github.com/blueman-project/blueman/pull/1572
upstream.
Cheers
Hi,
it effectively depends on either dbus-user-session or dbus-x11. What
happens if you only have dbus-user-session installed?
2.1 versions work fine without dbus-x11, is that correct?
To my understanding buster only receives security fixes, so (apart from
providing a backport) I don't see
That seems to be the problem here, yes.
Although it was fixed upstream in 5.51 via
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/obexd/src/obex.service.in?id=78bce480093799c287ac8561b9407fa48796a130,
the Debian package ships the unreplaced @libexecdir@ in
Hi Salvatore,
2.1.4-1 is waiting at https://mentors.debian.net/package/blueman/. I can
add the CVE number and / or this bug to the changelog if you like.
Unfortunately my sponsor Nobuhiro seems to be unavailable.
Regards
31.10.20 13:26 Andrew McCarthy:
Error checking for authorization org.blueman.network.setup:
GDBus.Error:org.freedesktop.PolicyKit1.Error.NotAuthorized: Only trusted
callers (e.g. uid 0 or an action owner) can use CheckAuthorization() for
subjects belonging to other identities
That means that
(Please don't forget to send your replies to 973...@bugs.debian.org as
well. Thanks)
30.10.20 16:32 Andrew McCarthy:
The netdev group already has the user pi added to it. pi is the user
account of the gnome session.
You can verify the Polkit-1 setup by running
pkcheck --action-id
2020-10-30 09:29, Andrew McCarthy:
I attempted to add my user pi to the netdev group, but the system
reports it already exists...
What exists?
You can check the user's groups with the groups command.
Hi Andrew,
the 2.0.8 security update enabled Polkit-1 authorization. There is a
rules file at /usr/share/polkit-1/rules.d/blueman.rules that allows
access without authentication to users in the sudo and netdev groups.
You should be fine if you add your user to netdev.
Cheers
Hi Sandro, 2.1.3-2 on mentors fixes this. I'm waiting for my sponsor to
upload it.
Control: close 950520
Control: fixed 950520 2.1.3-1
I'm not sure if moving '/usr/lib/systemd/user/blueman-applet.service' to
'/lib/systemd/user/blueman-applet.service' is the correct solution here.
No, it's not. It caused #961215 and is thus reverted in 2.1.3-2.
According to the
Hi Emilian,
that error from BlueZ basically means that your adapter fails to
communicate with the device. This can have all sorts of causes, usually
related to chipsets / firmware / kernel.
Strategies I've seen working to solve it temporarily include re-pairing
the device or restarting
Hi Jiff,
that message is just a warning, does not deter blueman from launching,
and is fixed in blueman 2.1.
Any additional output? What is the return code?
Cheers
Peter, In 2.1 you have to provide --loglevel debug to get a useful output.
Tom, awesomewm with KDE as well?
Hi Peter,
sounds like there's some issue with the libappindicator-based icon
implementation which disables the GTK-based one. Your edit effectively
avoids the latter.
Did you try blueman 2.1.1-1 yet?
Cheers
Recent changes in upstream master make blueman compatible with
adwaita-icon-theme and papirus-icon-theme. blueman 2.0 is not.
tango-icon-theme is not compatible at all.
Hi Marek,
I don't see how dropping the dependency would be a good idea but of
course we can add alternative dependencies on compatible icon themes,
i.e. mate-icon-theme and yes, elementary-xfce-icon-theme seems to be a
third one now. I will add both in the next version.
Cheers
Hi Ron,
there should not be any such auto-connect feature in blueman. You can
easily confirm that by stopping blueman-applet and check if it still
happens (you can use bluetoothctl to disconnect if that's necessary).
I actually think it is a feature of the headphones and not triggered
from
> systemctl status bluetooth.service
> ● bluetooth.service - Bluetooth service
>Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
> preset
>Active: inactive (dead)
> Condition: start condition failed at Sat 2018-03-03 18min ago
>└─
Hi Alexander,
> If one selects the blueman applet from the LXDE menu, it fails to start saying
> "Bluez daemon is not running, blueman-manager cannot continue. This probably
> means that there were no Bluetooth adapters detected or Bluetooth daemon was
> not started".
That message is triggered
Hi Bjørn,
thanks for your comment.
> Why not raise your hand and offer to maintain IrDA in mainline instead?
I might be wrong but that just sounds like a lot of work and
responsibility which I cannot currently offer.
> The problems causing it to be shceduled for removal will not be
> magically
Package: wnpp
Severity: wishlist
Owner: Christopher Schramm <deb...@cschramm.eu>
* Package name: irda-dkms
Version : 0.1
* URL : https://github.com/cschramm/irda
* License : GPL
Programming Lang: C
Description : IrDA subsystem and device drivers
Th
> I notice there is
>
>
> I was expecting the at_console clause to make it just work if I'm logged
> in on a console with X. Is that not the expected behaviour?
Depends. You'd need consolekit or systemd-logind or some API like that
and your DM needs to inform that API about the session and
I think I found the initial problem: /usr/bin/dbus-launch does not
terminate abnormally, it doesn't even start as it's not present. blueman
is missing a dependency on dbus-x11.
Hi Bob,
sounds like your user is not allowed to use bluetooth. Make sure he's a
member of the bluetooth group. Relevant rules are in
/etc/dbus-1/system.d/bluetooth.conf from bluez.
Regards
Hi Michelle,
>> you can try the helper manually with sudo
>> /usr/lib/dbus-1.0/dbus-daemon-launch-helper org.blueman.mechanism and
>> see what happens. Also check /var/log/daemon.log.
>
> Nothing special, it loads proprtly.
> Should this service not started automatically?
the service is not
Hi Michelle,
you can try the helper manually with sudo
/usr/lib/dbus-1.0/dbus-daemon-launch-helper org.blueman.mechanism and
see what happens. Also check /var/log/daemon.log. You can try to invoke
blueman-mechanism directly with sudo /usr/lib/blueman/blueman-mechanism.
If you're using systemd,
Hi Wiktor,
blueman-applet uses the rfkill system to soft-block bluetooth. See
https://github.com/blueman-project/blueman/issues/794#issuecomment-347432973
on how to check that it's really blocked and if it's actually
blueman-applet that unblocks it during boot.
Regards
Source: py3cairo
Severity: normal
Upstream is currently at 1.15 and the libcairo2 package is at 1.14 while
py3cairo is still at 1.10. Specific need is that blueman master requires 1.14.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (700, 'testing'), (600,
Hey,
this issue will be fixed in OpenSSL 1.1.1 with an
SSL_OP_NO_ENCRYPT_THEN_MAC option and I can work around it in OpenSSL
1.1.0 by forcing the use of a stream cipher.
I'm currently calling set_ciphers('AESGCM:AESCCM:CHACHA20:!aNULL') on
the SSLContext. That requires the server to support any
Hi Eduard,
looks like an issue with bluez-obexd. Does it work with 5.43-2?
Regards
Hi,
that feature does not work with BlueZ 5 and support was dropped from
gvfs. blueman 2.1.alpha1 does not use it anymore.
See
https://github.com/blueman-project/blueman/wiki/Integrations#obex-file-transfer.
Regards
Hi Dio,
I'm not sure what you mean. You reported a potential issue in blueman
2.0.4-1 and then stated it would be resolved in sid which currently has
the exact same version.
Can you please clarify?
Package: libpython3.5-minimal
Version: 3.5.3-1
Severity: normal
Hi,
I'm having huge problems with HTTPS since this package started using libssl1.1.
It is not an issue with the Python packages themselves, but you might want to
consider to switch back to libssl1.0.2 because of it.
See my report
Hi Eduard,
I guess you're using systemd for which bluez-obexd's default setup is
broken. See #804908 for insights and solutions.
Regards
Package: libphutil
Version: 0~git20160726-1
Severity: normal
After upgrading to PHP 7 arcanist / libphutil stopped working due to
utf8_decode missing. Installing php-xml manually fixed that.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (700, 'testing'),
Hi Norbert,
that typically means that the TransferService plugins is disabled and
should be mentioned in the tooltip of the greyed out widget.
Regards
Hi Jelmer,
you're trying to use an item from "Recent connections" that is not valid
in 2.1.alpha1 anymore. You can get rid of that entry with:
dconf reset /org/blueman/plugins/recentconns/recent-connections
I've filed an upstream bug regarding an automatic reset on every
installation:
The package is out of sync with android-platform-system-core which is
now at 1:6.0.1+r43.
If incompatibilites are expected in such cases the dependencies should
specify the version.
09.06.2016 06:49 Chris Dellin:
> If anyone knows a functional workaround, please let me know! (My
> understanding is that Debian 7 should have security support until May
> 2018 [2].)
Put the libflashplayer.so file contained in the .tar.gz from
https://get.adobe.com/de/flashplayer/ at
Package: haskell-stack
Version: 1.0.0-1
Severity: normal
There have been a lot of fixes and improvements sind 1.0.0 and the current
upstream release is 1.1.0.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (700, 'testing'), (600, 'unstable'), (500,
Package: samba
Version: 2:4.2.10+dfsg-0+deb8u2
Severity: normal
Dear Maintainer,
since the samba version in jessie was updated to 4.2 we have an issue with our
server that renders shares unusable. After they've been accessed for a small
amount of time, the log constantly shows:
Hi Ralf,
could you try and see if
https://github.com/blueman-project/blueman/commit/f7c0f6af1d7623775587abc1f439d96f3bc53c95
helps with your issue?
If you need assistance to apply it, just get in touch with me (off list).
Regards
Hi Nelson,
thanks for the report.
The error indicates that your adapter is not powered. blueman-browse
does not have a handling for that as it's usually started from the
applet menu and blueman-applet should either auto-power the adapter on
startup or - if that's disabled or fails - refuse to
Hi Ralf,
providing --device does not mean much difference to the GUI selection.
The only thing I could imagine playing a role for you is that a
discovery is started if you use the GUI selection.
You could try starting a discovery (e.g. with bluetoothctl or blueman)
and see if `blueman-sendto
Hi Ralf,
thanks for your report.
The first - not working - way you describe should invoke
`blueman-sendto` without any options.
The second should invoke `blueman-sendto --source=
--device=`.
Could you try those two variants manually and see if the result is the
same as through the applet and
This is a setting of the PowerManager plugin.
> It's a release goal in Lubuntu to not have python2 on the image.
Err, good luck. ;)
> Upstream has completed in version 2.0 a port to python 3 [1][2].
Yes, blueman supports Python versions 2.7, and 3.2+.
I think depending on the distribution's default python version is
exactly what the
Hi Neil,
I cannot reproduce this issue. Can you please show the full messages?
Does it happen with blueman 2.0-1 too (I cannot think of any changes
that could cause this)?
Regards
> Even if there is some problem with dbus-daemon, this must not prevent
> blueman installing - requiring a reboot to complete an installation is
> not acceptable.
This is not a blueman issue as it's not blueman that asks for the reboot.
blueman requires the dbus configuration to be reloaded (it
By the way: Downgrading your dbus configuration files to fit the version
that's running would solve this as well of course.
blueman auto powers on adapters. You can disable this in the settings of
the PowerManager plugin.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Please see https://bugzilla.redhat.com/show_bug.cgi?id=1227868#c3 and
check if it helps.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Brice,
I guess at the end of XFCE session actually means when blueman is
closed, right? So closing blueman with a soft killswitch enabled
disables that switch for you? Please run blueman-applet in a terminal
and post the output you get when exiting it.
Regards
--
To UNSUBSCRIBE, email to
Hi Karl-Heinz,
can you please try the patch at [1]? It sets a title on the
GtkStatusIcon which is hopefully what gets picked up by the KDE settings
tool.
[1]
https://github.com/blueman-project/blueman/commit/671ba8cdfd5bdcb3d712d42b4ae415dd907c4911
Regards
--
To UNSUBSCRIBE, email to
Package: arcanist
Version: 0~git20150525-1
Severity: grave
Tags: upstream fixed-upstream
Justification: renders package unusable
This snapshot has a severe issue which renders `arc land` unusable. Here is the
upstream bug report including a reference to the fix in current master:
Hi Dominik,
I'm not sure what a notification flying through the screen looks like.
:D Can you describe it or take a screenshot or something?
What notification system do you use? mate-notification-daemon?
I doubt that this is an issue in blueman as we just use the libnotify
interface to create a
OK, found it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779870
https://github.com/mate-desktop/mate-notification-daemon/issues/51
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
See now it's too bad that this wasn't marked as an RC bug because now
Jessie doesn't ship with this fix.
I'm not sure what's your point here. If this would have been marked as
an RC bug, Jessie would not even ship blueman.
Isn't there a way the new alpha can be bumped into jessie now?
Newer
Is this bug report still valid for 1.99~alpha2-1?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I can now confirm that this is due to an issue between obex-data-server
and BlueZ 5. It is basically https://bugs.debian.org/774796 and not
really a blueman issue.
The problem is that obex-data-server tries to use the /var/run/sdp
socket, which in BlueZ 5 is a) disabled by default and b) limited
Hi Jean-Michel,
The default configuration for plugin StatusIcon is blueman-tray
that one is an old configuration value and the icon is no longer
available. It should work if you just remove that name.
1.99~alpha2 changelog shows some changes related to icons, but I did not
tested it yet
I just tried and rebooted:
Unfortunately, this removed the icon.
Entirely.
Whoops, I'm so sorry. Glad we removed that option upstream... :B
The default value that should work in alpha 1 would be just blueman. In
case you don't trust me anymore (I'd totally understand that), here's
the code
Hi Andreas,
did you check a current upstream version?
To see what's going on in blueman (if anything), we need the output from
blueman-applet. See
https://github.com/blueman-project/blueman/wiki/Troubleshooting for
information on this.
I think it's best you create an upstream issue for this. I
Anyway, connecting to a NAP should work. You just have to select the
service from the device menu and not use the generic connect item for that.
There's no service from the menu, in fact, the Serial server menu item
is gone.
So you are talking about a serial service, not a NAP service.
Hi Antoine,
unfortunately BlueZ 5's generic connect method is a misconception in my
eyes as in your case it will not connect the NAP service. In the current
upstream master you will not get a generic connect item in the menu
anymore, but see which services are provided and could be connected with
Hi,
can you please try the version from wheezy-backports? I guess 1.23 does
not detect pulseaudio 2.x correctly.
Regards
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Alessandro,
this is possible already. You just need to enable the ExitItem plugin.
Regards
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Patrick,
to look into this we need blueman's output from a terminal. See [1] for
instructions on how to get it.
[1] https://github.com/blueman-project/blueman/wiki/Troubleshooting
It's best to open a new GitHub issue for this [2].
[2] https://github.com/blueman-project/blueman/issues/new
According to the discussion upstream [1] it works with awesome-3.5.5,
maybe due to the migration to GTK+ 3 in the meantime.
[1] https://github.com/blueman-project/blueman/issues/8
I'm thus closing this. Drop me a line if you can still reproduce.
--
To UNSUBSCRIBE, email to
I feel that this problem is something to do with systemd as it is a big
system change from wheezy.
No. I'm sure I could reproduce the issue with sysvinit. It's also not
specific to Debian.
I think it only happens with BlueZ 5, but I don't know what that means
exactly. I don't think it's a
I installed bluedevil ,and it is not working either
Interesting... then it might be the case that obex-data-server is just
not compatible with BlueZ 5...
That leaves me with the obexd-server migration as the only way to solve
this. It's the number one task on my list anyway, as soon as I find
I'm working on a transition to obexd-server upstream which will fix
this. We could also find a fix for making it work with obex-data-server
again, but I do not have a starting point for this.
Unfortunately neither will make it into jessie before the freeze.
--
To UNSUBSCRIBE, email to
I can confirm that it was #754850, since updating cgmanager made Xfce
work with sysvinit again. :)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi James,
thanks for your report. I'm tracking this upstream:
https://github.com/blueman-project/blueman/issues/109#issuecomment-58625633
Cheers
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
12.09.2014 10:12, Christopher Schramm:
Sorry, I missed that one, since it came weeks after the versions of
xfce4-session with which the problem started. That resolves it of course.
Said that too fast... :(
Looks like there are two different issues I encounter. As I've said I've
seen
Thanks, Martín. I've added it upstream:
https://github.com/blueman-project/blueman/commit/8ce4f61ed160fdd940d8330ec4fd05e977b59ba2
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Alessandro, I've created an upstream item for this:
https://github.com/blueman-project/blueman/issues/94
I think it should be possible to set an arbitrary browser command, but I
need to check that. Anyway, built-in caja support would definitely be good.
--
To UNSUBSCRIBE, email to
Xfce handles permissions through
PolicyKit, which needs libpam-systemd, which in turns requires either
systemd-sysv or systemd-shim.
I do have libpam-systemd, but neither systemd-sysv nor systemd-shim.
Obviously none of them was needed for xfce4-session 4.10.1-7 (dpkg
does not now them, so
Then upgrade? libpam-systemd 208-8 (currently in jessie) does depend on
systemd-sysv | systemd-shim.
Sorry, I missed that one, since it came weeks after the versions of
xfce4-session with which the problem started. That resolves it of course.
Thanks for your patient support!
--
To
I think it's more related to the systemd changes. What init system are
you using?
My /sbin/init is provided by sysvinit-core, but systemd is running as
well (I think it is invoked via dbus by network-manager / libpam-systemd).
I guess my problem is caused by
Can you try with init=/lib/systemd/systemd or with systemd-sysv.
I'll try.
Also, is systemd-shim installed?
No.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: xfce4-session
Version: 4.10.1-8
Severity: normal
Starting with xfce4-session 4.10.1-7 I'm having trouble with shutdown and
reboot in conjunction with SLiM. When I try to shut down or reboot the system
using Xfce's dialog, the desktop disappears as usual, but then SLiM shows
failed to
Is this still valid for recent versions?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hey, are these issues still valid for the latest versions?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Dean,
This new version seems to change blueman from being a gtk-only piece of
software to something bound inseparably to gnome.
why is that? The changes in dependencies primarily represent the switch
from GTK+ 2 to GTK+ 3 and thus to GObject Introspection, since that's
the preferred (or
The following extra packages will be installed:
gir1.2-appindicator3-0.1 gir1.2-atk-1.0 gir1.2-freedesktop
gir1.2-gconf-2.0
gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 gir1.2-notify-0.7 gir1.2-pango-1.0
libappindicator3-1 libdbusmenu-glib4 libdbusmenu-gtk3-4 libindicator3-7
This is due to the
Hi Tom,
thanks for your report.
What you describe sounds like 1.23-git201406261335-deb-1 (still in
jessie) works. Is that correct?
Does it work when using the current blueman version with BlueZ 4? You
can get 4.99-2 from wheezy. Switching BlueZ versions is a little tricky.
I think you need to
I was able to reproduce it and created an upstream issue for this:
https://github.com/blueman-project/blueman/issues/83
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Blueman (?) generates an popup error message, with this information:
org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process org.blueman.Mechanism
received signal 5
Might sound strange, but: Do you have any Wayland related stuff on your
system?
Hi Mattia,
The strange thing is that it did work on bluez5 until the last minor version
update.
that's not possible. I can rebuild and send you 1.23-git201403102151-1
(the version in testing for the last three months), if you want to test
it. You can also check your apt(itude) logs if you
1 - 100 of 176 matches
Mail list logo
