[Bug 2056665] Re: systemd-xdg-autostart-generator-ed service does not correctly run script that detaches a subprocess

2024-03-10 Thread Yann Salmon 
** Package changed: ubuntu => systemd (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056665

Title:
  systemd-xdg-autostart-generator-ed service does not correctly run
  script that detaches a subprocess

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2056665/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2056665] [NEW] systemd-xdg-autostart-generator-ed service does not correctly run script that detaches a subprocess

2024-03-10 Thread Yann Salmon 
Public bug reported:

I have a script that basically does

```
#! /usr/bin/bash
sleep 5
thunderbird &
```


and an appropriate desktop file in .~/.config/autostart to run it.

Since upgrading from Plasma 5.24 to 5.27 (from the backports PPA), this
no longer works. The script is run (added logging, eg. with systemd-cat,
prove it) but Thunderbird does not appear. However, it does work if I
change it to the following.

```
#! /usr/bin/bash
sleep 5
thunderbird
```

So I suspect this is related to how systemd-xdg-autostart-generator runs
the associated service. I tried various combinations like ``kstart5
thunderbird & disown``, to no avail.

Note this script is an MWE example ; my actual script is more convoluted
and needs subprocess detachment to work properly.

Plasma 5.24 did not exhibit this behaviour. I do not know if it was
using systemd-xdg-autostart-generator to manage autostart.

Current systemd version is 249.11-0ubuntu3.12, which is too old to
report upstream about.

Operating System: Kubuntu 22.04
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.3
Kernel Version: 5.15.0-100-generic (64-bit)
Graphics Platform: X11

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2056665

Title:
  systemd-xdg-autostart-generator-ed service does not correctly run
  script that detaches a subprocess

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2056665/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880341] [NEW] org.kde.discovernotifier missing

2020-05-23 Thread Yann Salmon 
Public bug reported:

Hello,

upon upgrading from KUbuntu 18.04 to 20.04 and subsequently from plasma-
discover 5.12.8 to 5.18.4.1, I noticed the files in
/usr/share/plasma/plasmoids/org.kde.discovernotifier/ are no longer
present, which causes an update notifier widget to report 'module
"org.kde.discovernotifier" is not installed'.

How can I get this QML module back ? Or is there a replacement ?

** Affects: plasma-discover (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880341

Title:
  org.kde.discovernotifier missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1880341/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811214] Re: plasmashell stops updating when compositing is disabled

2019-01-10 Thread Yann Salmon 
** Bug watch added: KDE Bug Tracking System #361763
   https://bugs.kde.org/show_bug.cgi?id=361763

** Also affects: kde-workspace via
   https://bugs.kde.org/show_bug.cgi?id=361763
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811214

Title:
  plasmashell stops updating when compositing is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-workspace/+bug/1811214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811214] [NEW] plasmashell stops updating when compositing is disabled

2019-01-10 Thread Yann Salmon 
Public bug reported:

I ordinarily run KUbuntu 18.04 with desktop compositing enabled, using
OpenGL 3.1 and this works quite well.

However on some occasions when compositing gets disabled, either because
a game disables it or when I manually disable it in the configuration
panel, Plasmashell's taskbar stops updating and its appearance gets
replaced with an old version.

I can tell because the application taskbar buttons are not correct and
the hour is also not the right one. Reactivating composition restores
normal behaviour. Only the display is affected : even if some
application button is not displayed, I can still click on it if I
remember where it is.

The information displayed during this problem is always the same until I
kill plasmashell and restart it. What is displayed seems to be the state
when plasmashell was last (re)started, or when the computer resumed from
either suspend or hibernation.

** Affects: plasma-workspace (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811214

Title:
  plasmashell stops updating when compositing is disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1811214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1799289] Re: guvcview replaces kde plasmashell display with older one

2018-10-22 Thread Yann Salmon 
** Summary changed:

- gucview replaces kde plasmashell display with older one
+ guvcview replaces kde plasmashell display with older one

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/1799289

