February 2016 - openSUSE KDE - openSUSE Mailing Lists

[opensuse-kde] Weird desktop folder behaviour Tumbleweed.
by Steven Hess 28 Feb '16

28 Feb '16

On a uptodate Tumbleweed with look and feel set to Breeze theme and desktop theme set to Air When I left select on a folder in the Desktop Folder it tries to open the folder with Audacious. When I right select a folder it correctly opens with Dolphin Going to desktop settings Personalization> Applications> File Associations> Default Applications> File Manager and selecting> Dolphin instead of Audacious ( which it's defaulting to ) and applying then going back to try and open the file is again it tries to open with Audacious and the setting in desktop settings Personalization> Applications> File Associations> Default Applications> File Manager is defaulted back to Audacious. I've had this happen previously but the change in the file manager stuck when I changed it. What do I need to fix this? Thanks Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND 927.0875Mhz and 441.125 Repeaters Taft Ca. openSUSE Tumbleweed KDE Plasma with Packman, Leap 42.1 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 5

Re: [opensuse] Re: [opensuse-kde] Weird desktop folder behaviour Tumbleweed.
by Steven Hess 27 Feb '16

27 Feb '16

Ah! Great success. Thanks sdm. I would have never thought to look there in a million years. Steven ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND 927.0875Mhz and 441.125 Repeaters Taft Ca. openSUSE Tumbleweed KDE Plasma with Packman, Leap 42.1 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Updated to Plasma 5.5.4, now sddm is broken
by Darryl Gregorash 27 Feb '16

27 Feb '16

With all the stuff that got updated with today's release of Plasma ver 5.5.4, sddm is now broken. I get a blank screen on tty7, and nothing will get the login screen to come up. Kdm however is working fine (otherwise I wouldn't be writing this message). I have neither the time nor the patience to try to figure out what went wrong; all I want is to get a working system back -- one, that is, that uses sddm, since I have grown rather used to it. Any help most graciously received. TYIA. PS for Markus: sorry, but no... Plasma 5.5 does *not* return functionality to left/right clicks of the scroll wheel (eg to change desktops). In fact, I am not certain that those are even recognized at all anymore. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 9

[opensuse-kde] Spectacle and its save menu
by ianseeks 24 Feb '16

24 Feb '16

Hi Is there any way to recofingure the Save menu so i can make "Save as" the default instead of "Save & Exit"? I tend to name my snapshots with meaningful names and its easy to press save and exit by mistake. Regards Ian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] elarun splash with KDM?
by Felix Miata 22 Feb '16

22 Feb '16

What actually controls what splash is available, the greeter/DM, or the DE? Is there a TW or Leap package I can install to get Elarun in KF5 instead of a choice between Breeze and nothing? Configure splash doesn't provide a way to see where the selections live so as to be able to run rpm -qf on them to see what rpm owns them. Installing kde4-wallpaper-default got Elarun for the desktop wallpaper, but not for splash. SDDM isn't an option due to KDM features SDDM lacks, unless SDDM can be used just for configuration access to optional splashes and not required to be the configured greeter. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 12

[opensuse-kde] Show Desktop widget
by ianseeks 22 Feb '16

22 Feb '16

Hi I've having weird responses using "Show Desktop". One one login if i have a program open and i press "show desktop", the desktop shows correctly but as soon as i click on a folder in my folder view on the desktop, the program that was moved away comes back instead of opening Dolphin to view the folder. On one other user, pressing "show desktop" just makes the program that should be moved away, lose focus. Any ideas? Regards Ian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] Need xenon : aka Full unstable Git + Qt56
by Bruno Friedmann 22 Feb '16

22 Feb '16

Hi, I'm fighting with by Skylake Xeon :-) It is a very powerfull computer, which actually handle quite well 16 coresdump at the same time for a load of 32. :-) But I would like (until everything become a stable target) do something else with it. So my question is : can I create a Xenon derivative for Xeon :-) I've seen a target openSUSE_Factory_Qt56 on the Unstable repos, which for the moment is desactivated (since december) Is there any chances that can be put again as active. Shall I clone/branch the whole repo and build them (or try to) in my own home ? I've absolutely no idea how much time/effort is needed to make it buildable, but I would prefer to try to keep it under your governance and help : Yeap I'm volunter to help, cause it seems there's no hope for me except be in the far edging future ;-) Any advise or comment is welcomed. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 1

[opensuse-kde] digikam requires marble
by Felix Miata 21 Feb '16

21 Feb '16

