from:"Erich"

https://bugs.kde.org/show_bug.cgi?id=456958

--- Comment #4 from Erich Eickmeyer  ---
(In reply to Nate Graham from comment #3)
> There may be a second issue here; my ~/.config/kglobalaccelrc file has
> entries for all shortcuts written to it, even those with empty shortcuts. So
> for example my file has:
> 
> Decrease Opacity=none,,Decrease Opacity of Active Window by 5 %
> Increase Opacity=none,,Increase Opacity of Active Window by 5 %
> 
> This will override any default settings at a lower level because user
> settings take precedence over systemwide settings.

If ${setting}=none, shouldn't it look for a setting up the path until it finds
one to fill the gap? Seems like if it's writing that, it would prevent any
default from being configured ever.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

https://bugs.kde.org/show_bug.cgi?id=453752

--- Comment #7 from Erich Eickmeyer  ---
(In reply to Erich Eickmeyer from comment #6)
> No, my testing involved using /etc/xdg directly. It's simply not inheriting
> $XDG_CONFIG_DIRS paths.

Rather, my testing involved both directories.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

https://bugs.kde.org/show_bug.cgi?id=453752

--- Comment #6 from Erich Eickmeyer  ---
No, my testing involved using /etc/xdg directly. It's simply not inheriting
$XDG_CONFIG_DIRS paths.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

https://bugs.kde.org/show_bug.cgi?id=453752

Erich Eickmeyer  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 Ever confirmed|1   |0

--- Comment #4 from Erich Eickmeyer  ---
That's exactly what Michael was referring to is that even when a file named
"kwinrc" is in that path with those contents, it has no effect when "Defaults"
is selected. The initial configuration is honored, but when "Defaults" is
selected, it no longer gathers the defaults from the $XDG_CONFIG_DIRS path.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kglobalaccel] [Bug 456958] New: kglobalshortcutsrc does not propagate via $XDG_CONFIG_DIRS

https://bugs.kde.org/show_bug.cgi?id=456958

Bug ID: 456958
Summary: kglobalshortcutsrc does not propagate via
$XDG_CONFIG_DIRS
Product: frameworks-kglobalaccel
Version: 5.95.0
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: kdelibs-b...@kde.org
Reporter: eeickme...@ubuntu.com
Target Milestone: ---

SUMMARY

If a distribution or OEM places a kglobalshortcuts file in the path defined in
$XDG_CONFIG_DIRS, whether that's in /etc/xdg or otherwise, the settings fail to
propogate but get superseded by some kind of built-in hardcoded mechanism as
opposed to those that were defined by the distribution or OEM. These settings
should simply get written based on whatever the hardcoded defaults are *unless*
a default has been defined somewhere in the $XDG_CONFIG_DIRS path (in this
case,
~/.config/kdedefaults:/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings).

STEPS TO REPRODUCE
1. Create a /etc/xdg/kglobalshortcutsrc file containing the following:

[kwin]
Decrease Opacity=Meta+_,,Decrease Opacity of Active Window by 5 %
Increase Opacity=Meta++,,Increase Opacity of Active Window by 5 %

2. Create a new user.
3. Login as new user.
4. Open Dolphin.
5. Attempt to decrease and increase opacity with Meta-Shift-+ or Meta-Shift-=.

OBSERVED RESULT
Shortcut keys have no effect. Corresponding setting in System Settings >
Shortcuts > Shortcuts > KWin shows "No active shortcuts.

EXPECTED RESULT
Shortcut keys should change opacity of the active window and be set to do so by
default. This should be able to be verified via System Settings > Shortcuts >
Shortcuts > KWin.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.95
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Without a way for distributions and OEMs to set hardware or distribution-unique
shortcuts, this limits the customization capabilities of KDE Plasma to be
custom pre-configured.

--
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

https://bugs.kde.org/show_bug.cgi?id=456956

--- Comment #4 from Erich Eickmeyer  ---
Issue is also present in Plasma 5.25.3

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

https://bugs.kde.org/show_bug.cgi?id=456956

--- Comment #3 from Erich Eickmeyer  ---
(In reply to Erich Eickmeyer from comment #0)
> SUMMARY
> 
> If a distribution or OEM places a powermanaagementprofilesrc file in the
> path defined in $XDG_CONFIG_DIRS, whether that's in /etc/xdg or otherwise,
> the settings fail to propogate but get superseded by some kind of built-in
> hardcoded mechanism as opposed to those that were defined by the
> distribution or OEM. These settings should simply get written based on
> whatever the hardcoded defaults are *unless* a default has been defined
> somewhere in the $XDG_CONFIG_DIRS path (in this case,
> ~/.config/kdedefaults:/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-
> default-settings/kf5-settings).
> 

This isn't entirely accurate. As in Step 3 of the Steps to Reproduce, the
initial propagation is there, it's just not there after the steps are taken in
the Steps to Reproduce.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

https://bugs.kde.org/show_bug.cgi?id=456956

--- Comment #2 from Erich Eickmeyer  ---
(In reply to Erich Eickmeyer from comment #1)
> In the steps to reproduce, step #2:
> 
> s/powermanagement/powermanagementrc

By that I meant powermanagementprofilesrc

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 456956] Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

https://bugs.kde.org/show_bug.cgi?id=456956

--- Comment #1 from Erich Eickmeyer  ---
In the steps to reproduce, step #2:

s/powermanagement/powermanagementrc

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 456956] New: Power script settings, perhaps other settings, from $XDG_CONFIG_DIRS are discarded when user clicks on Defaults

https://bugs.kde.org/show_bug.cgi?id=456956

Bug ID: 456956
Summary: Power script settings, perhaps other settings, from
$XDG_CONFIG_DIRS are discarded when user clicks on
Defaults
Product: systemsettings
Version: 5.24.6
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_powerdevil
Assignee: plasma-b...@kde.org
Reporter: eeickme...@ubuntu.com
CC: k...@privat.broulik.de
Target Milestone: ---

SUMMARY

If a distribution or OEM places a powermanaagementprofilesrc file in the path
defined in $XDG_CONFIG_DIRS, whether that's in /etc/xdg or otherwise, the
settings fail to propogate but get superseded by some kind of built-in
hardcoded mechanism as opposed to those that were defined by the distribution
or OEM. These settings should simply get written based on whatever the
hardcoded defaults are *unless* a default has been defined somewhere in the
$XDG_CONFIG_DIRS path (in this case,
~/.config/kdedefaults:/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings).

Additionally, a few GUI glitches occur, such as the checkbox getting rechecked
without anything in the script box, as well as a few other items that don't
make logical sense. You'll probably have to see for yourself as you work in the
steps to reproduce below.

STEPS TO REPRODUCE
1. Create a script in /usr/local/bin. I made one called
/usr/local/bin/HelloPopup with the following contents:

#! /bin/bash

kdialog --msgbox 'Hello World'

2. Add the following to /etc/xdg/powermanagement

[AC][RunScript]
idleTime=60
scriptCommand=/usr/local/bin/HelloPopup
scriptPhase=0

[Battery][RunScript]
idleTime=60
scriptCommand=/usr/local/bin/HelloPopup
scriptPhase=0

[LowBattery][RunScript]
idleTime=60
scriptCommand=/usr/local/bin/HelloPopup
scriptPhase=0

3. Create a new user.

4. Open System Settings > Power Management > Energy Saving

Notice all fields are correct, including script field.

5. Uncheck script field, click apply.

6. Switch to a different System Settings module and come back to Energy Saving.

7. Click "Defaults", click "Yes".

OBSERVED RESULT

Script field does not result in original default being applied.

EXPECTED RESULT

Script field goes back to original default.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04
(available in About System)
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.95.0
Qt Version: 5.13.3

--
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

2022-07-19 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=453752

Erich Eickmeyer  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|DOWNSTREAM  |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 453752] Effects Settings from XDG_CONFIG_DIRS are discarded when user clicks on [Defaults]

