[neon] [Bug 482488] 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'."
https://bugs.kde.org/show_bug.cgi?id=482488 --- Comment #2 from Jos van den Oever --- Discover is installed and it is possible to install applications with it. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482488] 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'."
https://bugs.kde.org/show_bug.cgi?id=482488 --- Comment #1 from Jos van den Oever --- Created attachment 166435 --> https://bugs.kde.org/attachment.cgi?id=166435=edit screenshot of the trigger and the dialog -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482488] New: 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'."
https://bugs.kde.org/show_bug.cgi?id=482488 Bug ID: 482488 Summary: 'Get $application... buttons in launcher give error: "Unable to create KIO worker: Unknown protocol 'appstream'." Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: j...@vandenoever.info CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Installing an application from the launch menu does not work. An error dialog is shown. STEPS TO REPRODUCE 1. Install Neon from neon-user-20240304-2101.iso 2. Log into Plasma 6 3. In the application laucher type an application name e.g. 'Libreoffice Calc' and click on 'Get LibreOffice Calc...' OBSERVED RESULT A dialog is shown with the text Unable to create KIO worker: Unknown protocol 'appstream'. and only an 'Ok' button. EXPECTED RESULT The desired application is installed or a window is shown from where the application can be installed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482283] Installation in VM gives an error: "Bad main script file"
https://bugs.kde.org/show_bug.cgi?id=482283 Jos van den Oever changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Jos van den Oever --- I confirm that installation with neon-user-20240304-2101.iso works without issue. The installer finishes and boots into Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482283] Installation in VM gives an error: "Bad main script file"
https://bugs.kde.org/show_bug.cgi?id=482283 --- Comment #3 from Jos van den Oever --- I confirm that my error looked that same as in Sharath's screenshot. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482283] Installation in VM gives an error: "Bad main script file"
https://bugs.kde.org/show_bug.cgi?id=482283 --- Comment #1 from Jos van den Oever --- In /tmp there are a number of calamares-* diretories. All of them are empty. Only one is very large: calamares-root-*. No log could be found. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482283] New: Installation in VM gives an error: "Bad main script file"
https://bugs.kde.org/show_bug.cgi?id=482283 Bug ID: 482283 Summary: Installation in VM gives an error: "Bad main script file" Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Live/Install images Assignee: neon-b...@kde.org Reporter: j...@vandenoever.info CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Running neon-user-20240303-0009.iso in a QEmu VM on a x86_64 laptop fails during installation. STEPS TO REPRODUCE 1. download neon-user-20240303-0009.iso from neon.kde.org 2. boot the iso in a vm 3. start "Install system" 4 choose timezone Amsterdam, English language, Dutch locale 5. choose to erase the entire disk (55GB) 6. continue to the installation and show the logs 6.1 disk is being partitioned 6.2 rsync is run to copy files OBSERVED RESULT A dialog pops up: "Main script file /usr/lib/x86_64-linux-gnu/calamares/modules/networkcfg/main.py for python job networkcfg raised an exception. The network in the VM is a wired connection. Browsing the web with Firefox works from the live image. EXPECTED RESULT The installation of KDE Neon completes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471819] kwin hangs when there is no render node e.g. in qemu
https://bugs.kde.org/show_bug.cgi?id=471819 --- Comment #2 from Jos van den Oever --- I tried again today with kwin_wayland for kf5 and kf6 compiled from today's git repositories. weston works fine in the same setup, but kwin_wayland from kf5 gives this output: ``` No backend specified, automatically choosing drm pci id for fd 19: 1234:, driver (null) MESA-LOADER: failed to open bochs-drm: /run/opengl-driver/lib/dri/bochs-drm_dri.so: cannot open shared object file: No such file or directory (search paths /run/opengl-driver/lib/dri, suffix _dri) pci id for fd 17: 1234:, driver (null) kmsro: driver missing OpenGL vendor string: Mesa OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits) OpenGL version string: 4.5 (Core Profile) Mesa 23.0.3 OpenGL shading language version string: 4.50 Driver: LLVMpipe GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 23.0.3 Linux kernel version: 6.1.31 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_wayland_drm: Failed to create gamma blob! Invalid argument ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471819] New: kwin hangs when there is no render node e.g. in qemu
https://bugs.kde.org/show_bug.cgi?id=471819 Bug ID: 471819 Summary: kwin hangs when there is no render node e.g. in qemu Classification: Plasma Product: kwin Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- SUMMARY When there is no render node in kwin_wayland, no rendering is done. In QEmu, when no opengl is available the rendering falls back to a primary node: `kwin_scene_opengl: No render nodes have been found, falling back to primary node` kwin continues executing, but freezes at some point without rendering anything. A solution might be to have an early check for that and automatically fall back to CPU rendering if there are not any render nodes. STEPS TO REPRODUCE 1. install kwin in a qemu image and 2. start kwin OBSERVED RESULT kwin hangs without showing any input. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: master kwin: b23d707e0cc12156b0eb9613bb791365d1217f25 (available in About System) KDE Plasma Version: master KDE Frameworks Version: master Qt Version: 6.5 ADDITIONAL INFORMATION I ran this in qemu with ``` nixos-rebuild build-vm --flake 'git+https://invent.kde.org/vandenoever/kde-nix-flake/?ref=kf6-qt6=44a978ee14f0f776113369780dca10fecd7d3629#test-x86_64-linux' result/bin/run-nixos-vm ``` This boots a qemu with a recent (~2023-06-20) git version of KDE software. When booted, kwin_wayland is started from a user account (user tester, pwd test) ``` qt.dbus.integration: Could not connect "org.freedesktop.login1.Session" to handleResumeDevice(uint, uint, QDBusUnixFileDescriptor) pci id for fd 17: 1234:, driver (null) MESA-LOADER: failed to open bochs-drm: /run/opengl-driver/lib/dri/bochs-drm_dri.so: cannot open shared object file: No such file or directory (search paths /run/opengl-driver/lib/dri, suffix _dri) pci id for fd 18: 1234:, driver (null) kmsro: driver missing OpenGL vendor string: Mesa OpenGL renderer string: llvmpipe (LLVM 15.0.7, 256 bits) OpenGL version string: 4.5 (Core Profile) Mesa 23.0.3 OpenGL shading language version string: 4.50 Driver: LLVMpipe GPU class: Unknown OpenGL version: 4.5 GLSL version: 4.50 Mesa version: 23.0.3 Linux kernel version: 6.1.31 Requires strict binding:no GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no kwin_scene_opengl: No render nodes have been found, falling back to primary node kwin_core: kwin-dmabuf-feedback-table: mmap failed: Invalid argument kwin_core: Failed to create RamFile for LinuxDmaBufV1FormatTable kwin_wayland_drm: DPMS has unrecognized enum 'On' kwin_wayland_drm: DPMS has unrecognized enum 'Standby' kwin_wayland_drm: DPMS has unrecognized enum 'Suspend' kwin_wayland_drm: DPMS has unrecognized enum 'Off' gbm_bo_get_fd_for_plane() failed: Function not implemented kwin_wayland_drm: Checking test buffer failed for (1) kwin_wayland_drm: Failed to find a working setup for new outputs! gbm_bo_get_fd_for_plane() failed: Function not implemented kwin_wayland_drm: Checking test buffer failed for (1) kwin_core: Applying output config failed! kf.coreaddons: The plugin "/nix/store/zdmvxgsb36biv1lrs4jg13vvyzs6lvac-kwin-6-20230626gitb23d707/lib/qt-6/plugins/kwin/plugins/StickyKeysPlugin.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed error marshalling arguments for format_table: dup failed: Bad file descriptor error in client communication (pid 1201) qt.qpa.wayland: Creating a fake screen in order for Qt not to crash kf.package: Invalid metadata for package structure "Plasma/Wallpaper" kf.package: Invalid metadata for package structure "Plasma/LookAndFeel" kscreenlocker_greet: Lockscreen QML outdated, falling back to default kf.package: Cannot set a path in a package without structure "org.kde.breeze.desktop" kf.package: Cannot set a path in a package without structure "org.kde.image" ``` -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa
https://bugs.kde.org/show_bug.cgi?id=409587 --- Comment #10 from Jos van den Oever --- Created attachment 159802 --> https://bugs.kde.org/attachment.cgi?id=159802=edit Script to show the number of watches per application -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa
https://bugs.kde.org/show_bug.cgi?id=409587 --- Comment #9 from Jos van den Oever --- Created attachment 159801 --> https://bugs.kde.org/attachment.cgi?id=159801=edit Dialog for increasing the number of watches -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa
https://bugs.kde.org/show_bug.cgi?id=409587 --- Comment #8 from Jos van den Oever --- Created attachment 159800 --> https://bugs.kde.org/attachment.cgi?id=159800=edit popup about the need for more watches -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 409587] Many inotify_add_watch errors starting Elisa
https://bugs.kde.org/show_bug.cgi?id=409587 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #7 from Jos van den Oever --- I can confirm this issue. I happens every time when elisa is run. ``` Inotify Watch Capacity Low Your open applications want to watch too many files for changes! When the capacity is exhausted it will prevent further file monitoring from working correctly. Either close some applications or increase the limit. Currently using 25% of instances and 98% of watches. Increase Watch Limit ``` Increasing the limit via the dialog (see attachments) helps to solve the problem. With `inotify-consumers` it is possible to list the applications that use inotify. Elisa uses over 100k monitors and the number keeps increasing. ``` $ bash /tmp/inotify-consumers INOTIFY INSTANCES WATCHES PER COUNT PROCESS PID USER COMMAND 115295 5 2102749 nlnet /nix/store/3wvgmnm5rkqii79arggmvnda25ahqwcq-elisa-23.04.1/bin/elisa 202 1 1954876 nlnet /run/current-system/sw/bin/kded5 126 2 1954922 nlnet /nix/store/d5dv3b5r919hvknf248xvw6rwa5ggbf1-plasma-workspace-5.27.5/bin/plasmashell 117 3 1955567 nlnet /nix/store/3igqa8akmyswkanm6vpk11if4fiqrji8-firefox-113.0.2/bin/.firefox-wrapped --name firefox 114 1 1955198 nlnet /nix/store/cm63hmpc7976x74f344bbg7pa7grj0i6-thunderbird-102.10.1/bin/.thunderbird-wrapped --name thunderbird 19 1 2065953 nlnet /nix/store/0wyqlfsi1gpnqbvy9pkmlbz91vbly65r-rust-analyzer-unwrapped-2022-10-31/bin/rust-analyzer 18 3 392486 nlnet /nix/store/75wxj2a3c0pdbf46bzmff8qr9vbjm5y1-systemd-253.3/lib/systemd/systemd --user 8 1 392718 nlnet /nix/store/w2rxmc5wqlw28r23rrsvl1qwxq3qlhra-dbus-1.14.6/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 8 1 1954664 nlnet dbus-daemon --nofork --print-address 4 --session 4 1 1954967 nlnet /nix/store/pil9rmdpn1j73j21bbcx60pgcanv30zh-kactivitymanagerd-5.27.5/libexec/kactivitymanagerd 3 3 1945296 nlnet /nix/store/3a566gibjcsrmi0pbdndqpfdpv37wh6a-wireplumber-0.4.14/bin/wireplumber 2 2 410389 nlnet gpg-agent --homedir /home/nlnet/.gnupg --use-standard-socket --daemon 2 1 1954928 nlnet /nix/store/2nhjxk2jcxp6z64iv9r1yxpbafajpjc7-powerdevil-5.27.5/libexec/org_kde_powerdevil 1 1 2037433 nlnet /home/nlnet/.nix-profile/bin/konsole 1 1 2035949 nlnet /nix/store/v7qc7q2w1ji5v0a4gyrh36bm1vxqqvz0-kwallet-5.106.0-bin/bin/kwalletd5 1 1 1954954 nlnet /run/current-system/sw/bin/gmenudbusmenuproxy 1 1 1954704 nlnet /nix/store/dvwkf9i5vyffqs6bn001ili2f94nrqx8-xdg-desktop-portal-1.16.0/libexec/xdg-desktop-portal 115922 WATCHES TOTAL COUNT INotify instances per user (e.g. limits specified by fs.inotify.max_user_instances): INSTANCESUSER --- -- 29 nlnet ``` Elisa uses 100% CPU while setting all these watches. After running for a few minutes, the watch capacity needs to be increased again. At this point the number of watches is 123674. Increasing the limit more does not create more watches. The limit is at 124304 (`cat /proc/sys/fs/inotify/max_user_watches`). Since elisa has taken all the available inotify watches, other applications cannot set any watches. Closing elisa frees up the watches. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462105] New: copy from the history with keyboard
https://bugs.kde.org/show_bug.cgi?id=462105 Bug ID: 462105 Summary: copy from the history with keyboard Classification: Applications Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: history Assignee: konsole-de...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- Konsole has a history. A very common action is to select text with the mouse and copy it into a new command or command-line application. The applications screen and emacs offer ways to select text from the terminal history with the keyboard instead of the mouse. It would be great to have selection mode where a user can select a line, work or file path with just the keyboard. Version 22.08.3 of Konsole does not have such a feature. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 --- Comment #9 from Jos van den Oever --- The issue happened again on two machines. Removing the files `~/.local/share/akonadi/db_data/ib_logfile*` solved the issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 425131] After crashing, akonadi cannot start up and cannot recover itself
https://bugs.kde.org/show_bug.cgi?id=425131 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #8 from Jos van den Oever --- This bug has happened on a laptop I maintain as well. The file `~/.local/share/akonadi/db_data/mysql.err` reported that InnoDB missed MLOG_CHECKPOINT between another checkpoint and the end. The database would not start because of this. The user had no feedback. All they could see was a message in KMail that akonadi would not start. Removing the files `~/.local/share/akonadi/db_data/ib_logfile*` solved the issue. Perhaps a solution might be to let akonadictl make a backup of the db_data directory and then remove the ib_logfiles and retry starting up. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455713] New: slider for feedback level does not fit on screen
https://bugs.kde.org/show_bug.cgi?id=455713 Bug ID: 455713 Summary: slider for feedback level does not fit on screen Product: systemsettings Version: 5.25.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_feedback Assignee: aleix...@kde.org Reporter: j...@vandenoever.info CC: plasma-b...@kde.org Target Milestone: --- Created attachment 150004 --> https://bugs.kde.org/attachment.cgi?id=150004=edit screenshot of the User Feedback screen in System Settings SUMMARY The slider for the level of user feedback reporting does not fit on the screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: PostmarketOS edge Device: Pinephone KDE Plasma Version: 5.25.0 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452492] external screen brightness is not restored after wakeup
https://bugs.kde.org/show_bug.cgi?id=452492 --- Comment #1 from Jos van den Oever --- The monitor is visible like this: ``` $ ddcutil detect Display 1 I2C bus: /dev/i2c-9 EDID synopsis: Mfg id: GSM Model:LG HDR 4K Product code: 30471 Serial number: Binary serial number: [..] Manufacture year: [..] VCP version: 2.1 ``` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 452492] New: external screen brightness is not restored after wakeup
https://bugs.kde.org/show_bug.cgi?id=452492 Bug ID: 452492 Summary: external screen brightness is not restored after wakeup Product: kwin Version: 5.24.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- Flags: Wayland+, Intel+ SUMMARY *** When the external monitor is set to turn off after a certain time of no activity, the brightness is not fully restored after wakeup. The brightness can be fixed with the the keyboard brightness buttons or with `ddcutil setvsp 10 + 65535`. *** STEPS TO REPRODUCE 1. run wayland session with dbus-run-session startplasma-wayland 2. set 'Screen energy savings' to 'Switch off after 3 min', press 'Apply' 3. wait 3 minutes until screen turns off 4. awaken screen by doing user input on keyboard OBSERVED RESULT The external monitor is on lowest brightness setting. EXPECTED RESULT The external monitor is on the same brightness as before it went to sleep. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.3 Linux Kernel: 5.15.30 Graphics platform: Wayland ADDITIONAL INFORMATION The graphics is embedded Intel graphics UHD Graphics 620. The monitor is LG connected via USB-C for display and power to the laptop. The laptop screen and the external monitor are active. Only the laptop monitor is restored to the initial brightness. Related bug: https://bugs.kde.org/show_bug.cgi?id=423457 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450378] Per window scaling with shift-drag on window border
https://bugs.kde.org/show_bug.cgi?id=450378 --- Comment #3 from Jos van den Oever --- The linked Wayland protocol issue (47) has suggestions for adding per window scaling via additions such as `wanted_scale`, `set_client_scale`, `setting_client_scale`. Since the current method of scaling is blurry and resource intensive I hope that these additions will be picked up soon. E.g. if you have a 4k display with 1.25 scaling, the current scaling method on Wayland would give a 6144x3456 (4k / 1.25 * 2) buffer to a fullscreen application such as the always-present desktop background. That is a buffer that is 2.56x as large as a 4k buffer. Not fun. So Wayland has a big incentive to fix 47. The proposed additions could be used to implement this scale-by-dragging feature. Or vice-versa, this feature request could be one more reason to have those Wayland additions. Scaling windows up and down by dragging makes for wonderfully visual demo material besides simply being very handy. Perhaps it's easier to first implement it on X11. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450378] Per window scaling with shift-drag on window border
https://bugs.kde.org/show_bug.cgi?id=450378 --- Comment #1 from Jos van den Oever --- Related issues: https://bugs.kde.org/show_bug.cgi?id=227284 also request per-window scaling as an accessibility feature. https://bugs.kde.org/show_bug.cgi?id=446674 and https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/47 discuss how fractional scaling would improve crispiness and decrease graphical buffer size on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450378] New: Per window scaling with shift-drag on window border
https://bugs.kde.org/show_bug.cgi?id=450378 Bug ID: 450378 Summary: Per window scaling with shift-drag on window border Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- It would be nice to set a scaling factor per window. No other desktop supports this but it could be very intuitive, like resizing pictures on a canvas. Using shift-drag on window borders could be the way to change the scale factor. Currently resizing windows, changes their layout. UI elements might appear or get hidden. This can be frustrating. Also, some windows cannot deal with small resolution screens which makes parts of the window inaccessible. In such cases, doing shift-drag on the window border to zoom in or out would be a convenient and intuitive way to adjust the window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446674] In Wayland with fractional scaling fonts and images are blurry from downscaling
https://bugs.kde.org/show_bug.cgi?id=446674 --- Comment #3 from Jos van den Oever --- To support the proposal for fractional scaling, Qt applications need to be able to change their scaling at runtime. Scaling of applications is explained in <https://doc.qt.io/qt-5/highdpi.html> and <https://doc.qt.io/qt-6/highdpi.html>. On Windows, the setting 'Per-Monitor DPI Aware' seems close to what this proposal needs. The applications gets a buffer corresponding the the actual pixels on the screen and also a scaling factor at which the UI should be rendered. A dynamic scale factor per window would be fantastic. There could be a 'zoom resize' (shift + drag border) where the aspect ratio and layout would stay the same, but the fonts and icons got larger or smaller. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 446674] In Wayland with fractional scaling fonts and images are blurry from downscaling
https://bugs.kde.org/show_bug.cgi?id=446674 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.
https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #10 from Jos van den Oever --- And yes to 0.4.0 in case of merge indeed. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.
https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #9 from Jos van den Oever --- Yes, the resulting master should be as much functional as the current one. I'll have a look this week to see what the means. I've two projects I'd like to test with these changes, one public (mailmodel) and one private. Commit squashing is not something I've a strong opinion on. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.
https://bugs.kde.org/show_bug.cgi?id=448087 --- Comment #5 from Jos van den Oever --- That all seems a sensible. The code was originally written when I was less familiar with rust's rules. The rust_by_function as the only way to get data is more verbose in implementation.rs and might have performance overhead, but the binding to a GUI is not the place to worry about that. What would the RefCell code look like? I'm asking because I'm modifying a model from multiple threads, so a Mutex might be more appropriate. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 406178] Mutability of Rust objects
https://bugs.kde.org/show_bug.cgi?id=406178 Jos van den Oever changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Jos van den Oever --- Your analysis is correct. Going to '' instead of ' mut' is the way to go. Do you want to make a merge request from your ro branch? -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 448087] rust-qt-binding-generator: Undefined Behaviour: One can obtain a mutable reference to a Rust struct from an immutable reference.
https://bugs.kde.org/show_bug.cgi?id=448087 Jos van den Oever changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Jos van den Oever --- I agree with the analysis. This is a fundamental problem that I did not realize before. One can get rid of the undefined behavior by changing all ' self' to '' in the interface and leave the problem for the implementer. (This is also what kdebuac.rhn describes in https://bugs.kde.org/show_bug.cgi?id=406178 ) They might then use a Mutex. That would then lead to a deadlock instead of undefined behavior. The idea of a QueuedConnection would not solve the problem general problem. One would need to guarantee that any code that calls into C++ does not call back in Rust. The only safe way is to have only immutable references. The read-only experimental branch might be the solution: https://gitlab.com/rhn/rust-qt-bindings-generator/-/commits/simplify_ro -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 445879] Support some of the built-in Qt types, when exposing them to Rust
https://bugs.kde.org/show_bug.cgi?id=445879 Jos van den Oever changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Jos van den Oever --- Calling QML code from Rust is out of scope. The design of RQBG is such that you can crate a data model in Rust, but the Rust does not know about the QML code. You can trigger functions in the QML by binding to property states. Calling QML from Rust is out of scope for the current design. However, if you have ideas for doing this is in a safe and simple way, I might add it. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 445878] Support generating and emitting custom signals
https://bugs.kde.org/show_bug.cgi?id=445878 --- Comment #1 from Jos van den Oever --- You can currently emit signals by modifying properties. So the machinery for emitting signals is there. If I understand correctly, you would like to have a way to specify signals in the bindings json file that generates rust functions for emitting other signals. When signals are tied to properties, it's convenient in QML to tie the state to something in the UI. For signals that are not tied to any property, the update would only have temporary information. To use that information later, you'd then need to store that information in a QML property. Can you explain your use-case? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 401050] kmail mailto invokation fails if akonadi is loaded
https://bugs.kde.org/show_bug.cgi?id=401050 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #1 from Jos van den Oever --- On NixOS 20.09 with KMail version 5.16.3 (20.12.3) this bug is not present. The compose window opens when running kmail -qwindowtitle KMail mailto:847...@bugs.debian.org even when kmail and akonadi were not running. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 206269] mailto links only read up to first hash (#) symbol
https://bugs.kde.org/show_bug.cgi?id=206269 Jos van den Oever changed: What|Removed |Added Product|konqueror |kmail2 Version|SVN |5.16.3 Assignee|konq-b...@kde.org |kdepim-b...@kde.org Component|khtml |general --- Comment #6 from Jos van den Oever --- Assigning back to KMail because a comment points out that the bug is there with an easy way to reproduce the problem. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 206269] mailto links only read up to first hash (#) symbol
https://bugs.kde.org/show_bug.cgi?id=206269 --- Comment #5 from Jos van den Oever --- This bug is still present in KMail version 5.16.3 (20.12.3) I tested with the command from Comment 3. https://bugs.kde.org/show_bug.cgi?id=206269#c3 -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 190698] rotating svg cube (javascript) does not work in konqueror
https://bugs.kde.org/show_bug.cgi?id=190698 Jos van den Oever changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Jos van den Oever --- This now works with konqueror 20.08.2. qsvgviewer is not packaged by my distribution any more. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406261] Kmail2 crashes when accepting meeting invitation
https://bugs.kde.org/show_bug.cgi?id=406261 Jos van den Oever changed: What|Removed |Added Version|5.10.3 |5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 406261] Kmail2 crashes when accepting meeting invitation
https://bugs.kde.org/show_bug.cgi?id=406261 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #1 from Jos van den Oever --- I can confirm this crash with KMail version 5.15.2 (20.08.2) #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7fab13207528 in __GI_abort () at abort.c:79 #2 0x7fab135a1693 in ?? () from /nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6 #3 0x7fab135acf06 in ?? () from /nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6 #4 0x7fab135acf71 in std::terminate() () from /nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6 #5 0x7fab135ad1c4 in __cxa_throw () from /nix/store/hxs99j1kx878pxxw5lbdarml69r5f1qb-gcc-9.3.0-lib/lib/libstdc++.so.6 #6 0x7fab115b6ebd in Akonadi::Item::throwPayloadException(int, int) const [clone .cold] () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #7 0x7fab11636b7f in std::enable_if::isPolymorphic, QByteArray>::type Akonadi::Item::payloadImpl() const () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #8 0x7fab11634fc9 in non-virtual thunk to Akonadi::DefaultItemSerializerPlugin::serialize(Akonadi::Item const&, QByteArray const&, QIODevice&, int&) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #9 0x7fab1163483b in Akonadi::ItemSerializer::serialize(Akonadi::Item const&, QByteArray const&, QIODevice&, int&) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #10 0x7fab11635409 in Akonadi::ItemSerializer::serialize(Akonadi::Item const&, QByteArray const&, QByteArray&, int&) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #11 0x7fab116b8460 in Akonadi::ItemCreateJobPrivate::preparePart(QByteArray const&) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #12 0x7fab116b88f0 in Akonadi::ItemCreateJob::doHandleResponse(long long, QSharedPointer const&) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #13 0x7fab116c9430 in Akonadi::JobPrivate::handleResponse(long long, QSharedPointer const&) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #14 0x7fab11681f10 in Akonadi::SessionPrivate::handleCommands() () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #15 0x7fab1167eb60 in Akonadi::Session::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /nix/store/wfi2sdx331gj636qrhhfhx3fbvhrlwp3-akonadi-20.08.2/lib/libKF5AkonadiCore.so.5 #16 0x7fab139cec99 in QObject::event(QEvent*) () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core.so.5 #17 0x7fab146bed7f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Widgets.so.5 #18 0x7fab146c7a10 in QApplication::notify(QObject*, QEvent*) () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Widgets.so.5 #19 0x7fab139a1d8a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core.so.5 #20 0x7fab139a46b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core.so.5 #21 0x7fab139fb713 in ?? () from /nix/store/9fmvcacvkj6s65j3l5pf96nbqwjp73wb-qtbase-5.15.2/lib/libQt5Core -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 206269] mailto links only read up to first hash (#) symbol
https://bugs.kde.org/show_bug.cgi?id=206269 --- Comment #4 from Jos van den Oever --- This happens in KMail Version 5.15.2 (20.08.2) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 206269] mailto links only read up to first hash (#) symbol
https://bugs.kde.org/show_bug.cgi?id=206269 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #3 from Jos van den Oever --- An escaping problem also occurs with '&' in subject or body. kmail 'mailto:t...@example.com?subject=A%26B=D%26C' gives Subject: A Body: D= but it should be: Subject: A Body: D -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list
https://bugs.kde.org/show_bug.cgi?id=395192 Jos van den Oever changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 423280] rust-qt-binding-generator templates fail to build with mingw64
https://bugs.kde.org/show_bug.cgi?id=423280 --- Comment #2 from Jos van den Oever --- If you have a patch, I can consider it. I do not have a windows system to test on. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 420449] add support for saving as (lossless) webp
https://bugs.kde.org/show_bug.cgi?id=420449 --- Comment #3 from Jos van den Oever --- After installing the Qt image plugins, spectacle can save as webp. Very nice! When I save images with webp 100% quality the files are much smaller than when saving with 99% quality. E.g. a screenshot of a browser is 366K when saving at 99% quality and 197K when saving at 100% quality. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 420449] add support for saving as (lossless) webp
https://bugs.kde.org/show_bug.cgi?id=420449 --- Comment #2 from Jos van den Oever --- That's great to hear. I've plugins/imageformats/libqwebp.so on my machine but do not see an option to save to webp or set it as a default format. Is there an option to save losslessly? webp can save lossy and losslessly and often for screenshots the lossless version is smaller as well as more accurate. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 420449] New: add support for saving as (lossless) webp
https://bugs.kde.org/show_bug.cgi?id=420449 Bug ID: 420449 Summary: add support for saving as (lossless) webp Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: j...@vandenoever.info CC: k...@david-redondo.de Target Milestone: --- SUMMARY Files saved by spectacle can be quite large. Using oxipng or optipng can often shave 30% of the size in a fraction of a second. oxipng /tmp/Screenshot_20200423_111228.png Processing: /tmp/Screenshot_20200423_111228.png 1411x1217 pixels, PNG format 4x8 bits/pixel, RGBA IDAT size = 285460 bytes File size = 285946 bytes Trying: 8 combinations Found better combination: zc = 9 zs = 0 f = 0203982 bytes IDAT size = 203982 bytes (81478 bytes decrease) file size = 204060 bytes (81886 bytes = 28.64% decrease) Output: /tmp/Screenshot_20200423_111228.png Even more space can be saved by saving as lossless webp. Webp is supported in all new browsers. Making it the default is perhaps a bit early, but it would be nice if spectable would remember the preference for webp. STEPS TO REPRODUCE $ cwebp -lossless /tmp/Screenshot_20200423_111228.png -o /tmp/Screenshot_20200423_111228.webp Saving file '/tmp/Screenshot_20200423_111228.webp' File: /tmp/Screenshot_20200423_111228.png Dimension: 1411 x 1217 Output:92618 bytes (0.43 bpp) Lossless-ARGB compressed size: 92618 bytes * Header size: 2129 bytes, image data size: 90463 * Lossless features used: SUBTRACT-GREEN * Precision Bits: histogram=5 transform=5 cache=10 OBSERVED RESULT $ ls -l /tmp/Screenshot_20200423_111228.* 285946 23 apr 11:12 /tmp/Screenshot_20200423_111228.png 92618 23 apr 11:13 /tmp/Screenshot_20200423_111228.web SOFTWARE/OS VERSIONS Linux/KDE Plasma: 19.12 (available in About System) KDE Plasma Version: 19.12 KDE Frameworks Version: 5.66 Qt Version: 5.12.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 415915] Upgrading serde-xml-rs from 0.2 to 0.3.1
https://bugs.kde.org/show_bug.cgi?id=415915 Jos van den Oever changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Jos van den Oever --- This is fixed in 4d393706b84a3c2852ece2689366811a0fc02207. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379763] plasmashell settings windows show plasma background
https://bugs.kde.org/show_bug.cgi?id=379763 --- Comment #5 from Jos van den Oever --- In the past I did not find a way to reproduce this issue which happened occasionally. I've not experienced the issue for a long time. I'm still using X11 but have upgraded tot plasma 5.16. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407163] compilation fails due to wrong include statement
https://bugs.kde.org/show_bug.cgi?id=407163 --- Comment #5 from Jos van den Oever --- If you have proposed or applied patch for mailcommon/src/CMakeLists.txt, I can test it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406829] kwin_x11 crashes on alt-tab
https://bugs.kde.org/show_bug.cgi?id=406829 Jos van den Oever changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME --- Comment #2 from Jos van den Oever --- After upgrading Qt from 5.12.0 to 5.12.3, the bug was gone. Setting to WORKSFORME because I do not know what fixed it. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 407163] compilation fails due to wrong include statement
https://bugs.kde.org/show_bug.cgi?id=407163
--- Comment #1 from Jos van den Oever ---
This patch to kmail solves the issue (and one other similar issue):
diff --git a/agents/archivemailagent/CMakeLists.txt
b/agents/archivemailagent/CMakeLists.txt
index 48ed076..9c56896 100644
--- a/agents/archivemailagent/CMakeLists.txt
+++ b/agents/archivemailagent/CMakeLists.txt
@@ -22,6 +22,7 @@ ki18n_wrap_ui(libarchivemailagent_SRCS
ui/archivemailwidget.ui )
add_library(archivemailagent STATIC ${libarchivemailagent_SRCS})
target_link_libraries(archivemailagent
KF5::MailCommon
+KF5::Libkdepim
KF5::I18n
KF5::Notifications
KF5::IconThemes
diff --git a/agents/followupreminderagent/CMakeLists.txt
b/agents/followupreminderagent/CMakeLists.txt
index a56b730..83604cf 100644
--- a/agents/followupreminderagent/CMakeLists.txt
+++ b/agents/followupreminderagent/CMakeLists.txt
@@ -23,6 +23,7 @@ target_link_libraries(followupreminderagent
KF5::AkonadiMime
KF5::AkonadiAgentBase
KF5::DBusAddons
+KF5::FollowupReminder
KF5::XmlGui
KF5::KIOWidgets
KF5::Notifications
--
You are receiving this mail because:
You are watching all bug changes.
[kmail2] [Bug 407163] New: compilation fails due to wrong include statement
https://bugs.kde.org/show_bug.cgi?id=407163 Bug ID: 407163 Summary: compilation fails due to wrong include statement Product: kmail2 Version: 5.11.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- SUMMARY include/KF5/mailcommon/backupjob.h contains this include statement: #include "libkdepim/progressmanager.h" When compiling KMail 5.11 on NixOS 19.03, this compilation error is given: /nix/store/zikg7mfgx01isvw6qzi969f1a1yhr7m3-mailcommon-19.04.0-dev/include/KF5/mailcommon/backupjob.h:25:10: fatal error: libkdepim/progressmanager.h: No such file or directory #include "libkdepim/progressmanager.h" that is because the directory .../include/KF5/libkdepim is given in KF5LibkdepimTargets.cmake, but not the parent directory .../include/KF5. There are two solutions: 1) adapt backupjob.h 2) adapt KF5LibkdepimTargets.cmake I'm compiling this on NixOS 19.03. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 406829] New: kwin_x11 crashes on alt-tab
https://bugs.kde.org/show_bug.cgi?id=406829 Bug ID: 406829 Summary: kwin_x11 crashes on alt-tab Product: kwin Version: 5.15.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- SUMMARY kwin_x11 crashes when the pressing alt-tab. Doing one alt-tab quickly, releasing both buttons fast, is fine. Holding alt and just clicking tab causes a crash. STEPS TO REPRODUCE 1. Log in to Plasma 2. Open a few applications 3. Hold Alt and click tab. OBSERVED RESULT kwin_x11 crashes (and restarts immediately). EXPECTED RESULT No crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Distribution: Nixos 19.04 I'm updating the KDE packages for the distribution and testing their stability. $ valgrind kwin_x11 --replace ==26137== Memcheck, a memory error detector ==26137== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==26137== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==26137== Command: kwin_x11 --replace ==26137== --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 --26137-- Warning: DWARF2 CFI reader: unhandled DW_OP_ opcode 0x13 ==26137== Warning: set address range perms: large range [0x59c92000, 0xd9c92000) (defined) qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2707, resource id: 115343413, major code: 3 (GetWindowAttributes), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 2708, resource id: 115343413, major code: 14 (GetGeometry), minor code: 0 ==26137== Thread 5 QQmlThread: ==26137==
[rust-qt-binding-generator] [Bug 404960] Cannot build a demo and templates
https://bugs.kde.org/show_bug.cgi?id=404960 --- Comment #1 from Jos van den Oever --- To build the demo, rust_qt_binding_generator should be built. rust_qt_binding_generator is part of the parent project. To build the demo, do this: cd rust_qt_binding_generator mkdir build cd build cmake .. make Demo -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 404820] default construction SyntaxHighlighter() crashes
https://bugs.kde.org/show_bug.cgi?id=404820 --- Comment #4 from Jos van den Oever --- Upstream patch and removing the '= nullptr' is enough to close this bug imo. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 404820] New: default construction SyntaxHighlighter() crashes
https://bugs.kde.org/show_bug.cgi?id=404820
Bug ID: 404820
Summary: default construction SyntaxHighlighter() crashes
Product: frameworks-syntax-highlighting
Version: 5.55.0
Platform: Other
OS: All
Status: REPORTED
Severity: crash
Priority: NOR
Component: framework
Assignee: kwrite-bugs-n...@kde.org
Reporter: j...@vandenoever.info
Target Milestone: ---
SUMMARY
SyntaxHighlighter(QObject* parent = nullptr) calls QSyntaxHighlighter(parent).
If parent == nullptr, this crashes because QSyntaxHighlighter(QObject *parent)
dereferences parent without checking for nullptr. This could be considered a
bug in QSyntaxHighlighter. However, QSyntaxHighlighter does not have a default
argument nullptr but SyntaxHighlighter does.
I do not see a way to fix SyntaxHighlighter so that SyntaxHighlighter() can be
called without crashing. Ideally, one would do this:
SyntaxHighlighter::SyntaxHighlighter(QObject* parent) :
QSyntaxHighlighter(parent ?QSyntaxHighlighter(parent)
:QSyntaxHighlighter((QTextDocument*)0)),
AbstractHighlighter(new SyntaxHighlighterPrivate)
{
qRegisterMetaType();
}
but that does not compile.
Is there a way to choose what superclass constructor to call at runtime?
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 Jos van den Oever changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/kco ||nfig/2cdcd4f30666fd1095ab7c ||f31361e404db871075 Version Fixed In||5.56 Resolution|--- |FIXED --- Comment #16 from Jos van den Oever --- Git commit 2cdcd4f30666fd1095ab7cf31361e404db871075 by Jos van den Oever. Committed on 20/02/2019 at 16:19. Pushed by vandenoever into branch 'master'. Write valid UTF8 characters without escaping. Summary: commit 6a18528 introduced escaping of bytes >= 127 to ensure that KConfig files are valid UTF8. The simplistic approach with a cutoff results in many escaped bytes where it is not required. Especially non-western configuration files would have many escapes. This commit fixes that by only escaping bytes that are not valid UTF8. FIXED-IN: 5.56 Test Plan: ninja && ninja test Reviewers: dfaure, arichardson, apol, #frameworks, thiago Subscribers: rapiteanu, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D19107 M +52 -2autotests/kconfigtest.cpp M +2-0autotests/kconfigtest.h M +113 -9src/core/kconfigini.cpp https://commits.kde.org/kconfig/2cdcd4f30666fd1095ab7cf31361e404db871075 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 --- Comment #15 from Jos van den Oever --- Most distributions do. The first answer on this question affirms that assuming UTF-8 is generally safe. https://unix.stackexchange.com/questions/2089/what-charset-encoding-is-used-for-filenames-and-paths-on-linux -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 --- Comment #13 from Jos van den Oever --- Even though KConfig should not be used by globalpaths.cpp, KConfig can be improved. https://phabricator.kde.org/D19107 does that. But note that while the bug described here will probably go away for the reporters setup, the bug in globalpaths.cpp is not really solved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 --- Comment #12 from Jos van den Oever --- xdg-user-dirs documentation says: "This file is in a shell format, so its easy to access from a shell script." https://www.freedesktop.org/wiki/Software/xdg-user-dirs/ The tool xdg-user-dirs does not assume an encoding: https://cgit.freedesktop.org/xdg/xdg-user-dirs/tree/xdg-user-dir-lookup.c#n84 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 --- Comment #11 from Jos van den Oever --- globalpaths.cpp should not use KConfig to write user-dirs.dirs KConfig escapes bytes >= 127. Improving that so that it does not escape UTF8 would be nice, but it would only solve this issue for users with UTF8 locales. I think that `user-dirs.dirs` is written in the locale of the user. https://code.woboq.org/qt5/qtbase/src/corelib/io/qstandardpaths_unix.cpp.html#177 This does not mention what the encoding of user-dirs.dirs is. http://manpages.ubuntu.com/manpages/cosmic/man5/user-dirs.dirs.5.html -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557
--- Comment #8 from Jos van den Oever ---
I've just written a test to recreate the issue.
void KConfigTest::testQStringUtf8()
{
QTemporaryFile file;
QVERIFY(file.open());
KConfig config(file.fileName(), KConfig::SimpleConfig);
KConfigGroup general(, "General");
const QString value("Téléchargements");
general.writeEntry("Utf8", value);
config.sync();
file.flush();
file.close();
QFile readFile(file.fileName());
QVERIFY(readFile.open(QFile::ReadOnly));
// check that reading works
KConfig config2(file.fileName(), KConfig::SimpleConfig);
KConfigGroup general2(, "General");
QCOMPARE(value, general2.readEntry("Utf8", QByteArray()));
}
This passes. The é is escaped in the file. This is not needed. Any value above
126 is non-printable or valid UTF8 or another binary value.
Not escaping valid UTF8 sequences is an improvement. But that is not the issue
here.
"Téléchargements" is escaped on saving. That is fine. But it should be
unescaped when loading. This happens in the test, but not in
plasma-desktop/kcms/desktoppaths/globalpaths.cpp.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 --- Comment #6 from Jos van den Oever --- Got a reply now. https://lxr.kde.org/source/kde/workspace/plasma-desktop/kcms/desktoppaths/globalpaths.cpp -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403557] UTF-8 characters are not saved correctly using the implicit path configuration module
https://bugs.kde.org/show_bug.cgi?id=403557 --- Comment #5 from Jos van den Oever --- The information for folder preferences is written to $HOME/.config/user-dirs.dirs I've tried to recreate the bug by renaming my Downloads folder to Téléchargements. This gave me ``` XDG_DOWNLOAD_DIR="$HOME/Téléchargements" `` in $HOME/.config/user-dirs.dirs Reopening the settings dialog again showed me Téléchargements. My environment has LANG=en_US.UTF-8. KDE Frameworks 5.49.0 which is from before D17651. I've tried asking LXR which code writes user-dirs.dirs. https://lxr.kde.org/search?_filestring=&_string=user-dirs.dirs but I'm not getting a reply. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 404127] Crashes if Cargo.toml isn't in the same dir as bindings.json
https://bugs.kde.org/show_bug.cgi?id=404127 --- Comment #1 from Jos van den Oever --- Can you check with version 0.3.1 (master)? -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 403017] Qt-binding-generator "No such file or directory (os error 2)" on run
https://bugs.kde.org/show_bug.cgi?id=403017 Jos van den Oever changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Jos van den Oever --- Thanks for the report. The fixed version is available as 0.3.1. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 402528] Build breaks on Fedora 28
https://bugs.kde.org/show_bug.cgi?id=402528 Jos van den Oever changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jos van den Oever --- Thanks for the report and the fix. The fixed version is available as 0.3.1. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"
https://bugs.kde.org/show_bug.cgi?id=376032 --- Comment #5 from Jos van den Oever --- Selecting the mails in kmail and doing ctrl-u to mark them unread and then ctrl-r to mark them as read sometimes moves them from 'new' to 'cur'. Selecting all mail in a folder (ctrl-a) and doing the same does not move any mails, but it does leave quite some mails in the unread state. Those mails are then *not* moved to 'new'. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 376032] Emails not being moved from "new" to "cur"
https://bugs.kde.org/show_bug.cgi?id=376032 Jos van den Oever changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||j...@vandenoever.info --- Comment #4 from Jos van den Oever --- I'm seeing the same problem. Marking mails as read does not always move them from 'new' to 'cur'. The mails as shown as having been read in KMail but on disk they are still stored in 'new'. I'm using KMail 5.9.0 with KDE Frameworks 5.49.0 on Linux. The mails are retrieved via pop and store in a maildir. KMail reports that it is a valid Maildir. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 402422] Precompile qml
https://bugs.kde.org/show_bug.cgi?id=402422 Jos van den Oever changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Jos van den Oever --- Good idea. You can compile them into the binary by generating them like so: for f in *.qml; do qmlcachegen $f; done and then adding them to the *.qrc file. I do not know if the files will be picked up like that. http://doc.qt.io/qt-5/qtquick-deployment.html has more information for how to do this with QMake and CMake. On my machine compiling the qmlc files takes about 10ms per file. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 401913] Add support for Rust 2018 edition projects.
https://bugs.kde.org/show_bug.cgi?id=401913 Jos van den Oever changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Jos van den Oever --- The solution by Owen Nelson was committed. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400716] Build issues on Windows
https://bugs.kde.org/show_bug.cgi?id=400716 --- Comment #10 from Jos van den Oever --- Have you tried running 'make install' on the ECM in Windows? Or you might be able to change the demo CMakeLists.txt with some IF statement so that missing ECM is not a problem. KDE parts are optional and just for the use with Kirigami. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400716] Build issues on Windows
https://bugs.kde.org/show_bug.cgi?id=400716 --- Comment #8 from Jos van den Oever --- The demo application takes information from the parent directory CMakeLists.txt. The example and template applications are stand-alone. You can run cmake and build in example/todo/, but not in demo/. For demo you run cmake for the parent and then 'make Demo'. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400994] New: build tools not detected by cargo install on Fedora Rawhide
https://bugs.kde.org/show_bug.cgi?id=400994 Bug ID: 400994 Summary: build tools not detected by cargo install on Fedora Rawhide Product: rust-qt-binding-generator Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: j...@vandenoever.info Reporter: j...@vandenoever.info Target Milestone: --- SUMMARY Run `cargo install qrep`. This will download rust-qt-binding-generator for `build.rs`. On Fedora rawhide, Qt binaries are called differently. moc is called moc-qt5 rcc is called rcc-qt5 build.rs in rust-qt-binding-generator should check for these more specific names first and only then try moc and rcc. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400716] Build issues on Windows
https://bugs.kde.org/show_bug.cgi?id=400716 --- Comment #4 from Jos van den Oever --- The patch also fixes the 'test' and 'demo' targets. I'm curious if the demo application works on windows. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400716] Build issues on Windows
https://bugs.kde.org/show_bug.cgi?id=400716 Jos van den Oever changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/rus ||t-qt-binding-generator/f678 ||d441e9fe31d6d933f6c27b884b8 ||07438fcad --- Comment #3 from Jos van den Oever --- Git commit f678d441e9fe31d6d933f6c27b884b807438fcad by Jos van den Oever. Committed on 11/11/2018 at 15:03. Pushed by vandenoever into branch 'master'. Fix building with MSVC M +10 -3demo/CMakeLists.txt M +8-1examples/todos/CMakeLists.txt M +5-1templates/qt_quick/CMakeLists.txt M +5-1templates/qt_widgets/CMakeLists.txt M +8-3tests/CMakeLists.txt https://commits.kde.org/rust-qt-binding-generator/f678d441e9fe31d6d933f6c27b884b807438fcad -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400716] Build issues on Windows
https://bugs.kde.org/show_bug.cgi?id=400716
--- Comment #1 from Jos van den Oever ---
Nice to hear you got it working on windows.
Would these changes work for you?
diff --git a/examples/todos/CMakeLists.txt b/examples/todos/CMakeLists.txt
index 9a940af..8400542 100644
--- a/examples/todos/CMakeLists.txt
+++ b/examples/todos/CMakeLists.txt
@@ -37,7 +37,11 @@ feature_summary(WHAT ALL INCLUDE_QUIET_PACKAGES
FATAL_ON_MISSING_REQUIRED_PACKAG
### build commands ###
SET(RUST_DIR "${CMAKE_CURRENT_SOURCE_DIR}/rust")
-SET(RUST_LIB "${RUST_DIR}/${RUST_TARGET_DIR}/librust.a")
+if (MSVC)
+ SET(RUST_LIB "${RUST_DIR}/${RUST_TARGET_DIR}/rust.lib")
+else()
+ SET(RUST_LIB "${RUST_DIR}/${RUST_TARGET_DIR}/librust.a")
+endif()
# generate c++ and rust code from bindings.json
add_custom_command(
@@ -61,6 +65,9 @@ add_custom_command(
add_custom_target(rust_target DEPENDS "${RUST_LIB}")
list(APPEND Libs "${RUST_LIB}")
+if (MSVC)
+ list(APPEND Libs WS2_32.LIB Userenv.lib)
+endif()
list(APPEND Libs Qt5::Core Qt5::Quick Threads::Threads ${CMAKE_DL_LIBS})
set(SRCS src/main.cpp src/Bindings.cpp "qml.qrc")
add_executable(todos ${SRCS})
--
You are receiving this mail because:
You are watching all bug changes.
[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list
https://bugs.kde.org/show_bug.cgi?id=395192
--- Comment #4 from Jos van den Oever ---
The functionality that you want is possible, but quite some work.
The Model/View in Qt is based on QAbstractItemModel. The current code creates
one QAbstractItemModel for a List or a Tree. Each node in the List or Tree has
the same properties.
Your binding is for a List with a top level of nodes that have `name` and
`novel_list`. Each `novel_list` of type `Source` has a list of items again:
`chapter_list`. So your model is a tree but the nodes on each level have a
different type. It is a clear and logical model from a data modelling point of
view.
A logical Rust structure for this would be
struct Sources {
name: String,
novel_list: Vec,
}
struct Source {
name: title: String,
chapter_list: Vec,
}
struct Novel {
index: u32,
title: String,
content: String,
}
In Qt Model/View each node in a tree has an index and all nodes are basically
the same. The delegates that render the nodes also treat all nodes the same.
But each property can have a different role. If you want to show this model in
a QTreeView or TreeView, you'd specify a different role or column for each
property. So the role numbers and column numbers should be unique for the
properties in the combination of Sources, Source and Novel. The solution I gave
you does that. But it does not look as nice as the structure you want.
The current code could be expanded to interpret Sources, Source and Novel as
belonging to one Tree. It would be very nice, but hard to implement such an
addition to the code generator.
The solution I gave is also flawed in that I forgot to add `optional`:
"objects": {
"Novels": {
"type": "Tree",
"itemProperties": {
"sourcesName": {
"type": "QString",
"optional": true
},
"sourceTitle": {
"type": "QString",
"optional": true
},
"novelIndex": {
"type": "quint32",
"optional": true
},
"novelTitle": {
"type": "QString",
"optional": true
},
"novelContent": {
"type": "QString",
"optional": true
}
}
}
}
This limitation in the generator is also present in Qt itself. If you write C++
code with QAbstractItemModel, you'd face the same issue that it expects each
node in the tree to be the same.
--
You are receiving this mail because:
You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400480] cargo --verbose install qrep fails on Kubuntu 18.04
https://bugs.kde.org/show_bug.cgi?id=400480 --- Comment #1 from Jos van den Oever --- Can you run qmake -query QT_VERSION and report the output? Does /usr/lib/x86_64-linux-gnu/qt4/bin/qmake exist? It seems that you might have qmake from Qt4 installed. Which version of Qt do you have installed? -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400393] When using cargo for compilation, the C++ standard lib is incorrect on Windows when linking but not compiling.
https://bugs.kde.org/show_bug.cgi?id=400393 --- Comment #2 from Jos van den Oever --- Thank you for the bug report and pointer. Commit 89c86642f8e39c1906da72333b431e72ba8dc268 should fix it. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 400393] When using cargo for compilation, the C++ standard lib is incorrect on Windows when linking but not compiling.
https://bugs.kde.org/show_bug.cgi?id=400393 Jos van den Oever changed: What|Removed |Added Latest Commit||https://commits.kde.org/rus ||t-qt-binding-generator/89c8 ||6642f8e39c1906da72333b431e7 ||2ba8dc268 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Jos van den Oever --- Git commit 89c86642f8e39c1906da72333b431e72ba8dc268 by Jos van den Oever. Committed on 28/10/2018 at 21:05. Pushed by vandenoever into branch 'master'. Print the c++ library that cargo should link against This is used when calling "cargo build" when no actual recompile is needed. M +19 -1src/build.rs https://commits.kde.org/rust-qt-binding-generator/89c86642f8e39c1906da72333b431e72ba8dc268 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365422] digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 Jos van den Oever changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Jos van den Oever --- This bug is not present anymore in current Plasma. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 397837] Dockerfile has wrong permissions in container and unset variable in script.
https://bugs.kde.org/show_bug.cgi?id=397837 --- Comment #4 from Jos van den Oever --- Did you try running the docker container via docker-bash-session.sh That script sets XDG_CURRENT_DESKTOP -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 397749] NoData error while talking to IMAP server
https://bugs.kde.org/show_bug.cgi?id=397749
--- Comment #1 from Jos van den Oever ---
Here is another one. Just like in the previous example, I've anonymized the
values.
NoData: too few fields for a Message-message
* 820 FETCH (UID 22252 ENVELOPE ("Wed, 22 Aug 2018 12:36:01 +" "FW:
Afspraak G" (("Person" NIL "person" "domain.com")) NIL NIL
(("per...@domain.com" NIL "person" "domain.com")) NIL NIL "" "") INTERNALDATE
"22-Aug-2018 14:36:22 +0200" BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET"
"ISO-8859-1") NIL NIL "QUOTED-PRINTABLE" 759 9)("MESSAGE" "RFC822" NIL NIL NIL
NIL 23738 296) "MIXED") RFC822.SIZE 19350 BODY[HEADER.FIELDS (REFERENCES
LIST-POST)] {131}
References: ,
)
--
You are receiving this mail because:
You are watching all bug changes.
[trojita] [Bug 397749] New: NoData error while talking to IMAP server
https://bugs.kde.org/show_bug.cgi?id=397749
Bug ID: 397749
Summary: NoData error while talking to IMAP server
Product: trojita
Version: 0.7
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: IMAP
Assignee: trojita-b...@kde.org
Reporter: j...@vandenoever.info
Target Milestone: ---
This error was shown in a dialog in Trojita 0.7. The messaged urged to submit a
bug report. The IMAP server is DavMail.
NoData: too few fields for a Message-message
* 253 FETCH (UID 21034 ENVELOPE ("Mon, 30 Jul 2018 11:20:39 +" "FW: Stand
Up CvS" (("W" NIL "j" "logius.nl")) (("O" NIL "j" "logius.nl")) NIL
(("j...@o.nl"
NIL "j" "k")) NIL NIL "" "") INTERNALDATE "30-Jul-2018 13:21:02 +0200"
BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "ISO-8859-1") NIL NIL
"QUOTED-PRINTABLE" 759 9)("MESSAGE" "RFC822" NIL NIL NIL NIL 6355 79) "MIXED")
RFC822.SIZE 4649 BODY[HEADER.FIELDS (REFERENCES LIST-POST)] {72}
References:
)
--
You are receiving this mail because:
You are watching all bug changes.
[rust-qt-binding-generator] [Bug 397107] PATCH WIP: Add moveable objects
https://bugs.kde.org/show_bug.cgi?id=397107 --- Comment #3 from Jos van den Oever --- Please upload the patch to code review so we can discuss it in detail. https://phabricator.kde.org/differential/diff/create/ -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 397107] PATCH WIP: Add moveable objects
https://bugs.kde.org/show_bug.cgi?id=397107 Jos van den Oever changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #1 from Jos van den Oever --- Making the object optional is one option. The other option is to require that the object implements the Default trait. Implying that the object is optional is bad in my opinion. If the the first of the two alternatives is chosen, it should require that the binding JSON explicitly contains '"optional": true'. Can you say a bit more about 'creating objects on the fly'? -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 396600] compile qt
https://bugs.kde.org/show_bug.cgi?id=396600 Jos van den Oever changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Jos van den Oever --- rust_qt_binding_generator generates cpp files and rust files from a json file. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 396599] demo example not compile
https://bugs.kde.org/show_bug.cgi?id=396599 --- Comment #1 from Jos van den Oever --- What operating system and version are you using? The rust_qt_binding_generator uses CMake files, not qmake .pro files. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list
https://bugs.kde.org/show_bug.cgi?id=395192
--- Comment #2 from Jos van den Oever ---
I recommend writing the binding like this:
"objects": {
"Novels": {
"type": "Tree",
"itemProperties": {
"sourcesName": {
"type": "QString"
},
"sourceTitle": {
"type": "QString"
},
"novelIndex": {
"type": "quint32"
},
"novelTitle": {
"type": "QString"
},
"novelContent": {
"type": "QString"
}
}
}
}
Then you model it such that a novel has QAbstractItemModel::parent() which is
the source and the source has a parent() which is the list of all sources.
--
You are receiving this mail because:
You are watching all bug changes.
[rust-qt-binding-generator] [Bug 395192] rust-qt-binding-generator: unable to compile multi-dimensional list
https://bugs.kde.org/show_bug.cgi?id=395192 --- Comment #1 from Jos van den Oever --- The binding.json that you use has nested lists. That is currently not supported. The bug is that there is no error message for that. You can nest a List or a Tree in an Object. Could you remodel the structure into something where there is no nesting of Lists of Trees? -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 392959] Invalid QString conversion in TreeModel.data.fieldname
https://bugs.kde.org/show_bug.cgi?id=392959 Jos van den Oever <j...@vandenoever.info> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Jos van den Oever <j...@vandenoever.info> --- This issue is fixed as of 57d557378ee629496b4a6afc58022f0677cdff06. The struct qstring_t is not present anymore. QString data is now passed as two pieces of data: the pointer to the characters and the length. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 389419] "MyExe" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=389419 Jos van den Oever <j...@vandenoever.info> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #21 from Jos van den Oever <j...@vandenoever.info> --- This should be fixed as of 57d557378ee629496b4a6afc58022f0677cdff06. I've tested Demo, qt_widget and qt_quick in Arch. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 392246] Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=392246 Jos van den Oever <j...@vandenoever.info> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jos van den Oever <j...@vandenoever.info> --- This should be fixed as of 57d557378ee629496b4a6afc58022f0677cdff06. I've tested Demo qt_widget and qt_quick in Arch. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 390440] The SSL certificate is invalid
https://bugs.kde.org/show_bug.cgi?id=390440 --- Comment #4 from Jos van den Oever <j...@vandenoever.info> --- The root certificates were missing in the docker image. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 390440] The SSL certificate is invalid
https://bugs.kde.org/show_bug.cgi?id=390440 Jos van den Oever <j...@vandenoever.info> changed: What|Removed |Added Latest Commit||https://commits.kde.org/rus ||t-qt-binding-generator/d313 ||4229ae60d8981e1ff5fbb766048 ||a6d0d853a Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Jos van den Oever <j...@vandenoever.info> --- Git commit d3134229ae60d8981e1ff5fbb766048a6d0d853a by Jos van den Oever. Committed on 30/04/2018 at 14:44. Pushed by vandenoever into branch 'master'. Add package ca-certificates M +1-0docker/Dockerfile https://commits.kde.org/rust-qt-binding-generator/d3134229ae60d8981e1ff5fbb766048a6d0d853a -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 389419] "MyExe" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=389419 --- Comment #20 from Jos van den Oever <j...@vandenoever.info> --- I can reproduce this error in a VirtualBox with Arch and rustc 1.25. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 392679] playing a video with mpv counts as activity to RSIbreak
https://bugs.kde.org/show_bug.cgi?id=392679 Jos van den Oever <j...@vandenoever.info> changed: What|Removed |Added Version|0.12.8 |5.44.0 Product|rsibreak|frameworks-kidletime Assignee|aa...@kde.org |kdelibs-b...@kde.org Component|general |general -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 392679] playing a video with mpv counts as activity to RSIbreak
https://bugs.kde.org/show_bug.cgi?id=392679 --- Comment #3 from Jos van den Oever <j...@vandenoever.info> --- The bug report at mpv is here. https://github.com/mpv-player/mpv/issues/5702 I agree that this might require work in kidletime instead of rsibreak. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 392679] playing a video with mpv counts as activity to RSIbreak
https://bugs.kde.org/show_bug.cgi?id=392679 --- Comment #1 from Jos van den Oever <j...@vandenoever.info> --- The combination VLC and RSIbreak is fine. So mpv is behaving in a way that lets RSIbreak think there is activity. Easy way to test: play a video not full-screen and after 40 seconds without keyboard or mouse activity (the default) the activity icon should become fully purple instead of 3/4, 1/2 or 1/4 purple. -- You are receiving this mail because: You are watching all bug changes.
[rsibreak] [Bug 392679] New: playing a video with mpv counts as activity to RSIbreak
https://bugs.kde.org/show_bug.cgi?id=392679 Bug ID: 392679 Summary: playing a video with mpv counts as activity to RSIbreak Product: rsibreak Version: 0.12.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: j...@vandenoever.info Target Milestone: --- When playing a video with mpv, RSIbreak thinks the user is active. This results in RSIbreak interrupting the video with a popup. This happens when running the video fullscreen and in window on X windows. A workaround would be to make a script that suspends RSIbreak for the duration of the video via DBus. But that does not cover the situation where a video is playing an the user continues to use mouse and keyboard. -- You are receiving this mail because: You are watching all bug changes.
[rust-qt-binding-generator] [Bug 389419] "MyExe" received signal SIGSEGV, Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=389419 --- Comment #15 from Jos van den Oever <j...@vandenoever.info> --- That is very disappointing. What would be the quickest way for me to replicate your setup in a VM? -- You are receiving this mail because: You are watching all bug changes.
