Hello!
Recently I've maid Qt5 build of leechcraft package and found interesting
runtime issue. Leechcraft loads Qt5Network library (linking) that loads
libproxy1 (linking) that loads libproxy1-config-kde4 if it is installed
(plugin) that loads kde4 libs and finally Qt4 libs that leads to a
segmentation fault. Fuh =) Any ideas? Does every Qt5Network linked package
have to conflict against libproxy1-config-kde4 package?
--
Best regards,
Dmitriy DA(P).DarkneSS Perlow @ Linux x64
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hi,
Using oS 13.2 x86_64, kde 4.14.4 and several earlier versions on a
computer with the nvidia binary graphics driver, occasionally the
krunner window (Alt-F2) is repelled by the mouse pointer when it is
placed near the right or left side of the window. If it is placed on the
top side, then moving the mouse drags the window with it.
Has anyone else seen this? Any ideas about debugging it?
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We're plagued by a bug that is in its nature minor, but makes the whole
Factory development model a mess: plasma doesn't start correctly
*sometimes* on first boot.
It's always the same - the system installs cleanly and then you end up
in a screen like this:
https://openqa.opensuse.org/tests/49951/modules/first_boot/steps/2
Plasma is fine - beside the missing panel. We changed the tests to
upload tons of log files (download them from e.g
https://openqa.opensuse.org/tests/49951), but noone so far found
the reason.
I bet this is a stupid race of config file creation deep within plasma
initial startup - but it's a real bug and we need someone to hunt it ;(
I will test drive as many patches as needed, but someone needs to
actually create debug output or develop a theory what's going on.
Greetings, Stephan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlTsNVEACgkQwFSBhlBjoJZ3FACff6RV0Dif9HUF/PaeQ0CeagZy
DzsAniOxZyxuDWELvh+itmjCNS0N1a/L
=a7GU
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Introducing our 3D/2D animation services.
We are specialized in providing 3D designing/modelling/animation services
across the globe. From 3D architecture, character animation, 3D
industrialdesign, rendering, prototype animation to 3D walkthroughs, we
provide high
quality effects to provide a virtual product.
We do mainly belowings:
3D Animation
2D Animation
Architecture Visualization
Character Animation
Animated Commercial
Product Modelling
Animated Presentation
Walkthrough Animation
Animated Movies
Looking forward to start cooperation with you soon.
Thanks,
Roy
Email: donghuacon(a)tom.com
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
openSUSE-13.1 KDE
Is there any way that I can retrieve the Konsole history log from the
backing files for crashed Konsole instances? If so, how may I do it?
I have Konsole set to have unlimited scrollback. I often like to save
the Konsole transcript (history, output, log, or whatever the nom du
jour is) before closing the konsole instance. However, rather
frequently, something else kills the konsoles before I can do that.
Since I have set the konsole to have unlimited scrollback, the log is
saved in a file which appears to persist if the konsole is killed
abnormally. The data in the history files appears to be encoded
somehow. How, may I retrieve the unencoded data (i.e., equiv to that if
I'd selected "File >> Save Output As..." menu item) from the history
files? (the history files are named like, e.g.,
"konsole-zc3534.history")
Thanks!
--Phil
--
Philip Amadeo Saeli
psaeli(a)zorodyne.com
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hi to all.
It seems that libqxt became dead around 2014-07-26:
http://dev.libqxt.org/libqxt/wiki/Home
%osc whatdependson openSUSE:Factory libqxt standard x86_64
libqxt :
clementine (maintained by KDE team)
leechcraft (maintained by me)
qutim (maintained by KDE team and me a bit)
So should I open a delete request and disable leechcraft&qutim related
stuff?
--
Best regards,
Dmitriy DA(P).DarkneSS Perlow @ Linux x64
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kde+owner(a)opensuse.org
Hi fellow packagers of KDE:Extra,
I'd like to propose building against 13.2:Update instead of the plain 13.2
repo for the following reasons:
I added the KDE:Extra repo to my setups for updated apps. With the updates
pushed into the 13.2:Update channel though, I get some problems due to the
fact that KDE:Extra is built against the (outdated) libs from 13.2:standard.
E.g. I encountered the following bug:
https://bugs.kde.org/show_bug.cgi?id=344096
Also, e.g. digikam now builds with the old libkface2 instead of the bundled
libkface3 or the one available through 13.2:Update thus missing several
improvements made here.
Building against 13.2:Update would require users to install the updates in
order to use this repo. However, I'd vote against keeping a plain 13.2 repo
because I guess whoever uses KDE:Extra to get updated apps also has the system
updates enabled ;)
Nico
Hi,
This message contains a password encrypted pdf file. The password for
the pdf can be retrieved by logging into the web portal.
The first time you login, you need to choose a new password.
You can read the message by following these steps:
1. click the link below.
2. If prompted with There is a problem with this website's security certificate. then choose Continue to this website (not recommended).
3. choose a password, and confirm it by typing it again.
4. log in to the site with the password you just chose.
5. press 'generate' to generate the password to the pdf file.
6. copy the generated password.
7. open the pdf file, attached to the email you received, and paste the
password in the password box.
Next time you receive an encrypted pdf file, the email will contain a
link, and you can login with your password
https://gateway.fortworthheart.com/web/portal/secure/otp?id=615756359&pwl=1…
The password ID of this email is: 615756359
Best regards,
Алимпий
---
Sent with DJIGZO
I have 13.2 and TW installations using Classic Menu Style showing both
Configure Desktop in main menu level, plus as Applications -> System
Settings. Anyone else? Everyone else not using Application Launcher style?
Selected packages on one TW installation:
PackageKit-branding-openSUSE-13.2-5.3.noarch
branding-openSUSE-13.2-10.40.noarch
gio-branding-openSUSE-13.2-3.2.noarch
kdebase4-runtime-branding-upstream-14.12.1-1.2.x86_64
kdebase4-workspace-branding-upstream-4.11.15-1.2.x86_64
kdelibs4-branding-upstream-4.14.4-1.3.x86_64
kdm-branding-upstream-4.11.15-1.2.x86_64
plasma-addons-4.14.3-3.2.x86_64
systemd-presets-branding-openSUSE-0.3.0-16.1.noarch
wallpaper-branding-openSUSE-13.2-10.40.noarch
xdg-menu-0.2-217.1.noarch
xdg-utils-20150119-1.1.noarch
--
"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