2022-07-19 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=453752

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #2 from Erich Eickmeyer  ---
On the contrary, Nate, this is something that should be inherited by
$XDG_CONFIG_DIRS in which case /usr/share/kubuntu-default-settings/kf5-settings
is added to the path by the distribution. Therefore, by adding a file with a
config to the aforementioned directory is inherently doing the same as adding
it to /etc/xdg since it is in the same $XDG_CONFIG_DIRS path, at least
according to the XDG spec.

This is, of course, unless KDE is deviating from the Open Desktop Guidelines
and not using the $XDG_CONFIG_DIRS system variable when searching for config
files.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

https://bugs.kde.org/show_bug.cgi?id=456049

--- Comment #4 from Erich Eickmeyer  ---
Created attachment 150205
  --> https://bugs.kde.org/attachment.cgi?id=150205=edit
After relog or reboot 4 monitors

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

https://bugs.kde.org/show_bug.cgi?id=456049

--- Comment #3 from Erich Eickmeyer  ---
Created attachment 150204
  --> https://bugs.kde.org/attachment.cgi?id=150204=edit
Before relog or reboot 4 monitors

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

https://bugs.kde.org/show_bug.cgi?id=456049

--- Comment #2 from Erich Eickmeyer  ---
Created attachment 150203
  --> https://bugs.kde.org/attachment.cgi?id=150203=edit
After relog or reboot 2 monitors

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 456049] On multiple displays, when relogging or rebooting, widgets will move or resize

https://bugs.kde.org/show_bug.cgi?id=456049

--- Comment #1 from Erich Eickmeyer  ---
Created attachment 150202
  --> https://bugs.kde.org/attachment.cgi?id=150202=edit
Before relog or reboot 2 monitors

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 456049] New: On multiple displays, when relogging or rebooting, widgets will move or resize

https://bugs.kde.org/show_bug.cgi?id=456049

Bug ID: 456049
   Summary: On multiple displays, when relogging or rebooting,
widgets will move or resize
   Product: plasmashell
   Version: 5.25.1
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Desktop Containment
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: notm...@gmail.com
  Target Milestone: 1.0

SUMMARY

Signing out and back in with multiple monitors connected and/or setting a
different monitor to primary screen will move  widgets seemingly randomly based
on the system.

STEPS TO REPRODUCE
1. Connect to external monitor
2. Add widgets to desktop
3. Relog or reboot

OBSERVED RESULT

Widgets move to different location than originally placed

EXPECTED RESULT

Widgets remain in same place after relog or reboot

SOFTWARE/OS VERSIONS
Linux: Kubuntu 22.04
KDE Plasma Version: Plasma 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION

Reported by Kubuntu Focus testers

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-plasma] [Bug 454946] plasmashell crashes in Plasma::Applet::destroyedChanged() when switching between Global Theme desktop layouts

2022-06-24 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=454946

--- Comment #8 from Erich Eickmeyer  ---
Still having this issue with 5.25.1, but I'm unable to provide a further
backtrace as drkonqi is also malfunctioning. However, the symptoms are exactly
the same.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 454946] plasmashell crashes when switching between Global Theme desktop layouts

2022-06-07 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=454946

Erich Eickmeyer  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |---
 Status|NEEDSINFO   |REPORTED

--- Comment #6 from Erich Eickmeyer  ---
Thanks for the hint, Rik!

Here's the full backtrace:

Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x7f2c8df6b4c4 in QQuickWindow::maybeUpdate() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f2c8df53e1a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f2c8df53e8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f2c8df53fb7 in QQuickItemPrivate::setVisible(bool) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f2c8c539783 in QtPrivate::QSlotObjectBase::call (a=0x7ffdf1acad50,
r=0x556422a0cf20, this=0x556422b61840) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#9  doActivate (sender=0x556422a17b90, signal_index=5,
argv=0x7ffdf1acad50) at kernel/qobject.cpp:3886
#10 0x7f2c8c532a97 in QMetaObject::activate (sender=,
m=m@entry=0x7f2c8e570980 ,
local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffdf1acad50)
at kernel/qobject.cpp:3946
#11 0x7f2c8e4e6de6 in Plasma::Applet::destroyedChanged (this=, _t1=, _t1@entry=true) at
./obj-x86_64-linux-gnu/src/plasma/KF5Plasma_autogen/include/moc_applet.cpp:546
#12 0x7f2c8e4faaf8 in Plasma::AppletPrivate::setDestroyed
(this=0x556422896c40, destroyed=destroyed@entry=true) at
./src/plasma/private/applet_p.cpp:232
#13 0x7f2c8e4e808a in Plasma::Applet::destroy (this=0x556422a17b90) at
./src/plasma/applet.cpp:309
#14 0x556420a68254 in ShellCorona::unload (this=this@entry=0x5564227b7b20)
at ./shell/shellcorona.cpp:834
#15 0x556420a6bdd8 in ShellCorona::unload (this=0x5564227b7b20) at
./shell/shellcorona.cpp:606
#16 ShellCorona::loadLookAndFeelDefaultLayout (this=0x5564227b7b20,
packageName=...) at ./shell/shellcorona.cpp:602
#17 0x556420a9cd83 in PlasmaShellAdaptor::qt_metacall (this=0x556422948ad0,
_c=QMetaObject::InvokeMetaMethod, _id=3, _a=0x7ffdf1acafa0) at
./obj-x86_64-linux-gnu/shell/plasmashelladaptor.moc:197
#18 0x7f2c8ceb359b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., slotIdx=)
at ../../include/QtCore/../../src/corelib/tools/qvarlengtharray.h:190
#19 0x7f2c8ceb6fec in QDBusConnectionPrivate::activateCall
(this=this@entry=0x7f2c78008a00, object=0x556422948ad0, flags=flags@entry=273,
msg=...) at ./src/dbus/qdbusintegrator.cpp:904
#20 0x7f2c8ceb79f9 in QDBusConnectionPrivate::activateCall (msg=...,
flags=273, object=, this=0x7f2c78008a00) at
./src/dbus/qdbusintegrator.cpp:853
#21 QDBusConnectionPrivate::activateObject (this=0x7f2c78008a00, node=...,
msg=..., pathStartPos=) at ./src/dbus/qdbusintegrator.cpp:1497
#22 0x7f2c8ceb9dac in QDBusActivateObjectEvent::placeMetaCall
(this=0x7f2c7804acf0) at ./src/dbus/qdbusintegrator.cpp:1617
#23 0x7f2c8c52f40e in QObject::event (this=0x5564227b7b20,
e=0x7f2c7804acf0) at kernel/qobject.cpp:1314
#24 0x7f2c8d1f8713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#25 0x7f2c8c501e2a in QCoreApplication::notifyInternal2
(receiver=0x5564227b7b20, event=0x7f2c7804acf0) at
kernel/qcoreapplication.cpp:1064
#26 0x7f2c8c504f17 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x556422697ec0) at
kernel/qcoreapplication.cpp:1821
#27 0x7f2c8c55ba57 in postEventSourceDispatch (s=0x556422787ec0) at
kernel/qeventdispatcher_glib.cpp:277
#28 0x7f2c8a8d1d1b in g_main_dispatch (context=0x7f2c80005010) at
../../../glib/gmain.c:3417
#29 g_main_context_dispatch (context=0x7f2c80005010) at
../../../glib/gmain.c:4135
#30 0x7f2c8a9266f8 in g_main_context_iterate.constprop.0
(context=context@entry=0x7f2c80005010, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4211
#31 0x7f2c8a8cf3c3 in g_main_context_iteration (context=0x7f2c80005010,
may_block=1) at ../../../glib/gmain.c:4276
#32 0x7f2c8c55b0a8 in QEventDispatcherGlib::processEvents
(this=0x5564227884e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#33 0x7f2c8c50074b in QEventLoop::exec (this=this@entry=0x7ffdf1acb580,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x7f2c8c508ce4 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x556420a43dce in main (argc=, argv=) at
./shell/main.cpp:238
[Inferior 1 (process 1472) detached]

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 454946] plasmashell crashes when switching between Global Theme desktop layouts

