[frameworks-plasma] [Bug 396097] Bug in KDE desktop. Set Settings to doubleclick. Plasma desktop opens TWO instance when double clicking
https://bugs.kde.org/show_bug.cgi?id=396097 --- Comment #2 from deadlydud --- Hello Nate. Thank you for the explanation. BUT: KDE DESKTOP = Icons on the desktop: not buttons on a task bar. SO: one would expect it to behave the same as ICONS within Dolphin. Though it seems the icons on the desktop behaves like a task-bar, not a desktop. I DID find a work-around: remove all the icons from the desktop, add widget FOLDER VIEW. Drag icons from your favorites, drop it in the folder view. Conclusion: Then it works as expected. You click once to select it, right-click to have several actions, and double-click to launch it (it honors the settings!). One can even drag a box around several icons to multi-select, and one can control-click or shift-click to select many at once or deselect some. Am pretty sure 67.5% of all KDE users expect a Desktop to behave like a desktop, and if one sets Setting: Double-click: then a true desktop would honor its setting. Makes sense. Hope this work-around helps some other people. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 396097] New: Bug in KDE desktop. Set Settings to doubleclick. Plasma desktop opens TWO instance when double clicking
https://bugs.kde.org/show_bug.cgi?id=396097 Bug ID: 396097 Summary: Bug in KDE desktop. Set Settings to doubleclick. Plasma desktop opens TWO instance when double clicking Product: frameworks-plasma Version: 5.47.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: kdeb...@galaxy.za.net Target Milestone: --- Open KDE settings... set mouse to doubleclick to open application. Dolphin honors it. KDE desktop doesn't. Expected behavior: KDE desktop: doubleclick chrome icon should open ONE instance of Gooogle Chrome. Not TWO. Don't spin it. Just accept it as a bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 393021] New: Desktop control-a, delete, then control-z
https://bugs.kde.org/show_bug.cgi?id=393021 Bug ID: 393021 Summary: Desktop control-a, delete, then control-z Product: frameworks-plasma Version: 5.41.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: kdeb...@galaxy.za.net Target Milestone: --- click on desktop. then Control-A (select all) .. delete.. deletes desktop icons then control-Z.. (or rightclick and look for an undo).. get strange popup "This should never happen" -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373881] Discover says cannot update no network connection
https://bugs.kde.org/show_bug.cgi?id=373881 deadlydud changed: What|Removed |Added Platform|Ubuntu Packages |Kubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373881] Discover says cannot update no network connection
https://bugs.kde.org/show_bug.cgi?id=373881 --- Comment #4 from deadlydud --- battles to compile it .. (had to install pkg-config libqtglib-2.0-0 glib-2.0 libglib2.0-dev) eddie@mezzodud:~$ gcc `pkg-config --cflags --libs glib-2.0 gio-2.0` gnetworkmonitor-test.c -g -O0 -o test && ./test gnetworkmonitor-test.c: In function ‘main’: gnetworkmonitor-test.c:14:2: warning: ‘g_type_init’ is deprecated [-Wdeprecated-declarations] g_type_init (); ^ In file included from /usr/include/glib-2.0/gobject/gobject.h:24:0, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from gnetworkmonitor-test.c:4: /usr/include/glib-2.0/gobject/gtype.h:681:23: note: declared here void g_type_init(void); ^ /tmp/ccpuJJ92.o: In function `main': /home/eddie/gnetworkmonitor-test.c:14: undefined reference to `g_type_init' /home/eddie/gnetworkmonitor-test.c:16: undefined reference to `g_network_monitor_get_default' /home/eddie/gnetworkmonitor-test.c:17: undefined reference to `g_network_address_new' /home/eddie/gnetworkmonitor-test.c:18: undefined reference to `g_network_monitor_get_network_available' /home/eddie/gnetworkmonitor-test.c:19: undefined reference to `g_network_monitor_can_reach' /home/eddie/gnetworkmonitor-test.c:22: undefined reference to `g_clear_error' /home/eddie/gnetworkmonitor-test.c:25: undefined reference to `g_object_unref' collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373881] Discover says cannot update no network connection
https://bugs.kde.org/show_bug.cgi?id=373881 deadlydud changed: What|Removed |Added Keywords||usability Platform|Other |Ubuntu Packages -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 373881] New: Discover says cannot update no network connection
https://bugs.kde.org/show_bug.cgi?id=373881 Bug ID: 373881 Summary: Discover says cannot update no network connection Product: Discover Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: kdeb...@galaxy.za.net Target Milestone: --- Discover says cannot update no network connection, yet if I open bash I can do sudo apt-get upgrade without problem. Discover probably relying on knetworkmanager but system is configured with static network without knetworkmanager -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 355505] Icon disappears during package upgrade
https://bugs.kde.org/show_bug.cgi?id=355505 deadlydud changed: What|Removed |Added Product|Planet KDE |plasma-pa Version|unspecified |5.5.5 Component|general |general CC||plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 355505] Icon disappears during package upgrade
https://bugs.kde.org/show_bug.cgi?id=355505 deadlydud changed: What|Removed |Added Component|desktop |general Product|plasma4 |Planet KDE -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 355505] Icon disappears during package upgrade
https://bugs.kde.org/show_bug.cgi?id=355505 --- Comment #1 from deadlydud --- It keeps happening .. install opera .. it creates /usr/bin/opera .. drag from Kmenu Application Internet Opera to desktop as shortcut ... wait for "a new update of opera" (which just replaces /usr/bin/opera with a new version) .. desktop icon disappears during the upgrade.. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 303627] update-mime-database complains about unknown media types
https://bugs.kde.org/show_bug.cgi?id=303627 deadlydud changed: What|Removed |Added CC||kdeb...@galaxy.za.net --- Comment #11 from deadlydud --- It seems that since 2008 this has been a irritation visual bug in kubuntu /ubuntu, even after fresh installs and after upgrading previous kubuntu releases. Why not fix update-mime-database to NOT complain about all/all and all/allfiles ? (should be simple enough ... if mime-type == all/all* ... don't moan about it... (if it cannot be removed from /usr/share/mime/packages/kde.xml for some good reason) Since this looks like a issue introduced with kde.xml, maybe David Faure could look at it? Would be nice to solve a 8 year old bug. during apt-get operations: displays warnings Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Saw other people mentioned it all over the place .. https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/289592 http://askubuntu.com/questions/39852/how-to-remove-warnings-like-unknown-media-type some google threads claim it's "solved", yet it persists. Maybe Kubuntu staff can contact the author listed in http://linux.die.net/man/1/update-mime-database and get this resolved?... Thomas Leonard the author ? .. my 2c (I googled for a few minutes and couldn't find the source code for "update-mime-database" to look at source) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362667] New: kwin crashed after coming back from chrome full screen view using F11 and having kontact open
https://bugs.kde.org/show_bug.cgi?id=362667 Bug ID: 362667 Summary: kwin crashed after coming back from chrome full screen view using F11 and having kontact open Product: kwin Version: 5.5.5 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kdeb...@galaxy.za.net Application: kwin_x11 (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: using Chrome in full screen mode, kontact kmail was running trying to fetch a mail message from local lan imap server, kwin crashed, leaving no window decorators on open kde windows. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fef3e906940 (LWP 4059))] Thread 5 (Thread 0x7fef1baa7700 (LWP 4088)): #0 0x7fef3e3f3d13 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fef3cbf810f in qt_safe_select (nfds=15, fdread=fdread@entry=0x7fef0c000a78, fdwrite=fdwrite@entry=0x7fef0c000d08, fdexcept=fdexcept@entry=0x7fef0c000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fef3cbf9c0e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fef0c000f98, writefds=0x7fef0c000d08, readfds=0x7fef0c000a78, nfds=, this=0x7fef0c0008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fef0c0008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fef3cbfa13e in QEventDispatcherUNIX::processEvents (this=0x7fef0c0008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fef3cba3dea in QEventLoop::exec (this=this@entry=0x7fef1baa6c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fef3c9c08a4 in QThread::exec (this=this@entry=0x2401230) at thread/qthread.cpp:503 #7 0x7fef374d63c5 in QQmlThreadPrivate::run (this=0x2401230) at qml/ftw/qqmlthread.cpp:141 #8 0x7fef3c9c584e in QThreadPrivate::start (arg=0x2401230) at thread/qthread_unix.cpp:331 #9 0x7fef383796fa in start_thread (arg=0x7fef1baa7700) at pthread_create.c:333 #10 0x7fef3e3fdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fef18db3700 (LWP 4092)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef1a342213 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #2 0x7fef1a341937 in ?? () from /usr/lib/x86_64-linux-gnu/dri/r600_dri.so #3 0x7fef383796fa in start_thread (arg=0x7fef18db3700) at pthread_create.c:333 #4 0x7fef3e3fdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7fef10e2b700 (LWP 4104)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7fef3bb4dbd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7fef3bb4dc19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7fef383796fa in start_thread (arg=0x7fef10e2b700) at pthread_create.c:333 #4 0x7fef3e3fdb5d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7fef1162c700 (LWP 4515)): #0 0x7fef3e3f3d13 in select () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fef3cbf810f in qt_safe_select (nfds=14, fdread=fdread@entry=0x7fef08000a78, fdwrite=fdwrite@entry=0x7fef08000d08, fdexcept=fdexcept@entry=0x7fef08000f98, orig_timeout=orig_timeout@entry=0x0) at kernel/qcore_unix.cpp:75 #2 0x7fef3cbf9c0e in QEventDispatcherUNIX::select (timeout=0x0, exceptfds=0x7fef08000f98, writefds=0x7fef08000d08, readfds=0x7fef08000a78, nfds=, this=0x7fef080008c0) at kernel/qeventdispatcher_unix.cpp:320 #3 QEventDispatcherUNIXPrivate::doSelect (this=this@entry=0x7fef080008e0, flags=..., flags@entry=..., timeout=timeout@entry=0x0) at kernel/qeventdispatcher_unix.cpp:196 #4 0x7fef3cbfa13e in QEventDispatcherUNIX::processEvents (this=0x7fef080008c0, flags=...) at kernel/qeventdispatcher_unix.cpp:607 #5 0x7fef3cba3dea in QEventLoop::exec (this=this@entry=0x7fef1162bc60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7fef3c9c08a4 in QThread::exec (this=this@entry=0x2ed3cc0) at thread/qthread.cpp:503 #7 0x7fef374d63c5 in QQmlThreadPrivate::run (this=0x2ed3cc0) at qml/ftw/qqmlthread.cpp:141 #8 0x7fef3c9c584e in QThreadPrivate::start (arg=0x2ed3cc0) at thread/qthread_unix.cpp:331 #9 0x7fef383796fa in start_thread (arg=0x7fef1162c700) at pthread_create.c:333 #10 0x7fef3e3fdb5d in clone () at ../s
[muon] [Bug 347602] Update Manager systray icon and info still reports pending updates after updates applied
https://bugs.kde.org/show_bug.cgi?id=347602 deadlydud changed: What|Removed |Added CC||kdeb...@galaxy.za.net --- Comment #38 from deadlydud --- apt-get upgrade does not seem to fix the issue. -- You are receiving this mail because: You are watching all bug changes.
