From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 215594] New: Unable to transfer big files to Nokia N9 and Jolla phone
Date: Fri, 11 Feb 2022 16:03:42 +0000 [thread overview]
Message-ID: <bug-215594-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215594
Bug ID: 215594
Summary: Unable to transfer big files to Nokia N9 and Jolla
phone
Product: Drivers
Version: 2.5
Kernel Version: 5.16-rc1
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: pmenzel+bugzilla.kernel.org@molgen.mpg.de
Regression: No
Created attachment 300440
--> https://bugzilla.kernel.org/attachment.cgi?id=300440&action=edit
Output of `btmon --write /dev/shm/btmon-trace.log`
Report:
https://lore.kernel.org/linux-bluetooth/def03073-3fab-3b34-6ffc-702bb1b3758f@leemhuis.info/T/#m04445e920610d42a9510d0f6d97afa5376e4a3ca
Created Bugzilla issue to upload log files.
Unfortunately, I do not know, how to capture `obexd` logs. `obexd -d` did not
print any messages to the terminal. `obexctl --monitor` also did not get it
more verbose.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2022-02-11 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:03 bugzilla-daemon [this message]
2022-02-11 23:59 ` [Bug 215594] Unable to transfer big files to Nokia N9 and Jolla phone bugzilla-daemon
2022-02-12 6:34 ` bugzilla-daemon
2022-02-12 6:56 ` bugzilla-daemon
2022-02-12 6:57 ` bugzilla-daemon
2022-02-12 18:39 ` bugzilla-daemon
2022-02-12 22:26 ` bugzilla-daemon
2022-02-12 22:29 ` bugzilla-daemon
2022-02-14 18:19 ` bugzilla-daemon
2022-02-15 6:47 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215594-62941@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).