aseman-land / cutegram Goto Github PK

Hello,

Currently, it is impossible to build Cutegram version 2.1.0 with libqtelegram (rev 87), because something changed in libqtelegram since the release of Cutegram 2.1.0, and it is not easy for maintainers.

It would be a lot easier if Cutegram were to fix the version of libqtelegram used for each release.

It would make building Cutegram way more reliable, and potentially easy debugging.

for telegram desktop and android, when you send a gif file, you can see it moving inside the messenger windows. on cutegram you need to click on it and it will open the default image viewer but shows only a static image inside

also on cutegram when you drag and drop it will convert the *,gif to a *.jpeg....it should keep the *-gif as it is by default.

How fix this?

Could you please create a tag for version 2.1.0? :) It is than more comfortable to point the source service of the openSUSE Build Service to the right code.

I'd love to have this option in cutegram ! Thank you for your work !

Hello guys, I am trying to update the cutegram package on Mageia, but I am getting the follow error with 2.2.0 version:

$ cutegram

(cutegram:3665): GLib-GObject-WARNING **: cannot register existing type 'GstObject'

(cutegram:3665): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(cutegram:3665): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed

(cutegram:3665): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed

(cutegram:3665): GStreamer-CRITICAL **: gst_element_class_set_details_simple: assertion 'GST_IS_ELEMENT_CLASS (klass)' failed

(cutegram:3665): GStreamer-WARNING **: static caps 0x7f3fecae3650 string is NULL

(cutegram:3665): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed

(cutegram:3665): GStreamer-WARNING **: static caps 0x7f3fecae35d0 string is NULL

(cutegram:3665): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed

(cutegram:3665): GStreamer-WARNING **: static caps 0x7f3fecae3650 string is NULL

(cutegram:3665): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed

It is related with GStreamer but would you have some idea about what is it?

Thanks.

If I change the output screen when Cutegram is minimized to tray, it crashes after I try to open it.
Can't copy-paste Apport's logs, but here is a screen


There are more fields, but they are not screenshotable. I can try to get a true stacktrace if that's not enough

I suggest to join your efforts with tdesktop instead of forking a dead project.

I already know that tdesktop guys very slow and they don't merge requests until a while but enlarging desktop client community is in favor of the community instead of split the community between two projects,

If a user's name contains emoticon, cutegram only shows rectangle. Both Android and browser app can display emoticon in name. They show them differently though.

I cannot receive anymore a sound when a message arrives, i see the message in the tray but can't ear the sound, i have all sounds enabled and even tried to select a custom sound.
I use ubuntu and installed the deb package

Never mind, i muted the contact -.-" i'm sorry...

Cutegram hangs on startup with:

(cutegram:4923): GLib-GObject-WARNING **: cannot register existing type 'GstObject'
(cutegram:4923): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
(cutegram:4923): GLib-GObject-CRITICAL **: g_type_register_static: assertion 'parent_type > 0' failed
(cutegram:4923): GLib-CRITICAL **: g_once_init_leave: assertion 'result != 0' failed
(cutegram:4923): GStreamer-CRITICAL **: gst_element_class_set_details_simple: assertion 'GST_IS_ELEMENT_CLASS (klass)' failed
(cutegram:4923): GStreamer-WARNING **: static caps 0x7f833b28cc90 string is NULL
(cutegram:4923): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed
(cutegram:4923): GStreamer-WARNING **: static caps 0x7f833b28cc10 string is NULL
(cutegram:4923): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed
(cutegram:4923): GStreamer-WARNING **: static caps 0x7f833b28cc90 string is NULL
(cutegram:4923): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 'mini_object != NULL' failed

System:
Ubuntu 14.04 x64

Built from git.

No icon is in tray on Mint 17 (Ubuntu) + XFCE

I have 2 step auth enabled in my account and when I enter my phone number while logging in, message arrives to my phone, saying something like that: "this app doesn't support 2-step authentication".

