I have this problem in Hardy, too. In my case the errors reappear after
Rhythmbox is restarted.
My Music folder is symlinked to a samba share on my Hardy-Server.
--
Symbolic links cause file import errors
https://bugs.launchpad.net/bugs/185362
You received this bug notification because you are
Hello.
Sorry, but i don't know how to get a debug log. I only see the entries in the
section Import errors.
Could you explain how i can get such a debug log? thanks.
--
Symbolic links cause file import errors
https://bugs.launchpad.net/bugs/185362
You received this bug notification because you
Ok.
I've got an debug.log and attached it on this post.
** Attachment added: Debug.log of rhythmbox
http://launchpadlibrarian.net/15337866/debug.log
--
Symbolic links cause file import errors
https://bugs.launchpad.net/bugs/185362
You received this bug notification because you are a member
Hello.
I had this problem too, until today.
On high load my nic (realtek 8169) cut the connection. I've add acpi=off
to the /boot/grub/menu.lst at the ende of the kernel line. After
rebooting the system i have copy 10 GB and 27 GB to my server without
any transmit error.
Perhaps somebody can
h...@all.
I have the same problem with my openoffice files, as described in this
bug. I have it since I updated my NFS-server from Hardy to Lucid. With
NFS on Hardy and OpenOffice on my Lucid-Client everything worked fine.
My workaround is to mount the nfs share with the nolock option on my
I have the problem on Ubuntu 13.10 / Pidgin 2.10.7 / pidgin-otr 4.0.0-1,
too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/303862
Title:
Pidgin freezes when generating new OTR private key
To
entropy for /dev/random. After 1-2 minutes
the key was created successfully.
I agree with Paul that there should be a hint for the user what to do,
to get the key generated.
Cheers,
Tronde
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: lsb_release-a.txt
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1315425/+attachment/4103454/+files/lsb_release-a.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1315425/+attachment/4103457/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315425
** Attachment added: uname-r.txt
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1315425/+attachment/4103455/+files/uname-r.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315425
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1315425/+attachment/4103456/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315425
driver - version 331.38
I use GNOME Shell 3.10.4 and kernel 3.13.0-24-generic.
Does this happen to anybody else?
Regards
Tronde
** Affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: gnome-shell-version.txt
https://bugs.launchpad.net/bugs
Hello.
I can confirm this Bug for Ubuntu GNOME 14.04 (Trusty) with network-
manager 0.9.8.8-0ubuntu7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1104476
Title:
Network manager cannot connect to
Well, you're lucky. For me this happens every time I try to shutdown or
reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315425
Title:
Cannot shutdown or reboot system from Gnome or
I was able to reproduce the issue on a fresh install of Xenial today.
You could find the degug log at: https://paste.ubuntuusers.de/423433/
** Changed in: autofs (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
uot; After running `sudo systemctl restart
autofs.service` it works like a charme.
Here is my '''/etc/auto.master.d/diskstation.autofs''':
~~~
/home/tronde/diskstation /etc/auto.diskstation
~~~
And my '''/etc/auto.diskstation''':
~~~
music -fstype=cifs,uid=1000,credentials=/home/tronde/.smbc
and the system shuts
down like expected. Please, update the version of davfs2 in universe to
version 1.5.4 or backport the fixes which lead to the solution.
Best Regards,
Tronde
** Affects: davfs2 (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-software-version
** Package changed
Would there be an updated version in the next xenial point release? Is
there any chance to get autofs (5.1.2-1) at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
autofs
The tag upgrade-software-version was added first and then removed again.
Could you explain why, please?
Is there any chance to get an updated version of davfs2 in xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Is it possible to update or rebase the openssh package in Xenial to at
least version 7.3?
Besides the bugfixes in this release I would like to use the ProxyJump
option introduced in this version. See [OpenSSH 7.3](
https://www.openssh.com/txt/release-7.3) for further
This bug seems to be fixed upstream in a newer version: [Debian Bug report logs
- #865770
openssh-server fails to validate configuration before reloading, under
systemd](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865770)
Maybe it is possible to get a version update in Xenial?!
** Bug
Public bug reported:
After adding some lines to /etc/ssh/sshd_config I tried to reload the
configuration with the command:
```
sudo systemctl reload sshd
```
No error message was returned. So I assumed that the sshd was running
with the current config. But `sudo systemctl status sshd` told me
I've just checked in Bionic:
~~~
$ uname -rvsop
Linux 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64
GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04
Codename:
Hi there,
I tested version 1:7.2p2-4ubuntu2.5 from proposed but the issue still
exists. Behavior is exactly as before.
Regards,
Tronde
** Tags removed: verification-needed-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member
Public bug reported:
Description:Ubuntu 16.04.4 LTS
Release:16.04
logrotate:
Installiert: 3.8.7-2ubuntu2.16.04.2
Installationskandidat: 3.8.7-2ubuntu2.16.04.2
The URL to the project Homepage is wrong:
~~~
Homepage: https://fedorahosted.org/logrotate/
~~~
The URL
Today I've checked in Xenial with autofs 5.1.1-1ubuntu3.1. So far it
seems to be working here as well. I would guess this bug is fixed then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
d in the snoop I see the expected packages crossing the network.
That's it. I do not know what else I could do to help with this matter.
If you need additional information tell me what you need, please.
Regards,
Tronde
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Good Moring,
I would like to add some news. I have removed and purged autofs from one
of my Thinkpads and installed autofs 5.1.2-1 from Bionic in Xenial. I
have used the packages from
http://archive.ubuntu.com/ubuntu/pool/main/a/autofs/autofs_5.1.2-1ubuntu2_amd64.de
Surprise, the behaviour is
Hi,
I would like to confirm that this bug affects Xenial, too. Both conditions from
#5 are fulfilled, too. To work around I follow the suggestion from #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, I'm lost. Today I've checked in another Xenial with autofs
5.1.1-1ubuntu3.1. Kernel is 4.4.0-116-generic as in the system of my
last post. But in this system I have to restart autofs.service each time
after a (re)boot otherwise I cannot access the shares. I really don't
get it.
Maybe some
Hi,
Thank you very much for the backport of davfs2 1.5.4-2.
For testing purposes it is ok to use a PPA. I could test the package and
give feedback here. But for production using a PPA is not an option. If
the backport is stable I would like to get an update in the universe
repo, too.
--
You
Is there anything else to do? Any chance to get a version update in
Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40189
Title:
[SRU] [xenial] autofs needs to be restarted to pick up
@ahasenack, of course I could double check. I've done so a few minutes
ago and you are right. After trying to reload with a corrupted config
file the reload failed but the service is still up and running.
Please see the following output for confirmation:
~~~
root@vbox-xenial:~# systemctl status
Ubuntu 18.04.1 with autofs version 5.1.2-1ubuntu3 --> Still the same problem.
Service restart is required to get autofs to work.
How could I help to triage this bug? What information are needed to help
reproduce it so it could be fixed?
--
You received this bug notification because you are a
Wow, six years and still now solution or even someone working on this. I
suffer from this bug on the latest versions of 16.04 and 18.04. Newer
versions I did not test, yet.
What is needed, that this bug is processed, triaged and maybe resolved?
--
You received this bug notification because you
35 matches
Mail list logo
