[Bug 1311403] Re: Can't type password after resume.
Exact same problem (at the unlock screen, it is not possible to enter any characters on the password box, as if focus is not there) on Xubuntu 18.04 and Xubuntu 20.04 in three different machines (two laptops and one desktop); problem existed since 18.04 and persists after upgrade to 20.20 focal fossa. ** Also affects: xubuntu-greeter Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311403 Title: Can't type password after resume. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715552] Re: VMWare does not start
@Michael Harmon, you are very welcome. I can confirm that my above procedure also works for Workstation Pro 14.1.2. >> Updated instructions to successfully install Workstation Pro 14.1.2 in (K)ubuntu 18.04 1. Do the normal installation of VMWare Workstation. Do not run vmware yet. It will fail anyway. 2. Do a git clone (or download as zip package) of the vmware-host- modules project hosted in https://github.com/mkubecek/vmware-host- modules. Make sure to read the README to understand what branch you need to checkout. Detailed instructions for doing this is in the INSTALL document. For example: If you are installing Workstation 14.1.2, then you'd do: git clone https://github.com/mkubecek/vmware-host-modules.git cd vmware-host-modules git checkout workstation-14.1.2 (This project is recommended by: https://wiki.archlinux.org/index.php/VMware#Kernel_modules). 3. cd to the git repo dir (vmware-host-modules) and follow the instructions in the INSTALL document of the project to "Build and install modules - DIRECTLY", i.e., the section "2a." as of this writing. This is important, as it will ensure that your modules are build specifically for your CURRENT kernel. Follow all the steps carefully. For example: In my case, I want to build and install modules against my current kernel, so I just need to issue this command -from the directory to which I cd before: make && sudo make install You are NOT done yet! If you run vmware at this point, you will get the error that this bug mentions. Next step, you'll fix it. 4. Enter the following sequence of commands in the console: cd /usr/lib/vmware/lib/libz.so.1 sudo mv libz.so.1 libz.so.1.old sudo ln -s /lib/x86_64-linux-gnu/libz.so.1 . sudo depmod -a sudo /etc/init.d/vmware restart 5. If all went OK, you should be ready by know. VMware Workstation (at least 14.1.2 on (K)Ubuntu 18.04) now should work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715552 Title: VMWare does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715552] Re: VMWare does not start
A small correction to the step 2 above: In the example, after you do the 'git clone ...' command, you have to change directory to the git repo dir (e.g. 'cd vmware-host-modules') before issuing the 'git checkout workstation-x.y.z'. Else, you'd get a git error like this: 'fatal: not a git repository ...', which, while harmless, it might confuse you. Sorry for the lapse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715552 Title: VMWare does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715552] Re: VMWare does not start
To successfully install VMware Workstation 12.5.9 (and probably 14.x also) in Ubuntu 18.04, follow this procedure: 1. Do the normal installation of VMWare Workstation. Do not run vmware yet. It will fail anyway. 2. Do a git clone (or download as zip package) of the vmware-host-modules project hosted in https://github.com/mkubecek/vmware-host-modules. Make sure to read the README to understand what branch you need to checkout. Detailed instructions for doing this is in the INSTALL document. For example: If you are installing Workstation 12.5.9, then you'd do: git clone https://github.com/mkubecek/vmware-host-modules.git git checkout workstation-12.5.9 (This project is recommended by: https://wiki.archlinux.org/index.php/VMware#Kernel_modules). 3. cd to the git repo dir (vmware-host-modules) and follow the instructions in the INSTALL document of the project to "Build and install modules - DIRECTLY", i.e., the section "2a." as of this writing. This is important, as it will ensure that your modules are build specifically for your CURRENT kernel. Follow all the steps carefully. You are NOT done yet. If you run vmware at this point, you will get the error that this bug mentions. Next step, you'll fix it. 4. Enter the following sequence of commands in the console: cd /usr/lib/vmware/lib/libz.so.1 sudo mv libz.so.1 libz.so.1.old sudo ln -s /lib/x86_64-linux-gnu/libz.so.1 . sudo depmod -a sudo /etc/init.d/vmware restart 5. If all went OK, you should be ready by know. VMware Workstation (at least 12.5.9 on Ubuntu 18.04) now should work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715552 Title: VMWare does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1715552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)
I am also affected. My system: ACER Predator 17 G9-791, running Kubuntu 17.04. Problem has been permanent ever since first install (in dual boot with Windows) of Kubuntu 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672822 Title: sound only coming from left speaker on acer predator (fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1672822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684240] Re: Mouse pointer behaves strangely
...and I should have guessed all that information from your six words post because...? So in your opinion: because I could not guess all of that, I should have opened my own bug report and fight it all by myself from zero, ignoring the fact that someone already had opened a bug report because "everyone is trying to help everyone by providing information about their issues". Touching words, "everyone trying to help everyone". But it seems that this one was opened to get help for your own issue and not to "share" anything with anyone. So "someone wrote" is another way of telling the community (you say you are trying to help), that you are not sharing neither contents of said advice nor source of it; you just happen to "have found it". Nice. So, should I have written my own report after wasting my time on this one: how would you feel if I would have concluded it with a six words post like: "I have fixed the problem now." with no more context. The internet is full of this kind of rubbish. Precisely: not a Help Desk, not a "sharing place", no nothing. No, this is not Help Desk, and precisely because it's not, people should use it consciously and realizing that it's not because one opens a "ticket" that it makes them automatically a "community's hero" if you are not going to steer the bug report in the sense of making it an useful place of sharing information and not one where others will stumble upon and get frustrated by the "I have fixed my problem, goodbye" posts. That community you talk about always expect that a bug report owner would have the minimum courtesy of providing any information that might be somehow relevant and potentially help. Not confusing/frustrating the community, which is what posts like those do. So like you said: "community where everyone is trying to help everyone by providing information about their issues" is the opposite of what I found here, as your own last two posts unfortunately prove it. Either you share or you don't. You didn't. Just read your own words again, please, and try to actually apply those good ideas, next time. That would do everyone a service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Mouse pointer behaves strangely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684240] Re: Mouse pointer behaves strangely
Finally found the bug report of this problem. It affects me, exactly the same. I could provide more details BUT it doesn't seem to be relevant, doesn't it? I explain: A couple of notes, @jgrns: What do you mean "the problem disappeared"? Does it mean: it "disappeared" from your system? Or: on everybody else's systems? It didn't "disappear" from mine. Mind to provide any useful context? Posts like that are the ones that make so many people hate 'this' (you know, Linux, FOSS, and all the things that they should not hate for things like this). Not because you are inaccurate and confusing, but because you seem to have the power to change the status of the bug (without actually fixing it), whatever "nouveau" means in your launchpad jargon. The bugs reports are not to satisfy those who have the power of changing status of bugs. They are for the users, because without users software is useless. Far too frequently I see these useless posts that seem to imply that magic does exist. Problems don't "disappear" by magic in Engineering or in Science or in Life. And if you think they do, at least you should propose some theory that doesn't make you look that you just want to dismiss the problem or make us believe that "if you wait long enough, all your problems in life will disappear" --which is true, but some us don't want to wait until we die to see all troubles vanishing from our lives. I would be fired if I would ever suggest that to my customers, or worse, tell them that because all of a sudden I ceased to see the problem, they are wrong and it doesn't exist. Sorry if it looks that I am irritated, but those six words did the job. I am sure others with this problem would also feel. Please if you can't help with this bug, or believe it's something magical that comes and go, or if open tickets are annoying, then please at least don't dismiss it with "it disappeared" without at least a slight context. It doesn't really add credibility to a --presumably-- software developer who tells users with a complaint that the problem was perhaps abducted by aliens and now "is gone". It's not. It's a bad bug, it disrupts tremendously the work in the KDE environment, to the point of almost preventing us to work with most of the programs that use the mouse at all. It is a show stopper. You can change the status of the bug to whatever you please, it's not "my" bug report system. But then it's a bit useless for the rest of the people. Anyhow, thanks for the bug report, because it is very well described. I might copy/paste part of the description and seek for help somewhere else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Mouse pointer behaves strangely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1684240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091464] Re: Unable to chainload Windows 8 with Secure Boot enabled
This is the first case reported here of the bug in (k)ubuntu 15.10, the newest ubuntu family as of October 2015. I can confirm the bug exists in a Toshiba Satellite C850-19D laptop, with pre-installed Windows 8, and parallel installation of Kubuntu 15.10 "WIlly Werewolf". Same as other cases above, Kubuntu 15.10 installed very well and boots OK from Grub2 menu, but Windows 8 does not boot from this menu, showing instead the error "/EndEntire filepath: /ACPI(a0341d0,0)/PCI(2,1f)/Sata(0,0,0)/HD(2,e1800,82000,cc51b24f9affe111,2,2)/File(\EFI\Microsoft\Boot)/File(bootmgfw.efi)/EndEntire Cannot load image" Note the following: 1. The original workaround of disabling Secure Boot in the BIOS works in this case, and it is very easy to reproduce the issue. I have decided to stay without Secure Boot, as it is the simplest of all the workarounds so far. 2. Following advise from NVieville on post #48, since this is a Toshiba Satellite C850, I did a BIOS upgrade to the latest version for this model: v6.80, from 22-Jan-2014. I repeated the experiments and saw no improvement, i.e., the problem exists exactly the same with the new BIOS and I must disable Secure Boot to get Windows 8 booting. 3. A side note but useful: For those interested in Linux (Ubuntu) support for this Toshiba Satellite model, good news: All hardware is supported and working fine out of the box, no need to do any special or additional procedures: Wi-fi, sound, all FN keys, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091464 Title: Unable to chainload Windows 8 with Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1091464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1362963] Re: findsmb command is missing from smbclient package
I can confirm that findsmb is also missing from the package smbclient 2:4.1.13+dfsg-4ubuntu3 in Kubuntu 15.04 (Kubuntu Vivid). After installing that package and reinstalling it (also reinstalling samba) the findsmb script does not exist anywhere. For a workaround, I have taken a copy of the findsmb script from an older installation (Mint 14 "Nadia"/Ubuntu Quantal) and that copy runs and seems to do what it is supposed to do - or at the very least it is listing the systems that I was expecting to respond to it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1362963 Title: findsmb command is missing from smbclient package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1362963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 794513] Re: Please remove kdelibs and kdewebdev-kde3 from the archive
Many existing kde3 projects are destroyed by this decision. This is causing a lot of difficulties and specially for those of us who upgraded to 11.10 and did not know that this was going to happen . I have important projects for example in kommander kde3, now things are broken. Please at least provide some guidance. Don't do it this way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794513 Title: Please remove kdelibs and kdewebdev-kde3 from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/794513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750423] Re: update-rc.d: warning: resolvconf stop runlevel arguments (none) do not match LSB Default-Stop values
The bug persists in Ubuntu 11.10 oneiric. I have just dist. upgraded from 11.04 (Kubuntu, with gnome and unity too) and when installed manually resolvconf: $ sudo apt-get install resolvconf (.) Setting up resolvconf (1.48ubuntu1) ... mkdir: created directory `/etc/resolvconf/run' mkdir: created directory `/etc/resolvconf/run/interface' update-rc.d: warning: resolvconf stop runlevel arguments (none) do not match LSB Default-Stop values (0 6) $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750423 Title: update-rc.d: warning: resolvconf stop runlevel arguments (none) do not match LSB Default-Stop values To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/750423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 859137] Re: Motherboard AMD 990FX/SB950 usb don't work
I have just confirmed : You do NOT want to enable the IOMMU mode on the Asus Croshair V Formula motherboard (AMD 990FX/SB950 chipset) if you want to have your usb working on Ubuntu. In particular, if you enable IOMMU and if your keyboard and mouse are usb, then you will NOT be able to log on to Ubuntu. If you use PS2 keyboard and PS2 mouse, though, then they will work, but you will have no usb functionality. Among other things, this is a pity, because the BIOS of this motherboard explains: "IOMMU is supported on Linux based systems to convert 32 bit I/O to 64 bit MMIO". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/859137 Title: Motherboard AMD 990FX/SB950 usb don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/859137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 859137] Re: Motherboard AMD 990FX/SB950 usb don't work
I am also affected by this problem. I am just finalizing a migration of my Ubuntu 11.04 to a Phenom II X6 1100T Processor mounted on an Asus Crosshair V Formula, with 8GB RAM. I have also found the hard way that if I enable the IOMMU MODE in the North Bridge Configuration screen, then I cannot even log on to my system because both my keyboard and mouse (USB) just don't work. Setting the "IMMU MODE" to DISABLED allows me to use my usb keyboard and usb wireless mouse. >From the perspective of an user who uses usb keyboard and mouse and has just enabled the IMMU mode, the Ubuntu system will be completely broken, completely irresponsive, where not even the Alt-SysRq R-E-I-S-U-B sequence could help because there is no keyboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/859137 Title: Motherboard AMD 990FX/SB950 usb don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/859137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573615] Re: udev error message and kernel panic
*** This bug is a duplicate of bug 155689 *** https://bugs.launchpad.net/bugs/155689 If the main report is the #155689, then please change the status to "Confirmed" also there. I am having same issue in Ubuntu 10.10 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/573615 Title: udev error message and kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/573615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 177457] Re: [Gutsy] Kernel panic on boot, "run-init: nuking initramfs contents: Directory not empty"
*** This bug is a duplicate of bug 155689 *** https://bugs.launchpad.net/bugs/155689 The duplicate status of this bug is wrong: bug #155689 is different because it affects much newer versions of Ubuntu than "Gutsy", which this bug refers to, and this was ages ago. Please have a look to bug #155689 which is still hitting in as recently as July 25 2011 and Ubuntu 10.10 (Maverick). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/177457 Title: [Gutsy] Kernel panic on boot, "run-init: nuking initramfs contents: Directory not empty" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/177457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155689] Re: nuking initramfs contents: Kernel panic at boot
I am having this problem intermittently. I have Ubuntu 10.10 on an Asus EEE PC 1005 HA (Hard drive), 1 Mb of RAM, dual booting with Windows XP. This has been updated from Ubuntu 10.04 (which was all OK) just a week ago, so this might possibly related to the upgrade (?). Additional info: this error on cold boot happened after having had an X crash also during bootup, where the screen became blank after showing the plymouth splash for only one second, then some lines with errors for a fraction of a second, then frozen. Needed to use power button. Then after a couple of times same failure, the kernel panic error: run-init: nuking initramfs contents: Directory not empty [ 2.768910] Kernel panic - not syncing: Attempted to kill init! udevd-work[100]: inotify_add_watch(6, /dev/sda7, 10) failed: No such file or directory. There are other people affected recently - see the duplicates of this bug. Dear devs, any comment? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/155689 Title: nuking initramfs contents: Kernel panic at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/155689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742516] Re: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme)
Correction, I do have raleigh, I just did not look in the right place (System Settings -> Application Appearance -> GTK+ Appearance -> Widget style. I did as in post #39, gimp now works, although still it gives the following error when launched from a terminal prompt: (gimp-2.6:5552): GLib-WARNING **: /build/buildd/glib2.0-2.28.6/./glib/goption.c:2132: ignoring no-arg, optional-arg or filename flags (8) on option of type 0 (gimp-2.6:5552): Gimp-Widgets-WARNING **: gimp_dialog_factory_dispose: stale non-toplevel entries in factory->open_dialogs The missing folder ~.gimp-2.6 now obviously exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742516 Title: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/742516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 742516] Re: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme)
I am also affected. Kubuntu 11.04 64 bit, up to date. Also I am using Oxygen. Note that the original installation was actually Ubuntu (with the horrible Unity) and I installed Kubuntu desktop on top of it, and was forced to use gdm (else if switched to Unity, it would not load desktop). I have not yet tried the workarounds. I do not have at this moment the ~/.gimp-2.6 folder. @Martin Pitt: I am wondering: Why would such a bug (a show stopper!!) have its "importance" lowered from High to Medium?What is the criteria here? A user click the gimp icon and the system does not do anything. Hello? aren't we talking about The gimp here? Is the criteria to not consider it High priority because it happens with Oxigen? so what? isn't that still critical to an user? If Photoshop would be crashing when a Windows or Mac user would be using certain window decoration, how acceptable would it be for any user whatsoever that Microsoft/Apple would not consider such bug High priority? Why Linux would have to have this attitude towards their users? The gimp is a flagship for Linux ! don't you see that? When compared to Oxygen, who cares for Oxygen in this context? Secondly, it has not been explained yet which one is the "best" workaround: to change window decorator or to create the missing directory? What about any other themes? I don't have Raleigh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/742516 Title: gimp-2.6 crashed with SIGSEGV in g_closure_invoke() (with oxygen GTK theme) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/742516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 653877] Re: deprecation warning in boot.log every startup after plugging in HP printer
The hplip udev rules have been written like this on purpose, at least for the /etc/udev/rules.d/55-hpmud.rules , where you can read: (quote) "It seems SFSFS has been replaced or depreciated by ATTR/ATTRS, but I continue to use SFSFS in order to be compatible with older distros. SFSFS was defined in "Writing udev rules" Ver 0.72, Daniel Drake. 2/11/2009, D Suffield" (...) This rules file is an attempt at being compatable with all distros. Feel free to make your own changes and if you feel your changes are not distro specific please send your patch to us. 2/11/2009, D Suffield" (end of quote). The 55-hpmud.rules and the 56-hpmud_support.rules files both belong to hplip , but for whatever reason the explanations above are only included in the 55-hpmud.rules file only. In my case, (Ubuntu Lucid, upgraded from Karmic just a couple of weeks ago) I have the same warning errors as you but referring to the following files: /etc/udev/rules.d/55-hpmud.rules(hplip) /etc/udev/rules.d/56-hpmud_support.rules(hplip) /etc/udev/rules.d/65-libmtp.rules /etc/udev/rules.d/45-libnjb5.rules and /etc/udev/rules.d/025_logitechmouse.rules While those warnings do look ugly, the are harmless. If you want to get rid of those, you just need to edit the offending files and replace all the occurrences of SYSFS by ATTR . ( Make sure you backup first whichever file you are editing ! ). Then you may want, as a precaution, to reconfigure the udev package by running (as root) dpkg-reconfigure udev However, you should be aware that if you choose to edit your .rules files to get rid of the warnings, you are accepting that the next time you make an upgrade to the next Ubuntu version (e.g. 10.10 ), then you will have the very annoying (at least annoying to me) task of having to answer questions during the upgrade, regarding the changes that you have made in your files. If you want my advice, here it is: if we are talking about Ubuntu packages maintained by the Ubuntu team, I would say that it is best to leave them as they are, because whenever those rules become obsolete and break the packages, the maintainers are going to have to fix them anyway, so when you upgrade, the work should have been done for you; no questions for you to answer during the upgrade. One reference that might be useful: http://reactivated.net/writing_udev_rules.html As of today, it contains the v0.74, by Daniel Drake. -- deprecation warning in boot.log every startup after plugging in HP printer https://bugs.launchpad.net/bugs/653877 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 251769] Re: Creating new project from svn repository does not identify Python sources
Since I did not hear from you for a long while, I progressively moved away from eric because of the bug. Version control is fundamental to my work. Your comment implies that after one year you don't know the cause and whether this works or not in the newest release as it should. That does not encourage me to suppose that the bug has disappeared by coincidence. Bringing my project back to eric will mean extra work and time, but I suppose it will not hurt to try it again with new release, although I am afraid that if I find the same bug again (you admit not to know what is the cause) I will be stuck again and not having any comments from you for another 14 months... Sorry to 'punish' you with this comment, I am also very busy person like you are, but I thought opening this bug would raise your interest in reasonable time. Can you please at least tell me if you can (or could) reproduce the problem I describe above? Please give me anything that will help me believing it is worth to dedicate my time to this or any other eric's bug. -- Creating new project from svn repository does not identify Python sources https://bugs.launchpad.net/bugs/251769 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 251769] Re: Creating new project from svn repository does not identify Python sources
** Description changed: - When creating a new project by selecting "Project -> Version Control -> - New from repository..." in a remote Subversion repository that contains - a Python project, Eric fails to automatically identify the source files - as Python, and places them all into the "Others" category in the Project - Viewer. + In eric4, when creating a new project by selecting "Project -> Version + Control -> New from repository..." in a remote Subversion repository + that contains a Python project, Eric fails to automatically identify the + source files as Python, and places them all into the "Others" category + in the Project Viewer. Then, in this view, all the files remain in a status in which it is not possible to rename, delete from the project or delete the file (the options are disabled). This means that there is no way to move them to the appropriate "Sources" view, except by manually adding them into this category but then having them all duplicated into the "Others" tab. If one would then create the project manually from an existing checkout (working copy) of a project, then there will be no chance to use the VCS feature, since the program does not have any possibility to put an existing project into an existing version control system except by creating a new repository. The only way around this is to create the project manually and not using the version control feature at all. - The package is Eric v4.1.1-ubuntu1, in Ubuntu Hardy. + eric4 version: eric4-1.1 (r1972) + The package is eric v4.1.1-ubuntu1, in Kubuntu Hardy. Version Numbers: Python 2.5.2 Qt 4.4.0 PyQt4 4.3.3 sip 4.7.3 QScintilla 2-snapshot-20070923 eric4 4.1.1 (r1972) Platform: linux2 2.5.2 (r252:60911, Apr 21 2008, 11:12:42) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] + Ubuntu 2.6.24-19.36-generic -- Creating new project from svn repository does not identify Python sources https://bugs.launchpad.net/bugs/251769 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 251769] Re: Creating new project from svn repository does not identify Python sources
** Description changed: When creating a new project by selecting "Project -> Version Control -> New from repository..." in a remote Subversion repository that contains a Python project, Eric fails to automatically identify the source files as Python, and places them all into the "Others" category in the Project Viewer. Then, in this view, all the files remain in a status in which it is not possible to rename, delete from the project or delete the file (the options are disabled). This means that there is no way to move them to the appropriate "Sources" view, except by manually adding them into this category but then having them all duplicated into the "Others" tab. If one would then create the project manually from an existing checkout - (working copy) of a project, then there will be no possibility to use - the VCS feature, since the program does not have any possibility to put - an existing project into an existing version control system except by + (working copy) of a project, then there will be no chance to use the VCS + feature, since the program does not have any possibility to put an + existing project into an existing version control system except by creating a new repository. The only way around this is to create the project manually and not using the version control feature at all. The package is Eric v4.1.1-ubuntu1, in Ubuntu Hardy. Version Numbers: Python 2.5.2 Qt 4.4.0 PyQt4 4.3.3 sip 4.7.3 QScintilla 2-snapshot-20070923 eric4 4.1.1 (r1972) Platform: linux2 2.5.2 (r252:60911, Apr 21 2008, 11:12:42) [GCC 4.2.3 (Ubuntu 4.2.3-2ubuntu7)] ** Tags added: eric ide python repository subversion svn -- Creating new project from svn repository does not identify Python sources https://bugs.launchpad.net/bugs/251769 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
