Mantis - ISSUES

0000440: Neveikia vertimai su '

Nu tiesiog neveikia

0000433: obex-data-server crashed with SIGSEGV in g_main_context_dispatch() after transfer

There is a crasher that make o-d-s crash after a transfer, the stacktrace is not complete because some glib symbols were missing, I'm waiting a better one from reporters.

.
Thread 1 (process 1421):
#0 obex_io_callback (io_channel=0x938c348, cond=,
data=0x938e978) at src/ods-session.c:193
session = (OdsSession *) 0x0
error = (GError *) 0x0
ret =
__FUNCTION__ = "obex_io_callback"
0000001 0x00299e6b in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
0000002 0x002555e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
No symbol table info available.
0000003 0x002592d8 in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
0000004 0x00259817 in g_main_loop_run () from /lib/libglib-2.0.so.0
No symbol table info available.
0000005 0x08051b5d in main (argc=2, argv=0xbf91e594) at src/ods-main.c:195
session_connection =
error = (GError *) 0x0
context =
sa = {__sigaction_handler = {sa_handler = 0x80515f0 ,
sa_sigaction = 0x80515f0 }, sa_mask = {__val = {
0 }}, sa_flags = 0, sa_restorer = 0}
no_daemon = 1
system_bus = 0
show_version = 0
log = 0
debug = 0
options = {{long_name = 0x8064775 "no-daemon", short_name = 110 'n',
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0xbf91e4c8,
description = 0x806477f "Do not daemonize", arg_description = 0x0}, {
long_name = 0x8064790 "system-bus", short_name = 115 's', flags = 0,
arg = G_OPTION_ARG_NONE, arg_data = 0xbf91e4c4,
description = 0x8064888 "Use system bus instead of the default session bus", arg_description = 0x0}, {long_name = 0x80647b2 "log", short_name = 108 'l',
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0xbf91e4bc,
description = 0x806479b "Log all messages to syslog",
arg_description = 0x0}, {long_name = 0x80647b6 "debug",
short_name = 100 'd', flags = 0, arg = G_OPTION_ARG_NONE,
arg_data = 0xbf91e4b8,
description = 0x80647bc "Enable debugging messages",
arg_description = 0x0}, {long_name = 0x80647d6 "version",
short_name = 118 'v', flags = 0, arg = G_OPTION_ARG_NONE,
arg_data = 0xbf91e4c0,
description = 0x80648bc "Show version of obex-data-server and exit immediately", arg_description = 0x0}, {long_name = 0x0, short_name = 0 '\0',
flags = 0, arg = G_OPTION_ARG_NONE, arg_data = 0x0, description = 0x0,
arg_description = 0x0}}

0000223: Not possible to change timeout period

It should be possible to change timeout period. Not sure if it should be done globally with configure or possible to change at runtime as well...

0000401: obex-data-server crashes after BT transmission is finished

I'm using obex-data-server invoked by kbluetooth to transfer data to my mobile. unfortunately, everytime I try to transfer a file, after transmission is finished, obex-data-server crashes. Here is a part from dmesg:

obex-data-serve[8803]: segfault at c ip 0805feef sp bfde3480 error 4 in obex-data-server[8048000+1f000]
obex-data-serve[10198]: segfault at 14 ip 0805fef2 sp bf904df0 error 4 in obex-data-server[8048000+1f000]
obex-data-serve[10377]: segfault at 1d8 ip b784a246 sp bfc4fb60 error 4 in libgobject-2.0.so.0.2200.4[b7825000+36000]
obex-data-serve[10395]: segfault at c ip 0805feef sp bf93a060 error 4 in obex-data-server[8048000+1f000]
obex-data-serve[10510]: segfault at c ip 0805feef sp bfec1790 error 4 in obex-data-server (deleted)[8048000+1f000]
obex-data-serve[10553]: segfault at f0 ip b7780246 sp bf9c1990 error 4 in libgobject-2.0.so.0.2200.4[b775b000+36000]
obex-data-serve[10690]: segfault at c ip 0805feef sp bfd7e4c0 error 4 in obex-data-server[8048000+1f000]
obex-data-serve[10711]: segfault at 3f40 ip b7819246 sp bfc6fda0 error 4 in libgobject-2.0.so.0.2200.4[b77f4000+36000]
obex-data-serve[10888]: segfault at c ip 0805feef sp bffc74b0 error 4 in obex-data-server[8048000+1f000]

and obex-data-server dies. In an attachment you can find a strace from one of such executions. I can reproduce it every time. I don't think it is a kbluetooth problem, therefore I'm reporting it here. If you are sure it's just the other way, I'll report it to the KDE team.

0000351: Reikia momentinio nuotrauku ikelimo image plugin'ui

Reikia kad prie ten kur galima irasyti img URL butu galimybe tiesiai nusiusti nuotrauka i serveri ir kad laukelyje atsirastu URL be browsinimo

0000246: obex-data-server can not receive file through bluetooth with size large than 512 bytes

When I send a file with size >= 512 from phone to PC through bluetooth, obex-data-server will fail to receive it.

