[Smb4k] [Bug 427941] The gksu package is no longer included in Ubuntu

2020-10-18 Thread Doug Baden
https://bugs.kde.org/show_bug.cgi?id=427941

--- Comment #2 from Doug Baden  ---
Yes. I was looking at the configuration and found this. I can talk more
later tonight (USA EDT).

On Sun, Oct 18, 2020 at 4:58 PM Alexander Reinholdt <
bugzilla_nore...@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=427941
>
> --- Comment #1 from Alexander Reinholdt 
> ---
> Are you using Smb4K 2.1.0 from the Ubuntu repository?
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[Smb4k] [Bug 427941] The gksu package is no longer included in Ubuntu

2020-10-18 Thread Doug Baden
https://bugs.kde.org/show_bug.cgi?id=427941

--- Comment #3 from Doug Baden  ---
Can you send me the calling configuration for Smb4k?  This may be an
Elementary OS configuration error. The configuration error I found was in
/use/share/accessories/smb4k.desktop

On Sun, Oct 18, 2020 at 5:10 PM Doug Baden  wrote:

> Yes. I was looking at the configuration and found this. I can talk more
> later tonight (USA EDT).
>
> On Sun, Oct 18, 2020 at 4:58 PM Alexander Reinholdt <
> bugzilla_nore...@kde.org> wrote:
>
>> https://bugs.kde.org/show_bug.cgi?id=427941
>>
>> --- Comment #1 from Alexander Reinholdt 
>> ---
>> Are you using Smb4K 2.1.0 from the Ubuntu repository?
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>
>

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

[Smb4k] [Bug 427941] New: The gksu package is no longer included in Ubuntu

2020-10-18 Thread Doug Baden
https://bugs.kde.org/show_bug.cgi?id=427941

Bug ID: 427941
   Summary: The gksu package is no longer included in Ubuntu
   Product: Smb4k
   Version: unspecified
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: critical
  Priority: NOR
 Component: general
  Assignee: alexander.reinho...@kdemail.net
  Reporter: dougba...@gmail.com
  Target Milestone: ---

Created attachment 132539
  --> https://bugs.kde.org/attachment.cgi?id=132539=edit
A screenshot of the error

SUMMARY
Smb4k relies on gksu to get the network domains and this package is no longer
in the general release of Umbutu 18.04.  Perhaps use pkexec?

STEPS TO REPRODUCE
1. Start program
2. 
3. 

OBSERVED RESULT
Error pops up for a moment "Error retrieving the list of available domains
failed:"

EXPECTED RESULT
Listing of the domains in the window

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Elementary OS 5.1.7/Ubuntu 18.04 
(available in About System)
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION

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

[kmymoney] [Bug 427196] New: Cancelling a repeating schedule will cancel the wrong entry

2020-10-01 Thread Doug Lytle
https://bugs.kde.org/show_bug.cgi?id=427196

Bug ID: 427196
   Summary: Cancelling a repeating schedule will cancel the wrong
entry
   Product: kmymoney
   Version: 5.1.0
  Platform: Compiled Sources
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: kmymoney-de...@kde.org
  Reporter: kde4b...@pf01.com
  Target Milestone: ---

Created attachment 132040
  --> https://bugs.kde.org/attachment.cgi?id=132040=edit
Test kmymoney file showing the issue

SUMMARY

When trying to cancelled a repeating scheduled entry, clicking on the second or
third item in the schedule, results of the first time being reported as the
object to be cancelled.


STEPS TO REPRODUCE
1. Create a test kmymoney file
2. Set up a repeating payment schedule for every two weeks
3. Click on the second or third entry and kmymoney will prompt to cancel the
first

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[Smb4k] [Bug 427941] The gksu package is no longer included in Ubuntu

2020-10-29 Thread Doug Baden
https://bugs.kde.org/show_bug.cgi?id=427941

--- Comment #6 from Doug Baden  ---
Since I am on 2.1.0 this could be useful :).

On Thu, Oct 29, 2020 at 3:04 PM Nate Graham 
wrote:

> https://bugs.kde.org/show_bug.cgi?id=427941
>
> Nate Graham  changed:
>
>What|Removed |Added
>
> 
>Version Fixed In||3.0.0
>  Status|REPORTED|RESOLVED
>  CC||n...@kde.org
>  Resolution|--- |FIXED
>
> --
> You are receiving this mail because:
> You reported the bug.

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

[frameworks-kconfig] [Bug 426813] Some KXMLGui-using apps are opening maximized instead of windowed

2021-07-07 Thread Doug Glenn
https://bugs.kde.org/show_bug.cgi?id=426813

Doug Glenn  changed:

   What|Removed |Added

 CC||d...@wildhair.org

--- Comment #30 from Doug Glenn  ---
(In reply to 0xCAP from comment #9)
> I currently solved
> the issue by removing a bunch of "suspicious" lines from my
> ~/.config/konsolerc file.
> The lines looked like the following:
> 
> Window-Maximized 1016x1807=true
> ect ...

This fixed my issue. I'd always had a window size defined (130 x 80) that was a
good starting point. But like this gentleman, I had a window-maximized line
that was totally out of place. Removed it, and expected behaviour was restored.

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

[frameworks-kconfig] [Bug 426813] Some KXMLGui-using apps are opening maximized instead of windowed

2021-07-07 Thread Doug Glenn
https://bugs.kde.org/show_bug.cgi?id=426813

--- Comment #32 from Doug Glenn  ---
(In reply to Nate Graham from comment #31)
> Yeah there was a brief period of time during which those items were
> inappropriately written to people's config files. The bug causing this to
> happen has been fixed now, but it's possible that you would still be
> affected if it happened to you during that period of time. Removing them is
> a perfectly acceptable way to fix it for yourself.

Considering the time stamp of the participants, true. What flummoxed me was the
location. The convention for the .config directory originally was in this
format $XDG_CONFIG_HOME/subdir/filename, so I was looking for
.config/kde/configuration file location. It never occurred to me they would be
in the base of the .config file. The KDE configuration file location has
shifted a time or two since it was originally released so I was actually poking
around the ./local directory looking. The issue wasn't a major file to me and I
knew I'd eventually get around to finding an answer. I do wish the files would
eventually follow the convention, but innovation doesn't occur without breaking
a rule or two and the growth of Linux, KDE and the other windowing systems is
phenomenal. When I ran across it in 1995 you had to know the specific hardware
configuration and chipset of the video card to get X to run and all the apps
had to be built in order to run. It was a daunting experience but I knew OS/2
was in it's death spiral and I was desperate not to be forced into using any
Microsoft products at home. I switched to Linux full time in 1997 and the
change from the 1995 version was profound. The growth and maturity has
continued to defy my expectations and I don't see that changing.

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

[okular] [Bug 307224] Ability to rotate single pages

2023-09-03 Thread doug strain
https://bugs.kde.org/show_bug.cgi?id=307224

doug strain  changed:

   What|Removed |Added

 CC||t...@digimeas.com

--- Comment #2 from doug strain  ---
Hi!
Just got this funny email from bugzilla_nore...@kde.org: 

Bug 307224 Some or all of your votes have been removed.

Some or all of your votes have been removed from bug 307224.
You had 10 votes on this bug, but 10 have been removed.
You have no more votes remaining on this bug.
Reason:
  The rules for voting on this product has changed; you had
  too many total votes, so all votes have been removed.
https://bugs.kde.org/show_bug.cgi?id=307224

What's a vote? 

I'm pretty sure all I did was submit the feature request, and that's it.
Thanks
Doug

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

[ksirk] [Bug 474349] Ksirk crashes in Ksirk::GameLogic::AIPlayer::~AIPlayer

2023-09-11 Thread Doug Forguson
https://bugs.kde.org/show_bug.cgi?id=474349

--- Comment #2 from Doug Forguson  ---
Hi Nate,

Can you provide some guidance on the best way to get a valid package 
with one of these versions? Do I need to DL source and build or is there 
a package I can get somewhere?

Thanks,

Doug

On 9/11/23 14:04, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=474349
>
> Nate Graham  changed:
>
> What|Removed |Added
> 
>  Product|kde |ksirk
>   Status|REPORTED|NEEDSINFO
>   CC||kde-games-b...@kde.org,
> ||n...@kde.org
> Assignee|unassigned-b...@kde.org |nemhi...@gmail.com
>   Resolution|--- |WAITINGFORINFO
>  Summary|Ksirk crashes with a|Ksirk crashes in
> |SEGFAULT error in libc  |Ksirk::GameLogic::AIPlayer:
> ||:~AIPlayer
>Component|general |general
>  Version|unspecified |21.12.3
>
> --- Comment #1 from Nate Graham  ---
> 22.04 ships the quite-outdated version 21.12 version of KSirk which is almost
> two years old, and as such, out of support from KDE. Any chance you can 
> upgrade
> to 23.04 or 23.08 and try again? Thanks!
>

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

[kde] [Bug 474349] New: Ksirk crashes with a SEGFAULT error in libc

2023-09-09 Thread Doug Forguson
https://bugs.kde.org/show_bug.cgi?id=474349

Bug ID: 474349
   Summary: Ksirk crashes with a SEGFAULT error in libc
Classification: I don't know
   Product: kde
   Version: unspecified
  Platform: Ubuntu
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: d...@forguson.com
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
Running on Ubuntu studio 22.04 with xfce desktop. Note I also saw this issue
when using the default kde plasma desktop.

STEPS TO REPRODUCE
1. Launch ksirk application
2. Run as normal and app will frequently crash.
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: NA
macOS: NA
Linux/KDE Plasma:  Witnessed this under plasma and xfce desktop.
(available in About System)
KDE Plasma Version: ???
KDE Frameworks Version: 
Qt Version: 

Ran ksirk from gdb and captured the below stack trace. Never did get the kde
auto report tool to work. Always said it couldn't capture a backtrace even when
I launched using gdb.

ADDITIONAL INFORMATION

Thread 1 "ksirk" received signal SIGSEGV, Segmentation fault.
0x75d57c5d in __pthread_cancel (th=140736290416192) at
./nptl/pthread_cancel.c:64
Download failed: Invalid argument.  Continuing without source file
./nptl/./nptl/pthread_cancel.c.
64  ./nptl/pthread_cancel.c: No such file or directory.

(gdb) backtrace
#0  0x75d57c5d in __pthread_cancel (th=140736290416192) at
./nptl/pthread_cancel.c:64
#1  0x762078c9 in QThread::terminate() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x555faff7 in Ksirk::GameLogic::AIPlayer::~AIPlayer
(this=, this=)
at ./ksirk/GameLogic/aiplayer.cpp:84
#3  0x555e7b8d in Ksirk::GameLogic::AIColsonPlayer::~AIColsonPlayer
(this=, this=)
at ./ksirk/GameLogic/aiColsonPlayer.cpp:69
#4  0x555c2aae in Ksirk::KGameWindow::attackEnd (this=0x559492a0)
at ./ksirk/kgamewin.cpp:833
#5  0x555b08bf in Ksirk::KGameWindow::terminateAttackSequence
(this=0x559492a0) at ./ksirk/kgamewin.cpp:1901
#6  Ksirk::GameLogic::GameAutomaton::slotNetworkData (this=0x5592ec40,
msgid=, buffer=..., receiver=0, 
sender=1) at ./ksirk/GameLogic/gameautomaton.cpp:2145
#7  0x7642c793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x77d02087 in KGame::signalNetworkData
(this=this@entry=0x5592ec40, _t1=, _t1@entry=275, 
_t2=..., _t3=, _t3@entry=0, _t4=,
_t4@entry=1)
at
./obj-x86_64-linux-gnu/src/private/KF5KDEGamesPrivate_autogen/BQQKSAKFSH/moc_kgame.cpp:417
#9  0x77d17dc8 in KGame::networkTransmission (this=0x5592ec40,
stream=..., msgid=531, receiver=0, sender=1)
at ./src/private/kgame/kgame.cpp:1066
#10 0x77d1e82c in KGameNetwork::receiveNetworkTransmission
(this=0x5592ec40, receiveBuffer=..., clientID=1)
at ./src/private/kgame/kgamenetwork.cpp:482
#11 0x7642c793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x77d02247 in KMessageClient::broadcastReceived
(this=this@entry=0x55967750, _t1=..., _t2=, 
_t2@entry=1) at
./obj-x86_64-linux-gnu/src/private/KF5KDEGamesPrivate_autogen/BQQKSAKFSH/moc_kmessageclient.cpp:258
#13 0x77d2943e in KMessageClient::processMessage (this=0x55967750,
msg=...)
at ./src/private/kgame/kmessageclient.cpp:212
#14 0x7642c793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x77d01f76 in KMessageIO::received (this=, _t1=...)
at
./obj-x86_64-linux-gnu/src/private/KF5KDEGamesPrivate_autogen/BQQKSAKFSH/moc_kmessageio.cpp:152
#16 0x77d2d0ea in KMessageServer::broadcastMessage
(this=0x558c4780, msg=...)
at ./src/private/kgame/kmessageserver.cpp:340
#17 0x77d2fdc6 in KMessageServer::processOneMessage
(this=0x558c4780)
at ./src/private/kgame/kmessageserver.cpp:416
--Type  for more, q to quit, c to continue without paging--
#18 0x7642c793 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x764307fe in QTimer::timeout(QTimer::QPrivateSignal) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x7642233f in QObject::event(QEvent*) () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x76fc2713 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
()
   from /lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x763f4e3a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x7644d3eb in QTimerInfoList::activateTimers() () from