Cutegram work well in KDE 5 , but tray icon does not fit with the Breeze default theme.

It happens in Linux and Windows. Cutegram 2.1.0.

Before this I had 2.2.0 and everything was working fine.
Now I upgraded to 2.2.1 and when the program starts, it freezes like this:

Terminal output shows this:

QVariant::load: unable to load type 1208.
QVariant::save: unable to save type 'QJSValue' (type id: 1208).

QVariant::load: unable to load type 1208.
QVariant::save: unable to save type 'QJSValue' (type id: 1208).

QVariant::load: unable to load type 1208.
QVariant::save: unable to save type 'QJSValue' (type id: 1208).

and so on.
OS: Linux Mint 17 w/KDE.

When the Cutegram window is open, it consumes significant CPU time (constant 30% of one core on my laptop - i7-3520M). When the window is closed (Cutegram still running in background), it consumes negligible CPU. I see a lot of hits to the VIDIOC_INT_RESET ioctl in strace, so maybe this is related to some sort of camera code? Otherwise, I guess there's some other over-agressive loop in the renderer.

Cutegram is a huge battery killer currently, if the window gets left open.

You can see:
https://www.transifex.com/projects/p/cutegram/

Chinese is fully translated and reviewed right now, so please merge it to new coming release.

From commit log and released changelog I can see a 2.3.0 is available for Linux, but I cannot find any tagged 2.3.0 release here.
I am maintaining a cutegram package for archlinux, a tagged release will help me release a stable version for archlinux user.
Thank you very much

I could not find any way to add a contact in Cutegram, and had to use Telegram to do it.

When a Cutegram window (like "Add contact") is opened, the explanation text is cut by the window if it is larger than the original english string. You can test it with "Add contact" window in Asturian language.

Affects only those who are not in contact list. When I open a conversation with them it starts endless sync, messages never get there and answered.
Fo example, there is a bot (telerobot, tg://resolve?domain=telerobot) who answers the weather if one sends him "погода москва"
Nothing happens here, endless sync + endless sending

when you record a voicemessege(voiceM) on cutegram it will saved and send in *mp3 format

my 3sec voiceM from desktop is about 45kIB (mp3)
my 9 sec voiceM from android is about 14kiB (opus)

because telegram is heavily used in mobile systems the mp3 files are much to big, wich leads to a to big delay for sending the file (telegram works greate(fast!) for small "edge"-connections, cutegram dont).

so my request is: please use the same as telegram uses (*.opus files)
http://www.opus-codec.org/comparison/
on top of that opus is the only format for speach and music, an internet standard and one of my favorites to convert my music in :)

because of a new phone number i had to delete the old one. so i removed all configs in ~/.config/Cutegram
now i used my new number (already registered via telegram on android)
the first thing i experienced was that there are no avatar (user pictures). next i tried to send a file, but nothing happens. at last i've seen that there are already 10new messeges for my avalable but not a single one poped up in cutegram

console output:
cutegram
service is "org.kde.StatusNotifierItem-3312-1"
kf5.kiconthemes: "Theme tree: (Breeze)"
Registering a client interface to the KStatusNotifierWatcher
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesGetDialogs(qint32, qint32, qint32): AUTH_KEY_UNREGISTERED"
void TelegramQml::getFile(FileLocationObject_, qint64, qint32) : Can't detect size of: ChatPhotoObject(0x307c1d0)
void TelegramQml::getFile(FileLocationObject_, qint64, qint32) : Can't detect size of: ChatPhotoObject(0x307cc40)
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::accountUpdateStatus(bool): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesGetHistory(const InputPeer&, qint32, qint32, qint32): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesReadHistory(const InputPeer&, qint32, qint32, bool): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesGetHistory(const InputPeer&, qint32, qint32, qint32): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesSetTyping(const InputPeer&, const SendMessageAction&): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesSetTyping(const InputPeer&, const SendMessageAction&): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesSetTyping(const InputPeer&, const SendMessageAction&): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesSendMessage(const InputPeer&, const QString&, qint64): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesGetDialogs(qint32, qint32, qint32): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesReadHistory(const InputPeer&, qint32, qint32, bool): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesSetTyping(const InputPeer&, const SendMessageAction&): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesSetTyping(const InputPeer&, const SendMessageAction&): AUTH_KEY_UNREGISTERED"
void TelegramQml::error(qint64, qint32, QString) "qint64 Api::messagesGetHistory(const InputPeer&, qint32, qint32, qint32): AUTH_KEY_UNREGISTERED"
[....]