bluetooth-applet show following logging when it start.
** Message: adding killswitch idx 1 state 1
** Message: Reading of RFKILL events failed
** Message: killswitch 1 is 1
** Message: killswitches state 1
** (bluetooth-applet:3529): DEBUG: Unhandled UUID 00005005-0000-1000-8000-0002ee000001 (0x5005)
** Message: killswitch 1 is 1
** Message: killswitches state 1

obex-data-server console displays while transtering:

** Message: server socket created
** Message: Server created by: :1.40

** (obex-data-server:3465): WARNING **: Server path: /mypath
** Message: Client connecting

** (obex-data-server:3465): WARNING **: Session path: /mypath
** Message: Bluetooth address: 00:13:70:22:12:42
** Message: Creating server session
** Message: io callback
** Message: event: 1
** Message: event: 2
** Message: CMD_CONNECT requested
** Message: Version: 0x10. Flags: 0x00 OBEX packet length: 4000

** Message: Resizing stream chunks to 3800

** Message: event: 3
** Message: io callback
** Message: event: 1
** Message: event: 11
** Message: CMD_PUT requested at REQCHECK
** Message: header: 1
** Message: HDR_NAME: tbig
** Message: header: 195
** Message: HDR_LENGTH: 512
** Message: header: 66
** Message: ret=-1
** Message: event: 3
** Message: io callback
** Message: server session closed
** Message: closing connection

It is tested on
ubuntu 9.10 32bit (kernel 2.6.31-16)
bluetooth dongle BCM2035
obex-data-server 0.4.4-2build1(installed by default in ubuntu 9.10)

Phone: Nokia 3230

0000242: delete not compliant with obex specification

I have debugged a communication problem (with a own-developed client) until finding that the server does not follows the OBEX specification for deleting files, potentially causing data transmissions to be incorrectly handled as if they were file deletions. Since I have previously used the same client and never found a problem (both with other linux and Windows/Mac obex servers) I suspect that this may cause incompatibilities with many other clients out there, depending on their design.

I detected the problem in the 0.4.4 version ship with ubuntu karmic, but it is still present in the subversion trunk (I have not tested previous versions). The problem is due to the following: the function ods_obex_srv_put() in ods-obex.c considers that the PUT request is a file deletion (is_delete = TRUE) unless the client has previously sent any of the following headers: OBEX_HDR_BODY, OBEX_HDR_TYPE or OBEX_HDR_LENGTH. Since my client do not sends the type nor the length (unknown at transmission start) and it does not sends a body header in the first packet, obex-data-server incorrectly interpretes this as a file deletion and aborts the data transmission.

The OBEX specification (at least 1.2) says about delete:

"A PUT operation with NO Body or End-of-Body headers whatsoever should be treated as a delete request. Similarly, a PUT operation with an empty End-of-Body header requests the recipient to create an empty object. This definition may not make sense or apply to every implementation (in other words devices are not required to support delete operations or empty objects)."

That is, it mentions the complete "PUT operation" (not the first packet) and includes a "whatsoever" word. In another section, the specification is even more clear about this fact:

"A PUT request consists of one or more request packets, the last of which has the Final bit set in the opcode. The implementer may choose whether to include an object Body header in the first packet, or wait until the response to the initial packet is received before sending any object body chunks."

I was one of those implementers choosing not to send a body header in the first packet. My current workarround in order to improve the compatibility with previous obex-data-server versions it will be to include a OBEX_HDR_TYPE.

0000233: File corruption when transferring with nautilus

Sometimes when transferring multiple files with nautilus some files come out corrupted. In the case of images, the bottom part is cut off, if multiple images are corrupted, those images are cut off at the exactly same place.

Can't seem to reproduce when transferring files one by one, only when bunch of files are selected and copied.

Nautilus: 2.26
gvfs: 1.4.1
ods: 0.4.5

0000227: Failing to compile on my machine.

First error was stdlib.h was not included in src/ods-common.c.