2022-06-07 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=454946

--- Comment #4 from Erich Eickmeyer  ---
Right, that's why I added Rik Mills on the CC here, maybe he can chime-in to
help.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 454946] plasmashell crashes when switching between layouts

2022-06-07 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=454946

Erich Eickmeyer  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---
 CC||rikmi...@kde.org

--- Comment #2 from Erich Eickmeyer  ---
Hi Nate,

I'm afraid the debug symbols were unavailable even though the correct packages
were installed. And sorry, I should've clarified: this crash happens when
switching between look & feel t (global) themes when "Use desktop layout from
theme" is checked.

Thanks!

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 454946] New: plasmashell crashes when switching between layouts

2022-06-06 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=454946

Bug ID: 454946
   Summary: plasmashell crashes when switching between layouts
   Product: plasmashell
   Version: 5.24.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: eeickme...@ubuntu.com
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Application: plasmashell (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.94.0
Operating System: Linux 5.17.0-1004-oem x86_64
Windowing System: X11
Distribution: Ubuntu 22.04 LTS
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
When switching between layouts, plasmashell inevitably crashes, and sometimes
fails to recover. This can be reproduced in both virtual machines and on actual
hardware.

- Unusual behavior I noticed:
Black screen, sometimes full kwin crash as well would happen.

- Custom settings of the application:
Stock Kubuntu installation, Kubuntu Focus hardware

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault

[KCrash Handler]
#4  0x7f4c702014c4 in QQuickWindow::maybeUpdate() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#5  0x7f4c701e9e1a in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7f4c701e9e8b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7f4c701e9fb7 in QQuickItemPrivate::setVisible(bool) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7f4c6e7cf783 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f4c7077cde6 in Plasma::Applet::destroyedChanged(bool) () from
/lib/x86_64-linux-gnu/libKF5Plasma.so.5
#10 0x7f4c70790af8 in ?? () from /lib/x86_64-linux-gnu/libKF5Plasma.so.5
#11 0x7f4c7077e08a in Plasma::Applet::destroy() () from
/lib/x86_64-linux-gnu/libKF5Plasma.so.5
#12 0x55f492d75254 in ?? ()
#13 0x55f492d78dd8 in ?? ()
#14 0x55f492da9d83 in ?? ()
#15 0x7f4c6f14959b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#16 0x7f4c6f14cfec in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#17 0x7f4c6f14d9f9 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#18 0x7f4c6f14fdac in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5
#19 0x7f4c6e7c540e in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7f4c6f48e713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#21 0x7f4c6e797e2a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f4c6e79af17 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7f4c6e7f1a57 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7f4c6cb67d1b in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#25 0x7f4c6cbbc6f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f4c6cb653c3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f4c6e7f10a8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f4c6e79674b in
QEventLoop::exec(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#29 0x7f4c6e79ece4 in QCoreApplication::exec() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#30 0x55f492d50dce in ?? ()
#31 0x7f4c6e0b3d90 in __libc_start_call_main
(main=main@entry=0x55f492d4ff70, argc=argc@entry=2,
argv=argv@entry=0x7ffd15d4a068) at ../sysdeps/nptl/libc_start_call_main.h:58
#32 0x7f4c6e0b3e40 in __libc_start_main_impl (main=0x55f492d4ff70, argc=2,
argv=0x7ffd15d4a068, init=, fini=,
rtld_fini=, stack_end=0x7ffd15d4a058) at ../csu/libc-start.c:392
#33 0x55f492d50ef5 in ?? ()
[Inferior 1 (process 2036) detached]

Possible duplicates by query: bug 453681, bug 450723, bug 450594, bug 450163,
bug 450124.

Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04

2022-05-15 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=452532

--- Comment #13 from Erich Eickmeyer  ---
My 2c is this is something that KDE *should* fix in kdesu because it means that
kdesu has been taking advantage of an exploit in sudo for years, perhaps
decades. Basically, it's the same mechanism that the CVE exploits, and that's
not a good thing. To use a security hole for functionality sake, even if
unknown at the time, is generally bad practice.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04

2022-05-04 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=452532

--- Comment #4 from Erich Eickmeyer  ---
(In reply to Ahmad Samir from comment #3)
> The daemon is kdesud, which is typically installed in /usr/libexec.

That's true on Arch systems, but not Debian/Ubuntu. It's just one way, not the
only way.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kdesu] [Bug 452532] kdesu not working after upgrade from Ubuntu 20.04 to 22.04

2022-04-25 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=452532

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #2 from Erich Eickmeyer  ---
We have been noticing this behavior on Ubuntu for a few months, but the blame
was being passed to pkexec, not realizing that when, for instance, discover
launches software-properties-qt that it uses kdesu to do so. 

We have an open downstream bug report at https://launchpad.net/bugs/1965439

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

2021-11-30 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=441121

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[gwenview] [Bug 441121] gwenview crashes when opening .jpg in X11 Session (wayland not possible on graphics card)

2021-11-30 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=441121

--- Comment #19 from Erich Eickmeyer  ---
Created attachment 144108
  --> https://bugs.kde.org/attachment.cgi?id=144108=edit
New crash information added by DrKonqi

gwenview (21.11.90) using Qt 5.15.2

- What I was doing when the application crashed:
Attempting to open a family photo I had just exported from Darktable

-- Backtrace (Reduced):
#4  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139723732405312)
at pthread_kill.c:44
#5  __pthread_kill_internal (signo=6, threadid=139723732405312) at
pthread_kill.c:80
#6  __GI___pthread_kill (threadid=139723732405312, signo=signo@entry=6) at
pthread_kill.c:91
#7  0x7f13fcc35476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#8  0x7f13fcc1b7b7 in __GI_abort () at abort.c:79

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 432513] Discover/Packagekit appears to be marking packages as manually installed

