^LTS
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1883370
Title:
system-config-printer hangs when trying to change driver
Status in System Config Printer:
Fix Relea
Please fix this in 20.04 LTR (Focal), too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1883370
Title:
system-config-printer hangs when trying to change driver
Status
I tried this by 20.04, but could not get sound via HDMI cable work,
except once, even if I had sample rate 44100 set in daemon.conf. I
wonder what is wrong. TV tells: "unknown audio signal, check the
source."
--
You received this bug notification because you are a member of Desktop
Packages, whic
** Description changed:
# Summary
`apt install libegl-mesa0` does not install it due to a dependency
conflict in the apt repo.
libegl-mesa0 has dependency to explicit versions of:
* libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
* libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)
But the l
Public bug reported:
# Summary
`apt install libegl-mesa0` does not install it due to a dependency
conflict in the apt repo.
libegl-mesa0 has dependency to explicit versions of:
* libgbm1 (= 22.2.5-0ubuntu0.1~22.04.1)
* libglapi-mesa (= 22.2.5-0ubuntu0.1~22.04.1)
But the latest in ubuntu repos a
bug still found on lunar
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1996927
Title:
Nautilus send mail not working
Status in nautilus package in Ubuntu:
Confirmed
Bug descript
Public bug reported:
Hi,
After upgrade from 22.04 to 22.10 Send an attached file to email from
nautilus is not working anymore.
Menu sendmail ( courriel in french) appears when i right click on file ,
then thunderbird appears but without the attachement . It was working
very
** Also affects: lightdm
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1946987
Title:
Regression: Nvidia 340 Xorg driv
** Summary changed:
- Nvidia 340 Xorg driver is installed but not loaded after OS upgrade
+ Regression: Nvidia 340 Xorg driver is installed but not loaded after OS
upgrade
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-
** Description changed:
I tried both nouveau and nvidia-340 drivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, cur
Related question: https://askubuntu.com/q/1370465/21005
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1946987
Title:
Nvidia 340 Xorg driver is installed but not l
Maybe lightdm could do something differently? What causes HDMI to appear
when I log out of session?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1946987
Title:
N
** Description changed:
I tried both nouveau and nvidia-340 drivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, cur
What does the "Report problem..." button in the dialog do, then if I
have to use command line to report the crash files?
I see "sudo nvidia-xconfig" generates some basic /etc/X11/xorg.conf
file.
Regardless, I noted the following:
If I log out from the Xfce session back to the LightDM greeter the
BTW after every boot I see "System program problem detected?" dialog and
every time I choose "Report problem...". I booted today, too.
$ LC_ALL=C ls -l /var/crash/
total 4624
-rw-r- 1 jarnos whoopsie 1416740 Oct 14 11:05
_usr_bin_xfce4-power-manager.1000.crash
-rw-r- 1 root whoopsie 331
Where can those differences be? I could compare to another machine with
the same driver. The graphics card is different, though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad
Could there be something in upgrading process that caused this that
clean install wouldn't have done? Could the relevant parts be clean
installed now?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
One more thing. I get an error dialog after startup in the desktop. It
does not tell what went wrong, but it has an option to report to
developers and so I did.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 i
Hmm. I have another computer that is more successful with nvidia-340 in
Xubuntu 20.04. When I compare to Xorg.0.log files, I see differences
after line
"(II) systemd-logind: logind integration requires -keeptty and -keeptty
was not provided, disabling logind integration". The successful one has
"
I searched for all .conf files in the device for "fbdev" (case
insensitive) and found these:
/usr/src/linux-headers-5.4.0-84-generic/include/config/auto.conf
CONFIG_XEN_FBDEV_FRONTEND=m CONFIG_DRM_FBDEV_EMULATION=y
CONFIG_DRM_FBDEV_OVERALLOC=100
/usr/src/linux-headers-5.4.0-84-generic/include/con
There is no string "Default Screen Section" in
/usr/share/X11/xorg.conf.d directory.
The directory contains files: 10-amdgpu.conf
10-quirks.conf
10-radeon.conf
40-libinput.conf
51-synaptics-quirks.conf
70-synaptics.conf
70-wacom.conf
nvidia-drm-outputclass-ubuntu.conf
The last one is attached.
*
I don't know if it is relevant, but even with Xubuntu 18.04 I had to
force pulseaudio sample rate to 44100 to be able to successfully play
sound via HDMI.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubun
Public bug reported:
$ xrandr | grep -i hdmi
HDMI-1 disconnected (normal left inverted right x axis y axis)
This is even when the monitor is connected.
IIRC it has never worked with nouveau, but on the other hand nvidia-340
is unsupported nowadays by Nvidia.
ProblemType: Bug
DistroRelease: Ubun
** Description changed:
- I tried both nouveau and nvidia-340 deivers. It used to work at least by
+ I tried both nouveau and nvidia-340 drivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
- $ xrandr
+ $ xrandr
xran
There exists no /etc/X11/xorg.conf file. I already switched to nouveau
using "Software & Updates" rebooted, switched back to nvidia-340 by the
same application, and rebooted, but it did not help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
Public bug reported:
I tried both nouveau and nvidia-340 deivers. It used to work at least by
the latter one in Xubuntu 18.04, even with HWE kernel
When using the nvidia-340 driver:
$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1200, current 1920 x 1200
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Worked with nvidia-340 driver which is no more updated.
- When I resume, nothing works. Macbook keyboard lights are on, but
- otherwise the machine seems dead. Power button reboot needed.
+ Wh
Same thing in focal. I also tried 5.13.0-1010-oem kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1922562
Title:
Resume from suspend to RAM fails
Status in
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New
** Tags added: focal
** Description changed:
Worked with nvidia-340 driver which is no more updated.
When I resume, nothing works. Macbook keyboard lights are on, but
otherwise the machine s
I created the custom default.pa. It adds only two commands when compared to
default /etc/pulse/default.pa:
load-module module-native-protocol-tcp auth-ip-acl=192.168.100.51
set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo
The first one I need for network access of pulseaudio from a
** Attachment removed: "default.pa"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513625/+files/default.pa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.n
>From syslog:
"Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this
name or index.
Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize
daemon due to errors while executing startup commands. Source of commands:
/home/jarnos/.config/pulse//default.pa
>From syslog:
"Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: No card found by this
name or index.
Jul 25 00:07:01 jarnos-OptiPlex-9010 pulseaudio[1580]: Failed to initialize
daemon due to errors while executing startup commands. Source of commands:
/home/jarnos/.config/pulse//default.pa
** Description changed:
- First pulseaudio fails for some reason.
+ First pulseaudio fails for some reason. Pulseaudio Plugin i.e. the
+ volume control in Xfce panel shows mute after I start session, but I can
+ not change it. This does not happen every time.
ProblemType: Bug
DistroRelease:
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1937919/+attachment/5513397/+files/syslog
** Description changed:
- This is not always reproduceable.
+ First pulseaudio fails for some reason.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package
Public bug reported:
This is not always reproduceable.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
Audio
** Description changed:
+ I have "set-card-profile alsa_card.pci-_00_1b.0 input:analog-stereo"
+ in "~/.config/pulse/default.pa". It caused pulseaudio to fail with this
+ version. I removed the line and run pulseaudio.
+
Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 C
** Description changed:
Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition
Audio Controller (rev 04)
+
+ EDIT: oh, it works again. I'll keep track of this issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1
Public bug reported:
Unrecognized device:
Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition
Audio Controller (rev 04)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname:
You do not need to switch from guest session to do those nowadays:
https://help.ubuntu.com/community/CustomizeGuestSession
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1022858
Title:
*** This bug is a duplicate of bug 1022858 ***
https://bugs.launchpad.net/bugs/1022858
** This bug has been marked a duplicate of bug 1022858
Guest session asks for a password after switching users
--
You received this bug notification because you are a member of Desktop
Packages, which i
Does one need to switch from guest session? Maybe it should be disabled.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1022858
Title:
Guest session asks for a password after switchin
@Sushenjit did you file a bug report?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481804
Title:
LightDM's guest-account script should disable screen lock universally
for guest s
Mika, I can confirm, oddly it helped renaming
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf to
/usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf.bak.
I am using 20.04 now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Well, how are you supposed to know, which resample method is actually
used?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1741045
Title:
Change the default resample-method to spee
** Tags added: eoan focal
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1855350
Title:
Will not logout
*** This bug is a duplicate of bug 1855350 ***
https://bugs.launchpad.net/bugs/1855350
** This bug has been marked a duplicate of bug 1855350
Will not logout or shutdown form guest-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
Yes, it still happens on Xubuntu 18.04, nvidia driver, sync to vblank
set in OpenGL settings in NVIDIA X Server Settings. But I expect it to
be better with 19.10 (Xfce 4.14) when using compositor. Chromium Version
80.0.3987.163 (Official Build) Built on Ubuntu , running on Ubuntu 18.04
(64-bit)
--
I didn't notice to mention this earlier as I had no windows open on the
top monitor at the time of writing, but it is fair to mention that the
top monitor's app overview works flawlessly, only the bottom monitor is
broken. Attached picture for clarification.
** Attachment added: "Top monitor has t
I have reported this problem on the gnome-shell gitlab, new bug ID is 2528.
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2528
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2528
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2528
--
You received this bug notifica
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1869571/+attachment/5342951/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1869571/+attachment/5342948/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bug
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1869571/+attachment/5342950/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1869571/+attachment/5342949/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https:/
apport information
** Tags added: apport-collected focal third-party-packages
** Description changed:
Very recently I have started experiencing a constant bug of the app
overview / search functions of gnome shell being entirely unusable
because shell operates at such a tiny scale that bare
Public bug reported:
Very recently I have started experiencing a constant bug of the app
overview / search functions of gnome shell being entirely unusable
because shell operates at such a tiny scale that barely anything is
shown on screen.
I managed to narrow the problem down to having something
** Description changed:
In the video mode there are moving stripes on the screen and monitor
turns off occasionally. (Maybe this is just bad behaving monitor, an old
Samsung TV) It became got good after I run
xrandr --output HDMI-1 --mode 1920x1080
(and --auto for each other video
** Description changed:
In the video mode there are moving stripes on the screen and monitor
- turns off occasionally. (Maybe this is bad behaving monitor, an old
- Samsung TV) It got good after I run
+ turns off occasionally. (Maybe this is just bad behaving monitor, an old
+ Samsung TV) It bec
Public bug reported:
In the video mode there are moving stripes on the screen and monitor
turns off occasionally. (Maybe this is bad behaving monitor, an old
Samsung TV) It got good after I run
xrandr --output HDMI-1 --auto
(and similar for each other video output) in /usr/local/bin/monitor-
con
** Description changed:
- The following command tells the files:
+ The following command tells the files:
grep awk $(dpkg-query -L pulseaudio | grep
/usr/share/bash-completion/completions/)
/usr/share/bash-completion/completions/pulseaudio:pactl list cards 2>
/dev/null | awk -e \
/usr
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/243
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1857708
Title:
Uses GNU awk specific option in bash completio
Stephen, do you use xfce4-screensaver? Is the other lock screen from
light-locker. You do not have to use both. Check your autostarts.
Purging light-locker changes power manager settings UI, but there is
still checkbox for locking.
--
You received this bug notification because you are a member of
Sebastien Bacher, I attach the output of 'LC_ALL=C journalctl -b'. I issued ls
command
on 11.39.34 and it took about 5 minutes to complete.
** Attachment added: "LC_ALL=C journalctl -b"
https://bugs.launchpad.net/libmtp/+bug/1792085/+attachment/5323736/+files/j.log
** Summary changed:
- MT
The previous was on Xubuntu 19.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1792085
Title:
Regression: MTP not working/very slow
Status in libmtp:
New
Status in gvfs package in U
It is odd that this slowness happens with some directories, but not with
others. For example it happens on a directory with 7 files; file names
consist of letters, '-', digits and '.'. ls command on that directory
takes about 5 minutes. But there are other directories (where there are
more or less
Does it work better with nvidia driver?
You could use another locker in 18.10 as workaround. See contents of
/usr/bin/xflock4 script for hint. (You have to kill light-locker process
and make it not start in "Session and Startup" dialog.
--
You received this bug notification because you are a mem
Guess what? Affects Xubuntu 19.10. What is so difficult in not asking
password when guest session is concerned?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1022858
Title:
Guest ses
Public bug reported:
The following command tells the files:
grep awk $(dpkg-query -L pulseaudio | grep
/usr/share/bash-completion/completions/)
/usr/share/bash-completion/completions/pulseaudio:pactl list cards 2>
/dev/null | awk -e \
/usr/share/bash-completion/completions/pulseaudio:pa
I installed gnome-terminal and got 'unconfined'. So I could view the
home directory of another user, but if the directories had no
permissions for Other group, I could not view the contents in guest
session. So I think a better solution than disabling guest sessions is
to make proper default permis
I tested this on Xubuntu 18.04.3, and xfce4-terminal gives the expected
output (like xterm as well). I do not see how this should depend on the
terminal application used. I guess it is pretty safe to use guest
session in Xubuntu.
--
You received this bug notification because you are a member of D
** Description changed:
- If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to
Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker
is not used).
+ If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to
Ctrl-Alt-F6), screen is bla
Oh, I found alternative way that works for GRUB menu resolution and
console resolution, too, and no need to create /etc/X11/xorg.conf.
Edit /etc/default/grub accordingly:
GRUB_GFXMODE=1280x1024,auto
GRUB_GFXPAYLOAD_LINUX=keep,text
You may want to or have to use a different resolution than 1280x1
I used
sudo nvidia-xconfig
to create initial /etc/X11/xorg.conf file like told in #18
Then added
Section "Files"
ModulePath "/usr/lib/nvidia-340/xorg"
ModulePath "/usr/lib/xorg/modules"
# ModulePath "/usr/lib/x86_64-linux-gnu/xorg"
EndSection
in /etc/X11/xorg.conf
The last
ls /usr/lib/x86_64-linux-gnu/nvidia*
tells "No such file or directory"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1760068
Title:
Wrong resolution at unlock scr
** Description changed:
Does not play sound when playing file that has 48000 Hz sample rate via
- sink output:iec958-stereo
+ sink output:iec958-stereo. This is when using proprietary nvidia-340
+ driver; when using nouveau driver, HDMI is not even recognized (Bug
+ #1844129).
Note that the
** Description changed:
Does not play sound when playing file that has 48000 Hz sample rate via
sink output:iec958-stereo
+
+ Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics
+ adapter) does not have real HDMI audio, but audio is somehow wired from
+ motherboard's S/PDIF
** Summary changed:
- Will not play sound via HDMI unless you run pavucontrol first
+ Will not play sound via HDMI using 48000 Hz sample rate
** Description changed:
- Does not play sound via sink output:iec958-stereo unless I start
- pavucontrol before running the player such as paplay. Player
I had this problem, too, but it suddenly started to work in the middle
of session. I don't know, if installing package android-tools-adb and
pcmanfm had anything to do with it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubunt
** Description changed:
OS: from Hardy to at least Bionic.
When you use Finnish keyboard, you have to hold Alt Gr down to type | or
\ or certain other characters. When typing a shell command, you may
often want to enter a space character after such characters. But it
easily happens th
** Description changed:
- OS: from Hardy to at least Trusty.
+ OS: from Hardy to at least Bionic.
When you use Finnish keyboard, you have to hold Alt Gr down to type | or
\ or certain other characters. When typing a shell command, you may
often want to enter a space character after such c
** Summary changed:
- Non-breaking space is easy to write accidentally and impossible to
distinguish from regular space.
+ Non-breaking space is easy to write accidentally and impossible or hard to
distinguish from regular space.
--
You received this bug notification because you are a member o
** Description changed:
OS: from Hardy to at least Trusty.
When you use Finnish keyboard, you have to hold Alt Gr down to type | or
\ or certain other characters. When typing a shell command, you may
often want to enter a space character after such characters. But it
easily happens th
** Description changed:
If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to
Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker
is not used).
- This happens with nvidia-340 driver (I am using version
340.107-0ubuntu0.18.04.1 from bionic-updates
** Description changed:
If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to
Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker
is not used).
- This happens with nvidia-340 driver (I am using version
340.107-0ubuntu0.18.04.1 from bionic-updates
Public bug reported:
Command 'pulseaudio --dump-resample-methods' displays available resample
methods, but there are more methods described in 'man pulse-
daemon.conf'. For example, if I run 'pulseaudio --resample-method=soxr-
hq'. Either it should be documented which resample method is used, if a
** Description changed:
Does not play sound via sink output:iec958-stereo unless I start
pavucontrol before running the player such as paplay. Player does not
show any error and takes its time to play, but there is no sound.
+
+ Workaround:
+ Set
+ alternate-sample-rate = 44100
+ in /etc/pu
When pavucontrol is not running, it depends on sample rate of playback,
whether or not the sound is audible:
$ speaker-test -r 48000
not audible
$ speaker-test -r 47999
audible
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio
Public bug reported:
Does not play sound via sink output:iec958-stereo unless I start
pavucontrol before running the player such as paplay. Player does not
show any error and takes its time to play, but there is no sound.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ub
I did already
# libdir=/usr/lib/x86_64-linux-gnu/python3.6/site-packages
# cp /usr/share/lirc/python-pkg/config.py $libdir/lirc
# ln -s $libdir/lirc /usr/lib/python3/dist-packages/
# ln -s $libdir/lirc-setup /usr/lib/python3/dist-packages/
as superuser and
'systemctl disable --no
^fails. If I add the lirc group, then I can run 'sg dialout lirc-setup',
and setup, and even make ir receiver react, but testing by irw still
does not display anything. Is there some guide for what has changed so
that setting up correctly would be easier?
--
You received this bug notification bec
I tried running lirc-setup on fresh 18.04 install, but it fais as group
lirc does not exist.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lirc in Ubuntu.
https://bugs.launchpad.net/bugs/1788235
Title:
lirc broken on 18.04
Status in
** Description changed:
If I try to switch to a virtual console by Ctrl-Alt-F1 or greater (up to
Ctrl-Alt-F6), screen is black. But I can return by Ctrl-Alt-F7 (if light-locker
is not used).
This happens with nvidia-340 driver (I am using version
340.107-0ubuntu0.18.04.1 from bionic-updates
My 18.04 upgrade was somewhat corrupted. I had to do some manual
troubleshooting first to make the upgrade complete. I do not know, if
it is still complete, but this bug exists anyway.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvid
*** This bug is a duplicate of bug 1811402 ***
https://bugs.launchpad.net/bugs/1811402
Public bug reported:
NA
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-340 340.107-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-ge
Does not work with 340.107-0ubuntu0.18.04.2 either. HW: Geforce 9400M.
I do not know, if related, but with different hardware and
340.107-0ubuntu0.16.04.2 in Xenial I can switch to TTY: On a laptop with
a monitor connected to HDMI, the TTY is seen in integrated display only
even if the X session i
Fixed in 340.107-0ubuntu0.16.04.2
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/
Works fine with 340.107-0ubuntu0.16.04.2
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1819077
Title:
SRU Request: nvidia-340 340.107-0ubuntu0.16.04.1: nvidia-340
Bug #1819077
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1573508
Title:
n
Public bug reported:
nvidia-340 (from xenial-proposed) does not work with kernel from linux-
generic-hwe-16.04.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
Uname: Linux 4.4.0-142-generic x
I upgraded from 16.04 to 18.04 and lirc does not work anymore. systemd shows
errors such as "lircd-0.10.0[928]: Error: Cannot glob
/sys/class/rc/rc0/input[0-9]*/event[0-9]*"
I suppose it is a bug, as lirc should work after upgrade without manual
reconfiguration.
--
You received this bug notifi
1 - 100 of 414 matches
Mail list logo