My next error is im getting undefined reference to `OBEX_FindInterfaces' in ods-obex.c.

I'm not sure how to fix this but I can see that OBEX_FindInterfaces is declared in obex.h.

Here's the error output ..

src/ods-obex.o: In function `ods_obex_setup_usbtransport':
/root/software/build/bluez/obex-data-server/src/ods-obex.c:408: undefined reference to `OBEX_FindInterfaces'
collect2: ld returned 1 exit status

0000215: USE_USB guards don't protect missing usb.h

Not entirely sure which package usb.h comes in, but in any case, I did configure with usb disabled and I get build errors because of usb.h. If you move '#ifdef USE_USB' above the includes (but below '#include "config.h"'), all is well.

This occurs in ods-usb.c and ods-usb.h.

0000213: Check dbus service file when running in system bus

When running in system bus (ods -s), check dbus .service file on startup so that ods would have -s arg in .service file!

0000160: Ability to send files from memory.

Morning Tadas,

I've been working on a concept here which requires us to push files to a remote device however the file doesn't exist on the FS only in memory as a binary string. This comes about because the environment the app will run on only has a read-only FS so all content which is being sent to the remote device only exists in memory.

I feel it might be nice to have a method in ODS which allows us to pass the binary string to ODS and send that file to the remote device without us having to write it to the FS first.

What are your thoughts on this?

Thanks mate, I hope you're well :-)

Heston

0000003: Translation'ai veikia neoptimaliai

Dabar kiekvienai frazei ishverti reikia kreiptis i DB. Vietoj to geriau prefetchinti vertimus (t.y. viska ishversti ir laikyti $GLOBALS variable). Tai galima igivendinti su funkcija Translate::Prefetch() (egzistuoja lazeriai branche).

Kita vertus, geriau butu viska optimizuot nerashant daug kodo. Galbut butu imanoma padaryti, kad smartyje naudojant {_}{/_} bloka butu translatinami tik visi blokai vienu kartu (nzn ar ishvis imanoma taip suimplementuot smartyje).

0000012: Sutvarkyti security checkinima

Dabar 'auto' branche prihardcodinta stebuklingu security check'inimu. Reikia nuspresti kas gali buti panaudota (ir kaip) generic branche (weblancet_db). Ir atatinkamai reikia sumerginti.

0000022: Perkelinejant item'a su Move($newId) nesutvarko level ir position'u.

Kai perkelinejamas item'as su ta Move funkcija, jei jis perkeliamas i kita level'i tai duombazej nepasikeicia niekas. Taip pat reikia istestuoti kaip ten su pozicijojm, man rodos nesitvarko.

0000106: nesudeti visi actionai i weblancet_clean ir web;ancet_b_vupraktika

nesudeti info i weblancet_clean ir praktika del to negalima kai kuriu elementu istrinti ir t.t.

0000105: meniu neteisingai atvaizduojamas

REikia apdaryti kad uppercasintu meniu pavadinimus ir kazkodel nerodo meniu punkto kai buna mouseover.

0000010: Suimplementuoti 'Override' direktorija

Panaikinti 'Templates' direktorija ir vietoj to naudoti 'Override' direktorija, kur butu galima overridinti ne tik templatus bet ir klases.

0000066: Image manager in TinyMCE

If you import image, then delete it and import another one with the same name it shows the old image, not new, so you need to rename new image and can't upload with the same that was there before.

0000064: Importing Images into content with TinyMCE

When i try to put in any king of image (.jpg .png etc.) writing url manualy, the image does not appear in content. The editor just writes extra parameters and the image doesn't appear.

/UserFiles/Images/kontaktai_image.jpg&Width=560&Height=200&Method=5

0000110: nesimato pakeitimu sukurtu atskiruose straipsniuose,

Prie projekto Subertres, redaguojant atskirus staripsnius pvz. is Produktų katalogas, nesimato pakeitimu "pakeitimų peržiūroje", matos itik vidiniuose elementuose kada keista...

0000133: europraktika

Prisijungus su studentu Tadas Matiejunas, issiunciau laiska imonei, pirma akrta paluzo ir neuzsikrve, tada antra karta viskas ok, prikabinau faila, o tada studentas jau negali pasirinkti pasiulymo - paspaudzia -sutinku, ir niekas nesidaro.

0000134: išsikriapo puslapis kuriant skelbimą organziacijose

prisijungaint prie organziacijų (t.y. sukūriau naują ) ir rašaupraktiksos kelkbim, bet tas langas labai išsimėtė. pvz. save mygtukas į viršų užšukęs ir pan.

vienas laukas per platus ir pan.

0000130: Studento prisijungimo pirmas langas

Prisijungus studentui prie IS, nedingsta pagrindinio puslapio mygtukai, ir dabartiniu esanciu nereikia. bus kur atsiunte Deimante penktadieni

Apacioje mygtuke turi vietoj anglisko uzraso buti lietuviskas - Erasmus informacnė sistema, Gauminos logotpas - lietuviskas,

Virš prisijungimo duomenų kur juo įvesti, turi būti užrašas - VU informacinė sistema

Studento darbinis laukas - pagrindiniame lauke prisijungimas

Jūs esate prisijungę -> prie VU IS prisijungęs/ usi Studentas Studentauskas

Jūsų paraiškos statusas -> Jūsų virtuali darbo vieta

žemiau parašyti

Erasmus praktikos etapai:

užrašas: dabartinis etapas: su aprašymais atsiranda tik kai užpildomas CV.

Dabartinis etapas: - šriftas turi būti tuo gražiu šriftu.
Dabartinio etapo aprašus įdėti į rėmelius. - kaip anketose būna laukas informacijai parašyti.

Jūsų praktikos dokumentai -> Praktikos paieškos dokumentai
(išvardinti sąrašas)
ir taip pat išsiskiria dokumentai pagal Deimantės pateiktą sąrašą
Praktikos vietos paieška -> patvirtinta praktikos vieta

Paraiškos Europraktikos mob. stipendijai gauti pateikimas -> skirta praktikos stipendija
Praktikos plano pateikimas -> suderintas praktikos planas

erasmus prktikos etapai:

0000104: Neprisijungia prie TVS

Neprisijungia prie TVS jeigu esi katik atsijunges ir URL buna ?Action=Security/Logout