openSUSE KDE July 2016

kde@lists.opensuse.org

22 participants
22 discussions

[opensuse-kde] cannot add google calendars to korganizer

by Patrick Shanahan

openSUSE Tumbleweed kdepim-16.04.0-60.3.x86_64 kdepim-addons-16.04.0-4.1.x86_64 kdepim-apps-libs-16.04.0-1.1.x86_64 kdepimlibs4-4.14.10-1.2.x86_64 kdepim-runtime-16.04.0-36.1.x86_64 kio-pimlibs-16.04.0-49.1.x86_64 libbaloopim4-4.14.3-2.2.x86_64 libkdepim-16.04.0-1.3.x86_64 libkdepimlibs4-4.14.10-1.2.x86_64 libKF5Libkdepim5-16.04.0-1.3.x86_64 this machine originally ran 12.1, used Greg KH's "rolling" updates into original Tumbleweed and up-to-date. I cannot add google calendar to korganizer. asks for google acct name, then password allow permission to akonadi to access google services "authorizing token. This should take just a moment.." window closes with no error msg but calendar does not appear help please. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 years, 6 months

[opensuse-kde] gtk3 apps ignoring Plasma UI fonts

by Felix Miata

FF 47.0.1 is my most used example, occurring on multiple installations on multiple machines with multiple profiles. I install FF ESR rpm, and use mozilla.org binaries for other releases. In 5.24.0/QT5.6.1 (aka TW; as well as 13.2/KDE4), FF 47 is ignoring UI fonts, as if its UI DPI was set to a lower value (e.g. 96) rather than actual DPI (e.g. 120). However, fonts and DPI in web pages are working exactly the same as in ESR. This was not a problem with mozilla.org's 46.0.x. Neither is it a problem with 47.0.1 running KDE3, so I'm in brainlock what to try. Even though kde-gtk-config5 is installed, there is no place I can find in Plasma5 systemsettings to choose GTK fonts, and I'm at a loss to figure out what other package might be missing to provide such control. Is there any such package any more for controlling fonts in either GTK2 or GTK3 apps in the latest Plasma? If so, what? -- "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

4 years, 9 months

[opensuse-kde] KShutdown as root

by Markus Slopianka

Hi. Why does KShutdown run as root? It works just fine without it. Why does my Submit Request to fix that get declined with nothing but a "No"? https://build.opensuse.org/request/show/406887 The SR that implemented that change <https://build.opensuse.org/request/show/397792>, is not helpful at all. The only description is "Please accept these changes" and the changelog also does clarify the change to run KShutdown as root. Can anyone please enlighten me? Bye. Markus -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 years, 11 months

[opensuse-kde] Inconsistent set of Unstable KDE repositories for Tumbleweed

by Freek de Kruijf

I am trying to install the unstable KDE repositories, but trying to do a "zypper dup" on the repository http://download.opensuse.org/repositories/KDE:/ Qt56/openSUSE_Factory/ results in removing almost all KDE applications. Trying to update i.e. akonadi_resources results in a lot of changes to a lower architecture. Trying to dup Applications shows one missing module: libQt5Core.so.5. It looks like the package libQt5Core is missing; libQt5Core-devel is available. Also libQt5Core5 is available. Bug report? -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 years, 11 months

[opensuse-kde] Plasma 5.8 and openSUSE 42.2

by Antonio Larrosa

