This has shown up again in 18.04.
dpkg: warning: version '/etc/lsb-release' has bad syntax: version number
does not start with digit
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"
--
You received this bug
I also have this issue on 16.04. I can restart plasmashell, but this
only fixes the issue for a few hours, not good when I usually leave my
machine running for week on end.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is definitely an issue on 16.04. If I kill plasmashell and restart
it again the problem go away for about 6 hours then slowly returns.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592668
This bug seems to have risen it's ugly little head again in 12.04. I'm
getting the exact same problem I was getting in 11.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883585
Title:
Kubuntu
I'm also getting this segfault in /var/log/syslog:
May 26 10:33:19 odyssey kernel: [ 2602.050199] VirtualBox[9318]:
segfault at 29 ip 7fb3c13b4b8c sp 7fff7115ffd8 error 4 in
libQtCore.so.4.7.4[7fb3c12ed000+292000]
--
You received this bug notification because you are a member of Kubuntu
At this point you should just be able to do an update on your machine and
get the fixed packages.
On Tue, Jan 3, 2012 at 9:54 AM, Antonio Sánchez
883...@bugs.launchpad.netwrote:
Please, how can I install the fix released?
I have updated my system according to
Martin,
That looked better, I went ahead and installed them, but I did it remotely,
so I will need to wait till I get home and reinstall the printer to see if
it will work.
Thanks
$ sudo apt-get install -t oneiric-proposed cups | tee apt-get.out
Reading package lists...
Building dependency
Martin,
It worked, I can access my printer through cups now.
The device URI: dnssd://EPSON%20Stylus%20NX410%20on%20nas-
storage._ipp._tcp.local/
I still need to test it with a USB connected printer, but I need to wait
a few days for a new Toner Cartridge to arrive before I can run the
test.
Martin,
After setting up oneiric-proposed as per your link and running:
$ sudo aptitude install cups/oneiric-proposed
aptitude wanted to update/remove over 500 packages that were not in the
proposed repository. Obviously I said NO to this. If it only wanted to
update 6 or 7 packages I'd have
I am also getting the same thing in my NAS log:
E [12/Nov/2011:00:59:27 -0500] get_printer_attrs: resource name '/Stylus_NX410'
no good!
E [12/Nov/2011:00:59:27 -0500] get_printer_attrs: resource name '/Stylus_NX410'
no good!
E [12/Nov/2011:00:59:28 -0500] get_printer_attrs: resource name
Right that did it. My printer now works using smb://, but I would still
like to see this bug fixed so it will work with cups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883585
Title:
Kubuntu
I also am printing to a NAS cups server. I wonder if the cups server on
the NAS is, somehow, not compatible with the cups server on my laptops?
Humm, I'll have to test out that theory, by connecting the printer to my
server instead of the NAS. This may also explain the errors I saw in the
network
Public bug reported:
Description:Ubuntu 11.10
Release:11.10
This is a very serious bug most likely in cups itself. Any printer
connected either over a network or directly onto the machine can be
found, but will not print. The print job stays in the queue forever.
There are many
** Description changed:
Description:Ubuntu 11.10
Release:11.10
This is a very serious bug most likely in cups itself. Any printer
connected either over a network or directly onto the machine can be
found, but will not print. The print job stays in the queue forever.
** Description changed:
Description:Ubuntu 11.10
Release:11.10
This is a very serious bug most likely in cups itself. Any printer
connected either over a network or directly onto the machine can be
found, but will not print. The print job stays in the queue forever.
-
Yes most likely it is related as portmap is used in NFS and it must be
running for NFS to work.
~Carl
On Wed, Sep 22, 2010 at 3:46 PM, Josh Brown 590...@bugs.launchpad.net wrote:
I'm not sure if this is related, but I found this in my
/var/log/boot.log file:
init: portmap main process (771)
OK, I waited a day to see how the changes I made to the /etc/aliases
file went and that seemed to solve the issue with dovecot trying to do
things in the /root/ dir.
There is still the issue where dovecot will NOT listen to port 995
either locally or externally.
$ openssl s_client -connect
$ ls -dl /etc/ssl/certs/ssl-cert-snakeoil.pem
-rw-r--r-- 1 root root 660 2010-01-27 22:39 /etc/ssl/certs/ssl-cert-snakeoil.pem
$ sudo ls -dl /etc/ssl/private/ssl-cert-snakeoil.key
-rw-r- 1 root ssl-cert 891 2010-01-27 22:39
/etc/ssl/private/ssl-cert-snakeoil.key
OK, it seems removing both
I suppose that
ssl_listen = *:995
would have worked.
So I have dovecot working now I cannot access postfix through smpts port
465. Almost the same problem I had with dovecot.
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
OK, I waited a day to see how the changes I made to the /etc/aliases
file went and that seemed to solve the issue with dovecot trying to do
things in the /root/ dir.
There is still the issue where dovecot will NOT listen to port 995
either locally or externally.
$ openssl s_client -connect
$ ls -dl /etc/ssl/certs/ssl-cert-snakeoil.pem
-rw-r--r-- 1 root root 660 2010-01-27 22:39 /etc/ssl/certs/ssl-cert-snakeoil.pem
$ sudo ls -dl /etc/ssl/private/ssl-cert-snakeoil.key
-rw-r- 1 root ssl-cert 891 2010-01-27 22:39
/etc/ssl/private/ssl-cert-snakeoil.key
OK, it seems removing both
I suppose that
ssl_listen = *:995
would have worked.
So I have dovecot working now I cannot access postfix through smpts port
465. Almost the same problem I had with dovecot.
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
Yes port 110 only, but no matter what I do it will not listen to port
995.
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
https://bugs.launchpad.net/bugs/623520
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Sorry for putting this directly into the post, but I was not on site
when I ran the command and it was a lot easier to just grab the screen
output an past it in.
These are the certs and keys on my box.
$ ll /etc/ssl/certs/ssl-mail.pem
lrwxrwxrwx 1 root root 36 2010-07-28 22:19
I know I'm not the only person getting this issue. It was said the issue
is that the /etc/aliases file needs to point to a valid user on the
system other that root. This I fix, but dovecot doesn't seem to listen
to this even after bouncing both postfix and dovecot.
The error below will show up in
Yes port 110 only, but no matter what I do it will not listen to port
995.
--
dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
https://bugs.launchpad.net/bugs/623520
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Sorry for putting this directly into the post, but I was not on site
when I ran the command and it was a lot easier to just grab the screen
output an past it in.
These are the certs and keys on my box.
$ ll /etc/ssl/certs/ssl-mail.pem
lrwxrwxrwx 1 root root 36 2010-07-28 22:19
I know I'm not the only person getting this issue. It was said the issue
is that the /etc/aliases file needs to point to a valid user on the
system other that root. This I fix, but dovecot doesn't seem to listen
to this even after bouncing both postfix and dovecot.
The error below will show up in
Public bug reported:
If dovecot -n is executed it will show the wrong settings. In other words it
seems to be ignoring what is in the /etc/dovecot/dovecot.conf
completely. For example I only have pop3s set in protocols but it is
permitting everything. Also the wrong certs are being used not
Yes the dovecot-postfix package is installed. I'm am using 10.04 Lucid.
I updated the file in /etc/dovecot/conf.d to what I want, now dovecot -n
gives me the right info, but I still get this:
$ openssl s_client -connect localhost:995
connect: Connection refused
connect:errno=111
This also
Public bug reported:
If dovecot -n is executed it will show the wrong settings. In other words it
seems to be ignoring what is in the /etc/dovecot/dovecot.conf
completely. For example I only have pop3s set in protocols but it is
permitting everything. Also the wrong certs are being used not
Yes the dovecot-postfix package is installed. I'm am using 10.04 Lucid.
I updated the file in /etc/dovecot/conf.d to what I want, now dovecot -n
gives me the right info, but I still get this:
$ openssl s_client -connect localhost:995
connect: Connection refused
connect:errno=111
This also
This is the same bug as 590570, but this one has been around longer.
I think the real issue underlying this bug is in bug 525154 which
relates to a race condition while starting portmap which in turn starts
statd. This only seems to be an issue if you have /var as a separate
mount point where
Post 13 in bug 525154 above has solved the issue with statd, but now
autofs is failing to start. I tried to something similar with
/etc/init/autofs.conf but to no avail. Still no joy here.
k3nt-1 are you seeing the error messages in your /var/logs/boot.log file
that I posted above?
--
autofs
This is the same bug as 590570, but this one has been around longer.
I think the real issue underlying this bug is in bug 525154 which
relates to a race condition while starting portmap which in turn starts
statd. This only seems to be an issue if you have /var as a separate
mount point where
This seems to be the cause of both bugs 573919 and 590570.
--
mountall for /var races with rpc.statd
https://bugs.launchpad.net/bugs/525154
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Post 13 in bug 525154 above has solved the issue with statd, but now
autofs is failing to start. I tried to something similar with
/etc/init/autofs.conf but to no avail. Still no joy here.
k3nt-1 are you seeing the error messages in your /var/logs/boot.log file
that I posted above?
--
autofs
This seems to be the same bug as in 573919 where statd is not started.
If you look in /etc/init/portmap.conf you will see that its prerequisite
for starting is statd which must have been started when I used one of
the two methods mentiond above to restart portmap.
I have found this in my
If you look in /etc/init/portmap.conf you will see that its prerequisite
for starting is statd which is done in /etc/init/portmap.conf. However,
there are numerous errors in my /var/log/boot.log file.
I upgraded two machines and both have the same issue as mentioned above.
A new install I did
Some more recent info on this bug:
A complete stop and start of portmap will also get things working. So
here's the current situation. Either do a
$ sudo service portmap stop
$ sudo service portmap start
or
$ sudo dpkg-reconfigure portmap choose No
$ sudo service portmap restart
will get
Portmap is always running.
To restart portmap I use:
$ sudo service portmap restart
The time stamps have not changed since I last reconfigured portmap.
I am seeing behavior I have never seen before on two machines after
upgrades. A third machine was a fresh install and doesn't exhibit this
** Description changed:
Binary package hint: portmap
I am running automount (autofs) for my NFS mounts. When I log out then
back in I cannot get to the mounts any more. I need to run
$ sudo dpkg-reconfigure portmap choose No
$ sudo service portmap restart
to get them working
Public bug reported:
Binary package hint: portmap
I am running automount (autofs) for my NFS mounts. When I log out then
back in I cannot get to the mounts any more. I need to run
$ sudo dpkg-reconfigure portmap choose No
$ sudo service portmap restart
to get them working again. Restarting
I have finally physically got to where the machine is and rebooted it
after making the changes to /etc/pam.d/common-auth. This has solved the
issues I originally posted here. It has not solved the portmap issues I
mentioned above which indeed seems to be a completely separate issue.
Daniel thanks
I have finally physically got to where the machine is and rebooted it
after making the changes to /etc/pam.d/common-auth. This has solved the
issues I originally posted here. It has not solved the portmap issues I
mentioned above which indeed seems to be a completely separate issue.
Daniel thanks
I had found mention of gdm being a related issues, but it wasn't
running on my server which I would expect because it's a server.
I am also running samba so I edited the file you mentioned and added the
auth methods = guest sam winbind
line to the [global] settings. However, I'm not physically
An additional issue I have found is that often when I need to use sudo
the screen locks up immediately after I type in my password. On occasion
it will time out, but most times I need to log in again and kill the
session.
--
Lucid server upgrade login times out
Public bug reported:
I have just upgraded a server running 9.10 to 10.04. When Ubuntu comes
up and I try to log in with the same username and password I have used
before I get Login timed out after 60 seconds. However, if I try
multiple times it will eventually let me in. I had set up ssh tokens
I'm still here. I hope to be testing this off a live CD this weekend
(2010-05-22/23). I'll be deprecating this machine soon, so hardy will
be the last version that will ever be on it. The monitor will be going
soon also as it won't be needed anymore.
~Carl
On Fri, May 21, 2010 at 1:48 PM, Bryce
be way off on this, but maybe there is germ is truth it it.
~Carl
On Fri, May 21, 2010 at 2:06 PM, Carl Nobile carl.nob...@gmail.com wrote:
I'm still here. I hope to be testing this off a live CD this weekend
(2010-05-22/23). I'll be deprecating this machine soon, so hardy will
be the last
This is also happening with virt-manager, but as it has been mention has
no effect on the running of the application.
--
g_set_prgname() called multiple times
https://bugs.launchpad.net/bugs/501670
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
51 matches
Mail list logo