2021-08-26 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=432513

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

--- Comment #2 from Erich Eickmeyer  ---
Apparently this is an upstream bug in Packagekit:
https://github.com/PackageKit/PackageKit/issues/450

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 432513] Discover/Packagekit appears to be marking packages as manually installed

2021-02-04 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=432513

--- Comment #1 from Erich Eickmeyer  ---
Downstream bug: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 432513] New: Discover/Packagekit appears to be marking packages as manually installed

2021-02-04 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=432513

Bug ID: 432513
   Summary: Discover/Packagekit appears to be marking packages as
manually installed
   Product: Discover
   Version: 5.18.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PackageKit
  Assignee: lei...@leinir.dk
  Reporter: er...@ericheickmeyer.com
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
With the machines I help administer, we have been finding situations where the
/boot directory is filling-up beyond 3 kernels on LUKS encrypted systems. apt
autoremove is not removing old kernels as expected, nor is unattended-upgrades
on the Ubuntu machines picking-up on the removable kernels.

We have had a system with as many as 15 kernel packages installed as a result
of this not working as expected.

The majority of these machines are using Discover to do their package
upgrading, which uses PackageKit as its backend.

This has led us to believe that Discover and Packagekit are possibly marking
apt packages that should be marked as "auto" as "manual". We were able to get
unattended-upgrades to to the trick and "apt autoremove" to do its job by using
"apt-mark auto linux-image-${version}-generic). However, this manual
intervention should not be required.

Per this downstream bug, we have confirmed that the problem does not lie in apt
nor unattended-upgrades.

STEPS TO REPRODUCE
1. Run Kubuntu normally on a LUKS encrypted system
2. Wait a few upgrades on the kernels over time
3. Kernels do not get automatically removed and /boot partition fills-up.

OBSERVED RESULT
Boot partition gets full blocking further upgrades of any packages. Unused/old
kernel images do not get automatically removed. Investigation shows new kernel
versions are marked as manually installed.

EXPECTED RESULT
Unused kernel images should be automatically removed upon reboot and/or using
"apt autoremove". Applications installed from a metapackage (case in point,
linux-image-generic) should be marked as auto-installed, allowing the
autoremove process to work as expected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

2021-01-18 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=431712

Erich Eickmeyer  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Ever confirmed|0   |1
 Status|NEEDSINFO   |ASSIGNED

--- Comment #5 from Erich Eickmeyer  ---
(In reply to Jan Blackquill (Carson Black) from comment #2)
> Doesn't seem to be reproducible on latest Breeze GTK for me. Can you try
> using the latest release version and see if this is still reproducible on it
> for you?

The latest version of the Breeze GTK theme requires a newer version of GTK than
is available in the Ubuntu 20.04 LTS repos. Since Plasma 5.18 is an LTS,
whatever fix was done to the Breeze GTK theme in the latest version needs to be
cherry-picked back to the LTS version. As you can see per the attachments, this
isn't a bug in GTK since using Adwaita-Dark makes things show-up as expected.
Additionally, I have tried with the Materia theme and this issue is also not
present, which means the issue is in the Breeze theme.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

2021-01-17 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=431712

--- Comment #4 from Erich Eickmeyer  ---
Created attachment 134969
  --> https://bugs.kde.org/attachment.cgi?id=134969=edit
Breeze GTK on Evolution

Also discovered it's occurring on the standard (light) version of the theme,
just inverted.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

2021-01-16 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=431712

--- Comment #3 from Erich Eickmeyer  ---
That cannot be done. The newest version of the theme simply won't install. And
since this is on the LTS version of Plasma (5.18), it really needs to be fixed
in that branch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 431712] Breeze-Dark GTK: Incorrect colors in Evolution

2021-01-16 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=431712

--- Comment #1 from Erich Eickmeyer  ---
Created attachment 134948
  --> https://bugs.kde.org/attachment.cgi?id=134948=edit
Adwaita-Dark on Evolution

-- 
You are receiving this mail because:
You are watching all bug changes.

[Breeze] [Bug 431712] New: Breeze-Dark GTK: Incorrect colors in Evolution

2021-01-16 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=431712

Bug ID: 431712
   Summary: Breeze-Dark GTK: Incorrect colors in Evolution
   Product: Breeze
   Version: 5.18.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: gtk theme
  Assignee: uhh...@gmail.com
  Reporter: er...@ericheickmeyer.com
CC: plasma-b...@kde.org
  Target Milestone: ---

Created attachment 134947
  --> https://bugs.kde.org/attachment.cgi?id=134947=edit
Breeze-Dark GTK on Evolution

SUMMARY

The Breeze-Dark GTK theme is rendering incorrectly in the Account Setup Wizard
of Evolution. Attached are two examples: one using Breeze-Dark, the other using
Adwaita-Dark.

STEPS TO REPRODUCE
1. Set GTK 3 theme to Breeze Dark, make sure Breeze Dark colors are selected.
2. Run evoluton. Observe account setup window.
3. If Evolution has been run before, Go to File > New > Mail Account

OBSERVED RESULT

White text on white background can be observed in the left pane of the wizard.
EXPECTED RESULT

White text on a dark background should be observed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68
Qt Version: 5.12.8

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 421240] New: Create a way to set a variable for downstreams to customize default GTK theme

2020-05-09 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=421240

Bug ID: 421240
   Summary: Create a way to set a variable for downstreams to
customize default GTK theme
   Product: systemsettings
   Version: 5.18.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: kcm_style
  Assignee: plasma-b...@kde.org
  Reporter: er...@ericheickmeyer.com
CC: zom...@protonmail.com
  Target Milestone: ---

SUMMARY
Currently, barring using /etc/skel, there is no way to set the default GTK
theme for downstream Linux distributions. In my case, Ubuntu Studio, we use the
Materia theme by default. We wish to make it the default for GTK and Qt
applications, which I can do for Qt, but not for GTK.

STEPS TO REPRODUCE
Attempt to set default GTK theme via $XDG_CONFIG_DIRS/gtk-3.0/settings.ini
and/or $XDG_CONFIG_DIR/.gtkrc-2.0


OBSERVED RESULT
Settings are completely ignored, defaults to Breeze theme.

EXPECTED RESULT
Settings default to theme set in $XDG_CONFIG_DIRS/gtk-3.0/settings.ini and/or
$XDG_CONFIG_DIRS/.gtkrc-2.0

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04 LTS
(available in About System)
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
I'm the Ubuntu Studio lead, and, while not completely barring our transition to
KDE Plasma, this does create an issue for users that hit the "default" button
and it defaults to Breeze. Currently, I'm having to use /etc/skel to set the
default for new user accounts, which is far from ideal.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4

2019-10-01 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=412366