Hello, As you know, a few weeks ago KDE announced Plasma 5.8 would be a LTS release. I think the decision to create a LTS release was at least partly caused by our (openSUSE) needs, so I think it's nice of them to decide to do that for us and I think it would benefit both KDE and openSUSE if we included Plasma 5.8 in openSUSE Leap 42.2 . 18 months of upstream support? I'm sure nobody would say no to that. The problem comes when one looks at the schedules for Plasma and openSUSE Leap releases: https://community.kde.org/Schedules/Plasma_5 https://en.opensuse.org/openSUSE:Roadmap The main part of the current schedules is: 2016-08-25: openSUSE 42.2 Beta 1 2016-09-15: KDE 5.8 Repo Freeze 2016-09-21: openSUSE 42.2 Beta 2 - Package freeze 2016-09-29: KDE 5.7.95 LTS (5.8.0 Beta) 2016-10-06: openSUSE 42.2 RC1 2016-10-13: KDE 5.8.0 LTS Release 2016-10-18: openSUSE 42.2 RC2 first week of November 2016: openSUSE 42.2 Release As you see, there's quite bad timing in there. I've talked with some plasma developers and Ludwig separately trying to move both schedules around in a way that could make it possible to get 5.8.0 in openSUSE 42.2. I have a proposal that I think (and hope) that will satisfy everyone so I think it's time to move this forward to all involved parties. In that sense, I wrote a very similar mail to the plasma developers and will send it at the same time than this one. I hope you like the proposal and note that I've tried to keep in mind the needs of each project (QtCon/Akademy dates and the desire to have a stable Plasma release on one side, SUSECon/SLE12SP2/other dates and the desire to have a stable openSUSE release on the other). This mean bringing forward some kde release dates and postponing some openSUSE pre-releases to make everything fit tightly: 2016-09-01: openSUSE 42.2 Beta 1 (this would include the last Plasma release available at that time, 5.7.4 or 5.7.5) 2016-09-08: Plasma 5.8 Repo Freeze (last day of Akademy, maybe that could be moved to freeze the repo just before QtCon?) 2016-09-15: Plasma 5.7.95 LTS (aka 5.8.0 Beta) 2016-09-21: openSUSE 42.2 Beta 2 - Package freeze (with 5.7.95) 2016-09-29: Plasma 5.8.0 LTS Release 2016-10-06: openSUSE 42.2 RC1 (with Plasma 5.8.0) 2016-10-11: Plasma 5.8.1 LTS 2016-10-18: openSUSE 42.2 RC2 (most probably including Plasma 5.8.1 if bugs found and depending on the size of changes) 2016-10-18: Plasma 5.8.2 LTS 2016-11-01: Plasma 5.8.3 LTS First week of November 2016: openSUSE 42.2 Release Following that schedule means that openSUSE 42.2 would be released including 5.8.1. This would mean too that we (can I include myself as a kde packager too? :) ) would have less time to package KDE releases for 42.2 and less time to test them too since some openSUSE betas would be postponed but RC1 and RC2 would stay at the same dates. Ludwig also mentioned he's willing to shift the Leap schedule a bit more if needed, but for now, the proposal is what's stated above. So, my question is, would you agree with that? Anybody sees any problem if both projects agree to those changes to their respective schedules? Please, keep in mind that both projects have needs and requirements, but it would be great to find one solution that benefits both of us and for that, both projects have to give in a little. Thanks, -- Antonio Larrosa alarrosa(a)suse.de larrosa(a)kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org

4 years, 11 months

[opensuse-kde] Tumbleweed : drkonqui crash each time kde plasma5 is started SEGV

by Bruno Friedmann