Title:
  guvcview replaces kde plasmashell display with older one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guvcview/+bug/1799289/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1799289] [NEW] gucview replaces kde plasmashell display with older one

2018-10-22 Thread Yann Salmon 
Public bug reported:

I started guvcview for the first time since I switched from Xubuntu to
Kubuntu.

guvcview seems to replace the plasmashell display with the appearance it
had when I logged back into my session after resuming from suspend !

The screen capture shows it : the taskbar displays the tasks that were
opened at that time, the notification icons (with activity on the
network icon because it is reconnecting after resuming from suspend) and
of course the time (which if more the 2 hours in the past).

None of these elements are animated (notably not the clock). Clicking on
them does have the usual behaviour, except for tasks where the
"present/actual" task button do not correspond to the display.

Alt-tab also works normally (displaying the actual tasks, including
guvcview).

guvcview seem to work normally, except that the video feed from the
camera sometimes visibly misses a frame. Other application also work.

When I close guvcview, the taskbar is again correctly displayed.

The phenomenon happens each time I open guvcview.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: guvcview 2.0.5+debian-1
Uname: Linux 4.17.14-041714-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Oct 22 21:57:32 2018
InstallationDate: Installed on 2016-09-07 (775 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: guvcview
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: guvcview (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: plasma-workspace (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

** Attachment added: "Screenshot_20181022_215629.png"
   
https://bugs.launchpad.net/bugs/1799289/+attachment/5204300/+files/Screenshot_20181022_215629.png

** Also affects: plasma-workspace (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799289

Title:
  gucview replaces kde plasmashell display with older one

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/guvcview/+bug/1799289/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1790777] [NEW] Performance hit after hibernation (lag) [nvidia driver]

2018-09-05 Thread Yann Salmon 
Public bug reported:

The interface to select a rectangular region for screen capture is laggy
after there has been an hibernation cycle (it is not otherwise) : the
rectangle follows the mouse cursor with a very noticeable delay that
makes it difficult to use.

Furthermore this may be the most visible sign of a more general
performance hit.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-spectacle 17.12.3-0ubuntu1
Uname: Linux 4.17.14-041714-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Sep  5 07:43:18 2018
InstallationDate: Installed on 2016-09-07 (727 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: kde-spectacle
UpgradeStatus: Upgraded to bionic on 2018-07-01 (65 days ago)

** Affects: kde-spectacle (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790777

Title:
  Performance hit after hibernation (lag) [nvidia driver]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-spectacle/+bug/1790777/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783954] Re: [NVIDIA] GPU lockup (screen freeze) after resume from hibernation / suspend

2018-08-13 Thread Yann Salmon 
I do not have access to that computer right now.

But the same problem appeared today with my laptop, which is also
running KUbuntu 18.04 with an NVIDIA card (Geforce 840M) and with driver
390.77.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783954

Title:
  [NVIDIA] GPU lockup (screen freeze) after resume from hibernation /
  suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1783954/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1785761] Re: Wrong driver shown as active; Selecting proprietary driver seems to have no effect

2018-08-07 Thread Yann Salmon 
I managed to activate NVIDIA driver instead of nouveau by adding
"blacklist=nouveau rdblacklist=nouveau" to my kernel parameters.

But KDE Driver Manager still claims that nouveau is in use, when it is
not the case :

compare kcmshell5 kcm_driver_manager

Dev(
  id: "/sys/devices/pci:00/:00:01.0/:01:00.0"
  modalias: "pci:v10DEd13BBsv10DEsd1098bc03sc00i00"
  model: "GM107GL [Quadro K620]"
  vendor: "NVIDIA Corporation"
  driver("nvidia-340" recommended[false] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("nvidia-driver-390" recommended[false] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("nvidia-driver-396" recommended[true] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("xserver-xorg-video-nouveau" recommended[false] free[true] 
fromDistro[true] builtin[true] manualInstall[false] fuzzyActive[false] 
package[0x0])
)


with /var/log/gpu-manager.log : 
…
Is nvidia loaded? yes
Was nvidia unloaded? no
Is nvidia blacklisted? no
Is intel loaded? yes
Is radeon loaded? no
Is radeon blacklisted? no
Is amdgpu loaded? no
Is amdgpu blacklisted? no
Is amdgpu versioned? no
Is amdgpu pro stack? no
Is nouveau loaded? no
Is nouveau blacklisted? yes
Is nvidia kernel module available? yes
Is amdgpu kernel module available? no
Vendor/Device Id: 8086:191d
BusID "PCI:0@0:2:0"
Is boot vga? no
Vendor/Device Id: 10de:13bb
BusID "PCI:1@0:0:0"
Is boot vga? yes
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card0", driven by "nvidia-drm"
Skipping "/dev/dri/card1", driven by "i915"
Skipping "/dev/dri/card0", driven by "nvidia-drm"


** Summary changed:

- Selecting proprietary driver seems to have no effect
+ Wrong driver shown as active; Selecting proprietary driver seems to have no 
effect

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785761

Title:
  Wrong driver shown as active; Selecting proprietary driver seems to
  have no effect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1785761/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1785761] [NEW] Selecting proprietary driver seems to have no effect

2018-08-07 Thread Yann Salmon 
Public bug reported:

I am trying to activate nvidia-driver-390 for my graphics card instead
of nouveau. The graphical interface of the Driver Manager detects my GPU
and the available drivers but selecting nvidia-driver-390 seems to have
no effect (the packages have already been installed but nouveau is still
used).

Running kcmshell5 kcm_driver_manager in the console enabled me to get
the following messages. Usage was to select nvidia-driver-390 and click
Apply.


QDBusArgument& operator<<(QDBusArgument&, const DeviceList&) is noop
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
const QDBusArgument& operator>>(const QDBusArgument&, DeviceList&)
Dev(
  id: "/sys/devices/pci:00/:00:01.0/:01:00.0"
  modalias: "pci:v10DEd13BBsv10DEsd1098bc03sc00i00"
  model: "GM107GL [Quadro K620]"
  vendor: "NVIDIA Corporation"
  driver("nvidia-driver-396" recommended[true] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("nvidia-driver-390" recommended[false] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("nvidia-340" recommended[false] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("xserver-xorg-video-nouveau" recommended[false] free[true] 
fromDistro[true] builtin[true] manualInstall[false] fuzzyActive[false] 
package[0x0])
)
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
not reporting "xserver-xorg-video-nouveau" because it is builtin
("nvidia-driver-390") ("nvidia-340", "nvidia-driver-396")
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
const QDBusArgument& operator>>(const QDBusArgument&, DeviceList&)
Dev(
  id: "/sys/devices/pci:00/:00:01.0/:01:00.0"
  modalias: "pci:v10DEd13BBsv10DEsd1098bc03sc00i00"
  model: "GM107GL [Quadro K620]"
  vendor: "NVIDIA Corporation"
  driver("nvidia-driver-396" recommended[true] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("nvidia-driver-390" recommended[false] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("nvidia-340" recommended[false] free[true] fromDistro[false] 
builtin[false] manualInstall[false] fuzzyActive[false] package[0x0])
  driver("xserver-xorg-video-nouveau" recommended[false] free[true] 
fromDistro[true] builtin[true] manualInstall[false] fuzzyActive[false] 
package[0x0])
)
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded
kf5.kwidgetsaddons: No frame loaded

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kubuntu-driver-manager 15.10ubuntu4
Uname: Linux 4.17.0-996-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: KDE
Date: Tue Aug  7 09:32:36 2018
InstallationDate: Installed on 2016-09-07 (698 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: kubuntu-driver-manager
UpgradeStatus: Upgraded to bionic on 2018-07-01 (36 days ago)

** Affects: kubuntu-driver-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785761

Title:
  Selecting proprietary driver seems to have no effect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1785761/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs