** Changed in: mutter (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1880405
Title:
Unresponsive GUI and journal flooded
This problem is still in 20.04.1, but appears to have been fixed in
master udisk2, patching from 10 mins to 60 mins.
https://github.com/storaged-project/udisks/issues/407#ref-commit-326b182
I assume this is in 21.x, but not available in LTS (?)
As a workaround, you can turn off the smarts
Sorry should have been:
smartctl -s on /dev/sdX.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899361
Title:
udisk prevent disk from standby, standby timer is broken
Status in
Rocko,
Slightly OT
I see a variety of behaviour., based on the disks.
On 14.04 with the 30min polling patch: If you set the spindown to 15
mins and poll at 30, all of my disks spin down and stay down ( see list
above).
If you set the spindown to 5 and polling to 10, I have problems with
the
Happening in evince and xpdf for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1317599
Title:
Evince doesn't show fi-ligatures in a pdf file
Status in “evince” package in
Can confirm that the SMART polling by udisk2 every 10 mins appears to
reset the sleep timer on all of my disks: So all disks are kept awake by
SMART polling where sleep timer 10 mins. As previously stated later WD
disks have a minimum sleep timer of 10 mins ( hdparm -S120 /dev/sdx)
defaults to
--- udiskslinuxprovider.c 2014-05-02 13:54:46.826781083 +0100
+++ udiskslinuxprovider.c.30minpoll 2014-05-02 13:55:54.034178153 +0100
@@ -465,8 +465,8 @@
g_list_free_full (udisks_devices, g_object_unref);
udisks_info (Initialization complete);
- /* schedule housekeeping for
Public bug reported:
When I start banshee, sometimes it hangs. I do killall -SIGQUIT
banshee. I've attached the log file.
** Affects: banshee (Ubuntu)
Importance: Undecided
Status: New
** Tags: banshee mtp
** Attachment added: Banshee log
I did run that command. If it happens again I'll make doubly sure.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/1196828
Title:
Cannot restart banshee after crash
Status in
Agreed the situation wouldn't be much better in terms of playing music
but I think banshee's behaviour could be. At the moment Ubuntu appears
not to work as I try to start banshee and nothing happens (not even an
error message). Are there no system calls that can return errors instead
of
Here's the log you asked for.
** Attachment added: debug log as asked for
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/1196828/+attachment/3742400/+files/log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in
I think better than rebooting might be unmounting the network share.
I'll try that next time.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/1196828
Title:
Cannot restart banshee
Is it really solved though? Despite the problem being caused by a
cifs/nfs error, banshee's behaviour is still quite bad. A GUI shouldn't
really be unresponsive even if there are network problems behind the
scenes. BTW I have been running using a NFS mount instead of CIFS mount
for a few days now
Thanks for the pointers. I'm pretty convinced it happens when there is a
problem with my network mounted filesystem (/etc/fstab):
//192.168.1.74/music/mnt/htpc-music cifs
noauto,credentials=/etc/samba/user,noexec,uid=john,gid=john 0 0
The advice in the noah.org article looks
Public bug reported:
I was running banshee in debug mode when it crashed with a message about a
locked databse.
a
john@W530$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 13.04
Release:13.04
Codename: raring
john@W530$ dpkg -l |
john@W530$ lsof ~/.config/banshee-1/banshee.db
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
unity-mus 2969 john9u REG 252,1 45050880 401760
/home/john/.config/banshee-1/banshee.db
banshee 25995 john9u REG 252,1 45050880 401760
Here is the current ps output:
john@W530$ ps -ef|grep banshee
john 2170 1711 0 17:58 pts/21 00:00:00 grep --color=auto banshee
john 25995 15673 4 13:00 pts/700:14:35 [banshee] defunct
--
You received this bug notification because you are a member of Desktop
Packages, which is
Banshee crashed again but the process didn't disappear. Here's the log
for the banshee I'm trying to start.
john@W530$ banshee --debug
** Running Mono with --debug **
[1 Debug 17:54:39.785] Bus.Session.RequestName ('org.bansheeproject.Banshee')
replied with InQueue
I've attached the log for
Good point, I didn't check the output too closely. 15673 is the bash
shell I started banshee from:
~/Downloads
john@W530$ ps -ef|grep 15673
john 4724 4624 0 18:59 pts/21 00:00:00 grep --color=auto 15673
john 15673 10712 0 Jul09 pts/700:00:00 bash
john 25995 15673 4 13:00
OK I can try and kill bash but I'd like to know what to do when the
parent is 1. That is the problem and forces me to reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/1196828
Killing bash make the PPID 1 and banshee won't start
~/Downloads
john@W530$ kill 15673
~/Downloads
john@W530$ kill -9 15673
~/Downloads
john@W530$ ps -ef|grep banshee
john 6435 4624 0 20:04 pts/21 00:00:00 grep --color=auto banshee
john 25995 1 3 13:00 ?00:14:35
I see this on that link you provided: init can never have zombie
children. From the wikipedia article: When a process loses its parent,
init becomes its new parent. Init periodically executes the wait system
call to reap any zombies with init as parent. One of init's
responsibilities is reaping
See link to askubuntu question for ps output but I don't see what you
can learn from that. I'm not sure it is a banshee bug either. Banshee is
dead but why cannot I start another banshee process?
--
You received this bug notification because you are a member of Desktop
Packages, which is
23 matches
Mail list logo