--- Comment #12 from Erich  ---
(In reply to Ralf Habacker from comment #10)
> 
> Is there any chance that someone can apply and check attachment 122967
> [details] if it works with unpatched kdelibs ? This patch provides print
> preview support and I would  add it to the next release.

I tested attachment 122967 on top of branch 4.8 (195f84d09 Avoid showing the
print dialog twice with an unpatched kdelibs).

kdelibs is version 4.14.38.

Print preview works correctly for report charts.  Printing from the print
preview dialog works correctly.

However, print preview for anything else (report tables and home screen tested)
brings up the print dialog and KMyMoney goes through the print process instead.
 If printing to a file, the PDF is created as if "Print" were chosen instead. 
THEN, the print preview windows shows up, showing the last "successful" print
preview.  This is either blank, or if a print preview was previously generated
for a report chart, that report chart is shown in the print preview dialog.

My opinion as a user:  Print preview is new functionality, so previously it
wasn't even an option.  KDE4 is extremely old at this point.  If most of your
users of KMyMoney 4.8 are on kdelibs >= 4.14.65 and print preview works
correctly there, you should just keep your patch as is.  When I asked about my
original bug report on the slackbuilds mailing list, only 1 person responded,
and he doesn't even use the Print to File feature.  Eventually Slackware 15
will be released (nobody knows when...) and I can only assume it will have
Qt5/KDE5, at which point I would move to KMyMoney 5.  So I don't care if print
preview is broken for everything except report charts.  I wouldn't want you to
waste time trying to make it work correctly just for me if it already works for
all other users.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4

2019-10-01 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=412366

--- Comment #11 from Erich  ---
(In reply to Ralf Habacker from comment #10)
> Is there any chance that someone can apply and check attachment 122967
> [details] if it works with unpatched kdelibs ? This patch provides print
> preview support and I would  add it to the next release.

Yes I will test it later today.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4

2019-09-29 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=412366

--- Comment #7 from Erich  ---
I can confirm that the following all work:

Attachment 122884 (https://bugs.kde.org/attachment.cgi?id=122884) to kdelibs
adds the required functionality to kdelibs so that KMyMoney 4.8.4 print works
correctly.  (Of course KMyMoney must be recompiled after upgrading kdelibs so
that the new behavior to print() is enabled.)

OR

Commit beca6d920
(https://cgit.kde.org/kmymoney.git/commit/?id=beca6d92002eabc52ebd1da52d6edf4c06c9c22c)
restores print functionality on stock Slackware64 14.2.  The print dialog
appears twice, but this is acceptable for me.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 412366] Print to File (PDF) broken on KDE4 in 4.8.4

2019-09-26 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=412366

--- Comment #2 from Erich  ---
Hi Ralf,

I will try your patch.

Are there any concerns with updating KDE_VERSION_RELEASE to 65?  The patch file
increases it from 60 to 65, whereas Slackware has it at 38.  I assume I'll be
missing additional functionality that was added along the way?

Where can I find these additional patches to kdelibs?  I was under the
impression that 4.14.38 was the last release of kdelibs.

Erich

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 412366] New: Print to File (PDF) broken on KDE4 in 4.8.4

2019-09-26 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=412366

Bug ID: 412366
   Summary: Print to File (PDF) broken on KDE4 in 4.8.4
   Product: kmymoney
   Version: 4.8.4
  Platform: Slackware Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: reports
  Assignee: kmymoney-de...@kde.org
  Reporter: erich.public+bugs.kde@protonmail.com
  Target Milestone: ---

Created attachment 122879
  --> https://bugs.kde.org/attachment.cgi?id=122879=edit
Restore "Print to File (PDF)" functionality for KDE4

SUMMARY
Commit 15ac7d472af41fc503dc5209643cfc8b392b0089, introduced in KMyMoney 4.8.4,
breaks Print to File (PDF) functionality on KDE4 in Slackware64 14.2. 
Reverting that commit on branch 4.8 HEAD restores Print to File (PDF)
functionality.

STEPS TO REPRODUCE
1. Choose Reports, 1. Income and Expenses -> Income and Expenses This Month
(Default Report)
2. Then choose Print, Print to File (PDF).

OBSERVED RESULT
KMyMoney goes through all the motions - including asking for confirmation to
overwrite an existing file - but the PDF does not get created.  Versions 4.8.3
and earlier create the PDF as expected.


EXPECTED RESULT
PDF file gets created by KMyMoney.

SOFTWARE/OS VERSIONS
Linux: Slackware64 14.2
KDE Platform Version: 4.14.38
Qt Version: 4.8.7

ADDITIONAL INFORMATION

I also developed a small patch which restores Print to File (PDF) functionality
for me, but the print dialog appears twice (I did expect that to happen when I
tried out the patch).  So it is not a proper patch.

What I believe is the cause of the problem:
The net result of patches:
5f4f90e83565647f3579660e4c5d9ac447547a02 Fix 'Printer settings are not saved'
15ac7d472af41fc503dc5209643cfc8b392b0089 Add print support for report charts
Changes the "print" command from
m_part->view()->print()
to
q->m_part->view()->print(true);
when KDE_IS_VERSION(4, 14, 65) is false (which is the case for me).

>From what I can tell from reading the docs (I am not a KDE developer), this
changes the "print" command from "print by asking the user how to print" to
"print using the default settings".  Unfortunately, those "default settings"
are not what KMyMoney asked about in the code immediately preceding the "print"
command, they must be the system-wide defaults.  My minimally-invasive patch
simply changes the print command back to what it used to be, with the net
effect that the print dialog appears twice when printing a report.

I did not test printing charts, which is what
15ac7d472af41fc503dc5209643cfc8b392b0089 addressed in the first place.

Another Slackware user was able to reproduce the issue.  See thread at:
https://lists.slackbuilds.org/pipermail/slackbuilds-users/2019-September/023367.html

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmymoney] [Bug 405061] No chart printing support

2019-09-23 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=405061

Erich  changed:

   What|Removed |Added

 CC||erich.public+bugs.kde.org@p
   ||rotonmail.com

--- Comment #5 from Erich  ---
Commit 15ac7d472af41fc503dc5209643cfc8b392b0089 breaks "Print to PDF" for me.

I noticed after upgrading to 4.8.4 that "Print to File (PDF)" no longer worked
for printing report tables.  Doing a git bisect, I learned that 15ac7d472 "Add
print support for report charts" is what broke "Print to File (PDF)". 
Reverting this commit on top of branch 4.8 (HEAD was at 0ae5377fd "Fix reverse
sort order handling in register" at time of testing) restored "Print to PDF"
functionality for me.

I am using Slackware64 14.2 (latest stable version of Slackware 64-bit, with
all patches installed).  KMyMoney was compiled using the build script from
https://slackbuilds.org/repository/14.2/office/kmymoney/

Steps to reproduce:
Choose Reports, 1. Income and Expenses -> Income and Expenses This Month
(Default Report)
Then choose Print, Print to File (PDF).

4.8.4 fails to create the PDF (but it does ask for confirmation when trying to
overwrite an existing PDF).

It gets weirder, though: on my home laptop, choosing the "Print to File (PDF)"
option actually sends the job to my physical printer.  This caused me to burn
through a lot of paper, because the printer is in a different room, and I
didn't realize it was printing...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 405695] Crash while opening Kontact Settings

https://bugs.kde.org/show_bug.cgi?id=405695

Erich Eickmeyer  changed:

   What|Removed |Added

Summary|Crash while opening Contact |Crash while opening Kontact
   |Settings|Settings

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 405695] Crash while opening Kontact Settings

https://bugs.kde.org/show_bug.cgi?id=405695

Erich Eickmeyer  changed:

   What|Removed |Added

 CC|eeickme...@ubuntu.com   |

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 405695] Crash while opening Kontact Settings

