[Bug 1898493] Re: /dev/dri/card0 not closed when plasmashell forks

2024-04-03 Thread Keith Owens
Retested on plasma-workspace 4:5.24.7-0ubuntu0.1. xterm no longer
inherits /dev/dri/card0. Close the bug.

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

Title:
  /dev/dri/card0 not closed when plasmashell forks

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


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

[Bug 1898493] [NEW] /dev/dri/card0 not closed when plasmashell forks

2020-10-04 Thread Keith Owens
Public bug reported:

plasmashell forks xterm. xterm inherits /dev/dri/card0 open on fd 15.
Working as designed? Or forgot to close it/mark it as CLOEXEC?

# lsof -p 2624 | grep /dev/dri
plasmashe 2624 kaos   12u  CHR  226,0  0t0347 
/dev/dri/card0
plasmashe 2624 kaos   13u  CHR  226,0  0t0347 
/dev/dri/card0
plasmashe 2624 kaos   14u  CHR  226,0  0t0347 
/dev/dri/card0
plasmashe 2624 kaos   15u  CHR  226,0  0t0347 
/dev/dri/card0

xterm child on pid 3659

# lsof -p 3659 | grep /dev/dri
xterm   3659 kaos   15u   CHR  226,0  0t0  347 
/dev/dri/card0

strace 2624 shows no close for fd 12, 13, 14 but they are not inherited
by 3659. So they are probably marked CLOEXEC. But fd 15 is left open and
is inherited by all children of plasmashell.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: plasma-workspace 4:5.18.5-0ubuntu0.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Oct  5 12:24:05 2020
InstallationDate: Installed on 2017-07-12 (1180 days ago)
InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
SourcePackage: plasma-workspace
UpgradeStatus: Upgraded to focal on 2020-06-21 (105 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  /dev/dri/card0 not closed when plasmashell forks

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

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

[Bug 909171] Re: firefox 9 statusbar url popup is unusable with dark grey text on black background

2016-01-16 Thread Keith Owens
One possible cause is a conflict between the KDE theme and GTK. I had
the same problem because ~/.kde/env contained a file gtk2-engines-
qtcurve.rc.sh with

export GTK2_RC_FILES=$HOME/.gtkrc-2.0-kde4

Commenting out the export, logging out and in again fixed the dark grey
on black problem for alternate text.

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

Title:
  firefox 9 statusbar url popup is unusable with dark grey text on black
  background

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

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


[Bug 788998] [NEW] winbind hang after 10 hours, Kerberos and DNS related

2011-05-27 Thread Keith Owens
Public bug reported:

Binary package hint: samba

Ubuntu 10.04 (Samba2:3.4.7~dfsg-1ubuntu3.6) , Ubuntu 10.10. (Samba
2:3.5.4~dfsg-1ubuntu8.4)

Winbind is using a Windows active directory. /etc/resolv.conf is
pointing at a Linux based DNS which "replicates" data from the Windows
DC.

Problem:

winbind starts up, issues DNS requests, is happy with its responses.

winbind gets its Kerberos token [see below for a related problem].

Everything is happy for 10 hours (Kerberos token lifetime).

The Kerberos token expires.

winbind starts issuing DNS requests to the same Linux server to find the
Kerberos server. It gets responses but this time it is not happy with
the contents.

After a few tries at getting the DNS response, winbind gives up on DNS
and drops through to LMHOSTS (nothing there) and finally SMB broadcast
mode.

The winbind client is on a different network from the Windows DC, so
broadcast gets no response.

winbind stalls issuing broadcast packets but not doing any work
(Kerberos has expired).

winbind still accepts client connections over its pipe, each of which
gets allocated a file descriptor. Its clients all stall, waiting for a
response from winbind.

Eventually winbind runs out of file descriptors and dies.

If winbind needs to open a new log file it cannot, all file descriptors
are in use.

Everything grinds to a halt waiting for a response from winbind, until
winbind is restarted.

Workaround:

Point /etc/resolv.conf at the Windows DC instead of the Linux name
server.

Outstanding:

Why does winbind accept the DNS responses at start up but not when
Kerberos expires?

winbind needs to reserve a couple of file descriptors for its log files.
Losing the log file in the middle of this problem was "interesting".

winbind constructs its own krb5.conf, removing all the local settings
that are set in /etc/krb5.conf. This results in the main winbind process
using values from /etc/krb5.conf, while the remaining processes use
potentially different values from its own krb5.conf. Trying to test
workarounds was frustrating because dropping the key lifetime in
/etc/krb5.conf had no effect. In the end I used a syscall wrapper around
rename to intercept and replace the contents of winbind's copy of
krb5.conf. As I say, it was "interesting".

** Affects: samba (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/788998

Title:
  winbind hang after 10 hours, Kerberos and DNS related

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


[Bug 222239] Re: acpid upgrade fails on non-standard kernel

2008-04-25 Thread Keith Owens

** Attachment added: "Dependencies.txt"
   http://launchpadlibrarian.net/13914323/Dependencies.txt

-- 
acpid upgrade fails on non-standard kernel
https://bugs.launchpad.net/bugs/39
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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


[Bug 222239] [NEW] acpid upgrade fails on non-standard kernel

2008-04-25 Thread Keith Owens
Public bug reported:

Binary package hint: acpid

Upgrading kubuntu from gibbon to heron. I forgot that I was running a
non-standard kernel when I started the upgrade. acpid post processing
failed because /proc/sys/events did not exist on the non-standard
kernel. Not that big a deal (fix: upgrade using the right kernel), but
you might want to check for the existence of that file instead of just
failing.

ProblemType: Package
Architecture: i386
Date: Sat Apr 26 09:08:20 2008
DistroRelease: Ubuntu 8.04
ErrorMessage:
 ErrorMessage: subprocess post-installation script returned error exit status 1
Package: acpid 1.0.4-5ubuntu9
PackageArchitecture: i386
SourcePackage: acpid
Title: package acpid 1.0.4-5ubuntu9 failed to install/upgrade: 
Uname: Linux 2.6.24-kaos i686

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


** Tags: apport-package

-- 
acpid upgrade fails on non-standard kernel
https://bugs.launchpad.net/bugs/39
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

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