https://bugs.kde.org/show_bug.cgi?id=484739
--- Comment #1 from Rob Chiocchio ---
An additional crash occurred under similar circumstances while trying to set
the default program for .tar.xz files. Below is the trace:
-- Backtrace:
Application: Portal (xdg-desktop-portal-kde), signal: Aborted
tal window froze and then crashed.
The crash does not seem to be reproducible.
-- Backtrace:
Application: Portal (xdg-desktop-portal-kde), signal: Aborted
PID: 2452 (xdg-desktop-por)
UID: 1000 (rob)
GID: 1000 (rob)
Signal: 6 (ABRT)
Timestamp: Sat 2024-0
https://bugs.kde.org/show_bug.cgi?id=484144
Bug ID: 484144
Summary: Kmail does not remember toolbar positions in the
message window
Classification: Applications
Product: kmail2
Version: 6.0.0
Platform: unspecified
https://bugs.kde.org/show_bug.cgi?id=439961
Rob Krum changed:
What|Removed |Added
Version|5.83.0 |5.115.0
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=439961
--- Comment #7 from Rob Krum ---
Created attachment 166540
--> https://bugs.kde.org/attachment.cgi?id=166540=edit
Screenshot which shows the error still occurs in fresh install of TW
To see if the error was still reproducible using the steps gi
https://bugs.kde.org/show_bug.cgi?id=439961
--- Comment #6 from Rob Krum ---
> If you can't reproduce it anymore, maybe it should be resolved WORKSFORME.
In my previous post I stated
> However, I am confident if I just installed Firefox with Kmozillahelper and
> use it, I would
https://bugs.kde.org/show_bug.cgi?id=439961
Rob Krum changed:
What|Removed |Added
Attachment #156588|0 |1
is obsolete
https://bugs.kde.org/show_bug.cgi?id=462750
Rob Hall changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=454247
rob.rol...@gmail.com changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=479655
Bug ID: 479655
Summary: Impliment auto-tagging in icon-view
Classification: Applications
Product: digikam
Version: 8.3.0
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=472068
--- Comment #4 from Rob ---
I noticed there was a minor upgrade to Gwenview from the Tumble weed repos this
morning - 23.04.3 -1.1. Gwenview now seems to be working completely normally,
thank you.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=472068
--- Comment #3 from Rob ---
I would be surprised if this is a duplicate of 470880 as it occurs with JPEG
files, both processed in Darktable/GIMP and straight out of the (Nikon) camera.
I have found a bit more information. The crash does not occur
https://bugs.kde.org/show_bug.cgi?id=472068
--- Comment #2 from Rob ---
I would be surprised if this is a duplicate of 470880 as it occurs with JPEG
files, both processed in Darktable/GIMP and straight out of the (Nikon) camera.
I have found a bit more information. The crash does not occur
https://bugs.kde.org/show_bug.cgi?id=472068
Bug ID: 472068
Summary: Gwenview crash on startup
Classification: Applications
Product: gwenview
Version: 23.04.2
Platform: openSUSE
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=470943
Rob Matlack changed:
What|Removed |Added
CC||okie2...@gmail.com
--- Comment #1 from Rob
https://bugs.kde.org/show_bug.cgi?id=393158
--- Comment #12 from Rob D ---
(In reply to Maik Qualmann from comment #11)
> How is the geolocation editor supposed to know which of all the tags are the
> location tags? The Tags column is only intended to show when new ones are
> added.
https://bugs.kde.org/show_bug.cgi?id=468018
Bug ID: 468018
Summary: Konqueror Auto bug
Classification: Applications
Product: konqueror
Version: 21.12.3
Platform: Kubuntu
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=457435
Rob V changed:
What|Removed |Added
CC||rvalk...@protonmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=457435
--- Comment #3 from Rob V ---
Created attachment 157336
--> https://bugs.kde.org/attachment.cgi?id=157336=edit
New crash information added by DrKonqi
kmail (5.19.2 (21.12.2)) using Qt 5.15.2
Folders in KMail had stopped refreshing with new ema
https://bugs.kde.org/show_bug.cgi?id=466503
Bug ID: 466503
Summary: Dolphin crashes when 2nd monitor is disabled from
Nvidia control panel
Classification: Applications
Product: dolphin
Version: 22.12.2
Platform:
https://bugs.kde.org/show_bug.cgi?id=439961
--- Comment #2 from Rob Krum ---
Sadly I am unable to reproduce the error with the script provided. I had
however put: [export QT_LOGGING_RULES="kf.kio.widgets.kdirmodel.warning=false"]
into my .bashrc file previously to supress the noise th
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_mouse
Assignee: plasma-b...@kde.org
Reporter: rob...@gmx.com
Target Milestone: ---
Created attachment 156682
--> https://bugs.kde.org/attachment.cgi?id=156682=edit
Screenshot of Sys
https://bugs.kde.org/show_bug.cgi?id=465720
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=465338
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=465720
--- Comment #3 from Rob ---
Ok this build should include fixes for both the QML rendering bug and the port
selector not showing up bug reported in this bug post.
www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg
Please try it out and let me
https://bugs.kde.org/show_bug.cgi?id=465338
--- Comment #4 from Rob ---
Ok this build should include fixes for both the QML rendering bug displayed
here and the port selector not showing up bug.
www.indilib.org/jdownloads/kstars/beta/kstars-3.6.3.dmg
Please try it out and let me know
https://bugs.kde.org/show_bug.cgi?id=465338
--- Comment #2 from Rob ---
Ok I think I have figured out the issue and I have a workaround. It looks like
there is some sort of QT bug with renderType being set incorrectly for various
components as I mentioned and setting the renderType for each
https://bugs.kde.org/show_bug.cgi?id=465858
Rob changed:
What|Removed |Added
CC||robcr...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=465858
Bug ID: 465858
Summary: shift + drag does not interact with the tiling layout
if Both Shifts together enable Caps Lock
Classification: Plasma
Product: kwin
Version: 5.27.0
https://bugs.kde.org/show_bug.cgi?id=286619
--- Comment #8 from Rob van der Linde ---
Sorry I didn't get around to testing this.
But "resolved, works for me" is that really a good way for a bot to close a
ticket?
How does a bot know it works? It's not as if the bot tested it... just
https://bugs.kde.org/show_bug.cgi?id=465338
--- Comment #1 from Rob ---
This is very strange indeed. I haven't seen this happen since I started
helping with KStars back in 2016. I did a whole bunch of stuff with the QML
code and I never saw it do that. I can confirm that after testing
https://bugs.kde.org/show_bug.cgi?id=286619
--- Comment #5 from Rob van der Linde ---
I will try to reproduce it this weekend if I can. The bug is stagnant because I
sort of stopped using Kopete when Google abandoned GTalk. But hopefully it's
still testable regardless of this.
--
You
https://bugs.kde.org/show_bug.cgi?id=462263
Bug ID: 462263
Summary: Dolphin File Explore
Classification: I don't know
Product: kde
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=460144
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=460144
Rob changed:
What|Removed |Added
CC||rlanca...@gmail.com
--- Comment #1 from Rob
https://bugs.kde.org/show_bug.cgi?id=399873
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=449509
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=457431
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=450148
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=454493
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=458351
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=457858
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=458640
--- Comment #3 from Rob ---
What I am thinking of with reducing variables would be to see if using the
internal guider vs using PHD2 is causing the issue. Then to try not using the
indi driver for the guide camera and using the internal driver in PHD2
https://bugs.kde.org/show_bug.cgi?id=458640
--- Comment #1 from Rob ---
I'm sorry this happened to you. The first question is really which thing is
causing the problem. From what you said, it could possibly be KStars, or INDI,
or PHD2, something with the network, or something with the camera
https://bugs.kde.org/show_bug.cgi?id=457425
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=457425
--- Comment #5 from Rob ---
Are you trying the latest dmg that I posted here?
https://edu.kde.org/kstars/#download
Because it definitely was doing what you described, but a more recent commit
fixed the issue and put into the stable 3.6.0 and then I
https://bugs.kde.org/show_bug.cgi?id=458158
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=457425
--- Comment #2 from Rob ---
It has taken me some time to work through several issues, but I think the 3.6.0
is now a pretty good one. Please check to see if it is improved. Based on
what you said here, I think you were having the issue with opening
https://bugs.kde.org/show_bug.cgi?id=457431
--- Comment #1 from Rob ---
It has taken me some time to work through several issues, but I think the 3.6.0
is now a pretty good one. Please check to see if it is improved. Based on
what you said here, I suspect you had the issue that was caused
https://bugs.kde.org/show_bug.cgi?id=457858
--- Comment #1 from Rob ---
It has taken me some time to work through several issues, but I think the 3.6.0
is now a pretty good one. Please check to see if it is improved. Based on
what you said here, I suspect you had the issue that was caused
https://bugs.kde.org/show_bug.cgi?id=458158
--- Comment #1 from Rob ---
It has taken me some time to work through several issues, but I think the 3.6.0
is now a pretty good one. Please check to see if it is improved. Based on
what you said here, I suspect you had the issue that was caused
https://bugs.kde.org/show_bug.cgi?id=458351
--- Comment #3 from Rob ---
So I have been building KStars DMGs and releases on my machine since 2016 or so
and every release was built and released that way. It was only a very short
time (~ 1 month or so) that we have been using the KDE binary built
https://bugs.kde.org/show_bug.cgi?id=456039
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=450582
--- Comment #26 from Rob ---
> However, given how buggy window shading is and how difficult it is to
> make it work right, I think that it's better to deprecate window shading
> and remove it in some future release.
Please do not do this.
https://bugs.kde.org/show_bug.cgi?id=456039
--- Comment #9 from Rob ---
This appears resolved now in 5.25.2? If you agree @hpj I will close as fixed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456039
--- Comment #8 from Rob ---
I just forced a rollback to kwin-5.24.5, and ran
$ kwin_x11 --replace
And right away all windows are shading properly.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456039
--- Comment #7 from Rob ---
Hmm, try as I might I cannot duplicate that. It just continues to exhibit the
broken behavior.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=456039
--- Comment #5 from Rob ---
Interesting, I cannot get a proper shade effect to work under any
circumstances. Shading, then switching to a Konsole and then back just
continues to display the old window contents. In fact, anything I drag into
the old
https://bugs.kde.org/show_bug.cgi?id=455859
Bug ID: 455859
Summary: digiKam 7.7.0 FTBFS with Qt 5.9 (as in Ubuntu 18.04
Bionic LTS)
Product: digikam
Version: 7.7.0
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=455725
--- Comment #3 from Rob Kemp ---
OK, I see, I'll search harder next time! Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455725
--- Comment #1 from Rob Kemp ---
I should have added I'm using X, not Wayland.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455725
Bug ID: 455725
Summary: Screen edge effects not working when window is
fullscreen
Product: kwin
Version: 5.25.1
Platform: Archlinux Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=449509
--- Comment #1 from Rob ---
I think I corrected this issue a few months ago, can you please check and
verify?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452116
--- Comment #1 from Rob ---
This is a long existing annoyance on MacOS. Basically the problem is that QT
on MacOS doesn't have the same parent - child window behavior as the other
operating systems. When I first ported KStars to the Mac, all
https://bugs.kde.org/show_bug.cgi?id=450148
--- Comment #4 from Rob ---
I believe this issue was resolved with a change I made a few months ago, can
you please check to see if it is fixed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453050
--- Comment #1 from Rob ---
The .solved and .cancel files are REALLY critical for external astrometry.net.
This is not a bug if you are referring to those two file types. The external
program astromety.net uses those files to determine that it should
https://bugs.kde.org/show_bug.cgi?id=454493
--- Comment #1 from Rob ---
If you would like a version of KStars with a code signature, you can get the
builds produced by craft on a daily basis.
https://binary-factory.kde.org/view/MacOS/job/KStars_Release_macos/
I have been working hard to get
https://bugs.kde.org/show_bug.cgi?id=454247
Bug ID: 454247
Summary: Cannot override / add to lsp settings in .kateproject
Product: kate
Version: 21.12.2
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=453630
--- Comment #3 from Rob D ---
(In reply to Maik Qualmann from comment #2)
> Which git/master digiKam-8.0.0 version are you using exactly? I just tested
> it here quickly, but I don't see any difference whether the tags were
> written w
https://bugs.kde.org/show_bug.cgi?id=453630
Bug ID: 453630
Summary: Metadata doesn 't always keep it's hierarchy when
written with exiftool
Product: digikam
Version: 8.0.0
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=451927
--- Comment #1 from Rob ---
What you are describing here sounds a lot like an intermittent issue we
discovered a couple of months ago.
https://indilib.org/forum/ekos/11081-mac-kstars-3-5-7-beta-new-build-please-test.html?start=48#79669
At the moment
https://bugs.kde.org/show_bug.cgi?id=450148
--- Comment #3 from Rob ---
We could have an option to automatically generate an alignment list and run
through the routine on startup.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450148
--- Comment #2 from Rob ---
There is a problem with that idea, that is different nights or times might have
different alignment points since as the time goes on, some of the points will
go below the horizon.
--
You are receiving this mail because
https://bugs.kde.org/show_bug.cgi?id=450148
--- Comment #1 from Rob ---
You are quite right. I experimented a little with this today. Yes they were
"save" and "save as" buttons. But yeah, you are right, it did ask twice on my
Mac about overwriting existing files. I
https://bugs.kde.org/show_bug.cgi?id=451366
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=451331
Rob changed:
What|Removed |Added
CC||rlanca...@gmail.com
--- Comment #1 from Rob ---
Hi
https://bugs.kde.org/show_bug.cgi?id=449731
Rob changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=451366
--- Comment #4 from Rob ---
Oops, I posted this before I read the post at the bottom, so it has been fixed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=451366
--- Comment #3 from Rob ---
Hi there, can you verify if this issue still exists now that I made
StellarSolver 2.2 and that we released KStars 3.5.8? I worked hard to address
crashing issues like this one, so hopefully these changes will fix it. I am
https://bugs.kde.org/show_bug.cgi?id=450639
--- Comment #12 from Rob ---
(In reply to Jose Antonio from comment #11)
> After upgrading to Plasma 5.24.2, the problem is gone.
Also fixed for me on Plasma 5.24.2.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414362
Rob changed:
What|Removed |Added
CC||r...@maris-ee.eu
--- Comment #23 from Rob ---
Since
https://bugs.kde.org/show_bug.cgi?id=310210
--- Comment #11 from Rob Collins ---
(Sorry - correction.there are about 1 billion icloud account/users not 1
million as posted in comment 8 LOL)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=310210
--- Comment #10 from Rob Collins ---
(moved version to 5.19.2 archlinux version of akonadi in the bug report header
as OP was 10 years ago with equivalent old versions)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=310210
Rob Collins changed:
What|Removed |Added
Platform|openSUSE RPMs |Archlinux Packages
Version|4.9
https://bugs.kde.org/show_bug.cgi?id=310210
Rob Collins changed:
What|Removed |Added
Summary|Cannot add apple / icloud |Cannot add apple / icloud
https://bugs.kde.org/show_bug.cgi?id=310210
--- Comment #9 from Rob Collins ---
Created attachment 146966
--> https://bugs.kde.org/attachment.cgi?id=146966=edit
Error 401 when trying to create carddav connection
This image belongs with comment 8
https://bugs.kde.org/show_bug.cgi?id=310210
https://bugs.kde.org/show_bug.cgi?id=310210
Rob Collins changed:
What|Removed |Added
CC||robcollin...@icloud.com
--- Comment #8 from Rob
https://bugs.kde.org/show_bug.cgi?id=450563
Bug ID: 450563
Summary: Could not download v7.5.0 from 7.3.0
Product: digikam
Version: 7.3.0
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity:
https://bugs.kde.org/show_bug.cgi?id=446885
Rob Hasselbaum changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=449731
--- Comment #1 from Rob ---
Thanks, I put in a pull request that should fix this
https://invent.kde.org/education/kstars/-/merge_requests/527
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=446885
--- Comment #10 from Rob Hasselbaum ---
Waiting on release of Plasma 5.24 to Arch repos to see if it fixes it. Will
update then.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405437
--- Comment #218 from Rob ---
So I am not sure what would cause this to print out. I did a google search for
"CC_READ_SUBTRACT_LINE" and found that it was probably associated with the SBIG
driver. You might want to post in the INDI for
https://bugs.kde.org/show_bug.cgi?id=449107
--- Comment #4 from Rob Savoury ---
(In reply to Maik Qualmann from comment #3)
> Hi Rob, please test if everything compiles fine now under Qt-5.9.5.
>
> Maik
Hi Maik, everything compiles fine now for Qt 5.9.5 and thanks for the quick
https://bugs.kde.org/show_bug.cgi?id=449107
Bug ID: 449107
Summary: digiKam 7.5.0 FTBFS with Qt 5.9.5 (as found in Ubuntu
Bionic 18.04)
Product: digikam
Version: 7.5.0
Platform: Ubuntu Packages
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=449080
--- Comment #5 from Rob D ---
I would have expected that if address elements have been defined, a path for
tag information could be determined and the information filled in.It was
just a thought for an enhancement.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=449080
--- Comment #2 from Rob D ---
All versions. Every version if Digikam since 5.0 that I can remember
(not sure whick version introduced reverse geotagging)
This is on all versions I've downloaded, as well as build from source
up to and including
https://bugs.kde.org/show_bug.cgi?id=449080
Bug ID: 449080
Summary: Assigned tags not appearing in geolocation editor
Product: digikam
Version: unspecified
Platform: unspecified
OS: All
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=442577
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=412719
Rob changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=420111
Rob changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
1 - 100 of 433 matches
Mail list logo
