[partitionmanager] [Bug 400652] Partition Manager does not support whole disk partitions
https://bugs.kde.org/show_bug.cgi?id=400652 Andrius Štikonas changed: What|Removed |Added CC||pseudo-acco...@yandex.ru --- Comment #4 from Andrius Štikonas --- *** Bug 407713 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 397302] KDE Partition manager crashing after upgrade
https://bugs.kde.org/show_bug.cgi?id=397302 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #2 from Andrius Štikonas --- Could also be resolved in kpmcore 4 which uses different backend. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407617] Partition manager crash on clicking (probably faulty) drive.
https://bugs.kde.org/show_bug.cgi?id=407617 --- Comment #2 from Andrius Štikonas --- By the way, I don't think it's because of faulty drive. The drive is probably fine. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407617] Partition manager crash on clicking (probably faulty) drive.
https://bugs.kde.org/show_bug.cgi?id=407617 --- Comment #1 from Andrius Štikonas --- Is this reproducible? I think I saw similar backtrace from time to time but could never reproduce it reliably. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 353651] Formatting disks gives wrong permissions
https://bugs.kde.org/show_bug.cgi?id=353651 Andrius Štikonas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|ASSIGNED|RESOLVED --- Comment #2 from Andrius Štikonas --- Closing this as duplicate even though the other bug is much newer (but it has more accurate comments, i.e. it's not because of GUI running as root). *** This bug has been marked as a duplicate of bug 407192 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 Andrius Štikonas changed: What|Removed |Added CC||nortex...@gmail.com --- Comment #8 from Andrius Štikonas --- *** Bug 353651 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 --- Comment #6 from Andrius Štikonas --- (In reply to Nate Graham from comment #5) > So should we move this bug to frameworks-solid? I don't know... But it would be good to know opinion of more people on who should change permissions. Maybe solid people would think that we shouldn't change permissions when we mount external devices in solid. Do you know who maintains Solid? Maybe we can add them to CC on this bug and ask what they think? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407414] Partition Manager shows no disk information
https://bugs.kde.org/show_bug.cgi?id=407414 Andrius Štikonas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DOWNSTREAM -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407414] Partition Manager shows no disk information
https://bugs.kde.org/show_bug.cgi?id=407414 --- Comment #1 from Andrius Štikonas --- Might be packaging bug. Can you open Slackware bug and post a link here? It looks like DBus permissions issue. kpmcore installs the following files: /etc/dbus-1/system.d/org.kde.kpmcore.applicationinterface.conf /etc/dbus-1/system.d/org.kde.kpmcore.externalcommand.conf /etc/dbus-1/system.d/org.kde.kpmcore.helperinterface.conf and it seems to work on all other distros. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407210] Partition manager gets stuck when scanning for partitions on a drive containing a partition with jfs
https://bugs.kde.org/show_bug.cgi?id=407210 --- Comment #1 from Andrius Štikonas --- what is the version of jfsutils? I have 1.1.15 and it seems to work fine. What about if you run jfs_debugfs manually. KDE Partition Manager basically runs "jfs_debugfs /dev/sdb1" and inputs "dm" Maybe you can paste the output of that command? -- 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 Andrius Štikonas changed: What|Removed |Added Version Fixed In||4.0.1 -- 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 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||kpmcore/commit/4b6a26f0f800 ||60d522e485c0ebf1b14eb089ef5 ||2 Resolution|--- |FIXED --- Comment #5 from Andrius Štikonas --- Git commit 4b6a26f0f80060d522e485c0ebf1b14eb089ef52 by Andrius Štikonas. Committed on 10/05/2019 at 01:12. Pushed by stikonas into branch 'master'. Fix setting partition path when restoring partitions. M +1-1src/ops/restoreoperation.cpp https://invent.kde.org/kde/kpmcore/commit/4b6a26f0f80060d522e485c0ebf1b14eb089ef52 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 --- Comment #4 from Andrius Štikonas --- (In reply to Nate Graham from comment #2) > This is probably a side effect of running the whole app as root. Now that > partition manager uses polkit, hopefully that will fix or alleviate the > issue. If not, it really should explicitly return ownership of the new > partition to the user who has just made it. By the way, GUI running as normal user wouldn't fix it. All operations are still done with root privileges, e.g. sfdisk or mkfs.ext4 runs as root. -- 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 #4 from Andrius Štikonas --- 2019 m. gegužės 9 d., ketvirtadienis 10:51:19 BST rašėte: > 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. Thanks! This piece of information is really useful. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 --- Comment #3 from Andrius Štikonas --- (In reply to Nate Graham from comment #2) > This is probably a side effect of running the whole app as root. Now that > partition manager uses polkit, hopefully that will fix or alleviate the > issue. If not, it really should explicitly return ownership of the new > partition to the user who has just made it. In principle I can run chown after creating the partition. But the question is why is this partition manager's job. Shouldn't it be the job of whatever mounts the new partition (Solid?). Let's say user A has two computers, on one computer his UID is 1000, on another, 1001. If the user formats USB stick with Ext4 on the first computer, that user won't have permissions on the other computer. Shouldn't this be done while mounting from e.g. Dolphin/Plasma? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 407276] In partitionmanager 4.0 S.M.A.R.T. status is not working
https://bugs.kde.org/show_bug.cgi?id=407276 Andrius Štikonas changed: What|Removed |Added Product|partitionmanager|neon Assignee|andr...@stikonas.eu |neon-b...@kde.org CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Component|general |Packages User Edition -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407276] In partitionmanager 4.0 S.M.A.R.T. status is not working
https://bugs.kde.org/show_bug.cgi?id=407276 --- Comment #1 from Andrius Štikonas --- You need to install smartmontools 7.0. I guess neon is based on Ubuntu 18.04 LTS, so smartmontools are too old. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407191] Video playback stops and mouse cursor is laggy while partition manager creates and formats partitions
https://bugs.kde.org/show_bug.cgi?id=407191 --- Comment #9 from Andrius Štikonas --- You can also try some Live CDs to see if you can reproduce it there. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407191] Video playback stops and mouse cursor is laggy while partition manager creates and formats partitions
https://bugs.kde.org/show_bug.cgi?id=407191 Andrius Štikonas changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #8 from Andrius Štikonas --- Yes, I'll take a look at it too. I'll close this bug in the meantime as it's not something I can fix in partition manager. But you can still comment here. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407191] Video playback stops and mouse cursor is laggy while partition manager creates and formats partitions
https://bugs.kde.org/show_bug.cgi?id=407191 --- Comment #6 from Andrius Štikonas --- Ok, so that's not partition manager bug. Something else is broken on your system and triggering udev rules triggers CPU usage. This should not happen. Hmm, maybe you can figure out what is wrong by enabling udev debugging. https://wiki.archlinux.org/index.php/udev#Debug_output Hmm, maybe open Arch bug that "udevadm trigger" causes this? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407191] Video playback stops and mouse cursor is laggy while partition manager creates and formats partitions
https://bugs.kde.org/show_bug.cgi?id=407191 --- Comment #4 from Andrius Štikonas --- Try running some of these commands manually to see if anything triggers high CPU usage. Maybe udevadm triggers it? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407191] Video playback stops and mouse cursor is laggy while partition manager creates and formats partitions
https://bugs.kde.org/show_bug.cgi?id=407191 --- Comment #1 from Andrius Štikonas --- Did you notice anything else unusual? E.g. CPU usage went up to 100% or maybe system started swapping. I never observed anything like that and nobody else reported this. As it stands, I'm not even sure where to start with this bug. You might want to try running some of the same commands that partition manager runs to see if any of them cause slowdowns (if you start partitionmanager from terminal with "KPMCORE_DEBUG=1 partitionmanager" it will print list of commands that it is running), although, a few commands require input which is not printed. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 --- Comment #1 from Andrius Štikonas --- Hmm, I'm not sure if it's partition manager's responsibility to do that. It might be whoever is mounting (Solid?). I discussed it briefly with Fedora packager some time ago (after fedora bug was open https://bugzilla.redhat.com/show_bug.cgi?id=1538641) It was actually Fedora packager who thought that this is not partition manager's responsibility. Well, let's keep this bug open, to track this issue even though I was aware of it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360475] Open in file manager for individual images
https://bugs.kde.org/show_bug.cgi?id=360475 --- Comment #9 from Andrius --- I have noticed that the feature works in GIMP (on Windows). Is there any way their code could be used in digiKam ? I think I found it: https://gitlab.gnome.org/GNOME/gimp/blob/master/app/dialogs/file-open-location-dialog.c -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400331] partition flags are not imported
https://bugs.kde.org/show_bug.cgi?id=400331 --- Comment #3 from Andrius Štikonas --- Git commit a6861bf202a60462dd8063064749417b07df4117 by Andrius Štikonas. Committed on 28/02/2019 at 00:16. Pushed by stikonas into branch 'master'. When importing partition table, pass the flags to Partition class. Note, this is not enough for flags to work. We need to run a job to set flags. M +1-1src/gui/mainwindow.cpp https://invent.kde.org/kde/partitionmanager/commit/a6861bf202a60462dd8063064749417b07df4117 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400331] partition flags are not imported
https://bugs.kde.org/show_bug.cgi?id=400331 --- Comment #2 from Andrius Štikonas --- Git commit 92065f7a23cf83a52a82d87c1b4002c8e233a8cc by Andrius Štikonas. Committed on 28/02/2019 at 00:15. Pushed by stikonas into branch 'master'. Add a function to convert QStringList of flag names to flags. M +14 -0src/core/partitiontable.cpp M +1-0src/core/partitiontable.h https://invent.kde.org/kde/kpmcore/commit/92065f7a23cf83a52a82d87c1b4002c8e233a8cc -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||partitionmanager/commit/730 ||b2a9992251cb2841cb8baa73d9d ||baa8fbad54 Resolution|--- |FIXED --- Comment #8 from Andrius Štikonas --- Git commit 730b2a9992251cb2841cb8baa73d9dbaa8fbad54 by Andrius Štikonas. Committed on 27/02/2019 at 23:15. Pushed by stikonas into branch 'master'. Fix race condition in reading fstype on partition table import. Thanks to Christoph Vogtländer for reporting and fixing. M +1-1src/gui/mainwindow.cpp https://invent.kde.org/kde/partitionmanager/commit/730b2a9992251cb2841cb8baa73d9dbaa8fbad54 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 Andrius Štikonas changed: What|Removed |Added Version Fixed In||4.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #7 from Andrius Štikonas --- (In reply to Christoph Vogtländer from comment #6) > I launched my favorite debugger and found the problem: > mainwindow.cpp:1006: QLatin1String fsName = > QLatin1String(rePartition.captured(4).toLatin1()); > > From the Qt documentation: > QLatin1String::QLatin1String(const QByteArray ) > Constructs a QLatin1String object that stores str. > **The string data is not copied. The caller must be able to guarantee that > str will not be deleted or modified as long as the QLatin1String object > exists.** > > So it is a mistake to construct a QLatin1String from a temporary. > > As "fsType" is required to be a QString later anyway, a possible fix would > be to simply create a QString: > QString fsName = rePartition.captured(4); > > I tested this and it works. > > But, this has explicitly changed in 4b4198c34a9f4880546242de330138cc11da8359 > together with the creation of "fs*". The latter was reverted in > 24237a6120e31f1051a07499f04c7391b877552c Oh thanks for debugging this! I just started looking at this issue a few minutes ago. But you already finished investigation -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #5 from Andrius Štikonas --- (In reply to Andrius Štikonas from comment #3) > I am actually surprised that sometimes partition is loaded correctly. > > As far as I remember, there is no code to detect file system type in file. > > We use "udevadm info --query=property /dev/deviceNode" to detect fs type but > that only works with kernel devices, not files. Sorry, this comment was misleading, since the bug is about partition table import, not restoring partitions (which would be much harder to fix). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #3 from Andrius Štikonas --- I am actually surprised that sometimes partition is loaded correctly. As far as I remember, there is no code to detect file system type in file. We use "udevadm info --query=property /dev/deviceNode" to detect fs type but that only works with kernel devices, not files. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 400330] Filesystem type unknown after partition table import
https://bugs.kde.org/show_bug.cgi?id=400330 --- Comment #1 from Andrius Štikonas --- Can you confirm whether that this happens before applying operations? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 404788] Secure Erase
https://bugs.kde.org/show_bug.cgi?id=404788 Andrius Štikonas changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Andrius Štikonas --- By the way, you can also write random data to partitions, not just format. (That said it does not replace SSD Secure replace) -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 404743] Data source for National Library of Lithuania has incorrect address
https://bugs.kde.org/show_bug.cgi?id=404743 --- Comment #2 from Andrius Kurtinaitis --- Could you please also include the z39.libis.lt? The "Union" catalogue is larger, because it includes the books from National Library and also several other large public libraries in Lithuania. -- You are receiving this mail because: You are watching all bug changes.
[tellico] [Bug 404743] New: Data source for National Library of Lithuania has incorrect address
https://bugs.kde.org/show_bug.cgi?id=404743 Bug ID: 404743 Summary: Data source for National Library of Lithuania has incorrect address Product: tellico Version: HEAD Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ro...@periapsis.org Reporter: andr...@kurtinaitis.lt Target Milestone: --- The file /usr/share/tellico/z3950-servers.cfg contains entry [libis] Host=z3950.libis.lt This one does not resolve in DNS. The correct host address is z39.libis.lt. Please replace it. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 404636] Device/partition properties dialogs: minimum size is too small
https://bugs.kde.org/show_bug.cgi?id=404636 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 404636] Device/partition properties dialogs: minimum size is too small
https://bugs.kde.org/show_bug.cgi?id=404636 --- Comment #1 from Andrius Štikonas --- This already fixed in 4.0 beta. On Thu, Feb 21, 2019 at 07:59:03AM +, tguen wrote: > https://bugs.kde.org/show_bug.cgi?id=404636 > > Bug ID: 404636 >Summary: Device/partition properties dialogs: minimum size is > too small >Product: partitionmanager >Version: 3.3 > Platform: Archlinux Packages > OS: Linux > Status: REPORTED > Severity: normal > Priority: NOR > Component: general > Assignee: andr...@stikonas.eu > Reporter: tg...@tutanota.com > Target Milestone: --- > > Created attachment 118245 > --> https://bugs.kde.org/attachment.cgi?id=118245=edit > screenshot of partition properties > > SUMMARY > In the device/partition properties dialogs, there is a map of the > device/partition at the top. When the dialog is shrunk vertically to its > minimum size, the next row of widgets are pushed on top of it. The 'flags' > list > widget at the bottom of partition properties also becomes unusable because it > is only big enough to show half an item. > > > SOFTWARE/OS VERSIONS > Arch Linux > KDE Plasma Version: 5.15.1 > KDE Frameworks Version: 5.55.0 > Qt Version: 5.12.1 > > -- > You are receiving this mail because: > You are the assignee for the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404580] kwin crashes when enabling laptop screen
https://bugs.kde.org/show_bug.cgi?id=404580 --- Comment #3 from Andrius Štikonas --- On 2019-02-20 05:24, Martin Flöser wrote: > https://bugs.kde.org/show_bug.cgi?id=404580 > > --- Comment #2 from Martin Flöser --- > I don't see a crash in the frame stacks. How can I obtain a crash log then. I obtained this by running coredumpctl debug /usr/bin/kwin_wayland. And dmesg clearly indicates General protection fault, so some illegal action was being attempted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404580] kwin crashes when enabling laptop screen
https://bugs.kde.org/show_bug.cgi?id=404580 --- Comment #1 from Andrius Štikonas --- I can also see this in journalctl vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: Change detected vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: Change detected vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: Change detected vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:19 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:19 laptop kernel: traps: kwin_wayland[3739] general protection ip:7fe8e2ae4040 sp:7ffe3c050b60 error:0 in libQt5Core.so.5.12.1[7fe8e279f000+65f000] vas. 20 00:59:19 laptop systemd[1]: Started Process Core Dump (PID 5436/UID 0). vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: Saving current config to file vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: Config saved on: "/home/andrius/.local/share/kscreen/2c86d3716a57a3dfb9e034cabaced403" vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 1 "AUO eDP-1-unknown" connected disabled pos: QPoint(0,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferredMode: false ) vas. 20 00:59:20 laptop kdeinit5[3778]: kscreen.kded: KScreen::Output( 2 "SAM HDMI-A-1-S24C300/808661304" connected enabled primary pos: QPoint(1920,0) res: QSize(-1, -1) modeId: "0" scale: 1 followPreferred> vas. 20 00:59:22 laptop konsole[5372]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop systemsettings5[5308]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop plasmashell[4391]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop org.kde.kpasswdserver[3701]: The Wayland connection broke. Did the Wayland compositor die? vas. 20 00:59:22 laptop org.kde.kpasswdserver[3701]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDEDModule*): Pointers are not supported: KDEDModule* vas. 20 00:59:22 laptop org.kde.kuiserver[3701]: The Wayland connection broke. Did the Wayland compositor die? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404580] kwin crashes when enabling laptop screen
https://bugs.kde.org/show_bug.cgi?id=404580 Andrius Štikonas changed: What|Removed |Added CC||h...@kde.org, ||k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 404580] New: kwin crashes when enabling laptop screen
https://bugs.kde.org/show_bug.cgi?id=404580 Bug ID: 404580 Summary: kwin crashes when enabling laptop screen Product: kwin Version: 5.15.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: andr...@stikonas.eu Target Milestone: --- I have an external screen that is plugged into my laptop. Normally, my display configuration is laptop screen (on the left) is turned off, and external screen on the right is enabled. If I go to screens kcm and enabled laptops screen (positioning it to the left of external screen), kwin_wayland crashes. (gdb) thread apply all bt Thread 10 (Thread 0x7fe8a242e700 (LWP 3771)): #0 0x7fe8e15c9d43 in poll () from /lib64/libc.so.6 #1 0x7fe8d7fb31cb in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe8d7fb32ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe8e2b2aa52 in QEventDispatcherGlib::processEvents (this=0x7fe89c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7fe8e2a9c5ff in QEventLoop::processEvents (this=0x7fe8a242dce0, flags=...) at kernel/qeventloop.cpp:138 #5 0x7fe8e2a9c8fd in QEventLoop::exec (this=0x7fe8a242dce0, flags=...) at kernel/qeventloop.cpp:225 #6 0x7fe8e285b62d in QThread::exec (this=0x55582905ef40) at thread/qthread.cpp:531 #7 0x7fe8eab51a65 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7fe8e285e290 in QThreadPrivate::start (arg=0x55582905ef40) at thread/qthread_unix.cpp:361 #9 0x7fe8e55d496a in start_thread () from /lib64/libpthread.so.0 #10 0x7fe8e15d591f in clone () from /lib64/libc.so.6 Thread 9 (Thread 0x7fe89a49f700 (LWP 3772)): #0 0x7fe8e15cfdf9 in syscall () from /lib64/libc.so.6 #1 0x7fe8e285ff94 in QtLinuxFutex::_q_futex (addr=0x55582918fa80, op=0, val=0, val2=0, addr2=0x0, val3=0) at thread/qfutex_p.h:92 #2 0x7fe8e286451f in QtLinuxFutex::futexWait > (futex=..., expectedValue=0) at thread/qfutex_p.h:107 #3 0x7fe8e286406d in futexSemaphoreTryAcquire_loop (u=..., curValue=4294967296, nn=8589934593, timeout=-1) at thread/qsemaphore.cpp:219 #4 0x7fe8e2863c96 in futexSemaphoreTryAcquire (u=..., n=1, timeout=-1) at thread/qsemaphore.cpp:262 #5 0x7fe8e28635ee in QSemaphore::acquire (this=0x55582918fa80, n=1) at thread/qsemaphore.cpp:326 #6 0x7fe8c66c77da in ?? () from /usr/lib64/libQt5HunspellInputMethod.so.5 #7 0x7fe8e285e290 in QThreadPrivate::start (arg=0x55582918fa60) at thread/qthread_unix.cpp:361 #8 0x7fe8e55d496a in start_thread () from /lib64/libpthread.so.0 #9 0x7fe8e15d591f in clone () from /lib64/libc.so.6 Thread 8 (Thread 0x7fe898c9c700 (LWP 3775)): #0 0x7fe8e55db57c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe8ec0389c4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fe8ec038a09 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fe8e55d496a in start_thread () from /lib64/libpthread.so.0 #4 0x7fe8e15d591f in clone () from /lib64/libc.so.6 Thread 7 (Thread 0x7fe8a700 (LWP 3770)): #0 0x7fe8e15c9d43 in poll () from /lib64/libc.so.6 #1 0x7fe8d7fb31cb in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe8d7fb32ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe8e2b2aa52 in QEventDispatcherGlib::processEvents (this=0x7fe8a4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4 0x7fe8e2a9c5ff in QEventLoop::processEvents (this=0x7fe8afffece0, flags=...) at kernel/qeventloop.cpp:138 #5 0x7fe8e2a9c8fd in QEventLoop::exec (this=0x7fe8afffece0, flags=...) at kernel/qeventloop.cpp:225 #6 0x7fe8e285b62d in QThread::exec (this=0x555828f39720) at thread/qthread.cpp:531 #7 0x7fe8eab51a65 in ?? () from /usr/lib64/libQt5Qml.so.5 #8 0x7fe8e285e290 in QThreadPrivate::start (arg=0x555828f39720) at thread/qthread_unix.cpp:361 #9 0x7fe8e55d496a in start_thread () from /lib64/libpthread.so.0 #10 0x7fe8e15d591f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fe8b581c700 (LWP 3743)): #0 0x7fe8e55db57c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe8b61968cb in ?? () from /usr/lib64/dri/i965_dri.so #2 0x7fe8b61965da in ?? () from /usr/lib64/dri/i965_dri.so #3 0x7fe8e55d496a in start_thread () from /lib64/libpthread.so.0 #4 0x7fe8e15d591f in clone () from /lib64/libc.so.6 ---Type to continue, or q to quit--- Thread 5 (Thread 0x7fe8c4b3c700 (LWP 3742)): #0 0x7fe8e15c9d43 in poll () from /lib64/libc.so.6 #1 0x7fe8d7fb31cb in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe8d7fb32ec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe8e2b2aa52 in QEventDispatcherGlib::processEvents (this=0x7fe8bc000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:422 #4
[plasmashell] [Bug 390092] plasmashell crashes on boot
https://bugs.kde.org/show_bug.cgi?id=390092
--- Comment #12 from Andrius Štikonas ---
(In reply to Kai Uwe Broulik from comment #6)
> The code in question is
>
> if (!m_desktopViewforId.contains(m_screenPool->id(screen->name( {
>
> and in QScreen::name() it does
>
> return d->platformScreen->name();
>
> so I suspect for whatever reason it never set a platform screen
I think it's the QScreen::handle() function that crashes, i.e. call to
d->platformScreen, not d->platformScren->name().
--
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 Andrius Štikonas changed: What|Removed |Added URL||https://bugzilla.redhat.com ||/show_bug.cgi?id=1639021 -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 384452] KTorrent does not recognize directories when creating .torrent file
https://bugs.kde.org/show_bug.cgi?id=384452 Andrius Štikonas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kto ||rrent/dab5abcd2172155c511e0 ||666d867c37382829226 Resolution|--- |FIXED --- Comment #2 from Andrius Štikonas --- Git commit dab5abcd2172155c511e0666d867c37382829226 by Andrius Štikonas, on behalf of Jiva Totin. Committed on 17/02/2019 at 20:00. Pushed by stikonas into branch 'master'. Allow creating torrent for a single file. Added 2 new radio buttons. One for choosing directory and the other one for choosing files. Differential Revision: https://phabricator.kde.org/D11728 M +17 -1ktorrent/dialogs/torrentcreatordlg.cpp M +3-0ktorrent/dialogs/torrentcreatordlg.h M +38 -18 ktorrent/dialogs/torrentcreatordlg.ui https://commits.kde.org/ktorrent/dab5abcd2172155c511e0666d867c37382829226 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390092] plasmashell crashes on boot
https://bugs.kde.org/show_bug.cgi?id=390092 Andrius Štikonas changed: What|Removed |Added Attachment #110444|0 |1 is obsolete|| --- Comment #11 from Andrius Štikonas --- Created attachment 118157 --> https://bugs.kde.org/attachment.cgi?id=118157=edit backtrace.txt Updating backtrace with Plasma 5.15. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 Andrius Štikonas changed: What|Removed |Added Latest Commit||fa7c27c9cf8e30699fb6070f644 ||5496016bb1990 --- Comment #58 from Andrius Štikonas --- (In reply to Tristan Miller from comment #57) > I see this bug has just been marked as RESOLVED/FIXED. Could someone point > me to the commit where the feature has been added? https://cgit.kde.org/kdepim-runtime.git/commit/resources/ews?id=fa7c27c9cf8e30699fb6070f6445496016bb1990 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390092] plasmashell crashes on boot
https://bugs.kde.org/show_bug.cgi?id=390092 Andrius Štikonas changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #10 from Andrius Štikonas --- Nope. It still crashed after a few more reboots. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390092] plasmashell crashes on boot
https://bugs.kde.org/show_bug.cgi?id=390092 Andrius Štikonas changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Andrius Štikonas --- Somehow the crash is gone after upgrading to Qt 5.12.1 (from Qt 5.12.0). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 78629] MS Exchange mail support
https://bugs.kde.org/show_bug.cgi?id=78629 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED CC||andr...@stikonas.eu Status|REOPENED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Andrius Štikonas changed: What|Removed |Added Severity|critical|normal --- Comment #15 from Andrius Štikonas --- Lowering priority to Normal since part of functionality is restored. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 404398] Ability to move partition of unknown type
https://bugs.kde.org/show_bug.cgi?id=404398 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||kpmcore/commit/ecb78121f36d ||6e30e164e5ea7f3145504765f48 ||a --- Comment #3 from Andrius Štikonas --- Git commit ecb78121f36d6e30e164e5ea7f3145504765f48a by Andrius Štikonas. Committed on 15/02/2019 at 19:16. Pushed by stikonas into branch 'master'. Allow moving partitions of unknown type. This usually be safe. There is a theoretical chance that some unknown OS fails to boot, but I'm not aware of any such cases. M +3-0src/fs/unknown.cpp M +7-2src/fs/unknown.h https://invent.kde.org/kde/kpmcore/commit/ecb78121f36d6e30e164e5ea7f3145504765f48a -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 404398] Ability to move partition of unknown type
https://bugs.kde.org/show_bug.cgi?id=404398 --- Comment #1 from Andrius Štikonas --- Well, in principle this can be added. But then there is a risk that we incorrectly move some partition of unknown type. Not msft-reserved as this partition is just a blank partition but e.g. FAT/NTFS need extra adjustments after move (I think update boot sector location), gparted probably doesn't do that but I haven't checked recently. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 --- Comment #14 from Andrius Štikonas --- > --- Comment #13 from Tony Murray --- > Wayland does not support embedding one process' window in another. > > To fix this, it probably needs to use the xfreerdp libraries and draw > into the > krdc window. Is this really the case? I haven't looked at Wayland in enough detail to know. it might be worth looking at what mpv does on Wayland. There is something here: https://github.com/mpv-player/mpv/commit/8d8d4c5cb1b3553215a8ba547d4db463fdc88831 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 --- Comment #12 from Andrius Štikonas --- I've pushed improved patch as: https://cgit.kde.org/krdc.git/commit/?id=94c7c9ada2103ef8274dd6046e69fe82d7b755d2 I'll leave the bug open until somebody fixes embedding wayland RDP window into krdc. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 403179] Compositor (System Settings Module) window is open upon login
https://bugs.kde.org/show_bug.cgi?id=403179 --- Comment #8 from Andrius Štikonas --- (In reply to Martin Flöser from comment #7) > (In reply to Vlad Zagorodniy from comment #6) > > > This is from KWin, automatically showing the dialog when it is sure the > > > settings are not right and need to be adjusted by the user. > > I can't find any code that spawns the Compositing KCM. Does KWin actually do > > that? > > it did, but IIRC I removed it. Coincidentally, I haven't managed to reproduce this yet after upgrading to Plasma 5.15 beta. Although, even before it wasn't easy to reproduce due to kwin crashes when display outputs are changed. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403980] Partition manager crashes with segmentation fault when finished moving or resizing partitions
https://bugs.kde.org/show_bug.cgi?id=403980 --- Comment #1 from Andrius Štikonas --- Yes, if you can obtain backtrace, it would be useful. Otherwise it's hard to fix this since I can't reproduce it. Just to make sure, you were not closing any windows? Have operations just finished and KDE Partition Manager crashed without any of your actions or have you closed Apply Progress Dialog? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 --- Comment #9 from Andrius Štikonas --- Nouveau? https://bugs.archlinux.org/task/61638 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 --- Comment #8 from Andrius Štikonas --- (In reply to mthw0 from comment #7) > After a further investigation it looks like I have this with every app that > has a menu. So it is probably kwin or Qt bug and this can be closed then. [20:09] stikonas: there are constant fixes to QtWayland wrt popup handling [20:10] there's another one on review ATM [20:11] I see. Strangely everything works fine for me in this case [20:12] I would guess you have a newer Qt than the reporter [20:12] actuallty older. I have QT 5.12.0, reporter has Qt 5.12.1 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403966] Program always starts in privileges-less mode on wayland
https://bugs.kde.org/show_bug.cgi?id=403966 --- Comment #5 from Andrius Štikonas --- [20:09] stikonas: there are constant fixes to QtWayland wrt popup handling [20:10] there's another one on review ATM -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 --- Comment #4 from Andrius Štikonas --- (In reply to mthw0 from comment #3) > It looks like on Plasma Xorg this problem doesn't occur and partitionmanager > runs just fine. What about GNOME Wayland? -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403970] Partition manager crashes just by browsing menus
https://bugs.kde.org/show_bug.cgi?id=403970 --- Comment #2 from Andrius Štikonas --- Hmm, for now I still can't reproduce with Qt 5.12.0 KDE Frameworks 5.54 KDE Plasma Version (Wayland): 5.14.90 So as you can see, a fairly similar versions. Can you try without Wayland? It could be that you are hitting something else, but I'm not sure. (I've been using Wayland for over a year, haven't seen any issues) -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403966] Program always starts in privileges-less mode on wayland
https://bugs.kde.org/show_bug.cgi?id=403966 --- Comment #4 from Andrius Štikonas --- (In reply to mthw0 from comment #3) > (In reply to Andrius Štikonas from comment #2) > > Oh, and can you mention in more details what is unstable? Just "unstable" is > > not very helpful for me. > > Yeah, I know that isn't a very good description, but I was running it with > gdb and it didn't show me a single line when it crashed. I will build and > try the new version (3.80.0) anyway. Version 3.80.0 is easier to debug with gdb too. In version 3.3, when you start partitionmanager, it starts another instance of partitionmanager which runs as root. It could be that your gdb was attached to the wrong intance of partitionmanager. Version 4 beta also has two processes but different ones. One is partitionmanager process which is most of the code and a small daemon (kpmcore_externalcommandhelper) which runs as root. And the good thing is that even if partitionmanager crashes or is killed, kpmcore_externalcommandhelper will keep running until it finishes current job (not the whole operation, just particular job, but that's already much safer). -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403966] Program always starts in privileges-less mode on wayland
https://bugs.kde.org/show_bug.cgi?id=403966 --- Comment #2 from Andrius Štikonas --- Oh, and can you mention in more details what is unstable? Just "unstable" is not very helpful for me. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403966] Program always starts in privileges-less mode on wayland
https://bugs.kde.org/show_bug.cgi?id=403966 Andrius Štikonas changed: What|Removed |Added Version Fixed In||3.80.0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403966] Program always starts in privileges-less mode on wayland
https://bugs.kde.org/show_bug.cgi?id=403966 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Andrius Štikonas --- (In reply to mthw0 from comment #0) > Starting partition manager with QT_QPA_PLATFORM=wayland fixes this, so why > doesn't start like this by default? Also when run with the command above the > cursor is wrong and the program is unstable, so I wouldn't trust it doing > anything with my partitions. > > KDE Plasma Version: 5.14.90 > KDE Frameworks Version: 5.54 > Qt Version: 5.12.1 > > ADDITIONAL INFORMATION > Only on wayland I don't think cursor is wrong. It uses the cursor that is defined in user's settings (which is root). As for QT_QPA_PLATFORM=wayland, partitionmanager 3.3 only depends on Qt 5.10 but new Plasma releases don't set QT_QPA_PLATFORM when Qt is 5.11 or newer. Anyway, the points above become moot with latest beta version of kpmcore/partitionmanager 4.0 since the GUI no longer runs as root. Since you are running beta version of Plasma desktop, you can try beta version of KDE Partition Manager too. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403927] KDE Partition Manager crashes if I click the X during partition scanning
https://bugs.kde.org/show_bug.cgi?id=403927 Andrius Štikonas changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Andrius Štikonas --- *** This bug has been marked as a duplicate of bug 393275 *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 393275] Crash after dismissing "Scanning devices..." and closing KPM
https://bugs.kde.org/show_bug.cgi?id=393275 Andrius Štikonas changed: What|Removed |Added CC||jyn...@gmail.com --- Comment #9 from Andrius Štikonas --- *** Bug 403927 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 --- Comment #11 from Andrius Štikonas --- Created attachment 117710 --> https://bugs.kde.org/attachment.cgi?id=117710=edit wayland.patch Perhaps something like this to start with. It still doesn't embed window on Wayland but at least it shows it in the external window. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 377911] [Wayland] RDP doesn't work under Wayland
https://bugs.kde.org/show_bug.cgi?id=377911 Andrius Štikonas changed: What|Removed |Added CC||stiko...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 401031] Font thumbnailer crashes on Wayland
https://bugs.kde.org/show_bug.cgi?id=401031 Andrius Štikonas changed: What|Removed |Added CC||stiko...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403439] Partition manager doesn't use desktop theme
https://bugs.kde.org/show_bug.cgi?id=403439 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Andrius Štikonas --- You need to set theme of root user in 3.3. Next version of KDE Partition Manager does not run as root, so user theme is used. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Buffer age is broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=387313 Andrius Štikonas changed: What|Removed |Added CC||stiko...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 403222] KDE Partition Manager is using device name's for fstab entries instead of uuids.
https://bugs.kde.org/show_bug.cgi?id=403222 --- Comment #1 from Andrius Štikonas --- > Uuid is used to define the partition in the fstab Have you selected UUID in combobox? It should use whathever you tell it to... (path, label, uuid, GPT partition label, GPT partition UUID) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403179] Compositor (System Settings Module) window is open upon login
https://bugs.kde.org/show_bug.cgi?id=403179 Andrius Štikonas changed: What|Removed |Added Ever confirmed|0 |1 Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Andrius Štikonas --- Happens independently of that setting. I reproduced it even with start with an empty session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403179] Compositor (System Settings Module) window is open upon login
https://bugs.kde.org/show_bug.cgi?id=403179 Andrius Štikonas changed: What|Removed |Added CC||stiko...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 392892] kde partition manager unable to recognize bitlocker partition
https://bugs.kde.org/show_bug.cgi?id=392892 --- Comment #14 from Andrius Štikonas --- Git commit e749b01b8e85415a437eaf1043d64d6e52d96ae0 by Andrius Štikonas. Committed on 13/01/2019 at 13:16. Pushed by stikonas into branch 'master'. Fix a typo in filesystem support dialog. BitLocker was mixed up with btrfs. M +1-1src/fs/filesystemfactory.cpp https://invent.kde.org/kde/kpmcore/commit/e749b01b8e85415a437eaf1043d64d6e52d96ae0 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 392892] kde partition manager unable to recognize bitlocker partition
https://bugs.kde.org/show_bug.cgi?id=392892 Andrius Štikonas changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/kde/ ||partitionmanager/commit/6f1 ||ca2cca9cabfe8714db74ea0436c ||20e9732d43 --- Comment #13 from Andrius Štikonas --- Git commit 6f1ca2cca9cabfe8714db74ea0436c20e9732d43 by Andrius Štikonas. Committed on 13/01/2019 at 02:39. Pushed by stikonas into branch 'master'. Add BitLocker support. M +29 -0src/config/configurepagefilesystemcolors.ui M +2-0src/partitionmanager.kcfg https://invent.kde.org/kde/partitionmanager/commit/6f1ca2cca9cabfe8714db74ea0436c20e9732d43 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 392892] kde partition manager unable to recognize bitlocker partition
https://bugs.kde.org/show_bug.cgi?id=392892 --- Comment #12 from Andrius Štikonas --- Git commit 708318a5ad0c3851d276672932f287264eeb31c6 by Andrius Štikonas. Committed on 13/01/2019 at 02:24. Pushed by stikonas into branch 'master'. Add BitLocker detection support. M +2-0src/fs/CMakeLists.txt A +30 -0src/fs/bitlocker.cpp [License: GPL (v3+)] A +61 -0src/fs/bitlocker.h [License: GPL (v3+)] M +4-2src/fs/filesystem.cpp M +1-0src/fs/filesystem.h M +3-0src/fs/filesystemfactory.cpp M +1-0src/plugins/sfdisk/sfdiskbackend.cpp https://invent.kde.org/kde/kpmcore/commit/708318a5ad0c3851d276672932f287264eeb31c6 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 348122] KDE Partition Manager ignores Hybrid MBR
https://bugs.kde.org/show_bug.cgi?id=348122 Andrius Štikonas changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #4 from Andrius Štikonas --- I tested it with partition manager from master (that uses sfdisk). It seems to preserve protective MBR. If it still does not work, please reopen this bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401912] Crash on adding GPS coordinates to multiple images (6.0.0beta3 Windows x64)
https://bugs.kde.org/show_bug.cgi?id=401912 --- Comment #5 from Andrius --- (In reply to caulier.gilles from comment #3) > Can you reproduce the dysfunction using the last digiKam 6.0.0-beta3 just > released ? > > https://www.digikam.org/news/2018-12-30-6.0.0-beta3_release_announcement/ I just added geolocation to about 500 images and the application did not crash... The only thing I have noticed is that digiKam regenerated thumbnails after I added GPS coordinates to the images. I am not sure why. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401912] Crash on adding GPS coordinates to multiple images (6.0.0beta3 Windows x64)
https://bugs.kde.org/show_bug.cgi?id=401912 --- Comment #4 from Andrius --- (In reply to caulier.gilles from comment #2) > Maik, > > Under Windows, we use now DrMinGW to get the crash backtrace automatically > in a dialog in this kind of situation (as under Linux in fact). > > There is no specific reason to run digiKam in GDB as well. The DrMinGW crash > handler must do the job instead. It's more simple for end users to report a > dysfunction. > > Andrius, do you see the crash handler dialog appear when application crash ? > If yes, all the relevant backtrace must be there. Just copy and paste the > contents in this file. > > Look like Krita application use also DrMinGW. The team provide a nice > documentation to get all debug information for developers : > > https://docs.krita.org/en/reference_manual/dr_minw_debugger.html > > Gilles Caulier Gilles, no the application crashes quietly and there is no DrMinGW window pops up. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 322917] Please allow mounting partitions
https://bugs.kde.org/show_bug.cgi?id=322917 Andrius Štikonas changed: What|Removed |Added CC||report...@mailna.biz --- Comment #1 from Andrius Štikonas --- *** Bug 402974 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 402974] partitionmanager does not allow to mount without saving to fstab
https://bugs.kde.org/show_bug.cgi?id=402974 Andrius Štikonas changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Andrius Štikonas --- *** This bug has been marked as a duplicate of bug 322917 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401964] Wrong datestamp video/mp4
https://bugs.kde.org/show_bug.cgi?id=401964 --- Comment #7 from Andrius --- (In reply to Maik Qualmann from comment #6) > Right, the Z stands for UTC. And we deliberately ignore it because of bug > reports. There are cameras that correctly encode the date/time in UTC, while > others do not. These will append a Z to the date string even if they store > locale time. We will not find a satisfactory solution here, in this case I > consider Exiftool as a reference. Since Exiftool has no information (UTC, Z) > we probably have a similar reason. You can adjust the digiKam timestamp with > the Time Adjust tool (deactivate all checkboxes). > > Maik Maik, thanks for your feedback. I hoped there will be some like 'if "Z" present then do "minus 7 hours"' but I guess it is more complicated than that. I can leave with manual adjustments. Looks like the way Android phones write the date stamp into video files changes over time too. Most of my videos are fine but the recent ones are all +7 hours. I guess I should report on Samsung Galaxy website. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401964] Wrong datestamp video/mp4
https://bugs.kde.org/show_bug.cgi?id=401964 --- Comment #5 from Andrius --- (In reply to Maik Qualmann from comment #4) > I have just watched under Windows 10, here only the file date is displayed, > which is the date for me today. As I said, digiKam and Exiftool read the > creation date from the video metadata in the file. And that is clearly 18:39. > > Maik Maik, Here is the output of Mediainfo: https://pastebin.com/eBbPepvw UTC 2018-11-23 18:39:59 exiftool: https://pastebin.com/JSL6EtYh 2018:11:23 18:39:59 I think exiftool always shows time in UTC... ffmpeg: https://pastebin.com/5KDmEBiJ 2018-11-23T18:39:59.00Z I think Z stands for UTC -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401964] Wrong datestamp video/mp4
https://bugs.kde.org/show_bug.cgi?id=401964 --- Comment #3 from Andrius --- (In reply to Maik Qualmann from comment #2) > DigiKam is not wrong and displays the correct date and time, which is stored > in the video (2018-11-23 6:39 PM (18:39).) Exiftool displays exactly the > same creation date. > > Maik Hi Maik This video definitely was taken at 11-39am. I checked its properties in Android and Windows 10 and both show 11-39am. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401964] Wrong datestamp video/mp4
https://bugs.kde.org/show_bug.cgi?id=401964 --- Comment #1 from Andrius --- Here is a sample: https://drive.google.com/file/d/1GyXBiejiOeamDGhPrTgFqIZC5UqlXIB-/view?usp=sharing The video was taken on 2018-11-23 at 11-39am digikam shows under the thumbnail: 2018-11-23 6:39PM Mod. 2018-11-23 11:39AM and in the right panel - caption - description: 2018-11-23 18:39:59 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401964] New: Wrong datestamp video/mp4
https://bugs.kde.org/show_bug.cgi?id=401964 Bug ID: 401964 Summary: Wrong datestamp video/mp4 Product: digikam Version: 6.0.0 Platform: Other OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Albums-Sort Assignee: digikam-bugs-n...@kde.org Reporter: aegor...@gmail.com Target Milestone: --- I have noticed that some of my MP4 videos files aren't sorted by date correctly still in digikam 6.0.0beta3. Looks like Date Modified and Date Taken might be mixed up. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 401912] New: Crash on adding GPS coordinates to multiple images (6.0.0beta3 Windows x64)
https://bugs.kde.org/show_bug.cgi?id=401912 Bug ID: 401912 Summary: Crash on adding GPS coordinates to multiple images (6.0.0beta3 Windows x64) Product: digikam Version: 6.0.0 Platform: Other OS: MS Windows Status: REPORTED Severity: crash Priority: NOR Component: Geolocation-Editor Assignee: digikam-bugs-n...@kde.org Reporter: aegor...@gmail.com Target Milestone: --- Created attachment 116797 --> https://bugs.kde.org/attachment.cgi?id=116797=edit logfile from DebugView digikam 6.0.0beta3 win_x64 just crashed on me three times in a row during applying GPS coordinates to multiple JPG+DNG images (more than 35 images). For your convenience I have attached a log from DebugView. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385289] Kmail: Crash when moving or deleting imap folder (Wayland)
https://bugs.kde.org/show_bug.cgi?id=385289 --- Comment #22 from Andrius Štikonas --- (In reply to Rainer Finke from comment #21) > With Kmail 5.9.2 drag and drop doesn't work anymore so for now at least > there is no crash of the application. For me it works with 5.9.3. And doesn't seem to crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #23 from Andrius Štikonas --- (In reply to Andrius Štikonas from comment #22) > After I booted with just laptop screen and blur was working, I plugged in my > external screen, this caused laptop screen to turn off. External screen had > no blur. > > So I think somehow blur is lost during output switching. And it doesn't > matter whether it happens during plasma boot or later. When booting with 2 screens on, blur works. So I think this confirms that something bad happens when output is switched off. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #22 from Andrius Štikonas --- After I booted with just laptop screen and blur was working, I plugged in my external screen, this caused laptop screen to turn off. External screen had no blur. So I think somehow blur is lost during output switching. And it doesn't matter whether it happens during plasma boot or later. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #21 from Andrius Štikonas --- (In reply to Vlad Zagorodniy from comment #20) > Hmm, given the debug output I don't see a reason why blur is not working. I did some more testing. The crucial thing seems to be that one output is disabled in my case (laptop monitor ies turned off in systemsettings, only external HDMI is used). When I booted with external screen unplugged, so laptop's screen was used, blur was enabled on boot without any further workarounds. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 398154] kpmcore starts external process dd
https://bugs.kde.org/show_bug.cgi?id=398154 Andrius Štikonas changed: What|Removed |Added Latest Commit|https://commits.kde.org/kpm |https://commits.kde.org/kpm |core/09e4d47e0711a800be858f |core/80f5a32dc04c4150d3b32c |dd6691f59838bc3003 |46526b6489f8fa853c --- Comment #4 from Andrius Štikonas --- Git commit 80f5a32dc04c4150d3b32c46526b6489f8fa853c by Andrius Štikonas. Committed on 29/11/2018 at 22:32. Pushed by stikonas into branch 'master'. Remove remaining cases of call to dd binary. M +1-1src/fs/fat12.cpp M +1-1src/fs/fat16.cpp M +1-4src/fs/ntfs.cpp M +1-1src/util/externalcommandhelper.cpp M +1-1src/util/externalcommandhelper.h https://commits.kde.org/kpmcore/80f5a32dc04c4150d3b32c46526b6489f8fa853c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #19 from Andrius Štikonas --- Created attachment 116560 --> https://bugs.kde.org/attachment.cgi?id=116560=edit WAYLAND_DEBUG=1 konsole -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #18 from Andrius Štikonas --- (In reply to Andrius Štikonas from comment #17) > Created attachment 116555 [details] > supportInformation > > So apparently in my case blur sometimes works but sometimes doesn't (e.g. > yesterday it was working, today it stopped). At the moment I'm not sure what > causes it to fail. Ok, some further debugging shows that blur is fixed when I uncheck it in system settings, apply settings, reenable blur and apply. Until next logout... So it's simply not enable on boot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #17 from Andrius Štikonas --- Created attachment 116555 --> https://bugs.kde.org/attachment.cgi?id=116555=edit supportInformation So apparently in my case blur sometimes works but sometimes doesn't (e.g. yesterday it was working, today it stopped). At the moment I'm not sure what causes it to fail. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392693] [wayland] - Blur effect isnt applied under wayland
https://bugs.kde.org/show_bug.cgi?id=392693 --- Comment #14 from Andrius Štikonas --- (In reply to Andrius Štikonas from comment #13) > Blur also doesn't work for me. I have background contrast effect enabled, > but on dual screen setup I have one screen completely disabled. To be more precise, in my case blur is sometimes not applied. E.g. everything under plasma bar is blured but when I move windows, blur is not applied. -- You are receiving this mail because: You are watching all bug changes.
