[okular] [Bug 463647] Slow start on network mounts because of image icon lookups + may broken UI
https://bugs.kde.org/show_bug.cgi?id=463647 Bernard Gray changed: What|Removed |Added CC||bernard.g...@gmail.com --- Comment #6 from Bernard Gray --- We're experiencing it over a CIFS network share. Examining the calls via wireshark we get a lot of failed attempts to open non-existant files - examples include: bookmark-new.bw help-about.ani help-about.avif kde.epsi kde.gif okular.jpg Screenshot of wireshark: https://drive.google.com/file/d/18vEk8G30uHFKy7W5PZJAWmiaSoCHc5q9/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Bernard Gray changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Bernard Gray --- After some review/modifications, both patches have been accepted upstream https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1411 https://invent.kde.org/graphics/okular/-/merge_requests/764 Setting RESOLVED FIXED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 --- Comment #6 from Bernard Gray --- PR for okular: https://invent.kde.org/graphics/okular/-/merge_requests/764 PR for poppler: https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1411 PPA for jammy if people feel like testing: https://launchpad.net/~bernard-gray/+archive/ubuntu/okular-poppler -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 --- Comment #5 from Bernard Gray --- Created attachment 159408 --> https://bugs.kde.org/attachment.cgi?id=159408=edit Comparison of PDF output with Overprint on vs off -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 --- Comment #4 from Bernard Gray --- Created attachment 159407 --> https://bugs.kde.org/attachment.cgi?id=159407=edit PDF file requiring Overprint support to display correctly done! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Bernard Gray changed: What|Removed |Added Version|0.15.2 |21.12.3 --- Comment #2 from Bernard Gray --- I have raised this request in the okular mailing list: https://mail.kde.org/pipermail/okular-devel/2023-May/044525.html Oliver Sander has indicated that (some level of) overprint support exists in poppler: > See for example the manpage of pdftops. Ref: https://mail.kde.org/pipermail/okular-devel/2023-May/044531.html They have directed me to raise an issue here - I will crosslink this bug back to the mailing list and see if it can get some movement :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Bernard Gray changed: What|Removed |Added CC||bernard.g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 454693] Okular throws error when saving to mounted Samba share
https://bugs.kde.org/show_bug.cgi?id=454693 --- Comment #9 from Bernard Gray --- Further testing: Ubuntu 18.04 - Mounting samba share with ver=2.1 and using okular 17.12.3 Can edit and save file Ubuntu 20.04 - Mounting samba share with ver=2.1 and using okular 19.12.3 Fails as per bug To summarise: Okular has previously been able to edit and save files over smb protocal v2.1, and this functionality broke between 17.12.3 and 19.12.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 454693] Okular throws error when saving to mounted Samba share
https://bugs.kde.org/show_bug.cgi?id=454693 Bernard Gray changed: What|Removed |Added CC||bernard.g...@gmail.com --- Comment #8 from Bernard Gray --- (In reply to Albert Astals Cid from comment #2) > Any chance you can point us to how to create a "CIFS mounted Samba share > which is working properly" so we can try to reproduce the problem? > > At least me i have no idea about Samba Hi @albert, We have been experiencing the same issue - Here is a basic open rw share config for an ubuntu server: https://ubuntu.com/server/docs/samba-file-server To mount, use commands as per OP: sudo mount -t cifs ///share /path/to/local/mountpoint/ -o uid=1000,gid=1000 Some further testing: - This is only an issue on samba 4, using smb protocols v[2.0 | 2.1 | 3.1.1 ] - samba 3, using smb protocol v1.0 is not affected -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 347772] kscreenlocker_greet using 100% cpu on plasma 5
https://bugs.kde.org/show_bug.cgi?id=347772 Bernard Gray changed: What|Removed |Added CC||bernard.g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 418906] UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten
https://bugs.kde.org/show_bug.cgi?id=418906 --- Comment #2 from Bernard Gray --- Further clarification: When mounting the network share, use `sudo mount.cifs` (not the KDE userspace way). In my specific use case, users mount network shares using mount.cifs called by the pam_mount module at login - -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 418906] UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten
https://bugs.kde.org/show_bug.cgi?id=418906 --- Comment #1 from Bernard Gray --- To extend ADDITIONAL INFORMATION section: ...making the shortcut inaccessible to user1 via the Devices panel list. Note that user1 still *sees* the share/Device listed (which is expected), but clicking on it attempts to display the contents of the mountpoint in user2's home directory (which is *not* expected) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 418906] New: UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten
https://bugs.kde.org/show_bug.cgi?id=418906 Bug ID: 418906 Summary: UDI (Unique Device Identifier) provided by solid is not actually unique, entry gets overwritten Product: frameworks-solid Version: 5.44.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: lu...@kde.org Reporter: bernard.g...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Unique Device Identifier provided by solid is not unique STEPS TO REPRODUCE 1. Sign in as user 1 and mount a samba network share (cifs://server/files) as user1 under /home/user1/files/ 2. run `solid-hardware list details` to see the solid-hardware entry, note the: UDI /org/kde/fstab///server/files, and StorageAccess.filePath = '/home/user1/files' (String) 3. Switch user and sign in as user2 , then mount _the_same_ network share smb://server/files as user2 under /home/user2/files/ 4. confirm both shares are correctly mounted: `mount | grep files` 5. run `solid-hardware list details` to see the solid-hardware entries OBSERVED RESULT solid-hardware list details shows a single entry for the mounted network share, with the StorageAccess.filePath value of the most recently mounted share. The previous solid-hardware device entry is overwritten The UDI is identical to the first mounted device, which means that solid is not actually using "Unique" Identifiers - EXPECTED RESULT solid-hardware list details should show multiple entries for the same network share mounted at different locations. These entries should have a unique UDI SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.04 (bionic)/KDE Plasma 5.12.9 (available in About System) KDE Plasma Version: 5.12.9 KDE Frameworks Version: 5.44.0 Qt Version: 5.9.5 ADDITIONAL INFORMATION This manifests itself in places like dolphin, in the device list it will only show the most recently mounted share, making the shortcut inaccessible to user1 via the Devices panel list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378683] org.kde.plasma.systemtray configKeys not accessible via plasma script api
https://bugs.kde.org/show_bug.cgi?id=378683 --- Comment #7 from Bernard Gray --- Hi Konrad, Apologies, I forgot about this. I'm not sure there was an actual issue in the end, so this should be fine to close - appreciate the assistance! -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 292068] no option to start krfb in background
https://bugs.kde.org/show_bug.cgi?id=292068 Bernard Gray changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||bernard.g...@gmail.com --- Comment #3 from Bernard Gray --- This can be closed: commit d5aff98912deebf204ddcc773894b73a3163eb56 Author: Friedrich W. H. Kossebau Date: Fri Mar 1 05:31:12 2019 +0100 Properly add "nodialog" option before running QCommandLineParser::process() -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 411986] [PATCH] Simplify attended password, multi case/character is too hard to read out over the phone for support
https://bugs.kde.org/show_bug.cgi?id=411986 --- Comment #1 from Bernard Gray --- Please note, this only affects the password factor of the *attended password* - the second factor (user allowing the connection) is still required in case the password is guessed -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 411986] New: [PATCH] Simplify attended password, multi case/character is too hard to read out over the phone for support
https://bugs.kde.org/show_bug.cgi?id=411986
Bug ID: 411986
Summary: [PATCH] Simplify attended password, multi
case/character is too hard to read out over the phone
for support
Product: krfb
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: grundleb...@googlemail.com
Reporter: bernard.g...@gmail.com
Target Milestone: ---
Created attachment 122685
--> https://bugs.kde.org/attachment.cgi?id=122685=edit
patch
SUMMARY
The current attended password format is simply too complicated for users to
read out over the phone.
This patch simplifies it to a 4 digit integer, patch from the current github
master
--- a/krfb/invitationsrfbserver.cpp
+++ b/krfb/invitationsrfbserver.cpp
@@ -110,7 +110,7 @@ void InvitationsRfbServer::toggleUnattendedAccess(bool
allow)
InvitationsRfbServer::InvitationsRfbServer()
{
-m_desktopPassword = readableRandomString(4) + QLatin1Char('-') +
readableRandomString(3);
+m_desktopPassword = readableRandomFourDigits();
m_unattendedPassword = readableRandomString(4) + QLatin1Char('-') +
readableRandomString(3);
KConfigGroup krfbConfig(KSharedConfig::openConfig(),"Security");
m_allowUnattendedAccess = krfbConfig.readEntry(
@@ -207,6 +207,19 @@ void InvitationsRfbServer::walletOpened(bool opened)
}
}
+// a random string made up of numbers for easy readability
+// based on KRandom::random()
+QString InvitationsRfbServer::readableRandomFourDigits()
+{
+int r = KRandom::random();
+while (r < 1000) {
+r = KRandom::random();
+}
+QString str = QString::number(r);
+str.resize(4);
+return str;
+}
+
// a random string that doesn't contain i, I, o, O, 1, l, 0
// based on KRandom::randomString()
QString InvitationsRfbServer::readableRandomString(int length)
diff --git a/krfb/invitationsrfbserver.h b/krfb/invitationsrfbserver.h
index 6b6b16d..cc54a29 100644
--- a/krfb/invitationsrfbserver.h
+++ b/krfb/invitationsrfbserver.h
@@ -68,6 +68,7 @@ private:
QString m_unattendedPassword;
KWallet::Wallet *m_wallet;
+QString readableRandomFourDigits();
QString readableRandomString(int);
Q_DISABLE_COPY(InvitationsRfbServer)
};
--
You are receiving this mail because:
You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #13 from Bernard Gray --- Thanks all :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392913] NTFS mountpoints appears as hidden after mount
https://bugs.kde.org/show_bug.cgi?id=392913 Bernard Gray changed: What|Removed |Added CC|bernard.g...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #9 from Bernard Gray --- (In reply to Albert Astals Cid from comment #8) > I understand your use case seems common to you, because it's your use case > to you it happens 100% of the time, but no one reported this before. I fully understand, I was being funny (at least, attempting to be) :P > That's why I am asking someone from the Plasma side to answer whether we > want to backport this fixes or not. Pretty please? Just to confirm, are you asking me to ask the question to the plasma maintainers? Or have you asked the question to the maintainers already? Or are you asking if someone else knows how to ask the plasma maintainers? -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #7 from Bernard Gray --- (In reply to Albert Astals Cid from comment #6) > (In reply to Fabian Vogt from comment #5) > > It's not fixed - that commit is not in 5.12.x. > > > > @aacid: Any reason in particular it was only submitted for 5.13? > > I guess i found it to be corner case-y and not warranted a backport since > there's always the risk/benefit calculation you have to do when backporting > something to a LTS branch. > > I've no idea how common this scenario and how "live-tested" we can say my > new code is to say "yes it doesn't seem to cause regressions let's bring it > to 5.12 since it's an important fix" * sddm is shipping with a default config which uses pam_kwallet*.so * I expect most enterprise deployments will use the libpam_mkhomedir.so module ie Most enterprise deployments shipping vanilla-ish KDE which, from my perspective of course, isn't really a corner case :P -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 Bernard Gray changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #4 from Bernard Gray --- (In reply to Fabian Vogt from comment #3) > This should be fixed in pam_kwallet 5.13.0 - not sure why it wasn't added to > Plasma/5.12. > > Can you build pam_kwallet with > https://cgit.kde.org/kwallet-pam.git/commit/ > ?id=06760eed821f5383d03dc83a9a077a377ba39541 to confirm that it's fixed or > try pam_kwallet 5.13.x? Should be relatively easy, pam_kwallet has no > dependencies on other parts of Plasma. Hi Fabian, Thanks for this tidbit - I did give it a test last week with this patch, and it has resolved the issue. My apologies for the slow reply! -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 --- Comment #2 from Bernard Gray --- (In reply to Kai Uwe Broulik from comment #1) > > *** This bug has been marked as a duplicate of bug 392913 *** This has nothing to do with the duplicate you've marked -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 Bernard Gray changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|DUPLICATE |--- -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 395947] New: Using pam_kwallet5.so breaks pam_mkhomedir.so
https://bugs.kde.org/show_bug.cgi?id=395947 Bug ID: 395947 Summary: Using pam_kwallet5.so breaks pam_mkhomedir.so Product: kwallet-pam Version: 5.12.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: bernard.g...@gmail.com Target Milestone: --- Created attachment 113617 --> https://bugs.kde.org/attachment.cgi?id=113617=edit /etc/pam.d/sddm on k/ubuntu 18.04 Hi folks, I'm running k/ubuntu 18.04, and using pam to do ldap authenticated logins. As part of this process, for each user I need to create my default environment from /etc/skel/ What Happened: When I login, the home dir is created without the contents of /etc/skel What I expect to Happen: When I login, the home dir is created *with* the contents of /etc/skel How to recreate the problem: 1. Enable the pam_mkhomedir.so according to your platform requirements - on ubuntu, I use a config in /usr/share/pam-configs/ and run sudo pam-auth-update to apply it to the various /etc/pam.d/common-* files 2. Login to an account that doesn't have any home dir created yet 3. Verify that files from /etc/skel/ have not been copied (.bashrc is a really obvious one) Extra Investigation Notes: * This came about because sddm pulls in an /etc/pam.d/sddm config (attached), which has a couple of pam_kwallet*.so entries. * This bug report against sddm suggested a workaround which involved removing all the pam_kwallet*.so entries and adding the pam_mkhomedir entry manually (I verified this works): https://github.com/sddm/sddm/issues/769 * in order to verify separation from sddm, I load the pam_kwallet5.so in common-[auth,session] instead of the sddm config. I use a different display manager (gdm3) and pam_mkhomedir.so fails to run. If I disable the kwallet entries and login using gdm3, pam_mkhomedir.so runs (in gdm3 it gives you a status message). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #9 from Bernard Gray <bernard.g...@gmail.com> --- (In reply to Jonathan Riddell from comment #8) ... > However I couldn't get pykde4 to build with latest sip/kdelibs/whatever > /usr/include/kautomount.h:105:5: error: ‘KAutoUnmount::~KAutoUnmount()’ is > private > http://build.neon.kde.org/job/xenial_release_forks_pykde4_bin_amd64/1/console Hi Jonathon, thanks for having a look. I had the same issue trying to build pykde4, the packages that depend on it are pretty thin on the ground now, is it worth just committing to it's removal for neon? python3-pykde4 Reverse Depends: python3-pykde4-dbg update-manager-kde apturl-kde update-manager-kde python3-keyring python3-keyrings.alt gdebi-kde apturl-kde -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #7 from Bernard Gray <bernard.g...@gmail.com> --- I've done a bit more digging: I ended up finding the following bug/patch on the NixOS github project: https://github.com/NixOS/nixpkgs/issues/24548 https://github.com/NixOS/nixpkgs/commit/8c9b60a8307b4dafffb894b3d652389f6079b68a "This package is broken since 0a3b7f9 (python-sip: 4.18.1 -> 4.19.1). Removing it seems reasonable since we're dropping KDE4 anyway." I suspect that this is precisely what Neon is doing too, although I don't know where to find evidence of it. I've ended up migrating my in-house python package to PyQt5 anyway since finding this :) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 381385] KFileDialog ignores SingleClick=false directive
https://bugs.kde.org/show_bug.cgi?id=381385 Bernard Gray <bernard.g...@gmail.com> changed: What|Removed |Added Resolution|WAITINGFORINFO |INVALID Status|NEEDSINFO |RESOLVED --- Comment #2 from Bernard Gray <bernard.g...@gmail.com> --- Ah thanks for the tip - You're absolutely correct, I've got it configured in ~/.kde/share/config/kdeglobals (KDE4 I presume), but not in ~/.config/kdeglobals (KDE5 I guess?) - setting both resolves it Apologies for the dud bug report, and thanks for looking at it :) -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 381385] New: KFileDialog ignores SingleClick=false directive
https://bugs.kde.org/show_bug.cgi?id=381385 Bug ID: 381385 Summary: KFileDialog ignores SingleClick=false directive Product: kdelibs Version: 4.14.0 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: bernard.g...@gmail.com Target Milestone: --- I've configured the KDEGlobals with SingleClick=false directive. This means I single-click to select in most programs (eg Dolphin) and Double-click to execute/activate. The KFileDialog file picker always does the SingleClick=true behaviour (ie single-click to execute/activate) regardless of what is set in KDEGlobals, which is a bug - It should behave in whatever way the SingleClick= directive is configured. -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #4 from Bernard Gray <bernard.g...@gmail.com> --- Hi Scott, Thanks for the reply. I apologise, but I thought this bugtracker is where I would make neon related requests. I gather from your post that I was wrong - can you point me in the direction of where I should post my request to rebuild python3-pykde4? -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #2 from Bernard Gray <bernard.g...@gmail.com> --- (In reply to Bernard Gray from comment #1) > Is it possible to build python3-sip to include provides for sip-py3api-11.X > AND sip-py3api-12.X? Alternatively, can neon start including compatible builds of python3-pykde4 in their repos? -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 381003] python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 --- Comment #1 from Bernard Gray <bernard.g...@gmail.com> --- Ok, I've worked it out what's actually going wrong. Apologies, lack of sleep and soforth: "python3-pykde4" is an ubuntu provided package, that depends on a virtual package "sip-py3api-11.2" provided by python3-sip (< 4.19) The neon repositories now include python3-sip=4.19.2+dfsg-1+16.04+xenial+build3 but this does not provide "sip-py3api-11.2" # apt-cache show python3-sip | egrep -e ^Provides -e ^Version Version: 4.19.2+dfsg-1+16.04+xenial+build3 Provides: sip-py3api-12.0, sip-py3api-12.1 ... Is it possible to build python3-sip to include provides for sip-py3api-11.X AND sip-py3api-12.X? -- You are receiving this mail because: You are watching all bug changes.
[bindings] [Bug 381003] New: python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip)
https://bugs.kde.org/show_bug.cgi?id=381003 Bug ID: 381003 Summary: python3-pykde4 won't install due to broken dep on sip-py3api-11.2 (provided by python3-sip) Product: bindings Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: pykde Assignee: kde-bindi...@kde.org Reporter: bernard.g...@gmail.com Target Milestone: --- Hi all, I hope this is the correct place to report this - In short, I'm building cleanroom chroots on KDE Neon user/lts packages - about 24 hours ago, I began getting build failures: > The following packages have unmet dependencies: > python3-pykde4 : Depends: sip-py3api-11.2 Digging into this, 1. python3-pykde4 is an ubuntu provided package 2. the missing dependency is provided by python3-sip, a neon provided package For reasons beyond my understanding, python3-pykde4 is not taking any notice of the python3-sip Provides which satisfies the sip-py3api-11.2 dep # apt-cache policy python3-pykde4 python3-pykde4: Installed: (none) Candidate: 4:4.14.2-0ubuntu6 Version table: 4:4.14.2-0ubuntu6 500 500 http://aptmirror.debortoli.private:3142/archive.ubuntu.com/ubuntu xenial/universe amd64 Packages # apt-cache policy python3-sip python3-sip: Installed: 4.19.2+dfsg-1+16.04+xenial+build3 Candidate: 4.19.2+dfsg-1+16.04+xenial+build3 Version table: *** 4.19.2+dfsg-1+16.04+xenial+build3 500 500 http://archive.neon.kde.org/user/lts xenial/main amd64 Packages 100 /var/lib/dpkg/status 4.18.1+dfsg-2+16.04+build3 500 500 http://archive.neon.kde.org/user/lts xenial/main amd64 Packages 4.17+dfsg-1build1 500 500 http://aptmirror.debortoli.private:3142/archive.ubuntu.com/ubuntu xenial/universe amd64 Packages ** I used this aptitude search command to see what packages provide sip-py3api-11.2, and their installation status: # aptitude search '~Psip-py3api-11.2' i python3-sip - Python 3/C++ bindings generator runtime library p python3-sip:i386 ** So with everything ready to go, deps satisfied by virtual packages, I should be able to install python3-pykde4: # apt-get install python3-pykde4 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-pykde4 : Depends: sip-py3api-11.2 E: Unable to correct problems, you have held broken packages. ** there are no held packages # dpkg --get-selections | grep hold # -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380344] Shutdown/Reboot countdown overlay incorrectly shows Logout option when logout=false set in KDE Action Restrictions
https://bugs.kde.org/show_bug.cgi?id=380344 --- Comment #2 from Bernard Gray <bernard.g...@gmail.com> --- Thankyou guys, this is spectacular service. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 380344] New: Shutdown/Reboot countdown overlay incorrectly shows Logout option when logout=false set in KDE Action Restrictions
https://bugs.kde.org/show_bug.cgi?id=380344 Bug ID: 380344 Summary: Shutdown/Reboot countdown overlay incorrectly shows Logout option when logout=false set in KDE Action Restrictions Product: plasmashell Version: 5.8.7 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: bernard.g...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 105769 --> https://bugs.kde.org/attachment.cgi?id=105769=edit screenshots showing the directive, Leave menu, and overlay Hi all, When I set the logout=false directive in my KDE Action Restrictions, it hides the logout item from the Application Launcher "Leave" tab, but still shows the Logout item in the Shutdown/Reboot countdown overlay. The Logout option should not be visible in the Shutdown/Reboot overlay if the logout=false directive is set. I've attached a couple of screenshots highlighting the problem. My complete [KDE Action Restrictions] section looks like this (all the other directives work): [KDE Action Restrictions][$i] logout=false action/switch_user=false action/start_new_session=false -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378683] org.kde.plasma.systemtray configKeys not accessible via plasma script api
https://bugs.kde.org/show_bug.cgi?id=378683 --- Comment #5 from Bernard Gray <bernard.g...@gmail.com> --- The config looks as follows after running the script as described above (new panel, add systemtray widget, write systemtray configs): = [Containments][22][General] extraItems=org.kde.discovernotifier,org.kde.kdeconnect,org.kde.plasma.bluetooth,org.kde.plasma.clipboard,org.kde.plasma.devicenotifier,org.kde.plasma.mediacontroller,org.kde.plasma.networkmanagement,org.kde.plasma.notifications,org.kde.plasma.printmanager,org.kde.plasma.volume,org.kde.ktp-contactlist,org.kde.plasma.battery hiddenItems=org.kde.plasma.battery,org.kde.plasma.ktp-contactlist knownItems=org.kde.kdeconnect,org.kde.ktp-contactlist,org.kde.plasma.battery,org.kde.plasma.clipboard,org.kde.plasma.devicenotifier,org.kde.plasma.mediacontroller,org.kde.plasma.networkmanagement,org.kde.plasma.notifications,org.kde.plasma.printmanager,org.kde.plasma.volume = Which looks normal, except the widgets which are explicitly listed under the hiddenItems key are still visible on the newly created panel (battery, ktp-contactlist). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378683] org.kde.plasma.systemtray configKeys not accessible via plasma script api
https://bugs.kde.org/show_bug.cgi?id=378683
--- Comment #3 from Bernard Gray <bernard.g...@gmail.com> ---
Argh! Lastly, there seems to be quite a bit of lag between creating the
systemtray widget, and being able to reference/modify it's configKeys -
eg, the following code does not actually apply/honour any of the configs I
write, if executed as per below:
===
var panel = new Panel();
var widget = panel.addWidget("org.kde.plasma.systemtray");
var sysTrayId = widget.readConfig("SystrayContainmentId", -1);
if (sysTrayId > 0) {
print(sysTrayId);
var containment = desktopById(sysTrayId);
containment.currentConfigGroup = ["General"];
var showns = [ "org.kde.discovernotifier",
"org.kde.kdeconnect",
"org.kde.plasma.bluetooth" ,
"org.kde.plasma.clipboard" ,
"org.kde.plasma.devicenotifier" ,
"org.kde.plasma.mediacontroller" ,
"org.kde.plasma.networkmanagement" ,
"org.kde.plasma.notifications" ,
"org.kde.plasma.printmanager" ,
"org.kde.plasma.volume"
];
var hiddens = [ "org.kde.plasma.battery" ,
"org.kde.plasma.ktp-contactlist"
];
containment.writeConfig("extraItems", showns);
containment.writeConfig("hiddenItems", hiddens);
}
If instead of creating a new panel, I grab the systray from an existing panel,
it applies fine...
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 378683] org.kde.plasma.systemtray configKeys not accessible via plasma script api
https://bugs.kde.org/show_bug.cgi?id=378683
--- Comment #2 from Bernard Gray <bernard.g...@gmail.com> ---
Hi David,
Thank you so much - that's really helpful!
I've hit one more (hopefully related) snag - so I've got the correct
containment now, I can manipulate the widgets that appear in the systemtray,
but I'm now having difficult setting the [Auto|Hidden|Shown] immutability(?)
configKey on a per widget/applet level.
To clarify, at the SystemTray level the applets can be set to appear or not
appear (this is what you've given me access to already) -
At an applet level, they can be set to Appear in the main tray (Shown), Appear
in the popup dialog when you click on the SystemTray arrow (Hidden), or work it
out for themselves (Auto).
I believe the key for this setting is "immutability", but I can't seem to find
how to access this key now - code snippet:
===
panel = panels()['0'];
for (var j in panel.widgetIds) {
var widget = panel.widgetById(panel.widgetIds[j]);
sysTrayId = widget.readConfig("SystrayContainmentId", -1);
if (sysTrayId > 0) {
var containment = desktopById(sysTrayId);
containment.currentConfigGroup = ["General"];
print(containment.configKeys);
print(containment.widgetIds);
for (var w in containment.widgetIds) {
var cwidget = containment.widgetById(containment.widgetIds[w]);
print(cwidget.type);
print(cwidget.configGroups);
print(cwidget.configKeys);
}
}
}
cwidget.configGroups and cwidget.configKeys are empty - even after manually
setting some different immutability's on various systray widgets - can I be so
bold as to ask for another pointer on how to get into these settings?
Thanks -
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 378683] New: org.kde.plasma.systemtray configKeys not accessible via plasma script api
https://bugs.kde.org/show_bug.cgi?id=378683
Bug ID: 378683
Summary: org.kde.plasma.systemtray configKeys not accessible
via plasma script api
Product: plasmashell
Version: 5.9.4
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: System Tray
Assignee: plasma-b...@kde.org
Reporter: bernard.g...@gmail.com
Target Milestone: 1.0
I'm trying to programmatically customise my corporate desktop environment,
which involves hiding a few systemtray items.
I start up the interactive scripting console as per:
qdbus org.kde.plasmashell /PlasmaShell showInteractiveConsole
My script to interrogate the systemtray widget looks like:
==
panel = panels()['0'];
for (var j in panel.widgetIds) {
var widget = panel.widgetById(panel.widgetIds[j]);
print(widget.configKeys);
if (widget.type == "org.kde.plasma.systemtray") {
print(widget.type);
print(widget.configGroups);
widget.currentConfigGroup = ["General"];
print(widget.currentConfigGroup);
print(widget.configKeys);
}
}
==
This output should contain a bunch of configKeys such as:
* applicationStatusShown
* communicationsShown
* extraItems
* knownItems
* hiddenItems
but I'm not seeing *any*.
I can also writeConfig("$rand_configKey", "some_value"); and it doesn't error,
but it also doesn't change anything.
--
You are receiving this mail because:
You are watching all bug changes.