https://bugs.kde.org/show_bug.cgi?id=405695

Erich Eickmeyer  changed:

   What|Removed |Added

 CC||eeickme...@ubuntu.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[kontact] [Bug 405695] New: Crash while opening Contact Settings

https://bugs.kde.org/show_bug.cgi?id=405695

Bug ID: 405695
   Summary: Crash while opening Contact Settings
   Product: kontact
   Version: 5.10.3
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: eeickme...@ubuntu.com
  Target Milestone: ---

Application: kontact (5.10.3)

Qt Version: 5.11.3
Frameworks Version: 5.56.0
Operating System: Linux 5.0.0-7-generic x86_64
Distribution: Ubuntu Disco Dingo (development branch)

-- Information about the crash:
- What I was doing when the application crashed:

Attempting to open Kontact settings (Settings > Configure Kontact)

Reproducible every time.

Ubuntu 19.04 Disco Dingo (pre-release)

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbdf24f8f40 (LWP 8505))]

Thread 52 (Thread 0x7fbd8e7fc700 (LWP 23596)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbd8e7fb3c0, expected=0, futex_word=0x7fbd8e7fb5a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbd8e7fb460,
mutex=0x7fbd8e7fb558, cond=0x7fbd8e7fb580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916 in __pthread_cond_timedwait (cond=0x7fbd8e7fb580,
mutex=0x7fbd8e7fb558, abstime=0x7fbd8e7fb460) at pthread_cond_wait.c:667
#3  0x7fbdebf8fa47 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fbdebf9231a in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fbdebf92402 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fbdebf96991 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fbdebf97c8f in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fbdebfa0c91 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fbdf2294182 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fbdf34a8faf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 51 (Thread 0x7fbca7dd2700 (LWP 23595)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbca7dd13c0, expected=0, futex_word=0x7fbca7dd15a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbca7dd1460,
mutex=0x7fbca7dd1558, cond=0x7fbca7dd1580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916 in __pthread_cond_timedwait (cond=0x7fbca7dd1580,
mutex=0x7fbca7dd1558, abstime=0x7fbca7dd1460) at pthread_cond_wait.c:667
#3  0x7fbdebf8fa47 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fbdebf9231a in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fbdebf92402 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fbdebf96991 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fbdebf97e71 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fbdebfa0c91 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fbdf2294182 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fbdf34a8faf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 50 (Thread 0x7fbc9e10f700 (LWP 18686)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbc9e10e3c0, expected=0, futex_word=0x7fbc9e10e5a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbc9e10e460,
mutex=0x7fbc9e10e558, cond=0x7fbc9e10e580) at pthread_cond_wait.c:533
#2  0x7fbdf229a916 in __pthread_cond_timedwait (cond=0x7fbc9e10e580,
mutex=0x7fbc9e10e558, abstime=0x7fbc9e10e460) at pthread_cond_wait.c:667
#3  0x7fbdebf8fa47 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fbdebf9231a in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fbdebf92402 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fbdebf96991 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fbdebf97e71 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fbdebfa0c91 in  () at /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fbdf2294182 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fbdf34a8faf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 49 (Thread 0x7fbc9e910700 (LWP 9509)):
#0  0x7fbdf229a916 in futex_reltimed_wait_cancelable (private=, reltime=0x7fbc9e90f3c0, expected=0, futex_word=0x7fbc9e90f5a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fbdf229a916 in __pthread_cond_wait_common (abstime=0x7fbc9e90f460,
mutex=0x7fbc9e90f558, cond=0x7fbc9e90f580) at pthread_cond_wait.c:533
#2

[Heaptrack] [Bug 396240] New: fails to build from source on 32-bit linux

2018-07-06 Thread Erich Eckner

https://bugs.kde.org/show_bug.cgi?id=396240

Bug ID: 396240
   Summary: fails to build from source on 32-bit linux
   Product: Heaptrack
   Version: 1.1.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: k...@eckner.net
  Target Milestone: ---

Created attachment 113793
  --> https://bugs.kde.org/attachment.cgi?id=113793=edit
log of failing build

compilation on archlinux32 fails with:

/build/heaptrack/src/heaptrack-1.1.0/src/util/linewriter.h:170:46: error: call
of overloaded ‘clz(long long unsigned int&)’ is ambiguous
 const unsigned zeroBits = value ? clz(value) : numBits;
   ~~~^~~
/build/heaptrack/src/heaptrack-1.1.0/src/util/linewriter.h:151:28: note:
candidate: ‘static unsigned int LineWriter::clz(unsigned int)’
 inline static unsigned clz(unsigned V)
^~~
/build/heaptrack/src/heaptrack-1.1.0/src/util/linewriter.h:156:28: note:
candidate: ‘static unsigned int LineWriter::clz(long unsigned int)’
 inline static unsigned clz(long unsigned V)
^~~

version 1.0.0 was built successfully, though

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 389991] Sleep key no longer initiates sleep

2018-02-08 Thread Erich Eickmeyer

https://bugs.kde.org/show_bug.cgi?id=389991

Erich Eickmeyer <er...@ericheickmeyer.com> changed:

   What|Removed |Added

 CC||er...@ericheickmeyer.com

--- Comment #7 from Erich Eickmeyer <er...@ericheickmeyer.com> ---
Upgraded Kubuntu to Plasma 5.12, had the same problem with the brightness keys
(both screen and keyboard) on my 2011 MacBook Pro. Workaround fix was to fix
the global keyboard shortcuts in power management by custom-assigning the
respective functions to the correct keys. It pops up dialogs saying there's a
conflict. Do it twice and it will realize that the button you're using is the
default and assign it accordingly.

Seems as though the global shortcut mapping is getting confused between
releases specifically as it comes to power management control.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 377188] New: Cannot get smooth brush with OpenGL enabled

2017-03-03 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=377188

Bug ID: 377188
   Summary: Cannot get smooth brush with OpenGL enabled
   Product: krita
   Version: 3.1.2
  Platform: unspecified
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: OpenGL Canvas
  Assignee: krita-bugs-n...@kde.org
  Reporter: erich...@gmail.com
  Target Milestone: ---

Created attachment 104358
  --> https://bugs.kde.org/attachment.cgi?id=104358=edit
sample

On macOS Sierra I can´t get smooth lines when OpenGL is enabled. The attached
file shows a sample.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kde] [Bug 374308] New: crash on shutdown

2016-12-29 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=374308