Everytime I start my computer, I've an event for drkonqui in coredump I'm using autologin qt-kt:~ # coredumpctl gdb 1024 PID: 1024 (drkonqi) UID: 1502 (bruno) GID: 1500 (ioda) Signal: 6 (ABRT) Timestamp: Sun 2016-07-17 11:01:25 CEST (5h 46min ago) Command Line: /usr/lib64/libexec/drkonqi -platform xcb -display :0 --appname kdeinit5 --kdeinit --apppath /usr/bin --signal 11 --pid 3054 --startupid 0 -- restarted Executable: /usr/lib64/libexec/drkonqi Control Group: /user.slice/user-1502.slice/session-1.scope Unit: session-1.scope Slice: user-1502.slice Session: 1 Owner UID: 1502 (bruno) Boot ID: a24e755e12b84261a49ff60422e4d104 Machine ID: 5796a69412fbda1c055a261856a26e81 Hostname: qt-kt.labaroche.ioda.net Coredump: /var/lib/systemd/coredump/core.drkonqi. 1502.a24e755e12b84261a49ff60422e4d104.1024.1468746085000000.xz Message: Process 1024 (drkonqi) of user 1502 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib64/libexec/drkonqi...Reading symbols from /usr/ lib/debug/usr/lib64/libexec/drkonqi.debug...done. done. [New LWP 1024] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib64/libexec/drkonqi -platform xcb -display :0 -- appname kdeinit5 --kdein'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f31b1195975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007f31b1195975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 #1 0x00007f31b1196d8a in __GI_abort () at abort.c:78 #2 0x00007f31b1925331 in QMessageLogger::fatal(char const*, ...) const (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1648 #3 0x00007f31b1925331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffcd36cf170, msg=msg@entry=0x7f31a6d14a10 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:790 #4 0x00007f31a6c8a007 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (this= 0x22486b0, nativeInterface=0x22485b0, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:585 #5 0x00007f31a6c8cede in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (this=<optimized out>, parameters=..., argc=@0x7ffcd36cf7bc: 13, argv=0x7ffcd36cfa28) at qxcbintegration.cpp:179 #6 0x00007f31a6f8e4fd in QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (this=<optimized out>, system=..., parameters=..., argc=@0x7ffcd36cf7bc: 13, argv=0x7ffcd36cfa28) at qxcbmain.cpp:50 #7 0x00007f31b2057d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (argv=0x7ffcd36cfa28, argc=@0x7ffcd36cf7bc: 13, parameters=..., key=..., loader=<optimized out>) at kernel/qplatformintegrationfactory.cpp:56 #8 0x00007f31b2057d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (platform=..., paramList=..., argc=@0x7ffcd36cf7bc: 13, argv=argv@entry=0x7ffcd36cfa28, platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:73 #9 0x00007f31b2066365 in QGuiApplicationPrivate::createPlatformIntegration() (argv=<optimized out>, argc=@0x7ffcd36cf7bc: 13, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1058 #10 0x00007f31b2066365 in QGuiApplicationPrivate::createPlatformIntegration() (this=0x222e620) at kernel/qguiapplication.cpp:1227 #11 0x00007f31b206715d in QGuiApplicationPrivate::createEventDispatcher() (this=<optimized out>) at kernel/qguiapplication.cpp:1244 #12 0x00007f31b1b1bd5f in QCoreApplicationPrivate::init() (this=this@entry=0x222e620) at kernel/qcoreapplication.cpp:814 #13 0x00007f31b2068adf in QGuiApplicationPrivate::init() (this=this@entry=0x222e620) at kernel/qguiapplication.cpp:1267 #14 0x00007f31b285e329 in QApplicationPrivate::init() (this=0x222e620) at kernel/qapplication.cpp:578 #15 0x000000000041db89 in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/plasma-workspace-5.7.0/drkonqi/ main.cpp:60 (gdb) This kind of crash exist since months, and I would like to improve my start speed, so limiting SEGV on boot and coredump collection would be a first step. I've reported that some months ago, https://bugs.kde.org/show_bug.cgi?id=363676 Am I alone to experiment this kind of crash ? If not could you add your backtrace to the bug, so its status will move to confirmed. To check just run coredumpctl --no-pager to see the list of those your system could have cought. Thanks for your attention. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, 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

4 years, 12 months

[opensuse-kde] Inconsistent set of Unstable KDE repositories for Tumbleweed

by Freek de Kruijf

5 years

[opensuse-kde] Leap 42.1 + KDE:/Frameworks5 KDE:/Qt5 KDE:/Applications and owncloud SEGV

by Bruno Friedmann