Seriously? Why? Is upstream responsible? Installing digikam creates a one line main menu item "Education", with a submenu containing "Science", containing only KDE Marble. Trying to uninstall either marble-kde or marble wants to remove digikam. :-( -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

5 4

[opensuse-kde] Argon and Kryqton
by Luiz Fernando Ranghetti 19 Feb '16

19 Feb '16

https://news.opensuse.org/2016/02/19/opensuse-offers-choices-for-kde-git-bu… -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Remove all traces of KF5/Plasma 5 from oS 13.2
by Rodney Baker 19 Feb '16

19 Feb '16

Hi all. I'm trying to remove all traces of KF5 and Plasma 5 from my oS 13.2 system and revert to the last working version of KDE4. This seems to be like unscrambling an egg. The KDE4 repositories appear to have vanished, and telling Yast to switch system packages to the oS Update repository results in a never ending cycle of intertwined dependencies that insist on removing x86_64 packages and replacing them with i586 packages or removing the KDE base system altogether! After the last set up updates, the system is broken, with transparency apparently "not supported", hence my desire to revert. Besides, I hate the "flat" look of Plasma 5 and really don't want it (so I won't be upgrading to Leap any time soon). Is there a way, any way, to unscramble this egg, short of a complete reinstall? Perhaps I need to disable all bar the base oS 13.2 repositories and do a zypper dup (and dump all previous updates in the process)? Will that fix it? Or has the horse well and truly bolted with Plasma 5? I even thought about switching distros to Debian (desperate, I know) but even there, Plasma 5 is it. Any suggestions gratefully received (unless they involve sticking with Plasma 5). Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au ============================================================== -- ============================================================== Rodney Baker VK5ZTV rodney.baker(a)iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 6

[opensuse-kde] Kmail, automatic signature file
by C. Brouerius van Nidek 19 Feb '16

19 Feb '16

Since years I am using a automatic signature file in my kmail to sign me emails. Today I discovered that the automatic file did not show the actual use of my KDE. I assume that in the meantime this signature should have shown that I am using KDE5 so I had a look at the file. Changing the first KDE4 in KDE5 was no showstopper but the automatic read of kde='kde4-config -v |grep KDE' echo "" $kde into: kde='kde5-config -v |grep KDE' echo "" $kde did result in an empty space. Could somebody help me out with the right command sentence? original file: ------------- powered="(head -n 1 /etc/SuSE-release)" echo " Linux User 183145 using KDE4 Tumbleweed on a Pentium IV ," kernel='uname -r' echo " powered by $powered Kernel : $kernel" kde='kde4-config -v |grep KDE' echo "" $kde uptime --------------- -- Linux User 183145 using KDE5 Tumbleweed on a Pentium IV , powered by openSUSE 20160209 (x86_64) Kernel: 4.4.1-4.g4dac1be-default 14:29pm up 23:15, 3 users, load average: 0.66, 1.84, 2.44 $ #!/bin/bash -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 4

[opensuse-kde] Help is required by QTCurve maintainer to add the qtcurve-q5 window decoration to Plasma 5
by Roman Bysh 18 Feb '16

18 Feb '16

Dear List Mates, Users of QTCurve have found that the qtcurve window decoration is still missing from Plasma 5. This is probably due to changes in the API in KDE5. Ref: https://bugs.kde.org/show_bug.cgi?id=353216 Screenshot: https://bugs.kde.org/attachment.cgi?id=94973&action=edit GIT Ref: https://github.com/QtCurve/qtcurve-qt5 The maintainer is: Yichao Yu email: yyc1992(a)gmail.com Quote: "I'm having a really hard time finding any document on porting to kdecorate2 or the api itself" Yichau Thank you Roman -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 2

[opensuse-kde] Leap, Dolphin -15.12.1 missing icons for a lot of devices in /dev/
by Daniele 17 Feb '16

17 Feb '16

HI guys, point Dolphin to /dev. No icons for sd*, tty* ... almost all devices. No matter the view size/type. Broken mimetype ? Missing icon ? Image attacched- Thanks, Daniele. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 10

RE: [opensuse-kde] KDE5 bluetooth system not running
by stakanov＠freenet.de 17 Feb '16

17 Feb '16

> -----Ursprüngliche Nachricht----- > Von: Malte Gell > Gesendet: Sa. 23.01.2016 14:12 > An: opensuse-kde , > Betreff: [opensuse-kde] KDE5 bluetooth system not running > > Hi there, > > I have a USB bluetooth dongle connected to my machine (0a5c:21e8 > Broadcom Corp. BCM20702A0 Bluetooth 4.0 to be precise). > > When I now log in to a new KDE5 session, the bluetooth icon appears, but > the BT adapter seems to not be activated.... > > Service bluetooth.service is running, restarting it, does not help. > > The only help so far is to pull and replug the BT dongle. > > Do you know any workaround to get active BT in KDE5 from start? > > Thanks > -- > To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Hi Malte. Unfortunately you did not mention what version of operating system you are running. I had a short exchange at opensuse main mailing list and earned a lot of "pun" because I dared to say BT is broken in opensuse 13.2 [opensuse] Leap, KDE, Bluetooth: how to create a special keyboard shortcut for an inside application function was the title. You can read about it (if you can work through the "noise". I can tell you that: with 13.2 BT is broken for GSM phones and BT mices. Adapters are sometimes recognized after sleep or restart, but you will always end up with the device not pairing any more with the adapter. So the adapter does not wake up. Only workaround is to pull and plug the whole thing. In Leap with a "Hamlet" adapter and a Logitech BT mouse I did have it working (that induces my suspect that you are working with 13.2). Still, also in leap pairing of gsm phones will work on an off, the pairing function of BT4 seems not to work correctly and the one of BT3 seems better fitting. 2.1 seems to work normally. Try to look if you need to install the corresponding firmware from the repos. There was a broadcom firware rpm I recall. Good luck. P.S. as the posters on opensuse said that it is "known" I guess there is a bug report. If you find that there isn't any, well let me know I will open a bug. Or let me know about your report if you open one. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

3 2

RE: Re: [opensuse-kde] KDE Neon and opensuse
by stakanov＠freenet.de 14 Feb '16

14 Feb '16

> -----Ursprüngliche Nachricht----- > Von: sdm > Gesendet: Sa. 13.02.2016 19:30 > An: opensuse-kde(a)opensuse.org > Betreff: Re: [opensuse-kde] KDE Neon and opensuse > > On 02/13/2016 10:17 AM, Luca Beltrame wrote: >> Sorry, but as people from KDE helped me to prevent disrespect towards >> our distribution, there's no need to do the reverse. > > It's not disrespect, it's the truth. Yet another fork: more confusion, > less resources going to fixing the openSUSE default distribution. We > don't need that for our users, and new users. I'm also not going to stop > either, Neon is a turd and it will fail. Plain and simple. If you don't > like me saying that, too bad. > -- > To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- Could you refrain on stepping up as "we". You are you. Your opinion has been heard. Whether one has the same opinion or not will not be influenced and success or failure, time will tell. Please do not use offensive and aggressive language. It does not add to your point. Some points you made are surely valuable, but do in my experience apply to some developer, by no means to all. Please continue to post about this, nobody wants to censor but please post only if you have any valuable new point to make. Thank you. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

7 11

[opensuse-kde] bootloader problem TW
by C. Brouerius van Nidek 14 Feb '16

14 Feb '16

As I have added some commands to the bootloader in Yast I found that it takes me up to 10 minutes to open the bootloader and for the saving of the new bootloader. CPU use 50% of my total of 4Gb. Y2base in Ksysguard says it it is waitingfor something to happen and gives as status 'sleeping' Have the feeling that something is broken on my system. I have already reinstalled all grub2 files but without any progress. Where should I start looking for an improvement of the bootloader? -- Linux User 183145 using KDE4 Tumbleweed on a Pentium IV , powered by openSUSE 20160209 (x86_64) Kernel: 4.4.1-4.g4dac1be-default KDE Development Platform: 4.14.16 10:49am up 2:31, 2 users, load average: 2.76, 2.06, 1.33 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] KDE Neon and opensuse
by Alin Marin Elena 13 Feb '16

13 Feb '16

Dear All, Having in mind the discussions appeared lately about KDE Neon... I think we shall have an official postion since we still ship kde as default de. My main concern is that bugs reported from anything else than neon will be considered non-kde. Already had this experience working in a kde project with some of the supporters of neon... for background: this is Bryan article http://www.networkworld.com/article/3032063/opensource-subnet/kdes-new-linu… a more interesting because of comments version https://plus.google.com/+BryanLunduke/posts/XfLoyBaxeea the kde-promo mailing list (this got censored to prevent the best coming out from neon supporters) [kde-promo] KDE Neon and how to handle this? an interesting link on reedit... In which the is kde neon a distro question is answered... by one of the neon people... https://www.reddit.com/r/kde/comments/43tp4i/ is_kde_neon_a_distribution_or_not/ ten days ago seems the answer is: yes, and is indeed a fork/continuation of some other distro three days ago the answer seems to be yes and no... Regards, Alin -- Without Questions there are no Answers! ______________________________________________________________________ Dr. Alin Marin ELENA http://alin.elena.space/ ______________________________________________________________________

9 18

Re: [opensuse-kde] Leap Display settings
by Felix Miata 10 Feb '16

10 Feb '16

don fisher composed on 2016-02-09 11:25 (UTC-0700): > Felix Miata wrote: > Sorry, but I never made a screen shot before. How do you do this? My It used to be a utility aptly named ksnapshot, but since Kupstream recently decided an apt name was no longer appropriate, I don't recall its name. Try looking in graphics and utilities sections of main menu. If you don't see anything and googling is no help, inquire on the opensuse-kde or a kde.org mailing list what you're supposed to look for. > ~/.xsession-errors file is empty, yesterdays date. I have attached the > .xsession-errors-:0 file. Don't recall what the difference is right now. I don't either. > I have also attached the outputs of the zypper and lspci commands you > requested. Do you know how do you get Thunderbird to see fies starting > with a .? Possibly by a right click while the file picker is open to see something like "show all files". > felix.txt > zypper se -s | grep ^i | sort | egrep 'creen|randr' ... > lspci | grep VGA > 18:01:00.0 VGA compatible controller: NVIDIA Corporation GK104M [GeForce GTX 880M] (rev a1) > xsession-errors-:0 ... Nothing there that I recognize as trouble, except that the session was not plasma, but fvwm. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

RE: Re: [opensuse-kde] Leap Display settings
by stakanov＠freenet.de 09 Feb '16

09 Feb '16

> -----Ursprüngliche Nachricht----- > Von: Felix Miata > Gesendet: Di. 09.02.2016 20:06 > An: opensuse-kde(a)opensuse.org > Kopie: don fisher , > Betreff: Re: [opensuse-kde] Leap Display settings > > don fisher composed on 2016-02-09 11:25 (UTC-0700): > >> Felix Miata wrote: > >> Sorry, but I never made a screen shot before. How do you do this? My > > It used to be a utility aptly named ksnapshot, but since Kupstream recently > decided an apt name was no longer appropriate, I don't recall its name. Try > looking in graphics and utilities sections of main menu. If you don't see > anything and googling is no help, inquire on the opensuse-kde or a kde.org > mailing list what you're supposed to look for. > >> ~/.xsession-errors file is empty, yesterdays date. I have attached the >> .xsession-errors-:0 file. Don't recall what the difference is right now. > > I don't either. > >> I have also attached the outputs of the zypper and lspci commands you >> requested. Do you know how do you get Thunderbird to see fies starting >> with a .? > > Possibly by a right click while the file picker is open to see something like > "show all files". > >> felix.txt >> zypper se -s | grep ^i | sort | egrep 'creen|randr' > ... >> lspci | grep VGA >> 18:01:00.0 VGA compatible controller: NVIDIA Corporation GK104M [GeForce GTX 880M] (rev a1) > > >> xsession-errors-:0 > ... > Nothing there that I recognize as trouble, except that the session was not > plasma, but fvwm. > -- > "The wise are known for their understanding, and pleasant > words are persuasive." Proverbs 16:21 (New Living Translation) > > Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! > > Felix Miata *** http://fm.no-ip.com/ > -- > To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- The desired application is called "Spectacle" You can find it in Accessories or, if the shortcut is correctly set, it is sufficient as Per wrote to tap on the print screen button of you keyboard. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] How are opensuse doing on the webkit-security updates?
by ianseeks 09 Feb '16

09 Feb '16

There is an accusation that distros are a long way behind the curve on updates. https://blogs.gnome.org/mcatanzaro/2016/02/01/on-webkit-security-updates/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Does kmymoney work with KDEPIM5?
by Stefan Vater 08 Feb '16

08 Feb '16

Hi, after Tumbleweed switched to KDEPIM5, I would like to use it too. But I also need kmymoney which has no official kf5 based version yet, and depends on akonadi4 in some parts. However, when I try to upgrade yast/zypper does not suggest to uninstal kmymoney. So does it still work with new KDEPIM5? If anyone has experience in that, I would appreciate! Thanks, Stefan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] /var/tmp/kdecache-<username>/*
by Felix Miata 07 Feb '16

07 Feb '16

What's the purpose of multiple files of size 10280K or 82240K for every user who's ever logged into KDE? I find it hard to believe there would be more than a tiny fraction of icon files consuming space on disk compared to the 10280K icon-cache.kcache file, or that every user needs one or more theme cache's of 82240K. I also find it hard to believe a cache file of 82240K size could speed anything up. /var/tmp/kdecache-<username>/plasma-wallpapers/usr/share/wallpapers/Elarun/contents/images/2560x1600.png_#000000_0_1920x1200.png's 859115 byte consumption makes no sense either. What's the story on this puzzling filesystem space consumption? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

1 0

[opensuse-kde] Tumbleweed : constant crash of plasma5
by Bruno Friedmann 06 Feb '16

06 Feb '16

I'm seeing tons of crash with my newer TW Opening closing, changing desktop etc lead to several kind of crash. They are all marked as closed (upstream QT) or directly in kde like https://bugs.kde.org/show_bug.cgi?id=355650 or Most of them tagged as duplicate of https://bugs.kde.org/show_bug.cgi?id=342763 I'm a bit confuse, since the version indicated as fixed seems to be installed Qt5.5.1 or plasma5 at 5.5.3-1.1 Anyone who can drive me to better backtrace or stop the crash will be receive here as a "hero" :-)) Some informations. My computer is a new Dell Workstation Precision Laptop 7510 series with a Intel(R) Xeon(R) CPU E3-1535M v5 @ 2.90GHz as cpu Intel GPU is P630 + Nvidia Quadro M2000M (actually with nouveau on optimus configuration) (i915 + nouveau ) loaded. I've tried few days ago Nvidia LTS 352.79 and also the newer 316.18 With kernel 4.4.0 and latest 4.5-rc1 (from kernel:head) without seeing big differences. On compositor I'm using openGL 3.1 + EGL Typical crash backtrace : Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff9aa4b68c0 (LWP 19416))] Thread 8 (Thread 0x7ff993c31700 (LWP 19419)): #0 0x00007ff9a3a3724d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ff9a890d432 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7ff993c30c00) at /usr/include/bits/poll2.h:46 #2 0x00007ff9a890d432 in _xcb_conn_wait (c=c@entry=0xd3ed90, cond=cond@entry=0xd3edd0, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459 #3 0x00007ff9a890f007 in xcb_wait_for_event (c=0xd3ed90) at xcb_in.c:693 #4 0x00007ff995d80e29 in QXcbEventReader::run() (this=0xd492a0) at qxcbconnection.cpp:1229 #5 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0xd492a0) at thread/qthread_unix.cpp:331 #6 0x00007ff9a323e4a4 in start_thread (arg=0x7ff993c31700) at pthread_create.c:334 #7 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7ff991d9c700 (LWP 19426)): #0 0x00007ff9a3a3724d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ff9a012c264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7ff984003070, timeout=<optimized out>, context=0x7ff984000990) at gmain.c:4135 #2 0x00007ff9a012c264 in g_main_context_iterate (context=context@entry=0x7ff984000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3835 #3 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff984000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff9840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff991d9bcf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0xe23720) at thread/qthread.cpp:503 #7 0x00007ff9a73f39a5 in QQmlThreadPrivate::run() (this=0xe23720) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0xe23720) at thread/qthread_unix.cpp:331 #9 0x00007ff9a323e4a4 in start_thread (arg=0x7ff991d9c700) at pthread_create.c:334 #10 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7ff97ffc2700 (LWP 19427)): #0 0x00007ff9a016f4b9 in g_mutex_lock (mutex=mutex@entry=0x7ff978000990) at gthread-posix.c:1338 #1 0x00007ff9a012ba91 in g_main_context_query (context=context@entry=0x7ff978000990, max_priority=2147483647, timeout=timeout@entry=0x7ff97ffc1bdc, fds=fds@entry=0x7ff978002e70, n_fds=n_fds@entry=1) at gmain.c:3544 #2 0x00007ff9a012c1df in g_main_context_iterate (context=context@entry=0x7ff978000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3822 #3 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff978000990, may_block=may_block@entry=1) at gmain.c:3901 #4 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff9780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff97ffc1cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x11bd4a0) at thread/qthread.cpp:503 #7 0x00007ff9a73f39a5 in QQmlThreadPrivate::run() (this=0x11bd4a0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #8 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x11bd4a0) at thread/qthread_unix.cpp:331 #9 0x00007ff9a323e4a4 in start_thread (arg=0x7ff97ffc2700) at pthread_create.c:334 #10 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7ff97e752700 (LWP 19428)): #0 0x00007ff9a012b8a6 in g_main_context_prepare (context=context@entry=0x7ff970000990, priority=priority@entry=0x7ff97e751bd8) at gmain.c:3453 #1 0x00007ff9a012c193 in g_main_context_iterate (context=context@entry=0x7ff970000990, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3820 #2 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff970000990, may_block=may_block@entry=1) at gmain.c:3901 #3 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff9700008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff97e751cf0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x1243b90) at thread/qthread.cpp:503 #6 0x00007ff9a73f39a5 in QQmlThreadPrivate::run() (this=0x1243b90) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141 #7 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x1243b90) at thread/qthread_unix.cpp:331 #8 0x00007ff9a323e4a4 in start_thread (arg=0x7ff97e752700) at pthread_create.c:334 #9 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7ff97ce67700 (LWP 19430)): #0 0x00007ff9a324407f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007ff9a9b9ba84 in QTWTF::TCMalloc_PageHeap::scavengerThread() (this=0x7ff9a9e82ea0 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00007ff9a9b9bac9 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00007ff9a323e4a4 in start_thread (arg=0x7ff97ce67700) at pthread_create.c:334 #4 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7ff974ac3700 (LWP 19436)): #0 0x00007ff9a3a3724d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007ff9a012c264 in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7ff8e40041d0, timeout=<optimized out>, context=0x7ff8e400c7f0) at gmain.c:4135 #2 0x00007ff9a012c264 in g_main_context_iterate (context=context@entry=0x7ff8e400c7f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3835 #3 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff8e400c7f0, may_block=may_block@entry=1) at gmain.c:3901 #4 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff8e40040b0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #5 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff974ac2cb0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x1964ad0) at thread/qthread.cpp:503 #7 0x00007ff9a7f78e42 in QQuickPixmapReader::run() (this=0x1964ad0) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/quick/util/qquickpixmapcache.cpp:760 #8 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x1964ad0) at thread/qthread_unix.cpp:331 #9 0x00007ff9a323e4a4 in start_thread (arg=0x7ff974ac3700) at pthread_create.c:334 #10 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7ff8ea7fe700 (LWP 19440)): #0 0x00007ff9a016f4d4 in g_mutex_unlock (mutex=0x7ff8dc00c700) at gthread-posix.c:1350 #1 0x00007ff9a012c186 in g_main_context_iterate (context=context@entry=0x7ff8dc00c700, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3818 #2 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff8dc00c700, may_block=may_block@entry=1) at gmain.c:3901 #3 0x00007ff9a434d52b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7ff8dc002c70, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ff8ea7fdcd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x00007ff9a4123b1c in QThread::exec() (this=this@entry=0x3c6aa80) at thread/qthread.cpp:503 #6 0x00007ff8d207ce47 in KCupsConnection::run() (this=0x3c6aa80) at /usr/src/debug/print-manager-15.12.1/libkcups/KCupsConnection.cpp:304 #7 0x00007ff9a412894f in QThreadPrivate::start(void*) (arg=0x3c6aa80) at thread/qthread_unix.cpp:331 #8 0x00007ff9a323e4a4 in start_thread (arg=0x7ff8ea7fe700) at pthread_create.c:334 #9 0x00007ff9a3a3fbdd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7ff9aa4b68c0 (LWP 19416)): [KCrash Handler] #6 0x00007ff9a71cfdf8 in VDMModelDelegateDataType::notify(QQmlAdaptorModel const&, QList<QQmlDelegateModelItem*> const&, int, int, QVector<int> const&) const (this=<optimized out>, items=..., index=1, count=1, roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/util/qqmladaptormodel.cpp:167 #7 0x00007ff9a74328ea in QQmlDelegateModel::_q_itemsChanged(int, int, QVector<int> const&) (roles=..., count=1, index=1, items=..., this=<optimized out>) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/util/qqmladaptormodel_p.h:118 #8 0x00007ff9a74328ea in QQmlDelegateModel::_q_itemsChanged(int, int, QVector<int> const&) (this=<optimized out>, index=1, count=1, roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/types/qqmldelegatemodel.cpp:1144 #9 0x00007ff9a7432a1a in QQmlDelegateModel::_q_dataChanged(QModelIndex const&, QModelIndex const&, QVector<int> const&) (this=<optimized out>, begin=..., end=..., roles=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/types/qqmldelegatemodel.cpp:1546 #10 0x00007ff9a74585bc in QQmlDelegateModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x35b7e60, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=12, _a=_a@entry=0x7ffe92db6a80) at .moc/moc_qqmldelegatemodel_p.cpp:203 #11 0x00007ff9a7458ca8 in QQmlDelegateModel::qt_metacall(QMetaObject::Call, int, void**) (this=0x35b7e60, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0x7ffe92db6a80) at .moc/moc_qqmldelegatemodel_p.cpp:344 #12 0x00007ff9a4327140 in QMetaObject::activate(QObject*, int, int, void**) (sender=0x35a62d0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6a80) at kernel/qobject.cpp:3728 #13 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=<optimized out>, m=m@entry=0x7ff9a473cf40 <QAbstractItemModel::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6a80) at kernel/qobject.cpp:3578 #14 0x00007ff9a439f21c in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector<int> const&) (this=<optimized out>, _t1=..., _t2=..., _t3=...) at .moc/moc_qabstractitemmodel.cpp:548 #15 0x00007ff8e80d1834 in TaskManager::TasksModelPrivate::itemChanged(QFlags<TaskManager::TaskChange>) (this=0x35a5b70, changes=...) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/tasksmodel.cpp:521 #16 0x00007ff8e80d29b7 in TaskManager::TasksModel::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=_o@entry=0x35a62d0, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=9, _a=_a@entry=0x7ffe92db6c60) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_tasksmodel.cpp:214 #17 0x00007ff9a4326f8a in QMetaObject::activate(QObject*, int, int, void**) (sender=0x3f2ff70, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6c60) at kernel/qobject.cpp:3713 #18 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=<optimized out>, m=m@entry=0x7ff8e82f7900 <TaskManager::AbstractGroupableItem::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6c60) at kernel/qobject.cpp:3578 #19 0x00007ff8e80da338 in TaskManager::AbstractGroupableItem::changed(QFlags<TaskManager::TaskChange>) (this=<optimized out>, _t1=...) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_abstractgroupableitem.cpp:223 #20 0x00007ff8e80c7b90 in TaskManager::TaskItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (change=..., this=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/taskitem.cpp:73 #21 0x00007ff8e80c7b90 in TaskManager::TaskItem::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_taskitem.cpp:147 #22 0x00007ff9a4326f8a in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x358f0e0, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6da0) at kernel/qobject.cpp:3713 #23 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x358f0e0, m=m@entry=0x7ff8e82f7600 <TaskManager::Task::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe92db6da0) at kernel/qobject.cpp:3578 #24 0x00007ff8e80da468 in TaskManager::Task::changed(QFlags<TaskManager::TaskChange>) (this=this@entry=0x358f0e0, _t1=...) at /usr/src/debug/plasma-workspace-5.5.3/build/libtaskmanager/moc_task.cpp:359 #25 0x00007ff8e80ba22b in TaskManager::Task::setActive(bool) (this=this@entry=0x358f0e0, a=a@entry=true) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/task.cpp:178 #26 0x00007ff8e80cd759 in TaskManager::TaskManager::activeWindowChanged(unsigned long long) (this=0x7ff8e82f8fa0 <TaskManager::(anonymous namespace)::Q_QGS_privateTaskManagerSelf::innerFunction()::holder>, w=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/libtaskmanager/taskmanager.cpp:412 #27 0x00007ff9a4326e17 in QMetaObject::activate(QObject*, int, int, void**) (a=0x7ffe92db6f20, r=0x7ff8e82f8fa0 <TaskManager::(anonymous namespace)::Q_QGS_privateTaskManagerSelf::innerFunction()::holder>, this=<optimized out>) at ../../src/corelib/kernel/qobject_impl.h:124 #28 0x00007ff9a4326e17 in QMetaObject::activate(QObject*, int, int, void**) (sender=sender@entry=0x7ff9a7125c00 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>, signalOffset=<optimized out>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe92db6f20) at kernel/qobject.cpp:3698 #29 0x00007ff9a4327787 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x7ff9a7125c00 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>, m=m@entry=0x7ff9a7124b80 <KWindowSystem::staticMetaObject>, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffe92db6f20) at kernel/qobject.cpp:3578 #30 0x00007ff9a6f170e2 in KWindowSystem::activeWindowChanged(unsigned long long) (this=this@entry=0x7ff9a7125c00 <(anonymous namespace)::Q_QGS_g_kwmInstanceContainer::innerFunction()::holder>, _t1=132120581) at /usr/src/debug/kwindowsystem-5.18.0/build/src/moc_kwindowsystem.cpp:303 #31 0x00007ff991fb080b in NETEventFilter::nativeEventFilter(xcb_generic_event_t*) (this=0x317ae40, ev=0x7ff98c007b60) at /usr/src/debug/kwindowsystem-5.18.0/src/platforms/xcb/kwindowsystem.cpp:208 #32 0x00007ff9a42f687f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) (this=<optimized out>, eventType=..., message=message@entry=0x7ff98c007b60, result=result@entry=0x7ffe92db7048) at kernel/qabstracteventdispatcher.cpp:460 #33 0x00007ff995d84804 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) (this=this@entry=0xd3d1a0, event=event@entry=0x7ff98c007b60) at qxcbconnection.cpp:1020 #34 0x00007ff995d8558b in QXcbConnection::processXcbEvents() (this=0xd3d1a0) at qxcbconnection.cpp:1504 #35 0x00007ff9a4327d79 in QObject::event(QEvent*) (this=0xd3d1a0, e=<optimized out>) at kernel/qobject.cpp:1239 #36 0x00007ff9a56708cc in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=this@entry=0xd2e2e0, receiver=receiver@entry=0xd3d1a0, e=e@entry=0x7ff98c003c80) at kernel/qapplication.cpp:3716 #37 0x00007ff9a56759d6 in QApplication::notify(QObject*, QEvent*) (this=0x7ffe92db7760, receiver=0xd3d1a0, e=0x7ff98c003c80) at kernel/qapplication.cpp:3499 #38 0x00007ff9a42f9cf3 in QCoreApplication::notifyInternal(QObject*, QEvent*) (this=0x7ffe92db7760, receiver=0xd3d1a0, event=event@entry=0x7ff98c003c80) at kernel/qcoreapplication.cpp:965 #39 0x00007ff9a42fc016 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (event=0x7ff98c003c80, receiver=<optimized out>) at kernel/qcoreapplication.h:224 #40 0x00007ff9a42fc016 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xd237b0) at kernel/qcoreapplication.cpp:1593 #41 0x00007ff9a42fc4f8 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1451 #42 0x00007ff9a434d103 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0xd7e500) at kernel/qeventdispatcher_glib.cpp:271 #43 0x00007ff9a012c097 in g_main_context_dispatch (context=0x7ff98c0016f0) at gmain.c:3154 #44 0x00007ff9a012c097 in g_main_context_dispatch (context=context@entry=0x7ff98c0016f0) at gmain.c:3769 #45 0x00007ff9a012c2c8 in g_main_context_iterate (context=context@entry=0x7ff98c0016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3840 #46 0x00007ff9a012c36c in g_main_context_iteration (context=0x7ff98c0016f0, may_block=may_block@entry=1) at gmain.c:3901 #47 0x00007ff9a434d50f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0xda0be0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #48 0x00007ff9a42f763a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffe92db7610, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #49 0x00007ff9a42ff2fd in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1229 #50 0x00007ff9a483553c in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1527 #51 0x00007ff9a566cf75 in QApplication::exec() () at kernel/qapplication.cpp:2976 #52 0x0000000000436527 in main(int, char**) (argc=4, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.5.3/shell/main.cpp:179 -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] KDE Keyboard Shortcuts work everywhere except in KDE apps
by billb＠sent.at 05 Feb '16

05 Feb '16

I installed OpenSUSE Leap 42.1. I want the newer KDE experience, so following the info at https://en.opensuse.org/SDB:KDE_repositories I installed Version: Leap 42.1 Extra: http://download.opensuse.org/repositories/KDE:/Extra/openSUSE_Leap_42.1/ Applications: http://download.opensuse.org/repositories/KDE:/Applications/openSUSE_Leap_4… KDE Frameworks 5: http://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Leap_42… I want to have a Keyboard Shortcut assigned to type my email address on a keystroke. So I opened "System Settings"/"Workspace"/"Shortcuts"/"Custom Shortcuts"/"Configure Input Actions settings". I right-clicked and created a "New > Global Shortcut > Send keyboard input" shortcut with Name == "TypeMyEmail" Then I set Comment == "Comment" Trigger == "Meta+Ctrl+Alt+M" Action == "m:e:Shift+2:e:x:a:m:p:l:e:.:c:o:m" I open a LibreOffice document and press "Meta+Ctrl+Alt+M". I immediately get the email address me(a)example.com typed into the document. I test it in Firefox when filling out forms and it works too. But when I try it in any KDE application, like Kate or Konsole, I don't get the address output. I get different output depending on the app. For example in Kate -> "." in Konsole -> "^C" in ApplicationLauncher -> it closes the window in Dolphin -> "." How do I fix this so the KDE Shortcuts work in KDE apps too? Bill -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1

[opensuse-kde] digikam and marble
by Olaf Hering 03 Feb '16

03 Feb '16

Problem: digikam-libs-4.14.0-3.1.x86_64 requires marble-data, but this requirement cannot be provided A few months ago I tried to install digikam, which would have installed "half of KDE". As a result I have added a lock on "marble", then installed digikam and all was fine. The current digikam pkg introduced a hard requirement for marble. Will digikam really stop working when marble is not installed? Perhaps the "Requires: marble-data" was meant to be a Recommends. Olaf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

2 1