Bug ID: 374308
   Summary: crash on shutdown
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: er...@irq.at
  Target Milestone: ---

Application: kdeinit5 ()

Qt Version: 5.5.1
Operating System: Linux 4.1.36-41-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was shutting down the OS (Suse Leap 41.1) before the crash happened, no other
activities or clicks etc...

-- Backtrace:
Application: kdeinit5 (kdeinit5), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9c9213d780 (LWP 1944))]

Thread 6 (Thread 0x7f9c637fe700 (LWP 2583)):
#0  0x7f9c8d033cf9 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0
#1  0x7f9c8cff14b9 in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#2  0x7f9c8cff1d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f9c8cff1f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f9c9083dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f9c907e4d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f9c9060661a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f9c9060b32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f9c8dcb60a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f9c9029d02d in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7f9c63fff700 (LWP 2010)):
#0  0x7f9c90603bfa in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#1  0x7f9c9083dcb5 in ?? () from /usr/lib64/libQt5Core.so.5
#2  0x7f9c8cff14ad in g_main_context_prepare () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9c8cff1d80 in ?? () from /usr/lib64/libglib-2.0.so.0
#4  0x7f9c8cff1f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#5  0x7f9c9083dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#6  0x7f9c907e4d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#7  0x7f9c9060661a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#8  0x7f9c9060b32f in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f9c8dcb60a4 in start_thread () from /lib64/libpthread.so.0
#10 0x7f9c9029d02d in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7f9c6ad5c700 (LWP 2009)):
#0  0x7f9c90294bfd in poll () from /lib64/libc.so.6
#1  0x7f9c8cff1e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9c8cff1f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f9c9083dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#4  0x7f9c907e4d53 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#5  0x7f9c9060661a in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#6  0x7f9c73796cf7 in KCupsConnection::run() () from
/usr/lib64/libkcupslib.so
#7  0x7f9c9060b32f in ?? () from /usr/lib64/libQt5Core.so.5
#8  0x7f9c8dcb60a4 in start_thread () from /lib64/libpthread.so.0
#9  0x7f9c9029d02d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7f9c70b14700 (LWP 1956)):
#0  0x7f9c90294bfd in poll () from /lib64/libc.so.6
#1  0x7f9c8cff1e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f9c8cff219a in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x7f9c7142b426 in ?? () from /usr/lib64/libgio-2.0.so.0
#4  0x7f9c8d016f65 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f9c8dcb60a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f9c9029d02d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f9c7cc63700 (LWP 1947)):
#0  0x7f9c90294bfd in poll () from /lib64/libc.so.6
#1  0x7f9c915b9422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f9c915bb00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f9c7efb83c9 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x7f9c9060b32f in ?? () from /usr/lib64/libQt5Core.so.5
#5  0x7f9c8dcb60a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f9c9029d02d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f9c9213d780 (LWP 1944)):
[KCrash Handler]
#6  0x7f9c901ed0c7 in raise () from /lib64/libc.so.6
#7  0x7f9c901ee478 in abort () from /lib64/libc.so.6
#8  0x7f9c9022a784 in __libc_message () from /lib64/libc.so.6
#9  0x7f9c90230026 in malloc_printerr () from /lib64/libc.so.6
#10 0x7f9c90230d53 in _int_free () from /lib64/libc.so.6
#11 0x7f9c7ed723f1 in XIQueryDevice () from /usr/lib64/libXi.so.6
#12 0x7f9c7efd90bf in
QXcbConnection::handleEnterEvent(xcb_enter_notify_event_t const*)

[plasmashell] [Bug 372405] New: Plasma crashes consistantly & immediately following startx since 1st reboot following last system auto-update

2016-11-12 Thread Erich

https://bugs.kde.org/show_bug.cgi?id=372405

Bug ID: 372405
   Summary: Plasma crashes consistantly & immediately following
startx since 1st reboot following last system
auto-update
   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: k...@stepfordrobotics.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.4.0-47-generic x86_64
Distribution: Ubuntu 16.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed: Either system restart or
startx from terminal

- Unusual behavior I noticed: On system restart, loads to non-responsive blank
black screen with only funtioning mouse pointer.  Ctrl-alt-F(1-6) starts
terminal, and startx results in three separate Plasma crash reports.  This is
the output of the first report.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa97c30c900 (LWP 1528))]

Thread 6 (Thread 0x7fa94d21c700 (LWP 1577)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa97bd4dbd4 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa97bd4dc19 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa972bff754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7fa9761f270a in start_thread (arg=0x7fa94d21c700) at
pthread_create.c:333
#5  0x7fa976a1b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7fa94eb91700 (LWP 1576)):
#0  0x7fa9737a48eb in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7fa9737a52cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fa9737a54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7fa97733c7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fa9772e3b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa977100834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa9799a83c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7fa9771057be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa972bff754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#9  0x7fa9761f270a in start_thread (arg=0x7fa94eb91700) at
pthread_create.c:333
#10 0x7fa976a1b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7fa954a80700 (LWP 1567)):
#0  __lll_unlock_wake () at
../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371
#1  0x7fa9761f654f in __pthread_mutex_unlock_usercnt (decr=1,
mutex=0x7fa972e5ca40) at pthread_mutex_unlock.c:55
#2  __GI___pthread_mutex_unlock (mutex=0x7fa972e5ca40) at
pthread_mutex_unlock.c:314
#3  0x7fa972bf974b in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4  0x7fa972bfe766 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#5  0x7fa96f5d9bf7 in ?? () from
/usr/lib/nvidia-304/tls/libnvidia-tls.so.304.132
#6  0x7fa9737e8740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7fa9737a4e84 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x7fa9737a5340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7fa9737a54ac in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x7fa97733c7eb in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7fa9772e3b4a in
QEventLoop::exec(QFlags) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7fa977100834 in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7fa9799a83c5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#14 0x7fa9771057be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x7fa972bff754 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#16 0x7fa9761f270a in start_thread (arg=0x7fa954a80700) at
pthread_create.c:333
#17 0x7fa976a1b82d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fa95f5ef700 (LWP 1543)):
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1  0x7fa9761f4e92 in __GI___pthread_mutex_lock (mutex=0x7fa972e5ca40) at
../nptl/pthread_mutex_lock.c:115
#2  0x7fa972bf99f2 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#3  0x7fa972bfe290 in ?? () from /usr/lib/nvidia-304/libGL.so.1
#4

[plasmashell] [Bug 362004] New: Plasma crashed due to switching the main screen off and on

2016-04-20 Thread Erich via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=362004

Bug ID: 362004
   Summary: Plasma crashed due to switching the main screen off
and on
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: e...@led-company.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.20-11-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

I've two screens and I accidentally switched the main screen off and back on
again.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f2b46f2a800 (LWP 25630))]

Thread 32 (Thread 0x7f2b2fcdd700 (LWP 25633)):
#0  0x7f2b403b2bbd in poll () from /lib64/libc.so.6
#1  0x7f2b45359422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x7f2b4535b00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x7f2b324963c9 in QXcbEventReader::run (this=0xffc160) at
qxcbconnection.cpp:1229
#4  0x7f2b40ab132f in QThreadPrivate::start (arg=0xffc160) at
thread/qthread_unix.cpp:331
#5  0x7f2b3fbae0a4 in start_thread () from /lib64/libpthread.so.0
#6  0x7f2b403bafed in clone () from /lib64/libc.so.6