Kubuntu 15.04
Plasma 5.3.1
Qt 5.4.1
uname -mr -> 3.19.0-18-lowlatency x86_64

when you send a *.gif file from cutegram to another telegram client it will be send as a unknown file. just like an *.iso or *.doc ... you cant see it directly in the chat.

when you send a *.gif from telegram itself, you will see that it is a image in cutegram (but it isnt moving, wich is another bug)

Allow customize UI elements such as checkboxes, radiobuttons, buttons, text edits etc. via theme.

Cutegram 2.3.0
Ubuntu 14.10

I started a secret chat with a client that doesn't automatically accept it (Android does that, on Ubuntu phone it doesn't, at least yet). I saw an obscured spinner in the dark header of the secret chat, I take it was waiting for the chat to be accepted. Out of curiosity, I wrote a short message. Immediately I got.. like a response (although this didn't come from the Ubuntu phone), saying:
"Media files are not currently supported on secret chats"
Even once I accepted the secret chat on the other device at this point, further messages in that secret chat would continue to get the above mentioned reply.

I think simply preventing from sending a message before the chat is accepted by the other party will resolve the issue :)

Please see screens. Compare fonts on Cutegram and Telegram Desktop

OS: Kubuntu 15.04
DE: KDE 5
Font: Droid Sans 10 regular
Smoothing: Enabled
Sub-pixel rendering: System default
Hiting: System default

As i said in the title, "Proxy settings", "About (Cutegram/Aseman)", "Custom" and "System color" words are untranslatable in settings menu, also the second line of Aseman description is not translated correctly. However there are others strings like "Hijri", "2Shanbe", "Moharram" etc which i have no idea where they are and what mean.

I attach screenshoots:

Thank you.

It would be great to have counter on unity icon, like in Telegram ;)

This is for wishlist.

Please add stickers support. At least for incoming messages.

I'm add first commit 19 days ago. Why Russian language not available on Cutegram now?

The tdesktop client and webapp of telegram supported these features:

• AT(@) username
• reply to a message

Steps to reproduce:

1. Enable detailed list
2. Let someone send you a message with emoji. (Or send one to yourself)

That is wrong:
The last message shown in detailed list will only show half of the line.
The line seems to be higher than the display size.

My environment:

• Archlinux
• Cutegram 2.3

Hello, I am using Cutegram 2.0.0 from Mageia package. But the problem in chat with non-contacts remains. The history of chat not update and I can not to send message for them. Is there some way how I can to provide a log or something about it? Thanks!

First of all I want to mention that this is the most beautiful telegram client I have seen so far :D

I'm having some issues thou:

On Windows the Application just hangs in a "bootloop" if i start it a second time (not at the same time. registration was no problem but it just hangs after restart).
I'm running into the same "loop" after i come back from suspend on arch linux.

Are there some log files i could provide to give you guys more informations about this bug?

OS Specs
Windows:
Windows 8 Pro 64-bit
AMD FX-8350

Linux:
Arch Linux x64
GNOME
Intel I7-4710HQ

Keep up the good work!

Tray Icon in message menu is working but is invisible.

One of the most useful feature in TDesktop that we really apreciate in Cutegram..

There are lot of AUTH_KEY_UNREGISTERED errors in console output, in windows and linux.

For example:
qint64 Api::accountUpdateStatus(bool): AUTH_KEY_UNREGISTERED

Hi. I try to build latest code and give me the following error:

