[plasma-pa] [Bug 485787] New: No output or input devices/applications found
https://bugs.kde.org/show_bug.cgi?id=485787 Bug ID: 485787 Summary: No output or input devices/applications found Classification: Plasma Product: plasma-pa Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: plasma-b...@kde.org Reporter: alterme...@gmail.com CC: isma...@gmail.com, m...@ratijas.tk Target Milestone: --- Created attachment 168671 --> https://bugs.kde.org/attachment.cgi?id=168671=edit Screenshot that demonstrates the issue SUMMARY The plasma-pa plasmoid reports "No output or input devices found" on the "Devices" tab and "No applications playing or recording audio" on the "Applications" tab. I actually have audio devices (e.g. headphones) and audio applications running (e.g. YouTube on Firefox) and they work correctly. They are also recognized in the "Sound" section of systemsettings. STEPS TO REPRODUCE 1. Connect audio devices 2. Play some audio (notice how the audio plays correctly) 3. Open the plasma-pa applet OBSERVED RESULT No devices or applications are found, which results in not being able to set the volume for anything, or move an application to a different audio device, unless you click on the configuration icon which leads to the systemsettings page. EXPECTED RESULT You should see running audio applications and existing audio devices and be able to configure volume and bind applications to audio devices. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.4 on X11 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I'm using PipeWire, not PulseAudio. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449706] Keypad decimal separator should respect regional formatting
https://bugs.kde.org/show_bug.cgi?id=449706 --- Comment #5 from Mattia --- Tested today with: Operating System: Fedora Linux 40 KDE Plasma Version: 5.93.0 KDE Frameworks Version: 5.249.0 Qt Version: 6.6.1 Kernel Version: 6.8.0-0.rc0.20240112git70d201a40823.5.fc40.x86_64 (64-bit) Still not working as expected. Looking at the keyboard mapping graphical preview (System Settings -> Input Devices -> Keyboard -> Mappings) the keypad button is mapped as ". / KP Delete", but I suppose it should be mapped as "KP Decimal / KP Delete" to respect regional settings? -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 478689] New: C++ Semantic analysis gets confused by class inheritance
https://bugs.kde.org/show_bug.cgi?id=478689 Bug ID: 478689 Summary: C++ Semantic analysis gets confused by class inheritance Classification: Applications Product: kdevelop Version: 5.12.230801 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- Created attachment 164276 --> https://bugs.kde.org/attachment.cgi?id=164276=edit Screenshot showing kdevelop properly detects base classes but still marks them as an error SUMMARY It seems KDevelop starts giving type errors for conversions between a pointer to a derived class to its base class / ancestors. It correctly finds the methods and highlights them / give the correct info on hover but marks it as an error. This happens both with function calls and access to members declared in base classes using `->`. It seems to be caused by multiple inheritance because commenting out one of the base classes seems to fix the issue. The same codebase worked fine a couple kdevelop versions ago. STEPS TO REPRODUCE 1. For me it happens for this class: https://invent.kde.org/graphics/glaxnimate/-/blob/master/src/gui/widgets/dialogs/glaxnimate_window.hpp#L40 2. Open the project mentioned above with kdevelop 3. Open https://invent.kde.org/graphics/glaxnimate/-/blob/master/src/gui/widgets/dialogs/gw_impl_ui.cpp OBSERVED RESULT Bunch of correct code marked as an error EXPECTED RESULT It shouldn't mark it SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-14-generic (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon RX 470 Graphics Manufacturer: NOVATECH LTD Product Name: PC-X006665 System Version: V1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478102] New: Digital clock doesn't follow time locale settings
https://bugs.kde.org/show_bug.cgi?id=478102 Bug ID: 478102 Summary: Digital clock doesn't follow time locale settings Classification: Plasma Product: plasmashell Version: 5.27.8 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: 1.0 Created attachment 163895 --> https://bugs.kde.org/attachment.cgi?id=163895=edit Screnshots showing settings and the digital clock SUMMARY Digital clock doesn't follow the system wide time format. The same issue was marked as fixed in 5.27.4 but for me it happens in 5.27.8 https://bugs.kde.org/show_bug.cgi?id=395048 (My goal was to set it to 24 hours with a leading 0 -- ie: 09:45 instead of 9:45 or 9:45 AM) STEPS TO REPRODUCE 1. Set a time format on settings to something other than en_US (easiest way to see the bug is a 24 hour locale) 2. Add a digital clock 3. Set the digital clock to Use Region Defaults 4. Restart Plasmashell in case the locale needs to be loaded OBSERVED RESULT It ignores the locale completely, it ignores leading 0s and even 12/24 hours settings EXPECTED RESULT It should format the time the same as it's displayed in System Settings > Region & Language > Time I attached a screenshot showing the applet settings, locale settings, and applet SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-13-generic (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon RX 470 Graphics Manufacturer: NOVATECH LTD Product Name: PC-X006665 System Version: V1.0 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474710] New: Dolphin crashes when reloading a directory that no longer exists
https://bugs.kde.org/show_bug.cgi?id=474710 Bug ID: 474710 Summary: Dolphin crashes when reloading a directory that no longer exists Classification: Applications Product: dolphin Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: alterme...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.3-arch1-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: Basically the title. In particular, I had a directory of an external USB device open, then I unmounted the device keeping Dophin open, went back to Dolphin, hit F5 and it crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f7513f44e21 in () at /usr/lib/libKF5KIOCore.so.5 #5 0x7f7513f4358d in () at /usr/lib/libKF5KIOCore.so.5 #6 0x7f75122c4174 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #7 0x7f7512f7893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #8 0x7f751229c6f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7f75122a165b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5 #10 0x7f75122e76d8 in () at /usr/lib/libQt5Core.so.5 #11 0x7f750ff0df19 in () at /usr/lib/libglib-2.0.so.0 #12 0x7f750ff6c2b7 in () at /usr/lib/libglib-2.0.so.0 #13 0x7f750ff0c112 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #14 0x7f75122eb51c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #15 0x7f751229b404 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7f751229c8a3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #17 0x55f146b5bdb8 in () #18 0x7f7511827cd0 in () at /usr/lib/libc.so.6 #19 0x7f7511827d8a in __libc_start_main () at /usr/lib/libc.so.6 #20 0x55f146b5c575 in () [Inferior 1 (process 25976) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449706] Keypad decimal separator should respect regional formatting
https://bugs.kde.org/show_bug.cgi?id=449706 --- Comment #3 from Mattia --- (In reply to Vlad Zahorodnii from comment #2) > Can you check whether running app through xwayland makes a difference? a qt > application can be forced to run through xwayland by passing -platform xcb > argument, e.g. `kate -platform xcb` Thanks, yes, forcing xwayland make it work as expected. I tried with `kmymoney -platform xcb` and also a GTK app with `env WAYLAND_DISPLAY= libreoffice`. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449706] Keypad decimal separator should respect regional formatting
https://bugs.kde.org/show_bug.cgi?id=449706 --- Comment #1 from Mattia --- keypad dot is always inserted as dot (not as decimal separator) when running KDE under Wayland, works fine under X11 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427147] Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 --- Comment #10 from Mattia Basaglia --- (In reply to Sven Brauch from comment #8) > @Mattia Basaglia Sorry for not replying any more after you posted the > backtrace, I overlooked it. The libclang you had the issue with is 5 > versions old, if you are still using KDevelop, does it still happen with the > current libclang? I have had some crashes recently but didn't get a backtrace for them. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 464399] New: QString::indexOf(): partitionmanager killed by SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=464399 Bug ID: 464399 Summary: QString::indexOf(): partitionmanager killed by SIGSEGV Classification: Applications Product: partitionmanager Version: 22.12.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- A SIGSEV has been reported by a Fedora user, the full backtrace is available at https://bugzilla.redhat.com/show_bug.cgi?id=2161264 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 463193] New: RFE: copy - paste template with inline editing
https://bugs.kde.org/show_bug.cgi?id=463193 Bug ID: 463193 Summary: RFE: copy - paste template with inline editing Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: 1.0 Having to copy/paste configuration commands with different settings, one needs to edit the text to be copied before pasting it, or just copy the fixed text and manually add the changing parts. It would be nice to have a way to define a template text, like: `ip addr add <192.168.1.1::ADDRESS> dev ` and then, upon pasting, klipper stops entering text when it detect the templating and shows some popups asking for 'ADDRESS' (with a default pre-filled value of 192.168.1.1) and for 'IFNAME'. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 383418] Saving diff produces empty file
https://bugs.kde.org/show_bug.cgi?id=383418 Mattia changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- Version|4.1.3 |4.1.22082 --- Comment #8 from Mattia --- Hello, yes I can still reproduce in 4.1.22082 Comparing two simple text files in user home directory, UI shows differences, choosing "File -> save comparison" (roughly translated from Italian) if I fill "run comparison in" field (with the same user home directory or another parent dir), the produced output file is empty. The output is fine if I leave that field empty. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429132] Crash when using the quick open box
https://bugs.kde.org/show_bug.cgi?id=429132 Mattia Basaglia changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED Version|5.5.0 |5.7.211203 --- Comment #3 from Mattia Basaglia --- (In reply to Justin Zobel from comment #2) > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? Yeah it happened again not long ago with 5.7.211203, it doesn't happen often but once it does it might crash a couple times in a row -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 339962] Once installed on Windows 8.1 as admin it can't be run as normal user
https://bugs.kde.org/show_bug.cgi?id=339962 --- Comment #3 from Mattia Rossi --- Wow, this bug is so old that I simply can't reproduce it because I don't have a single windows machine anymore since 5 years... So, feel free to close it if no one else ever reported it. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458155] Hovered unfocused items in lists aren't colored correctly
https://bugs.kde.org/show_bug.cgi?id=458155 Mattia changed: What|Removed |Added Platform|unspecified |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 458155] New: Hovered unfocused items in lists aren't colored correctly
https://bugs.kde.org/show_bug.cgi?id=458155 Bug ID: 458155 Summary: Hovered unfocused items in lists aren't colored correctly Product: Breeze Version: 5.25.4 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: gtk theme Assignee: plasma-b...@kde.org Reporter: alterme...@gmail.com CC: agrine...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 151491 --> https://bugs.kde.org/attachment.cgi?id=151491=edit Current behavior followed by expected behavior followed by Qt equivalent (KDE system settings) SUMMARY When you hover over an item of a GTK list (for example a GtkListBox or a GtkStackSidebar) the background color of such item becomes #3daee9 (in the default breeze dark), which is the same color as the selected items in the list. These colors should actually be different. STEPS TO REPRODUCE 1. Open an application that contains a list (e.g. the sidebar on the GTK file picker), or quickly create a layout in Glade 2. Select an item in the list 3. Hover over a different item OBSERVED RESULT The two items have identical background colors (#3daee9 in the default breeze dark). EXPECTED RESULT The selected item has the correct color, however the hovered one should be different (e.g. #1f485e on the default breeze dark). SOFTWARE/OS VERSIONS GTK Version: 3; might also happen on 2 and 4 but I can't test them OS: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I managed to fix it for Breeze Dark by modifying gtk.css in the "Lists" section: sed -i '2336s/theme_selected_bg_color_breeze/theme_unfocused_selected_bg_color_breeze/' gtk.css -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 443004] gdb keeps crashing on kdevelop
https://bugs.kde.org/show_bug.cgi?id=443004 --- Comment #1 from Mattia Basaglia --- This still happens as of version 5.7.211203 -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 452703] New: klipper not listed in the products list
https://bugs.kde.org/show_bug.cgi?id=452703 Bug ID: 452703 Summary: klipper not listed in the products list Product: bugs.kde.org Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: product/component changes Assignee: sysad...@kde.org Reporter: mattia.ve...@tiscali.it CC: christo...@krop.fr Target Milestone: --- I'd like to file a RFE against klipper, but when I try to enter a new bug klipper is not listed in the products list. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 450132] RFE: pipe terminal output to file in parallel
https://bugs.kde.org/show_bug.cgi?id=450132 --- Comment #3 from Mattia --- (In reply to ninjalj from comment #1) > Why not just use script(1) > (https://man7.org/linux/man-pages/man1/script.1.html) ? I wasn't aware of script. Anyway, it does the work but I get bad characters in output: ``` Script started on 2022-02-13 13:08:26+01:00 [TERM="xterm-256color" TTY="/dev/pts/3" COLUMNS="92" LINES="33"] ]0;mattia@Hamal:~/Devel/fed-users[?2004h[mattia@Hamal fed-users]$ exit [?2004l exit Script done on 2022-02-13 13:08:46+01:00 [COMMAND_EXIT_CODE="0"] ``` I suppose it should be tweaked in some way, but I'd like something more user friendly and easier for a user to discover rather than searching through linux scripts. Also, by default it doesn't flush the output in real time (I had to search through the options to find the '-f' flag). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 450132] New: RFE: pipe terminal output to file in parallel
https://bugs.kde.org/show_bug.cgi?id=450132 Bug ID: 450132 Summary: RFE: pipe terminal output to file in parallel Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- SUMMARY I'd like to request the feature to pipe the terminal output in parallel to a file. This is different than the "File -> Save Output As" option: the current behavior is that one can save the history already showed in the terminal. But if one have a very long history to save it may miss the tsart if the scrollback lines parameter isn't set enough high in the profile; or one could set it to unlimited, hoping to not bog the RAM. My request is to pipe the output (all output showed, including using input) to a file while it's being outputted to the terminal. So, the scrollback history doesn't need to be modified, but even if the output is longer than the history it will be available in the file. Like a "start logging to file" and "stop logging to file" button. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449706] New: Keypad decimal separator should respect regional formatting
https://bugs.kde.org/show_bug.cgi?id=449706 Bug ID: 449706 Summary: Keypad decimal separator should respect regional formatting Product: systemsettings Version: 5.23.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: mattia.ve...@tiscali.it CC: butir...@gmail.com Target Milestone: --- SUMMARY I'm using Italian regional format in KDE settings, but despite of that the keypad decimal separator always inserts a '.' (dot) instead of a ',' (comma). STEPS TO REPRODUCE 1. open system settings, regional settings, format and set Italy 2. open system settings, input devices, keyboard 3. focus the test area field and push the Del/. button on keypad (while Num Lock is on) OBSERVED RESULT A '.' (dot) is entered. EXPECTED RESULT Italian regional settings use ',' (comma as decimal separator, so pressing the Del/. key on the keypad should enter a ',' (comma) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Fedora Linux 35 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.5-200.fc35.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 27.3 GiB of RAM Graphics Processor: AMD RENOIR ADDITIONAL INFORMATION I've also tried in the keyboard advanced settings to enable keyboard option "Del behavior" to '4th level with abstract separator', but it doesn't work (nothing is inserted in test area with that option enabled) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447574] Conflict between packages in latest updateitems
https://bugs.kde.org/show_bug.cgi?id=447574 --- Comment #2 from Mattia --- You can try to run 'sudo dnf copr enable zawertun/kde && sudo dnf upgrade --refresh --skip-broken' to temporarily bypass the broken steam upgrade. Or just disable the repository which provides steam appending '--disablerepo='. Or disable steam repository forever with 'dnf disable '. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 447574] Conflict between packages in latest updateitems
https://bugs.kde.org/show_bug.cgi?id=447574 Mattia changed: What|Removed |Added CC||mattia.ve...@tiscali.it --- Comment #1 from Mattia --- This has nothing to do with Discover. That message simply says that both steam-1.0.0.73-7.fc35.i686 and steam-devices-1.0.0.74-1.fc35.i686 are providing the same file, so the conflict. Whatever repository is providing the steam upgrade either is only providing steam-devices 1.0.0.74 without steam 1.0.0.74 or the steam upgrade is broken. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 447416] New: Unable to use mariadb 10 remote database with digikam 7.3
https://bugs.kde.org/show_bug.cgi?id=447416 Bug ID: 447416 Summary: Unable to use mariadb 10 remote database with digikam 7.3 Product: digikam Version: 7.3.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- I had a working digikam 7.2 installation (from Fedora Linux 35 RPMs) with a remote MariaDB 5.x database on a Qnap NAS. Things still worked after I migrated the database to MariaDB 10.x on the same NAS. After the upgrade to digikam 7.3 (always Fedora Linux RPMs) at startup I got: digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 12 digikam.coredb: Core database: makeUpdates 12 to 13 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "Column count of mysql.proc is wrong. Expected 21, found 20. Created with MariaDB 50544, now running 100508. Please use mariadb-upgrade to fix this error" "1558" 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV12ToV13" ] Statement [ "\nDROP PROCEDURE IF EXISTS create_index_if_not_exists;\n" ] digikam.coredb: Core database: schema update to V 13 failed! digikam.coredb: Core database: cannot process schema initialization I made several attempts to export/import the database and to drop the db and let digikam 7.3 recreate it, but it always fails. So, I started from scratch: downgraded Digikam to 7.2, start Digikam from clean and let it create a local SQLite database. After that I've upgraded Digikam to 7.3, started with the local SQLite database and tried to run the migration tool to the newly created MariaDB on NAS, but I get: digikam.coredb: Core database: running schema update digikam.coredb: Core database: no database file available digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: Unable to execute query" "You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)" "1419" 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "CreateTriggers" ] Statement [ "CREATE TRIGGER insert_tagstree AFTER INSERT ON Tags FOR EACH ROW\n INSERT INTO TagsTree SELECT NEW.id, NEW.pid\n UNION SELECT NEW.id, pid FROM TagsTree WHERE id = NEW.pid;\n" ] Downgrading Digikam to 7.2 and running the migration tool succeeds, but then I return to the initial "schema update failed" error... Version of components: digikam-7.2.0-5.fc35 digikam-7.3.0-4.fc35 MariaDB 10.5.8 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 446423] Autocomplete doesn't highlight the correct item
https://bugs.kde.org/show_bug.cgi?id=446423 --- Comment #3 from Mattia Basaglia --- I'm not sure exactly, I use my distro package for kdevelop. I noticed the issue since I upgraded to Ubuntu 21.10 The package list shows the same version as in Ubuntu 20.04: https://packages.ubuntu.com/search?keywords=kdevelop but it was definitely working fine before I upgraded -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 446423] New: Autocomplete doesn't highlight the correct item
https://bugs.kde.org/show_bug.cgi?id=446423 Bug ID: 446423 Summary: Autocomplete doesn't highlight the correct item Product: kdevelop Version: 5.6.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Code completion Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- Created attachment 144171 --> https://bugs.kde.org/attachment.cgi?id=144171=edit Screen grab of the bug SUMMARY I think this is a regression because it was working fine on older version. Now it seems autocomplete most of the time highlights the first entry in the completion menu, whether it has anything to do with what you are typing or not STEPS TO REPRODUCE 1. Have enough code that you can have autocompletion 2. start typing OBSERVED RESULT The completion suggestion is the first in alphabetical order. Sometimes it shows the right completion for a fraction of a second but then switches to the wrong one EXPECTED RESULT it should suggest based on what you typed so far SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-22-generic (64-bit) Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics ADDITIONAL INFORMATION I attached a video showing the issue -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 444811] New: Missing libreswan connection editor
https://bugs.kde.org/show_bug.cgi?id=444811 Bug ID: 444811 Summary: Missing libreswan connection editor Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: jgrul...@redhat.com Reporter: mattia.ve...@tiscali.it Target Milestone: --- There's no way to configure libreswan VPN from the plasma-nm editor. It would be nice to have an interface for it, some distributions like Fedora Linux have switched from openswan to libreswan. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 443004] New: gdb keeps crashing on kdevelop
https://bugs.kde.org/show_bug.cgi?id=443004 Bug ID: 443004 Summary: gdb keeps crashing on kdevelop Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- SUMMARY When debugging using kdevelop, I often get the message that gdb crashed and the debugging session ends. If I use gdb outside kdevelop I have no issues with it. STEPS TO REPRODUCE It mostly crashes if I add breakpoints when the debugger is running or when I'm stepping through the code after it hit a breakpoint. While it isn't super consistent, it happens very often when I'm debugging this project: https://gitlab.com/mattbas/glaxnimate OBSERVED RESULT KDevelop stops debugging and shows this message: The debugger process 'gdb' crashed. Because of that the debug session has to be ended. Try to reproduce the crash without KDevelop and report a bug. EXPECTED RESULT It shouldn't crash, I'm fairly certain it's a Kdevelop bug because gdb from the command line does not crash. SOFTWARE/OS VERSIONS gdb: GNU gdb (Ubuntu 10.1-2ubuntu2) 10.1.90.20210411-git Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-36-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-simplemenu] [Bug 441996] New: menu hidden behind main panel
https://bugs.kde.org/show_bug.cgi?id=441996 Bug ID: 441996 Summary: menu hidden behind main panel Product: plasma-simplemenu Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mattia.ve...@tiscali.it CC: plasma-b...@kde.org Target Milestone: --- Created attachment 141288 --> https://bugs.kde.org/attachment.cgi?id=141288=edit submenu hidden behind main panel Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.13.13-200.fc34.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD RENOIR Sub-menus are displayed behind the main panel and latest elements in the menu are not accessible (see screenshot). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 438389] New: Renaming variable causes an endless amount of warnings
https://bugs.kde.org/show_bug.cgi?id=438389 Bug ID: 438389 Summary: Renaming variable causes an endless amount of warnings Product: kdevelop Version: 5.6.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Write some C++ class with a data member, separating header and implementation files 2. Right click on said data member 3. Select "Rename namespace::Class::member" 4. Type a new name and confirm OBSERVED RESULT It renames the variables correctly but there's a warning above the tab bar saying that the header file needs an update. This warning disappears and re-appears several times. Saving or closing the file doesn't make it go away. After enough times of showing and disappearing, it will stop but that takes a while. While it's doing that, the text editor is pretty much unusable because every time the warning appears and disappears it pushes the editor up and down a couple lines. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-18-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437860] New: Views at the bottom of the window disappear when switching between files
https://bugs.kde.org/show_bug.cgi?id=437860 Bug ID: 437860 Summary: Views at the bottom of the window disappear when switching between files Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Have multiple files open (happens both with tabs or split view) 2. Open a view at the bottom of the window (eg: Konsole, GDB, etc.) 3. Switch file (click on another tab or split file) OBSERVED RESULT The bottom view is hidden, its button is still in its checked state as if it were visible but it isn't visible. You need to click the button twice to bring it back. EXPECTED RESULT It should stay on SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437851] The quick open dropdown shows files that have been excluded from the project
https://bugs.kde.org/show_bug.cgi?id=437851 --- Comment #1 from Mattia Basaglia --- Created attachment 138876 --> https://bugs.kde.org/attachment.cgi?id=138876=edit Filters for that project -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 437851] New: The quick open dropdown shows files that have been excluded from the project
https://bugs.kde.org/show_bug.cgi?id=437851 Bug ID: 437851 Summary: The quick open dropdown shows files that have been excluded from the project Product: kdevelop Version: 5.6.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- Created attachment 138875 --> https://bugs.kde.org/attachment.cgi?id=138875=edit Quick open with unwanted entries STEPS TO REPRODUCE 1. Add an "Exclude" filter to the project 2. Type something in "quick open" that is contained in the filtered files OBSERVED RESULT Quick open includes files that should be excluded EXPECTED RESULT Those files shouldn't be listed SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-17-generic OS Type: 64-bit Graphics Platform: X11 Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 31.4 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 436339] Kdevelop gdb integration is extremely slow
https://bugs.kde.org/show_bug.cgi?id=436339 --- Comment #3 from Mattia Basaglia --- I think it's related to the "variables" pane, if I collapse "Locals" it's a bit faster at stepping than when it's expanded. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 436339] New: Kdevelop gdb integration is extremely slow
https://bugs.kde.org/show_bug.cgi?id=436339 Bug ID: 436339 Summary: Kdevelop gdb integration is extremely slow Product: kdevelop Version: 5.5.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- SUMMARY Not always, but often enough, debugging is very slow with kdevelop. Symptoms include: * taking several seconds before "step over" and similar take effect * variable values not updating / loading in their tree view * the "GDB cmd" textbox being grayed out each of the above can take a long time to solve (like 20 seconds or so) to the point of being unusable. The slow down isn't consistent, sometimes everything works, sometimes it takes a handful of seconds (which is annoying but manageable), sometimes it takes a very long time, which makes debugging unusable. This issue only happens with Kdevelop, if I use gdb from the terminal it works fine. I have a fairly powerful computer so that isn't an issue. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-50-generic OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 23.5 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 436059] New: Kdevelop limits the frame stack view to 20 items
https://bugs.kde.org/show_bug.cgi?id=436059 Bug ID: 436059 Summary: Kdevelop limits the frame stack view to 20 items Product: kdevelop Version: 5.5.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: CPP Debugger Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com CC: niko.s...@gmail.com Target Milestone: --- Created attachment 137807 --> https://bugs.kde.org/attachment.cgi?id=137807=edit screenshot comparing the Frame Stack view and gdb output SUMMARY When debugging, the "Frame Stack" tab only ever shows 20 items STEPS TO REPRODUCE 1. have a breakpoint somewhere that is more than 20 frames deep 2. look at "Frame Stack" OBSERVED RESULT "Frame stack" only shows 20 frames. If you run "bt" on the GDB tab you get the full stack. EXPECTED RESULT It should show all the frames, or at least have an option to show more SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-50-generic OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 23.5 GiB of RAM Graphics Processor: AMD Radeon ™ RX 470 Graphics -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384773] Default to not save source list edits
https://bugs.kde.org/show_bug.cgi?id=384773 Mattia changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 306447] Integrate encfs support in dolphin
https://bugs.kde.org/show_bug.cgi?id=306447 Mattia changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432273] New: Breeze icon align-horizontal-left-out uses the wrong graphics
https://bugs.kde.org/show_bug.cgi?id=432273 Bug ID: 432273 Summary: Breeze icon align-horizontal-left-out uses the wrong graphics Product: Breeze Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: mattia.basag...@gmail.com CC: kain...@gmail.com Target Milestone: --- SUMMARY align-horizontal-left-out at 32 resolution uses the same graphics as align-vertical-top-out. STEPS TO REPRODUCE https://github.com/KDE/breeze-icons/blob/master/icons/actions/32/align-horizontal-left-out.svg looks the same as https://github.com/KDE/breeze-icons/blob/master/icons/actions/32/align-vertical-top-out.svg but it should look more in line with this (the 16 resolution version of the icon): https://github.com/KDE/breeze-icons/blob/master/icons/actions/16/align-horizontal-left-out.svg Same thing happens for icons-dark -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 430907] New: RFE: support for exfatprogs
https://bugs.kde.org/show_bug.cgi?id=430907 Bug ID: 430907 Summary: RFE: support for exfatprogs Product: partitionmanager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- It would be nice to have kpmcore support for exfatprogs now that Linux Kernel has exfat support. Though, I don't know if it can co-exist alongside with exfat-utils support or one exclude the other. For example, they share the same `mkfs.exfat`, but I don't know if the two implementations use the same syntax. Fedora cannot ship exfat-utils, but has recently gained exfatprogs in its repos. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 429132] New: Crash when using the quick open box
https://bugs.kde.org/show_bug.cgi?id=429132 Bug ID: 429132 Summary: Crash when using the quick open box Product: kdevelop Version: 5.5.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- Application: kdevelop (5.5.0) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-53-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: Quite often focusing/clicking on "quick open" causes KDevelop to crash. I can't reproduce consistently but it happens every few days. The crash can be reproduced sometimes. -- Backtrace (Reduced): #6 0x7ff47e475114 in QIcon::QIcon(QIcon const&) () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7ff47eb24a99 in QAction::icon() const (this=) at kernel/qaction.cpp:643 [...] #10 0x7ff47debafa9 in QAbstractProxyModel::data(QModelIndex const&, int) const (this=, proxyIndex=..., role=1) at itemmodels/qabstractproxymodel.cpp:245 #11 0x7ff47edb8bc1 in QModelIndex::data(int) const (arole=1, this=0x7fffb73b7410) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:458 #12 QItemDelegate::rect(QStyleOptionViewItem const&, QModelIndex const&, int) const (this=this@entry=0x55a7c16f64c0, option=..., index=..., role=role@entry=1) at itemviews/qitemdelegate.cpp:1045 Possible duplicates by query: bug 410767, bug 409263, bug 375162, bug 323216, bug 213924. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 427147] New: Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 Bug ID: 427147 Summary: Often the background parser causes crashes Product: kdevelop Version: 5.5.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Language Support: CPP (Clang-based) Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- SUMMARY Sometimes KDevelop enters a state where it crashes within a few seconds of opening a project. This seems to happen quite often when I'm refactoring large parts of C++ code, so I think it's related to the C++ background parser. Clearing the cache doesn't help, I have to use other editors to finish my code changes before using KDevelop again. In the console KDevelop prints this before crashing: KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = kdevelop path = /usr/bin pid = 24966 KCrash: Arguments: /usr/bin/kdevelop KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 21 and type 'Read', disabling... QSocketNotifier: Invalid socket 29 and type 'Read', disabling... QSocketNotifier: Invalid socket 32 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 80 and type 'Read', disabling... QSocketNotifier: Invalid socket 75 and type 'Exception', disabling... QSocketNotifier: Invalid socket 24 and type 'Read', disabling... QSocketNotifier: Invalid socket 34 and type 'Read', disabling... QSocketNotifier: Invalid socket 65 and type 'Read', disabling... QSocketNotifier: Invalid socket 77 and type 'Read', disabling... QSocketNotifier: Invalid socket 72 and type 'Read', disabling... QSocketNotifier: Invalid socket 41 and type 'Read', disabling... QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 37 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... kdevelop.plugins.python.parser: Discarding parts of the code to be parsed because of previous errors SyntaxError: unmatched ']' (, line 1) Parsing FAILED LIBCLANG FATAL ERROR: IO failure on output stream: Bad file descriptor Unable to start Dr. Konqi Re-raising signal for core dump handling. Aborted (core dumped) STEPS TO REPRODUCE It's hard to repro, I can provide a tarball of the project that last happened to, but it's too large to attach here. When opening that project in a new KDevelop session it takes longer to crash, I assume it's because the parser needs to reach the point where it crashes. OBSERVED RESULT KDevelop crashes after a few seconds of opening the project SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-48-generic OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 23.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 424703] New: KDevelop keeps crashing while parsing a (C++) file
https://bugs.kde.org/show_bug.cgi?id=424703
Bug ID: 424703
Summary: KDevelop keeps crashing while parsing a (C++) file
Product: kdevelop
Version: 5.5.0
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: mattia.basag...@gmail.com
Target Milestone: ---
Created attachment 130426
--> https://bugs.kde.org/attachment.cgi?id=130426=edit
File I was editing
SUMMARY
It crashed a few times when I was writing the attached file, I left it in the
state it was when it last crashed.
That file is part of a project, not sure that has something to do with it but
it only started crashing when I created this file
OBSERVED RESULT
The output says this:
OverflowError: Python int too large to convert to C long
kdevelop.plugins.clang: No parse session / AST attached to context for url
QUrl("file:///(path to)/vector.hpp")
Segmentation fault (core dumped)
And crashes
EXPECTED RESULT
It shouldn't crash
SOFTWARE/OS VERSIONS
kdevelop 5.5.0
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.4.0-42-generic
OS Type: 64-bit
Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor
Memory: 23.5 GiB of RAM
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 420607] The digital clock shows a huge date
https://bugs.kde.org/show_bug.cgi?id=420607 --- Comment #2 from Mattia Basaglia --- hmm the issue for me is that it scales beyond panel width but it might be related to that other report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422528] New: Maximized windows go below some panels with multiple screens
https://bugs.kde.org/show_bug.cgi?id=422528 Bug ID: 422528 Summary: Maximized windows go below some panels with multiple screens Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: 1.0 SUMMARY Under specific configurations maximized windows stretch too much and are covered by the panels. STEPS TO REPRODUCE 1. Connect two screens 2. In the display settings, put a screen to the left and one to the right 3. In the left screen add a vertical panel on its right edge 4. Open a window on that same screen and maximize it OBSERVED RESULT The maximized window goes under the panel. Note that if you disable the other screen, or you move it to other sides in the display settings this issue doesn't occur. EXPECTED RESULT The maximized window should use the space between panels in the current screen, regardless of the virtual position of other screens. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-33-generic OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 23.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421190] New: Ability to highlight with shape (multiply)
https://bugs.kde.org/show_bug.cgi?id=421190 Bug ID: 421190 Summary: Ability to highlight with shape (multiply) Product: okular Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alterme...@gmail.com Target Milestone: --- Created attachment 128257 --> https://bugs.kde.org/attachment.cgi?id=128257=edit Example showing current behavior SUMMARY Currently, the only way to highlight is to use a highlighter tool, which can only highlight text. You can configure a shape tool to have opacity < 100%, but that will make the underlying content more faded. It would be nice to have the ability to set a multiply mode for shapes and lines, as other PDF viewers (like PDF-XChange) allow. STEPS TO REPRODUCE 1. Use a highlighter and see how only the background changes color, while text remains black 2. Now use a shape or a line configured with less than 100% opacity. OBSERVED RESULT The text will slightly change color to the color of the shape. EXPECTED RESULT If a 'multiply' mode existed in the annotation settings, you could make the shape only change the background color. SOFTWARE/OS VERSIONS Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.69.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420607] New: The digital clock shows a huge date
https://bugs.kde.org/show_bug.cgi?id=420607 Bug ID: 420607 Summary: The digital clock shows a huge date Product: plasmashell Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: 1.0 Created attachment 127880 --> https://bugs.kde.org/attachment.cgi?id=127880=edit what the digital clock shows SUMMARY I have a vertical panel, with a digital clock widget. I set the custom date format to "ddd d MMM" and it was fine at first. But after a restart the date is drawn with a giant font (see attached screenshot). Looks like going to the digital clock settings, setting an empty format, apply, and putting the format back what to it was makes it a little bit smaller but still too big. I'd want the date to be on a single line and be scaled down to fit, not scaled up so every word fills the panel width, otherwise the clock uses up most of the space of the panel itself. SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-26-generic OS Type: 64-bit Processors: 8 × AMD FX(tm)-8320 Eight-Core Processor Memory: 23.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 417628] Exclude filter in find/replace files dialog doesn't seem to work
https://bugs.kde.org/show_bug.cgi?id=417628 Mattia Basaglia changed: What|Removed |Added CC||mattia.basag...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 414624] New: FileSystem::sectorsUsed(): partitionmanager killed by SIGSEGV
https://bugs.kde.org/show_bug.cgi?id=414624 Bug ID: 414624 Summary: FileSystem::sectorsUsed(): partitionmanager killed by SIGSEGV Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- A Fedora user reported a crash while creating a LUKS ext4 partition. Version-Release number of selected component: kde-partitionmanager-4.0.0-2.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/user@1000.service/gnome-shell-wayland.service cmdline:partitionmanager crash_function: FileSystem::sectorsUsed executable: /usr/bin/partitionmanager journald_cursor: s=72b73fcd08f54901b8af8bfd9f1cc603;i=7acbd;b=be349b3e97fb464aaf595be88aaeb259;m=5955cd21;t=5985c3d576f8a;x=f6d3484cfa751398 kernel: 5.3.12-300.fc31.x86_64 rootdir:/ runlevel: N 5 type: CCpp uid:1000 Truncated backtrace: Thread no. 1 (10 frames) #0 FileSystem::sectorsUsed at /usr/include/c++/9/bits/unique_ptr.h:352 #1 Partition::sectorsUsed at /usr/src/debug/kpmcore-4.0.1-1.fc31.x86_64/src/core/partition.h:187 #2 Partition::used at /usr/src/debug/kpmcore-4.0.1-1.fc31.x86_64/src/core/partition.h:154 #3 PartWidget::paintEvent at /usr/src/debug/kpmcore-4.0.1-1.fc31.x86_64/src/gui/partwidget.cpp:96 #4 QWidget::event at kernel/qwidget.cpp:8965 #5 QApplicationPrivate::notify_helper at kernel/qapplication.cpp:3700 #6 QApplication::notify(QObject*, QEvent*) at kernel/qapplication.cpp:3446 #7 QCoreApplication::notifyInternal2 at kernel/qcoreapplication.cpp:1088 #8 QWidgetPrivate::sendPaintEvent at kernel/qwidget.cpp:5701 #9 QWidgetPrivate::drawWidget at kernel/qwidget.cpp:5641 The full backtrace is available at https://bugzilla.redhat.com/show_bug.cgi?id=1777607 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 412887] New: Shared library calls exit
https://bugs.kde.org/show_bug.cgi?id=412887 Bug ID: 412887 Summary: Shared library calls exit Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- rpmlint shows a warning about libkpmcore calling exit on GLIBC: kpmcore.x86_64: W: shared-lib-calls-exit /usr/lib64/libkpmcore.so.4.0.1 exit@GLIBC_2.2.5 shared-lib-calls-exit: This library package calls exit() or _exit(), probably in a non-fork() context. Doing so from a library is strongly discouraged - when a library function calls exit(), it prevents the calling program from handling the error, reporting it to the user, closing files properly, and cleaning up any state that the program has. It is preferred for the library to return an actual error code and let the calling program decide how to handle the situation. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 411287] New: Wrong link to splash screen SVGs
https://bugs.kde.org/show_bug.cgi?id=411287 Bug ID: 411287 Summary: Wrong link to splash screen SVGs Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Website Assignee: digikam-bugs-n...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- The link to SVGs files at https://www.digikam.org/contribute/splashscreens/ links to older versions in KDE repository which wouldn't open with up to date Inkscape. It should have been changed to link to Github versions. As a side not, I would like to suggest you to make use of images from Pixabay website for splash screens, which are all CC0. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 409230] New: The Javascript parser does not support modern Ecmascript versions
https://bugs.kde.org/show_bug.cgi?id=409230
Bug ID: 409230
Summary: The Javascript parser does not support modern
Ecmascript versions
Product: kdevelop
Version: 5.2.4
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: QML/JavaScript
Assignee: kdevelop-bugs-n...@kde.org
Reporter: mattia.basag...@gmail.com
Target Milestone: ---
SUMMARY
If I write javascript code using `class` and such, I get "Syntax Error" from
the parser
STEPS TO REPRODUCE
1. Create a js file in your project
2. Type something like `class Foo {}`
3. You might need to close and re-open the file for the parser to pick up the
errors (not 100% reliable)
4. Open the "Problems" pane
5. Notice it highlights "class" as a syntax error
OBSERVED RESULT
The parser treats ECMAScript 6 features as syntax errors.
EXPECTED RESULT
It should parse them correctly.
SOFTWARE/OS VERSIONS
Ubuntu 18.10
KDE Frameworks 5.50.0
Qt 5.11.1 (built against 5.11.1)
The xcb windowing system
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 407834] fatresize at the end of a restore operation fails with warning
https://bugs.kde.org/show_bug.cgi?id=407834 --- Comment #2 from Mattia --- (In reply to Andrius Štikonas from comment #1) > Does KDE Partition Manager report that operation succeeded (since it's a > warning only)? It wasn't clear to me from this bug. Yes, the final result reported by PM is that the operation succeeded. This is just a warning issued in the details log. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407834] New: fatresize at the end of a restore operation fails with warning
https://bugs.kde.org/show_bug.cgi?id=407834 Bug ID: 407834 Summary: fatresize at the end of a restore operation fails with warning Product: partitionmanager Version: 4.0.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- At the end of a restore operation a fatresize command is always performed even if one doesn't select the option to maximize the partition. Moreover, the fatresize command fails and produce a warning: Restore partition from ‘/home/taurus/efi.backup’ to ‘/dev/sda2’ Job: Restore the file system from file ‘/home/taurus/efi.backup’ to partition ‘/dev/sda2’ Copying 10 blocks (104857600 bytes) from 94371840 to 73495740416, direction: right. Copying 10 blocks (104857600 bytes) finished. Closing device. This may take a few seconds. Restore the file system from file ‘/home/taurus/efi.backup’ to partition ‘/dev/sda2’: Success Job: Check file system on partition ‘/dev/sda2’ Command: fsck.fat -a -w -v /dev/sda2 Check file system on partition ‘/dev/sda2’: Success Job: Maximize file system on ‘/dev/sda2’ to fill the partition Resizing file system from 104857600 to 204800 sectors. Command: fatresize --verbose --size 104857600 /dev/sda2 Maximize file system on ‘/dev/sda2’ to fill the partition: Error WARNING: Maximizing file system on target partition ‘/dev/sda2’ to the size of the partition failed. Restore partition from ‘/home/taurus/efi.backup’ to ‘/dev/sda2’: Warning -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 399791] Partitionmanager tries to check whole disk instead of partition after restore operation
https://bugs.kde.org/show_bug.cgi?id=399791 --- Comment #3 from Mattia --- I can reproduce the bug only if I try to restore to an already existent partition. For example, if I choose to restore the partition to unallocated space on the disk, PM will firstly create the partition, then it prints: Restore partition from ‘/home/taurus/efi.raw’ to ‘/dev/sda2’ Job: Restore the file system from file ‘/home/taurus/efi.raw’ to partition ‘/dev/sda2’ ... Restore the file system from file ‘/home/taurus/efi.raw’ to partition ‘/dev/sda2’: Success Job: Check file system on partition ‘/dev/sda2’ But if I choose to restore to an already partition I get the same output of the submitter's log. Pay attention to the change of the partition name from the second line onward: the first line correctly outputs '/dev/sda2' in both cases, but when restoring to an already existent partition it points to '/dev/sda'. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 407007] Slow performance on opening zip file
https://bugs.kde.org/show_bug.cgi?id=407007 --- Comment #4 from Mattia --- The libzip plugin doesn't get created in Fedora RPMS because the .spec file misses libzip-devel as BuildRequires. By using the libzip plugin the performance greatly improves, so I've reported to Fedora Bugzilla a request to enable it: https://bugzilla.redhat.com/show_bug.cgi?id=1706358 I think you can close this bug here. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 407007] Slow performance on opening zip file
https://bugs.kde.org/show_bug.cgi?id=407007 --- Comment #2 from Mattia --- (In reply to Elvis Angelaccio from comment #1) > Do you have the libzip plugin installed? Can you try again using that plugin? What do you mean with "libzip plugin"? I have libzip installed: $ rpm -q libzip libzip-1.5.2-1.fc30.x86_64 But in Ark settings -> extensions list I don't have libzip, only info-zip and p7zip (related to zip archves). Where I can found that plugin and how can I install it? -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 407007] New: Slow performance on opening zip file
https://bugs.kde.org/show_bug.cgi?id=407007 Bug ID: 407007 Summary: Slow performance on opening zip file Product: ark Version: 18.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: mattia.ve...@tiscali.it CC: rthoms...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Download breeze-icons tarball from https://github.com/KDE/breeze-icons 2. Try to open it with Ark, or select "Extract here" from contextual menu in dolphin OBSERVED RESULT Ark takes minutes to open the archive or extract the files, while from command line a "unzip breeze-icons-master.zip" takes a couple of seconds. EXPECTED RESULT Ark should have the same performance of command line. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora RPMs (available in About System) KDE Plasma Version: plasma-desktop-5.15.4-1.fc30.x86_64 KDE Frameworks Version: KDE Frameworks 5.55.0 Qt Version: Qt 5.12.1 (compilato con 5.12.1) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406733] New: Audio "Fade in" not working properly
https://bugs.kde.org/show_bug.cgi?id=406733 Bug ID: 406733 Summary: Audio "Fade in" not working properly Product: kdenlive Version: 19.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: alterme...@gmail.com Target Milestone: --- SUMMARY When adding a Audio correction / Fade in effect, the effect doesn't work at all. Furthermore, when moving the slider to change the duration, even a little bit, the diagonal line on the clip in the timeline becomes much longer than the time that's been set. STEPS TO REPRODUCE 1. Add an audio file into the timeline (I tested with an MKV video, removing the video part and leaving the Opus audio part) 2. Add the Audio correction > Fade in effect 3. Play the project 4. Try moving the slider in the effect settings to change the duration OBSERVED RESULT The effect doesn't work; Moving the slider causes the diagonal line in the timeline to be too long. EXPECTED RESULT The effect should work, with the audio slowly increasing its volume at the beginning; Moving the slider should cause a diagonal line to appear that's as long as the set time. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fully updated Arch Linux with the default repositories (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.2 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405828] Budget problems
https://bugs.kde.org/show_bug.cgi?id=405828 --- Comment #3 from Mattia --- Created attachment 119506 --> https://bugs.kde.org/attachment.cgi?id=119506=edit Budget widget screenshot (In reply to Thomas Baumgart from comment #2) > I may not completely understand your comment, but showing overruns in this > widget was never intended. Can you elaborate why you think it is not > working? How would you envision the overrun should be identified? In KMyMoney 4.x the widget used to show the monthly summary and the categories for which the budget was overrun in the month. Now it only shows the monthly summary, but in the categories table it always shows "No budget categories have been overrun" even if there are actually some categories for which the budget has been overrun. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 405828] Budget problems
https://bugs.kde.org/show_bug.cgi?id=405828 Mattia changed: What|Removed |Added CC||mattia.ve...@tiscali.it --- Comment #1 from Mattia --- In 5.0.3 the totals are working, but the widget still doesn't show budget overruns in categories (only the total overrun works). -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 406425] New: Revert current change not available on folder
https://bugs.kde.org/show_bug.cgi?id=406425 Bug ID: 406425 Summary: Revert current change not available on folder Product: kdesvn Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kdesvn-bugs-n...@kde.org Reporter: mattia.filippin...@gmail.com Target Milestone: --- SUMMARY Revert current change not available on folder Kubuntu 18.04 Kdesvn 2.0 STEPS TO REPRODUCE 1. Modify one file in any folder 2. Open kdesvn and select the folder 3. Under subversion->working copy there isn't Revert. 4. Instead if you selected directly the file, under subversion->working you can make a Revert. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 395856] Semantic highlighting uses hardcoded colors that cannot be changed
https://bugs.kde.org/show_bug.cgi?id=395856 Mattia changed: What|Removed |Added CC||toder...@gmail.com --- Comment #19 from Mattia --- I think this is a missing features too. It's frustating that i can't change color on some basic "keywords". -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 399791] Partitionmanager tries to check whole disk instead of partition after restore operation
https://bugs.kde.org/show_bug.cgi?id=399791 --- Comment #1 from Mattia --- With PM 3.80.0 the problem has now changed: the "Check file system" operation is now successful (it correctly checks the recovered partition instead of the whole disk), but after that a warning is produced in the "Maximize file system" operation: Job: Check file system on partition ‘/dev/vdb1’ Command: fsck.fat -a -w -v /dev/vdb1 Check file system on partition ‘/dev/vdb1’: Success Job: Maximize file system on ‘/dev/vdb1’ to fill the partition Resizing file system from 1262485504 to 2465792 sectors. Command: fatresize --verbose --size 1262485504 /dev/vdb1 Maximize file system on ‘/dev/vdb1’ to fill the partition: Error WARNING: Maximizing file system on target partition ‘/dev/vdb1’ to the size of the partition failed. Restore partition on ‘/dev/vdb’ at 1,00 MiB from ‘/home/rpmbuild/testbkp’: Warning -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360262] Plasmashell and krunner stop responding after copying text to clipboard
https://bugs.kde.org/show_bug.cgi?id=360262 Mattia changed: What|Removed |Added CC||mattia.ve...@tiscali.it Version|5.5.5 |5.14.90 --- Comment #6 from Mattia --- I've also seen this behavior since few years, it happens frequently when using Fedora with KDE in a guest KVM machine. When I try to copy text from kwrite it sometimes randomly freeze for 10 seconds or so, after that in the clipboard history I can see an empty line: it's like something weird and huge is being copied in the clipboard. I usually don't see this behavior in the host machine, only in the guest. I think bug #404145 may be a duplicate of this. Still seeing this on 5.14.90 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389241] Several errors in migrating from sqlite to external mysql server
https://bugs.kde.org/show_bug.cgi?id=389241 Mattia changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Mattia --- Not sure what is changed, but now it seems I have no more problems in migrating and using Digikam with external MySQL database on my NAS. One year ago I tried Digikam 5.9 from appimage, now I'm using 5.9 from Fedora repository and it works, so I'll close this bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391980] all budgets have no total balance amounts
https://bugs.kde.org/show_bug.cgi?id=391980 Mattia changed: What|Removed |Added CC||mattia.ve...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 399791] New: Partitionmanager tries to check whole disk instead of partition after restore operation
https://bugs.kde.org/show_bug.cgi?id=399791 Bug ID: 399791 Summary: Partitionmanager tries to check whole disk instead of partition after restore operation Product: partitionmanager Version: 3.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- Restoring a partition from a backup ends with a failure message, but the restore is successful. It seems that PM tries to check the whole disk instead of the partition in the end, so it gets a failure: https://bugzilla.redhat.com/show_bug.cgi?id=1639021 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 399790] New: Authorization problems
https://bugs.kde.org/show_bug.cgi?id=399790 Bug ID: 399790 Summary: Authorization problems Product: partitionmanager Version: 3.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- Some users in Fedora have reported to have authorization problems with current version of PM: https://bugzilla.redhat.com/show_bug.cgi?id=1575385 https://bugzilla.redhat.com/show_bug.cgi?id=1639020 I don't know if you want to bother with that, since I've tested both problems disappear by using the kauth experimental branch. Is there any ETA for that branch to become stable? -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 398091] New: Wait for identification before connect to channels
https://bugs.kde.org/show_bug.cgi?id=398091 Bug ID: 398091 Summary: Wait for identification before connect to channels Product: konversation Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: konversation-de...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- Please add an option to wait for identification before trying to join channels to avoid not being able to join channel at startup: [Channel] Cannot join channel (+r) - you need to be identified with services [Notice] -NickServ- You are now identified for ... -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396749] New: [kauth] NTFS partitions not recognized
https://bugs.kde.org/show_bug.cgi?id=396749 Bug ID: 396749 Summary: [kauth] NTFS partitions not recognized Product: partitionmanager Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- Using kauth branch, NTFS partitions are not correctly recognized, they're detected as "unformatted". -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396312] [Kauth] "Invalid cryptographic signature" error when using qca with openssl backend
https://bugs.kde.org/show_bug.cgi?id=396312 --- Comment #17 from Mattia --- Seems to work well, I don't see warnings or crashes anymore. Thanks -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396312] [Kauth] "Invalid cryptographic signature" error when using qca with openssl backend
https://bugs.kde.org/show_bug.cgi?id=396312
--- Comment #8 from Mattia ---
(In reply to Andrius Štikonas from comment #6)
>
> I think my GSoC student that if defice model name is empty it would be RAID.
> Which is actually false even for one of my USB sticks which is also missing.
> I guess that virtualized /dev/vda also doesn't have model name.
# lsblk --nodeps --paths --sort name --json --output type,name,model
{
"blockdevices": [
{"type": "disk", "name": "/dev/vda", "model": null}
]
}
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 396312] [Kauth] "Invalid cryptographic signature" error when using qca with openssl backend
https://bugs.kde.org/show_bug.cgi?id=396312
--- Comment #7 from Mattia ---
(In reply to Andrius Štikonas from comment #4)
>
> Can you check if you can see /dev/vda device in
> lsblk --nodeps --paths --sort name --json --output type,name
> and that it has "type": "disk"
>
> There were some RAID changes recently but they shouldn't have broken
> /dev/vda support...
Just tried and yes, /dev/vda is showed:
# lsblk --nodeps --paths --sort name --json --output type,name
{
"blockdevices": [
{"type": "disk", "name": "/dev/vda"}
]
}
Also note that NTFS partitions are not recognized correctly in kauth branch
(they are showed as "unknown" type).
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 396312] [Kauth] "Invalid cryptographic signature" error when using qca with openssl backend
https://bugs.kde.org/show_bug.cgi?id=396312 --- Comment #3 from Mattia --- I can't reproduce the crash, it only happened once, so maybe it was a coincidence. I've updated Fedora RPMs on COPR with today snapshot of kauth branch. The error is still showed, but I've noticed that I get it only switching backend: if I refresh the device list with F5, rescanning the partition table doesn't trigger that warning in console. Very rarely I can see a QT warning like this: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 12247, resource id: 35651797, major code: 40 (TranslateCoords), minor code: 0 Unfortunately, I also noticed that in device list I get only the LVM device, the real disk (/dev/vda) is not showed anymore. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396312] New: [Kauth] "Invalid cryptographic signature" error on Fedora 29
https://bugs.kde.org/show_bug.cgi?id=396312 Bug ID: 396312 Summary: [Kauth] "Invalid cryptographic signature" error on Fedora 29 Product: partitionmanager Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- Created attachment 113834 --> https://bugs.kde.org/attachment.cgi?id=113834=edit crash backtrace Running kauth git version of partitionmanager in Fedora 29 by using self compiled RPMs available in https://copr.fedorainfracloud.org/coprs/mattia/Testing/builds/ shows "Invalid cryptographic signature" error s in console while switching backend. I've also noticed that switching from sfdisk to dummy backend and then switching back to sfdsik, the devices list is not correctly refreshed. In a default installation, I have /dev/vda and /dev/fedora which is a partition of /dev/vda showed at startup in the devices window. After switching to dummy and back to sfdisk, most of the times I get a crappy device list with only /dev/vda or only /dev/fedora with a crappy partition table list which seems a mix between the partition table of the two devices... Only once I could get a crash backtrace while switching backends, which I report in the attached file. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 --- Comment #16 from Mattia --- I confirm all the issues are now fixed. Switching to dummy backend does not make PM crash anymore. About the polkit dialog which wasn't showed, launching PM from console showed a lot of "qca does not support rsa" messages. I've found that by installing package qca-qt5-ossl I can successfully authenticate and see the devices. >From console I can also see the "Inavlid cryptographic signature errors" every time I switch the backend. I will open a new ticket for that, because I've noticed some other strange behaviour here. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 --- Comment #13 from Mattia --- I'm waiting for the new build to be completed, unfortunately COPR seems to be down at the moment. https://copr.fedorainfracloud.org/coprs/mattia/Testing/build/774961/ I will test the fix when the build will be completed. I didn't see any error related to cryptographic signature, but in my previous tests I can't get the polkit dialog neither. I'm on #fedora-kde with nick mattiaV, although I'm rarely logged in. Thanks -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 --- Comment #6 from Mattia --- (In reply to Andrius Štikonas from comment #5) > Hi Mattia, > > I can see the crash with your packages on F28 too. Yet when I tried self > compiled build it worked. > > I guess we need to try to find out what is different... Maybe one of the security flags injected by Fedora build system leads to this difference? If you can give me any advice I can try to to some build excluding that flag. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 396196] New: Random crash on C++ autocompletion
https://bugs.kde.org/show_bug.cgi?id=396196 Bug ID: 396196 Summary: Random crash on C++ autocompletion Product: kdevelop Version: 5.2.1 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: mattia.basag...@gmail.com Target Milestone: --- Application: kdevelop (5.2.1) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-24-generic x86_64 Distribution: Ubuntu 18.04 LTS -- Information about the crash: - What I was doing when the application crashed: Kdevelip crashed when triggering autompletion on c++ sources, I noticed that while parsing the code at startup it used 4GB of RAM, not sure if that is related to the crash but it feels kdevelop is struggling to with my project (the source of the issue seems to have the code from this repo https://github.com/tdlib/td within the open project). -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7feca40b7940 (LWP 31667))] Thread 17 (Thread 0x7fec1f7fe700 (LWP 32165)): #0 0x7feca07470b4 in __GI___libc_read (fd=62, buf=0x7fec1f7fd980, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fec97671960 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fec9762cf27 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fec9762d3e0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fec9762d54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7feca109990b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7feca103e9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feca0e5d22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fec9e956a0f in () at /usr/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.52 #9 0x7feca0e6216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fec99edb6db in start_thread (arg=0x7fec1f7fe700) at pthread_create.c:463 #11 0x7feca075888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fec1effd700 (LWP 31793)): #0 0x7feca074bbf9 in __GI___poll (fds=0x7fec100051e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fec9762d439 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fec9762d54c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7feca109990b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feca103e9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7feca0e5d22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fec373bd3c5 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so #7 0x7feca0e6216d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fec99edb6db in start_thread (arg=0x7fec1effd700) at pthread_create.c:463 #9 0x7feca075888f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7fec353c4700 (LWP 31786)): #0 0x7feca071b9d0 in __GI___nanosleep (requested_time=0x7fec353c2a50, remaining=0x7fec353c2a50) at ../sysdeps/unix/sysv/linux/nanosleep.c:28 #1 0x7feca109927d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fec9e894c38 in KDevelop::DUChainLock::lockForWrite(unsigned int) () at /usr/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.52 #3 0x7fec9e894e4c in KDevelop::DUChainWriteLocker::lock() () at /usr/lib/x86_64-linux-gnu/libKDevPlatformLanguage.so.52 #4 0x7fec3f74c3f6 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.30 #5 0x7fec3f74c160 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.30 #6 0x7fec3f74c160 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.30 #7 0x7fec3f74c160 in ClangHelpers::buildDUChain(void*, QMultiHash const&, ParseSession const&, KDevelop::TopDUContext::Features, QHash&, ClangIndex*, std::function const&) () at /usr/lib/x86_64-linux-gnu/libKDevClangPrivate.so.30 #8 0x7fec3f74c160 in ClangHelpers::buildDUChain(void*, QMultiHash
[partitionmanager] [Bug 396099] [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 --- Comment #2 from Mattia --- (In reply to Andrius Štikonas from comment #1) > Strangely, crash happens in the code that reads colours from settings file. > Was this a new system? Or did you run older versions of KPM there (although, > it shouldn't interfere in my oppinion). This was a clean new system. I've also tried to uninstall the kauth version, install and run the stable version and the retry with the kauth version, but it still crashes. If you want to check build logs for something strange or odd build flags, here it is: https://copr.fedorainfracloud.org/coprs/mattia/Testing/build/772749/ It's also strange that if I install that build on my real machine which is running F28, when I launch partitionmanager I get the prompt which asks me for authentication; on F29 I get no prompt. In both cases the program can't see any disk. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 396099] New: [kauth] no devices listed and crash if select dummy backend
https://bugs.kde.org/show_bug.cgi?id=396099 Bug ID: 396099 Summary: [kauth] no devices listed and crash if select dummy backend Product: partitionmanager Version: Git Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- Created attachment 113722 --> https://bugs.kde.org/attachment.cgi?id=113722=edit backtrace I tried to build kauth branch on a Fedora Rawhide (F29) test virtual machine. When I launch partitionmanager I get no device listed. Looking in the settings, I tried to change the backend from sfdisk to Dummy, as soon as I click on apply, partitionmanager crashes with the attached backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 383418] Saving diff produces empty file
https://bugs.kde.org/show_bug.cgi?id=383418 --- Comment #5 from Mattia <mattia.ve...@tiscali.it> --- Yes, I'm using the F27 RPMs (and Rawhide RPMs on the Virtual machine). Running the command from console correctly produces the diff file. -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 383418] Saving diff produces empty file
https://bugs.kde.org/show_bug.cgi?id=383418 --- Comment #2 from Mattia <mattia.ve...@tiscali.it> --- Created attachment 110370 --> https://bugs.kde.org/attachment.cgi?id=110370=edit screenshot of diff settings I made the exact same steps (see screenshot), but when I save the diff file I get a 0 byte file: $ ls -l conf.diff -rw---. 1 marvin marvin 0 6 feb 17.28 conf.diff I get the same result in a freshly installed Fedora Rawhide virtual machine. I already tried to load default kompare settings, but nothing change. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389241] Several errors in migrating from sqlite to external mysql server
https://bugs.kde.org/show_bug.cgi?id=389241 --- Comment #6 from Mattia <mattia.ve...@tiscali.it> --- (In reply to Maik Qualmann from comment #5) > Are there any problems with other programs to access the MariaDB server, > possibly even Qt programs? There was a new client library with MariaDB-10.2. > It would be conceivable that there are therefore problems with the older > MariaDB server version on the NAS? Is there an update for the NAS? > > Maik Actually the only other program that uses the MariaDB on the NAS is Amarok and I never had any problem with it so far. Unfortunately, there's no update to MariaDB 10 for Qnap NASs. I always used to have Digikam database on the NAS with old 4.x, but after the port to Qt5 I had to revert back to Sqlite. Some months ago, with Digikam 5.6 (or maybe it was 5.7) I successfully managed to migrate the database on the NAS, but I reverted back because of the problems with disappearing tags. Now it seems that with 5.8 and 5.9 I'm not able to migrate the DB again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389241] Several errors in migrating from sqlite to external mysql server
https://bugs.kde.org/show_bug.cgi?id=389241 --- Comment #4 from Mattia <mattia.ve...@tiscali.it> --- (In reply to Maik Qualmann from comment #3) Can you test it with a locally running MariaDB server, if the > problem also occurs here? > > Maik The migration to a mysql server hosted locally works. But in this case I used MariaDB 10.2.9, while on the Qnap NAS I have MariaDB 5.5.44. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389241] Several errors in migrating from sqlite to external mysql server
https://bugs.kde.org/show_bug.cgi?id=389241 --- Comment #2 from Mattia <mattia.ve...@tiscali.it> --- Created attachment 110027 --> https://bugs.kde.org/attachment.cgi?id=110027=edit 5.9 appimage console output - migration fails (In reply to caulier.gilles from comment #1) > 5.9.0 include last changes from Maik about database migration tool. This can > fix your report. No, this doesn't solve the issue. Now it creates the database schema, but as soon as it starts creating AlbumRoots it says "Can't connect to MySQL server". I attach the output from console. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 389241] New: Several errors in migrating from sqlite to external mysql server
https://bugs.kde.org/show_bug.cgi?id=389241
Bug ID: 389241
Summary: Several errors in migrating from sqlite to external
mysql server
Product: digikam
Version: 5.8.0
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Database-Migration
Assignee: digikam-bugs-n...@kde.org
Reporter: mattia.ve...@tiscali.it
Target Milestone: ---
I've just upgraded to Digikam 5.8 and I tried the database migration tool to
migrate from local Sqlite database to an external mysql (mariadb) server
located on a local NAS.
First thing, it would be nice to have some debug output when things gone
wrong... at the moment I can only get some quite unuseful message.
The first error happens just at the first step ("Copy albums..."): suddendly I
get a "Lost connection to database server", but I don't know if it's caused by
a connection timeout or if the operation is successfully completed, but it
doesn't get finalized in some way (looking in the database by phpMyAdmin I can
see the "albums" table to be populated).
The second error is when I try to re-launch the migration tool: I get "Error
while trying to clean the destination database" (roughly translated from
Italian). Seems that the tool is not able to clean the database... I have to
manually drop the database and recreate it.
--
You are receiving this mail because:
You are watching all bug changes.
[partitionmanager] [Bug 387463] New: Wrong mountpoint creation
https://bugs.kde.org/show_bug.cgi?id=387463 Bug ID: 387463 Summary: Wrong mountpoint creation Product: partitionmanager Version: 3.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: mattia.ve...@tiscali.it Target Milestone: --- After creating a new partition formatted as FAT16 or FAT32, if you select to edit the mountpoint, partitionmanager creates an entry in /etc/fstab with type fat16 or fat32, which leads to a "unknown filesystem type 'fat16'" or "unknown filesystem type 'fat32'" error when trying to mount it. It should be a vfat mountpoint. Original bug was reported on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1517718 I also verified that if you change the filesystem from fat16 to fat32 or viceversa and then you edit the mountpoint, the type in fstab entry is not updated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 387287] New: Plasma desktop crashes on wayland when launching system settings (Fedora 27)
https://bugs.kde.org/show_bug.cgi?id=387287 Bug ID: 387287 Summary: Plasma desktop crashes on wayland when launching system settings (Fedora 27) Product: plasmashell Version: 5.11.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mattia.ve...@tiscali.it CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.3) Qt Version: 5.9.2 Frameworks Version: 5.40.0 Operating System: Linux 4.13.13-300.fc27.x86_64 x86_64 Distribution: "Fedora release 27 (Twenty Seven)" -- Information about the crash: - What I was doing when the application crashed: Logged in into plasma wayland and opened System Settings. Every time I open System Setting Plasma crashes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd71d486940 (LWP 1542))] Thread 25 (Thread 0x7fd604be1700 (LWP 2139)): [KCrash Handler] #6 0x7fd713c41ea0 in wl_proxy_create_wrapper () from /lib64/libwayland-client.so.0 #7 0x7fd6f44b12c1 in dri2_wl_create_window_surface () from /lib64/libEGL_mesa.so.0 #8 0x7fd6f449e857 in _eglCreateWindowSurfaceCommon () from /lib64/libEGL_mesa.so.0 #9 0x7fd6f4eb407d in QtWaylandClient::QWaylandEglWindow::updateSurface(bool) () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so #10 0x7fd6f4eb25f5 in QtWaylandClient::QWaylandGLContext::makeCurrent(QPlatformSurface*) () from /usr/lib64/qt5/plugins/wayland-graphics-integration-client/libwayland-egl.so #11 0x7fd7165c8096 in QOpenGLContext::makeCurrent(QSurface*) () from /lib64/libQt5Gui.so.5 #12 0x7fd71a883a04 in QSGRenderThread::invalidateOpenGL(QQuickWindow*, bool, QOffscreenSurface*) () from /lib64/libQt5Quick.so.5 #13 0x7fd71a88b30b in QSGRenderThread::event(QEvent*) () from /lib64/libQt5Quick.so.5 #14 0x7fd71a88a597 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #15 0x7fd71a88a96a in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #16 0x7fd7159bfb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #17 0x7fd714072609 in start_thread () from /lib64/libpthread.so.0 #18 0x7fd714d54e6f in clone () from /lib64/libc.so.6 Thread 24 (Thread 0x7fd6053e2700 (LWP 2138)): #0 0x7fd714078c3b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd66a3d23cb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fd66a3d22e7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fd714072609 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd714d54e6f in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fd605de7700 (LWP 2137)): #0 0x7fd714078c3b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd7159c02eb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7fd71a88a508 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7fd71a88a96a in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7fd7159bfb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7fd714072609 in start_thread () from /lib64/libpthread.so.0 #6 0x7fd714d54e6f in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fd6065e8700 (LWP 2136)): #0 0x7fd714078c3b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd66a3d23cb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fd66a3d22e7 in impl_thrd_routine () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fd714072609 in start_thread () from /lib64/libpthread.so.0 #4 0x7fd714d54e6f in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7fd606de9700 (LWP 2132)): #0 0x7fd714078c3b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd7159c02eb in QWaitCondition::wait(QMutex*, unsigned long) () from /lib64/libQt5Core.so.5 #2 0x7fd71a88a508 in QSGRenderThread::processEventsAndWaitForMore() () from /lib64/libQt5Quick.so.5 #3 0x7fd71a88a96a in QSGRenderThread::run() () from /lib64/libQt5Quick.so.5 #4 0x7fd7159bfb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7fd714072609 in start_thread () from /lib64/libpthread.so.0 #6 0x7fd714d54e6f in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7fd6075ea700 (LWP 2131)): #0 0x7fd714078c3b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fd66a3d23cb in util_queue_thread_func () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fd66a3d22e7 in impl_thrd_routine () from
[apper] [Bug 387063] Apper crashes on launch on Fedora 27
https://bugs.kde.org/show_bug.cgi?id=387063 Mattia <mattia.ve...@tiscali.it> changed: What|Removed |Added CC||mattia.ve...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 387063] Apper crashes on launch on Fedora 27
https://bugs.kde.org/show_bug.cgi?id=387063 --- Comment #1 from Mattia <mattia.ve...@tiscali.it> --- Created attachment 108959 --> https://bugs.kde.org/attachment.cgi?id=108959=edit New crash information added by DrKonqi apper (0.9.3) using Qt 5.9.2 - What I was doing when the application crashed: Apper crashes on launch. Fedora 27 x86_64 -- Backtrace (Reduced): #6 0x7f49f9f0e61a in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5 #7 0x560f0d2a08bb in MainUi::MainUi (this=0x560f0e1c1950, parent=) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48 #8 0x560f0d2a502a in Apper::showUi (this=0x7ffebf616220) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171 #9 0x7f49f240491a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #10 0x7f49f42624df in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 386617] New: Yahoo online quotes service has been shutted down
https://bugs.kde.org/show_bug.cgi?id=386617 Bug ID: 386617 Summary: Yahoo online quotes service has been shutted down Product: kmymoney Version: 4.8.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- Yahoo online quotes service has been shutted down and should be removed from the available services. Opening http://download.finance.yahoo.com/ in a browser returns: "It has come to our attention that this service is being used in violation of the Yahoo Terms of Service. As such, the service is being discontinued. For all future markets and equities data research, please refer to finance.yahoo.com." I think the entire list of online quotes service needs to be checked to see what works and what doesn't. -- You are receiving this mail because: You are watching all bug changes.
[apper] [Bug 384773] New: Default to not save source list edits
https://bugs.kde.org/show_bug.cgi?id=384773 Bug ID: 384773 Summary: Default to not save source list edits Product: apper Version: 0.9.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: mattia.ve...@tiscali.it Target Milestone: --- When editing the package sources list, apper will save edits as soon as I check/uncheck an entry in the list. My proposal is: 1. let the user make all the edits and save only when a confirmation button is pressed 2. put a checkbox to let the user choose if he wants to really save the edits as default setting for a future use, or only use the edits for the actual session. The second point is useful when you want to search and install a specific package from a updates-testing repository. At the moment I have to enable the updates-testing repository, install the package and then manually disable again the updates-testing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 375346] Many tags disappeared from database
https://bugs.kde.org/show_bug.cgi?id=375346 Mattia <mattia.ve...@tiscali.it> changed: What|Removed |Added CC||mattia.ve...@tiscali.it --- Comment #11 from Mattia <mattia.ve...@tiscali.it> --- I've hit this problem yesterday, after database migration from SQLite to MySQL external. The migration went fine, but after changing tags to some images and moving tags from one parent to another I saw Digikam doing something strange (tags in tags manager were not updated correctly). Closed and restarted Digikam, all tags disappeared. Probably related to bug 383326? There's also bug 383563 which seems a duplicate of this one. I'm switched back to SQLite, will retry as soon 5.7 will be available in Fedora repositories. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384492] Error migrating database from SQLite to MySQL external
https://bugs.kde.org/show_bug.cgi?id=384492 Mattia <mattia.ve...@tiscali.it> changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Mattia <mattia.ve...@tiscali.it> --- Sorry, it seems that my SQLite database was corrupted in some way. I had to delete it and let Digikam rebuild a new DB, after that I successfully migrated to mySQL. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 384492] New: Error migrating database from SQLite to MySQL external
https://bugs.kde.org/show_bug.cgi?id=384492 Bug ID: 384492 Summary: Error migrating database from SQLite to MySQL external Product: digikam Version: 5.6.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Migration Assignee: digikam-bugs-n...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- I'm trying to migrate my Digikam DB from SQLite to an external MySQL server (MariaDB 5.5.44 running on Qnap NAS). The process fails at 91% of "Copy ImageInformation" step with the error "Cannot add or update a child row: a foreign key constraint fails (`digikam`.`ImageInformation`, CONSTRAINT `ImageInformation_Images` FOREIGN KEY (`imageid`) REFERENCES `Images` (`id`) ON DELETE CASCADE ON UPDATE CASCADE)" -- You are receiving this mail because: You are watching all bug changes.
[kompare] [Bug 383418] New: Saving diff produces void file
https://bugs.kde.org/show_bug.cgi?id=383418 Bug ID: 383418 Summary: Saving diff produces void file Product: kompare Version: 4.1.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kompare-de...@kde.org Reporter: mattia.ve...@tiscali.it Target Milestone: --- If I compare two text files I can see the differences in the browser, but when I choose to save the comparison to a file, Kompare produces void file (zero byte). No error is showed. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 368175] Error creating new partition with KDE auto-mount enabled
https://bugs.kde.org/show_bug.cgi?id=368175 Mattia <mattia.ve...@tiscali.it> changed: What|Removed |Added Version|2.2 |3.0 --- Comment #1 from Mattia <mattia.ve...@tiscali.it> --- This still applies to PM 3.0.1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 374295] New: Systemsettings5 crashing after loading everything twice in "Application style"
https://bugs.kde.org/show_bug.cgi?id=374295 Bug ID: 374295 Summary: Systemsettings5 crashing after loading everything twice in "Application style" Product: systemsettings Version: 5.8.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: alterme...@gmail.com Target Milestone: --- Application: systemsettings5 (5.8.5) Qt Version: 5.7.1 Frameworks Version: 5.29.0 Operating System: Linux 4.8.13-1-ARCH x86_64 Distribution (Platform): Archlinux Packages -- Information about the crash: - What I was doing when the application crashed: I started systemsettings5 and went to "application style" under "appearance". Then, I loaded every sub-menu (on the left) twice or more. When going back to All settings after doing this, the application crashes. The crash can be reproduced every time. -- Backtrace: Application: Impostazioni di sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5205bcd1c0 (LWP 5705))] Thread 4 (Thread 0x7f51d6b1a700 (LWP 5711)): #0 0x7f51fbd19db9 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7f51fbcd4680 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f51fbcd489c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f52022142db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f52021bdd3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f5201fe0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f5200333e75 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f5201fe4cf8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f51fd9bf454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f52018fa7df in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f51e9e05700 (LWP 5708)): #0 0x7f52018f148d in poll () from /usr/lib/libc.so.6 #1 0x7f51fbcd4786 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f51fbcd489c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f52022142db in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f52021bdd3a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f5201fe0063 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f5202b29de5 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f5201fe4cf8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f51fd9bf454 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f52018fa7df in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f51f240f700 (LWP 5707)): #0 0x7f52018f148d in poll () from /usr/lib/libc.so.6 #1 0x7f51fe2428e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f51fe244679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f51f4561789 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f5201fe4cf8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f51fd9bf454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f52018fa7df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f5205bcd1c0 (LWP 5705)): [KCrash Handler] #6 0x7f5200204cc0 in QV4::PersistentValueStorage::freePage(void*) () from /usr/lib/libQt5Qml.so.5 #7 0x7f52002053a2 in QV4::WeakValue::free() () from /usr/lib/libQt5Qml.so.5 #8 0x7f5200275e42 in QV4::QObjectWrapper::destroyObject(bool) () from /usr/lib/libQt5Qml.so.5 #9 0x7f520010c63f in QV4::MemoryManager::sweep(bool) () from /usr/lib/libQt5Qml.so.5 #10 0x7f520010da4c in QV4::MemoryManager::~MemoryManager() () from /usr/lib/libQt5Qml.so.5 #11 0x7f52001f4f6b in QV4::ExecutionEngine::~ExecutionEngine() () from /usr/lib/libQt5Qml.so.5 #12 0x7f5200335926 in QV8Engine::~QV8Engine() () from /usr/lib/libQt5Qml.so.5 #13 0x7f5200335a49 in QV8Engine::~QV8Engine() () from /usr/lib/libQt5Qml.so.5 #14 0x7f520018c216 in QJSEngine::~QJSEngine() () from /usr/lib/libQt5Qml.so.5 #15 0x7f52002a00bd in QQmlEngine::~QQmlEngine() () from /usr/lib/libQt5Qml.so.5 #16 0x7f52002a0179 in QQmlEngine::~QQmlEngine() () from /usr/lib/libQt5Qml.so.5 #17 0x7f52021e9831 in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5 #18 0x7f52021f30df in QObject::~QObject() () from /usr/lib/libQt5Core.so.5 #19 0x7f52007fe4b4 in QQuickWindow::~QQuickWindow() () from /usr/lib/libQt5Quick.so.5 #20 0x7f52008adf89 in QQuickView::~QQuickView() () from /usr/lib/libQt5Quick.so.5 #21 0x7f5203dad2a5 in QWindowContainer::~QWindowContainer() () from /usr/lib/libQt5Widgets.so.5 #22 0x7f5203dad2c9 in QWindowContainer::~QWindowContainer() () from /usr/lib/libQt5Widgets.so.5 #23 0x7f52021e9831 in QObjectPrivate::deleteChildren() () from
[apper] [Bug 372292] apper hang on close
https://bugs.kde.org/show_bug.cgi?id=372292 Mattia <mattia.ve...@tiscali.it> changed: What|Removed |Added CC||mattia.ve...@tiscali.it -- You are receiving this mail because: You are watching all bug changes.
