It appears you are reporting two separate issues. Please pick one for
this bug to be about and then open a new bug for the other.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
Public bug reported:
Fresh install 18.04.2.Screen locks after 30 minutes despite toggle
ON/OFF in settings or terminal command "gsettings set
org.gnome.desktop.lockdown disable-lock-screen 'false' or 'true'"
Dock set to auto hide does not return properly when mouse over. Dock set
to 'Bottom'.
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
When the problem happens does the mouse pointer freeze too?
Only if the mouse pointer freezes is it the Xorg process that's frozen.
** Tags added: amdgpu
** Summary changed:
- Xorg freeze
+ [amdgpu[ Xorg freeze
** Summary changed:
- [amdgpu[ Xorg freeze
+ [amdgpu] Xorg freeze
** Package
If the problem started only a month ago then it wouldn't be pulseaudio
because that hardly ever changes. Most likely it is the kernel, which
gets updated more frequently.
Can you please try some older (or newer) kernel versions from here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
Yes, it seems to be an issue either with the amdgpu graphics driver, or
with the monitor's own detection data that the supported modes are
limited to
[ 3.773] (II) AMDGPU(0): Printing probed modes for output DisplayPort-0
[ 3.773] (II) AMDGPU(0): Modeline "2560x1440"x60.0 241.70 2560
It appears your system is having some disk trouble which may be related:
[8.507702] systemd-journald[282]: Received request to flush runtime journal
from PID 1
[9.786399] systemd-journald[282]: File
/var/log/journal/a99c9c8a58fcb89719f7d37e51877f86/system.journal corrupted or
uncleanly
Thanks for that. I've never seen pulseaudio do this before.
1. Do you have any ideas as to what apps might have been using
pulseaudio recently?
2. Is the problem regular? Does it return after a reboot?
3. Does the same problem exist in Ubuntu 19.04 if you boot that from
USB?
This is a strange one.
It appears you have an Intel GPU (I assume because the CPU is model
i7-8700). And the Linux kernel can find it on the bus:
00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:3e92] (prog-if 00 [VGA controller])
but the kernel is also failing to load
Yes, there is a power optimization in the 19.04.
please close that optimization by editing the /etc/modprobe.d/alsa-
base.conf
add options snd-hda-intel power_save=0
then reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thanks for the reply. It is 3.7G byte mapped hardware memory, not just virtual.
Here's the output you asked:
$ cat status
Name: pulseaudio
Umask: 0022
State: S (sleeping)
Tgid: 25499
Ngid: 0
Pid:25499
PPid: 1
TracerPid: 0
Uid:1000100010001000
Gid:1000
Thanks for the bug report.
'pmap' displays virtual memory (address space), which is mostly not real
memory.
Please attach a copy of your /proc/PID/status file. The important field
that affects machine performance is VmRSS, and VmData tells you the
amount of regular memory allocations.
**
Public bug reported:
Xubuntu 19.04, 64bit, encrypted drive, using a desktop computer with
ethernet to connect. Connects fine. Use openvpn also (from terminal).
When the modem is turned off and on, or when the modem remains on but
the ethernet connection is disabled (by unticking) and then ticking
Running with 'pmap -x' gives this info:
$ pmap -x 25499
25499: /usr/bin/pulseaudio --start --log-target=syslog
Address Kbytes RSS Dirty Mode Mapping
55e3bb805000 84 84 0 r-x-- pulseaudio
55e3bb805000 0 0 0 r-x-- pulseaudio
Public bug reported:
So, my pulseaudio process is 6Gbyte large, 3.5Gb of that resident in
memory.
version: 1:11.1-1ubuntu7.2
OS: Ubuntu 18.04.2 LTS
System uptime: 11 days
Desktop: GNOME
pmap output:
$ pmap 25499
25499: /usr/bin/pulseaudio --start --log-target=syslog
55e3bb805000
As a workaround now you may install and use the curl-metalink snap for
downloading Metalinks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1391779
Title:
curl not build
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in: hundredpapercuts
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
It literally doesn't go away, only reliable way is playing something
24/7 just to get Ubuntu to shut the f*** up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1833793
Is this some kind of new power optimization to constantly reinitialize
my sound card?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1833793
Title:
Updating to 19.04
Public bug reported:
I can't provide much in the way of detail as the freezes are seemingly
random. They happen with different software being used.
Release: Ubuntu 18.04.2 LTS
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu
Mortimer, it's still available at the Google cache:
https://webcache.googleusercontent.com/search?https://webcache.googleusercontent.com/search?q=cache:Ulh1YXwMuK8J:https://dev.getsol.us/T5224
It appears that the fix there addresses the same file and the same line
in that file. However, the lines
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: geoclue (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to geoclue in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1834782/+attachment/5274267/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1834782/+attachment/5274268/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1834782/+attachment/5274266/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
apport information
** Tags added: apport-collected bionic third-party-packages wayland-
session
** Description changed:
Issue: whichever sound-related action (sound +/- media keys, spotify song,
youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and
then stops and
I am not sure if this is a kernel/FW issue, as the soundcard is recognized and
the sound playes at first.
On the other hand there were not changes/updates to alsa,pulseaudio and the
sound used to work ok before.
These problems started to appear cca a month ago(?) but usually "some
trick" made
Public bug reported:
Issue: whichever sound-related action (sound +/- media keys, spotify song,
youtube vid in browser,...) I do, the sound works OK for about 2-3 seconds, and
then stops and becomes silent.
The interesting thing is that when I stop playing the audio (ie close the
browser tab
Same here, Ubuntu 19.04, not on wayland.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1807709
Title:
dbus always crashes at session start (on wayland)
Status in dbus
Here's crash report. Ubuntu 19.04, not on wayland.
** Attachment added: "Crash report"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1807709/+attachment/5274264/+files/_usr_bin_dbus-daemon.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
$ apport-collect 1834780
ERROR: The python3-launchpadlib package is not installed. This functionality is
not available.
** Summary changed:
- apport should have python3-launchpad in required dependencies
+ apport should have python3-launchpadlib in required dependencies
** Description changed:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1834780/+attachment/5274261/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1834780/+attachment/5274263/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Public bug reported:
When asked to report apt-collect , apport is not installed on my
system and I was told "apt install apport", so I did and the
installation went ok.
Problem:
apport then fails on missing dependency python3-launchpadlib
Workaround:
manually install it through apt.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1834780/+attachment/5274262/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
Uploaded apport-collect, please note the dependencies info is after I
needed to manually install the launchpadlib :)
--
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/1834780
** Changed in: bzip2 (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bzip2 in Ubuntu.
https://bugs.launchpad.net/bugs/1834494
Title:
latest bzip2 reports crc errors incorrectly
Filled respective bug in Debian as well as per
https://bugs.debian.org/931278
** Bug watch added: Debian Bug tracker #931278
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931278
** Also affects: bzip2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931278
Importance:
Does anybody care about lightdm bugs? I'm still seeing this issue but I
haven't found a way to debug it. Is there some environment variable or
some other method that can make all g_debug() messages visible from
lightdm? Currently no log seems to contain any of the g_debug() messages
in the lightdm
Can confirm the segfault.
Actually snap package is not a solution, it has a different behaviour
with media keys (not working without an explicit mapping) that's why the
deb package is preferrable.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Pardon my ignorance about the Launchpad bug metadata states, but: is
there going to be an update for Ubuntu Disco fixing this issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
41 matches
Mail list logo