$ make
cd Cutegram/ && ( test -e Makefile || /usr/lib/qt/bin/qmake /tmp/cosicas/Cutegram/Cutegram/Cutegram.pro PREFIX=/usr -o Makefile ) && make -f Makefile 
make[1]: Entering directory '/tmp/cosicas/Cutegram/build/Cutegram'
g++ -c -pipe -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -Wall -W -D_REENTRANT -fPIE -DNATIVE_ASEMAN_NOTIFICATION -DLINUX_NATIVE_ASEMAN_NOTIFICATION -DQT_NO_DEBUG -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I/usr/lib/qt/mkspecs/linux-g++ -I../../Cutegram -isystem /usr/include/libqtelegram -I/tmp/cosicas/Cutegram/build/Cutegram/../build/include/libqtelegram -isystem /usr/include/qt -isystem /usr/include/qt/QtQuick -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtQml -isystem /usr/include/qt/QtNetwork -isystem /usr/include/qt/QtSql -isystem /usr/include/qt/QtXml -isystem /usr/include/qt/QtDBus -isystem /usr/include/qt/QtCore -I/tmp/cosicas/Cutegram/build/Cutegram -I. -o main.o ../../Cutegram/main.cpp
g++ -c -pipe -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -Wall -W -D_REENTRANT -fPIE -DNATIVE_ASEMAN_NOTIFICATION -DLINUX_NATIVE_ASEMAN_NOTIFICATION -DQT_NO_DEBUG -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I/usr/lib/qt/mkspecs/linux-g++ -I../../Cutegram -isystem /usr/include/libqtelegram -I/tmp/cosicas/Cutegram/build/Cutegram/../build/include/libqtelegram -isystem /usr/include/qt -isystem /usr/include/qt/QtQuick -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtQml -isystem /usr/include/qt/QtNetwork -isystem /usr/include/qt/QtSql -isystem /usr/include/qt/QtXml -isystem /usr/include/qt/QtDBus -isystem /usr/include/qt/QtCore -I/tmp/cosicas/Cutegram/build/Cutegram -I. -o cutegram.o ../../Cutegram/cutegram.cpp
g++ -c -pipe -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -Wall -W -D_REENTRANT -fPIE -DNATIVE_ASEMAN_NOTIFICATION -DLINUX_NATIVE_ASEMAN_NOTIFICATION -DQT_NO_DEBUG -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_QML_LIB -DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I/usr/lib/qt/mkspecs/linux-g++ -I../../Cutegram -isystem /usr/include/libqtelegram -I/tmp/cosicas/Cutegram/build/Cutegram/../build/include/libqtelegram -isystem /usr/include/qt -isystem /usr/include/qt/QtQuick -isystem /usr/include/qt/QtWidgets -isystem /usr/include/qt/QtGui -isystem /usr/include/qt/QtQml -isystem /usr/include/qt/QtNetwork -isystem /usr/include/qt/QtSql -isystem /usr/include/qt/QtXml -isystem /usr/include/qt/QtDBus -isystem /usr/include/qt/QtCore -I/tmp/cosicas/Cutegram/build/Cutegram -I. -o telegramqml.o ../../Cutegram/telegramqml.cpp
../../Cutegram/telegramqml.cpp: In member function ‘void TelegramQml::sendMessage(qint64, const QString&)’:
../../Cutegram/telegramqml.cpp:804:84: error: no matching function for call to ‘Telegram::messagesSendEncrypted(qint64&, qint64&, const QString&)’
         sendId = p->telegram->messagesSendEncrypted(dId, p->msg_send_random_id, msg);
                                                                                    ^
../../Cutegram/telegramqml.cpp:804:84: note: candidate is:
In file included from ../../Cutegram/telegramqml.cpp:30:0:
/usr/include/libqtelegram/telegram.h:139:12: note: qint64 Telegram::messagesSendEncrypted(qint32, qint64, qint32, const QString&)
     qint64 messagesSendEncrypted(qint32 chatId, qint64 randomId, qint32 ttl, const QString &text);
            ^
