[Bug 1748935] [NEW] virtualbox-guest-dkms 5.1.30-dfsg-1: virtualbox-guest kernel module failed to build
Public bug reported: I don't have any further information, there was just the updater pop-up indicating an error when I got in on Monday AM. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: virtualbox-guest-dkms 5.1.30-dfsg-1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 DKMSKernelVersion: 4.13.0-32-generic Date: Fri Feb 9 12:55:09 2018 InstallationDate: Installed on 2017-06-16 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all PackageVersion: 5.1.30-dfsg-1 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: virtualbox Title: virtualbox-guest-dkms 5.1.30-dfsg-1: virtualbox-guest kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748935 Title: virtualbox-guest-dkms 5.1.30-dfsg-1: virtualbox-guest kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1748935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579246] Re: Ubuntu 16.04 nm-applet-Message: No keyring secrets found for
This affects me also. I work for a big Silicon Valley company with about 30,000 engineers. Mac is probably the majority platform in engineering, but there are a lot of us using Linux, too. This is kind of a big deal. Except for the fact that 802.1x works on wireless, this would be a BIG deal, because if it didn't work on wireless either, my sole option would be to install the corporate Windows image so that I could work, and relegate Ubuntu to a VM in Windows. I agree with all those who believe this shouldn't be a low-priority bug. It's a serious problem that affects many people using Ubuntu in the workplace. I get that it's an upstream bug, but couldn't Ubuntu fix it and submit the patch upstream? I've been using Ubuntu for 12 years (yeah, I go back a ways; switched from Debian) and this is the works usability problem I've ever encountered. I really, really hope you'll consider fixing it and submitting the patch upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579246 Title: Ubuntu 16.04 nm-applet-Message: No keyring secrets found for To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307559] Re: Window decorations not drawn on external monitor
I also have this problem, on a Dell M3800 with factory-installed Ubuntu 14.04. I've had it for a while but never connected an external monitor before. External monitor = Dell E248, connected via Mini DP with Mini DP to DVI adapter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307559 Title: Window decorations not drawn on external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1307559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563511] Re: Moonlight is dead but docs say to install it
You're most welcome. I'm working through the Pipelight instructions for Silverlight. I have it installed but not yet working in either Chromium or Firefox. As the Pipelight instructions note, Silverlight is touchy. I probably wouldn't care, except my city government has made the unfortunate choice to use it, putting me at a distinct disadvantage in trying to access government information. I made a polite comment to my councilman's office about why the government should use open standards. Pipelight/Silverlight takes some work, but instructions on how to make it work is maybe the way Ubuntu should go in the future. It's not as good as having a Free implementation of Silverlight, but since we no longer have one, it's better than nothing. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563511 Title: Moonlight is dead but docs say to install it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1563511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563511] [NEW] Moonlight is dead but docs say to install it
Public bug reported: This page: https://help.ubuntu.com/16.04/ubuntu-help/net-install-moonlight.html recommends installing the Moonlight plug-in to view Silverlight content. The Moonlight web site states that Moonlight is no longer actively developed and recommends moving away from it as soon as possible, but mentions you might be able to make it work by compiling from source: http://www.mono-project.com/docs/web/moonlight/ The help docs should probably no longer recommend installing Moonlight. ** Affects: ubuntu-docs (Ubuntu) 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/1563511 Title: Moonlight is dead but docs say to install it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1563511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453336] Re: shotwell fails to import iphone photos
Yeah, the upstream sounds like this bug, although gphoto2 is fairly successful at importing photos from my iPhone 5s running iOS 8.3, using these args: gphoto2 –port=usb: -R -P I picked that up from a bug report of the same problem in Fedora 21, on RedHat's bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1178256 Looks like there hasn't been any action on the upstream bug in a while, so getting the photos out of the camera via gphoto2 or the file manager, then importing into Shotwell, looks like it'll be our workaround for a while. ** Bug watch added: Red Hat Bugzilla #1178256 https://bugzilla.redhat.com/show_bug.cgi?id=1178256 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453336 Title: shotwell fails to import iphone photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1453336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Update: Using upstart instead of systemd made no difference: wired 802.1x still gets that failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
I'm seeing something very much like this (same syslog messages, e.g.) but the differences are: 1) It's on a wired interface (802.1x wired) 2) Suspend isn't involved; it never works 3) Wireless 802.1x works perfectly on the same machine (although I haven't tried suspending it; it's my work machine and is always lid-open in a dock) Hardware is a new ThinkPad W541 with Ultradock (but wired 802.1x doesn't work undocked, either). OS is a fresh install of Ubuntu 15.04. I'll try switching to Upstart later today and see if that helps; FWIW, I booted a live 14.04 DVD and wired 802.1x didn't work there, either, so I don't have high hopes for Upstart, but I'll try it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1439771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431857] Re: dbus crash in ubuntu 14.04
Will the fix also be made in 14.04? I plan to remain on LTS. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431857 Title: dbus crash in ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dell-recovery/+bug/1431857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431857] Re: dbus crash in ubuntu 14.04
Thanks, Mario! Patch applied, recovery .iso successfully built :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431857 Title: dbus crash in ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dell-recovery/+bug/1431857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1431857] Re: dbus crash in ubuntu 14.04
I'm also affected by this bug, also on a Dell Precision M3800 (new in February, 2015). Here's my output from sudo lsblk -o name,mountpoint,label,size,uuid $ sudo lsblk -o name,mountpoint,label,size,uuid NAME MOUNTPOINT LABEL SIZE UUID sda 477G ├─sda1 /boot/efiESP 500M 604D-2C6E ├─sda2 DIAGS40M B8A1-2902 ├─sda3 /tmp/tmpbs853iqc OS3G 1CA1-DD30 ├─sda4 / 441.6G a52f8e05-cd2c-4327-9682-824ac0ebfa8d └─sda5 [SWAP] 31.8G 9fbfde95-8da2-46ee-8f0a-45f86d186329 Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1431857 Title: dbus crash in ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dell-recovery/+bug/1431857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250424] Re: compiz does not start with correct keyboard configuration
I am also seeing this bug after upgrading from 13.10 to 14.04 beta. If I reboot or logout/restart X, I have a OWERTY keyboard layout even though QWERTY is not even in my list of layouts (I deleted it because I use only Dvorak and no one else uses this computer). I can get my Dvorak settings back by switching to one of my other text input modes (Japanese, Vietnamese), then switching back to English. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250424 Title: compiz does not start with correct keyboard configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1250424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195091] Re: [LENOVO 1S1680033630109] suspend/resume failure
I'm experiencing the same problem on an HP Envy 15 after upgrading (fresh install) to 13.10 from 13.04. It's completely repeatable and fails to resume from suspend every time, without exception, and the only way out is power off the machine. Overall I really like 13.10 compared to 13.04 but this bug is a showstopper. If a fix doesn't come out very soon I'll have to reluctantly downgrade to 13.04. I'm willing to test any packages that might fix the problem, just email me. I've tried all suggestion found through diligent googling; nothing helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1195091 Title: [LENOVO 1S1680033630109] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1195091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1068661] Re: 1002:6740 Unity does not load after installing fglrx-installer-updates Radeon HD 6700M Series w/ 8086:0116 Intel Integrated Card
This also affects me. Hardware: HP Envy 15 (about 6 months old), Intel integrated graphics plus Radeon HD 6600M. I've tried ever PPA that purports to solve the problem, and at this juncture see no alternative to downgrading to 12.04, since the free drivers don't work very well (heat and terrible battery life). I am left with the inescapable conclusion (and very bad taste in my mouth) that Ubuntu crowdsourced the QA on this one. Maybe you guys ought to consider only doing annual releases, but doing them very well and testing them thoroughly. Once a year done right sure beats twice a year releases that are the software equivalent of Chicago-job wiring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1068661 Title: 1002:6740 Unity does not load after installing fglrx-installer-updates Radeon HD 6700M Series w/ 8086:0116 Intel Integrated Card To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/1068661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924087] Re: Wireless causes unrecoverable system hang
I can confirm this bug exists in 12.04 release Live CD (both 32-bit and 64-bit). I picked up an Acer Aspire One 722-828 as one of the two shortlisted machines for my daughter. Booting from the Live CD works great until I enable wireless, then it hangs and has to be shut down with the power button. Also, it only sees my wireless-G network, not my N network. Suboptimal, since I'm trying really hard to phase out my G network. I'm going to order the other machine, an HP DMZ1, and see how that goes. The Acer is going back in the box and probably back to Costco. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924087 Title: Wireless causes unrecoverable system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/924087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841807] Re: ubiquity crashed with DBusException in call_blocking(): org.freedesktop.NetworkManager.Settings.NotPrivileged: Insufficient privileges.
Just happened to me (twice in a row) with the release version of 12.04 64-bit from the live CD. It never happened with beta versions of the alternate install disk, I'll try one of those next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841807 Title: ubiquity crashed with DBusException in call_blocking(): org.freedesktop.NetworkManager.Settings.NotPrivileged: Insufficient privileges. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/841807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 984615] Re: Wrong syndaemon settings in system settings
On 04/19/2012 04:59 AM, Sebastien Bacher wrote: > you can try to run "gsettings list-recursively> log" twice and diff the > log files, or to attach gdb to gnome-settings-daemon to "pause" it and > see if that st No effect with gdb, and diffing he log files found no differences. Two new data points: in xfce, the mouse will freeze and never come back after 1 or 2 minutes from login. The problem does not manifest in KDE, which seems to argue against the idea I'd had that this might be an fglrx problem. Gnome classic and Gnome shell both seem to not fully load, leaving me with a blank Ubuntu desktop. No idea what went wrong there, or when. My next step will be to run off the live cd for a while and see if everything behaves properly there. If it does, I'll try a reinstall and run for a while with the Free xorg driver and see how it goes, then try installing fglrx from jockey (haven't really been following related bugs, but maybe it's been sorted in the last week or two) and see if the problem shows up. This is probably an edge case, so don't lose any sleep over it. If I find a cause, I'll let you know. Since KDE is unaffected, the mouse freezes in xfce, and Gnome Shell and Classic both have problems, I'm thinking something just got hosed in GTK somewhere and a reinstall might be the best solution. Thanks, Jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984615 Title: Wrong syndaemon settings in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/984615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 984615] Re: Wrong syndaemon settings in system settings
On 4/19/12 04:59 , Sebastien Bacher wrote: > Your other bugs description are a bit confusing, is there one bug or > several bugs there? You use unity right? Yes, this is occurring in Unity. I haven't tried any of the other UI options to see if it does it there. I may have some disagreements with Unity and prefer Gnome 2 + Avant Window Navigator, but I like Unity a lot better than Gnome Shell, at least :p > > The "led is blinking" seems like it could be gnome-settings-daemon > getting "confused" or fighting with something else on keys status, I've > seen a bug report where it was setting numlock to off and on in loop > before > > you can try to run "gsettings list-recursively> log" twice and diff the > log files, or to attach gdb to gnome-settings-daemon to "pause" it and > see if that stops it I'll try those and see what I can get, thanks. > > not sure what you describe as "lock", is that the same issue? does it > happen in a gnome classic or guest session? seems like a compiz issue, > or maybe something flooding compiz (gnome-settings-daemon doing it?) > with events... Yes, it's all the same issue. When the white/orange blinking starts, the UI becomes completely non-responsive. Activity indicators (progress bar in Update Manager, etc.) all freeze until the episode passes, the mouse cursor will move, but I lose all control over the system. If I don't find anything, I'll do a reinstall once 12.04 final is out and see if it goes away, and also because I'm hoping to get fglrx installed through Jockey so I don't have to manually manage it. BTW, I'm running everything the system off of an encrypted LVM, just in case you might have heard of any weirdness surrounding that. My partition layout is /boot, / (encrypted LVM), swap (encrypted LVM), /home (encrypted LVM). These were set up at install time using the beta 2 AMD-64 alternate installer disc. Thanks, Jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984615 Title: Wrong syndaemon settings in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/984615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984615] Re: Wrong syndaemon settings in system settings
Sebastien I just had the "great flash of insight" regarding the freeze- up problem I described above: it's switching virtual desktops (something I do a lot) that triggers it. Happens every time, and it doesn't matter if I switch using the keyboard or the switcher applet in Unity. Even clicking the icon for an open app in the Unity panel will trigger it. Which package would you suggest I file a bug against for this? Thanks, Jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984615 Title: Wrong syndaemon settings in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/984615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 984615] Re: Wrong syndaemon settings in system settings
This is totally unrelated and I apologize for putting it in this bug thread, feel free to email me privately on it if you want, but I've had no success with googling to even figure out where to report this. I guess it's pretty obscure. I'm clueless about what to open a bug against, if this is a bug. Maybe you can point me in the right direction? On my HP Envy 15 with Ubuntu 12.04, it will get into this odd state where it doesn't answer mouse/touchpad clicks, or keyboard commands such as changing to another desktop (I have that set for alt-1 ~ alt-0, 10 virtual desktops). The mouse cursor moves normally, but nothing happens. However, I can still use the keyboard to type in whatever window has the focus on my current desktop. During this time, the wireless on/off light on F-12 is alternating between white (connected) and orange (off/connecting) with a fast blink. After anywhere from 15 seconds to a full minute, the wireless light stops blinking and goes back to solid white, then all of the key commands or mouse clicks will happen; it queues them up while in that state. Even stranger is that if it's in that state and I hit F12 (turns off the wireless) the problem immediately goes away and any pending actions immediately execute. If I run top in a shell and wait for it to happen (doesn't take long, it'll do it every few minutes), I see no unusual CPU consumption or high load averages. So far, nothing has jumped out at me from syslog, either. If you have any ideas where I should look for clues as to the issue, or if you know of any bugs that sound like this, I'd appreciate any pointers. I installed fglrx manually (and it's working) because I couldn't get it to install through jockey, if that might have any bearing on this. Thanks! Jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984615 Title: Wrong syndaemon settings in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/984615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 984615] Re: Wrong syndaemon settings in system settings
On 4/18/12 12:14 , Sebastien Bacher wrote: >> I realize that Ubuntu is all about providing less choice/dumbing down > the interface these days (which is why I'm on the brink of returning to > mainline Debian after using Ubuntu since it was in beta - the original > beta), but perhaps a good solution would to add a couple of additional > checkboxes under "Disable touchpad when typing), one with "Disable taps > and clicks" and the other with "Completely disable when typing." > > That's at best a misleading comment ;-) Ubuntu (following GNOME example) > tries to avoid "fix me" options to provide defaults that work for most > users, it helps to make the system easier to use (no need to look > through an hundred option to find things you are looking for) but also > to improve quality since less codepaths means code easier to > write,maintain,test,etc Easier to maintain is all well and good, but IMO you're taking away too much "easy to use." While I can and do fire up gconf-editor to do these things, it is my firm stance that I shouldn't have to. I'm sure you've noticed how much ground Mint has gained. While Mint has problems of its own, including IMO having artwork that isn't even close to Ubuntu's quality, I booted Mint Debian Edition in a VM the other day and it may be the best of both worlds. It reminds me very much of what Ubuntu was back in 2004: a distro that took Debian and put some really nice polish on it. I think Ubuntu has gotten far away from those roots. I realize there are bills to be paid and how hard it is to make money as a Linux distributor (I remember when Red Hat stopped selling boxed sets after 7.3 because they just couldn't make money on them), but I don't think it's the right path to make Linux so hard to use for real, actual Linux users just to make it easier for newcomers. You can make it plenty easy for newcomers without removing the features that experienced people want. One way to do it would be to have a knob that would enable the power user options. > >> I think it's also worth noting that both Mac and Windows - neither of > which offer focus-follows-mouse - completely disable the touchpad while > typing. > > That's what we did until recently, see the discussion on that bug for the > context of why that was changed: > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/962958 > > Basically moving the cursor is less likely to create confusion that > clicking (first because the default isn't focus follow mouse, but also > because palm touching the pad is not likely to move the cursor a lot It does move the cursor a lot. Really. If you're anywhere near San Jose, California, you're welcome to try it on my HP Envy 15 :-) It has a touchpad almost as big as a MacBook Pro's and it gets incidental palm hits all the time. Come to think of it, the mere fact that people open bugs about this is evidence of that. If it were a little thing, no one would bother to report a bug. I'm sure there are a lot of other people who are bothered by it but who don't go to the effort to create a Launchpad account and open a bug and either live with it, use a mouse, or vote with their feet. On the MacBook Pro, when I'm typing, the mouse cursor just vanishes when I type and reappears at the same spot I left it when I place a finger on the touchpad. This is Highly Desirable Behavior. I don't think it's unreasonable for people to expect that their hardware will work the same way under Linux that it does under Mac and Windows. Sometimes it doesn't because the functionality just isn't there upstream, but this isn't one of those cases. > Right, Apple is picking the hardware they use so they can make sure > their OS works on what they ship, it's harder in a world when you > don't control the vendors and hardware your users run ;-) That's true, and Microsoft has that issue as well, although Linux has it harder because MSFT doesn't have to reverse engineer anything. Still, making the mouse cursor behave the same way it does on Windows and OS X would be following the principle of least surprise. >> WRT the whole idea of poorly supporting things like focus-follow- > mouse, that's just not a good idea. People who've been using Linux for a > long time (since the nineties, in my case) universally hate losing these > features. > > It's not an "idea", it's just defining priorities, before having > something "working for that special usecase" you need "something working > at all", It did work for all. I've been using Ubuntu for 8 years, so I know this. I'm not asking you to add a feature; you're taking away features that were there all along. Please don't spin me. You can tell me to fsck off and I won't be offended, if users like me don't matter anymore and that's your honest opinion, or even the (un)?official position of Ubuntu - but please save the spin for the marketing department. I'd move on to another distro, sure. Either back to Debian or on to Slackware o
[Bug 984615] Re: Wrong syndaemon settings in system settings
Thanks for your response, Sebastien. I realize that Ubuntu is all about providing less choice/dumbing down the interface these days (which is why I'm on the brink of returning to mainline Debian after using Ubuntu since it was in beta - the original beta), but perhaps a good solution would to add a couple of additional checkboxes under "Disable touchpad when typing), one with "Disable taps and clicks" and the other with "Completely disable when typing." I think it's also worth noting that both Mac and Windows - neither of which offer focus-follows-mouse - completely disable the touchpad while typing. On a Mac (using one at the moment), they seem to do it by using really good palm detection, since if I type with one hand and use the other hand to move the mouse cursor, I can do it between key strokes, no matter how fast I type. Ubuntu seems to be slewing strongly in the OS X direction, and in many respects that's a Good Thing. Copying what Microsoft does in their UI surely is not, anyway. If it's going to go in that direction, let's really take in that direction, instead of having half-baked functionality like the one that led me to file this bug. WRT the whole idea of poorly supporting things like focus-follow-mouse, that's just not a good idea. People who've been using Linux for a long time (since the nineties, in my case) universally hate losing these features. You really need to bring back save-session-on-exit, too; yes, I've read the bug reports on that and the rationale around why it was removed, but they don't hold water. Other distros make it work; Ubuntu can, too. I know you're just one guy and maybe don't have much influence over those policy decisions, but honestly, Ubuntu appears to me to have long ago stopped being about what the users want and is only about what the design team wants. That's just not the road to success. Well, the Apple kind of success, but at some point you stop being Linux if you go to far down that road. Thanks for your time, Jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984615 Title: Wrong syndaemon settings in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/984615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984615] [NEW] Wrong syndaemon settings in system settings
Public bug reported: Description:Ubuntu precise (development branch) Release:12.04 Problem: checking "Disable touchpad while typing does not actually disable it (at least not on my new HP Envy 15). The settings it causes to be used are: syndaemon -d -i 2.0 -K -R -t This only disables taps, which causes the cursor to run wldly around the screen while typing. "Not a problem!" you say? Try using focus follows mouse, especially with auto-raise, then come back and tell me that :-) The correct settings are: syndaemon -d -i 2.0 -K -R This completely disables the touchpad while typing, for two seconds. My workaround was to uncheck the box and add syndaemon, with my parms, to the Startup Applications. This is maybe not a blocker, but I think getting a bug fix out on this sooner rather than later would be good. Putting the workaround in the release notes might also be a good idea. It could save others the hours of research I've put in. 2 seconds also seems a bit long, I'm going to try 1.5 and 1.25 and see how that works out. Let me know if there's any other info you need or anything you'd like me to test. Thanks! ** Affects: ubuntu 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/984615 Title: Wrong syndaemon settings in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/984615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979556] [NEW] package fglrx 2:8.951-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Public bug reported: This happened after I rebooted following manual installation of the fglrx driver (jockey never worked for me). fglrx is now working. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.951-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu2 AptOrdering: fglrx: Purge fglrx-amdcccle-updates: Purge fglrx-updates: Purge Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Apr 11 20:59:54 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.951, 3.2.0-23-generic, x86_64: installed ErrorMessage: subprocess installed post-removal script returned error exit status 1 GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1688] Advanced Micro Devices [AMD] nee ATI Whistler [AMD Radeon HD 6600M Series] [1002:6741] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1688] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327.1) JockeyStatus: xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use) MachineType: Hewlett-Packard HP ENVY 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/bg-root ro quiet splash vt.handoff=7 SourcePackage: fglrx-installer Title: package fglrx 2:8.951-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1688 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 44.1D dmi.chassis.asset.tag: CNU2140R40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd12/09/2011:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr06911020481620100:rvnHewlett-Packard:rn1688:rvrKBCVersion44.1D:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY 15 Notebook PC dmi.product.version: 06911020481620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.7.4-0ubuntu3 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu35 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package compiz-0.9 precise ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979556 Title: package fglrx 2:8.951-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/979556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979556] Re: package fglrx 2:8.951-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979556 Title: package fglrx 2:8.951-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/979556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804662] Re: jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2 must contain only strings
Affects me, too. Can't get drivers installed for my ATI. Machine is brand new HP Envy 15 laptop with ATI + Intel HD 3000. Ubunu 12.04 beta, up to date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804662 Title: jockey-gtk crashed with TypeError in _execute_child(): execv() arg 2 must contain only strings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/804662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500417] Re: nautilus doesn't honor gnome theme
I just experienced this for the first time (Ubuntu 10.10 AMD64). Nautilus came up with a theme that reminded me of motif (gag). The suggestion by lhotari in #22 was effective in clearing it. @Alexander Telenga: to make it work, you need to go to a shell and do "ps aux | grep nautilus" (without the quotes) and note the PID of the nautilus process. It will look something like this: your-user-id 2538 0.1 1.0 744556 42208 ?Sl 14:00 0:08 nautilus --sm-client-id 10f1e5588b647711d71265052703550018260031 --sm-client-state-file /home/jonathan/.config/session- state/nautilus-1294783068.desktop The PID is in the second column, and it is 2558. Then, in the same shell, type "kill 2558" (again, without the quotes). Make sure that ~/.gconf/apps/nautilus is still gone (it should be; never came back on my system). The start Nautilus and it should now honor the system theme. HTH, Jonathan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500417 Title: nautilus doesn't honor gnome theme -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 562414] Re: gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info()
Addendum to the above: I looked for a core file in my CWD but didn't find one. Where else might it leave the core file? Or is it dumping core but not leaving a core file? -- gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info() https://bugs.launchpad.net/bugs/562414 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 562414] Re: gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info()
I'm also getting this bug. When run from preferences, it fails silently. When run from a shell, I get: ]** (gpointing-device-settings:19152): CRITICAL **: gpds_ui_new: assertion `module != NULL' failed ** (gpointing-device-settings:19152): CRITICAL **: gpds_ui_is_available: assertion `GPDS_IS_UI(ui)' failed (gpointing-device-settings:19152): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed [1]+ Segmentation fault (core dumped) gpointing-device-settings Ubuntu 10.04 beta 2, all packages up-to-date. -- gpointing-device-settings crashed with SIGSEGV in gpds_xinput_utils_get_device_info() https://bugs.launchpad.net/bugs/562414 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 556019] [NEW] Touchpad not configurable in Kubuntu 10.04 B1
Public bug reported: Binary package hint: xserver-xorg-input-synaptics I have a Perixx Periboard 508 keyboard with integrated touchpad. The touchpad works but is not detected by the touchpad configuration in System Settings (all options are grayed out). Under "Informations" (sic) it says "Touchpad Name: Device not found" I attempted to use ubuntu-bug -p xserver-xorg-input-synaptics but it failed with: Warning: The options -p/-P are deprecated, please do not use them. See /usr/bin/ubuntu-bug --help QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /home/jbyrne/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon : Fatal IO error: client killed Here is what seems to be the relative part of my Xorg log: II) config/udev: Adding input device Cypress-Weikeng USB Adapter (/dev/input/event4) (**) Cypress-Weikeng USB Adapter: Applying InputClass "evdev pointer catchall" (**) Cypress-Weikeng USB Adapter: Applying InputClass "evdev keyboard catchall" (**) Cypress-Weikeng USB Adapter: always reports core events (**) Cypress-Weikeng USB Adapter: Device: "/dev/input/event4" (II) Cypress-Weikeng USB Adapter: Found 8 mouse buttons (II) Cypress-Weikeng USB Adapter: Found scroll wheel(s) (II) Cypress-Weikeng USB Adapter: Found relative axes (II) Cypress-Weikeng USB Adapter: Found x and y relative axes (II) Cypress-Weikeng USB Adapter: Found absolute axes (II) Cypress-Weikeng USB Adapter: Found keys (II) Cypress-Weikeng USB Adapter: Configuring as mouse (II) Cypress-Weikeng USB Adapter: Configuring as keyboard (**) Cypress-Weikeng USB Adapter: YAxisMapping: buttons 4 and 5 (**) Cypress-Weikeng USB Adapter: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "Cypress-Weikeng USB Adapter" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "sp_inet" (**) Option "xkb_layout" "us" (**) Option "xkb_options" "lv3:ralt_switch,terminate:ctrl_alt_bksp" (II) Cypress-Weikeng USB Adapter: initialized for relative axes. (WW) Cypress-Weikeng USB Adapter: ignoring absolute axes. (II) config/udev: Adding input device Cypress-Weikeng USB Adapter (/dev/input/mouse1) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event5) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/event2) (**) Macintosh mouse button emulation: Applying InputClass "evdev pointer catchall" (**) Macintosh mouse button emulation: always reports core events (**) Macintosh mouse button emulation: Device: "/dev/input/event2" (II) Macintosh mouse button emulation: Found 3 mouse buttons (II) Macintosh mouse button emulation: Found relative axes (II) Macintosh mouse button emulation: Found x and y relative axes (II) Macintosh mouse button emulation: Configuring as mouse (**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5 (**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE) (II) Macintosh mouse button emulation: initialized for relative axes. (II) config/udev: Adding input device Macintosh mouse button emulation (/dev/input/mouse0) (II) No input driver/identifier specified (ignoring) Please let me know if there are any other logs you need, or anything else. Thanks! ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New -- Touchpad not configurable in Kubuntu 10.04 B1 https://bugs.launchpad.net/bugs/556019 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