Until recently the combination in subject was working well. But since a few days (sorry can say exactly when) trying to run owncloud installed from repositories/isv:/ownCloud:/desktop/ openSUSE_Leap_42.1 give a SEGV in owncloud. I know this not a good ideas about mixing repositories, but as it was working previously it should continue ;-) Here's the (non perfect yet for dev) backtrace. (gdb) run Starting program: /usr/bin/owncloud Missing separate debuginfos, use: zypper install glibc- debuginfo-2.19-22.1.x86_64 [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe164a700 (LWP 6159)] Detaching after fork from child process 6160. Detaching after fork from child process 6165. Detaching after fork from child process 6182. [New Thread 0x7fffd1e9f700 (LWP 6186)] [New Thread 0x7fffe207f700 (LWP 6158)] [New Thread 0x7fffe32c5700 (LWP 6157)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd1e9f700 (LWP 6186)] 0x00007fffd103400e in ?? () from /usr/lib64/libkdecore.so.5 (gdb) bt #0 0x00007fffd103400e in () at /usr/lib64/libkdecore.so.5 #1 0x00007ffff7dea8ea in call_init.part () at /lib64/ld-linux-x86-64.so.2 #2 0x00007ffff7dea9d3 in _dl_init_internal () at /lib64/ld-linux-x86-64.so.2 #3 0x00007ffff7deeb08 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2 #4 0x00007ffff7dea7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #5 0x00007ffff7dee2fb in _dl_open () at /lib64/ld-linux-x86-64.so.2 #6 0x00007fffebb5d02b in dlopen_doit () at /lib64/libdl.so.2 #7 0x00007ffff7dea7a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2 #8 0x00007fffebb5d5dd in _dlerror_run () at /lib64/libdl.so.2 #9 0x00007fffebb5d0c1 in dlopen@@GLIBC_2.2.5 () at /lib64/libdl.so.2 #10 0x00007fffe81d4f25 in libmodman::module_manager::load_file(std::string, bool) () at /usr/lib64/libmodman.so.1 #11 0x00007fffe81d52b3 in libmodman::module_manager::load_dir(std::string, bool) () at /usr/lib64/libmodman.so.1 #12 0x00007fffec442e06 in () at /usr/lib64/libproxy.so.1 #13 0x00007fffec4439bb in px_proxy_factory_new () at /usr/lib64/libproxy.so.1 #14 0x00007ffff3c475d9 in QNetworkProxyFactory::systemProxyForQuery(QNetworkProxyQuery const&) () at / usr/lib64/libQt5Network.so.5 #15 0x00007ffff4e8a1aa in OCC::SystemProxyRunnable::run() () at /usr/lib64/ libowncloudsync.so.0 #16 0x00007ffff357f7ce in () at /usr/lib64/libQt5Core.so.5 #17 0x00007ffff3582899 in () at /usr/lib64/libQt5Core.so.5 #18 0x00007ffff173f0a4 in start_thread () at /lib64/libpthread.so.0 #19 0x00007ffff214202d in clone () at /lib64/libc.so.6 (gdb) cont Continuing. [Thread 0x7fffd1e9f700 (LWP 6186) exited] [Thread 0x7fffe164a700 (LWP 6159) exited] [Thread 0x7fffe207f700 (LWP 6158) exited] [Thread 0x7fffe32c5700 (LWP 6157) exited] Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. Has someone an idea ? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, 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

5 years

[opensuse-kde] Tumbleweed : kdeinit crash (segv) each time plasma5 start

by Bruno Friedmann