/usr/include/libqtelegram/telegram.h:139:12: note:   candidate expects 4 arguments, 3 provided
../../Cutegram/telegramqml.cpp: In member function ‘bool TelegramQml::sendFile(qint64, const QString&, bool)’:
../../Cutegram/telegramqml.cpp:1114:94: error: no matching function for call to ‘Telegram::messagesSendEncryptedPhoto(qint64&, qint64&, QString&)’
             fileId = p->telegram->messagesSendEncryptedPhoto(dId, p->msg_send_random_id, file);
                                                                                              ^
../../Cutegram/telegramqml.cpp:1114:94: note: candidate is:
In file included from ../../Cutegram/telegramqml.cpp:30:0:
/usr/include/libqtelegram/telegram.h:140:12: note: qint64 Telegram::messagesSendEncryptedPhoto(qint32, qint64, qint32, const QString&)
     qint64 messagesSendEncryptedPhoto(qint32 chatId, qint64 randomId, qint32 ttl, const QString &filePath);
            ^
/usr/include/libqtelegram/telegram.h:140:12: note:   candidate expects 4 arguments, 3 provided
../../Cutegram/telegramqml.cpp:1145:105: error: no matching function for call to ‘Telegram::messagesSendEncryptedVideo(qint64&, qint64&, QString&, QByteArray&)’
             fileId = p->telegram->messagesSendEncryptedVideo(dId, p->msg_send_random_id, file, thumbData);
                                                                                                         ^
../../Cutegram/telegramqml.cpp:1145:105: note: candidate is:
In file included from ../../Cutegram/telegramqml.cpp:30:0:
/usr/include/libqtelegram/telegram.h:141:12: note: qint64 Telegram::messagesSendEncryptedVideo(qint32, qint64, qint32, const QString&, qint32, qint32, qint32, const QByteArray&)
     qint64 messagesSendEncryptedVideo(qint32 chatId, qint64 randomId, qint32 ttl, const QString &filePath, qint32 duration, qint32 width, qint32 height, const QByteArray &thumbnailBytes);
            ^
/usr/include/libqtelegram/telegram.h:141:12: note:   candidate expects 8 arguments, 4 provided
In file included from ../../Cutegram/telegramqml.cpp:26:0:
../../Cutegram/objects/types.h: At global scope:
../../Cutegram/objects/types.h:5499:13: warning: ‘initialized’ defined but not used [-Wunused-variable]
 static bool initialized = initialize();
             ^
Makefile:1059: recipe for target 'telegramqml.o' failed
make[1]: *** [telegramqml.o] Error 1
make[1]: Leaving directory '/tmp/cosicas/Cutegram/build/Cutegram'
Makefile:43: recipe for target 'sub-Cutegram-make_first-ordered' failed
make: *** [sub-Cutegram-make_first-ordered] Error 2

It seems that there is no voice message support on any of the desktop apps. Also from what I gather it is just opus audio at a specific bitrate there'd just need to be a button to record and send it.

In my experience this is one of the more fun features :)

Looks like it just needs to be opus audio for widest support... https://github.com/DrKLO/Telegram/issues/809 So I imagine this would require buildsing ffmpeg with opus support or using libopus directly which I think is what mobile clients do.

When trying to compile Cutegram 2.2.0 it fails with the following missing header files:

