[Bug 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597466 Title: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1597466/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597792] Re: plasmashell high CPU usage (100%+)
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. https://bugs.launchpad.net/bugs/1597792 Title: plasmashell high CPU usage (100%+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1597792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592668] Re: plasmashell is eating 100% cpu and all UI is slow
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 Title: plasmashell is eating 100% cpu and all UI is slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1592668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762006] Re: current libqt4-opengl breaks virtualbox (again)
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 Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/762006 Title: current libqt4-opengl breaks virtualbox (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/762006/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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.net>wrote: > Please, how can I install the fix released? > > I have updated my system according to http://www.kubuntu.org/kde-sc-474. > I guess that is oneiric-updates repository. > > After downloading 150Mb I tried to install 'oneiric-proposed' but apt- > get complains with something like "invalid for APT::Default-Release as > that version is not available in the sources". > > How should I proceed? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/883585 > > Title: > Kubuntu 11.10 -- Network/Local Printers found but cannot print - > Unable to get printer status > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions > -- --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- 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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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. I'm glad there is a solution to this issue. -- 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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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 tree... Reading state information... The following extra packages will be installed: cups-bsd cups-client cups-dbg Suggested packages: cups-pdf xpp The following packages will be upgraded: cups cups-bsd cups-client cups-dbg 4 upgraded, 0 newly installed, 0 to remove and 51 not upgraded. Need to get 4,713 kB of archives. After this operation, 41.0 kB disk space will be freed. Do you want to continue [Y/n]? On Tue, Dec 6, 2011 at 7:49 AM, Robert Bradley wrote: > Stefan: I don't know if this will help at all, but there's a suggestion > at http://www.makestuff.eu/wordpress/?p=1747 about blacklisting the > usblp module. Perhaps that might be worth trying? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/883585 > > Title: > Kubuntu 11.10 -- Network/Local Printers found but cannot print - > Unable to get printer status > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions > -- --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- 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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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 done it, but 500 make me a bit queasy. Sorry, but this a non-starter for me, if there is a way to get around this issue and install the cups packages please let me know. -- 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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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 '/Stylus_NX410' no good! E [12/Nov/2011:00:59:28 -0500] get_printer_attrs: resource name '/Stylus_NX410' no good! E [12/Nov/2011:00:59:28 -0500] get_printer_attrs: resource name '/Stylus_NX410' no good! E [12/Nov/2011:00:59:28 -0500] get_printer_attrs: resource name '/Stylus_NX410' no good! And as my initial post above showed that there were errors in the request/response data between the client and server. However, also as I mentioned above even when I plugged a printer into the laptop itself the laptop couldn't print to it. In this case it was an old HP Deskjet-880C, so this is not just an issue between two cups servers of different versions. That said, tracking down the issues on the network might lead to what the major problem is. One other interesting this, I never hand edited the /etc/cups/cupsd.conf, but when I run cupsd -t I get errors. $ cupsd -t /etc/cups/cupsd.conf contains errors One additional piece of into is that when I machine set up the printer it did not use ipp://, but dnssd:// as the schema. -- 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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
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 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Printers found but cannot print
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 traffic between the two I listed above. However, I connected a printer directly to the laptop and that didn't work either. As far as using something other than cups you could always fall back to an LPD server, but the configuration will drive you nuts. In most cases you would have to write you own /etc/printcap file. Plus there are so many other apps in Ubuntu/Kubuntu that depent on cups being there that you may not be able to do it at all anymore. BTW, I have the exact same symptoms as you, which is another reason I believe there is a bug in cups code somewhere. -- 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 11.10 -- Printers found but cannot print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Printers found but cannot print
** 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. - There are many reports of this, but most people thing it's just their + There are many reports of this, but most people think it's just their own printer. Below are posts I made to other sites on this issue. - I'm getting the same issues and it seems to be printer independent. My printer is an HP Stylus 415. It worked fine on Natty, but on 11.04 I can set it up on the network but nothing will print to it. This is in the cups log: /var/log/cups/error_log D [18/Oct/2011:22:59:28 -0400] [Job 30] Getting supported attributes... D [18/Oct/2011:22:59:28 -0400] [Job 30] Get-Printer-Attributes: server-error-internal-error (Unknown) D [18/Oct/2011:22:59:28 -0400] [Job 30] Get-Printer-Attributes returned server-error-internal-error. E [18/Oct/2011:22:59:28 -0400] [Job 30] Unable to get printer status. This is also in the system log: /var/log/syslog Oct 19 19:50:40 odyssey kernel: [38119.579286] type=1400 audit(1319068240.145:24): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=4528 comm="apparmor_parser" Oct 19 19:50:40 odyssey kernel: [38119.580556] type=1400 audit(1319068240.149:25): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=4528 comm="apparmor_parser" Oct 19 19:50:40 odyssey udev-configure-printer: add /module/lp Oct 19 19:50:40 odyssey udev-configure-printer: Failed to get parent - I have now tried an old HP DeskJet-880C directly to the USB port. I can configure it fine, but it won't print. This is the same results I get from my network printer an Epson NX415, as I mention above. So it seems not to be printer drivers or a connection issue. I'm betting there is a problem with the cups server itself. I compared the /etc/cups/cupsd.conf with the one on an older machine which has Kubuntu 10.04 on it and except for a few minor things they were exactly the same. I even swapped the old version to the new release with no changes. I burned 11.10 onto a thumb drive and booted it from my eeePC 900 and guess what? Yup, the printer doesn't work from there either. There is definitely something wrong with cups itself. - I am very surprised that this even made it out to a release of Kubuntu which is what I use. It may be happening to other variations of Ubuntu also, but this I have not tried. - Edit: Below is what happens after I try to print. It keeps going periodically for some time after I have canceled the print job. $ sudo tcpdump -i eth0 -vvn tcp port 631 - [sudo] password for : + [sudo] password for : tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 18:55:05.723564 IP (tos 0x0, ttl 64, id 3643, offset 0, flags [DF], proto TCP (6), length 60) - 192.168.1.105.41323 > 192.168.1.126.631: Flags [S], cksum 0x8466 (incorrect -> 0xbb90), seq 967441230, win 14600, options [mss 1460,sackOK,TS val 14742901 ecr 0,nop,wscale 6], length 0 + 192.168.1.105.41323 > 192.168.1.126.631: Flags [S], cksum 0x8466 (incorrect -> 0xbb90), seq 967441230, win 14600, options [mss 1460,sackOK,TS val 14742901 ecr 0,nop,wscale 6], length 0 18:55:05.723960 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) - 192.168.1.126.631 > 192.168.1.105.41323: Flags [S.], cksum 0xfa1d (correct), seq 4196584152, ack 967441231, win 5792, options [mss 1460,sackOK,TS val 407635588 ecr 14742901,nop,wscale 4], length 0 + 192.168.1.126.631 > 192.168.1.105.41323: Flags [S.], cksum 0xfa1d (correct), seq 4196584152, ack 967441231, win 5792, options [mss 1460,sackOK,TS val 407635588 ecr 14742901,nop,wscale 4], length 0 18:55:05.724002 IP (tos 0x0, ttl 64, id 3644, offset 0, flags [DF], proto TCP (6), length 52) - 192.168.1.105.41323 > 192.168.1.126.631: Flags [.], cksum 0x845e (incorrect -> 0x3ea2), seq 1, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 0 + 192.168.1.105.41323 > 192.168.1.126.631: Flags [.], cksum 0x845e (incorrect -> 0x3ea2), seq 1, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 0 18:55:05.724303 IP (tos 0x0, ttl 64, id 3645, offset 0, flags [DF], proto TCP (6), length 211) - 192.168.1.105.41323 > 192.168.1.126.631: Flags [P.], cksum 0x5733 (correct), seq 1:160, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 159 + 192.168.1.105.41323 > 192.168.1.126.631: Flags [P.], cksum 0x5733 (correct), seq 1:160, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 159 18:55
[Bug 883585] Re: Kubuntu 11.10 -- Printers found but cannot print
** 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. There are many reports of this, but most people thing it's just their own printer. Below are posts I made to other sites on this issue. - I'm getting the same issues and it seems to be printer independent. My printer is an HP Stylus 415. It worked fine on Natty, but on 11.04 I can set it up on the network but nothing will print to it. This is in the cups log: /var/log/cups/error_log D [18/Oct/2011:22:59:28 -0400] [Job 30] Getting supported attributes... D [18/Oct/2011:22:59:28 -0400] [Job 30] Get-Printer-Attributes: server-error-internal-error (Unknown) D [18/Oct/2011:22:59:28 -0400] [Job 30] Get-Printer-Attributes returned server-error-internal-error. E [18/Oct/2011:22:59:28 -0400] [Job 30] Unable to get printer status. This is also in the system log: /var/log/syslog Oct 19 19:50:40 odyssey kernel: [38119.579286] type=1400 audit(1319068240.145:24): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=4528 comm="apparmor_parser" Oct 19 19:50:40 odyssey kernel: [38119.580556] type=1400 audit(1319068240.149:25): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=4528 comm="apparmor_parser" Oct 19 19:50:40 odyssey udev-configure-printer: add /module/lp Oct 19 19:50:40 odyssey udev-configure-printer: Failed to get parent - I have now tried an old HP DeskJet-880C directly to the USB port. I can configure it fine, but it won't print. This is the same results I get from my network printer an Epson NX415, as I mention above. So it seems not to be printer drivers or a connection issue. I'm betting there is a problem with the cups server itself. I compared the /etc/cups/cupsd.conf with the one on an older machine which has Kubuntu 10.04 on it and except for a few minor things they were exactly the same. I even swapped the old version to the new release with no changes. I burned 11.10 onto a thumb drive and booted it from my eeePC 900 and guess what? Yup, the printer doesn't work from there either. There is definitely something wrong with cups itself. - I am very surprised that this even made it out to a release of Kubuntu which is what I use. It may be happening to other variations of Ubuntu also, but this I have not tried. + + - + Edit: Below is what happens after I try to print. It keeps going periodically for some time after I have canceled the print job. + + $ sudo tcpdump -i eth0 -vvn tcp port 631 + [sudo] password for : + tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes + 18:55:05.723564 IP (tos 0x0, ttl 64, id 3643, offset 0, flags [DF], proto TCP (6), length 60) + 192.168.1.105.41323 > 192.168.1.126.631: Flags [S], cksum 0x8466 (incorrect -> 0xbb90), seq 967441230, win 14600, options [mss 1460,sackOK,TS val 14742901 ecr 0,nop,wscale 6], length 0 + 18:55:05.723960 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 60) + 192.168.1.126.631 > 192.168.1.105.41323: Flags [S.], cksum 0xfa1d (correct), seq 4196584152, ack 967441231, win 5792, options [mss 1460,sackOK,TS val 407635588 ecr 14742901,nop,wscale 4], length 0 + 18:55:05.724002 IP (tos 0x0, ttl 64, id 3644, offset 0, flags [DF], proto TCP (6), length 52) + 192.168.1.105.41323 > 192.168.1.126.631: Flags [.], cksum 0x845e (incorrect -> 0x3ea2), seq 1, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 0 + 18:55:05.724303 IP (tos 0x0, ttl 64, id 3645, offset 0, flags [DF], proto TCP (6), length 211) + 192.168.1.105.41323 > 192.168.1.126.631: Flags [P.], cksum 0x5733 (correct), seq 1:160, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 159 + 18:55:05.724352 IP (tos 0x0, ttl 64, id 3646, offset 0, flags [DF], proto TCP (6), length 648) + 192.168.1.105.41323 > 192.168.1.126.631: Flags [P.], cksum 0x6142 (correct), seq 160:756, ack 1, win 229, options [nop,nop,TS val 14742901 ecr 407635588], length 596 + 18:55:05.724708 IP (tos 0x0, ttl 64, id 52317, offset 0, flags [DF], proto TCP (6), length 52) + 192.168.1.126.631 > 192.168.1.105.41323: Flags [.], cksum 0x3d3b (correct), seq 1, ack 160, win 429, options [nop,nop,TS val 407635588 ecr 14742901], length 0 + 18:55:05.724802 IP (tos 0x0, ttl 64, id 52318, offset 0, flags [DF], proto TCP (6), length 52) + 192.168.1.126.631 > 192.168.1.105.41323: Flags [.], cksum 0x3a9c (correct), seq 1, ack 756, win 504, options [nop,nop,TS val 407635588 ecr 14742901], length 0 + 18:55:05.736123 IP (tos 0x0, ttl 64, id 52319, offset
[Bug 883585] [NEW] Kubuntu 11.10 -- Printers found but cannot print
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 reports of this, but most people thing it's just their own printer. Below are posts I made to other sites on this issue. - I'm getting the same issues and it seems to be printer independent. My printer is an HP Stylus 415. It worked fine on Natty, but on 11.04 I can set it up on the network but nothing will print to it. This is in the cups log: /var/log/cups/error_log D [18/Oct/2011:22:59:28 -0400] [Job 30] Getting supported attributes... D [18/Oct/2011:22:59:28 -0400] [Job 30] Get-Printer-Attributes: server-error-internal-error (Unknown) D [18/Oct/2011:22:59:28 -0400] [Job 30] Get-Printer-Attributes returned server-error-internal-error. E [18/Oct/2011:22:59:28 -0400] [Job 30] Unable to get printer status. This is also in the system log: /var/log/syslog Oct 19 19:50:40 odyssey kernel: [38119.579286] type=1400 audit(1319068240.145:24): apparmor="STATUS" operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" pid=4528 comm="apparmor_parser" Oct 19 19:50:40 odyssey kernel: [38119.580556] type=1400 audit(1319068240.149:25): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/cupsd" pid=4528 comm="apparmor_parser" Oct 19 19:50:40 odyssey udev-configure-printer: add /module/lp Oct 19 19:50:40 odyssey udev-configure-printer: Failed to get parent - I have now tried an old HP DeskJet-880C directly to the USB port. I can configure it fine, but it won't print. This is the same results I get from my network printer an Epson NX415, as I mention above. So it seems not to be printer drivers or a connection issue. I'm betting there is a problem with the cups server itself. I compared the /etc/cups/cupsd.conf with the one on an older machine which has Kubuntu 10.04 on it and except for a few minor things they were exactly the same. I even swapped the old version to the new release with no changes. I burned 11.10 onto a thumb drive and booted it from my eeePC 900 and guess what? Yup, the printer doesn't work from there either. There is definitely something wrong with cups itself. - I am very surprised that this even made it out to a release of Kubuntu which is what I use. It may be happening to other variations of Ubuntu also, but this I have not tried. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: cups printers -- 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 11.10 -- Printers found but cannot print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 590570] Re: After boot/logout portmap needs to be reconfigured and restarted
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) terminated with status 2 > init: portmap main process ended, respawning > init: statd pre-start process (788) terminated with status 2 > > -- > After boot/logout portmap needs to be reconfigured and restarted > https://bugs.launchpad.net/bugs/590570 > You received this bug notification because you are a direct subscriber > of the bug. > --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
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 https://bugs.launchpad.net/bugs/623520 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
$ 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 of the Lines you mentioned solved the problem, but all the docs I have read said to set ssl_listen: 995, verbose_ssl: yes I set on to try and debug the issue. So is this a bug in covecot or a bug in the tutorials I have been reading? -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: 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 localhost:995 connect: Connection refused connect:errno=111 The above is still an issue. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
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 the log erratically over the day sometime 20 time in just a few minutes then not again for almost a day. I assume there is an algorithm that determines when to check. Aug 25 12:19:34 foundation dovecot: deliver(root): chdir(/root) failed: Permission denied Aug 25 12:19:34 foundation dovecot: deliver(root): sieve: stat(/root/.dovecot.sieve) failed: Permission denied (using global script path in stead) Aug 25 12:19:34 foundation dovecot: deliver(root): stat(/root/Maildir) failed: Permission denied Aug 25 12:19:34 foundation dovecot: deliver(root): stat(/root/Maildir/tmp) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup) missing +x perm: /root) -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
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 /etc/ssl/certs/ssl-mail.pem -> /etc/ssl/certs/ssl-cert-snakeoil.pem $ sudo ls -l /etc/ssl/private/ssl-mail.key lrwxrwxrwx 1 root root 38 2010-07-28 22:19 /etc/ssl/private/ssl-mail.key -> /etc/ssl/private/ssl-cert-snakeoil.key I also cannot get dovecot to stop looking in the /root dir, so my log is full of error messages about permissions being denied. $ sudo dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-24-generic-pae i686 Ubuntu 10.04.1 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: pop3 pop3s ssl_listen: 995 ssl_cert_file: /etc/ssl/certs/ssl-mail.pem ssl_key_file: /etc/ssl/private/ssl-mail.key ssl_cipher_list: ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes mbox_write_locks: fcntl dotlock mail_executable: /usr/lib/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/modules/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh lda: postmaster_address: postmaster mail_plugins: sieve quota_full_tempfail: yes deliver_log_format: msgid=%m: %$ rejection_reason: Your message to <%t> was automatically rejected:%n%r auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/sieve -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: 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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] Re: dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
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 happens on the domain name coming from the outside. -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623520] [NEW] dovecot reports Invalid configuration in /etc/dovecot/dovecot.conf in all cases
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 the ones in my config. This happens whether or not I start dovecot on the command line using my config file or with sudo service dovecot start. dovecot is also trying to write to my /root dir even though I have /etc/aliases pointing to my user account. ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: dovecot ssl -- 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573919] Re: autofs doesn't work with lucid
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 doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525154] Re: mountall for /var races with rpc.statd
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573919] Re: autofs doesn't work with lucid
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 /var is not mounted when statd is started. Post 13 on bug 525154 seems to solve this issue, but it is only a workaround, it does not solve the race condition if my understanding is correct. -- autofs doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573919] Re: autofs doesn't work with lucid
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 does not have this issue, so it obviously is some config issues that is going badly when upgrading. I was originally fixing this issue by stopping then starting portmap again. (A restart didn't work.) I have found this in my /var/log/boot.log file: init: statd main process (730) terminated with status 1 init: statd main process ended, respawning init: statd main process (736) terminated with status 1 init: statd main process ended, respawning init: statd main process (747) terminated with status 1 init: statd main process ended, respawning init: statd main process (754) terminated with status 1 init: statd main process ended, respawning init: rpc_pipefs pre-start process (703) terminated with status 32 init: statd main process (764) terminated with status 1 init: statd main process ended, respawning init: statd main process (770) terminated with status 1 init: statd main process ended, respawning init: statd main process (776) terminated with status 1 init: statd main process ended, respawning init: statd main process (782) terminated with status 1 init: statd main process ended, respawning init: statd main process (788) terminated with status 1 init: statd main process ended, respawning init: statd main process (794) terminated with status 1 init: statd main process ended, respawning init: statd main process (800) terminated with status 1 init: statd respawning too fast, stopped -- autofs doesn't work with lucid https://bugs.launchpad.net/bugs/573919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590570] Re: After boot/logout portmap needs to be reconfigured and restarted
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 /var/log/boot.log file: init: statd main process (730) terminated with status 1 init: statd main process ended, respawning init: statd main process (736) terminated with status 1 init: statd main process ended, respawning init: statd main process (747) terminated with status 1 init: statd main process ended, respawning init: statd main process (754) terminated with status 1 init: statd main process ended, respawning init: rpc_pipefs pre-start process (703) terminated with status 32 init: statd main process (764) terminated with status 1 init: statd main process ended, respawning init: statd main process (770) terminated with status 1 init: statd main process ended, respawning init: statd main process (776) terminated with status 1 init: statd main process ended, respawning init: statd main process (782) terminated with status 1 init: statd main process ended, respawning init: statd main process (788) terminated with status 1 init: statd main process ended, respawning init: statd main process (794) terminated with status 1 init: statd main process ended, respawning init: statd main process (800) terminated with status 1 init: statd respawning too fast, stopped I will continue posting in the 573919 thread since this seems to be the same bug. -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590570] Re: After boot/logout portmap needs to be reconfigured and restarted
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 $ sudo service portmap restart will get automount working. -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590570] Re: After boot/logout portmap needs to be reconfigured and restarted
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 behavior. If I just restart portmap the mounts will never work unless I must reconfig first. I know it sound crazy but this is the only thing that gets the mounts to automount. The only thing I was mistaken on is that this only seems to be an issue after rebooting. Logging out then in again seems to work fine if I had reconfigured and restarted portmap beforehand. Another possibly related issue a friend of mine is having is that 10.04 seems to be trying to mount external file systems before the network has fully come up and consequently fails to mount anything. He also claims this has happened after an upgrade. Could there be a timing issue in the startup sequence? I get the following when I look at /var/log/message every time I boot: Jun 10 10:16:14 foundation kernel: [ 14.654977] svc: failed to register lockdv1 RPC service (errno 97). Jun 10 10:16:14 foundation kernel: [ 14.656050] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory Jun 10 10:16:14 foundation kernel: [ 14.683755] NFSD: starting 90-second grace period Jun 10 10:16:29 foundation kernel: [ 29.988891] ppdev: user-space parallel port driver Jun 10 10:21:50 foundation portmap: Removing stale lockfile for pid 718 -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590570] Re: After boot/logout portmap needs to be reconfigured and restarted
** 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 $ sudo service portmap restart to get them working again. Restarting alone doesn't fix it. This is happening on two machines both running Lucid 10.04 right after - an upgrade. One is a headless server and the other is my laptop. + an upgrade. One is a headless server and the other is my laptop. I have + a third netbook that I put a fresh install on and it does not have this + issue. -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 590570] [NEW] After boot/logout portmap needs to be reconfigured and restarted
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 $ sudo service portmap restart to get them working again. Restarting alone doesn't fix it. This is happening on two machines both running Lucid 10.04 right after an upgrade. One is a headless server and the other is my laptop. ** Affects: portmap (Ubuntu) Importance: Undecided Status: New ** Tags: autofs portmap ** Tags added: autofs portmap ** 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 $ sudo service portmap restart to get them working again. Restarting alone doesn't fix it. - This is happening on two machines are both running Lucid 10.04 right - after an upgrade. One is a headless server and the other is my laptop. + This is happening on two machines both running Lucid 10.04 right after + an upgrade. One is a headless server and the other is my laptop. -- After boot/logout portmap needs to be reconfigured and restarted https://bugs.launchpad.net/bugs/590570 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584428] Re: For Lucid server with Samba, console login times out
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 for the help. -- For Lucid server with Samba, console login times out https://bugs.launchpad.net/bugs/584428 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 584428] Re: Lucid server upgrade login times out
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 near the machine now so I can't test it at a VT until I get there. Thanks, I hope this fixes the issue, but it seems we still have a bug here and this is only a work around. I wonder if this could also be causing another issue I am having. I am running automount 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 $ sudo service portmap restart to get them working again. Restarting alone doesn't fix it. Should I enter another bug for this? On Tue, May 25, 2010 at 12:54 PM, Daniel Dickinson wrote: > a) I think gdm is the wrong package on several counts the most important > being that this is a server install and there is no mention of a > graphical login, and I experience this on an server with no console as > well > > b) I think this is related to samba / winbindd because when I checked > the logs there were error messages related to winbindd (this is a Linux- > only network, however it appears winbindd is now a default part of the > Ubuntu installation). > > c) I modified /etc/samba/smb.conf to have the line > auth methods = guest sam winbind > > and logins on the console worked correctly where they hadn't before. > > ** Tags added: samba winbind > > ** Tags added: console login timeout > > -- > Lucid server upgrade login times out > https://bugs.launchpad.net/bugs/584428 > You received this bug notification because you are a direct subscriber > of the bug. > -- Lucid server upgrade login times out https://bugs.launchpad.net/bugs/584428 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584428] Re: Lucid server upgrade login times out
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 https://bugs.launchpad.net/bugs/584428 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 584428] [NEW] 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 on this server and I can log in remotely with no issues. ** Affects: ubuntu Importance: Undecided Status: New -- Lucid server upgrade login times out https://bugs.launchpad.net/bugs/584428 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 112238] Re: mga driver no longer will display 1600x1200
Okay, I go to it a bit sooner than I thought. My ViewSonic GS790 still was only able to display in 1400x1050 even with the Lucid Live CD. Now something happened that has happened before and that is when I boot back into Hardy the display was in 1600x1200. This is always short lived however and the next time I boot it will revert back to 1400x1050. This seems to indicate that maybe the Live CD set the hardware in a state that lets it work for a while at 1600x1200, but after rebooting again the hardware falls back to the setting that only lets the monitor display at the lower res. I could 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 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 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 Harrington > wrote: >> ** Tags added: hardy >> >> -- >> mga driver no longer will display 1600x1200 >> https://bugs.launchpad.net/bugs/112238 >> You received this bug notification because you are a direct subscriber >> of the bug. >> --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- mga driver no longer will display 1600x1200 https://bugs.launchpad.net/bugs/112238 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 112238] Re: mga driver no longer will display 1600x1200
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 Harrington wrote: > ** Tags added: hardy > > -- > mga driver no longer will display 1600x1200 > https://bugs.launchpad.net/bugs/112238 > You received this bug notification because you are a direct subscriber > of the bug. > -- --- Carl J. Nobile (Software Engineer) carl.nob...@gmail.com --- -- mga driver no longer will display 1600x1200 https://bugs.launchpad.net/bugs/112238 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501670] Re: g_set_prgname() called multiple times
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