Related to drkonqui thread I'm seeing in parallel crash of kdeinit each time kde plasma5 session is started. I've this backtrace coredumpctl gdb 1027 PID: 1027 (klauncher) UID: 1502 (bruno) GID: 1500 (ioda) Signal: 6 (ABRT) Timestamp: Sun 2016-07-17 11:01:25 CEST (5h 55min ago) Command Line: klauncher [kdeinit5] --fd= Executable: /usr/bin/kdeinit5 Control Group: /user.slice/user-1502.slice/session-1.scope Unit: session-1.scope Slice: user-1502.slice Session: 1 Owner UID: 1502 (bruno) Boot ID: a24e755e12b84261a49ff60422e4d104 Machine ID: 5796a69412fbda1c055a261856a26e81 Hostname: qt-kt.labaroche.ioda.net Coredump: /var/lib/systemd/coredump/core.klauncher. 1502.a24e755e12b84261a49ff60422e4d104.1027.1468746085000000.xz Message: Process 1027 (klauncher) of user 1502 dumped core. GNU gdb (GDB; openSUSE Tumbleweed) 7.11.1 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/kdeinit5...Reading symbols from /usr/lib/debug/ usr/bin/kdeinit5.debug...done. done. warning: core file may not match specified executable file. [New LWP 1027] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `klauncher [kdeinit'. Program terminated with signal SIGABRT, Aborted. #0 0x00007f0af0b36975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 0x00007f0af0b36975 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/ sysv/linux/raise.c:54 #1 0x00007f0af0b37d8a in __GI_abort () at abort.c:78 #2 0x00007f0af0f3e331 in QMessageLogger::fatal(char const*, ...) const (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1648 #3 0x00007f0af0f3e331 in QMessageLogger::fatal(char const*, ...) const (this=this@entry=0x7ffdd8dcd240, msg=msg@entry=0x7f0ae0b2ca10 "QXcbConnection: Could not connect to display %s") at global/qlogging.cpp:790 #4 0x00007f0ae0aa2007 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (this= 0xff4f00, nativeInterface=0xff4e00, canGrabServer=<optimized out>, defaultVisualId=<optimized out>, displayName=<optimized out>) at qxcbconnection.cpp:585 #5 0x00007f0ae0aa4ede in QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (this=<optimized out>, parameters=..., argc=@0x7ffdd8dcd84c: 2, argv=0xfd4770) at qxcbintegration.cpp:179 #6 0x00007f0ae0d614fd in QXcbIntegrationPlugin::create(QString const&, QStringList const&, int&, char**) (this=<optimized out>, system=..., parameters=..., argc=@0x7ffdd8dcd84c: 2, argv=0xfd4770) at qxcbmain.cpp:50 #7 0x00007f0af1670d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (argv=0xfd4770, argc=@0x7ffdd8dcd84c: 2, parameters=..., key=..., loader=<optimized out>) at kernel/qplatformintegrationfactory.cpp:56 #8 0x00007f0af1670d1d in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (platform=..., paramList=..., argc=@0x7ffdd8dcd84c: 2, argv=argv@entry=0xfd4770, platformPluginPath=...) at kernel/qplatformintegrationfactory.cpp:73 #9 0x00007f0af167f365 in QGuiApplicationPrivate::createPlatformIntegration() (argv=<optimized out>, argc=@0x7ffdd8dcd84c: 2, platformThemeName=..., platformPluginPath=..., pluginArgument=...) at kernel/qguiapplication.cpp:1058 #10 0x00007f0af167f365 in QGuiApplicationPrivate::createPlatformIntegration() (this=0xfe03a0) at kernel/qguiapplication.cpp:1227 #11 0x00007f0af168015d in QGuiApplicationPrivate::createEventDispatcher() (this=<optimized out>) at kernel/qguiapplication.cpp:1244 #12 0x00007f0af1134d5f in QCoreApplicationPrivate::init() (this=this@entry=0xfe03a0) at kernel/qcoreapplication.cpp:814 #13 0x00007f0af1681adf in QGuiApplicationPrivate::init() (this=0xfe03a0) at kernel/qguiapplication.cpp:1267 #14 0x00007f0af16828f4 in QGuiApplication::QGuiApplication(int&, char**, int) (this=0x7ffdd8dcd880, argc=@0x7ffdd8dcd84c: 2, argv=0xfd4770, flags=329217) at kernel/qguiapplication.cpp:573 #15 0x00007f0ae0f72b7a in kdemain(int, char**) (argc=<optimized out>, argv=0xfd4770) at /usr/src/debug/kinit-5.24.0/src/klauncher/ klauncher_main.cpp:162 #16 0x000000000040886d in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) (argc=argc@entry=2, _name=_name@entry=0x40b247 "klauncher", args=<optimized out>, args@entry=0x7ffdd8dcdcd0 "--fd=8", cwd=cwd@entry=0x0, envc=envc@entry=0, envs=<optimized out>, envs@entry=0x0, reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x40b293 "0") at /usr/src/debug/kinit-5.24.0/src/kdeinit/kinit.cpp:759 #17 0x0000000000409687 in start_klauncher() () at /usr/src/debug/kinit-5.24.0/ src/kdeinit/kinit.cpp:1047 #18 0x0000000000405bb5 in main(int, char**) (argc=1, argv=<optimized out>) at /usr/src/debug/kinit-5.24.0/src/kdeinit/kinit.cpp:1809 (gdb I would like to report it but I don't know which component is related in bugs.kde.org or should it goes to qt directly ??? In both case, it's look like a (normally damn fixed qt5 bug about non existing screen or whatever xcb things) ;-) Thanks for your advise . -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, 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

5 years

[opensuse-kde] Rationale behind libqt5-qtbase

by Bruno Friedmann

I was surprized to not seen 5.6.2 still in TW (5.6.1 just coming today). I'm an unfortunate owner of skydale laptop (on which I only use nvidia blob). I'm also using multi-screen both are hidpi, and of course have different DPI but same size.... Few weeks ago, I was using K:Unstable and see a good improvement in qt 5.6.2 (almost stable without any crashes, even those nobody cares because they are trapped by the systemd/coredump) Try coredumpctl --no-pager to understand what I mean :-) So backtracing from where come libqt5-qtbase in Factory, and point to https://build.opensuse.org/package/show/KDE:Qt5/libqt5-qtbase Which start to integrate 5.7 actually. I would like to know if 5.6.2 will have a chance to finish in TW ? Perhaps it is already coming, and I was not able to retrieve its SR Thanks for the packages, and work done on maintenance, and your invaluable support. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, 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

5 years

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE KDE July 2016