/lib/x86_64-linux-gnu/libQt5Core.so.5
#24 0x7644dd34 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7404fd3b in g_main_dispatch (context=0x7fffe8005010) at

[kalendar] [Bug 455687] New: Crashes on startup.

2022-06-20 Thread Doug Royer
https://bugs.kde.org/show_bug.cgi?id=455687

Bug ID: 455687
   Summary: Crashes on startup.
   Product: kalendar
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: douglasro...@gmail.com
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendar (22.04.1)

Qt Version: 5.15.3
Frameworks Version: 5.93.0
Operating System: Linux 5.17.5-300.fc36.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 36 (Thirty Six)"
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
Initial start, first time I have used it. Crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: Kalendar (kalendar), signal: Aborted

[KCrash Handler]
#4  0x7f8987d8ac3c in __pthread_kill_implementation () from
/lib64/libc.so.6
#5  0x7f8987d3a9c6 in raise () from /lib64/libc.so.6
#6  0x7f8987d247f4 in abort () from /lib64/libc.so.6
#7  0x7f89882024e5 in QMessageLogger::fatal(char const*, ...) const () from
/lib64/libQt5Core.so.5
#8  0x7f898a68d4c8 in
QSGRenderLoop::handleContextCreationFailure(QQuickWindow*) () from
/lib64/libQt5Quick.so.5
#9  0x7f898a68e824 in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*)
() from /lib64/libQt5Quick.so.5
#10 0x7f898a690122 in
QSGGuiThreadRenderLoop::exposureChanged(QQuickWindow*) () from
/lib64/libQt5Quick.so.5
#11 0x7f8988855795 in QWindow::event(QEvent*) () from /lib64/libQt5Gui.so.5
#12 0x7f8988ec6c82 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#13 0x7f89883f8658 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#14 0x7f898884b435 in
QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*)
() from /lib64/libQt5Gui.so.5
#15 0x7f8988829f5c in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /lib64/libQt5Gui.so.5
#16 0x7f89753e5aee in xcbSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt5XcbQpa.so.5
#17 0x7f8985eb2faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#18 0x7f8985f082c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#19 0x7f8985eb0940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#20 0x7f89884492fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#21 0x7f89883f70ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#22 0x7f89883ff162 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#23 0x558f237e5028 in main ()
[Inferior 1 (process 154602) detached]

