[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Cesar Garcia changed: What|Removed |Added CC||cesa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #30 from Cesar Garcia --- Also happening on Plasma 6 with Dolphin 24.02.2. I am using k3s instead of Docker, and also the location bar starts working again once i stop k3s and kill all the containers. Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 Cesar Garcia changed: What|Removed |Added CC||cesa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459957] New: Problem with colors in breeze dark mode
https://bugs.kde.org/show_bug.cgi?id=459957 Bug ID: 459957 Summary: Problem with colors in breeze dark mode Classification: Applications Product: okular Version: 22.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: cesarjesusgeldre...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Active Dark Breeze color in Settings 2. Open a PDF 3. Select a menu tools or use an annotation. OBSERVED RESULT When using a tool, such as a typewriter, or drawing geometric shapes, the selection guide lines turn from black to white, making them invisible in a white page. Also, the text balloons indicating the selected tool appear with text and background of the same color (white). This makes them impossible to read. EXPECTED RESULT That the selection guide lines, and balloon text, are visible in Breeze Dark mode. SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458574] Denied access to save an opened file on Windows
https://bugs.kde.org/show_bug.cgi?id=458574 Cesar changed: What|Removed |Added CC||cesarjesusgeldres14@gmail.c ||om --- Comment #9 from Cesar --- (In reply to Albert Astals Cid from comment #6) > Git commit 8e93995e3caa49bcd7c2c862a66f959160194fda by Albert Astals Cid. > Committed on 04/09/2022 at 20:26. > Pushed by aacid into branch 'release/22.08'. > > Fix saving files on Windows > > turn a move into a copy and remove > > Seems to work better with windows way of working with open files being > overwritten and stuff > > M +19 -3part/part.cpp > > https://invent.kde.org/graphics/okular/commit/ > 8e93995e3caa49bcd7c2c862a66f959160194fda I have the same error. How can I repair it? I have the Microsoft Store version and I have no programming skills. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 451770] New: Erro de API AO BAIXAR TEMAS E APEIS DE PAREDE
https://bugs.kde.org/show_bug.cgi?id=451770 Bug ID: 451770 Summary: Erro de API AO BAIXAR TEMAS E APEIS DE PAREDE Product: Discover Version: 5.24.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: juliow...@hotmail.com CC: aleix...@kde.org Target Milestone: --- Problema API baixar temas e papéis de parede da erro na API DEBIAN BULLSEYE, E KDE PLASMA está na hora de corrigir pensei que era problema no debian mas quando instalei o plasma desktop o problema persistiu -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 451241] New: erro no centro de informações kinfocenter
https://bugs.kde.org/show_bug.cgi?id=451241 Bug ID: 451241 Summary: erro no centro de informações kinfocenter Product: kinfocenter Version: 5.23.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Info Assignee: plasma-b...@kde.org Reporter: juliow...@hotmail.com CC: hubn...@gmail.com Target Milestone: --- 1-O programa "kinfocenter" está funcionando como se fosse o gerenciador de configurações do sistema! Não mostra informações de sistema! 1-The "kinfocenter" program is working as if it were the system configuration manager! Does not show system information! 2-print screen não funciona 2-print screen does not work -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 447449] New: I get an error message that api-ms-win-downlevel-kernel32-l2-1-0.dll is not installed
https://bugs.kde.org/show_bug.cgi?id=447449 Bug ID: 447449 Summary: I get an error message that api-ms-win-downlevel-kernel32-l2-1-0.dll is not installed Product: krita Version: 5.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: cesarnavaarteaga...@gmail.com Target Milestone: --- I downloaded version 5.0 of krita but when I open it I see that I am missing the file I api-ms-win-downlevel-kernel32-l2-1-0.dll but when I close the window the program opens normally, there is really an error With the program? I cannot update the file because other programs do not work, this did not happen to me with previous versions or with betas 5.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 428868] New: Error al ejecutar sqldeveloper 20.2
https://bugs.kde.org/show_bug.cgi?id=428868 Bug ID: 428868 Summary: Error al ejecutar sqldeveloper 20.2 Product: konsole Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: single-process Assignee: konsole-de...@kde.org Reporter: crom...@promad.com.mx Target Milestone: --- Created attachment 133160 --> https://bugs.kde.org/attachment.cgi?id=133160&action=edit describe el error al ejecutar sqldeveloper S/home/cromero/Imágenes/Screenshot_20201108_211403.png Al ejecutar sqldeveloper me manda error adjuntado y si lo ejecuto por consola si abre de manera correcta -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well on decimal numbers with es_PE locale.
https://bugs.kde.org/show_bug.cgi?id=406388 --- Comment #16 from Cesar Garcia --- I tried to find the bottom of the rabbit hole and found that Qt (and maybe others) parses the Unicode Common Locale Data Repository (CLDR) for their locale info. In 2016 Perú issued a government resolution [1] where the comma must be used as decimal separator. I found the CLDR bug tracker and there is an issue [2] where they are aware of the change but are currently using the dot as is the common usage in the country right now. A proper fix would be that CLDR updates their data so other projects (including Qt) will use the correct separator. This won't happen anytime soon so a patch where the comma can also be used in the krunner calculator will be a welcome change. [1] https://www.sbn.gob.pe/Repositorio/resoluciones_sbn/RESOLUCION_559_0309.pdf [2] https://unicode-org.atlassian.net/projects/CLDR/issues/CLDR-11048 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well on decimal numbers with es_PE locale.
https://bugs.kde.org/show_bug.cgi?id=406388 --- Comment #14 from Cesar Garcia --- Just checked other systems (Libreoffice Calc, JS engines) and they all used dot for the separator on es_PE locale. Also asked other Peruvian people and while ISO says that the comma is used everybody uses the dot so i am not sure anymore if is a bug with Qt. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well on decimal numbers with es_PE locale.
https://bugs.kde.org/show_bug.cgi?id=406388 Cesar Garcia changed: What|Removed |Added Summary|Calculator doesn't work |Calculator doesn't work |well with locales using |well on decimal numbers |point instead of comma. |with es_PE locale. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388
Cesar Garcia changed:
What|Removed |Added
Ever confirmed|1 |0
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO |---
--- Comment #13 from Cesar Garcia ---
I have made more tests and seems that the bug is in Qt. I switched my locale to
Colombia (also uses the comma as decimal separator) and Krunner works as
expected. The system locale seems OK (added en_US as control)
$ LC_ALL=en_US.UTF-8 locale -kc LC_NUMERIC
LC_NUMERIC
decimal_point="."
thousands_sep=","
grouping=3;3
numeric-decimal-point-wc=46
numeric-thousands-sep-wc=44
numeric-codeset="UTF-8"
$ LC_ALL=es_PE.UTF-8 locale -kc LC_NUMERIC
LC_NUMERIC
decimal_point=","
thousands_sep="."
grouping=3;3
numeric-decimal-point-wc=44
numeric-thousands-sep-wc=46
numeric-codeset="UTF-8"
$ LC_ALL=es_CO.UTF-8 locale -kc LC_NUMERIC
LC_NUMERIC
decimal_point=","
thousands_sep="."
grouping=3;3
numeric-decimal-point-wc=44
numeric-thousands-sep-wc=46
numeric-codeset="UTF-8"
Then made a simple Qt app to check the number formatting of Colombia and Perú
(should be the same)
#include
#include
#include
int main(int argc, char *argv[])
{
QCoreApplication a(argc, argv);
double number = 2565.25;
QLocale peLocale(QLocale::Spanish, QLocale::Peru);
QString ss = peLocale.toString(number);
auto point = peLocale.decimalPoint();
qDebug() << "PE Separator:" << point;
qDebug()<<"PE formatted number: " << ss;
QLocale coLocale(QLocale::Spanish, QLocale::Colombia);
ss = coLocale.toString(number);
point = coLocale.decimalPoint();
qDebug() << "CO Separator:" << point;
qDebug()<<"CO formatted number: " << ss;
return 0;
}
But the results were different:
PE Separator: '.'
PE formatted number: "2,565.25"
CO Separator: ','
CO formatted number: "2.565,25"
I am gonna open a bug report with Qt and use es_CO for the KDE number format
settings as a workaround until the bug is resolved.
--
You are receiving this mail because:
You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 --- Comment #10 from Cesar Garcia --- Created attachment 130494 --> https://bugs.kde.org/attachment.cgi?id=130494&action=edit systemsettings capture that shows dot separator for es_PE locale. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 --- Comment #9 from Cesar Garcia --- Yes, the locale was es_PE.UTF-8, but according to the format settings in systemsettings, es_PE uses dot (.) for the decimal separator so i am not sure which one kde follows. I have a question about the calculator part in krunner? It works like kcalc where the decimal separator is always a dot or it should switch to comma based on LC_NUMERIC? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 --- Comment #6 from Cesar Garcia --- Tried with a Manjaro VM. Updated to the latest version offered: KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 libqalculate: 3.10.0 LC_NUMERIC information: $ locale -kc LC_NUMERIC LC_NUMERIC decimal_point="," thousands_sep="." grouping=3;3 numeric-decimal-point-wc=44 numeric-thousands-sep-wc=46 numeric-codeset="UTF-8" If i try =12.50+25.06 and press enter i get 37,56 on the edit area (and [37;56] on the resulting preview). If i try =12,50+25,06 and press enter i get [12; 75; 6] in both areas. So no matter the decimal separator used i end with a result that cannot be used to continue using arithmetic operations. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424061] wish: preview of list of files have metadata to be written
https://bugs.kde.org/show_bug.cgi?id=424061 --- Comment #2 from Cesar Martins --- Hi Maik, Let me explain my situation here. I'm selecting photos to publish where I need to fill the IPTC title, captions, fix the copyright, fix few tags before. Before committing all this, I would like to review what changes I made and how many pictures will be affected when I click to write all. This will not be a unique situation, probably I will do this frequently. -- Please, help me to understand one situation. Considering the lazy sync. Let's suppose I changed the metadata of 100 files. If I give up to apply theses metadata, I need to click on "Reread metadata from files" right? How do they know which files to reread? Then all changes are discarded, right? -- For better performance and avoid unnecessary I/O reading metadata from files (which is much heavy and slow compared to read a table into the database), should be better to implement a backup/stage table to save all data modified, don't agree? Then you can use this table to manage what was changed and rollback fast. When the user clicks to write all changes, just delete it from the backup table. If they rollback, update the data back and delete it from the staging table. This way you can manage fast what is changed, show it as a report like I'm asking, and improve performance avoid reading metadata from files and writing only when is really necessary. -- About what kind of data to show, I don't think in information like facial, geodata (coordinates), because they aren't readable information. I consider only what into the tab "Caption" and/or basic text fields of EXIF/IPTC/XMP. -- However, I know to implement this isn't trivial, and if isn't acceptable considering the workload and other priorities, that's ok, I understand. -- I see this application as a photo organizer and for that, I'm expecting more efficiency over the usability to make changes. Like the metadata editor, I really consider it very frustrating to use because as a user I need to make a lot of operation (mouse clicks) to change 2 or 3 fields. They should be a screen with a table where you can change fast multiple fields and also should be fast to do in multiple photos. Thanks for your attention! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424061] wish: preview of list of files have metadata to be written
https://bugs.kde.org/show_bug.cgi?id=424061 Cesar Martins changed: What|Removed |Added CC||cesar.inacio.martins@gmail. ||com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 424061] New: wish: preview of list of files have metadata to be written
https://bugs.kde.org/show_bug.cgi?id=424061 Bug ID: 424061 Summary: wish: preview of list of files have metadata to be written Product: digikam Version: 6.4.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Metadata-Maintenance Assignee: digikam-bugs-n...@kde.org Reporter: cesar.inacio.mart...@gmail.com Target Milestone: --- SUMMARY When have the metadata option "use lazy synchronization" active, to flush all changed data to the picture files, we need to click on "Album -> Write metadata to file". However, when we made lot of adjustments, we would like to review what will be written and which files and perhaps undo someone or other picture before the flush. -- My request is when clicking in this option, open a review screen with a table showing the list of files with a text showing the changes and a checkbox, to allow us to uncheck to not write that change at that moment. If double click over the picture name, go to the picture (to allow edit the metadata again if needed). Something like : apply| file | field | before| after -- [x] | c:\images\img_1341.jpg | caption| oaks | oaks trees are common in this region || Title | Tree on the mountain | The biggest Trees || Tags | trees view mountain | tree mountain landscape -- -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 --- Comment #2 from Cesar Garcia --- Tried it again but the bug is still present. KDE Neon: 5.19 KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 The only difference is that the libqalculate version provided by the distro is older than yours. libqalculate14: 2.2.1-0+18.04+bionic+build3 Did you compile libqalculate by yourself or are using a distro where a package for the latest version is provided? I could test again in a VM to check if the problem lies on a old libqalculate version of is still a kde related bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419544] KDE desktop crash when browsing firefox
https://bugs.kde.org/show_bug.cgi?id=419544 Hugo Cesar de Castro Carneiro changed: What|Removed |Added CC||hcesarcas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419544] KDE desktop crash when browsing firefox
https://bugs.kde.org/show_bug.cgi?id=419544 --- Comment #1 from Hugo Cesar de Castro Carneiro --- Created attachment 127780 --> https://bugs.kde.org/attachment.cgi?id=127780&action=edit New crash information added by DrKonqi plasmashell (5.18.4) using Qt 5.14.2 - What I was doing when the application crashed: Just logged into my session. As soon as it opened, Plasma crashed. I tried to use an Openbox/KDE session. Again, as soon as it opened, Plasma crashed. -- Backtrace (Reduced): #6 0x in () #7 0x7f6287171fa7 in () at /usr/lib/libQt5Quick.so.5 #8 0x7f6287172019 in () at /usr/lib/libQt5Quick.so.5 #9 0x7f6287338a93 in () at /usr/lib/libQt5Quick.so.5 #10 0x7f628096947a in () at /usr/lib/libQt5XcbQpa.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414840] plasmashell crashed after clicking on widget
https://bugs.kde.org/show_bug.cgi?id=414840 --- Comment #1 from Hugo Cesar de Castro Carneiro --- Created attachment 124438 --> https://bugs.kde.org/attachment.cgi?id=124438&action=edit New crash information added by DrKonqi plasmashell (5.17.4) using Qt 5.13.2 - What I was doing when the application crashed: I left clicked on Media Player/Spotify widget on System Tray and PlasmaShell crashed. Right clicking it does not crash PlasmaShell. It may be worth informing that there is no icon for this widget. - Unusual behavior I noticed: PlasmaShell crashed. The screen freezes for a little while and then the Panel vanishes. After about one second it reappears and everything comes back to normal. - Custom settings of the application: The Media Player used is the Spotify app. -- Backtrace (Reduced): #6 0x in () #7 0x7faef40c88d7 in () at /usr/lib/libQt5Quick.so.5 #8 0x7faef40c8949 in () at /usr/lib/libQt5Quick.so.5 #9 0x7faef427e2f3 in () at /usr/lib/libQt5Quick.so.5 #10 0x7faeedb3e72a in () at /usr/lib/libQt5XcbQpa.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414840] plasmashell crashed after clicking on widget
https://bugs.kde.org/show_bug.cgi?id=414840 Hugo Cesar de Castro Carneiro changed: What|Removed |Added CC||hcesarcas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412007] Problema ao iniciar o latte-dock
https://bugs.kde.org/show_bug.cgi?id=412007 --- Comment #6 from Julio Cesar --- This command resolved the issue. "latte-dock --cc" Now all that remains is to solve the application center problem. I will open a new ticket for the other issue. Thank you! :) Screenshot: https://ibb.co/LzXxmvV -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412007] Problema ao iniciar o latte-dock
https://bugs.kde.org/show_bug.cgi?id=412007 --- Comment #3 from Julio Cesar --- julio in ~ ❯ latte-dock --v Icon theme "gnome" not found. lattedock 0.9.85 It seems that the application center is also having problems. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 412007] Problema ao iniciar o latte-dock
https://bugs.kde.org/show_bug.cgi?id=412007 --- Comment #2 from Julio Cesar --- julio in ~ ❯ killall latte-dock latte-dock: nenhum processo localizado julio in ~ ❯ latte-dock --default-layout Icon theme "gnome" not found. KCrash: Attempting to start /usr/bin/latte-dock directly KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = latte-dock path = /usr/bin pid = 3811 KCrash: Arguments: /usr/bin/latte-dock --default-layout KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi directly Icon theme "gnome" not found. Icon theme "gnome" not found. "Já existe uma instância em execução, use --replace para reiniciar o Latte" [1] + 3811 suspended (signal) latte-dock --default-layout julio in ~ took 6s ✦ ❯ Error: The system returned an error stating that an instance is already running. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 412007] New: Problema ao iniciar o latte-dock
https://bugs.kde.org/show_bug.cgi?id=412007 Bug ID: 412007 Summary: Problema ao iniciar o latte-dock Product: kde Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jcmljun...@gmail.com Target Milestone: --- Application: latte-dock (0.9.85) Qt Version: 5.12.3 Frameworks Version: 5.62.0 Operating System: Linux 5.0.0-29-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: O pacote "latte-dock" não está inicializando com o sistema. Ao tentar executar manualmente via terminal; o mesmo apresentou erro. The crash can be reproduced every time. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3e2a4c4800 (LWP 1018))] Thread 5 (Thread 0x7f3dfa8ef700 (LWP 1109)): #0 0x7f3e2006d9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55f8d32d4338) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55f8d32d42e8, cond=0x55f8d32d4310) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55f8d32d4310, mutex=0x55f8d32d42e8) at pthread_cond_wait.c:655 #3 0x7f3dfb4d20aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f3dfb4d1dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f3e200676db in start_thread (arg=0x7f3dfa8ef700) at pthread_create.c:463 #6 0x7f3e2329f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f3e08f50700 (LWP 1099)): [KCrash Handler] #5 QQmlPropertyCacheCreator::propertyCacheForObject (this=this@entry=0x7f3e08f4f380, obj=obj@entry=0x7f3dfc3abd78, context=..., error=error@entry=0x7f3e08f4f220) at ../../include/QtQml/5.12.3/QtQml/private/../../../../../src/qml/compiler/qqmlpropertycachecreator_p.h:220 #6 0x7f3e27a73d78 in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7f3e08f4f380, objectIndex=, context=...) at ../../include/QtQml/5.12.3/QtQml/private/../../../../../src/qml/compiler/qqmlpropertycachecreator_p.h:172 #7 0x7f3e27a73f8e in QQmlPropertyCacheCreator::buildMetaObjectRecursively (this=this@entry=0x7f3e08f4f380, objectIndex=objectIndex@entry=0, context=...) at ../../include/QtQml/5.12.3/QtQml/private/../../../../../src/qml/compiler/qqmlpropertycachecreator_p.h:201 #8 0x7f3e27a6f9be in QQmlPropertyCacheCreator::buildMetaObjects (this=0x7f3e08f4f380) at ../../include/QtQml/5.12.3/QtQml/private/../../../../../src/qml/compiler/qqmlpropertycachecreator_p.h:132 #9 QQmlTypeCompiler::compile (this=this@entry=0x7f3e08f4f510) at compiler/qqmltypecompiler.cpp:86 #10 0x7f3e27be569b in QQmlTypeData::compile(QQmlRefPointer const&, QV4::CompiledData::ResolvedTypeReferenceMap*, std::function const&) (this=this@entry=0x55f8d3778bc0, typeNameCache=..., resolvedTypeCache=resolvedTypeCache@entry=0x7f3e08f4f5e8, dependencyHasher=...) at qml/qqmltypeloader.cpp:2651 #11 0x7f3e27bebe92 in QQmlTypeData::done (this=0x55f8d3778bc0) at qml/qqmltypeloader.cpp:2368 #12 0x7f3e27be4d7c in QQmlDataBlob::tryDone (this=0x55f8d3778bc0) at qml/qqmltypeloader.cpp:675 #13 0x7f3e27be65ee in QQmlTypeLoader::setData (this=this@entry=0x55f8d3240600, blob=blob@entry=0x55f8d3778bc0, d=...) at qml/qqmltypeloader.cpp:1312 #14 0x7f3e27be6e5a in QQmlTypeLoader::setData (this=this@entry=0x55f8d3240600, blob=0x55f8d3778bc0, fileName=...) at qml/qqmltypeloader.cpp:1292 #15 0x7f3e27be6ffb in QQmlTypeLoader::loadThread (this=0x55f8d3240600, blob=, blob@entry=0x55f8d3778bc0) at qml/qqmltypeloader.cpp:1162 #16 0x7f3e27be716d in QQmlTypeLoaderThread::loadThread (this=, b=0x55f8d3778bc0) at qml/qqmltypeloader.cpp:905 #17 0x7f3e27c5a474 in QQmlThreadPrivate::threadEvent (this=0x55f8d32dbd30) at qml/ftw/qqmlthread.cpp:197 #18 0x7f3e27c5ab4a in QQmlThreadPrivate::event (this=0x55f8d32dbd30, e=0x55f8d35e2ae0) at qml/ftw/qqmlthread.cpp:135 #19 0x7f3e25fc365c in QApplicationPrivate::notify_helper (this=this@entry=0x55f8d2ee3be0, receiver=receiver@entry=0x55f8d32dbd30, e=e@entry=0x55f8d35e2ae0) at kernel/qapplication.cpp:3736 #20 0x7f3e25fcab90 in QApplication::notify (this=0x7ffe1b187120, receiver=0x55f8d32dbd30, e=0x55f8d35e2ae0) at kernel/qapplication.cpp:3483 #21 0x7f3e2412ed18 in QCoreApplication::notifyInternal2 (receiver=0x55f8d32dbd30, event=0x55f8d35e2ae0) at kernel/qcoreapplication.cpp:1060 #22 0x7f3e2412 in QCoreApplication::sendEvent (receiver=, event=event@entry=0x55f8d35e2ae0) at kernel/qcoreapplication.cpp:1450 #23 0x7f3e241318d7 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55f8d32ece90)
[kwin] [Bug 409864] New: Plasma crashed when returned from Suspend mode
https://bugs.kde.org/show_bug.cgi?id=409864 Bug ID: 409864 Summary: Plasma crashed when returned from Suspend mode Product: kwin Version: 5.16.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: cesar@gmail.com Target Milestone: --- Application: kwin_x11 (5.16.3) Qt Version: 5.12.3 Frameworks Version: 5.60.0 Operating System: Linux 4.18.0-25-generic x86_64 Distribution: KDE neon User Edition 5.16 -- Information about the crash: - What I was doing when the application crashed: I've returned my computer from the suspend mode. The plasma crashed, returned again (was automatic and fast) and is working well. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2e9d401880 (LWP 1615))] Thread 5 (Thread 0x7f2e6592c700 (LWP 2018)): #0 0x7f2e95cd09f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f2e99289fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f2e95cd09f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f2e99289f68, cond=0x7f2e99289f90) at pthread_cond_wait.c:502 #2 0x7f2e95cd09f3 in __pthread_cond_wait (cond=0x7f2e99289f90, mutex=0x7f2e99289f68) at pthread_cond_wait.c:655 #3 0x7f2e98f93844 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f2e98f93889 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f2e95cca6db in start_thread (arg=0x7f2e6592c700) at pthread_create.c:463 #6 0x7f2e9cd6588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f2e7b16a700 (LWP 1818)): #0 0x7f2e9cd58cf6 in __GI_ppoll (fds=0x7f2e68000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f2e9a2acab1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f2e9a2ae1be in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2e9a25203a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2e9a0794ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2e946e8115 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f2e9a07ac72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2e95cca6db in start_thread (arg=0x7f2e7b16a700) at pthread_create.c:463 #8 0x7f2e9cd6588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f2e81d22700 (LWP 1652)): #0 0x7f2e9cd58cf6 in __GI_ppoll (fds=0x7f2e7400e968, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f2e9a2acab1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f2e9a2ae1be in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f2e9a25203a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f2e9a0794ca in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2e93558015 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f2e9a07ac72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f2e95cca6db in start_thread (arg=0x7f2e81d22700) at pthread_create.c:463 #8 0x7f2e9cd6588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f2e841e8700 (LWP 1618)): #0 0x7f2e9cd58bf9 in __GI___poll (fds=0x7f2e841e7c28, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f2e99db6747 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f2e99db836a in xcb_wait_for_event () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f2e85523578 in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f2e9a07ac72 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f2e95cca6db in start_thread (arg=0x7f2e841e8700) at pthread_create.c:463 #6 0x7f2e9cd6588f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f2e9d401880 (LWP 1615)): [KCrash Handler] #6 0x7f2e998016ef in KWin::WindowQuadList::makeInterleavedArrays(unsigned int, KWin::GLVertex2D*, QMatrix4x4 const&) const () at /usr/lib/x86_64-linux-gnu/libkwineffects.so.12 #7 0x7f2e79d1532a in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #8 0x7f2e79d1ca03 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #9 0x7f2e79d1cb37 in () at /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kwin.scenes/KWinSceneOpenGL.so #10 0x7f2e9c8ad416 in KWin::EffectsHandlerIm
[krunner] [Bug 406384] Calculator in Krunner does show any results approximately 60% of the time
https://bugs.kde.org/show_bug.cgi?id=406384 Cesar Garcia changed: What|Removed |Added CC||cesa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 304442] Calculator doesn't work well with locales using comma instead of point.
https://bugs.kde.org/show_bug.cgi?id=304442 Cesar Garcia changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=406388 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 Cesar Garcia changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=304442 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 406388] New: Calculator doesn't work well with locales using point instead of comma.
https://bugs.kde.org/show_bug.cgi?id=406388 Bug ID: 406388 Summary: Calculator doesn't work well with locales using point instead of comma. Product: krunner Version: 5.15.4 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: calculator Assignee: k...@privat.broulik.de Reporter: cesa...@gmail.com Target Milestone: --- SUMMARY This bug is very similar to #304442 but with inverse locale rules. My locale uses point to separate decimals, for example 123.45 but krunner calculator plugin gives the results on the wrong locale (using comma, like 123,45), thus making the result unusable to continue doing calculations. STEPS TO REPRODUCE 1. In krunner enter =12.50+25.06 2. Press 3. OBSERVED RESULT The calculator result shows 37,56 and upon pressing enter the result shows [37;56] (the edit area changes to 37,56). EXPECTED RESULT The calculator result should show 37.56 and upon pressing enter the result dissappears (the edit area should change to 37.56). SOFTWARE/OS VERSIONS KDE Neon: 5.15 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION My locale is es_PE.UTF-8, but any locale that uses dot for decimal separator should work. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404489] New: Kmymoney File protocol died unexpectedly
https://bugs.kde.org/show_bug.cgi?id=404489 Bug ID: 404489 Summary: Kmymoney File protocol died unexpectedly Product: kmymoney Version: 4.8.0 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: file Assignee: kmymoney-de...@kde.org Reporter: cesart...@gmail.com Target Milestone: --- SUMMARY KmyMoney 4.8.0 - Windows 10 64, starts to fail openning and importing .ofx files, the Message is always: " File protocol died unexpectedly" STEPS TO REPRODUCE 1. Just try to import any .ofx .qif or any other file 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: Win-10 64 bits, last update Kmymoney 4.8.0 ADDITIONAL INFORMATION - All the other functions are working normally. Thanks for helping Cesar -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399555] New: Discover crashes when access the "Installed" menu.
https://bugs.kde.org/show_bug.cgi?id=399555 Bug ID: 399555 Summary: Discover crashes when access the "Installed" menu. Product: Discover Version: 5.14.0 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: ce...@acearuja.com.br Target Milestone: --- Application: plasma-discover (5.14.0) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-36-generic x86_64 Distribution: KDE neon User Edition 5.14 -- Information about the crash: - What I was doing when the application crashed: I just clicked the button "Installed". The windows crashed. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa6ed647c80 (LWP 6001))] Thread 12 (Thread 0x7fa69d44a700 (LWP 6054)): #0 0x7fa6e8bc7bf9 in __GI___poll (fds=0x7fa6900018a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa6e3137439 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6e313754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6e9502a9b in QEventDispatcherGlib::processEvents (this=0x7fa69b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa6e94a6dea in QEventLoop::exec (this=this@entry=0x7fa69d449da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fa6e92d1b8a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fa6e92dcaab in QThreadPrivate::start (arg=0x7fa6c806f6f0) at thread/qthread_unix.cpp:367 #7 0x7fa6e52d26db in start_thread (arg=0x7fa69d44a700) at pthread_create.c:463 #8 0x7fa6e8bd488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 11 (Thread 0x7fa69e2b4700 (LWP 6051)): #0 0x7fa6e317cd79 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa6e3136805 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6e313736b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6e313754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa6e9502a9b in QEventDispatcherGlib::processEvents (this=0x7fa68c00a220, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fa6e94a6dea in QEventLoop::exec (this=this@entry=0x7fa69e2b3da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7fa6e92d1b8a in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7fa6e92dcaab in QThreadPrivate::start (arg=0x7fa6b8010b50) at thread/qthread_unix.cpp:367 #8 0x7fa6e52d26db in start_thread (arg=0x7fa69e2b4700) at pthread_create.c:463 #9 0x7fa6e8bd488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7fa69eab5700 (LWP 6016)): #0 0x7fa6e317cd94 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa6e31373f6 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6e313754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6e9502a9b in QEventDispatcherGlib::processEvents (this=0x7fa694000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7fa6e94a6dea in QEventLoop::exec (this=this@entry=0x7fa69eab4da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #5 0x7fa6e92d1b8a in QThread::exec (this=) at thread/qthread.cpp:525 #6 0x7fa6e92dcaab in QThreadPrivate::start (arg=0x558abf9676b0) at thread/qthread_unix.cpp:367 #7 0x7fa6e52d26db in start_thread (arg=0x7fa69eab5700) at pthread_create.c:463 #8 0x7fa6e8bd488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7fa6ad9a9700 (LWP 6011)): #0 0x7fa6e317b9f3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fa6e3136f27 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa6e31373e0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa6e313754c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fa6e9502a9b in QEventDispatcherGlib::processEvents (this=0x7fa6a4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7fa6e94a6dea in QEventLoop::exec (this=this@entry=0x7fa6ad9a8da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214 #6 0x7fa6e92d1b8a in QThread::exec (this=) at thread/qthread.cpp:525 #7 0x7fa6e92dcaab in QThreadPrivate::start (arg=0x558abe84e3c0) at thread/qthread_unix.cpp:367 #8 0x7fa6e52d26db in start_thread (arg=0x7fa6ad9a9700) at pthread_create.c:463 #9 0x7fa6e8bd488f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7fa6af149700 (LWP
[kdialog] [Bug 382437] Regression in kdialog causes wrong file extension
https://bugs.kde.org/show_bug.cgi?id=382437 Cesar Garcia changed: What|Removed |Added CC||cesa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367738] add to favorites "Display Config - KDE Control Module" unable to run.
https://bugs.kde.org/show_bug.cgi?id=367738 --- Comment #4 from Cesar Jimenez --- (In reply to Cesar Jimenez from comment #2) > Created attachment 100746 [details] > Screenshot_20160824_215241.png > > screen grab attached. > Plasma 5.5.5 César O. Jiménez > > From: David Edmundson via KDE Bugzilla > To: cesa...@yahoo.com > Sent: Wednesday, August 24, 2016 9:43 PM > Subject: [plasmashell] [Bug 367738] add to favorites "Display Config - KDE > Control Module" unable to run. > > https://bugs.kde.org/show_bug.cgi?id=367738 > > David Edmundson changed: > > What |Removed |Added > > CC| |k...@davidedmundson.co.uk > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from David Edmundson --- > Works here, can you confirm your plasma version? Reproduced with a new LIVE USB of kubuntu-16.04.1-desktop-amd64.iso download from Kubuntu webpage. Same version of Plasma version 5.5.5 and same error. Error reproduced from OEM image, no new apps installed, no changes to OS, just boot to LIVE and reproduced steps and got same error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367738] add to favorites "Display Config - KDE Control Module" unable to run.
https://bugs.kde.org/show_bug.cgi?id=367738 --- Comment #3 from Cesar Jimenez --- (In reply to Cesar Jimenez from comment #0) > Right click to "add to favorites" the Display Configuration - KDE Control > Module from menu creates the favorite icon. > Properties of this icon, kcm_kscreen.desktop, are general:kcm_kscreen. > Attempt to execute results in: > Error-Plasma > "Unable to run the command specified. The file or folder kcm_kscreen.desktop > does not exist." > Help icon for Display Configuration is grey out. > > Display Configuration does launch correctly, just not from favorites or "add > to desktop" > > 1. Click K menu, type "display", right click "Display Configuration" and > select "add to favorites" > 2. from K menu launch favorite "Display Configuration" > 3. Error - Plasma > > > Reproducible: Always > > Steps to Reproduce: > 1. Click K menu, type "display", right click "Display Configuration" and > select "add to favorites" > 2. from K menu launch favorites "Display Configuration" > 3. Error - Plasma > > Actual Results: > error - plasma, not launched > > Expected Results: > open display configuration from settings > > errors also if I create a shortcut on desktop from the favorites icon. > Unable to run the command specified. The file or folder > /usr/share/plasma/plasmoids/org.kde.plasma.icon/contents/ui/kcm_kscreen. > desktop does not exist. > > If I minimize this error it won't maximize by selecting it from the task > bar. Must ALT-TAB to maximize to error. No action can be done until error is > cleared. Reproduced with a new LIVE USB of kubuntu-16.04.1-desktop-amd64.iso download from Kubuntu webpage. Same version of Plasma version 5.5.5 and same error. Error reproduced from OEM image, no new apps installed, no changes to OS, just boot to LIVE and reproduced steps and got same error. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367738] add to favorites "Display Config - KDE Control Module" unable to run.
https://bugs.kde.org/show_bug.cgi?id=367738 --- Comment #2 from Cesar Jimenez --- screen grab attached. Plasma 5.5.5 César O. Jiménez From: David Edmundson via KDE Bugzilla To: cesa...@yahoo.com Sent: Wednesday, August 24, 2016 9:43 PM Subject: [plasmashell] [Bug 367738] add to favorites "Display Config - KDE Control Module" unable to run. https://bugs.kde.org/show_bug.cgi?id=367738 David Edmundson changed: What |Removed |Added CC| |k...@davidedmundson.co.uk Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- Works here, can you confirm your plasma version? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367738] New: add to favorites "Display Config - KDE Control Module" unable to run.
https://bugs.kde.org/show_bug.cgi?id=367738 Bug ID: 367738 Summary: add to favorites "Display Config - KDE Control Module" unable to run. Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: cesa...@yahoo.com CC: plasma-b...@kde.org Right click to "add to favorites" the Display Configuration - KDE Control Module from menu creates the favorite icon. Properties of this icon, kcm_kscreen.desktop, are general:kcm_kscreen. Attempt to execute results in: Error-Plasma "Unable to run the command specified. The file or folder kcm_kscreen.desktop does not exist." Help icon for Display Configuration is grey out. Display Configuration does launch correctly, just not from favorites or "add to desktop" 1. Click K menu, type "display", right click "Display Configuration" and select "add to favorites" 2. from K menu launch favorite "Display Configuration" 3. Error - Plasma Reproducible: Always Steps to Reproduce: 1. Click K menu, type "display", right click "Display Configuration" and select "add to favorites" 2. from K menu launch favorites "Display Configuration" 3. Error - Plasma Actual Results: error - plasma, not launched Expected Results: open display configuration from settings errors also if I create a shortcut on desktop from the favorites icon. Unable to run the command specified. The file or folder /usr/share/plasma/plasmoids/org.kde.plasma.icon/contents/ui/kcm_kscreen.desktop does not exist. If I minimize this error it won't maximize by selecting it from the task bar. Must ALT-TAB to maximize to error. No action can be done until error is cleared. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365583] New: Cierre inerperado de KDE
https://bugs.kde.org/show_bug.cgi?id=365583 Bug ID: 365583 Summary: Cierre inerperado de KDE Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: camte...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.26-21-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Algunas veces cuando me intento conectar a una red VPN o modificar los elementos graficos de la barra principal me sale el error hoy en el dia ya van mas de tres veces que parece, espero me puedan ayudar, Gracias. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe73fbe87c0 (LWP 11851))] Thread 16 (Thread 0x7fe72963e700 (LWP 11853)): #0 0x7fe7390dfbfd in poll () from /lib64/libc.so.6 #1 0x7fe73e033422 in ?? () from /usr/lib64/libxcb.so.1 #2 0x7fe73e03500f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x7fe72b78f3c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fe7397da32f in QThreadPrivate::start (arg=0x217f250) at thread/qthread_unix.cpp:331 #5 0x7fe7388e90a4 in start_thread () from /lib64/libpthread.so.0 #6 0x7fe7390e802d in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7fe72293b700 (LWP 11854)): #0 0x7fe7390dfbfd in poll () from /lib64/libc.so.6 #1 0x7fe7357bce64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe7357bcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe739a0cd8b in QEventDispatcherGlib::processEvents (this=0x7fe71c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fe7399b3d53 in QEventLoop::exec (this=this@entry=0x7fe72293adf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fe7397d561a in QThread::exec (this=this@entry=0x2251fb0) at thread/qthread.cpp:503 #6 0x7fe73cae9e18 in QQmlThreadPrivate::run (this=0x2251fb0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7fe7397da32f in QThreadPrivate::start (arg=0x2251fb0) at thread/qthread_unix.cpp:331 #8 0x7fe7388e90a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe7390e802d in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7fe715606700 (LWP 11870)): #0 0x7fe7390dfbfd in poll () from /lib64/libc.so.6 #1 0x7fe7357bce64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe7357bcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe739a0cd8b in QEventDispatcherGlib::processEvents (this=0x7fe718c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fe7399b3d53 in QEventLoop::exec (this=this@entry=0x7fe715605df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fe7397d561a in QThread::exec (this=this@entry=0x26291c0) at thread/qthread.cpp:503 #6 0x7fe73cae9e18 in QQmlThreadPrivate::run (this=0x26291c0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7fe7397da32f in QThreadPrivate::start (arg=0x26291c0) at thread/qthread_unix.cpp:331 #8 0x7fe7388e90a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe7390e802d in clone () from /lib64/libc.so.6 Thread 13 (Thread 0x7fe70fc87700 (LWP 11871)): #0 0x7fe7390dfbfd in poll () from /lib64/libc.so.6 #1 0x7fe7357bce64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe7357bcf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe739a0cd8b in QEventDispatcherGlib::processEvents (this=0x7fe7080008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7fe7399b3d53 in QEventLoop::exec (this=this@entry=0x7fe70fc86df0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fe7397d561a in QThread::exec (this=this@entry=0x26c0970) at thread/qthread.cpp:503 #6 0x7fe73cae9e18 in QQmlThreadPrivate::run (this=0x26c0970) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x7fe7397da32f in QThreadPrivate::start (arg=0x26c0970) at thread/qthread_unix.cpp:331 #8 0x7fe7388e90a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe7390e802d in clone () from /lib64/libc.so.6 Thread 12 (Thread 0x7fe70e3ee700 (LWP 11872)): #0 0x7fe7388ed03f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe73f2b886b in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fe73f2b8899 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fe7388e90a4 in start_thread () from /lib64/libpthread.so.0 #4 0x
[dolphin] [Bug 361765] New: Dolphin sudden close
https://bugs.kde.org/show_bug.cgi?id=361765 Bug ID: 361765 Summary: Dolphin sudden close Product: dolphin Version: 15.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ce...@acearuja.com.br Application: dolphin (15.12.3) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: It always happens when I copy a file from my home directory to a NTFS partition of the same HD. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe1e05e67c0 (LWP 3317))] Thread 3 (Thread 0x7fe1c3b81700 (LWP 3319)): #0 0x7fe1dfe89bbd in poll () from /lib64/libc.so.6 #1 0x7fe1d4edbe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe1d4edbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe1da1983fb in QEventDispatcherGlib::processEvents (this=0x7fe1bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #4 0x7fe1da14604b in QEventLoop::exec (this=this@entry=0x7fe1c3b80de0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7fe1d9f825da in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7fe1da5ac095 in ?? () from /usr/lib64/libQt5DBus.so.5 #7 0x7fe1d9f87079 in QThreadPrivate::start (arg=0x7fe1da814d00) at thread/qthread_unix.cpp:340 #8 0x7fe1d5a610a4 in start_thread () from /lib64/libpthread.so.0 #9 0x7fe1dfe91fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe1b8c52700 (LWP 3320)): #0 QMutex::unlock (this=this@entry=0x1b32718) at thread/qmutex.cpp:271 #1 0x7fe1da198335 in unlock (this=) at ../../src/corelib/thread/qmutex.h:138 #2 ~QMutexLocker (this=, __in_chrg=) at ../../src/corelib/thread/qmutex.h:132 #3 canWaitLocked (this=0x1b326f0) at ../../src/corelib/thread/qthread_p.h:248 #4 postEventSourcePrepare (s=0x7fe1b40012d0, timeout=0x7fe1b8c51c54) at kernel/qeventdispatcher_glib.cpp:253 #5 0x7fe1d4edb4ad in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #6 0x7fe1d4edbd80 in ?? () from /usr/lib64/libglib-2.0.so.0 #7 0x7fe1d4edbf7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #8 0x7fe1da1983fb in QEventDispatcherGlib::processEvents (this=0x7fe1b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #9 0x7fe1da14604b in QEventLoop::exec (this=this@entry=0x7fe1b8c51e10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #10 0x7fe1d9f825da in QThread::exec (this=) at thread/qthread.cpp:503 #11 0x7fe1d9f87079 in QThreadPrivate::start (arg=0x1b325b0) at thread/qthread_unix.cpp:340 #12 0x7fe1d5a610a4 in start_thread () from /lib64/libpthread.so.0 #13 0x7fe1dfe91fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe1e05e67c0 (LWP 3317)): [KCrash Handler] #6 QObjectPrivate::setParent_helper (this=0x1, o=o@entry=0x0) at kernel/qobject.cpp:1973 #7 0x7fe1da17a3b9 in QObject::setParent (this=, parent=parent@entry=0x0) at kernel/qobject.cpp:1950 #8 0x7fe1dbeffc6f in KCompositeJob::removeSubjob (this=, job=0x2401260) at /usr/src/debug/kcoreaddons-5.21.0/src/lib/jobs/kcompositejob.cpp:71 #9 0x7fe1ddf5c615 in KIO::CopyJobPrivate::slotResultErrorCopyingFiles (this=this@entry=0x25a52e0, job=job@entry=0x2401260) at /usr/src/debug/kio-5.21.0/src/core/copyjob.cpp:1412 #10 0x7fe1ddf5d2a2 in KIO::CopyJobPrivate::slotResultCopyingFiles (this=0x25a52e0, job=0x2401260) at /usr/src/debug/kio-5.21.0/src/core/copyjob.cpp:1280 #11 0x7fe1da171c41 in QMetaObject::activate (sender=sender@entry=0x2401260, signalOffset=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff864ff720) at kernel/qobject.cpp:3730 #12 0x7fe1da1727a7 in QMetaObject::activate (sender=sender@entry=0x2401260, m=m@entry=0x7fe1dc1520c0 , local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7fff864ff720) at kernel/qobject.cpp:3595 #13 0x7fe1dbf00642 in KJob::result (this=this@entry=0x2401260, _t1=_t1@entry=0x2401260) at /usr/src/debug/kcoreaddons-5.21.0/build/src/lib/moc_kjob.cpp:568 #14 0x7fe1dbf0136f in KJob::finishJob (this=this@entry=0x2401260, emitResult=emitResult@entry=true) at /usr/src/debug/kcoreaddons-5.21.0/src/lib/jobs/kjob.cpp:109 #15 0x7fe1dbf013da in KJob::emitResult (this=this@entry=0x2401260) at /usr/src/debug/kcoreaddons-5.21.0/src/lib/jobs/kjob.cpp:293 #16 0x7fe1ddf90a8c in KIO::FileCopyJob::slotResult (this=0x2401260, job=0x21274d0) at /usr/src/debug/kio-5.21.0/src/core/filecopyjob.cpp:563 #17 0x7fe1ddf91e10 in KIO::F
[frameworks-kio] [Bug 353195] Copy error for folders with mixed files & folders in Split View
https://bugs.kde.org/show_bug.cgi?id=353195 --- Comment #7 from Cesar Garcia --- I can reproduce the bug everytime with both sftp and smb connections in one of the panes. This is what i do: * Open split view * Open a network connection in one of the panes, for example a smb shared folder or just sftp://localhost/some_folder * Create a new folder in the local view using any name. * Create a file (or use an existing one) and move/copy it to the newly created folder. * Drag the folder to the smb/sftp pane and choose copy/move. Basically the trigger is to copy/move a file to a folder in one pane before moving that folder to the other pane. -- You are receiving this mail because: You are watching all bug changes.