Thread 31 (Thread 0x7f2b2d06d700 (LWP 25634)):
#0  0x7f2b403aec8d in read () from /lib64/libc.so.6
#1  0x7f2b384a0073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.361.42
#2  0x7f2b3ca6ab60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f2b3ca2 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f2b3ca29df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f2b3ca29f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f2b40ce3d8b in QEventDispatcherGlib::processEvents
(this=0x7f2b28c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f2b40c8ad53 in QEventLoop::exec (this=this@entry=0x7f2b2d06cdb0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f2b40aac61a in QThread::exec (this=this@entry=0x10d0df0) at
thread/qthread.cpp:503
#9  0x7f2b43df6e18 in QQmlThreadPrivate::run (this=0x10d0df0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#10 0x7f2b40ab132f in QThreadPrivate::start (arg=0x10d0df0) at
thread/qthread_unix.cpp:331
#11 0x7f2b3fbae0a4 in start_thread () from /lib64/libpthread.so.0
#12 0x7f2b403bafed in clone () from /lib64/libc.so.6

Thread 30 (Thread 0x7f2b1c4d5700 (LWP 25641)):
#0  0x7f2b403aec8d in read () from /lib64/libc.so.6
#1  0x7f2b384a0073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.361.42
#2  0x7f2b3ca6ab60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x7f2b3ca2 in g_main_context_check () from
/usr/lib64/libglib-2.0.so.0
#4  0x7f2b3ca29df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x7f2b3ca29f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#6  0x7f2b40ce3d8b in QEventDispatcherGlib::processEvents
(this=0x7f2b140008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#7  0x7f2b40c8ad53 in QEventLoop::exec (this=this@entry=0x7f2b1c4d4db0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x7f2b40aac61a in QThread::exec (this=this@entry=0x1276d00) at
thread/qthread.cpp:503
#9  0x7f2b43df6e18 in QQmlThreadPrivate::run (this=0x1276d00) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#10 0x7f2b40ab132f in QThreadPrivate::start (arg=0x1276d00) at
thread/qthread_unix.cpp:331
#11 0x7f2b3fbae0a4 in start_thread () from /lib64/libpthread.so.0
#12 0x7f2b403bafed in clone () from /lib64/libc.so.6

Thread 29 (Thread 0x7f2b1ac85700 (LWP 25642)):
#0  0x7f2b403b2bbd in poll () from /lib64/libc.so.6
#1  0x7f2b3ca29e64 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x7f2b3ca29f7c in g_main_context_iteration () from
/usr/lib64/libglib-2.0.so.0
#3  0x7f2b40ce3d8b in QEventDispatcherGlib::processEvents
(this=0x7f2b0c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#4  0x7f2b40c8ad53 in QEventLoop::exec (this=this@entry=0x7f2b1ac84db0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#5  0x7f2b40aac61a in QThread::exec (this=this@entry=0x14255a0) at
thread/qthread.cpp:503
#6  0x7f2b43df6e18 in QQmlThreadPrivate::run (this=0x14255a0) at
/usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/qml/ftw/qqmlthread.cpp:141
#7  0x7f2b40ab132f in QThreadPrivate::start (arg=0x14255a0) at
thread/qthread_unix.cpp:331
#8  0x7f2b3fbae0a4 in start_thread () from

[amarok] [Bug 360921] Amarok doesn't play music when i click on play or space bar

2016-03-24 Thread EricH via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=360921

--- Comment #7 from EricH <zen...@free.fr> ---
Ok, thank you

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 360921] Amarok doesn't play music when i click on play or space bar

https://bugs.kde.org/show_bug.cgi?id=360921

--- Comment #5 from EricH <zen...@free.fr> ---
Created attachment 98056
  --> https://bugs.kde.org/attachment.cgi?id=98056=edit
Phonon

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 360921] Amarok doesn't play music when i click on play or space bar

https://bugs.kde.org/show_bug.cgi?id=360921

--- Comment #4 from EricH <zen...@free.fr> ---
Amarok worked very well and for some time, I can not read my ogg

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 360921] Amarok doesn't play music when i click on play or space bar

https://bugs.kde.org/show_bug.cgi?id=360921

--- Comment #2 from EricH <zen...@free.fr> ---
Thank you for listening, but I read with my clementine mp3 and ogg files
without problem.

-- 
You are receiving this mail because:
You are watching all bug changes.

[amarok] [Bug 360921] New: Amarok doesn't play music when i click on play or space bar

https://bugs.kde.org/show_bug.cgi?id=360921

Bug ID: 360921
   Summary: Amarok doesn't play music when i click on play or
space bar
   Product: amarok
   Version: 2.8.0
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: amarok-bugs-d...@kde.org
  Reporter: zen...@free.fr

All functions of Amarok working, but I can not listen to music because when I
click play, it does nothing and the play bar does not react.

Reproducible: Always

Steps to Reproduce:
1.Amarok start
2.i click on play
3.don't work

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #23 from EricH <zen...@free.fr> ---
This is the : 
KDE Frameworks 5.19.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #21 from EricH <zen...@free.fr> ---
THANK YOU,
It works now  :-)
Good week-end

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #19 from EricH <zen...@free.fr> ---
Thank you for your help :-)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #18 from EricH <zen...@free.fr> ---
What is your KF5 Frameworks version?   
- I don't know

Also, can you run "rfkill list" as a normal user (no root or sudo).

eric@linux-seao:~> rfkill list
Absolute path to 'rfkill' is '/usr/sbin/rfkill', so running it may require
superuser privileges (eg. root).

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #16 from EricH <zen...@free.fr> ---
It doesn't work

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #14 from EricH <zen...@free.fr> ---
Created attachment 97846
  --> https://bugs.kde.org/attachment.cgi?id=97846=edit
Bluetooth Screenshot

The screenshot

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #12 from EricH <zen...@free.fr> ---
The system indicates that the device is disabled.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #10 from EricH <zen...@free.fr> ---
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: asus-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #8 from EricH <zen...@free.fr> ---
the answer:

linux-seao:~ # rfkill list
If 'rfkill' is not a typo you can use command-not-found to lookup the package
that contains it, like this:
cnf rfkill

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #6 from EricH <zen...@free.fr> ---
On Linux Mint cinnamon or Kubuntu, I could use my bluetooth, but not with
opensuse kde.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work

https://bugs.kde.org/show_bug.cgi?id=360392

--- Comment #4 from EricH <zen...@free.fr> ---
The terminal said

eric@linux-seao:~> qdbus --system org.bluez
/
/org
/org/bluez
eric@linux-seao:~> qdbus --system org.bluez /org/bluez/hci0
org.bluez.Adapter1.Powered
Error: org.freedesktop.DBus.Error.UnknownObject
Method "Powered" with signature "" on interface "org.bluez.Adapter1" doesn't
exist

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bluedevil] [Bug 360392] Bluetooth on my Asus G75VW does not work