Re: Dragging icons at desktop
Miguel A. Vallejo - 28.11.22, 23:26:52 CET: > Recently I noticed when I drag an icon in the desktop (fully updated > Sid), the icon lags behind the mouse cursor instead of following the > mouse cursor under it as it always did. I can confirm this. > I have searched in Preferences but I do not see anything about "drag > animations" or any related effect. > > Anyone know how to disable it and go back to the old behaviour? Yeah, would be nice to know. I am not yet sure whether I like to get used to this behavior. Best, -- Martin
Dragging icons at desktop
Hi all! Recently I noticed when I drag an icon in the desktop (fully updated Sid), the icon lags behind the mouse cursor instead of following the mouse cursor under it as it always did. It seems to be intentional because of the "cute animation", but it is terribly uncomfortable and breaks the workflow completely. I have searched in Preferences but I do not see anything about "drag animations" or any related effect. Anyone know how to disable it and go back to the old behaviour? Thanks in advance
qtcreator_9.0.0-3_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 28 Nov 2022 20:51:55 +0100 Source: qtcreator Architecture: source Version: 9.0.0-3 Distribution: experimental Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: qtcreator (9.0.0-3) experimental; urgency=medium . * Team upload. * When building with clang, force the v4 of the DWARF info: apparently the DWARF v5 that clang produces are not fully supported by dwz (see also #1016936): - append -gdwarf-4 to CFLAGS and CXXFLAGS Checksums-Sha1: 68260b1626e56317df13ded93cf82d92e75a3eae 2798 qtcreator_9.0.0-3.dsc 4fa0022d4693838c1beb2b1e4dae594dce0cbeff 29076 qtcreator_9.0.0-3.debian.tar.xz 6c1ca4b3a4479c107c12eb1272097a7a3c138b28 8319 qtcreator_9.0.0-3_source.buildinfo Checksums-Sha256: a0451613818fd2a2bbd25b4f4f744a45b0808b81fd5e2178f960d7ec6bf4d73f 2798 qtcreator_9.0.0-3.dsc 85f3d838e0290208d5e914f349bd8f77275b56c5797bec654086f7e72b4204d0 29076 qtcreator_9.0.0-3.debian.tar.xz 69bc1f4b1d4b925a21b409893ff38bb594a926abbd847547664e2e9391be9626 8319 qtcreator_9.0.0-3_source.buildinfo Files: a6d381582a1e1ac7c0b0478aa34b7ea7 2798 devel optional qtcreator_9.0.0-3.dsc fa88e61179126197a53a61c551e381af 29076 devel optional qtcreator_9.0.0-3.debian.tar.xz 486c5339ec8211b6f5e8f31fccd4016c 8319 devel optional qtcreator_9.0.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmOFEZ4ACgkQLRkciEOx P00KoA/+I2Ax1EgzEqqp0JrTaqXCdIbweAnEPJwKIvBwk32cjgyIKJoVieXsJKmt xoi1YryJVqzDN2a0bdF24y8ayqGXtZ8j6dNDPfvGiago2+DHHLLNJOXEGFxFGU9w rr8VP4s9g5iPjFuNm8Xe66/ShGyKvdOOxqZzvwUx7RsP6Lwt9scLd+pOZVbGPVCH HDxr0Mk+lOEsvUSAkV24Qp0TOEYpGr2pqA28Z0iDVQLNH4Gbq0rX/9rRZhrYLt5P Ccuu5vt5vEBSIqY/sdhmz6YX2ozEUvUBpLIJc16vfDNTMJVqycRNeyAuxYw7DnlX gfGDj0s3yaS4yGN5mxTOypfMc7IaqSQfABfwVWIcvUs0MvvWgGpBPcW3qytikSDW Klj3jReFS8a4EC8AO0L7sNuoX/2uiXBJi4a43QlVvzNVrYEO98k16Vr+bM1bdFST SEgeY0zQc6MGi8M0wSHkR/6fFtX1Yo5kgK/raH8o1MSnHVKXpjrqoAy3JleAbvqP wYhCcOQsAOas1CvGb8GzYlv/mPbSAUB+2s+g76la2uyhS/F5yb+5I1A7tZXe73ip yEW9bleHx4d0yW7nK+CBqbXSu5/KOzoQqPRGAtrSZ7LmXhww76CiNjjtZCijHUdy HojMCu5Vo3mPNLYTQ4mub0x6K/k5VMWBrt+rwtalVA7VFK4dRmU= =L9Nv -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of qtcreator_9.0.0-3_source.changes
qtcreator_9.0.0-3_source.changes uploaded successfully to localhost along with the files: qtcreator_9.0.0-3.dsc qtcreator_9.0.0-3.debian.tar.xz qtcreator_9.0.0-3_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
[bts-link] source package kaddressbook
# # bts-link upstream status pull for source package kaddressbook # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #831899 (http://bugs.debian.org/831899) # Bug title: kaddressbook crashes immediately on start # * http://bugs.kde.org/show_bug.cgi?id=358696 # * remote status changed: NEEDSINFO -> RESOLVED # * remote resolution changed: WAITINGFORINFO -> WORKSFORME # * closed upstream tags 831899 + fixed-upstream usertags 831899 - status-NEEDSINFO resolution-WAITINGFORINFO usertags 831899 + status-RESOLVED resolution-WORKSFORME thanks
[bts-link] source package kmix
# # bts-link upstream status pull for source package kmix # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # https://bts-link-team.pages.debian.net/bts-link/ # user debian-bts-l...@lists.debian.org # remote status report for #789887 (http://bugs.debian.org/789887) # Bug title: Uses cpu when remote pulse server is unavailable # * http://bugs.kde.org/show_bug.cgi?id=339913 # * remote status changed: NEEDSINFO -> RESOLVED # * remote resolution changed: WAITINGFORINFO -> WORKSFORME # * closed upstream tags 789887 + fixed-upstream usertags 789887 - status-NEEDSINFO resolution-WAITINGFORINFO usertags 789887 + status-RESOLVED resolution-WORKSFORME thanks
Processed: [bts-link] source package kaddressbook
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kaddressbook > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #831899 (http://bugs.debian.org/831899) > # Bug title: kaddressbook crashes immediately on start > # * http://bugs.kde.org/show_bug.cgi?id=358696 > # * remote status changed: NEEDSINFO -> RESOLVED > # * remote resolution changed: WAITINGFORINFO -> WORKSFORME > # * closed upstream > tags 831899 + fixed-upstream Bug #831899 [kaddressbook] kaddressbook crashes immediately on start Added tag(s) fixed-upstream. > usertags 831899 - status-NEEDSINFO resolution-WAITINGFORINFO Usertags were: status-NEEDSINFO resolution-WAITINGFORINFO. There are now no usertags set. > usertags 831899 + status-RESOLVED resolution-WORKSFORME There were no usertags set. Usertags are now: status-RESOLVED resolution-WORKSFORME. > thanks Stopping processing here. Please contact me if you need assistance. -- 831899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package kmix
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package kmix > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #789887 (http://bugs.debian.org/789887) > # Bug title: Uses cpu when remote pulse server is unavailable > # * http://bugs.kde.org/show_bug.cgi?id=339913 > # * remote status changed: NEEDSINFO -> RESOLVED > # * remote resolution changed: WAITINGFORINFO -> WORKSFORME > # * closed upstream > tags 789887 + fixed-upstream Bug #789887 [kmix] Uses cpu when remote pulse server is unavailable Added tag(s) fixed-upstream. > usertags 789887 - status-NEEDSINFO resolution-WAITINGFORINFO Usertags were: resolution-WAITINGFORINFO status-NEEDSINFO. There are now no usertags set. > usertags 789887 + status-RESOLVED resolution-WORKSFORME There were no usertags set. Usertags are now: resolution-WORKSFORME status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. -- 789887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1022972: Acknowledgement (konsole: Konsole does not handle arrow keys correctly anymore)
Max, Nathanael, could you confirm that you're too using Neo2, or similarly "exotic" layouts? Otherwise we're probably looking at different issues. Indeed, I use Neo2. This can be traced down to the keyboard configuration of konsole. When going to: Edit Current Profile... -> Keyboard -> Default (XFree 4) -> Edit... and then using the "input" field for testing, it can be observed that for the arrow up key, different rules trigger depending on the keyboard layout: Layout Rule Escape Sequence de neo Up-Shift+Ansi+AnyModifier\E[1;1A us Up-Shift+Ansi-AppCursorKeys-AnyModifier \E[A This workaround worked for me. I used some "normal" German variant, though. Best regards Max Görner