The reporter indicates this bug may be a duplicate of or related to bug 452590.

Possible duplicates by query: bug 452590, bug 452574, bug 444391, bug 419428.

Reported using DrKonqi

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

[dolphin] [Bug 468388] New: Dropbox plugin does not get acivated unless your FIRST visit the root of your Dropbox folder

2023-04-11 Thread Doug B
https://bugs.kde.org/show_bug.cgi?id=468388

Bug ID: 468388
   Summary: Dropbox plugin does not get acivated unless your FIRST
visit the root of your Dropbox folder
Classification: Applications
   Product: dolphin
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: w...@dougie.io
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Have some sub-folders in your Dropbox folder. Also be sure to enable the
Dropbox Dolphin plugin.
2. Visit these subfolders and add them to your 'Places' in Dolphin.
3. Close Dolphin
4. Open Dolphin and click one of the new Places items for your Dropbox
subfolders
5. Observe
6. Open the root of your Dropbox folder
7. Open a subfolder
8. Observe

OBSERVED RESULT

The Dropbox status icons do not show when you launch Dolphin and visit the
folder directly. You have to first navigate to the root Dropbox folder to
activate the plugin, then you can visit the sub directories and see the proper
file status icons.


EXPECTED RESULT

Whenever you visit any path within your Dropbox folder it should activate the
plugin.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.8
Kernel Version: 6.1.23-1-lts (64-bit)
Graphics Platform: X11

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

