The IPU6 webcam still does not work on my Dell XPS 16 (9640). I've
tested it with Ubuntu 24.04 daily builds including with the 6.9-rc1
kernel. What information would you need to check the problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Package changed: alsa-driver (Ubuntu) => firmware-sof (Ubuntu)
** Changed in: firmware-sof (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058691
This bug seems to affect me with a Dell XPS 16 2024. I get the following
dmesg output if it is of any use:
[2.844944] intel-ipu6 :00:05.0: enabling device ( -> 0002)
[2.845217] intel-ipu6 :00:05.0: Device 0x7d19 (rev: 0x4)
[2.845232] intel-ipu6 :00:05.0: physical base
After extracting the intel/sof-ipc4/mtl/sof-mtl.ri.zst and intel/sof-
ace-tplg/sof-mtl-rt711-4ch.tplg.zst and placing them in the same folder,
the following dmesg output is created:
snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info
0x040380
snd_hda_intel :00:1f.3:
During boot, dmesg reports that the intel/sof-ipc4/mtl/sof-mtl.ri and
intel/sof-ace-tplg/sof-mtl-rt711.tplg files can not be found. However,
the corresponding files are there but packaged with zst file endings.
sof-audio-pci-intel-mtl :00:1f.3: use msi interrupt mode
sof-audio-pci-intel-mtl
Public bug reported:
The sound card is not detected on the Dell XPS 16 2024 (9640). A Cirrus
Logic CS42L43 card is used which apparently got support in Linux 6.6
https://www.google.com/url?sa=t=web=j=89978449=https://www.phoronix.com/forums/forum/software/general-
The same issue affects the python3-distro-info package with version
1.1build1. It would be great to resolve both at the same time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926870
Title:
-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: moritz 2175 F pulseaudio
/dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio
/dev/snd/controlC0: moritz 2175 F pulseaudio
/dev/snd/pcmC0D0c: moritz 2175 F...m
I just got a SIGSEGV from using pinta 1.6-2 the first time.
I opened two images, and used the rectangle select tool. Nothing more.
Dunno if this this is the same bug as previously reported:
=
Native Crash Reporting
Public bug reported:
The mdadm package comes with two systemd timers that are activated
automatitcally, mdcheck_start.timer and mdcheck_continue.timer. The
corresponding services try to run /usr/share/mdadm/mdcheck which doesn't
exist. The units then fail, and no RAID check is run.
[0
I agree with Carlos Garcia.
This is a functionality that everyone expects to work out of the box
today.
It is frustrating to see that in every Ubuntu release something like
this comes up. Another example making ubuntu look bad: I also had to add
the "show desktop" icon manually to the system
** Also affects: timidity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
** Changed in: pulseaudio (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
As asked by @Hui Wang, I have created a separate bug #1880571 for my
problem on focal fossa and run apport-collect. As the data collected by
apport showed that timidity was running I have uninstalled timidity and
this seems to have fixed the problem: audio output was immediately
restored, and
Seeing 'timidity' in the data collected by apport I have just
uninstalled timidity. This has immediately restored the availability of
the sound output. Also after rebooting, sound output is working again (I
have since rebooted twice).
--
You received this bug notification because you are a
I had thought that appending
options snd-hda-intel dmic_detect=0
to /etc/modprobe.d/alsa-base.conf
had fixed the problem. But the problem has since reappeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376572/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376570/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376574/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376575/+files/WifiSyslog.txt
** Description changed:
After booting the system the internal laptop speakers and the internal
microphone are sometimes not detected, pavucontrol
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376565/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376573/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376568/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376569/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376564/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376571/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376562/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376563/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376567/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376561/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376566/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1880571/+attachment/5376560/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880571
Public bug reported:
After booting the system the internal laptop speakers and the internal
microphone are sometimes not detected, pavucontrol only shows a "Dummy Output".
They were working fine under ubuntu 18.04, stopped working after upgrading to
19.10 and are still not working under 20.04.
I have had this on 19.10 (see https://bugs.launchpad.net/ubuntu/+source
/linux-oem-osp1/+bug/1864061/comments/42) and on 20.04.
Adding "options snd-hda-intel dmic_detect=0" to the end of
/etc/modprobe.d/alsa-base.conf has apparently fixed the issue on 20.04
(microphone is still working).
I
The version in proposed it fixing a lot of the existing bugs I've seen.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876731
Title:
[SRU] Update to 3.36.3
To manage notifications about
Also experienced this bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736583
Title:
Evince annotations lost on save
To manage notifications about this bug go to:
I am having this problem (only dummy output) on ubuntu 19.10 with linux kernel
5.3.0.45.38. After booting I can make the output show up and work by running
pulseaudio -k && sudo alsa force-reload
Maybe that workaround helps other people suffering from this problem until a
fix is available.
--
Public bug reported:
Ubuntu release: bionic, cosmic, disco, eoan
Pkg version: 1.1.5-1, 1.1.7-1, 1.1.9-2
Steps to reproduce:
1. Install borgbackup and zsh packages
2. Execute zsh
3. Type "borg " and press TAB
Expected result:
Show list of available subcommands and options.
Actual result:
Shows
I also have the same problem on Ubuntu 18.04.2.
The login screen starts normally, but right after typing my password and
pressing enter the screen is black.
The problem started after an NVIDIA driver update with "apt upgrade". I was
using the nvidia driver form the CUDA Repository.
I tried
Is there any news on the issue? Why is the patch not accepted? This has
been annoying me for years.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/913444
Title:
Every wine update re-enables desktop
Public bug reported:
Clight is a C user daemon utility that aims to fully manage your
display. It will automagically change screen backlight level to match
ambient brightness, as computed by capturing frames from webcam.
URL: https://github.com/FedeDP/Clight
License: GNU General Public License
Public bug reported:
...
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: plymouth-theme-ubuntu-text 0.9.3-1ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Wed Sep 12
Related: #1677903, #1772457
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778770
Title:
GnuPG segfaults when encrypting mail to key with ed25519 / cv25519
subkeys
To manage notifications about
Affects multiple users (as per the comments).
** Changed in: gnupg2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778770
Title:
GnuPG segfaults when
Public bug reported:
Whenn upgrading from 16.04 to 18.04 the update fails due too an unknown
reason
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.25
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
Public bug reported:
Trying to encrypt an e-mail (suing a local RSA/RSA key pair) to a
recipient who combines an RSA public key with RSA and ed25519 (both
"usage: S", not expired) as well as a cv25519 (usage: E, not expired)
subkey.
Just running gpg2 --edit-key with the recipients' key prints:
Public bug reported:
I started installation from within live usb session, having two ntfs partitions
on the same hd (win7)
hp compaq 6200 pro sff
intel pentium cpu G630
ProblemType: Bug
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180405)
DistroRelease: Ubuntu 18.04
Public bug reported:
install fails with warning message
paket grub-efi-amd64-signed konnte nicht in /target/ installiert werden
package grub-efi-amd64-signed couldn't be installed into /target/
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.4
ProcVersionSignature: Ubuntu
Thank you Mathieu, your suspicion was correct: After disabling that
setting, the message on boot is gone, the latest versions of the
packages work and I now see an "ubuntu" entry next to the NVMe entry in
the UEFI boot device menu.
This resolves my immediate issue. I guess the actual problem is
When I first encountered the problem, I first tried to let boot-repair
(run from a live system) repair my Grub installation, since I'm not too
familiar with the boot process on UEFI. It failed multiple times, even
when I disabled Secure Boot and when I enabled the CSM and tried to
install grub-pc.
I've filed bug #1750351.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747889
Title:
(Acer Aspire V3-372) System not booting after update
To manage notifications about this bug go to:
Public bug reported:
After upgrading shim-signed to 1.33.1~17.10.1 (and installing the grub
updates that were published at the same time), the system is stuck in a
boot loop. I've had to downgrade shim and grub to their release versions
to get the system to boot again.
The following message gets
@cyphermox: Just to clarify: Do I need to install the faulty upgrade
again and then file the bug report from a live system? Or is it
sufficient if I collect the information on my current setup (with shim
and grub locked to the release versions)?
--
You received this bug notification because you
Ok, I'll file a different bug report, then. Already have a live USB
which I used for the recovery process. It's Ubuntu 17.10, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747889
Title:
I've taken a bunch of photos (see attachments). Please tell me what
other screens you're interested in, I included the "Security" menu
overview.
Product information from lshw:
product: 20HES0FA35 (LENOVO_MT_20HE_BU_Think_FM_ThinkPad T470)
vendor: LENOVO
version: ThinkPad T470
@yogeshpathade: See my first post. You'll have to boot into a live
system, mount the root filesystem, chroot into it and replace the
versions of shim-signed and grub with the original versions. To do so,
purge the installed versions, look up the original versions of those
packages via "apt-cache
Some additional information: On my system, a similar message is visible
for half a second every single time I boot. When I was stuck in the boot
loop, I saw another line that said "Reset system".
I'm not 100% sure I'm experiencing the exact same issue, but the very
same update also caused a
I have experienced the exact same problem on a different Laptop, a
Thinkpad T470. I fixed the issue by rolling back to the original
versions of grub and shim-signed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
during upgrade to ubuntu 17.10 cacti failed to connect to database,
upgrade of cacti failed
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: cacti 1.1.18+ds1-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
Public bug reported:
just the cryptsetup failed to start.
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: cryptsetup 2:1.7.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41-lowlatency 4.10.17
Uname: Linux 4.10.0-37-lowlatency x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture:
Happy tenth birthday to this bug report on a (universe, I admit) package
which has never worked in Ubuntu, and which has always provided
incorrect information. :-/
~mail-codenest Lynis test PKGS-7366 is already restricted to Debian
systems, see Lynis issue 446 (please open another bug report
If you happen to speak German, please also refer to
https://www.tabos.org/topic/fb6490-absturz-beim-einrichten/ - which is
the developers' official (and I think also the only) support channel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
While the OpenConnect CLI version available in Ubuntu 16.04.2 supports
connecting to (older but not current firmware versions of) Juniper/Pulse
VPN (SSL VPN) (using the --pulse option), the NM GUI does not allow for
configuring this type of VPN. You can choose to configure an
~mtmiller: Could it be that the Daily PPA at
https://launchpad.net/~openconnect/+archive/ubuntu/daily needs another
recipe update? It'd be great to have 2.08 builds (openconnect does not
currently work here against Pulse SSL-VPN unless compiled from source
with
I tried Ubuntu 17.04, still the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686189
Title:
External monitor connecting problem on Intel graphics card
To manage notifications about
The drm nightly kernel works for me (4.12.0-994-lowlatency). However, I
do not have WLAN.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686189
Title:
External monitor connecting problem on Intel
@Kai-Heng:
I do use a mini Displayport Cable with a Lenovo Thinkpad T460S. In the
meantime I tried every kernel I could install using ukuu. However, none
of them worked. Prior to Ukuu I did use a kernel from the nightly builds
(drm-intel) and the monitor worked but WLAN not. Therefore, I
Still the same issue:
4.11.7-041107-generic #201706240231 SMP Sat Jun 24 06:33:20 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
VGA compatible controller: Intel Corporation Sky Lake Integrated
Graphics (rev 07)
i915 1495040 9
i2c_algo_bit 16384 1 i915
drm_kms_helper
This should affect all embedded java uses which launch the JVM on the
main thread (the regular java launcher does not do that) and is caused
by the known buggy (http://www.openwall.com/lists/oss-
security/2017/06/22/6) custom CVE-2017-1000364 fix. Testing the upstream
patch on debian it seems to
>From a user perspective, ubuntu-support-status has not just been not
working, but has been providing false / misleading information across
the past two or three LTS releases. There is no hint on this fact
available anywhere but no this bug report. Plus (to my knowledge) there
is no other utility
so, what can I do? The padoka ppa package seems to be newer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697181
Title:
package mesa-vulkan-drivers (not installed) failed to install/upgrade:
Public bug reported:
E: /var/cache/apt/archives/mesa-vulkan-
drivers_17.0.3-1ubuntu1_amd64.deb: Versuch, »/usr/lib/x86_64-linux-
gnu/libvulkan_intel.so« zu überschreiben, welches auch in Paket libgl1
-mesa-glx:amd64 1:17.1.1-1~z~padoka0 ist
ProblemType: Package
DistroRelease: Ubuntu 17.04
Public bug reported:
some folder seems to be missing
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apt-cacher-ng 0.9.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49
Uname: Linux 4.4.0-70-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptOrdering:
apt-cacher-ng:
Command-line connections are not affected anymore, those have been fixed
by some update in the meantime. Only connections via the NetworkManager
plugin are still affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1545800 ***
https://bugs.launchpad.net/bugs/1545800
Same happens to me almost every time I close it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577853
The problem is that zatacka expects font.ttf somewhere. Unfortunately I
could not find out where, so my solution was to compile from source and
hard code a font path in fx.h, but if you can find out where it expects
font.ttf you can just ln -s any font there and it should work.
Cheers
--
You
This is a simple packaging/configuration issue, the bug has been
assigned for 18 months and it still isn't fixed? Come on, guys!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/934291
Title:
Deleting
Public bug reported:
When using 3 columns (each with a page) and resizing the window to 2 and
1 column, the middle column is empty after resizing to 3 columns again.
(The video may show this more clearly.)
Maybe I am just using this wrong.
Here is the code I used:
import QtQuick 2.4
import
Not sure if this helps, but i've been struggling with these issues since 12.04
(see bugs #1166442 and #1272777).
There have fixes in 3.15.05 and later ones, but this issue occured again with
kernels 4 and ongoing. Other than using these kernels, I have not found an
approriate solution.
May
Public bug reported:
lubuntu 16.04 32bit
"
lxpanel is set to disappear automatically; unfortunately it is also
disappearing when I try for example to click on the wlan-menu (same with
update-notification menu), after 1 second the opened menu closes in line with
the panel itself. (disabling
Public bug reported:
When executing ipa-server-install on a non-x86 architecture (here: ARMv7), the
following error messages appear after having filled out the initial
questionnaire:
...
Configuring directory server (dirsrv). Estimated time: 1 minute
[1/46]: creating directory server user
...
I've installed the 3.13.0-92.139 kernel from trusty-proposed on eight
production systems. I'll let you know by Monday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592429
Title:
trusty kernel
Actualyl that's David Woodhouse working on the protocol support
upstream, sorry I got this wrong. Still, I'd be interested in getting
daily builds + packages done for both openconnect + the NM integration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Great, thanks for working on Juniper / Pulse SC support upstream, Mike.
Is there a way I can help testing it (if not, yet, please consider
pinging me once you reach this point)? I noticed there is a 'daily'
build OpenConnect PPA (though it does not (currently) provide Xenial
builds), but none for
Public bug reported:
Similar to #1500826 there is an undocumented (?) "-juniper" option in
openconnect which allows for connecting to Pulse Secure VPNs using a
newer / modified protocol.
Unfortunately, the current Gnome NM GUI does not seem to support passing
this specific or any custom
This looks good to me: We have been running the test kernel on nine
production servers for more than a week now and the systems are stable
(while previous we'd seen three kernel hands over the course of 48
hours).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
The trusty kernel can crash if the OOM killer kills processes which have
reached a memory limit imposed by cgroups. More details can be found in
this blog post:
https://community.nitrous.io/posts/stability-and-a-linux-oom-killer-bug
The upstream patch series which
** Changed in: lightdm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318778
Title:
lightdm doesn't let pam_mkhomedir execute
To manage
The problem does not exist anymore. Probably an update solved it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1531902
Title:
Stopping cups-browsed.service may stall shutdown/reboot
To manage
algorithm prefix under
rsa_verify cmp is attached.
Not sure how a backward-compatible fix would look like (probably would
have to check whether this prefix is already present), but forcing
inject = INJECT_NONE in cmd_pksign seems to fix the issue for me.
Moritz
** Affects: gnupg-pkcs11-sc
** Tags added: amd64 trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318778
Title:
lightdm doesn't let pam_mkhomedir execute
To manage notifications about this bug go to:
I've tried to reproduce this bug with a current Ubuntu Xenial, by
adding:
sessionrequired pam_mkhomedir.so skel=/etc/skel/ umask=0022
to /etc/pam.d/common-account and creating a new user without home
directory with adduser --no-create-home afterwards. I also added a file
to /etc/skel.
I've tried to reproduce this bug with Xenial in a VirtualBox VM today,
and it didn't come up. After installing kubuntu-desktop and reboot,
lightdm came up and not sddm. Seems like Flames_in_paradise assumption
is correct and the bug is fixed upstream.
--
You received this bug notification
Public bug reported:
The icons (see the red icons in the attached screenshot) next to the
appointments are confusing or misleading, as they can easily be taken for the
date of the appointment.
Ideally they should contain the date (day in the month) of the appointment for
a quick overview.
**
I have this bug with i.e. the firefox-icon. It also appeared minimized
in the menu-editors sidebar but I could never set it via the submenu
"select icon". It also never appeared in the submenu "Icon Source ->
System icons", only under "Icon Source -> Other icons".
Since the Menu Editor never
** Tags added: xenial
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1450068
Title:
Icons missing in Plasma/KDE after upgrade to Ubuntu 15.04
To manage notifications about this bug
Public bug reported:
It would be nice, if the thumbnailer could preserve transparency in thumbnails
for e.g. logos.
The black background often looks really bad in applications that use a light
theme.
** Affects: thumbnailer (Ubuntu)
Importance: Undecided
Status: New
--
You
This also affects Xenial (tested on yesterday's live installer).
** Summary changed:
- apt-key del doesn't understand fingerprint
+ apt-key del silenty fails to delete keys due to limited understanding of
input formats
** Summary changed:
- apt-key del silenty fails to delete keys due to
I just ran into the same issue. What's not obvious from the original
post, though, is that apt-key reports back that it deleted the key "OK"
- but actually did not:
root@mybox:~# apt-key list | grep 79EAFD54
pub 1024D/79EAFD54 2009-01-22 [expired: 2013-06-28]
root@mybox:~# apt-key adv
Public bug reported:
Error message:
trying to overwrite '/usr/sbin/validlocale', which is also in package libc-bin
2.21-0ubuntu4
Installation from USB-Stick created with Unetbootin on Debian
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ubiquity 2.21.37
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1446760 ***
https://bugs.launchpad.net/bugs/1446760
Public bug reported:
After installing Unity via ubuntu-desktop in Kubuntu and choosing
lightdm as default display manager, sddm comes up at each restart,
ignoring the configuration.
sddm is version
1 - 100 of 649 matches
Mail list logo
