[plasmashell] [Bug 470983] After update from plasma5 2.24.4 to 5.27.4, when not using Systemd boot, scripts executed in terminals cannot change directory

[davejplater]

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

davejpla...@gmail.com  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #13 from davejpla...@gmail.com  ---
Info for needinfo in comment 11

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

[plasmashell] [Bug 470983] After update from plasma5 2.24.4 to 5.27.4, when not using Systemd boot, scripts executed in terminals cannot change directory

[davejplater]

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

--- Comment #11 from davejpla...@gmail.com  ---
(In reply to Nate Graham from comment #10)
> Probably something about the environment variables set during plasmashell's
> startup is triggering this. Can you try to figure out which environment
> variable is the cause?

I'm not really sure how systemd actually affects the shell to cause this, seems
like a security measure to prevent malicious scripts from executing. I compared
the output of "set" between the non systemd startup and the systemd startup and
searched through kernel settings but I couldn't  find anything.

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

[kwin] [Bug 470983] After update from plasma5 2.24.4 to 5.27.4, when not using Systemd boot, scripts executed in virtual consoles cannot change directory

[davejplater]

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

--- Comment #9 from davejpla...@gmail.com  ---
(In reply to Nate Graham from comment #8)
> Actually, let me ask for clarification on something. Are you using virtual
> terminals for this? Or are you just running `mc` in a regular terminal app
> like Konsole?

I experience this bug in any terminal app running under kde. I use konsole
exclusively but it happens in xterm or any other terminal app. It doesn't
happen in xfce or icewm or a virtual console, it only happens under kde and the
change in behavior causes scripts executed in the terminal app to be restricted
to a private shell and this causes the mc shell script to fail. Another
consequence is:
 https://bugzilla.suse.com/show_bug.cgi?id=1213156

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

[plasmashell] [Bug 470983] on update from plasma5 2.24.4 to 5.27.4 scripts executed in virtual consoles cannot change directory.

[davejplater]

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

--- Comment #6 from davejpla...@gmail.com  ---
(In reply to Nate Graham from comment #5)
> I'm afraid KDE doesn't have any control over the console behavior in VTs, so
> this issue will have been caused by something somewhere else. I'm pretty
> sure what happened is that with the newer Plasma version, we switched to
> Systemd boot by default, and you're running into a change in behavior coming
> from Systemd. So you have two options:
> - Disable the systemd boot with `kwriteconfig5 --file startkderc --group
> General --key systemdBoot false`
> - Follow up with the Systemd folks about it

I use systemdBoot false` in startkderc

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

[plasmashell] [Bug 470983] on update from plasma5 2.24.4 to 5.27.4 scripts executed in virtual consoles cannot change directory.

[davejplater]

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

--- Comment #4 from davejpla...@gmail.com  ---
It appears that this bug appeared after plasma 5.26.
See also:
https://bugzilla.suse.com/show_bug.cgi?id=1213156
https://bugs.kde.org/show_bug.cgi?id=433299

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

[plasmashell] [Bug 470983] on update from plasma5 2.24.4 to 5.27.4 scripts executed in virtual consoles cannot change directory.

[davejplater]

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

davejpla...@gmail.com  changed:

   What|Removed |Added

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

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

[plasmashell] [Bug 470983] on update from plasma5 2.24.4 to 5.27.4 scripts executed in virtual consoles cannot change directory.

[davejplater]

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

--- Comment #2 from davejpla...@gmail.com  ---
Sorry, I would like to know the commit's hash.

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

[plasmashell] [Bug 470983] on update from plasma5 2.24.4 to 5.27.4 scripts executed in virtual consoles cannot change directory.

[davejplater]

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

davejpla...@gmail.com  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
Summary|on update from plasma5  |on update from plasma5
   |2.24.4 to 5.27.4 midnight   |2.24.4 to 5.27.4 scripts
   |commander no longer exits   |executed in virtual
   |to it's current directory   |consoles cannot change
   ||directory.
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from davejpla...@gmail.com  ---
I've updated the title to reflect the true problem that scripts such as:
#! /usr/bin/bash

  dirc()
  {
  pushd ../../
  }

  dirc

don't work in kde anymore ie. the above script does nothing unless it is
prepended with the bash builtin "." which forces the script to execute in the
current shell. This wasn't the case in version 5.24.4 but is now the case in
5.27.4

If this behavior has been introduced as a security feature, I would appreciate
knowing when and why.

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

[plasmashell] [Bug 470983] New: on update from plasma5 2.24.4 to 5.27.4 midnight commander no longer exits to it's current directory

[davejplater]

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

Bug ID: 470983
   Summary: on update from plasma5 2.24.4 to 5.27.4 midnight
commander no longer exits to it's current directory
Classification: Plasma
   Product: plasmashell
   Version: 5.27.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Startup process
  Assignee: plasma-b...@kde.org
  Reporter: pla...@opensuse.org
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

See https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/569 for a
similar problem
See https://bugzilla.suse.com/show_bug.cgi?id=1203617

STEPS TO REPRODUCE
1. Upgrade plasma5 to 5.27.4
2. Attempt to use mc (midnight commander) to navigate to a directory
3. 

OBSERVED RESULT
On exiting mc you go back to the directory that you started from

EXPECTED RESULT
On exiting mc you are in the directory that you navigated to

SOFTWARE/OS VERSIONS
Operating System: openSUSE Leap 15.5
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.14.21-150500.53-default (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz
Memory: 7,6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 4600
Manufacturer: MSI
Product Name: MS-7851
System Version: 2.0

ADDITIONAL INFORMATION
Midnight Commander is a valuable command line tool but if it exits into it's
starting directory it becomes just another file manager. This issue was a major
blocker for me until a workaround was found.

This behavior doesn't happen in any other GUI than KDE, tested on icewm and
xfce.

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

[k3b] [Bug 382754] K3b complains about missing cdrskin at start up

[davejplater]

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

davejpla...@gmail.com  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|REOPENED|RESOLVED

--- Comment #26 from davejpla...@gmail.com  ---
This bug has disappeared with time

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

[davejplater]

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

--- Comment #55 from davejpla...@gmail.com  ---
I've built it in openSUSE's obs and installed it on my Leap:15.1 box happy to
say it works fine apart from not having KDirModel yet.

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

[davejplater]

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

--- Comment #54 from davejpla...@gmail.com  ---
Got it, in master 430c4c9f411cd1c6da436745512974c65bdf686e we have:
Don't find KHTML

Summary: It isn't linked any more

Reviewers: #konqueror, dfaure, vkrause

Reviewed By: #konqueror, dfaure, vkrause

Subscribers: vkrause

Maniphest Tasks: T11543

Differential Revision: https://phabricator.kde.org/D26471

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

[davejplater]

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

--- Comment #53 from davejpla...@gmail.com  ---
/insaner/konqueror master can't find khtml for some reason but one commit back:
919437c532a7ed79f85427356110b158a58b8b85 has built successfully using a barely
modified konqueror.spec from openSUSE:Tumbleweed/konqueror. I still have to add
all the sidebar parts to the package and hopefully it works.

See https://build.opensuse.org/package/show/home:plater/konqueror
If it works I'll submit it to KDE:Extra

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

[konqueror] [Bug 373824] Konqueror 16.12 is missing the sidebar

[davejplater]

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

davejpla...@gmail.com  changed:

   What|Removed |Added

 CC||pla...@opensuse.org

--- Comment #33 from davejpla...@gmail.com  ---
I'm also someone who was very disappointed when the sidebar disappeared from
konqueror. I also don't like dolphin and my most used file manager is Midnight
Commander. If I require a file manager gui I use konqueror and it's a fantastic
man and info page browser and (don't know what was called) the services browser
in the sidebar was also useful. I mainly used the file tree part of the sidebar
it gives flexibility when choosing directories but I cope without it.
I've removed dolphin file manager from the start menu and replaced it with
konqueror  --open-session fmngr since dolphin's appearance as the default. I
also managed to import all the kde4 konqueror bookmarks etc when it switched to
kf5, would have been nice to have had instructions.
+1 to konqueror being a first class file manager with network capabilities.

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

[k3b] [Bug 382754] K3b complains about missing cdrskin at start up

[davejplater]

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

--- Comment #14 from davejpla...@gmail.com  ---
Just to shed a bit of light. openSUSE worked with Jörg Schilling to have
cdrecord/cdrtools in the distribution in 2013 due to numerous bugs with
wodim/cdrkit-cdrtools-compat particularly with k3b. It has been a part of the
distribution since 13.2 2013-12-04 and has performed very well since then but
it has been installed from alternate repositories many years prior due to wodim
problems.
@Leslie Zhai you can understand our concerns about changing something that is
proven for something that is new.

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

[k3b] [Bug 382754] K3b complains about missing cdrskin at start up

[davejplater]

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

--- Comment #5 from davejpla...@gmail.com  ---
Next question, which version of libburn/cdrskin is stable. Ironically I tried
to submit the latest libburn to Leap:42.3 just before freeze last month and it
wasn't considered necessary. I maintain multimedia and not kde so I didn't have
a clue about this then.

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

[k3b] [Bug 382754] K3b complains about missing cdrskin at start up

[davejplater]

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

--- Comment #2 from davejpla...@gmail.com  ---
(In reply to Leslie Zhai from comment #1)
> > Forcing unsuspecting users to use a development alternative to cdrecord 
> > which works fine for years.
> 
> Really? I argue that
> https://lists.debian.org/debian-devel-announce/2006/09/msg2.html so
> please remove wodim (forked cdrecord) from cdrkit (CD only, DVD deprecated,
> unmaintained), website was down, release tarball is NOT available, svn repos
> is so quiet! But install cdrtools A.K.A cdrecord instead.
> http://www.leetcode.cn/2016/08/k3b.html#bug

We've had cdrtools a.k.a. cdrecord in openSUSE for a few years and had no
problems, I can understand the problem with distributions that don't want to
use schilly's program but it's well maintained and it works.
openSUSE:Leap:42.3 is supposed to be a stable lts release and it appears that
cdrskin is still in development. There should be a switch to disable this
message for those who wish to use cdrecord.
My question is will k3b still function as expected without cdrskin or do we
have to require cdrskin? I don't see anything relating to cdrskin in
CMakeLists,txt.
See also https://bugzilla.suse.com/show_bug.cgi?id=1050715

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

[k3b] [Bug 382754] New: K3b complains about missing cdrskin at start up

[davejplater]

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

Bug ID: 382754
   Summary: K3b complains about missing cdrskin at start up
   Product: k3b
   Version: 17.04.3
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: GUI/Usability
  Assignee: k...@kde.org
  Reporter: pla...@opensuse.org
CC: mich...@jabster.pl, tr...@kde.org
  Target Milestone: ---

See  Bug 137436
On start up k3b gives this message:
Unable to find cdrskin executable
K3b uses cdrskin in place of cdrecord.
Solution: Install the libburn package which contains cdrskin
Forcing unsuspecting users to use a development alternative to cdrecord which
works fine for years.

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

[konsole] [Bug 381400] Using plasma5 and booting into a saved session konsole doesn't start if session saved with now nonexistent usb drive.

[davejplater]

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

--- Comment #4 from davejpla...@gmail.com  ---
It seems that this fix wasn't backported to Leap:42.2 and has now been
rectified.
https://bugzilla.opensuse.org/show_bug.cgi?id=1045914
Thanks for your help.

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

[konsole] [Bug 381400] Using plasma5 and booting into a saved session konsole doesn't start if session saved with now nonexistent usb drive.

[davejplater]

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

--- Comment #2 from davejpla...@gmail.com  ---
This is fixed in 17.04.2, is there a patch available for 16.08.02 or is it
fixed in a later 16.08 version? I'll file am openSUSE bug to force an update.
Going to try the official openSUSE:Leap:42.2 version again.
The directory entry in
~/.config/session/konsole_10149dad0e400014870799260017800011_1498456552_181102
is:

WorkingDir[$e]=/run/media/davepl/DAVEWDE/vending/cypress/FX3_SDK/cyusb_linux_1.0.4

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

[konsole] [Bug 381400] New: Using plasma5 and booting into a saved session konsole doesn't start if session saved with now nonexistent usb drive.

[davejplater]

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

Bug ID: 381400
   Summary: Using plasma5 and booting into a saved session konsole
doesn't start if session saved with now nonexistent
usb drive.
   Product: konsole
   Version: 16.08.2
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: pla...@opensuse.org
  Target Milestone: ---

I manually save my plasma5 sessions from time to time. If I had a removable
drive open in one of my konsole tabs when I save the session then konsole
refuses to start on the next boot. If I then plug in and mount a usb drive and
it's mounted by plasma5 with the same drive descriptor and log out and log in
then the saved konsole will start. If I start xterm and start konsole from
there, I can get a new konsole instance. I can't find any error messages
konsole just silently refuses to start.

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