[plasma-systemmonitor] [Bug 481348] New: Crashes switching to any tab or menu

2024-02-14 Thread Doug Turex
https://bugs.kde.org/show_bug.cgi?id=481348

Bug ID: 481348
   Summary: Crashes switching to any tab or menu
Classification: Applications
   Product: plasma-systemmonitor
   Version: 5.27.5
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: ksysguard-b...@kde.org
  Reporter: truwre...@gmail.com
CC: ahiems...@heimr.nl, plasma-b...@kde.org
  Target Milestone: ---

Application: plasma-systemmonitor (5.27.5)

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.5.0-0.deb12.4-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Open System Monitor, select any tab or menu. Application hangs then crashes to
desktop. 

I have tried with default global themes dark themes. This application started
crashing after Debian updated to 12.5.

Linux 6.5.0-0.deb12.4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.5.10-1~bpo12+1
(2023-11-23) x86_64 GNU/Linux
01:00.0 VGA compatible controller: NVIDIA Corporation AD102 [GeForce RTX 4090]
(rev a1)

I currently have Backports-Bookworm enabled to get Kernel 6.5 for newer
hardware support.

The crash can be reproduced every time.

-- Backtrace:
Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault

[KCrash Handler]
#4  0x in ?? ()
#5  0x7efe49c3fae7 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#6  0x7efe49c3fb59 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#7  0x7efe49dc1dc2 in QAccessibleQuickItem::role() const () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#8  0x7efe4af77081 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x7efe4af79e04 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x7efe4af7b5a1 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#11 0x7efe49c4d6d3 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#12 0x7efe49c55ffd in QQuickItem::setParentItem(QQuickItem*) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#13 0x7efe49c5650d in QQuickItem::~QQuickItem() () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#14 0x7efe3ab9d8c5 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so
#15 0x7efe491b6357 in
QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*,
QQmlTableInstanceModel::DestructionMode) () from
/lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#16 0x7efe491dcaf1 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#17 0x7efe491b5d85 in QQmlTableInstanceModel::drainReusableItemsPool(int)
() from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5
#18 0x7efe49d3de8c in QQuickTableView::geometryChanged(QRectF const&,
QRectF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#19 0x7efe49c4c2e8 in QQuickItem::setSize(QSizeF const&) () from
/lib/x86_64-linux-gnu/libQt5Quick.so.5
#20 0x7efe492bd3a9 in QQuickControlPrivate::resizeContent() () from
/lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5
#21 0x7efe492b9ef3 in QQuickControlPrivate::setRightPadding(double, bool)
() from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5
#22 0x7efe50aeaa43 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#23 0x7efe50aeb93e in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#24 0x7efe50ae9354 in
QQmlBinding::update(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#25 0x7efe50ac677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#26 0x7efe4f2e8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#27 0x7efe50a6ea35 in QQmlVMEMetaObject::metaCall(QObject*,
QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#28 0x7efe50aeaa19 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#29 0x7efe50aeb93e in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#30 0x7efe50ae9354 in
QQmlBinding::update(QFlags) () from
/lib/x86_64-linux-gnu/libQt5Qml.so.5
#31 0x7efe50ac677f in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*,
void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5
#32 0x7efe4f2e8a8d in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x7efe49c4d728 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#34 0x7efe49c4d651 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#35 0x7efe49c4d651 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#36 0x7efe49c4d651 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from /lib/x86_64-linux-gnu/libQt5Quick.so.5
#37 0x7efe49c4d651 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) ()
from 

[kronometer] [Bug 477343] New: [Feature Request] Checkbox for showing current lap in lap list

2023-11-21 Thread Doug B
https://bugs.kde.org/show_bug.cgi?id=477343

Bug ID: 477343
   Summary: [Feature Request] Checkbox for showing current lap in
lap list
Classification: Applications
   Product: kronometer
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: w...@dougie.io
  Target Milestone: ---

Use case: Tracking time for work.

I love Kronometer and I'm experimenting with using it as a personal
productivity tool, always having an incrementing stopwatch on my monitor so I
don't waste too much time.

I nice feature would be a checkbox that shows the current lap in the lap list.
Currently, the lap doesn't show in the list until you press "Lap". It would be
nice to see the lap beforehand because then I can name the task I am working on
ahead of time in the "Note" column.

Thank you for your great work!

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

[kio] [Bug 357465] New: nfs async write causes CPU to spike 100%, plasma to freeze, incorrect write speed. Sync works however

2016-01-03 Thread doug via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357465

Bug ID: 357465
   Summary: nfs async write causes CPU to spike 100%, plasma to
freeze, incorrect write speed. Sync works however
   Product: kio
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: nfs
  Assignee: unassigned-b...@kde.org
  Reporter: dougiem...@gmail.com

Using a laptop with wireless connection to router
KDE Plasma Version: 5.5.2
QT Version 5.5.1
Kernel Version: 4.4.0-1-MANJARO
nfs-utils 1.3.3-3
fstab entry: 192.168.1.67:/volume1/share   /home/doug/NAS nfs
vers=4,noauto,user,noatime,x-systemd.device-timeout=10,timeo=14,intr,soft 0 0

Hi there,

When copying large files to an nfs4 drive mounted as async the copying
notification plasmoid freezes, cpu maxes out, dolphin freezes, write speed in
the copying notification is incorrect and then disappears.

This can be worked around by mounting as sync in fstab but this has slower read
/ writes. Can the async behaviour be fixed? In other desktop environments
mounting as the default option async is not an issue.

*strangely if it is mounted as async copying files over from the nfs drive to
laptop does not seem to be a problem. Even the copy speed within the copying
notification is correct.

Reproducible: Always

Steps to Reproduce:
1. mount nfs4 drive as async on wireless laptop connection
2. copy large file to nfs drive 
3.

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


[muon] [Bug 356284] New: password dialog closes before password can be entered, error message can not continue as permission not granted

2015-12-04 Thread Doug Taylor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356284

Bug ID: 356284
   Summary: password dialog closes before password can be entered,
error message can not continue as permission not
granted
   Product: muon
   Version: 2.2.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: updater
  Assignee: echidna...@kubuntu.org
  Reporter: doug.tay...@taymade.co.uk
CC: aleix...@kde.org, sit...@kde.org

problem also occurs with software updater

Reproducible: Always




waited for entry of data

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


[Discover] [Bug 356284] password dialog closes before password can be entered, error message can not continue as permission not granted

2016-03-22 Thread Doug Taylor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356284

--- Comment #2 from Doug Taylor <doug.tay...@taymade.co.uk> ---
On 22/03/2016 12:36, Aleix Pol via KDE Bugzilla wrote:
> https://bugs.kde.org/show_bug.cgi?id=356284
>
> Aleix Pol <aleix...@kde.org> changed:
>
> What|Removed |Added
> 
>   Resolution|--- |WAITINGFORINFO
>   Status|UNCONFIRMED |NEEDSINFO
>
> --- Comment #1 from Aleix Pol <aleix...@kde.org> ---
> Under which distribution?
>
Kubuntu 14.04

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


<    1   2   3   4   5