[   46s] In file included from ../../Cutegram/telegrammessagesmodel.cpp:22:0:
[   46s] ../../Cutegram/telegramqml.h:24:37: fatal error: types/inputfilelocation.h: No such file or directory
[   46s]  #include "types/inputfilelocation.h"
[   46s]                                      ^
[   46s] compilation terminated.
[   46s] Makefile:1307: recipe for target 'telegrammessagesmodel.o' failed
[   46s] make[1]: *** [telegrammessagesmodel.o] Error 1
[   46s] make[1]: *** Waiting for unfinished jobs....
[   46s] In file included from ../../Cutegram/telegramdialogsmodel.cpp:20:0:
[   46s] ../../Cutegram/telegramqml.h:24:37: fatal error: types/inputfilelocation.h: No such file or directory
[   46s]  #include "types/inputfilelocation.h"
[   46s]                                      ^
[   46s] compilation terminated.
[   46s] In file included from ../../Cutegram/telegramqml.cpp:22:0:
[   46s] ../../Cutegram/telegramqml.h:24:37: fatal error: types/inputfilelocation.h: No such file or directory
[   46s]  #include "types/inputfilelocation.h"
[   46s]                                      ^
[   46s] compilation terminated.
[   46s] Makefile:1298: recipe for target 'telegramdialogsmodel.o' failed
[   46s] make[1]: *** [telegramdialogsmodel.o] Error 1
[   46s] Makefile:1281: recipe for target 'telegramqml.o' failed
[   46s] make[1]: *** [telegramqml.o] Error 1
[   46s] In file included from ../../Cutegram/cutegram.cpp:29:0:
[   46s] ../../Cutegram/telegramqml.h:24:37: fatal error: types/inputfilelocation.h: No such file or directory
[   46s]  #include "types/inputfilelocation.h"
[   46s]                                      ^
[   46s] compilation terminated.

I used the following Ubunutu PPA to install Cutegram on my Ubuntu 14.04.2 "trusty" system (x86_64):

% cat /etc/apt/sources.list.d/aseman-desktop-apps-trusty.list
deb http://ppa.launchpad.net/aseman/desktop-apps/ubuntu trusty main
# deb-src http://ppa.launchpad.net/aseman/desktop-apps/ubuntu trusty main

However, I can no longer install from this repository, as the last version depends on "ffmpeg":

% sudo apt-get install cutegram                              
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 cutegram : Depends: ffmpeg but it is not installable
E: Unable to correct problems, you have held broken packages.

Cmd+Click on the messages will have multiple context menu get displayed

And there is no way to dismiss/hide them.

OS: Mac OSX version 10.10.4
Cutegram 2.3

right now cutegram uses gstremer0.10 for audiooutput (voicemessages). 0.10 is depricated and nobody installs it by default anymore.

for example when you run kubuntu 15.04 this feature wont work, because the plugin gstreamer0.10-plugins-bad isnt installed...

now there are 2 things you could do -> port is to gspreamer 1.0 diretly or port it to qt phonon (should be used by the qt multimedia framework by default)

Hi,

seems I need to authenticate every time cutegram starts. That is probably not expected ... ?

Also, everytime I quit cutegram, it loses its settings. Could this be some permission issue, and how to troubleshoot that? Where should cutegram store its settings? Only in ~/.config/Cutegram ?

I use ibus-pingyin for Chinese input, but it cannot use in GNOME 3.14 in cutegram. Others app works fine.

OS: Debian Jessie
GNOME 3.14.1

...Since Saturday April 11. Which is the reason? Closed for maintenance? Are they going to change the domain name? Is it the end for aseman-land?

Hello all the Aseman team I noted that the Cutegram's systray icon is not visiible on pantheon on elementary OS, I noted that the same issue is occurring on Ubuntu GNOME and Mint (issues #21 and #23) can you solve it? please?

Also I recommend you change the tray icon from the actual textured airplane to a flat red circle with a fllat white airplane, why? because it will make it look better, also when you get a message the tray icon changes to a red flat circe with a number inside, the new icon will make it look more consistent and beautyfull having a cutegram tray icon wich when you get a message turns the airplane into the number

I have a screen of 138 DPI and KDE5 auto-configured it for me. With this setting, the participants list get crowded with icons overlapping each other. A workaround will be setting DPI to 96 currently.

Here is a screenshot made on my laptop:

The other part of the UI works great under 138 DPI, so I guess there will be a solution to this problem.

My configuration:

• Cutegram 2.2.0-stable
• Archlinux
• KDE Plasma 5.3
• qt5 5.4.1