[kwin] [Bug 475642] New: Transparent XWayland Windows can have strange artifacts, demonstrated with Oneko and Neko98.
https://bugs.kde.org/show_bug.cgi?id=475642 Bug ID: 475642 Summary: Transparent XWayland Windows can have strange artifacts, demonstrated with Oneko and Neko98. Classification: Plasma Product: kwin Version: 5.27.8 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: platform-x11-nested Assignee: kwin-bugs-n...@kde.org Reporter: sa...@sarahduck.ca Target Milestone: --- Created attachment 162314 --> https://bugs.kde.org/attachment.cgi?id=162314=edit A screenshot of both Oneko and Neko98 with identical artifacting. SUMMARY On Fedora, running Oneko from the repos, from Flathub, or running Neko98 through Wine results in overlapping frames of animation. They look just fine on the standalone X11 session. I had a friend of mine running Gnome 44 on NixOS attempt to install and run Oneko, and it looked just fine on Wayland, so I'm guessing this is a KDE specific issue. I've managed to reproduce it both on my laptop with an AMD CPU/GPU, and on my tablet with an Intel CPU/GPU. STEPS TO REPRODUCE 1. Run Oneko on KDE Wayland OBSERVED RESULT I've attached a screenshot, they look very wrong. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 38, KDE 5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454312] Kate Vi mode mouse selection makes cursor position wrong (always +1 column)
https://bugs.kde.org/show_bug.cgi?id=454312 Sarah Wong changed: What|Removed |Added CC||n...@danger.chat --- Comment #1 from Sarah Wong --- Attempting a fix here: https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/430 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 454417] 'gv' can't select last selection sometimes in Kate Vi input mode
https://bugs.kde.org/show_bug.cgi?id=454417 Sarah Wong changed: What|Removed |Added CC||n...@danger.chat --- Comment #1 from Sarah Wong --- Attempting a fix here: https://invent.kde.org/frameworks/ktexteditor/-/merge_requests/430 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415570] Print > Selection omits some text
https://bugs.kde.org/show_bug.cgi?id=415570 Sarah Wong changed: What|Removed |Added CC||n...@danger.chat --- Comment #7 from Sarah Wong --- This problem seems to be because the logic to clip individual lines to selection doesn't work properly when there is a line wrap in the printed document: https://invent.kde.org/frameworks/ktexteditor/-/blob/4594c7e66df9325ef2dd256af75bbe9cf3b06398/src/printing/printpainter.cpp#L650-661 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433522] New: Updating screen lock settings crashes system setting window
https://bugs.kde.org/show_bug.cgi?id=433522 Bug ID: 433522 Summary: Updating screen lock settings crashes system setting window Product: systemsettings Version: 5.20.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sarah.azu...@gmail.com Target Milestone: --- Application: systemsettings5 (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.10.16-200.fc33.x86_64 x86_64 Windowing system: X11 Distribution: "Fedora release 33 (Thirty Three)" -- Information about the crash: - What I was doing when the application crashed: I was trying to change the background image for screen lock and it crashed. Restarted the app and tried to change another setting and it crashed again. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f996df0aa0e in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, QQmlPropertyData**) () from /lib64/libQt5Qml.so.5 #5 0x7f996deee491 in QV4::QQmlContextWrapper::getPropertyAndBase(QV4::QQmlContextWrapper const*, QV4::PropertyKey, QV4::Value const*, bool*, QV4::Value*, QV4::Lookup*) () from /lib64/libQt5Qml.so.5 #6 0x7f996deefe63 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter(QV4::Lookup*, QV4::ExecutionEngine*, QV4::Value*) () from /lib64/libQt5Qml.so.5 #7 0x7f996df24310 in QV4::Moth::VME::interpret(QV4::CppStackFrame*, QV4::ExecutionEngine*, char const*) () from /lib64/libQt5Qml.so.5 #8 0x7f996df2a775 in QV4::Moth::VME::exec(QV4::CppStackFrame*, QV4::ExecutionEngine*) [clone .part.0] () from /lib64/libQt5Qml.so.5 #9 0x7f996dec97bd in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /lib64/libQt5Qml.so.5 #10 0x7f996e024e71 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /lib64/libQt5Qml.so.5 #11 0x7f996dfe1011 in QQmlBoundSignalExpression::evaluate(void**) () from /lib64/libQt5Qml.so.5 #12 0x7f996dfe2a63 in QQmlBoundSignal_callback(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #13 0x7f996e005c0d in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib64/libQt5Qml.so.5 #14 0x7f996efba2f2 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7f996dfdc1f9 in QQmlContextData::emitDestruction() () from /lib64/libQt5Qml.so.5 #16 0x7f996dfdc21f in QQmlContextData::emitDestruction() () from /lib64/libQt5Qml.so.5 #17 0x7f996dfdc21f in QQmlContextData::emitDestruction() () from /lib64/libQt5Qml.so.5 #18 0x7f996dfdc21f in QQmlContextData::emitDestruction() () from /lib64/libQt5Qml.so.5 #19 0x7f996dfdc21f in QQmlContextData::emitDestruction() () from /lib64/libQt5Qml.so.5 #20 0x7f996dfdc44d in QQmlContextData::invalidate() () from /lib64/libQt5Qml.so.5 #21 0x7f996dfdbf7b in QQmlContextData::destroy() () from /lib64/libQt5Qml.so.5 #22 0x7f996dfdc15d in QQmlContext::~QQmlContext() () from /lib64/libQt5Qml.so.5 #23 0x7f996dfdc17d in QQmlContext::~QQmlContext() () from /lib64/libQt5Qml.so.5 #24 0x7f996efb293a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #25 0x7f996efb82ef in QObject::~QObject() () from /lib64/libQt5Core.so.5 #26 0x7f996e732ebd in KDeclarative::QmlObjectSharedEngine::~QmlObjectSharedEngine() () from /lib64/libKF5Declarative.so.5 #27 0x7f997044e6d6 in KQuickAddons::ConfigModule::~ConfigModule() () from /lib64/libKF5QuickAddons.so.5 #28 0x7f98f0067336 in ScreenLockerKcm::~ScreenLockerKcm() () from /usr/lib64/qt5/plugins/kcms/kcm_screenlocker.so #29 0x7f9970549e47 in KCModuleQml::~KCModuleQml() () from /lib64/libKF5KCMUtils.so.5 #30 0x7f9970549e6d in KCModuleQml::~KCModuleQml() () from /lib64/libKF5KCMUtils.so.5 #31 0x7f997054d298 in KCModuleProxy::deleteClient() () from /lib64/libKF5KCMUtils.so.5 #32 0x7f997054e41c in KCModuleProxy::~KCModuleProxy() () from /lib64/libKF5KCMUtils.so.5 #33 0x7f997054e51d in KCModuleProxy::~KCModuleProxy() () from /lib64/libKF5KCMUtils.so.5 #34 0x7f996efb293a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #35 0x7f996fb57246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #36 0x7f996fb5759d in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #37 0x7f996efb293a in QObjectPrivate::deleteChildren() () from /lib64/libQt5Core.so.5 #38 0x7f996fb57246 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #39 0x7f996fcb23dd in QScrollArea::~QScrollArea() () from /lib64/libQt5Widgets.so.5 #40 0x7f99702984d7 in
[kdenlive] [Bug 413597] video preview not playing
https://bugs.kde.org/show_bug.cgi?id=413597 Sarah changed: What|Removed |Added CC||sbair.em...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 413597] New: video preview not playing
https://bugs.kde.org/show_bug.cgi?id=413597 Bug ID: 413597 Summary: video preview not playing Product: kdenlive Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: sbair.em...@gmail.com Target Milestone: --- SUMMARY - Working on Kdenlive 15.12.3. OS is MATE 1.12.1. Two days ago the videos stopped playing. I can't play from where it opens, I can move the bar but it doesn't play from a new location either or a different clip. The time goes from 00:00:00:00 to 00:00:00:01 and stops but no picture appears in the clip monitor. I've tried multiple videos and created a new video with the same results. I can preview clips that I've uploaded from the bar on the left but not it will not play from what I've edited below. Thanks in advance. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 411498] Activating the Amarok Script Console makes Amarok unstartable
https://bugs.kde.org/show_bug.cgi?id=411498 Sarah changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 411498] Activating the Amarok Script Console makes Amarok unstartable
https://bugs.kde.org/show_bug.cgi?id=411498 --- Comment #2 from Sarah --- Brilliant. I've got amarok back now. Thanks. I'll try and burn a playlist later. It used to be on the tools menu but thats fine. thanks. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 411498] New: Amarok won't open as "A KDE text-editor component could not be found."
https://bugs.kde.org/show_bug.cgi?id=411498 Bug ID: 411498 Summary: Amarok won't open as "A KDE text-editor component could not be found." Product: amarok Version: 2.9.0 Platform: Mint (Debian based) OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: Tools/Script Manager Assignee: amarok-bugs-d...@kde.org Reporter: crazypigl...@gmx.com CC: darthco...@gmail.com Target Milestone: kf5 SUMMARY STEPS TO REPRODUCE 1. Open Amarok and choose Tools 2. Check a box to edit scripts (I can't open amarok to recreate so can't see exact box) 3. I was looking to see if the option to burn playlist to k3b was available as a script. OBSERVED RESULT a dialogue box opens saying "A KDE text-editor component could not be found. Please check your KDE installation. Exiting the console!" with the only option to 'ok' which then exits amarok. all subsequent attempts to open amarok have simply produced this dialogue without opening. EXPECTED RESULT either nothing or an option to install a script linking playlist to k3b (this used to be a feature) SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION i've uninstalled and reinstalled both amarok and amarok utils with no effect. I've installed Kate and Kwrite and the complete KDE (I'm on Mint which I know isn't K but amarok and some other applications always worked) to try to install the 'Text editor component' but with no effect. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 410249] New: Kdenlive Over-Renders Videos
https://bugs.kde.org/show_bug.cgi?id=410249 Bug ID: 410249 Summary: Kdenlive Over-Renders Videos Product: kdenlive Version: 19.04.0 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: sarahsz...@protonmail.com Target Milestone: --- SUMMARY If I add a small video and an .mp3 to the track and render the project it takes about 4 hours and has 20 minutes of extra blank space for seemingly no reason. My format was .mp4, but this shoudn't really matter. Quality settings are default. STEPS TO REPRODUCE 1. Open apt based kdenlive make simple project (HD 1080p 30fps) 2. Add Video and audio and render 3. See 20 minutes of extra dead space OBSERVED RESULT 20 minutes of extra dead space and about 600% extra render time EXPECTED RESULT Much faster renders and video should match timeline and not have extra dead space in it. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 19.04 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407621] New: I cant create a new canvas
https://bugs.kde.org/show_bug.cgi?id=407621 Bug ID: 407621 Summary: I cant create a new canvas Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: grave Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: sarahsalce...@gmail.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397288] FIlenames Disappear Upon Resume from Suspend?
https://bugs.kde.org/show_bug.cgi?id=397288 --- Comment #2 from Sarah --- Created attachment 114410 --> https://bugs.kde.org/attachment.cgi?id=114410=edit Graphics Card Specs Here is the graphics card specs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397288] New: FIlenames Disappear Upon Resume from Suspend?
https://bugs.kde.org/show_bug.cgi?id=397288 Bug ID: 397288 Summary: FIlenames Disappear Upon Resume from Suspend? Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sarahsz...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Upon resuming from suspend (On my HP ENVY 17 running Kubuntu 18.04.01) the filenames on the desktop folders and files are pixelated and often have black bars around the filenames, which sometimes disappear. The only solution I've found to remedy this issue is to killall plasmashell && kstart plasmashell. This restores the desktop, but this is a bug and shouldn't happen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-networkmanager-qt] [Bug 397287] New: Network Manager Doesn't Connect to Wi-Fi Log In Page?
https://bugs.kde.org/show_bug.cgi?id=397287 Bug ID: 397287 Summary: Network Manager Doesn't Connect to Wi-Fi Log In Page? Product: frameworks-networkmanager-qt Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: sarahsz...@protonmail.com CC: lamar...@kde.org, lukas.ti...@merlin.cz Target Milestone: --- When I try to connect to a wi-fi network that requires that I sign in, I don't get a redirect to their sign in/up webpage. When I try to connect to the network using the Qt panel in the toolbar, I connect to the network that would normally ask me to sign in to use it, and it connects just fine, but offers no redirect in Chromium (My default browser), and just says any attempt to access a webpage as not having any internet connection. I noticed this when i was visiting a relative at a hospital that had public wi-fi that only required agreeing to terms to use their wi-fi. I encountered the bug, but my friend who had a different laptop vendor, but the same OS/Version number was able to get the redirect and access the internet. I've observed that another Kubuntu 18.04.01 laptop is able to access the log in page, and this appears to be some kind of strange software interaction with my laptop's hardware. I'm running an HP ENVY 17 on Kubuntu 18.04.01 (Latest updates as of 08/08/2018) with this networking hardware: 07:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Kernel driver in use: iwlwifi Kernel modules: iwlwifi 0f:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c) Subsystem: Hewlett-Packard Company RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller Kernel driver in use: r8169 Kernel modules: r8169 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 397137] Wi-Fi is Inaccessible Due to Waiting forever for Password Info
https://bugs.kde.org/show_bug.cgi?id=397137 --- Comment #1 from Sarah --- Created attachment 114294 --> https://bugs.kde.org/attachment.cgi?id=114294=edit Youtube Video of the Bug -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 397137] New: Wi-Fi is Inaccessible Due to Waiting forever for Password Info
https://bugs.kde.org/show_bug.cgi?id=397137 Bug ID: 397137 Summary: Wi-Fi is Inaccessible Due to Waiting forever for Password Info Product: kwalletmanager Version: 18.04 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: va...@kde.org Reporter: sarahsz...@protonmail.com Target Milestone: --- Preface: I always log into a certain wi-fi network that is in my room. I have the password set to be remembered by the wi-fi manager (The encrypted setting). I also use a VPN and have it set up to automatically connect to it upon establishing a network connection. What happens: 1) Wi-Fi Manager attempts to connect to network, stalls forever, says 'Waiting for Authorization' 2)Indefinite Wait 3) sudo service network-manager restart is ineffective What should happen: wi-fi logs in like normal Workaround: Go to system settings/kde wallet, create new wallet and press `open wallet`, prompt for wi-fi opens up, enter password, enter password for VPN, connection established. I have to do this every time, and if I did't figure it out, I would be left without an internet connection. System: Kubuntu 18.04.01 on an HP ENVY 17. I will upload a video of the problem next time I restart the computer, but the description is accurate. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397135] There are black borders when moving windows from one monitor to second monitor.
https://bugs.kde.org/show_bug.cgi?id=397135 --- Comment #1 from Sarah --- Created attachment 114293 --> https://bugs.kde.org/attachment.cgi?id=114293=edit Youtube Video of the Effect -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 397135] New: There are black borders when moving windows from one monitor to second monitor.
https://bugs.kde.org/show_bug.cgi?id=397135 Bug ID: 397135 Summary: There are black borders when moving windows from one monitor to second monitor. Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: sarahsz...@protonmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Often happens after suspend then reopen (After I close it for the night to go to sleep) 1) Suspend Computer 2) Log Back In 3) Try to move window from one monitor to another 4) Get black borders A More Visual Representation: https://youtu.be/vGPKpl6MPyM Happened on Kubuntu 18.04.01 LTS on 03/08/2018 (Today) on a HP ENVY 17 Laptop -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 91221] Ability to view .txt files in files tab
https://bugs.kde.org/show_bug.cgi?id=91221 Sarah smh <smaiah.sa...@gmail.com> changed: What|Removed |Added CC||smaiah.sa...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
Finanztest: Die beste private Krankenversicherung 2016 – schon ab 89 € monatlich
Sehr geehrte Leserinnen und Leser, kurze Wartezeiten beim Arzt, beste Behandlung und Medikamente: Das bekommen Sie nur durch eine private Krankenversicherung (PKV). Und die muss nicht mal teuer sein. Wenn Sie eine Krankenversicherung privat abschließen, zahlen Sie häufig weniger als bei der gesetzlichen Krankenversicherung. Jetzt Beitrag berechnen: http://stiftungversicherungtest.net/track/?id=4CB15E0C44=2053D01357=F87D924104 Spartipp: In vielen Tarifen erhalten Sie eine teilweise Rückerstattung der Beiträge, wenn Sie keine Leistungen in Anspruch nehmen. Dies lohnt sich vor allem für junge, gesunde Verbraucher, die selten krank werden. Darüber hinaus zahlen einige Versicherer auch freiwillig eine erfolgsabhängige Beitragsrückerstattung, wenn in einem Jahr besonders gut gewirtschaftet wurde. Gern beraten Sie unsere Redakteure kostenlos und unverbindlich. Ihr Finanztest-Team Sarah Bader Redaktion Hallesches Ufer 59 72649 Wolfschlugen Keine weiteren News empfangen: http://stiftungversicherungtest.net/unsubscribe/?id=4CB15E0C44=F87D924104=4C0EB020C5=jgNoZff40E1_2wyK0Swk7kEIF-_-4BRhtpMIS-ABnryFccg8VkvsajuHc1RMzfub
[plasmashell] [Bug 365995] New: Shorter date formats for vertical taskbar users.
https://bugs.kde.org/show_bug.cgi?id=365995 Bug ID: 365995 Summary: Shorter date formats for vertical taskbar users. Product: plasmashell Version: 5.7.2 Platform: Gentoo Packages URL: http://lum.uk/temp/DigitalClock.png OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: kde-b...@lum.co.uk Currently the shortest date format available is a 10-digit format, DD/MM/ (in my locale), which is a bit too wide if you happen to prefer a vertical taskbar (useful on low-res widescreen devices). Would it be possible to provide two shorter options (DD/MM/YY and DD/MM) for users with this setup, or a custom date format option (ala T-Clock Redux for Windows) Reproducible: Always Steps to Reproduce: 1) Move the panel to the side of the screen 2) Shrink the panel to 50px or less Actual Results: Date is left-aligned and truncated with an elpisis (eg. DD/MM... as per screenshot) Expected Results: Date is centred with no elipsis. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [AIPTEK][VISTALK][ADESSO][TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #31 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99375 --> https://bugs.kde.org/attachment.cgi?id=99375=edit The 3.0 Alpha which works with Tablet I thought this might help if it shows the difference between the Krita which understands the awkward tablet and the one which causes Krita to crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [AIPTEK][VISTALK][ADESSO][TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 Sarah <slg...@hotmail.co.uk> changed: What|Removed |Added Attachment #99285|0 |1 is obsolete|| --- Comment #30 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99374 --> https://bugs.kde.org/attachment.cgi?id=99374=edit Debug report for latest Krita release showing the issue causing crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [AIPTEK][VISTALK][ADESSO][TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 Sarah <slg...@hotmail.co.uk> changed: What|Removed |Added Attachment #99284|0 |1 is obsolete|| --- Comment #29 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99373 --> https://bugs.kde.org/attachment.cgi?id=99373=edit Krita offset -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [AIPTEK][VISTALK][ADESSO][TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #28 from Sarah <slg...@hotmail.co.uk> --- (In reply to Dmitry Kazakov from comment #27) > Git commit 22c3c0d5d49ef164e4def4d545faee7f37797a5f by Dmitry Kazakov. > Committed on 03/06/2016 at 12:48. > Pushed by dkazakov into branch 'krita/3.0'. > > Add a workaround for weird tablets > > Instead of the returning the size of the needed buffer these > "nice" tablet drivers start writing its name straight into > the buffer pointed by a null pointer. > > See a comment in the code for more details > Related: bug 359298, bug 362868, bug 363684, bug 363873, bug 351059, bug > 354979 > > M +35 -2libs/ui/input/wintab/kis_tablet_support_win.cpp > > http://commits.kde.org/krita/22c3c0d5d49ef164e4def4d545faee7f37797a5f Hello I'm sorry to keep bothering you but I'm afraid the work around in the latest download 3.0 still has the same error. I read the bug fixing report and it was very interesting! I even understood some of it. :D Which is super rare for me with PC things. If there's nothing that can be done I appreciate all the time and effort you have made, we donated what we could afford which I hope offset the awkwardness a but for you. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 Sarah <slg...@hotmail.co.uk> changed: What|Removed |Added Attachment #99139|0 |1 is obsolete|| --- Comment #20 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99285 --> https://bugs.kde.org/attachment.cgi?id=99285=edit Debug crash report when using newest release Krita with Trust Tablet TB7300 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #19 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99284 --> https://bugs.kde.org/attachment.cgi?id=99284=edit Screen resolution box when I try to use the tablet -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #18 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99283 --> https://bugs.kde.org/attachment.cgi?id=99283=edit Monitor and graphics driver details -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #17 from Sarah <slg...@hotmail.co.uk> --- (In reply to Boudewijn Rempt from comment #16) > We got a second-hand Trust TB 5300... And that doesn't allow us to reproduce > the crash yet! Mine still does it but in a different way now! I downloaded the latest 3.0 (git f0cbffc) release and it comes up with a box about screen resolution. I didn't think I could describe it well so I took a screenshot and did another Debug report, Maybe I just have an awkward tablet which doesn't play well with others! Although I have been told my graphic card could also be being a bother, I have attached a screenshot of the details of the card and the monitors so I can be more specific. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [TRUST][PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #15 from Sarah <slg...@hotmail.co.uk> --- (In reply to Boudewijn Rempt from comment #14) > Hi Adriano and Sara, > > What are the exact types of these tablets and what are the exact driver > revisions you are using? HI again! I'm using a Trust WIDE SCREEN DESIGN TABLET TB-7300 with a Windows 10 (64 bit driver). The company doesn't produce the tablet any more but they created the windows 10 driver after finding out that I still using the tablet (isn't that lovely!?) http://www.trust.com/en/product/15358-wide-screen-design-tablet-tb-7300 Thanks again for all your help and looking into this, it means a lot. :D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #13 from Sarah <slg...@hotmail.co.uk> --- (In reply to Sarah from comment #12) > (In reply to Boudewijn Rempt from comment #11) > > Hi Sarah, > > > > What is your exact monitor configuration and resolution? > > Hi > > I have two monitors. My main monitor has a resolution of 1920 x 1080, this > is the monitor the tablet is configured to respond to (specifically I have > been told that the tablet is mapped to monitor 1 only - which is not the > TV). My other monitor is an older widescreen TC, the resolution is 1280 x > 720. So I am dual screening I think. > > Thanks for the speedy reply! Sorry widescreen TV not TC. Silly me! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #12 from Sarah <slg...@hotmail.co.uk> --- (In reply to Boudewijn Rempt from comment #11) > Hi Sarah, > > What is your exact monitor configuration and resolution? Hi I have two monitors. My main monitor has a resolution of 1920 x 1080, this is the monitor the tablet is configured to respond to (specifically I have been told that the tablet is mapped to monitor 1 only - which is not the TV). My other monitor is an older widescreen TC, the resolution is 1280 x 720. So I am dual screening I think. Thanks for the speedy reply! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 --- Comment #9 from Sarah <slg...@hotmail.co.uk> --- Created attachment 99139 --> https://bugs.kde.org/attachment.cgi?id=99139=edit Krita debug file when attempting to use Trust Tablet TB7300 Krita debug file when attempting to use Trust Tablet TB7300 on latest 3.0 release. Thanks! <3 :D -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362948] [PERITAB] Krita crashes if I touch the tablet with the pen
https://bugs.kde.org/show_bug.cgi?id=362948 Sarah <slg...@hotmail.co.uk> changed: What|Removed |Added CC||slg...@hotmail.co.uk --- Comment #8 from Sarah <slg...@hotmail.co.uk> --- (In reply to Boudewijn Rempt from comment #7) > Okay, so you didn't get a backtrace when testing the -dbg build? Hello. I think I have the same sort of problem. I use a Trust TB7300 (so old it's not even sold anymore but old faithful still works! But I understand you probably might not be able to do testing yourself <3) It didn't work on 2.7-2.9 releases but the Version: 3.1 Alpha (git be 28b 1b) it works! YAY! I tried the most recent 'bleeding' release announced on FB 18/05/16. Again it works fine until I touch the pen to the tablet whereupon Krita immediately crashes. My partner found out how to do a bug report and I will attach it to this message just as soon as I work out how to. Thanks for making such a wonderful art programme which has meant I can pursue my hobby btw! It really is wonderful! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359673] New: 4k Multi-Screen Graphics Drawing Size Incorrect
https://bugs.kde.org/show_bug.cgi?id=359673 Bug ID: 359673 Summary: 4k Multi-Screen Graphics Drawing Size Incorrect Product: plasmashell Version: 5.5.4 Platform: Compiled Sources OS: other Status: UNCONFIRMED Severity: crash Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: sarahsp...@gmail.com CC: plasma-b...@kde.org When hooking up two screens, a 4k screen, and a 1080p screen, and setting the font to an appropriate size in the 4k screen- This results in the display of fonts and the appearance of elements in the 1080p screen to be very large. Request separate font and element scaling options for multi-screen setups (for example scale to 1.5 on the 4k screen, and scale to 1.0 on 1080p screen). Reproducible: Always Steps to Reproduce: 1. Set up two monitors - 4k screen and 1080p screen. 2. Change display appearance to scale fonts for 4k screen. 3. Look at very large windows on 1080p screen. Actual Results: Very large scaling on 1080p screen which is unwanted. Expected Results: 1080p screen should have elements that are a normal size so it is usable. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 357347] KDevelop can't parse K function definitions
https://bugs.kde.org/show_bug.cgi?id=357347 --- Comment #2 from Sarah Day <sarah...@mit.edu> --- That's fine! I just pulled the KDevelop beta from Fedora Rawhide and it works :) Thanks for your help! -- You are receiving this mail because: You are watching all bug changes.
