Public bug reported:
In some cases the kernel does detect a newly connected USB device, but
this device is never handled by systemd. The device handling shows up in
dmesg, but no device /dev/sd.. entries are created to access this newly
connected storage device.
ProblemType: Bug
DistroRelease: Ub
Public bug reported:
assume /etc/apt/sources.list.d/somerepo.list:
Types: deb
URIs: https://repo.vivaldi.com/stable/deb/
Suites: stable
Components: main
Architectures: amd64
Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg
/etc/apt/trusted.gpg.d/4218647E.gpg
Then 'apt update' will produce:
# ap
# pcscd --foreground --info --color
debuglog.c:386:DebugLogSetLevel() debug level=info
0040 pcscdaemon.c:356:main() Force colored logs
0381 pcscdaemon.c:666:main() pcsc-lite 1.9.9 daemon ready.
00013684 hotplug_libudev.c:421:HPAddDevice() Adding USB device: REINER SCT
cyberJack wa
Public bug reported:
pcscd starts, then all readers connected are listed, but wont work.
starting pcsc_scan will never finish scanning, waiting on pcscd
returning data.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: pcscd 1.9.9-1ubuntu0.23.04.1
ProcVersionSignature: Ubuntu 6.2.0-39.40-gen
Public bug reported:
unattended-upgrades if enabled wont disable interactive mode. In tune an
unattended upgrade stops waiting for input never to expect, because the dialog
displayed is never seen by anyone.
Updates will not be installed at all in some cases.
ProblemType: Bug
DistroRelease: Ubu
This can be seen with
- 16.04
- 18.04
- 20.04
- 21.10
- 22.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1968028
Title:
unattended-upgrades if enabled wont
Public bug reported:
Paired Bluetooth devices are connected, then disconnected, connected
again, then finally disconected.
This is with
- Ubuntu, xUbuntu 21.10
- Ubuntu, xUbuntu 22.04(beta)
It works with
- kali (latest)
- debian 11.3 (latest)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package
Public bug reported:
Bluetooth devices do not connect. Or better: they connect, disconnect,
connect, then finally disconnect.
It is the same using graphical tools or cli.
It is the same for
- ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta)
- debian 11.3
- fedora 35
Solved upstream with later versions of cups
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1856187
Title:
Cups wont print to smb-shared printer requiring user authentication
Solved upstream with later versions of cups.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1852474
Title:
cups not printing if authentication required by server
Status in c
Solved with a later version of required packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1915707
Title:
keyboard settings not applied
Status in console-setup
Solved by a later version of systemd and sshd.
To have it work as intended sshd has to be compiled with different options set.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/
Solved by a new version of upgrade tools.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1968028
Title:
unattended-upgrades if enabled wont disable interactive
Meanwhile even the distros working until yesterday stopped working today
(5. May 2022 around 22:00).
The bug seems related to pipewire and switching to this new infrastructure.
It breaks nearly everything related with sound and bluetooth.
Modules involved:
- pipewire-pulse
- wireplumber
--
You
These modules seem to collide with pipewire-media-session, but are
required by bluez-stack to connect bluetooth headsets (or other devices)
to pulseaudio.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https:
xubuntu and kubuntu, as lubuntu do use pipewire for audio.
kali switched last night to use it.
openSUSE did so too.
i did not test on a plain vanilla gnome based ubuntu until now. Will do
it later this day (if time permits).
--
You received this bug notification because you are a member of Ubunt
I can't reproduce this issue on impish or jammy. It was fixed by a
change in handling sockets in systemd.
On Mon, May 9, 2022 at 6:25 PM Paride Legovini
<1957...@bugs.launchpad.net> wrote:
>
> Hello Thomas. You filed this bug against:
>
> DistroRelease: Ubuntu 21.10
> Package: openssh-server 1
Public bug reported:
openssh-server tries to restart itself, but openssh-server reports port
22 in use. This is true: systemd has taken port 22 to start sshd if one
connects to port 22.
two solutions:
1. dont start sshd after installing.
configure it without starting it afterwards.
2. stop sys
Start-Date: 2022-02-21 01:16:18
Commandline: apt -y upgrade
Requested-By: tps (1000)
Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1,
97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3,
2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1),
libctf-nobfd0:amd64
Public bug reported:
bluetooth connects with headset, then times out, deconnects.
Forcing it to connect again it does, then times out and deconnects again.
Seen this with:
- Cyber jack
- Phonak Hearing Aids
- Sennheiser Headset
Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00.
Public bug reported:
Hotplugging devices into USB 3.0/1/2 Ports does not create devices in
/dev. The plugged device is not accessible afterwards. This is for all
of them: USB-Disks (HD, CDROM, Tapes), USB to serial converters, Audio,
Video, Cameras.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Pa
sshd is started by systemd. No special configurations besides defaults
by Ubuntu/xUbuntu. Only change in /etc/ssh/sshd_config: "PermitRootLogin
prohibit-password" -> "PermitRootLogin yes"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Public bug reported:
Global keyboard settings are set in /etc/defaults/keyboard:
XKBMODEL="pc105"
XKBLAYOUT="de"
XKBVARIANT=""
XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp"
BACKSPACE="guess"
These settings are not active any more after upgrading from focal to groovy.
Same ap
Public bug reported:
systemd-resolved will, unter certain circumstances create local only DNS
resolution:
# host google.com
;; connection timed out; no servers could be reached
looking at what is going on behind:
# cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf)
nameserver 127.0.0
Public bug reported:
dnsmasq ist set up to resolve DNS names with a local, static file given at
/etc/dnsmasq-resolv.conf:
# cat /etc/dnsmasq-resolv.conf
nameserver 10.161.18.34
nameserver 10.177.18.34
nameserver 10.129.90.10
nameserver 10.160.90.10
nameserver 10.161.90.10
search
All servers g
Public bug reported:
Ubuntu creates /etc/environment and directory /etc/environment.d.
pam_env.so only reads /etc/environment, but not recursively
/etc/environment.d/
You'll have to add any files created within /etc/environment.d/ as an
additional line to your pam_env.so pam configuration. This
Public bug reported:
login:
password:
Just do nothing. About two seconds later ...
login:
password:
login:
password:
login:
password:
After this being displayed three times:
"Too many failure" or so and login is restarting.
You cant login at all. Only solution: clear the password for the
Setting the password again you'll have a login, but you cant type in
your password. After typing your login name followed by RETURN password
is immediately left. Looks like the entered RETURN is kept and all
subsequent calls see RETURN and just quit.
--
You received this bug notification because
Public bug reported:
Latest network-manager, systemd, kernel-updates killed ethernet
networking. It is impossible to have an address assigned.
I can make sure hardware is ok, by booting into SystemRescueCD. Ethernet
immediately is up and working. As soon as I boot into Ubuntu 18.10
networking wit
Public bug reported:
Since upgrading to openssh 7.2p2-4ubuntu2.7 it is impossible to login
remote. It does not matter what password is set, if you are root or not.
Login fails in all cases.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ssh (not installed)
ProcVersionSignature: Ubuntu 4.4.
This might be related to dhcp configuration not korrektly interpreted:
the dhcp-servers address is taken for the client address, which leads to
duplicate addresses:
dhcp-server: 172.18.8.186
dhcp-response: 172.18.8.111
clients takes 172.18.8.186 for his address instead of 172.18.8.111
--
You re
Older kernels do not matter. Same effect. Cant login remote. If I use
an older sshd it works. If I use a self compiled sshd (same version)
it works.
On Mon, Feb 18, 2019 at 9:00 AM Thomas Schweikle
<1816...@bugs.launchpad.net> wrote:
>
> This might be related to dhcp configuration n
Public bug reported:
resolv.conf holds after boot:
nameserver 127.0.0.53
options edns0
[...]
Trying to resolve google.com just leads to nothing. Same for any address you
try to resolve. Systemd just does not forward to the given resolver address in
/etc/systemd/resolved.conf:
[Resolve]
DNS=172.
Public bug reported:
cups does not print if servers require authenticated users to print. No
login-dialog is shown. Print jobs are on hold, waiting for
legitimization. But no legitimization dialog will be shown.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersio
Same for Ubuntu 19.10 with cups 2.2.12
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/788167
Title:
CUPS cannot print to Kerberos-authenticated SMB print queue
Status in cup
Public bug reported:
In /etc/systemd/resolved.conf I've entered the nameserver to use:
[Resolve]
DNS=172.18.8.1
#FallbackDNS=
Domains=fritz.box
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes
#ReadEtcHosts=yes
In /etc/resolv.conf after rebooting:
nameserver 12
Public bug reported:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFile
** Attachment added: "faulty /var/lib/dpkg/status"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+attachment/5309330/+files/status
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.la
Public bug reported:
Setup:
- Print server part of an AD domain. Print server requires authentication.
- Ubuntu client with cups-server. The client is part of the AD domain. The
client does not share printers (and never will).
- User authenticated by AD within the AD domain.
- Now user wants to p
Public bug reported:
Trying to delete a printer will fill up the filesystem with log messages ala
localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156
CUPS-Delete-Printer successful-ok
localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156
CUPS-Delete-Pr
Same for adding a new printer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1856189
Title:
Trying to delete a printer will fill up the filesystem with
logmessages
Status
Same for any page with any printer. CUPS seems to run an endless loop
exausting it has done ok. But nothing done at all. Just looping.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/
The loop isn't within cups, but within js running within the browser. Noting
this I tried to switch to an other browser to get rid of this loop. But without
success: any of the tested ones leads to this loop:
- Firefox (stable, esr, nightly)
- Chrome (stable, beta, unstable, waterfall)
- Chromium
Public bug reported:
If at least one printer is set to "AuthInfoRequested negotiate" this
will be taken for all printers, even if these have set
"AuthInfoRequested none".
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.
Public bug reported:
If a printer is set to "AuthInfoRequested negotiate" cups will ask for
password for user "negotiate" instead to exaust an error because
"negotiate" isn't a keyword.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-2
Public bug reported:
Since latest updates lightdm does not start any desktop environment.
After loging in a blank screen (if you had set a desktop background the
desktop background) is shown. No window manager, no session manager gets
started.
To start a desktop environment you'll have to switch
The boot space problem is not resolved by purge-old-kernels, since this
command does not remove old initrd from kernels not installed any more.
purge-old-kernels shall remove any initrd from kernels it removes!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
"systemd-resolve --status" reports "Failed to get global data: Unit
dbus-org.freedesktop.resolve1.service not found."
-> resolv.conf only holds two lines:
--- snip
nameserver 127.0.0.1
--- snap
and "host google.com" leads to
Host google.com not found: 5(REFUSED)
dnsmasq is
Public bug reported:
After upgrading lightdm does not have a config any more:
cat: /etc/lightdm/lightdm.conf: Datei oder Verzeichnis nicht gefunden
In tune it does not start ...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-137.
Public bug reported:
Cups tells changing a printer the user would have to authenticate with
username and password, but never asks for username and password in tune
cups denys access to printer configurations and no changes are possible
using the web interface.
ProblemType: Bug
DistroRelease: Ubun
Public bug reported:
Any printing attempt to any printer is quitted with "filter failed" by
cups. Even for test pages.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
Uname: Linux 4.15.0-37-generic x86_64
Apport
Public bug reported:
lightdm tries to initialize screen output, fails, tries again, fails
until the backlight electronics break, killing the monitor.
lightdm fails initializing screen. This turns on backlight, initializes
graphics, then lightdm stops with an error message. systemd starts
lightdm
Same problem: it does not matter if upgraded from 18.04 or installed new
with 18.10. lightdm might not allways be capable initializing graphics
leeding to some loop together with systemd turning on backlight, turning
it off again, then restarting.
Backlight is turned on, then off about twice a sec
This bug exists since 16.10 – we are at 18.10 now it is now two years
with this monitor killing bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1801533
Title:
lightdm
This schouldn't happen. lightdm should only be started about 10 times,
then disabled.
BTW: no errors are readable on screen. Logs only show lightdm restarted
by systemd after terminatating. Errors can be seen by disabling lightdm,
then starting it from commandline. But this isn't helpful either: "
Public bug reported:
Ubuntu 18.10 does not recognize sound devices. After upgrading there is
only a dummy device known. All others are gone. In tune there is no
sound output to nowhere.
It does not mater it headphones are plugged or not while booting. It
does not matter if any usb-sound device is
*** This bug is a duplicate of bug 210472 ***
https://bugs.launchpad.net/bugs/210472
Yes, that is it!
systemctl stop timidity.service
systemctl disable timidity.service
solves the problem.
On Sat, Nov 3, 2018 at 9:30 PM Cristian Aravena Romero
wrote:
>
> *** This bug is a duplicate of bug 2
Public bug reported:
After upgrading to the latest available packages for Ubuntu 15.10 sshd
will not start any more. The system aquires an address, but it does not
start sshd.
Result: no remote access. On servers this might be fatal, since it might
be a headless one and without sshd running acces
PS: the bug is reported from a 14.04 system, for a 15.10 system. At the
moment of writing, the 15.10 system is not accessible any more, because
of sshd not running (or no open port for sshd. May be even a firewall
problem).
Seen it on:
- 15.04 -- current, stable
- 15.10 -- upcomming
--
You recei
The problem is related to ignoring "noauto" in fstab. The system tries
to mount a nonexisting fd using ufs and fails.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1508470
Public bug reported:
mysql-server cant be installed, because systemd
(233-8ubuntu1~ubuntu16.04.1) requires a newer version of apparmor than
the installed version 2.10.95-0ubuntu2.7 this in tune breaks various
packages depending on mysql-server, like gnu-cash or others.
Possible solutions:
- provi
Ubuntu keeps to many old kernel-images and initrd within /boot. Space is
exausted and it fails to delete old unused kernels before creating a new
initrd failing building an initrd for the newly installed kernel.
A workaround is to delete all old unused kernels and then try it again.
It will succee
Same here. "dpkg-reconfigure lightdm" does not help out.
Lightdm seems to be started, but then is terminated because of "respawning to
fast".
lightdm log:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=2079
[+0.00s] DEBUG:
Public bug reported:
Package does not install completely, but seems to function afterwards.
Maybe it is because sshd may be restarted even if forked daemons are running
serving existing connections. Does the upgrading routine take these into
account while upgrading?
ProblemType: Package
DistroR
No I was not able to find anything except messages about deprecated
entries in /etc/ssh/sshd_config and /etc/ssh/ssh_config Maybe this is
the problem?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://
Public bug reported:
giving "halt -p" or "shutdown -p now" reboots system instead off
powering off.
I have tried some kernel commandline options already, but without success:
- reboot=bios
- acpi=noirq
but none did help. System keeps rebooting on "poweroff", "halt -p" or
"shutdown -p now"
Probl
System powers off if booted from Debian testing, Knoppix 7.7.1 or
FreeBSD 11.0. It also powers off if booted from Ubuntu 14.04.5. But not
if booted from Ubuntu 16.04.2 (on HD) or Ubuntu 16.10 (life-DVD).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Public bug reported:
dnsmasq may be started before all interfaces are available. In such
cases dnsmasq may quit or never bind to upcomming interfaces. In both
cases dns name resolution wont work.
I could notice this together with dynamicaly created interfaces by
- VMware Workstation
- VBox-Interf
Public bug reported:
if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load.
jackd tends to take all availabl CPU power bringing the system to slow
down remarkably. Killing jackd and jackdbus frees cpu and system load
drops from 100%/per CPU down to ~4% overall.
ProblemType: Bug
D
Did that already, got rid of the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1884101
Title:
jackdbus produces high cpu load
Status in jackd2 package in Ubuntu:
Public bug reported:
ubuntu-bug shall try to find a package a command belongs to if the given
name does not match an installed package.
Now:
# ubuntu-bug ubuntu-bug
dpkg-query: Kein Paket gefunden, das auf ubuntu-bug passt
ubuntu-bug shall do in such cases:
- look for the package:
# dpkg -S $(
Public bug reported:
while starting X11 xrandr executes commands:
xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168
2200 -hsync +vsync
xrandr --addmode DP-1 "3840x2160_30.00"
xrandr --output DP-1 --mode "3840x2160_30.00"
while newmode, addmode work, the third comma
Public bug reported:
dnsmasq does in all cases prepend "tftp_root" to tftp-files.
tftp-root=/data/tftp
dhcp-boot=grub/i386-pc/core.0
now have some config files for different subnets:
dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1
dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1
dhcp-boot=net:
Simplest thing would be:
tftp-root
sets the tftp-root directory: /data/tftp -> /
or: /var/lib/tftpboot -> /
Whatever is done is relative to this. tftp-root is then NEVER
prepended to any file given for tftp retrival.
--
You received this bug notification because you are a member of Ubuntu
Touc
ss any file on the
> machine, don't set a tftp-root.
>
>
> Simon.
>
>
> On 06/02/2020 11:02, Thomas Schweikle wrote:
> > Public bug reported:
> >
> > dnsmasq does in all cases prepend "tftp_root" to tftp-files.
> >
> > tftp-root=/
Seeing this behaviour on all distributions using ntp 4.2.6p5:
- Ubuntu 14.04
- CentOS 6.5
- Orcale Linux 6.5
- Debian 7
Bug seems resolved in ntp 4.2.8 as available from http://www.ntp.org
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
maybe it is a security problem if kerberos used: after a while your
clock is of too much and you can't login any more.
** Also affects: ntp (CentOS)
Importance: Undecided
Status: New
** Also affects: ntp (Debian)
Importance: Undecided
Status: New
--
You received this bug not
Public bug reported:
ntpd seems to add offsets instead of subtracting them from the running
synchronized clock, leading to time running away fast in one direction
-- forward if the offset is positive, -- backward if the offset is
negative, until the offset reaches its maximum.
ProblemType: Bug
Di
** No longer affects: ntp (CentOS)
** Bug watch added: CentOS Mantis #8140
http://bugs.centos.org/view.php?id=8140
** Also affects: ntp (CentOS) via
http://bugs.centos.org/view.php?id=8140
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Public bug reported:
After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works
with an older kernel but not with the latest one, I'd assume the newer
kernel does not initialize the devices the right way.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9git1
ProcVer
Public bug reported:
>From time to time NetworkManager does not start at system boot.
NetworkManager seems to be started, but being terminated immediately.
Symptoms:
* no network connection at system boot.
* no network connection while logging in.
* no network applet after logging in.
NetworkMan
Public bug reported:
NetworkManager seems to ignore flag "Use this configuration for all
users". The networkconfiguration is applied only for the one user who
created it, not globally and this configuration is not applied at system
boot! To have the system initialize network you'll have to log on
The bug report was generated on a migrated system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638391
Title:
NetworkManager wont apply configuration for all us
The bug report was generated on a migrated system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638388
Title:
NetworkManager wont start at system boot
Status i
Public bug reported:
After having managed to have a 1024x768 lightdm screen displayed begging
to login, I've tried and being prompted with "You where logged in with
cached credentials".
Not really: I am logged in, but immediately thrown out again. It is
impossible to work!
ProblemType: Bug
Distr
Public bug reported:
After upgrading from 14.04.5 to 16.04.1 lightdm does not start. Only
error I could find reported was:
[+0.19s] DEBUG: Launching process 1927: /usr/share/lightdm_xrandr
[+0.21s] DEBUG: Process 1927 exited with return value 1
[+0.21s] DEBUG: Seat seat0: Exit status of /usr/shar
/dev/xconsole isn't created if it isn't there. If /dev/xconsole exists
it is not taken to output logs as given in
/etc/rsyslog.d/50-default.conf.
Creating /dev/xconsole and changing user:group doesn't help. service
rsyslog restart doesn't have access to this pipe. It doesn't matter if
apparmore is
Public bug reported:
cgroup-lite installed, but daemon missing from cgroup-lite:
# dpkg -l | grep cgroup
ii cgmanager 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon
ii cgmanager-utils 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon
(utilities)
ii cgroup-bin
Public bug reported:
Err http://de.archive.ubuntu.com trusty/universe amd64 Packages
503 Service Unavailable
this is for various different servers. I found files "Source.gz" and
"Source.bz2" at
http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/, but not
"Source".
apt tried to downl
Fixed in a later release of ntpd
** Changed in: ntp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/697592
Title:
unable to
Had to do with the way proxys where addressed. Fixed with newer versions
of tools used for apt
** Changed in: apt (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
htt
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1306563
Title:
/etc/environment ignored
** Changed in: shadow (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1284599
Title:
login ignoring /etc/environment
Status in “
** Changed in: network-manager (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1306562
Title:
network manager discards u
** Changed in: apport (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1270717
Title:
apport-collect fails to login to launchpad w
Fixed
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/854908
Title:
update-initramfs ign
96 matches
Mail list logo