[kdevelop] [Bug 371641] New: KDevelop Icon style can not be customized.
https://bugs.kde.org/show_bug.cgi?id=371641 Bug ID: 371641 Summary: KDevelop Icon style can not be customized. Product: kdevelop Version: 5.0.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: UI: general Assignee: kdevelop-bugs-n...@kde.org Reporter: reeves...@gmail.com The lack of themability in KDevelope appears to be by design. This didn't bother me until I tried using 5.0.2. The first thing I noticed was that KDevelope is not distributed in a single "appimage" file. This makes the icons it uses by default in accessible for any sort of unsupported mod without rebuilding the whole thing. Unfortunately the chosen default icons are breeze themed. Which means gray scale toolbar icons. I don't use the breaze theme on my desktop and that's why. KDevelope should be made theme able to match the system theme regardless of what that is. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kdebugsettings] [Bug 356700] Segmentation fault after saving to a file and pressing OK
https://bugs.kde.org/show_bug.cgi?id=356700 michaelchanged: What|Removed |Added CC||reeves...@gmail.com --- Comment #4 from michael --- Patch seems to fix the problem on my system. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 --- Comment #9 from Michael--- Yes, nouveau driver (OpenGL ES 3.0 Mesa 12.0.3) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 --- Comment #4 from Michael--- Any news here? Facing the same problem (same with akregator) Version kmail2 5.3.0 (QtWebEngine) KDE Frameworks 5.26.0 Qt 5.6.1 (kompiliert gegen 5.6.1) Fedora 24 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 368445] kmail2 (v5.3.0) crashes : [warn] epoll_wait: Bad file descriptor
https://bugs.kde.org/show_bug.cgi?id=368445 Michaelchanged: What|Removed |Added CC||miga_m...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368899] New: .desktop starter containing cmdline won't be executed anymore
https://bugs.kde.org/show_bug.cgi?id=368899 Bug ID: 368899 Summary: .desktop starter containing cmdline won't be executed anymore Product: plasmashell Version: 5.7.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Dashboard Assignee: notm...@gmail.com Reporter: ila...@gmail.com CC: bhus...@gmail.com I've a desktop starter which opens a ssh connection. This did work before and suddenly it won't anymore. Tested on my workstation and notebook (both Arch Linux) here is the .desktop file: [Desktop Entry] Comment[de_DE]= Comment= Exec=ssh 192.168.1.123 -l foo GenericName[de_DE]= GenericName= Icon=/home/foo/Bilder/icons/NAS.png MimeType= Name[de_DE]=NAS Name=NAS Path=/home/foo/ StartupNotify=true Terminal=true TerminalOptions=\s--noclose Type=Application X-DBUS-ServiceName= X-DBUS-StartupType= X-KDE-SubstituteUID=false X-KDE-Username= Reproducible: Always Steps to Reproduce: 1. Create a new starter on desktop Enter a valid commandline. Set execute in terminal and keep window opened after program ended (in extended options) 2. Start the desktop shortcut from desktop 3. Actual Results: nothing Expected Results: open a terminal/konsole window and execute the commandline journalctl -xe klauncher[846]: -miniicon isn't supported anymore (service "NAS" ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366744] Several on start: No monitor specified for screen "Default Screen ... KDE debug won't install... Decorations
https://bugs.kde.org/show_bug.cgi?id=366744 --- Comment #2 from Michael--- I am now getting repeatable error pattern: Boot to plasma screen works OK. Cadence does not complete and appears on screen. Manual completion of ALSA audio for "Alsa->Loop=->Jack" and close Cadence. Open either Thunderbird mail or Firefox browser. Select an action that will open a new window. Crash will occur. (NOTE: crashes will now occur in the background, using up all of crash space but not showing in user notifications) Restart of kwin (win_x11 --crashes 1) is automatic (not instigated by myself) root@dad314159:/var/crash# ps -elf | grep kwin 0 S dad 6421 1 0 80 0 - 888134 poll_s 11:08 ? 00:00:27 /usr/bin/kwin_x11 --crashes 1 0 S dad 6422 5259 0 80 0 - 377912 poll_s 11:08 ? 00:00:04 /usr/lib/x86_64-linux-gnu/libexec/drkonqi -platform xcb -display :0 --appname kwin_x11 --apppath /usr/bin --signal 11 --pid 5464 --appversion 5.6.5 --programname KWin --bugaddress sub...@bugs.kde.org --startupid 0 0 S root 28619 7231 0 80 0 - 3220 pipe_w 12:39 pts/100:00:00 grep --color=auto kwin Still cannot install kwin debug so setting up sysky debug instead. I did a wuick look at what crash data I have before reboot with sysky: root@dad314159:/var/crash# tail -n100 _usr* 7f0cf6bda000-7f0cf6bdb000 r--p 2000 08:09 1595595 /lib/x86_64-linux-gnu/libdl-2.23.so 7f0cf6bdb000-7f0cf6bdc000 rw-p 3000 08:09 1595595 /lib/x86_64-linux-gnu/libdl-2.23.so 7f0cf6bdc000-7f0cf6d9c000 r-xp 08:09 1595589 /lib/x86_64-linux-gnu/libc-2.23.so 7f0cf6d9c000-7f0cf6f9b000 ---p 001c 08:09 1595589 /lib/x86_64-linux-gnu/libc-2.23.so 7f0cf6f9b000-7f0cf6f9f000 r--p 001bf000 08:09 1595589 /lib/x86_64-linux-gnu/libc-2.23.so 7f0cf6f9f000-7f0cf6fa1000 rw-p 001c3000 08:09 1595589 /lib/x86_64-linux-gnu/libc-2.23.so 7f0cf6fa1000-7f0cf6fa5000 rw-p 00:00 0 7f0cf6fa5000-7f0cf6fbd000 r-xp 08:09 1595503 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f0cf6fbd000-7f0cf71bc000 ---p 00018000 08:09 1595503 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f0cf71bc000-7f0cf71bd000 r--p 00017000 08:09 1595503 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f0cf71bd000-7f0cf71be000 rw-p 00018000 08:09 1595503 /lib/x86_64-linux-gnu/libpthread-2.23.so 7f0cf71be000-7f0cf71c2000 rw-p 00:00 0 7f0cf71c2000-7f0cf71e8000 r-xp 08:09 1585850 /lib/x86_64-linux-gnu/ld-2.23.so 7f0cf720e000-7f0cf724e000 rw-p 00:00 0 7f0cf724e000-7f0cf737e000 r--p 08:09 1216067 /usr/lib/locale/el_GR.utf8/LC_COLLATE 7f0cf737e000-7f0cf7383000 rw-p 00:00 0 7f0cf7386000-7f0cf73d4000 r--p 08:09 1216074 /usr/lib/locale/el_GR.utf8/LC_CTYPE 7f0cf73d4000-7f0cf73d5000 r--p 08:09 1879246 /usr/lib/locale/cy_GB.utf8/LC_NUMERIC 7f0cf73d5000-7f0cf73d6000 r--p 08:09 2356865 /usr/lib/locale/en_US.utf8/LC_TIME 7f0cf73d6000-7f0cf73d7000 r--p 08:09 2356861 /usr/lib/locale/en_US.utf8/LC_MONETARY 7f0cf73d7000-7f0cf73d8000 r--p 08:09 2273448 /usr/lib/locale/ug_CN/LC_MESSAGES/SYS_LC_MESSAGES 7f0cf73d8000-7f0cf73d9000 r--p 08:09 2273214 /usr/lib/locale/es_PA.utf8/LC_PAPER 7f0cf73d9000-7f0cf73da000 r--p 08:09 1879247 /usr/lib/locale/cy_GB.utf8/LC_NAME 7f0cf73da000-7f0cf73db000 r--p 08:09 2356862 /usr/lib/locale/en_US.utf8/LC_ADDRESS 7f0cf73db000-7f0cf73dc000 r--p 08:09 2273828 /usr/lib/locale/tl_PH.utf8/LC_TELEPHONE 7f0cf73dc000-7f0cf73dd000 r--p 08:09 2355924 /usr/lib/locale/yi_US.utf8/LC_MEASUREMENT 7f0cf73dd000-7f0cf73e4000 r--s 08:09 1331088 /usr/lib/x86_64-linux-gnu/gconv/gconv-modules.cache 7f0cf73e4000-7f0cf73e5000 r--p 08:09 2356864 /usr/lib/locale/en_US.utf8/LC_IDENTIFICATION 7f0cf73e5000-7f0cf73e7000 rw-p 00:00 0 7f0cf73e7000-7f0cf73e8000 r--p 00025000 08:09 1585850 /lib/x86_64-linux-gnu/ld-2.23.so 7f0cf73e8000-7f0cf73e9000 rw-p 00026000 08:09 1585850 /lib/x86_64-linux-gnu/ld-2.23.so 7f0cf73e9000-7f0cf73ea000 rw-p 00:00 0 7ffc1b29-7ffc1b2b1000 rw-p 00:00 0 [stack] 7ffc1b3ce000-7ffc1b3d r--p 00:00 0 [vvar] 7ffc1b3d-7ffc1b3d2000 r-xp 00:00 0 [vdso] ff60-ff601000 r-xp 00:00 0 [vsyscall] ProcStatus: Name: python3 State: R (running) Tgid: 5105 Ngid: 0 Pid: 5105 PPid: 5091 TracerPid: 0
[drkonqi] [Bug 326070] Crash handler fails to install debug symbols
https://bugs.kde.org/show_bug.cgi?id=326070 --- Comment #9 from Michael--- The problem occurs whenever I open either Firefox or Thunderbird for the first time following a boot up. Once this has happened, it rarely happens again. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 326070] Crash handler fails to install debug symbols
https://bugs.kde.org/show_bug.cgi?id=326070 --- Comment #8 from Michael--- Created attachment 100828 --> https://bugs.kde.org/attachment.cgi?id=100828=edit Back trace from log files. May need others but not sure what to provide. Additional info. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 326070] Crash handler fails to install debug symbols
https://bugs.kde.org/show_bug.cgi?id=326070 Michaelchanged: What|Removed |Added CC||mwinth...@comcast.net --- Comment #7 from Michael --- Created attachment 100827 --> https://bugs.kde.org/attachment.cgi?id=100827=edit Att-1 Fail to install kde debug I do not understand why this persists. Totally repeatable. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 367657] gewnview crash after opening an image in dolphin
https://bugs.kde.org/show_bug.cgi?id=367657 Michaelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Michael --- Solved by changing (downgrading) vendor of libexiv2-14 back to OpenSuse default repository -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 367657] gewnview crash after opening an image in dolphin
https://bugs.kde.org/show_bug.cgi?id=367657 Michaelchanged: What|Removed |Added Version|unspecified |Other (add details in bug ||description) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 367657] New: gewnview crash after opening an image in dolphin
https://bugs.kde.org/show_bug.cgi?id=367657 Bug ID: 367657 Summary: gewnview crash after opening an image in dolphin Product: gwenview Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: michaeljohannpe...@gmail.com CC: myr...@kde.org Application: gwenview (16.04.3) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.7.0-2-default x86_64 Distribution: "openSUSE Tumbleweed (20160812) (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Clicked on a jpg image in dolphin. Gwenview immediatly crashes. The image can be opend with GIMP. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f45519549c0 (LWP 12215))] Thread 4 (Thread 0x7f45297a2700 (LWP 12218)): [KCrash Handler] #6 0x7f454b6a28c2 in Exiv2::Exifdatum::Exifdatum(Exiv2::Exifdatum const&) () at /usr/lib64/libexiv2.so.14 #7 0x7f455109690a in () at /usr/lib64/libgwenviewlib.so.5 #8 0x7f455109535a in Gwenview::JpegContent::loadFromData(QByteArray const&, Exiv2::Image*) () at /usr/lib64/libgwenviewlib.so.5 #9 0x7f455105d862 in () at /usr/lib64/libgwenviewlib.so.5 #10 0x7f455105b901 in () at /usr/lib64/libgwenviewlib.so.5 #11 0x7f454c9675df in () at /usr/lib64/libQt5Core.so.5 #12 0x7f454c96b2d8 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f454643e474 in start_thread () at /lib64/libpthread.so.0 #14 0x7f454c2763ed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f4533fff700 (LWP 12217)): #0 0x7f4545f630a9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7f4545f1f03b in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f4545f1f16c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f454cb98aeb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f454cb4076a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f454c9663b3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f454bf199b5 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f454c96b2d8 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f454643e474 in start_thread () at /lib64/libpthread.so.0 #9 0x7f454c2763ed in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f4539eaa700 (LWP 12216)): #0 0x7f454c26da1d in poll () at /lib64/libc.so.6 #1 0x7f4543fd43c2 in () at /usr/lib64/libxcb.so.1 #2 0x7f4543fd610f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f453bde47b9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f454c96b2d8 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f454643e474 in start_thread () at /lib64/libpthread.so.0 #6 0x7f454c2763ed in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f45519549c0 (LWP 12215)): #0 0x7f454644409f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f454c96c18b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f454bf717db in () at /usr/lib64/libQt5DBus.so.5 #3 0x7f454bf2b6ec in () at /usr/lib64/libQt5DBus.so.5 #4 0x7f454bf2b88c in () at /usr/lib64/libQt5DBus.so.5 #5 0x7f454bf34bdb in () at /usr/lib64/libQt5DBus.so.5 #6 0x7f454bf35704 in QDBusAbstractInterface::QDBusAbstractInterface(QString const&, QString const&, char const*, QDBusConnection const&, QObject*) () at /usr/lib64/libQt5DBus.so.5 #7 0x7f455134b846 in () at /usr/lib64/libKF5Activities.so.5 #8 0x7f4551341315 in () at /usr/lib64/libKF5Activities.so.5 #9 0x7f45513418e3 in () at /usr/lib64/libKF5Activities.so.5 #10 0x7f455134011f in () at /usr/lib64/libKF5Activities.so.5 #11 0x7f45513402a9 in () at /usr/lib64/libKF5Activities.so.5 #12 0x7f45513396ba in KActivities::ResourceInstance::setUri(QUrl const&) () at /usr/lib64/libKF5Activities.so.5 #13 0x0043ed2d in () #14 0x0044011f in () #15 0x00456cb2 in () #16 0x004561d9 in () #17 0x00434347 in () #18 0x7f454c1ae741 in __libc_start_main () at /lib64/libc.so.6 #19 0x00434849 in _start () Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[analitza] [Bug 367522] New: Contact Norton Support –+1-877-523-3678 Norton Phone Number, and Chat Support options
https://bugs.kde.org/show_bug.cgi?id=367522 Bug ID: 367522 Summary: Contact Norton Support –+1-877-523-3678 Norton Phone Number, and Chat Support options Product: analitza Version: unspecified Platform: Gentoo Packages OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: analitzaplot Assignee: aleix...@kde.org Reporter: leemichael.exp...@gmail.com CC: percy.camilo...@gmail.com USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number USAtralia USA-1 877-523-3678++ Norton 360 support phone number Norton tech support phone number Norton 360 Tech Support Number USA USA-1 877-523-3678++ Norton 360 support phone number USA-1 877-523-3678USA/canada Norton 360 Tech Support Number @@!1-800-750-6584;!!Norton 360 Support Number Norton Live Support and Help 1 8(77-523-3678 @@ Norton tech support phone number Norton Live Support and Help 1 8(77-523-3678 @@ Norton tech support phone number Norton Live Support and Help 1 8(77-523-3678 Norton 360 support phone number USA USA Canada USA-1 877-523-3678++ Norton 360 support phone number USA-1 877-523-3678USA/canada Norton 360 Tech Support Number @@!1-800-750-6584;!!Norton 360 Support Number WikiGenes- @+++1800-750-6584++000Norton 360 support phone number18775233678USA/canada Norton antivirus technical support phone number 1.877-523-3678 hdfc toll free customer care number(((!1.877-523-3678)) Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678> Norton technical support phone number ((1.877-523-3678)) Norton technical support number 1.877-523-3678 Norton technical support number 1.877-523-3678 symantec technical support number 1.877-523-3678 Norton antivirus technical support number 1.877-523-3678 Norton support phone number 1.877-523-3678 Norton locations Norton 360 Tech Support Number @@!1.877-523-3678!! Norton 360 Support Number Norton 360 Tech Support Number @@!1.877-523-3678!! Norton 360 Support Number Norton customer service Norton antivirus customer care__Norton Support phone number 1.877-523-3678 Norton customer support phone number 1.877-523-3678 Norton customer support phone number 1.877-523-3678 Norton antivirus customer support phone number 1.877-523-3678Norton antivirus customer service phone number 1.877-523-3678 Norton antivirus technical support phone number 1.877-523-3678 Norton antivirus tech support phone number 1.877-523-3678 Norton antivirus phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton security center phone number 1.877-523-3678 Norton support telephone number 1.877-523-3678 Norton 360 technical support phone number 1.877-523-3678 symantec technical support phone number 1.877-523-3678 Norton tech support phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number apple technical support phone number 1.877-523-3678 USA microsoft technical support phone number 1.877-523-3678 USA gmail technical support phone number 1.877-523-3678 USA kaspersky technical support phone number 1.877-523-3678 USA lenovo technical support phone number 1.877-523-3678 USA epson technical support phone number 1.877-523-3678 USA Norton technical support phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton AntiVirus Customer Service Phone Number #1: 800-750-6584 Norton Phone number 1-800-750-6584 Norton 360 phone number Norton 360 support phone number Free~* C@ll 1.877-523-3678 Norton 360 technical support phone number USA 1.877-523-3678 Norton 360 technical support phone number Norton free call ~* C@ll 1.877-523-3678 Norton 360 technical support phone number USA 1.877-523-3678 Norton 360 technical support phone number Norton free call Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number PHONE support USA @1.877-523-3678 Norton antivirus technical support phone number Norton locations Norton online support Norton Support phone number 1.877-523-3678 Norton customer care Norton tech support phone number 1.877-523-3678 Norton tech support phone number 1.877-523-3678 Norton antivirus tech support phone number 1.877-523-3678 Norton locations Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton Support phone number 1.877-523-3678 service Norton com Norton login Norton technical support phone number 1.877-523-3678 Norton customer service
[amarok] [Bug 367515] New: USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number
https://bugs.kde.org/show_bug.cgi?id=367515 Bug ID: 367515 Summary: USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number Product: amarok Version: 2.8.90 (2.9 beta) Platform: Android URL: https://jogamp.org/bugzilla/show_bug.cgi?id=5266 OS: Windows CE Status: UNCONFIRMED Severity: normal Priority: NOR Component: Collections/CD Assignee: amarok-bugs-d...@kde.org Reporter: leemichael.exp...@gmail.com Chal ja tujhsai naoton +18775233678+norton antivirus technical support number USA +18775233678+18775233678+norton tech support number usa+18775233678+18775233678+18775233678 na hoga USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number USAtralia USA-1 877-523-3678++ Norton 360 support phone number Norton tech support phone number Norton 360 Tech Support Number USA USA-1 877-523-3678++ Norton 360 support phone number USA-1 877-523-3678USA/canada Norton 360 Tech Support Number @@!1-800-750-6584;!!Norton 360 Support Number Norton Live Support and Help 1 8(77-523-3678 @@ Norton tech support phone number Norton Live Support and Help 1 8(77-523-3678 @@ Norton tech support phone number Norton Live Support and Help 1 8(77-523-3678 Norton 360 support phone number USA USA Canada USA-1 877-523-3678++ Norton 360 support phone number USA-1 877-523-3678USA/canada Norton 360 Tech Support Number @@!1-800-750-6584;!!Norton 360 Support Number WikiGenes- @+++1800-750-6584++000Norton 360 support phone number18775233678USA/canada Norton antivirus technical support phone number 1.877-523-3678 hdfc toll free customer care number(((!1.877-523-3678)) Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678> Norton technical support phone number ((1.877-523-3678)) Norton technical support number 1.877-523-3678 Norton technical support number 1.877-523-3678 symantec technical support number 1.877-523-3678 Norton antivirus technical support number 1.877-523-3678 Norton support phone number 1.877-523-3678 Norton locations Norton 360 Tech Support Number @@!1.877-523-3678!! Norton 360 Support Number Norton 360 Tech Support Number @@!1.877-523-3678!! Norton 360 Support Number Norton customer service Norton antivirus customer care__Norton Support phone number 1.877-523-3678 Norton customer support phone number 1.877-523-3678 Norton customer support phone number 1.877-523-3678 Norton antivirus customer support phone number 1.877-523-3678Norton antivirus customer service phone number 1.877-523-3678 Norton antivirus technical support phone number 1.877-523-3678 Norton antivirus tech support phone number 1.877-523-3678 Norton antivirus phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton security center phone number 1.877-523-3678 Norton support telephone number 1.877-523-3678 Norton 360 technical support phone number 1.877-523-3678 symantec technical support phone number 1.877-523-3678 Norton tech support phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number apple technical support phone number 1.877-523-3678 USA microsoft technical support phone number 1.877-523-3678 USA gmail technical support phone number 1.877-523-3678 USA kaspersky technical support phone number 1.877-523-3678 USA lenovo technical support phone number 1.877-523-3678 USA epson technical support phone number 1.877-523-3678 USA Norton technical support phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton AntiVirus Customer Service Phone Number #1: 800-750-6584 Norton Phone number 1-800-750-6584 Norton 360 phone number Norton 360 support phone number Free~* C@ll 1.877-523-3678 Norton 360 technical support phone number USA 1.877-523-3678 Norton 360 technical support phone number Norton free call ~* C@ll 1.877-523-3678 Norton 360 technical support phone number USA 1.877-523-3678 Norton 360 technical support phone number Norton free call Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number PHONE support USA @1.877-523-3678 Norton antivirus technical support phone number Norton locations Norton online support Norton Support phone number 1.877-523-3678 Norton customer care Norton tech support phone number 1.877-523-3678 Norton tech support phone number 1.877-523-3678 Norton antivirus tech support phone
[akunambol] [Bug 367514] New: sade sab kuch +18775233678+norton antivirus technical support number USA +18775233678+18775233678+norton tech support number usa+18775233678+18775233678+18775233678
https://bugs.kde.org/show_bug.cgi?id=367514 Bug ID: 367514 Summary: sade sab kuch +18775233678+norton antivirus technical support number USA +18775233678+18775233678+norton tech support number usa+18775233678+18775233678+18775233678 Product: akunambol Version: 0.2.1 Platform: FreeBSD Ports URL: https://bugs.kde.org/show_bug.cgi?id=367513 OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: syncronization Assignee: m.gara...@gmail.com Reporter: leemichael.exp...@gmail.com CC: ricca...@kde.org USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number USA..1 877-523-3678++ Norton 360 support phone number om Norton tech support phone number Norton 360 Tech Support Number USAtralia USA-1 877-523-3678++ Norton 360 support phone number Norton tech support phone number Norton 360 Tech Support Number USA USA-1 877-523-3678++ Norton 360 support phone number USA-1 877-523-3678USA/canada Norton 360 Tech Support Number @@!1-800-750-6584;!!Norton 360 Support Number Norton Live Support and Help 1 8(77-523-3678 @@ Norton tech support phone number Norton Live Support and Help 1 8(77-523-3678 @@ Norton tech support phone number Norton Live Support and Help 1 8(77-523-3678 Norton 360 support phone number USA USA Canada USA-1 877-523-3678++ Norton 360 support phone number USA-1 877-523-3678USA/canada Norton 360 Tech Support Number @@!1-800-750-6584;!!Norton 360 Support Number WikiGenes- @+++1800-750-6584++000Norton 360 support phone number18775233678USA/canada Norton antivirus technical support phone number 1.877-523-3678 hdfc toll free customer care number(((!1.877-523-3678)) Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678 Norton toll free customer care number 1.877-523-3678> Norton technical support phone number ((1.877-523-3678)) Norton technical support number 1.877-523-3678 Norton technical support number 1.877-523-3678 symantec technical support number 1.877-523-3678 Norton antivirus technical support number 1.877-523-3678 Norton support phone number 1.877-523-3678 Norton locations Norton 360 Tech Support Number @@!1.877-523-3678!! Norton 360 Support Number Norton 360 Tech Support Number @@!1.877-523-3678!! Norton 360 Support Number Norton customer service Norton antivirus customer care__Norton Support phone number 1.877-523-3678 Norton customer support phone number 1.877-523-3678 Norton customer support phone number 1.877-523-3678 Norton antivirus customer support phone number 1.877-523-3678Norton antivirus customer service phone number 1.877-523-3678 Norton antivirus technical support phone number 1.877-523-3678 Norton antivirus tech support phone number 1.877-523-3678 Norton antivirus phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton security center phone number 1.877-523-3678 Norton support telephone number 1.877-523-3678 Norton 360 technical support phone number 1.877-523-3678 symantec technical support phone number 1.877-523-3678 Norton tech support phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number apple technical support phone number 1.877-523-3678 USA microsoft technical support phone number 1.877-523-3678 USA gmail technical support phone number 1.877-523-3678 USA kaspersky technical support phone number 1.877-523-3678 USA lenovo technical support phone number 1.877-523-3678 USA epson technical support phone number 1.877-523-3678 USA Norton technical support phone number 1.877-523-3678 Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number Norton AntiVirus Customer Service Phone Number #1: 800-750-6584 Norton Phone number 1-800-750-6584 Norton 360 phone number Norton 360 support phone number Free~* C@ll 1.877-523-3678 Norton 360 technical support phone number USA 1.877-523-3678 Norton 360 technical support phone number Norton free call ~* C@ll 1.877-523-3678 Norton 360 technical support phone number USA 1.877-523-3678 Norton 360 technical support phone number Norton free call Norton 360 Tech Support Number @@!1-800-750-6584!! Norton 360 Support Number PHONE support USA @1.877-523-3678 Norton antivirus technical support phone number Norton locations Norton online support Norton Support phone number 1.877-523-3678 Norton customer care Norton tech support phone number 1.877-523-3678 Norton tech support phone number 1.877-523-3678 Norton antivirus tech support phone number 1.877-523-3678 Norton locations Norton 360 Tech Support Number @@!1-800-750-6584!! Norton
[kdm] [Bug 105631] fully support alternative authentication methods
https://bugs.kde.org/show_bug.cgi?id=105631 Michaelchanged: What|Removed |Added CC||kmhess...@web.de --- Comment #73 from Michael --- Same here: Kubuntu 16.04. Please fix the problem, it's really poor not to have the fingerprint-reader. Please consider the time used and act soon! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 366744] New: Several on start: No monitor specified for screen "Default Screen ... KDE debug won't install... Decorations
https://bugs.kde.org/show_bug.cgi?id=366744 Bug ID: 366744 Summary: Several on start: No monitor specified for screen "Default Screen ... KDE debug won't install... Decorations Product: plasmashell Version: master Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mwinth...@comcast.net CC: bhus...@gmail.com, plasma-b...@kde.org (1) On startup with kubuntu 16.04 sddm sometimes starts. Other times: on start: No monitor specified for screen "Default Screen Section". Cannot start default from recovery screens. I usually perform F1 and log in. Then I run startx. After a few of these, the GUI login may return (sddm) (2) Once running, using synaptic I tried to install kde* debug. I get a failure as follows: The following packages have unmet dependencies: kded5-dbg : Depends: kded5 (= 5.18.0-0ubuntu1) but 5.23.0-0ubuntu1~ubuntu16.04~ppa1 is to be installed kdeplasma-addons-dbg : Depends: plasma-dataengines-addons (= 4:5.5.5-0ubuntu1) but 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1 is to be installed or plasma-runners-addons (= 4:5.5.5-0ubuntu1) but 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1 is to be installed or plasma-wallpapers-addons (= 4:5.5.5-0ubuntu1) but 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1 is to be installed or plasma-widgets-addons (= 4:5.5.5-0ubuntu1) but 4:5.6.5-0ubuntu1~ubuntu16.04~ppa1 is to be installed kdesignerplugin-dbg : Depends: kgendesignerplugin (= 5.18.0-0ubuntu1) but 5.23.0-0ubuntu1~ubuntu16.04~ppa1 is to be installed I am using plasma, and trying to have kubuntu-desktop, which I have reinstalled a few times and run: apt-get build-dep kubuntu-desktop There are no missing items. apt-get install --reinstall kubuntu-desktop same as before (3) Pianoteq application has no window decorations even when all other applications do (??) Background: I was running ubuntu 14.04 KXStudio. No problems. When the option to upgrade to kubuntu to 16.04, I used it from muon updater. From then to now, about three weeks, misery. It crashed at the very end of the install. I have been piecing together the packages, but cannot find an application that will review what is needed and what is present, then offer to complete3 the install. I have a DVD with K 16.04.1 but it is not willing to assure me that it is working on the sda9 slice and will not identify the root partition on its own. (4) I tried to install patchage and had more grief about dependencies on older packages Reproducible: Always Steps to Reproduce: 1. item (2) sudo apt-get --fix-missing --with-new-pkgs upgrade kde* or sudo apt-get install --reinstall kde* 2. 3. Actual Results: root@dad314159:/home/dad/Desktop# apt-get --fix-missing --with-new-pkgs upgrade kde* Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'kde-baseapps-bin' for glob 'kde*' Note, selecting 'kde-config-fcitx' for glob 'kde*' Note, selecting 'kde-runtime-data' for glob 'kde*' Note, selecting 'kde-telepathy-data' for glob 'kde*' Note, selecting 'kdelibs4c2a' for glob 'kde*' Note, selecting 'kde-notification-colibri' for glob 'kde*' Note, selecting 'kdevelop-php-docs-l10n-nds' for glob 'kde*' Note, selecting 'kdevelop-l10n-ptbr' for glob 'kde*' Note, selecting 'kde-thumbnailer-openoffice' for glob 'kde*' Note, selecting 'kde-baseapps-dbg' for glob 'kde*' Note, selecting 'kdelibs-bin' for glob 'kde*' Note, selecting 'kdelibs-data' for glob 'kde*' Note, selecting 'kde-telepathy-contact-list' for glob 'kde*' Note, selecting 'kdeartwork-theme-window' for glob 'kde*' Note, selecting 'kde-config-sddm-dbg' for glob 'kde*' Note, selecting 'kde-icons-crystal' for glob 'kde*' Note, selecting 'kdepim-runtime' for glob 'kde*' Note, selecting 'kdebase-runtime-dbg' for glob 'kde*' Note, selecting 'kdesdk-dolphin-plugins' for glob 'kde*' Note, selecting 'kdevelop-l10n' for glob 'kde*' Note, selecting 'kdeconnect' for glob 'kde*' Note, selecting 'kdevelop-php-l10n-cavalencia' for glob 'kde*' Note, selecting 'kdevelop-l10n-engb' for glob 'kde*' Note, selecting 'kdevelop-dbg' for glob 'kde*' Note, selecting 'kdevelop-dev' for glob 'kde*' Note, selecting 'kdelibs-dbg' for glob 'kde*' Note, selecting 'kdevelop-doc' for glob 'kde*' Note, selecting 'kde-config-touchpad' for glob 'kde*' Note, selecting 'kdebase-workspace-bin' for glob 'kde*' Note, selecting 'kdeartwork-style' for glob 'kde*' Note, selecting 'kde-cli-tools' for glob 'kde*' Note, selecting 'kde-config-gtk-style' for glob 'kde*' Note, selecting 'kde4pimlibs-dbg' for glob 'kde*' Note, selecting 'kde-config-cddb' for glob 'kde*' Note, selecting 'kdebase-workspace-dbg' for
[krita] [Bug 366243] Something's really wrong with the update scheduler/kisstroke/etc.
https://bugs.kde.org/show_bug.cgi?id=366243 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #7 from Michael --- I'm getting crashes with the Transform tool that may be related. #0 0x750a8418 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #1 0x750aa01a in __GI_abort () at abort.c:89 #2 0x750ea72a in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x752036b0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #3 0x750f4f01 in malloc_printerr (ar_ptr=0x3, ptr=, str=0x75203ab8 "malloc(): memory corruption (fast)", action=3) at malloc.c:5007 #4 _int_malloc (av=av@entry=0x75436b20 , bytes=bytes@entry=8) at malloc.c:3387 #5 0x750f65a4 in __GI___libc_malloc (bytes=8) at malloc.c:2914 #6 0x75c857f9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7371cbf9 in KisQueuesProgressUpdater::sigStartTicking() () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #8 0x7356c089 in KisQueuesProgressUpdater::updateProgress(int, QString const&) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #9 0x735692d2 in KisUpdateScheduler::progressUpdate() () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #10 0x7356a30a in KisUpdateScheduler::processQueues() () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #11 0x73569b7c in KisUpdateScheduler::endStroke(QWeakPointer) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #12 0x735891f9 in KisImage::endStroke(QWeakPointer) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #13 0x7fffc669f420 in KisToolTransform::endStroke() () from /home/abrahams/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so #14 0x7fffc669e336 in KisToolTransform::requestStrokeEnd() () from /home/abrahams/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so #15 0x7fffc6737bae in KisToolTransform::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /home/abrahams/lib/x86_64-linux-gnu/kritaplugins/kritatooltransform.so #16 0x75c85bc9 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x73719feb in KisImage::sigStrokeEndRequested() () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #18 0x7358936e in KisImage::requestStrokeEnd() () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #19 0x73588ca3 in KisImage::startStroke(KisStrokeStrategy*) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #20 0x7367b4ea in KisProcessingApplicator::KisProcessingApplicator(KisWeakSharedPtr, KisSharedPtr, QFlags, QVector, KUndo2MagicString const&, KUndo2CommandExtraData*, int) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaimage.so.15 #21 0x775a32ef in KisNodeJugglerCompressed::KisNodeJugglerCompressed(KUndo2MagicString const&, KisSharedPtr, KisNodeManager*, int) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #22 0x7759a0ec in KisNodeManager::Private::lazyGetJuggler(KUndo2MagicString const&) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #23 0x775972ae in KisNodeManager::moveNodesDirect(QList , KisSharedPtr, KisSharedPtr) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #24 0x775acb1c in KisNodeInsertionAdapter::moveNodes(QList , KisSharedPtr, KisSharedPtr) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #25 0x77591cf6 in KisMimeData::insertMimeLayers(QMimeData const*, KisSharedPtr, KisShapeController*, KisNodeDummy*, KisNodeDummy*, bool, KisNodeInsertionAdapter*) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #26 0x775b0048 in KisNodeModel::dropMimeData(QMimeData const*, Qt::DropAction, int, int, QModelIndex const&) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #27 0x75c0955a in QAbstractProxyModel::dropMimeData(QMimeData const*, Qt::DropAction, int, int, QModelIndex const&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7678d07c in QAbstractItemView::dropEvent(QDropEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x77810b2c in KisNodeView::dropEvent(QDropEvent*) () from /home/abrahams/lib/x86_64-linux-gnu/libkritaui.so.15 #30 0x7658d398 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7667376e in QFrame::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x76798593 in QAbstractItemView::viewportEvent(QEvent*) () from
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #5 from Michael--- Also a usable workaround for me on Neon: export QT_SCREEN_SCALE_FACTORS= && dolphin %u -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365836] "next activity" and "previous activity" shortcuts erratic
https://bugs.kde.org/show_bug.cgi?id=365836 --- Comment #7 from Michael--- I realized I never said thanks. The scripts are just what I was looking for, I appreciate it! -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 353528] QApt Batch Installer window hides authentication dialog
https://bugs.kde.org/show_bug.cgi?id=353528 Michaelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 348530] "Configure Selection" should be renamed to "Reconfigure Selection"
https://bugs.kde.org/show_bug.cgi?id=348530 Michaelchanged: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 348448] Search for "auto login" does not direct to the correct location
https://bugs.kde.org/show_bug.cgi?id=348448 Michaelchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 348618] Crash when cutting with ctrl-x
https://bugs.kde.org/show_bug.cgi?id=348618 Michaelchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 353611] Crash on viewing "Technical Details"
https://bugs.kde.org/show_bug.cgi?id=353611 Michaelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Michael --- Not getting this anymore in KDE Neon -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 --- Comment #4 from Michael--- Took a closer look at this bug since I'd quite like it fixed. In KItemListController.cpp around line 529, the function: bool KItemListController::mousePressEvent(QGraphicsSceneMouseEvent* event, const QTransform& transform) does not seem to be receiving any mouse events when clicking on the left half of the view after the bug is triggered. Debug output is generated from clicks in this part of the screen before opening a file, but after opening a file the debug output is gone. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 363548] file area becomes inaccessible for the mouse after opening a file on hidpi screen when using a multi monitor setting
https://bugs.kde.org/show_bug.cgi?id=363548 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #3 from Michael --- I'm getting the same thing with current KDE Neon. (Plasma 5.6.1, Frameworks 5.24.0, Dolphin 16.04.2) On my center monitor, mouse clicks register correctly on the right half of the Dolphin window but not on the left half. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 366020] New: no confirmation asked when quitting and still recording
https://bugs.kde.org/show_bug.cgi?id=366020 Bug ID: 366020 Summary: no confirmation asked when quitting and still recording Product: kaffeine Version: 2.0.1 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: pante...@web.de Kaffeine Version is 2.0.4 on closing the main window there is a conformation dialogbox if there are still scheduled records or kaffeine is still recording. This dialog is missing on quitting through the menu (File>Quit) or the shortcut Ctrl-Q. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364017] recording schedule with qdbus get disabled tv-records
https://bugs.kde.org/show_bug.cgi?id=364017 Michaelchanged: What|Removed |Added Attachment #100250|0 |1 is patch|| -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364017] recording schedule with qdbus get disabled tv-records
https://bugs.kde.org/show_bug.cgi?id=364017 --- Comment #4 from Michael--- Created attachment 100257 --> https://bugs.kde.org/attachment.cgi?id=100257=edit set recording.disabled to false in dvbEpgModell::scheduleProgram -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364017] recording schedule with qdbus get disabled tv-records
https://bugs.kde.org/show_bug.cgi?id=364017 --- Comment #3 from Michael--- Similar problem appears when scheduling a program through the EPG. You have to "confirm" the scheduling by going into the Edit-dialog for the recording. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 364017] recording schedule with qdbus get disabled tv-records
https://bugs.kde.org/show_bug.cgi?id=364017 --- Comment #2 from Michael--- Created attachment 100250 --> https://bugs.kde.org/attachment.cgi?id=100250=edit set recording.disabled to false on dbus ScheduleProgram -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365836] "next activity" and "previous activity" shortcuts erratic
https://bugs.kde.org/show_bug.cgi?id=365836 --- Comment #5 from Michael--- (In reply to Ivan Čukić from comment #4) > I'm unable to replicate this on a live neon (updated to 5.7.2) > > If I only press meta+tab, meta+tab, meta+tab it alternates between the two > last used activities - pressing meta+tab switches to the previous one (like > with alt+tab for windows). You're right, 'previous activity' alone does not have erratic behavior. The behavior of 'next activity' is erratic. I think the keybindings introduce a bit of a delay, I'll describe how I trigger the race condition. I bind "next activity" and "previous activity" to the forward/back buttons on my mouse. I send dbus commands with xbindkeys. Pressing meta+tab and meta+shift+tab introduces a bit of a delay so the race condition is less obvious. #Previous Activity - forward button "qdbus org.kde.kglobalaccel /component/plasmashell invokeShortcut 'previous activity'" b:9 #Next Activity - back button "qdbus org.kde.kglobalaccel /component/plasmashell invokeShortcut 'next activity'" b:8 > If I press meta+tab,tab,tab, it goes through the list from the most recently > used one to the least recently used one. So perhaps it will make sense why I preferred the behavior in Plasma 5.5: there's no way to bind meta+tab+tab+tab to mouse buttons, and no dbus interface I can use to replicate this. I don't think mimicking behavior similar to alt+tab is a good justification for the change. For one, the activity bar widget does not change around activity order, so there's no longer any useful visual indicator to explain where you're going to go when you press meta+tab or meta+shift+tab. I usually don't care to remember in advance which activity I came from last, I just want to cycle through the activity bar. Next, I expect people using more than 3-4 activities to be extremely small. When there are only 3 activities running there is not really any benefit to changing the order of activities around. Previously, with two shortcuts, there was always one button to map to each alternate activity. With four activities running, only one activity would require more than two presses. Pulling up a large activities sidebar to remind you of all the choices is not as useful. In the alt+tab task switcher case, it makes sense to observe the pop-up if you have 10 or 15 windows open. And finally, activating "previous activity" then "next activity" does not necessarily return you to where you started if you send the commands quickly enough. The commands are non-invertible. On top of those personal workflow preferences there is still the race condition with "next activity." if "previous activity" returns you to the activity you were using previously, what is a sensible behavior for "next activity" if you haven't pressed "previous activity?" There is no next, you're at the end of the line. I think at a minimum sending the 'next activity' command repeatedly shouldn't make the Activity Switcher widget flip around unpredictably. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 348613] Launcher icon disappears
https://bugs.kde.org/show_bug.cgi?id=348613 Michaelchanged: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Michael --- Not getting this anymore. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 349385] Add "Open header file" to context menu when right clicking on a file name
https://bugs.kde.org/show_bug.cgi?id=349385 Michaelchanged: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #2 from Michael --- Wasn't aware, that is good enough! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362056] Baloo crash - Baloo::MetadataMover::moveFileMetadata
https://bugs.kde.org/show_bug.cgi?id=362056 Michaelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Michael --- I upgraded to KDE Neon and this seems like it has been resolved. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362124] Plasma crash when typing and searching in Launcher
https://bugs.kde.org/show_bug.cgi?id=362124 Michaelchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Michael --- I upgraded to KDE Neon and this seems like it was resolved. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365836] "next activity" and "previous activity" shortcuts erratic
https://bugs.kde.org/show_bug.cgi?id=365836 --- Comment #2 from Michael--- Hello - I'm on KDE Neon, so as of today Plasma 5.7.2. It does seem erratic but I think I figured out the pattern. If I press Meta+Q to pull up the activities list, the activities move around the list. The top activity is the current one. "Next Activity" always moves to the second item on the list. "Previous Activity" moves to the last item on the list. So with three activities it's like a shell game, the activities switch around erratically as the list is flipped around with the activity itself changing simultaneously. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities] [Bug 365836] New: "next activity" and "previous activity" shortcuts erratic
https://bugs.kde.org/show_bug.cgi?id=365836 Bug ID: 365836 Summary: "next activity" and "previous activity" shortcuts erratic Product: frameworks-kactivities Version: 5.24.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: miabr...@gmail.com CC: plasma-b...@kde.org Repeatedly pressing meta+tab switches activities in a strange order. Sometimes it is erratic. Sometimes it flips between the current activity and the activity used directly prior to the current one. Pressing and holding meta and pressing tab implements the desired behavior, which is to cycle through all activities one at a time. This was working in Plasma 5.6. Reproducible: Always Steps to Reproduce: 1. Press meta+tab a few times. -- You are receiving this mail because: You are watching all bug changes.
[kaffeine] [Bug 365340] New: When opening .voc audio file error message reads, "Can not find demux plugin for MRL."
https://bugs.kde.org/show_bug.cgi?id=365340 Bug ID: 365340 Summary: When opening .voc audio file error message reads, "Can not find demux plugin for MRL." Product: kaffeine Version: 1.2.2 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: mchehab+...@kernel.org Reporter: mhc...@outlook.com Kaffeine was just installed on Ubuntu 16.04. I did reboot to attempt repair. Reproducible: Always Steps to Reproduce: 1.Either double-click .voc audio file, or 2.Open file from Kaffeine. 3.Same message appears. Actual Results: When opening .voc audio file error message reads, "Can not find demux plugin for MRL." Expected Results: Sound. Apparently something wasn't installed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 364964] New: search function does not recognize spaces within a word
https://bugs.kde.org/show_bug.cgi?id=364964 Bug ID: 364964 Summary: search function does not recognize spaces within a word Product: okular Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: michiball...@googlemail.com When using the search function and typing "example" it will find "example", but it will not find "e x a m p l e". Many OCR software do recognize words written in capital letters as words with spaces. Or some just do mistakes. It would be great if the search function also considers spaces within a word. Reproducible: Always Steps to Reproduce: 1. use a document with spaces within a word e.g. "ex ample" 2. try to search for "example" by using the search function (Ctrl+F) 3. it will not find the word Actual Results: it will not find the word Expected Results: it should find the word Adobe Reader for example does find words with spaces within it. Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363848] Transform tool does not allow rotating by fractions of a degree
https://bugs.kde.org/show_bug.cgi?id=363848 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #1 from Michael --- Transform tool input boxes now expand to 2 decimal places. https://quickgit.kde.org/?p=krita.git=commit=cd45a874b8a834823665eede0199fededb860b9e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 352205] shortcuc ctrl+w cannot be reassigned from default action
https://bugs.kde.org/show_bug.cgi?id=352205 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #4 from Michael --- The shortcuts for "Standard Actions" like open, save, copy, paste use an older configuration system which isn't playing nicely with Krita's shortcut management. Should look into KisActionManager::createStandardAction here... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 220180] Remember selection action setting on switching selection tool
https://bugs.kde.org/show_bug.cgi?id=220180 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #4 from Michael --- Six and a half years later this is implemented (= https://phabricator.kde.org/rKRITAd850ff238bd6b34aa6e5c7438d27d0f9791f3529 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 349782] Add a modifier key for transform tool to make rotation snap to common angles
https://bugs.kde.org/show_bug.cgi?id=349782 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #2 from Michael --- Should be fixed by: https://phabricator.kde.org/rKRITA76255392e01877055f6469f9debb3cc09c46a831 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363373] bezier curve selection tool in release v3.0
https://bugs.kde.org/show_bug.cgi?id=363373 --- Comment #7 from Michael--- Should be resolved now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 363373] bezier curve selection tool in release v3.0
https://bugs.kde.org/show_bug.cgi?id=363373 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #6 from Michael --- https://phabricator.kde.org/D1970 -- You are receiving this mail because: You are watching all bug changes.
[kdesudo] [Bug 353263] No icons show on root session. unable to assign any too.
https://bugs.kde.org/show_bug.cgi?id=353263 michaelchanged: What|Removed |Added CC||reeves...@gmail.com --- Comment #15 from michael --- The workaround fixes it for me too. In my case actually logging in as root from lightdm works as well but presents more of a risk. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361706] [NTRIG] Krita does not recognize a right click performed by Surface Pen while on canvas
https://bugs.kde.org/show_bug.cgi?id=361706 --- Comment #7 from Michael--- I think this is Microsoft's way of saying they really want everyone to implement their Ink API. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361706] [NTRIG] Krita does not recognize a right click performed by Surface Pen while on canvas
https://bugs.kde.org/show_bug.cgi?id=361706 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #5 from Michael --- I don't think I ever got the right click working, I focused on getting the eraser going. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 350082] missing some icons
https://bugs.kde.org/show_bug.cgi?id=350082 michaelchanged: What|Removed |Added CC||reeves...@gmail.com --- Comment #4 from michael --- This appears to be fixed by commit 44d4d2ea715719a08c639541530a5b330647297d which was not back-ported to 15.12.3. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 362045] Running dolphin from CLI (sudo dolphin) shows NO icons (folders, toolbar, or otherwise)!
https://bugs.kde.org/show_bug.cgi?id=362045 michaelchanged: What|Removed |Added CC||reeves...@gmail.com --- Comment #4 from michael --- The problem isn't specific to dolphin. Kate is also affected by this. It seems to be related to the qt5/frameworks transition. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362487] [Huion 610] Cursor is misaligned with brush/tools
https://bugs.kde.org/show_bug.cgi?id=362487 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #5 from Michael --- I racked my brain over this for a long time but couldn't pinpoint the problem. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362470] Prompt dialog asking about divergence between tablet resolution and screen resolution do not pop up
https://bugs.kde.org/show_bug.cgi?id=362470 --- Comment #3 from Michael--- And can you provide some more details about your configuration like your monitor setup, DPI scaling, and tablet mapping settings? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362470] Prompt dialog asking about divergence between tablet resolution and screen resolution do not pop up
https://bugs.kde.org/show_bug.cgi?id=362470 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #2 from Michael --- What sort of offset are you experiencing? The debugview log hasn't captured any tablet events. To enable tablet logging, press Ctrl+Shift+T while a canvas is open and draw some strokes. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 362878] New: Inactive selection settings doesn't apply
https://bugs.kde.org/show_bug.cgi?id=362878 Bug ID: 362878 Summary: Inactive selection settings doesn't apply Product: systemsettings Version: 5.6.3 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_colors Assignee: mwoehlke.fl...@gmail.com Reporter: sexymim...@gmail.com CC: jpwhit...@kde.org Trying to change the settings for inactive selection color doesn't update the settings. Reproducible: Always Steps to Reproduce: 1. Go to systemsettings > colors > options 2. Uncheck "Inactive selection changes color" 3. Apply changes 4. Go back to systemsettings. 5. Go back to colors > options Actual Results: The "Inactive selection changes color" box is still checked. The colors settings haven't changed. Expected Results: The "Inactive selection changes color" box should be unchecked. The colors settings should be updated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362743] Conflicting shortcuts don't get solved with 'reassign'
https://bugs.kde.org/show_bug.cgi?id=362743 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #2 from Michael --- Should be fixed here: https://phabricator.kde.org/rKRITA8b2567b4d186cd188f47c4b1aa20311b4f22728e -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 362825] Error in { : task 1 failed - "could not find function "trellis.last.object""
https://bugs.kde.org/show_bug.cgi?id=362825 --- Comment #3 from Michael--- Error in { : task 1 failed - "could not find function "trellis.last.object"" > getAnywhere("trellis.last.object") A single object matching ‘trellis.last.object’ was found It was found in the following places namespace:lattice with value function (..., prefix = lattice.getStatus("current.prefix")) { if (!lattice.getStatus("current.plot.saved", prefix = prefix)) { warning("Requested 'trellis' object was not saved") return(invisible(NULL)) } ans <- lattice.getStatus("last.object", prefix = prefix) update(ans, ...) } Thank You. On 05/09/2016 12:46 AM, Thomas Friedrichsmeier via KDE Bugzilla wrote: > https://bugs.kde.org/show_bug.cgi?id=362825 > > Thomas Friedrichsmeier changed: > > What|Removed |Added > > CC||thomas.friedrichsmeier@ruhr > ||-uni-bochum.de > > --- Comment #2 from Thomas Friedrichsmeier > --- > Thanks for reporting. I'll try to look into this, soon, but very distracted, > ATM. > > Could you add the output of > getAnywhere ("trellis.last.object") > to this report (after the error)? > > For the time being, you should be able to work around this by disabling the > plot history feature, either for this call, only (rk.without.plot.history()) > or > entirely (Settings->Onscreen Graphics->Screen device history). > -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 362825] Error in { : task 1 failed - "could not find function "trellis.last.object""
https://bugs.kde.org/show_bug.cgi?id=362825 --- Comment #1 from Michael--- (In reply to Michael from comment #0) > This error only occurs when running the R code in RKWard. > I ran the code in native R and the code runs as expected. > I reinstalled lattice but it was no help. > > The code is at this location. > https://github.com/hd625b/CaliforniaEarthQuakeStudy.git > > RKWard > Version 0.6.4 > Using KDE Development Platform 4.14.16 > > R version 3.2.5 (2016-04-14) > Platform: x86_64-pc-linux-gnu (64-bit) > Running under: Ubuntu 16.04 LTS > > locale: > [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C > [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 > [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 > [7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 > [9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8 > [11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8 > > attached base packages: > [1] parallel stats graphics grDevices utils datasets methods > [8] base > > other attached packages: > [1] doMC_1.3.4 iterators_1.0.8 foreach_1.4.3 > [4] effects_3.1-1dplyr_0.4.3 plyr_1.8.3 > [7] scatterplot3d_0.3-36 plot3D_1.1 reshape2_1.4.1 > [10] ggmap_2.6.1 ggplot2_2.1.0rgl_0.95.1441 > [13] qcc_2.6 forecast_7.1 timeDate_3012.100 > [16] zoo_1.7-13 rkward_0.6.3 > > loaded via a namespace (and not attached): > [1] splines_3.2.5 lattice_0.20-33 colorspace_1.2-6 > [4] XML_3.98-1.4nloptr_1.0.4sm_2.2-5.4 > [7] DBI_0.4 sp_1.2-3jpeg_0.1-8 > [10] stringr_1.0.0 munsell_0.4.3 gtable_0.2.0 > [13] RgoogleMaps_1.2.0.7 mapproj_1.2-4 codetools_0.2-14 > [16] labeling_0.3misc3d_0.8-4tseries_0.10-35 > [19] proto_0.3-10Rcpp_0.12.4 geosphere_1.5-1 > [22] scales_0.4.0lme4_1.1-12 fracdiff_1.4-2 > [25] digest_0.6.9rjson_0.2.15png_0.1-7 > [28] stringi_1.0-1 RJSONIO_1.3-0 grid_3.2.5 > [31] quadprog_1.5-5 tools_3.2.5 magrittr_1.5 > [34] maps_3.1.0 lazyeval_0.1.10 Matrix_1.2-6 > [37] MASS_7.3-45 minqa_1.2.4 assertthat_0.1 > [40] R6_2.1.2vioplot_0.2 compiler_3.2.5 > [43] nlme_3.1-127nnet_7.3-12 The error occurs when the "effect' function runs. # Effects Plot = print(plot(effect("net:magType", netBymagType), main = paste("Effect Plot - net by magType\n", Sys.Date()), lwd = 2, cex = 1.1, color = "black", ylab = "Maginitude", xlab = paste("'net' = Source of the Information \n", "magType = The Method used to Calculate the Magnitude"))) Error in rk.record.plot$.save.tlo.in.hP() : could not find function "trellis.last.object" -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 362825] New: Error in { : task 1 failed - "could not find function "trellis.last.object""
https://bugs.kde.org/show_bug.cgi?id=362825 Bug ID: 362825 Summary: Error in { :task 1 failed - "could not find function "trellis.last.object"" Product: rkward Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: hd6...@gmail.com This error only occurs when running the R code in RKWard. I ran the code in native R and the code runs as expected. I reinstalled lattice but it was no help. The code is at this location. https://github.com/hd625b/CaliforniaEarthQuakeStudy.git RKWard Version 0.6.4 Using KDE Development Platform 4.14.16 R version 3.2.5 (2016-04-14) Platform: x86_64-pc-linux-gnu (64-bit) Running under: Ubuntu 16.04 LTS locale: [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 [7] LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 [9] LC_ADDRESS=en_US.UTF-8LC_TELEPHONE=en_US.UTF-8 [11] LC_MEASUREMENT=en_US.UTF-8LC_IDENTIFICATION=en_US.UTF-8 attached base packages: [1] parallel stats graphics grDevices utils datasets methods [8] base other attached packages: [1] doMC_1.3.4 iterators_1.0.8 foreach_1.4.3 [4] effects_3.1-1dplyr_0.4.3 plyr_1.8.3 [7] scatterplot3d_0.3-36 plot3D_1.1 reshape2_1.4.1 [10] ggmap_2.6.1 ggplot2_2.1.0rgl_0.95.1441 [13] qcc_2.6 forecast_7.1 timeDate_3012.100 [16] zoo_1.7-13 rkward_0.6.3 loaded via a namespace (and not attached): [1] splines_3.2.5 lattice_0.20-33 colorspace_1.2-6 [4] XML_3.98-1.4nloptr_1.0.4sm_2.2-5.4 [7] DBI_0.4 sp_1.2-3jpeg_0.1-8 [10] stringr_1.0.0 munsell_0.4.3 gtable_0.2.0 [13] RgoogleMaps_1.2.0.7 mapproj_1.2-4 codetools_0.2-14 [16] labeling_0.3misc3d_0.8-4tseries_0.10-35 [19] proto_0.3-10Rcpp_0.12.4 geosphere_1.5-1 [22] scales_0.4.0lme4_1.1-12 fracdiff_1.4-2 [25] digest_0.6.9rjson_0.2.15png_0.1-7 [28] stringi_1.0-1 RJSONIO_1.3-0 grid_3.2.5 [31] quadprog_1.5-5 tools_3.2.5 magrittr_1.5 [34] maps_3.1.0 lazyeval_0.1.10 Matrix_1.2-6 [37] MASS_7.3-45 minqa_1.2.4 assertthat_0.1 [40] R6_2.1.2vioplot_0.2 compiler_3.2.5 [43] nlme_3.1-127nnet_7.3-12 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361578] Settings and Window menu absent from keyboard shortcut list
https://bugs.kde.org/show_bug.cgi?id=361578 --- Comment #3 from Michael--- Should be fixed by https://phabricator.kde.org/rKRITA37389d5353ec5aa4c4dacf2809c1b594b3fd06ab -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361578] Settings and Window menu absent from keyboard shortcut list
https://bugs.kde.org/show_bug.cgi?id=361578 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #2 from Michael --- You're right Boud, luckily this only required some simple reordering in krita.shortcuts and kritamenu.shortcuts. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361971] Canvas Input Settings reset to default on restart.
https://bugs.kde.org/show_bug.cgi?id=361971 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #3 from Michael --- This has something to do with KoDefaultPaths. In kis_input_profile_manager.cpp line 246: // we have one or more entries for this profile name. We'll take the last, // because that's the most local one. ProfileEntry entry = profileEntries[profileName].first(); So this assumption no longer holds in Krita 3.0, in fact we keep reloading the builtin profile from ~/share/ instead of the intended profile in ~/.local/. The 1/10 randomness is because the entries may arrive in a different order so that occasionally the first entry is in ~/.local/. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362327] cursor offset after tablet portrait/landscape orientation change
https://bugs.kde.org/show_bug.cgi?id=362327 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #2 from Michael --- This may be fixed in Krita 3.0 on Windows at least, the tablet settings are instructed to refresh whenever the screen geometry changes. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362074] In Krita 3.0 alpha, Shortcut Setting dialogue should have the Action trees expanded by default
https://bugs.kde.org/show_bug.cgi?id=362074 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #3 from Michael --- This should be enabled by: https://phabricator.kde.org/rKRITA7498d7d2b82bf73a22846f62ca63f3c7c05149b5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362134] Alternative shortcuts breaks primary shortcuts in Krita 3.0 alpha.
https://bugs.kde.org/show_bug.cgi?id=362134 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #3 from Michael --- This patch should help iron out some of the bugs. Let me know if the lastest master helps. https://phabricator.kde.org/rKRITA520cbbfdfb662a46476a69aa0d24d30507a198c5 Stefano: You're right that the shortcuts configuration code is pretty bad. Unfortunately KisShortcutsDialog, KActionCollection and everything else in XMLGUI ultimately comes from upstream, so if something is confusing or looks poorly designed your guess is as good as mine as to the justification. The patch I wrote basically sticks to modifying KisActionRegistry, to keep the shortcut data in the same format as XMLGUI. I wr -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362124] New: Plasma crash when typing and searching in Launcher
https://bugs.kde.org/show_bug.cgi?id=362124 Bug ID: 362124 Summary: Plasma crash when typing and searching in Launcher Product: plasmashell Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: miabr...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: - What I was doing when the application crashed: I click on the full screen launcher, start typing and wait for some search results to come up. In a second or two the shell will crash. - Unusual behavior I noticed: No search results are returned from the launcher. Baloo also crashes on my machine frequently, but I do not get a warning about baloo in this case.. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f7e5bf6d8c0 (LWP 21153))] Thread 35 (Thread 0x7f7e481c6700 (LWP 21166)): #0 0x7f7e56682e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7e5a747c62 in poll (__timeout=-1, __nfds=1, __fds=0x7f7e481c5c00) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 _xcb_conn_wait (c=c@entry=0xcdf7c0, cond=cond@entry=0xcdf800, vector=vector@entry=0x0, count=count@entry=0x0) at ../../src/xcb_conn.c:459 #3 0x7f7e5a7498d7 in xcb_wait_for_event (c=0xcdf7c0) at ../../src/xcb_in.c:693 #4 0x7f7e4a946629 in QXcbEventReader::run (this=0xcebb50) at qxcbconnection.cpp:1253 #5 0x7f7e56d7884e in QThreadPrivate::start (arg=0xcebb50) at thread/qthread_unix.cpp:331 #6 0x7f7e55e656fa in start_thread (arg=0x7f7e481c6700) at pthread_create.c:333 #7 0x7f7e5668eb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 34 (Thread 0x7f7e45599700 (LWP 21167)): #0 0x7f7e5667e9cd in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7e5345b6c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7e53417e04 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7e534182c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f7e5341842c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7e56fafa9b in QEventDispatcherGlib::processEvents (this=0x7f7e380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #6 0x7f7e56f56dea in QEventLoop::exec (this=this@entry=0x7f7e45598ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #7 0x7f7e56d738a4 in QThread::exec (this=this@entry=0xdbc9d0) at thread/qthread.cpp:503 #8 0x7f7e5961b3c5 in QQmlThreadPrivate::run (this=0xdbc9d0) at qml/ftw/qqmlthread.cpp:141 #9 0x7f7e56d7884e in QThreadPrivate::start (arg=0xdbc9d0) at thread/qthread_unix.cpp:331 #10 0x7f7e55e656fa in start_thread (arg=0x7f7e45599700) at pthread_create.c:333 #11 0x7f7e5668eb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 33 (Thread 0x7f7e34ae3700 (LWP 21168)): #0 0x7f7e56682e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f7e5341831c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f7e5341842c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f7e56fafa9b in QEventDispatcherGlib::processEvents (this=0x7f7e38c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f7e56f56dea in QEventLoop::exec (this=this@entry=0x7f7e34ae2ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f7e56d738a4 in QThread::exec (this=this@entry=0x10ea990) at thread/qthread.cpp:503 #6 0x7f7e5961b3c5 in QQmlThreadPrivate::run (this=0x10ea990) at qml/ftw/qqmlthread.cpp:141 #7 0x7f7e56d7884e in QThreadPrivate::start (arg=0x10ea990) at thread/qthread_unix.cpp:331 #8 0x7f7e55e656fa in start_thread (arg=0x7f7e34ae3700) at pthread_create.c:333 #9 0x7f7e5668eb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 32 (Thread 0x7f7e2ec40700 (LWP 21169)): #0 __GI___tls_get_addr (ti=0x7f7e571a3788) at dl-tls.c:831 #1 0x7f7e56d77792 in get_thread_data () at thread/qthread_unix.cpp:181 #2 QThreadData::current (createIfNecessary=createIfNecessary@entry=true) at thread/qthread_unix.cpp:212 #3 0x7f7e56faeffa in postEventSourcePrepare (s=0x7f7e280012d0, timeout=0x7f7e2ec3fb24) at kernel/qeventdispatcher_glib.cpp:247 #4 0x7f7e534178ad in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f7e5341824b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f7e5341842c in g_main_context_iteration () from
[Baloo] [Bug 362056] New: Baloo randomly crashes at memcpy_avx_unaligned
https://bugs.kde.org/show_bug.cgi?id=362056 Bug ID: 362056 Summary: Baloo randomly crashes at memcpy_avx_unaligned Product: Baloo Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: m...@vhanda.in Reporter: miabr...@gmail.com CC: pinak.ah...@gmail.com Application: baloo_file (5.18.0) Qt Version: 5.5.1 Operating System: Linux 4.4.0-21-generic x86_64 Distribution: Ubuntu 16.04 LTS -- Information about the crash: I was hoping this problem would disappear when upgrading to 16.04 but it does not. Usually Baloo would crash immediately when I turned my computer on. Now it takes a few minutes after I log in. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Indexing Daemon (baloo_file), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0cb21f28c0 (LWP 1726))] Thread 2 (Thread 0x7f0b686ad700 (LWP 9801)): #0 0x7f0cb0300e8d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f0cad4d131c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0cad4d142c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0cb0f36a9b in QEventDispatcherGlib::processEvents (this=0x7f0b68c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f0cb0edddea in QEventLoop::exec (this=this@entry=0x7f0b686acbc0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x00420cd8 in Baloo::FileContentIndexer::run (this=0x1505ee0) at ../../../src/file/filecontentindexer.cpp:71 #6 0x7f0cb0cfc343 in QThreadPoolThread::run (this=0x158d610) at thread/qthreadpool.cpp:93 #7 0x7f0cb0cff84e in QThreadPrivate::start (arg=0x158d610) at thread/qthread_unix.cpp:331 #8 0x7f0caf9636fa in start_thread (arg=0x7f0b686ad700) at pthread_create.c:333 #9 0x7f0cb030cb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f0cb21f28c0 (LWP 1726)): [KCrash Handler] #6 __memcpy_avx_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-avx-unaligned.S:245 #7 0x7f0cb13e98da in memcpy (__len=27845320, __src=, __dest=) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #8 Baloo::PostingCodec::decode (this=this@entry=0x7ffd0647377f, arr=...) at ../../../src/codecs/postingcodec.cpp:42 #9 0x7f0cb13d5814 in Baloo::PostingDB::get (this=this@entry=0x7ffd06473860, term=...) at ../../../src/engine/postingdb.cpp:100 #10 0x7f0cb13e63c6 in Baloo::WriteTransaction::commit (this=) at ../../../src/engine/writetransaction.cpp:277 #11 0x7f0cb13de032 in Baloo::Transaction::commit (this=this@entry=0x7ffd06473900) at ../../../src/engine/transaction.cpp:262 #12 0x0042a02b in Baloo::MetadataMover::moveFileMetadata (this=0x13f8380, from=..., to=...) at ../../../src/file/metadatamover.cpp:58 #13 0x7f0cb0f0ee4f in QtPrivate::QSlotObjectBase::call (a=0x7ffd06473a60, r=0x7ffd06474120, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #14 QMetaObject::activate (sender=sender@entry=0x150e2e0, signalOffset=, local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd06473a60) at kernel/qobject.cpp:3698 #15 0x7f0cb0f0f7d7 in QMetaObject::activate (sender=sender@entry=0x150e2e0, m=m@entry=0x644cc0 , local_signal_index=local_signal_index@entry=7, argv=argv@entry=0x7ffd06473a60) at kernel/qobject.cpp:3578 #16 0x0042aaba in KInotify::moved (this=this@entry=0x150e2e0, _t1=..., _t2=...) at ./moc_kinotify.cpp:330 #17 0x0042cbff in KInotify::slotEvent (this=, socket=) at ../../../src/file/kinotify.cpp:421 #18 0x7f0cb0f0ee4f in QtPrivate::QSlotObjectBase::call (a=0x7ffd06473cf0, r=0x150e2e0, this=) at ../../include/QtCore/../../src/corelib/kernel/qobject_impl.h:124 #19 QMetaObject::activate (sender=sender@entry=0x1511d90, signalOffset=, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd06473cf0) at kernel/qobject.cpp:3698 #20 0x7f0cb0f0f7d7 in QMetaObject::activate (sender=sender@entry=0x1511d90, m=m@entry=0x7f0cb1129780 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd06473cf0) at kernel/qobject.cpp:3578 #21 0x7f0cb0f8e51e in QSocketNotifier::activated (this=this@entry=0x1511d90, _t1=13) at .moc/moc_qsocketnotifier.cpp:134 #22 0x7f0cb0f1b47b in QSocketNotifier::event (this=0x1511d90, e=) at kernel/qsocketnotifier.cpp:260 #23 0x7f0cb0ee060c in QCoreApplication::notify (event=0x7ffd06473db0, receiver=0x1511d90, this=0x7ffd06474080) at kernel/qcoreapplication.cpp:1038 #24 QCoreApplication::notifyInternal (this=0x7ffd06474080, receiver=0x1511d90, event=event@entry=0x7ffd06473db0) at kernel/qcoreapplication.cpp:965 #25 0x7f0cb0f36f45 in QCoreApplication::sendEvent
[KScreen] [Bug 346961] Multi Monitor configuration lost on reboot, must reconfigure after startup
https://bugs.kde.org/show_bug.cgi?id=346961 Michaelchanged: What|Removed |Added CC||m...@one.com --- Comment #45 from Michael --- I am also seeing the same error on fedora 23 with package kscreen-5.5.5-1.fc23.x86_64.rpm. I have 2 identical screen where the left is turned 90 degrees. As of this morning, whenever I restart, both servers are identical, and in the screen view placed on top of each other (problem 1 from comment #38). When I setup my left screen the background says unturned, and overlaps into screen the right screen. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360595] Krita crashes when we cancel the save custom shortcut dialog box
https://bugs.kde.org/show_bug.cgi?id=360595 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #7 from Michael --- This should be fixed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359171] paint strokes with tablet less fluent than in 2.9.6
https://bugs.kde.org/show_bug.cgi?id=359171 --- Comment #16 from Michael--- Hmm, it looks like in the tablet logs, there is a TabletPress followed by a TabletMove with identical coordinates. This may be disrupting the smoothing algorithm. 063745.56365967[5900] krita.tabletlog: "[ ] TabletPress btn: 1 btns: 1 pos: 507, 496 gpos: 545, 580 hires: 544.924, 580.409 063845.56517029[5900] krita.tabletlog: "[ ] TabletMove btn: 0 btns: 1 pos: 507, 496 gpos: 545, 580 hires: 544.924, 580.409 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 359171] paint strokes with tablet less fluent than in 2.9.6
https://bugs.kde.org/show_bug.cgi?id=359171 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #13 from Michael --- (In reply to Chris Jones from comment #12) > I find this is much improved now, however there is still a slight glitch at > the start of each stroke. When drawing fast circles this appears as a > little hook on the SP4, and a short straight line on the desktop. Hi Chris, if this is still happening in the next release would you be able to upload another tablet log? Also, what are your smoothing settings? Sometimes I get glitches when using weighted smoothing, while basic smoothing leaves my stroke intact. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359766] New: new widgets and widget improvements
https://bugs.kde.org/show_bug.cgi?id=359766 Bug ID: 359766 Summary: new widgets and widget improvements Product: plasmashell Version: master Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mishaor2...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org I want to see update applet with all packages and "Update" button than update the packages without opening Muon. Also, i want to see Muon widget (that display popular apps) and list of desktops. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Michaelchanged: What|Removed |Added CC|miabr...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356394] Crash at some point while monitor power cycled
https://bugs.kde.org/show_bug.cgi?id=356394 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #10 from Michael --- Getting this when waking the computer up from sleep using the NVidia driver. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 349708] Intelligent Scissors - Magnetic Lasso
https://bugs.kde.org/show_bug.cgi?id=349708 --- Comment #8 from Michael--- I'll take a look at this again after Dmitry writes the lazy brush, since it would be using a lot of the same infrastructure. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 353090] Timer doesnt locks in panel properly
https://bugs.kde.org/show_bug.cgi?id=353090 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #1 from Michael --- I think this is a repeat of the bug I would like to report. Let me rephrase. When I add the timer plasmoid to the desktop, it displays the remaining time. When I add it to the panel, it shows only a static icon org.kde.plasma.timer. I believe this could be fixed by using the compactRepresentation/fullRepresentation properties. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 357873] New: libstdc++ unhandled instruction: 0xF 0xC7 0xF0 0x89
https://bugs.kde.org/show_bug.cgi?id=357873 Bug ID: 357873 Summary: libstdc++ unhandled instruction: 0xF 0xC7 0xF0 0x89 Product: valgrind Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: miabr...@gmail.com Running Krita development version in callgrind causes a crash at startup. The backtrace points to some point in the new c++11 stdlib random number facility. There is some mention of Vc SIMD library in the backtrace, but the call to std::random_device happens before any SIMD operations are invoked so I doubt that is the issue. The call occurs around line 165 here: https://phabricator.kde.org/diffusion/KRITA/browse/master/krita/image/kis_brush_mask_applicators.h vex amd64->IR: unhandled instruction bytes: 0xF 0xC7 0xF0 0x89 0x6 0xF 0x42 0xC1 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=0F vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==18052== valgrind: Unrecognised instruction at address 0x6a75ec5. ==18052==at 0x6A75EC5: std::(anonymous namespace)::__x86_rdrand() (random.cc:69) ==18052==by 0x6A76061: std::random_device::_M_getval() (random.cc:130) ==18052==by 0x869FF59: std::random_device::operator()() (in ~/lib/x86_64-linux-gnu/libkritaimage.so.15.0.0) ==18052==by 0x86A04C4: KisBrushMaskScalarApplicator::processScalar(QRect const&) (in ~/lib/x86_64-linux-gnu/libkritaimage.so.15.0.0) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying
https://bugs.kde.org/show_bug.cgi?id=357063 Michaelchanged: What|Removed |Added CC||m...@one.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 357063] New konsole uses desktop for background; echoing command input/out NOT displaying
https://bugs.kde.org/show_bug.cgi?id=357063 --- Comment #5 from Michael--- Same problem here. Started this morning. When I open konsole through the menu or when opening it on the second screen from XTerm it opens with the background, and its not possible to change anything, If opening on my primary screen, it opens correctly. The output when opening the console from XTerm: [mih@localhost ~]$ konsole QCoreApplication::arguments: Please instantiate the QApplication object first [mih@localhost ~]$ The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly. The font for use in the terminal has not been matched exactly. Perhaps it has not been found properly. 0x29633a0 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1db3800) ): Attempt to set a screen on a child window. 0x2963940 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1db3800) ): Attempt to set a screen on a child window. 0x2964630 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1db3800) ): Attempt to set a screen on a child window. 0x29d6220 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1db3800) ): Attempt to set a screen on a child window. 0x29c8d50 void QWindowPrivate::setTopLevelScreen(QScreen*, bool) ( QScreen(0x1db3800) ): Attempt to set a screen on a child window. QXcbConnection: XCB error: 8 (BadMatch), sequence: 1700, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1703, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1711, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1714, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1721, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1728, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1736, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1742, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1751, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1758, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1765, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1774, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1777, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1792, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1810, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1828, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1836, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1844, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1852, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1860, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1868, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1876, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1884, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1892, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1900, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1908, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1916, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1925, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1933, resource id: 8388711, major code: 130 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 1941, resource id: 8388711, major code: 130 (Unknown), minor code: 3
[valgrind] [Bug 357294] New: cannot start valgrind with tool dhat
https://bugs.kde.org/show_bug.cgi?id=357294 Bug ID: 357294 Summary: cannot start valgrind with tool dhat Product: valgrind Version: 3.8.0 Platform: RedHat RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: dhat Assignee: jsew...@acm.org Reporter: tianya0yin...@163.com Created attachment 96350 --> https://bugs.kde.org/attachment.cgi?id=96350=edit dhat log cannot start dhat program, the attachement is log . but when i upgrade valgrind to 3.11, the problem is not came out. Now, i use valgrind 3.11. So, it's ok for me. Maybe the log is helpful to develper. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356533] Windows and Widgets are hidden behind desktop background
https://bugs.kde.org/show_bug.cgi?id=356533 --- Comment #2 from michael--- Created attachment 96064 --> https://bugs.kde.org/attachment.cgi?id=96064=edit Plasmashell force stopped Yes, that command does show me the proper windows, with menu bar & buttons. I managed to take a screencap before Plasma restarted itself. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356533] New: Windows and Widgets are hidden behind desktop background
https://bugs.kde.org/show_bug.cgi?id=356533 Bug ID: 356533 Summary: Windows and Widgets are hidden behind desktop background Product: plasmashell Version: master Platform: openSUSE RPMs URL: http://imgur.com/bUjhK5T OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: michael.hrishe...@cerner.com CC: bhus...@gmail.com, plasma-b...@kde.org Seems very similar to https://bugs.kde.org/show_bug.cgi?id=260360 The operating system works as before as far as I can tell, with the exception of visibility. I can access any object, complete any action as long as I know where the buttons and windows are from memory, since they are no longer visible and seem hidden behind the background image. Correlating with this is that when shutting down, sometimes the background is taken down first, and I'm presented briefly with a black screen holding all the windows I have opened so far. Reproducible: Always Steps to Reproduce: 1. Start up Virtual Machine 2. Auto login enabled, as soon as I am logged in the issue is apparent. Actual Results: A KDE 5 desktop with no visibility apart from the bottom widget, set to draw itself in the space below the background image, instead of on top of it. Expected Results: Windows that are visible, toolbars on top of the desktop background. If I can figure out how, I'll try setting a transparent png as the background image. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 356393] valgrind (vex) crashes because isZeroU happened
https://bugs.kde.org/show_bug.cgi?id=356393 Michaelchanged: What|Removed |Added CC||miabr...@gmail.com --- Comment #1 from Michael --- I get a similar crash with Valgrind 3.11 in libcrypto at the same function call, ecp_nistz256_avx2_select_w7. I'm running Kubuntu 15.10. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 347022] Unable to setup wacom tablet - widget missing
https://bugs.kde.org/show_bug.cgi?id=347022 --- Comment #9 from Michael--- Hi Michael - as an alternative to using xcb-xinput (which is unstable API currently) there is a new branch releng3.0 and tag v3.0.0-beta1 which can be built without xcb-xinput. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 347284] update notifier gets available updates count wrong
https://bugs.kde.org/show_bug.cgi?id=347284 --- Comment #8 from michael--- Created https://git.reviewboard.kde.org/r/126284. Security updates are now correctly accounted for in MuonNotifier. No more double counting there. On my machine the count can also be lower than the actually package count for non-security updates. I don't know if this is still the case. Now works for me if only security updates are found not yet tested in other cases. -- You are receiving this mail because: You are watching all bug changes.