[Bug 1250875] Re: Lightdm sometimes fails to auto login
I have just noticed this: I created a second account (administrative) and gave it a distinct desktop background. Both accounts were set autologin=NO. On rebooting from a complete power off (at the wall), I of course got the login screen, BUT if I dropped down to the second account, its distinctive desktop background was displayed, whereas on returning up to my usual sole account, the background went to the standard purple, instead of my account's distinctive desktop background. I guess there is some sort of corruption in my account's files. I expect that complete removal of my account, followed by its exact re- creation might remove this problem. I am tempted to try, after the appropriate backups of course. By the way, am I talking to myself here, or is anybody who might be able to solve this also listening? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250875] Re: Lightdm sometimes fails to auto login
Humph! Problem returned at: Linux u1404tv 3.13.0-52-generic #86-Ubuntu SMP Mon May 4 04:32:59 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Drat! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250875] Re: Lightdm sometimes fails to auto login
Problem now gone at: uname -a Linux u1404tv 3.13.0-51-generic #84-Ubuntu SMP Wed Apr 15 12:08:34 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250875] Re: Lightdm sometimes fails to auto login
More: creating a new 'test' account on the i5 machine and changing auto login to that account results in auto login working OK for 'test'. That seems to suggest that a fault has somehow arisen in my usual account's control files. I'm hoping someone will discover such a fault and how to correct it by a tiny action. I am reluctant to go through the process of trying to ensure I have saved all my normal account's files and settings, then deleting and recreating that account! I try only to do that when I totally reload a machine and then only with a new LTS, which will not be until 16.04. I'd be pleased to receive via this forum requests for diagnostic information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250875] Re: Lightdm sometimes fails to auto login
Ubuntu 14.04 has just recently started doing this to me too about a week ago, today being 2015-04-22. I keep Ubuntu upgraded on this 64bit PC (Intel i5) to the latest state nearly all the time. I wonder if this helps: When I turn on the power (with the BIOS is set to start the PC when power resumes) I often see my desktop for an instant before the system flips to the login screen. If however I reboot the machine without downing the power, the auto logon works OK. Happy to do any diagnostics as directed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250875] Re: Lightdm sometimes fails to auto login
Oh, and another 64bit machine I have with an identical motherboard but an i3 instead of an i5 DOES carry out auto login OK after power on with BIOS set to boot up on power resume. Hmmm? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250875 Title: Lightdm sometimes fails to auto login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1250875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 792085] Re: Automatic remount of safely removed drive
I have this problem on 12.04 with a new Seagate 3TB usb3 external drive ON A USB3 interface. Will test later on 14.04; waiting for final release at present. For me, safe removal never works (drive always returns) unlike others above, who find it does work second time. I reduced the problem a little by: System Settings/Details/Removable Media/Never prompt or start programs on media insertion (TICK) and dconf-editor: org.gnome.desktop.media-handling automount (UNtick) automount-oepn (UNtick) automount-never (TICK) Of course, then I have to open disk utility and mount drives by hand and open the mount point by hand. No big deal. Interestingly, the problem does not occur if the drive is connected via a USB2 interface, but that rather spoils the point of having a USB3-capable drive! In fact, it dropped the read time to about 1/5th but made almost no difference to the write time, so if your use of the drive is primarily to archive files, it seems: connect via USB2 interface is quite a good idea for now! I suspect that the issue is related to the USB3 interface, both in the drive and the PC. A Seagate ST2000DM001 (2Tb USB interface) external drive CONNECTED ON A USB3 INTERFACE DOES behave correctly on SAFE REMOVAL and does NOT reappear in the list in disk utility. (probably off topic) It is interesting to note that on my drive (Seagate STNV3000300) the interface at the disk enclosure is a PAIR of connectors side by side, not a simple mini or micro USB peripheral interface. Nick Sharp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/792085 Title: Automatic remount of safely removed drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/792085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 987220] Re: System does not power off reliably when Shut Down chosen from GUI
I didn't regards Nick Sharp On 07/01/13 14:49, Adolfo Jayme Barrientos wrote: Please don't mess with bug statuses. ** Changed in: linux (Ubuntu Precise) Status: Fix Released = Confirmed -- Nick Sharp eMl:njsh...@bigpond.net.au Add:77 Brighton Street Curl Curl NSW 2096 Australia Tel:+61 2 9938 3459 Mob:+61 413 948 375 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/987220 Title: System does not power off reliably when Shut Down chosen from GUI To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515435] Re: File-operations window is emtpy
If this is now closed, please re-open. I have just experienced this bug (see attached) on a Dell 9150 running 64bit Ubuntu 12.04 as updated on 2012-05-16. I was copying from an external 2Tb USB drive via USB2.0 to an internal 300Gb IDE drive. I had earlier done a multiple drag and drop copy, and the fileops window showed just what it should - multiple copies in progress. When that had finished, I did another DD copy and the fileops window was blank as attached. Later still, I did another (two files selected) copy and that time got NO fileops window at all. All file copies seemed OK though. I have not yet rebooted, but expect I will see what earlier reporters saw, that is, that the error clears at least temporarily after a reboot. ** Attachment added: BlankFileOps.png https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/515435/+attachment/3149757/+files/BlankFileOps.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/515435 Title: File-operations window is emtpy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/515435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 997832] Re: Shutdown hangs
Thanks Joseph. This problem does NOT occur on every shutdown attempt, so I assume I should not take your requested action. I'm not sure I would be up to that anyway! Is this useful: I have 3 desktop machines other that this one (my general workhorse) running 12.04, all pretty much up to date with their updates. I also have 2 laptops on 12.04. I cannot recall seeing this problem on any of them, but would not swear to that. This machine: Linux u1204 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:22 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Base Board Information Manufacturer: ASUSTeK Computer INC. Product Name: M5A97 Version: Rev 1.xx BIOS Information Vendor: American Megatrends Inc. Version: 0705 Release Date: 08/22/2011 AMD Athlon(tm) II X2 260 Processor × 2 4Gb AMD Radeon HD 6000 Series I'm wondering if the shutdown sequence asks the hardware to do something, and then waits forever for that to complete because this HW specimen happens not to do that, or at least not to report back that it is done. I'm guessing that /var/log/syslog contains a trace log made during shutdown that might indicate the fail point? The last two entries last night were: May 16 20:43:26 u1204 kernel: Kernel logging (proc) stopped. May 16 20:43:26 u1204 rsyslogd: [origin software=rsyslogd swVersion=5.8.6 x-pid=882 x-info=http://www.rsyslog.com;] exiting on signal 15. of which the first looks like bye! from the kernel (which makes one wonder how the second gets there!). I can't remember, but I think that was a clean shutdown. Strangely, there seems to be very little in the log immediately prior to those. If I get another incident, I'll have another look in syslog. How more might I be able to help? Regards Nick Sharp On 17/05/12 06:58, Joseph Salisbury wrote: Does this happen for every shutdown attempt? If so, would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc7-precise/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997832 Title: Shutdown hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 997832] Re: Shutdown hangs
More: I just had another occurrence. This time after the shut down quickly reached Ubuntu over five white dots, the dots never changed to reds, and the machine seemed to hang, so was shut down with the power button. After that, I rebooted and am sending Joseph directly the syslog for the day. Nick Sharp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997832 Title: Shutdown hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/997832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635893] Re: update-apt-xapian-index crashed with OverflowError in index()
Hmm, I doubt if my report added anything useful to this bug's solution, so I'm sorry to have taken system and/or people cycles in marking it as a duplicate. I do see that there are many more duplicates, so I am not alone! I'm not very adept at bug submission, but as I have decided to trial natty beta1, I thought I should try it. I may be raving, but it seemed to me that the system suggested the package name was update-apt-xapian- index (which does not exist by that name?) whereas the main report shows it to be apt-xapian-index. My point is that perhaps the bug reporting software and launchpad system needs a bit more work to help bug-reporting-novices to avoid so many duplicates. I've actually been Linuxing (Fedora/CentOS, more recently Ubuntu) for nearly a decade now, but have not done much bug reporting at all. Looking forward to natty release! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635893 Title: update-apt-xapian-index crashed with OverflowError in index() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 578566] Re: [IDT 92HD75B3X5] Cracking noise on shutdown
Martin, thanks for that. I have just shut down my Dell Dimension 9150 U10.04 AMD64 with the speakers full on, got my head blasted with crackles as usual, and then booted from the alpha 3 U10.10 AMD64. Checked that sound was good, then shut down. Not a beep, crackle or hiss. Silent as the grave. Wehey! It would be good to know if this has happened as a deliberate recode by someone who knows what was doing it! That should make it easier to do as you suggest, retrofit to 10.04LTS. Regards -- [IDT 92HD75B3X5] Cracking noise on shutdown https://bugs.launchpad.net/bugs/578566 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 563555] Re: no mouse cursor
I have this problem: no mouse cursor after login, repeatable by logout login again. AFAIK I already had the metacity package as evidenced by CONFIG EDITOR/APPS (metacity present) WORK AROUND: BLINDLY!!:... 1 Move the mouse around, clicking left, until the cursor is clearly on Accessories then choose Terminal 2 Click in the terminal window and hit return 3 The mouse cursor appears and seems to stay until logout login again NOW that you can see the cursor, hit System/Preferences/Mouse and tick LOCATE POINTER, so that you get some temporary flashing rings round where the cursor is on the screen, just by pressing CTRL. This will help you do 1-3 next time. Sucks, but better than nothing! I look forward to a proper solution! I have had no such problems on other machines, so I reckon it might be specific to Dell Optiplex 260's Intel graphics hardware. I believe GPUs include some HW specific to showing the mouse pointer. Perhaps 10.04 is not treating this GPU properly. -- no mouse cursor https://bugs.launchpad.net/bugs/563555 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 599140] Re: Panel slow to open cause date/time applet
i -- Panel slow to open cause date/time applet https://bugs.launchpad.net/bugs/599140 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 599140] Re: Panel slow to open cause date/time applet
I have this issue as well. Notes: It is on Lucid AMD64 bit It happens not on my account (used in the install) but on other accounts on this machine. Removing the clock applet solves the slow panel appearance issue. BUT I also note that PLACES/CONNECT TO SERVER is very slow, and watching wireshark while trying to connect as login FTP on my LAN (almost instant from my account) it seems to me that the delay is inside this machine, that is, the network traffic is timely and as expected. An earlier commenter about this issue (in the Ubuntu forums?) also mentioned network flaky?. I think it appears to be slow network but is in fact something slow inside this machine. Ping to the FTP server is fine. Use of TOP does not point to something hogging CPU. Hope this might help. -- Panel slow to open cause date/time applet https://bugs.launchpad.net/bugs/599140 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 541511] Re: MASTER: [i855] GPU lockup (apport-crash)
It is good to see some folk getting 10.04+855GM working using various new kernels, but I expect I am not alone in saying that I am unlikely to load 10.04 on my 855GM Toshiba Satellite A10 (still 9.04 after a poor experience with 9.10 also) until: 1 Upstream release a newer kernel that works really well with 855GM (IF it's possible) and is ... 2 ... cut into Ubuntu 10.04 as a respin, so that I can simply download the CD, install and enjoy I might just about cope with a special install (boot time options re vesa, 915 nosplash etc), provided that an immediately following update pulls the new kernel and leaves the machine perfect from then on! I expect there are many who want to convert from the dark side who would not be prepared to do even that. In the meantime I am actually considering refreshing the Toshiba with a repeat install of 9.04 (I like to do a clean reload every year or so, even with Ubuntu but especially of W... you know what). If 1 and possibly 2 does not happen, I am likely to move the ~8 year old Toshiba back to its original WXP and find someone else who wants it. I never had any screen trouble with it under WXP. I believe 855GM has some fundamental flaws, and it certainly has some limitations that have begun to annoy me as high resolution second screens become available, namely its max 2048x2048 virtual display space. For nice intuitive use, you REALLY do want a second screen that is on the right hand side of the desk also to be VIRTUALLY on the right hand side of the laptop screen, and that cannot happen with 855GM if the second screen is more than 1024 wide (hard to get one as small as that now!!). So for me, perhaps it is time to retire the Toshiba to light duties elsewhere, and move on. Sad for one like me who likes to squeeze the last reasonable drop of use out of everything!! And for me it has been a very good machine. All the best to the gurus working on this! -- MASTER: [i855] GPU lockup (apport-crash) https://bugs.launchpad.net/bugs/541511 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 578566] Re: [IDT 92HD75B3X5] Cracking noise on shutdown
No such luck when I updated U10.04 my Dell Dimension 9150, but then a key difference is that my crackling noises are on an external amplifier which is NOT shut down when the PC turns itself off. Since the same HW with WXP does not exhibit the noise, I am still hoping to find there is some sort of 'turn off' that can be sent from Ubuntu to the sound card just before power off. Simply choosing mute on the speaker icon doesn't do it! -- [IDT 92HD75B3X5] Cracking noise on shutdown https://bugs.launchpad.net/bugs/578566 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 578566] Re: [IDT 92HD75B3X5] Cracking noise on shutdown
I wondered if Daniel Chen's suggestion was for Martin or me (Nick). Anyway, I tried it, and installed linux-alsa-driver-modules-2.6.32.-22-generic from ppa:ubuntu-audio-dev but after a reboot, the shutdown still made the horrible noises. I assume that since Windows can avoid this problem, it must somehow be setting the sound card's output to zero before the final shutdown, so that any audio interference arising from the power supply turn off never reaches the amplifier. I'm sure if Windows can do that (whatever THAT is??!!) then Linux could do it to. I remain hopeful! -- [IDT 92HD75B3X5] Cracking noise on shutdown https://bugs.launchpad.net/bugs/578566 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 578566] Re: [IDT 92HD75B3X5] Cracking noise on shutdown
Martin, thanks for raising this as a bug. Folks, there have been many comments about this issue in the forums, including mine at: http://ubuntuforums.org/showthread.php?t=1486446 with several workaround suggestions, some of which work for some people, some of the time! On my gear (see 1486446) the noise is a horrible banging and crackling, sometimes for 10-30 seconds after the PC has shutdown. It seems to me as though the gradual decay of the PSU's capacitors causes electrical noise, which is then amplified by the still-on amplifier. Yes I could first turn off the amplifier, but I want to shutdown remotely,whle I am near but not at the machine. Note that this problem NEVER occurs using the same HW under WXP MCE. It seems likely that Windows shut down routines must be doing some sort of turn off at the sound card prior to shut down, and Ubuntu isn't! This has been experienced by me with 9.04 Jaunty, 9.10 Karmic, and now 10.04 Lucid. I think I have tried both 32 and 64 bit in the past, but am now on Lucid 64. Interestingly, my 9.04 Toshiba Satellite A10 laptop has never made those noises on turning off, and shows shutting down ALSA late in the shutdown sequence (quiet and splash removed). (I have not moved that to 10.04 yet because of the Intel 855GM bugs.) I look forward to requests for tests to try or diagnostics to perform. Spelling them out 'for the dummy' would be appreciated! I'm not bad, but no guru! -- [IDT 92HD75B3X5] Cracking noise on shutdown https://bugs.launchpad.net/bugs/578566 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
