Unfortunately, after several hours/days, the issue reappears. It's as if
when Tracker3 is doing some more heavy reindexing in the background,
when the laptop is not in use, it hangs.
In my case the issue is definetely with Tracker3; Nautilus hanging is a
side effect of not being able to
Resetting Tracker3 (the file indexing daemon) seems to have done the
trick for me. I'd need a couple days to confirm that the issue is 100%
gone, but there's definetely something wrong with Tracker3, my data,
and/or the new version of Nautilus in Ubuntu 22.10:
tracker3 reset --filesystem
The problem seems to be related to the search provider, can anyone
confirm?
As soon as I search anything in Gnome Activities overview, Nautilus
hangs. If I disable Settings > Search > Files, I experience no hangs (of
course, I lose file results in the overview when searching, too).
--
You
I have to rectify a little bit my affirmation above, everything I said
about the video issues is right, but the problem with the video lagging
and blinking and re-scalling specially when you move the cursor while
watching in full screen mode look like a GNOME problem, not a NVIDIA
proprietary
As @vsulimov mention, the solution from @nightwing666 works, in my case
in a ThinkPad X1 Gen 2, but the video scaling in full screen doesn't, it
makes any video you try to reproduce in full screen to blink, and if you
set the video again in not fullscreen mode the video is scaled x2, or it
makes
i have recently installed chrome remote desktop too, and nautilus and terminal
stopped working.
running this solved the terminal issue for me, as suggested in this [0]
duplicate question:
dbus-update-activation-environment --systemd --all
for some reason, terminal wouldnt launch, but i could
I finally posted on the pulseaudio list and someone referred me to this
bug:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640
I uninstalled timidity and that seems to have fixed the problem.
--
You received this bug notification because you are a member of Desktop
Packages,
So is the next step that I should post this to pulseaudio-
disc...@lists.freedesktop.org? Do I need to be a list member to post
there?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
On my ubuntu 18.04 system I only have
/usr/bin/pulseaudio --start --log-target=syslog
owned by me. On my 19.04 system
/usr/bin/pulseaudio --daemonize=no
also owned by me. Note gdm is not running. I assume lightdm, which is
running, is the alternative.
--
You received this bug notification
>From ps I see that "/usr/bin/pulseaudio --daemonize=no" is running with
user "adrian" and also my home directory is owned by "adrian".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
I already posted the log file a.txt in its entirety. Here it is again:
D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
I forgot to mention that dpkg -S says:
libpulse0:amd64, libpulse0:i386: /etc/pulse/client.conf.d/00-disable-
autospawn.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828136
I looked around a bit and found ~/.config/pulse, a directory with
permission 700. Changed it to 777. That didn't make a difference.
Also found ~/.pulse with this contents:
12 -rw-r--r-- 1 adrian adrian 12288 Oct 7 2013
11597e2b32f1c4cb56501b9c0008-card-database.tdb
4 -rw-r--r-- 1 adrian
I removed the 00-disable-autospawn.conf file and rebooted. Then I get
a.txt containing this:
D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot
I believe that I upgraded incrementally as new releases came out from
14.04. (Hard to recall for sure back that far.) But definitely I got to
18.10 from 18.04 to 18.04 from 17.10. And 18.04, I didn't have this
problem. In fact, I have a second machine that I'm "scared" to upgrade
that's still
I followed the instructions but no log file was created.
I noticed in the man page for pulse-client.conf it says
extra-arguments= Extra arguments to pass to the PulseAudio daemon when
autospawning.
and in /etc/pulse/client.conf.d I see
autospan=no
I tried playing sound, running "alsa
The before file was attached to the last comment. Here's the after file
from pactl.
** Attachment added: "postforce"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce
--
You received this bug notification because you are a member of
I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the
pactl command. Results was as you predicted. The pactl outputs before
and after appear below.
Here's the before output:
Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner
I rebooted and went into the "Ubuntu" desktop and looked at the sound
settings. It shows an output tab and said "dummy". I clicked and was
able to switch it to the nvidia card. I think maybe the nvidia card was
off, which it should be since there's no output device connected.
I went back into
If I look at the sound settings using pavucontrol (I don't normally use
gnome and don't seem to have a program called gnome-sound-setting
installed) then under the configuration tab I see the nvidia hardware
but not the built in audio. (The nvidia card has only HDMI and my
speakers don't have
Summary: looks to me like aplay -l is showing the intel hardware. No
adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x 3 root root 320 May 9 18:07 ./
0 drwxr-xr-x 20 root root 5080 May 9 18:07 ../
0 drwxr-xr-x 2 root root 80 May 9 18:07 by-path/
0 crw-rw+ 1 root audio 116,
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262477/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262473/+files/CRDA.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262480/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262481/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262478/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
I ran the "apport-collect 1828136" command as directed by the automated
script. A little puzzled that it gave the message
dpkg-query: no packages found matching alsa-driver
dpkg-query: no packages found matching linux
--
You received this bug notification because you are a member of Desktop
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262475/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262479/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262476/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
The automated script said I should change the status to "confirmed" even
though I am the reporter.
When 18.10 came out some other people reported similar issues:
https://ubuntuforums.org/showthread.php?t=2403077
https://ubuntuforums.org/showthread.php?t=2405764
--
You received this bug
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262482/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262472/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262474/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and
I repeat, immediately after a reboot, audacity is not running. Are you
saying that audacity can prevent the system from recognizing my sound
hardware at boot just from being installed?
At the moment, sound works despite the audacity's configuration because
I ran "alsa force-reload'.
--
You
I'm a little confused here. What does audacity have to do with the fact
that there is no sound after a reboot? Audacity happens to be running
now...perhaps that's why it's the only program using ALSA. (Is ALSA
deprecated?) But audacity does not start automatically at boot, so it
is irrelevant
Public bug reported:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and persists now in 19.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
I've manually applied the patch proposed in comment #22 to my Ubuntu
18.10 desktop, and I can confirm that it fixes the issue for me. I
haven't seen any regression either, although my testing has been very
limited so far.
I've been experiencing this bug ever since Ubuntu 18.04 when
disconnecting
Hi, I no longer use TB and so I cannot confirm how is this working,
please feel free to close this report if you see it fit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1067446
Just FYI if it can help you guys in any way (I do know this is an Ubuntu
forum), I'm adding a confirmation that this is not Ubuntu specific. I've
also reproduced it in Fedora 27 under Wayland with 3 monitors: left
horizontal, middle vertical (rotated right), right horizontal. There's
algo an open
*** This bug is a duplicate of bug 1720400 ***
https://bugs.launchpad.net/bugs/1720400
It happenned just after adding a Google account.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Bueno, no entiendo un pomo de computadoras más que lo básico pero no sé por qué
me parece más amigable ubuntu. No obstante no me deja borrar programas desde
hace un tiempo y ni idea por qué.
También creo que tengo algunos errores pero no sé como solucionarlos. Si
alguien me proporciona ayuda,
Public bug reported:
No me deja instalar ese paquete. Ni idea mucho de Ubuntu ni de ingles.
Saludos
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-filters (not installed)
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic i686
ApportVersion:
I can confirm #69, using "killall nautilus" from terminal helps
--
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/1021375
Title:
Nautilus says the USB stick is read only when it is not
Updated appstream & libappstream3 to version 0.9.4-1ubuntu1, and
libappstream-glib8 to 0.5.13-1ubuntu1 just in case... Fixed for me.
Thanks you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
I have updated the BIOS. After this update the problem no longer
occurs.
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in
+1
German (legacy) brings back the dead key function for now, but I agree
with umehlig. A possible removal in the future should not happen, and
shunting the dead key function to the legacy keyboard layout is not a
nice solution.
--
You received this bug notification because you are a member of
Public bug reported:
I recently updated my Ubuntu version. Before it was working generally
(though I did experience a sporadic crash---don't know if that was
related).
Now after updates the log in display appears but when I attempt to
actually log in the screen clears to black, and then the
Mine says Network controller: Intel Corporation Centrino Advanced-N
6200 (rev 35).
It's almost the same chipset; mine (6200) is 802.11a/g/n certified,
whereas Anders' (6205) is 802.11a/b/g/n.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Public bug reported:
Ubuntu 14.04 LTS
wpasupplicant 2.1-0ubuntu1
wpa_supplicant is writing to syslog every couple of minutes. Example
output:
May 25 19:57:18 ubuntu wpa_supplicant[1161]: wlan0: CTRL-EVENT-SCAN-STARTED
May 25 19:57:23 ubuntu wpa_supplicant[1161]: nl80211:
I get the same error when running the trackballs program, which might
be easier to investigate since it's freely available.
Is there anything else I can do to shed light on this? Additional
tests I could run? Problem is 100% repeatable.
--
You received this bug notification because you are a
root# dpkg -S gs_fonts.ps
libgs9-common: /usr/share/ghostscript/9.10/Resource/Init/gs_fonts.ps
root# dpkg -l | grep libgs9-common
ii libgs9-common9.10~dfsg-0ubun all interpreter for the
PostScript language and f
root# dpkg -l | grep libgs9-common
ii libgs9-common
Why wouldn't sudo apt-get install package install all of the package's
dependencies? I didn't want to potentially install a bunch of extra
stuff from -proposed. I vaguely recall that when I upgraded ghostscript
that it did in fact install some other things.
--
You received this bug
I'm a little confused. I reverted my patch to
/usr/share/ghostscript/9.10/Resource/Init/gs_fonts.ps and then I
installed the proposed package, I think.
[code]
% dpkg -l | grep ghost
ii ghostscript 9.10~dfsg-0ubuntu10.1 amd64
interpreter for the
Public bug reported:
When searching for fonts ghostscript issues the error Error: /typecheck
in /findfont: and aborts.
This appears to be a bug in ghostscript having to do with .woff files.
http://bugs.ghostscript.com/show_bug.cgi?id=695031
I applied the patch given above and it fixed the
Public bug reported:
I'm trying to run a game called braid. I previously ran this game
successfully under 12.04 with my nVidia card using the proprietary
drivers, and I have also run it under 13.10 on a different box with a
different nVidia card. Now with 14.04 intel graphics finally actually
Public bug reported:
I have Ubuntu Desktop 64-bits 13.10 and 14.04.
I'm not able to see network traffic on gnome-system-monitor and/or nmon. In
both cases they are always in zero.
Network is working ok. Common web-browsers and BitTorrent are able to inform
the network traffic for their
When I tried to create the requested log, the sound wasn't working at
all. I rebooted...and then X wasn't working. The dust has settled now
and the sound bug seems to be fixed (after persisting through several
reboots and lasting for a couple months) so I guess the bug should be
closed.
--
You
Public bug reported:
I have used this USB mic (part of a webcam) for years under linux and it
has worked fine. Some recent changes seem to have broken it, and it has
never worked under 13.04.
Note also that today when I decided to try to report the bug the
behavior was a little different than
** Branch unlinked: lp:aptdaemon
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-center in Ubuntu.
https://bugs.launchpad.net/bugs/499937
Title:
[master] install/remove buttons don't react when policykit is not
running
Public bug reported:
Screen freezes continuously (let's say, once every 3 or 4 minutes),
mouse/trackpad and keyboard are unresponsive. Sometimes I need to do a
hard reboot. It happens since last kernel update to 3.5.0-26.42
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package:
Public bug reported:
I'm installing ati driver for HD 3100 radeon card
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: fglrx 2:8.970-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic i686
.tmp.unity.support.test.0:
ApportVersion:
This is still not fixed in Ubuntu 12.04 Precise. System monitor version
3.4.1.
See attachment.
** Attachment added: historico.png
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/460021/+attachment/3470346/+files/historico.png
--
You received this bug notification
This should be set and forget. I have to reconnect manually every
time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-pptp in Ubuntu.
https://bugs.launchpad.net/bugs/236576
Title:
Add feature reconnect on hangup
STAtions, this way it can associate to multiple APs
simultaneously. In that case we could even round robin connections and have
bandwidth incremented.
Regards,
Mariano
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu
Public bug reported:
After upgrading to Thunderbird 16.0.1 (via normal Ubuntu upgrade
process) one of the xmpp accounts I use to chat via Thunderbird gets
disconnected all the time although it is hard to pinpoint when it
happens: maybe after I don't use it for some minutes, when I go to the
tab
I have more data on this: each time I talk with somebody, the xmpp
account closes after 10 minutes of idle status.
Let me show an example (copy paste from the chat window, I am Me and
Sergio is my buddy):
04:50:54 PM - Me: son diccionarios ya listos para ir sumando de a uno
04:51:05 PM - Me:
Public bug reported:
I installed ubuntu 12.10. First I only have Unity so there is nothing to
choose in lightgdm. Then I installed gnome shell. So I have gnome shell,
gnome fallback, gnome fallback with no effects and unity. I can only
choose the last 2. When I click on gnome shell or gnome
It seems to be related to the network-manager-applet UI, and not the
underlying service/infraestructure. Restarting network-manager service
doesn't restore the VPN menu items.
And while the applet is broken, you can still turn the VPN connections
up and down with nmcli. In that case the applet
** Changed in: empathy (Ubuntu)
Assignee: (unassigned) = mariano perez gallardo (marianoperezgallardo)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to empathy in Ubuntu.
https://bugs.launchpad.net/bugs/889094
Title:
empathy
:00 2011
ExecutablePath: /usr/bin/empathy
ProcEnviron:
PATH=(custom, no user)
LANG=es_ES.UTF-8
SHELL=/bin/bash
SourcePackage: empathy
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: empathy (Ubuntu)
Importance: Undecided
Assignee: mariano perez gallardo
Hi everybody. I solved the problem unistalling pulseaudio, as I use
ALSA. Try to write killall pulseaudio in Terminal. If you can hear the
sound later, then you know what is causing the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is
job.
mariano
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/834164
Title
74 matches
Mail list logo
