[Bug 1733557] Re: Login screen showing Authentication Failure Switch to greeter...
In reply to #105 Have tested reverting that fix and it just re-introduces the bug "After locking screen there is no input field to type password for unlock" Having no input field is worse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failure Switch to greeter... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
As per https://patchwork.kernel.org/patch/10384111/ message from Bluez mailing list, editing 97-hid2hci.rules as follows works around the new uevents added to the kernel in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 -ACTION=="remove", GOTO="hid2hci_end" +ACTION!="add", GOTO="hid2hci_end" Bluetooth now works with kernels above and below 4.14. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767603] Re: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel
Duplicate of https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1759836 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767603 Title: BCM2046B1 and hid2hci generates highcpu usage due to udev since 4.14 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759836] Re: systemd-udevd consumes 100% of CPU
It's a known kernel bug that Dell bluetooth is broken in kernels >=4.14, so sticking with the old kernel that works for now. Kernel bluetooth bug causes bluez 97-hid2hci.rules udev rule to fail. systemd-udevd has always consumed 100% whenever a udev rule fails (could be argued that's also a bug but at least you become immediately aware there's a problem). Possibly no coincidence that the break was introduced at the same time kernel tree commits were made to btusb.c wrt. Dell 'features' being addded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1759836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651735] Re: $ mir_demo_server --help fails with an exception
Also occurs on Zesty installations that have been upgraded from Yakkety. Unity8 fails to launch (classic black screen) and unity8.log shows the error: "character conversion failed" This is due to incorrect multiple versions of boost being present on the system because they aren't removed when upgrading. Counted 6(six) different boost versions installed in Zesty because of taking the upgrade route through multiple Ubuntu versions. 'apt-get remove --auto-remove --purge' does not remove them so looks like a genuine dependency resolution problem when upgrading. Manually removing all the old boost versions works around the problem and allows Unity8 to work again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651735 Title: $ mir_demo_server --help fails with an exception To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1651735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
Many thanks Martin. Trawling through the linux-usb and distro kernel mailing list archives shows that the kernel blocking problem has been around for some time and discussed at length. What it seems to boil down to is this: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/drivers/usb/core/hub.c#n67 The fact that parameters exist to force or fallback to the old initialisation scheme indicates the kernel devs. are aware there could be problems with the way USB devices are initialised, depending on the USB device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546641 Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1546641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
So whether it be broken/missing libs or bad USB device enumeration causing upowerd to be either not available or slow to start, it would seem unity-settings-daemon could at least be improved to be robust enough not to segfault if upowerd is not present. In the meantime, I was able to solve the USB device problem to work around upower.service slow start by adding the kernel commandline parameters 'usbcore.use_both_schemes=y usbcore.old_scheme_first=y'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546641 Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301125] Re: Lock screen after idle time freezes unity
Still a problem in Xenial 16.04. I'm using Intel gfx driver so based on others using different video drivers (ati, nouveau and now intel) may indicate the problem lies at least not with the video drivers. Perhaps it's a problem with Unity's lockscreen? ** Changed in: unity (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301125 Title: Lock screen after idle time freezes unity To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1301125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
One last thing...ice in comment #12 said: "Some people say it has to do with a ASMedia USB Controller" Have found that USB enumeration failure can cause a bottleneck in systemd getting the upower.service unit to finally start. You'll know if the system is hit with this as it'll be much slower to boot and the kernel will spew errors of the type: kernel: usb 2-1.1: device descriptor read/64, error -110 kernel: usb 2-1-port1: unable to enumerate USB device Occasionally after several suspend/resumes, I have a USB device (wireless game controller) that must be unplugged/replugged to stop this error (simply rebooting does not fix). Have found on my laptop, if the USB enumeration boots through without any error then it's quick enough to have systemd start upower.service in time before u-s-d is started, otherwise the u-s-d segfault occurs as above. Thanks :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546641 Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1546641] Re: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
Looks to be a race condition where the session (and so unity-settings-daemon) is started before systemd has finished starting the upower.service unit. u-s-d tries to query the state of power and segfaults when upowerd hasn't finished initialising to be able respond. >From syslog: 17:14:31 kernel: unity-settings-[1722]: segfault at 0 ip 7fe3799805a9 sp 7ffec6513af0 error 4 in libupower-glib.so.3.0.1[7fe37996f000+25000] 17:14:50 dbus-daemon[460]: [system] Successfully activated service 'org.freedesktop.UPower' Confirmed this by doing the following: 1. Disabling lightdm from autostarting: systemctl disable lightdm 2. Reboot and wait until systemd starts upower.service 3. Start lightdm: systemctl start lightdm 4. u-s-d starts without issue and so default settings and themes are applied, media keys work, etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546641 Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1546641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332996] Re: QtCreator often halts for a minute
Broken again in 16.04 LTS exactly the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332996 Title: QtCreator often halts for a minute To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1332996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251915] Re: Dash + zeitgeist does not log use of KDE applications for 'Recently used'
Bug still present in Xenial. Creating symlinks as suggested in comment #2 has the unwanted side effect of creating duplicate entries for KDE applications in the Search and Applications lense. So it would seem the proper fix would instead be for Unity to grab the path of where the konsole.desktop file resides, and if it is found to be in /usr/share/applications/kde4, then the desktop filename presented to zeitgeist should be changed from konsole.desktop to kde4-konsole.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251915 Title: Dash + zeitgeist does not log use of KDE applications for 'Recently used' To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1251915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004197] Re: Opening new server opens to black the first time
Nope, still broken. Indeed it fails to ever work, black screen only for all Remmina connections :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004197 Title: Opening new server opens to black the first time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1004197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310404] Re: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design
Up to Wily now, still broken... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310404 Title: Enabling the onscreen keyboard in the accessibility menu changes lockscreen design To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1310404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1473269] Re: Wily login screen shows an all black notification bubble
Seems to be caused by changes in gtk+-3.16 as doing a test downgrade to gtk+-3.14 has the notification appear properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473269 Title: Wily login screen shows an all black notification bubble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1473269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420959] Re: xmir crashes when launching chromium
Full backtrace of crash. Seems also to be related to bug #1450581 ** Attachment added: gdb-xorg.txt https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1420959/+attachment/4390933/+files/gdb-xorg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420959 Title: xmir crashes when launching chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1420959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299872] Re: Quassel Client won't start with recent updates (3/30/2014)
That committed upstream fix was reverted due to some other dbus problems. Still tracking re-opened Quassel bug at http://bugs.quassel- irc.org/issues/1269 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to quassel in Ubuntu. https://bugs.launchpad.net/bugs/1299872 Title: Quassel Client won't start with recent updates (3/30/2014) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/quassel/+bug/1299872/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1420959] Re: xmir crashes when launching chromium
Same here, also using the Intel driver but happens in Vivid using Unity7. It appears any GL application in a Mir session will hard crash the session back to lightdm greeter. Am able to reproduce the same crash by using 'glxgears'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420959 Title: xmir crashes when launching chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1420959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1420959] Re: xmir crashes when launching chromium
BTW, the chromium crash is worked around by disabling hardware acceleration in chromium's settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1420959 Title: xmir crashes when launching chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1420959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251915] Re: Dash + zeitgeist does not log use of KDE applications for 'Recently used'
Still being hit with this bug on Trusty. Some digging into zeitgeist's source shows that it gets the application info from the *.desktop file using glib's GDesktopAppInfo https://developer.gnome.org/gio/2.33/gio-Desktop-file-based-GAppInfo.html#g-desktop-app-info-new Reading the info from the above URL and using konsole.desktop again as the example, zeitgeist will only find konsole.desktop if it is renamed kde4-konsole.desktop. Another solution is to create a symlink named /usr/share/kde4 that points to /usr/share/applications/kde4 and add /usr/share/kde4 to XDG_DATA_DIR desktop env. variable at login. ** Description changed: - Using Saucy 13.10, when using KDE applications launched from the Dash, - they do not show up as 'Recently used' neither in the Home or - Applications lenses. + Using Saucy 13.10 and Trusty 14.04, when using KDE applications launched + from the Dash, they do not show up as 'Recently used' neither in the + Home or Applications lenses. Seems zeitgeist or the information presented to it cannot get the path to the KDE application's *.desktop file. Using 'konsole' as a KDE application example: ~ $ /usr/libexec/zeitgeist-fts --log-level=DEBUG ** (zeitgeist-fts:28799): DEBUG: zeitgeist-fts.vala:106: got insertion notification ** (zeitgeist-fts:28799): DEBUG: Indexing event with ID: 6382 ** (zeitgeist-fts:28799): WARNING **: Unable to get info on application://konsole.desktop This happens because 'konsole.desktop' resides in /usr/share/applications/kde4/konsole.desktop If I symlink or copy 'konsole.desktop' to /usr/share/applications/konsole.desktop, then everything works as it should, zeitgeist index's the event correctly and Konsole shows under 'Recently used' for Home and Applications lenses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251915 Title: Dash + zeitgeist does not log use of KDE applications for 'Recently used' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
Hey all, I'm not sure if I should be posting to this bug or some other tracking type bug, or even as a github issue at https://github.com/darkxst/displayconfig so here goes...correct me if I'm wrong. I've been trying to get gnome-3.10 on Trusty using Jackson's packages for unity-settings-daemon and unity-control-center along with Tim's displayconfig pulled from his github repo. Everything is almost there except for the following issues: 1. Clicking 'Apply' in unity-control-center's 'Screen Display' dialog after making a change does not present the confirmation dialog messagebox that states Do you want to keep these display settings? with the option to 'Revert', 'Confirm' or 'Cancel'. As a consequence the timer for this messagebox silently ticks down in the background and the changed settings automatically revert to the previous setting. Some source digging reveals this messagebox is part of gnome-shell in js/ui/windowManager.js :( 2. In some rare instances, constantly clicking the 'Apply' button does actually get the setting to finally stick without it timing out, but the setting is not saved between desktop sessions. Let me know if I can do anything more to test, or even if this approach is still being developed as it's been a month since there was any action on this. Cheers :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295851] Re: Input lag after last update
Bug is still present here in mir-0.1.8+14.04.20140411-0ubuntu1 so may be slightly different to bug 1291755 ? Only other info I can offer is that with 0.1.7 I could Ctrl+Alt+func to a VT and back into the Xsession and that would work around the bug for some time (hour or two?) before I would have to do this again. With 0.1.8 this work around no longer seems to work and I have to restart the Xsession to get keyboard input to function correctly. Symptom starts as slow to respond to keyboard input (type a character and takes a few seconds for typed character to appear on screen). Shortly after this first symptom, displayed keyboard input degrades to being one character behind (type a character and character does not appear on screen until another character is pressed, or mouse is moved). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295851 Title: Input lag after last update To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1295851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277343] Re: XMir starts with black screen ([xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output)
Thanks again Daniel. http://bazaar.launchpad.net/~mir-team/mir/development-branch/revision/1405 fixes nicely, look forward to 0.1.6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277343 Title: XMir starts with black screen ([xmir] Failed to set new display config: ... std::exception::what: Invalid format for used output) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277343] Re: xmir crashes on startup (std::exception::what: Invalid format for used output)
Big thanks, applying the preview.diff from lp:~vanvugt/mir/eliminate- configure-output fixes the crash for me :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277343 Title: xmir crashes on startup (std::exception::what: Invalid format for used output) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277343] Re: xmir crashes on startup (std::exception::what: Invalid format for used output)
Only problem the elimination presents now is that unity-system- compositor will fail to build when it doesn't see 'configure_output'. unity-system-compositor-0.0.2+14.04.20140212.1/src/dbus_screen.cpp:66:28: error: 'class mir::graphics::DisplayConfiguration' has no member named 'configure_output' displayConfig-configure_output( ^ src/CMakeFiles/unity-system-compositor.dir/build.make:97: recipe for target 'src/CMakeFiles/unity-system-compositor.dir/dbus_screen.cpp.o' failed make[2]: *** [src/CMakeFiles/unity-system-compositor.dir/dbus_screen.cpp.o] Error 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277343 Title: xmir crashes on startup (std::exception::what: Invalid format for used output) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277343] Re: xmir crashes on startup (std::exception::what: Invalid format for used output)
It would seem the offending code comes from https://code.launchpad.net /~andreas-pokorny/mir/add-pixel-format-to-display- configuration/+merge/200294 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277343 Title: xmir crashes on startup (std::exception::what: Invalid format for used output) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1277343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212821] Re: Unity fails to load on old hardware on Saucy
I've been bitten by this also on a new install, exhibiting exactly the same blank desktop with no icons, side launcher or top panel. My gfx hardware is an Intel 855GM (not an 865 but is of the same generation chipset). The OpenGL failure (Root visual is not a GL visual) and the resulting compiz opengl plugin failure is due to the intel driver defaulting to the new 'sna' (Sandybridge) renderer. This generation of intel gfx cards needs the old 'uxa' renderer and so needs to be manually set in xorg.conf.d entry like so: # cat /etc/X11/xorg.conf.d/20-intel.conf Section Device Identifier Intel Graphics Driver intel Option AccelMethod uxa EndSection That should give you a very slow but working software rendered Unity desktop. It's debatable, but this slow desktop performance is probably unacceptable for everyday use. The card only supports up to OpenGL-1.3 and Unity3D needs OpenGL-1.4+ which is why it falls back to software render. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212821 Title: Unity fails to load on old hardware on Saucy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1212821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
Hear Hear! Been using this patch for quite some time now, so big thanks for maintaining sanity for the desktop people. However this previously working functionality is still spiralling in a downward direction. QT applications no longer show up in the systray and I've never had sni-qt work at all. Trying not to re-iterate what has largely already been said here regarding the amateurish breaking of applications that use the Linux DE standard systray (including nautilus file copy). Just like to add that all QT applications that previously ran in the systray using this patch, now don't show up unfortunately :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251915] [NEW] Dash + zeitgeist does not log use of KDE applications for 'Recently used'
Public bug reported: Using Saucy 13.10, when using KDE applications launched from the Dash, they do no show up as 'Recently used' neither in the Home or Applications lenses. Seems zeitgeist or the information presented to it cannot get the path to the KDE application's *.desktop file. Using 'konsole' as a KDE application example: ~ $ /usr/libexec/zeitgeist-fts --log-level=DEBUG ** (zeitgeist-fts:28799): DEBUG: zeitgeist-fts.vala:106: got insertion notification ** (zeitgeist-fts:28799): DEBUG: Indexing event with ID: 6382 ** (zeitgeist-fts:28799): WARNING **: Unable to get info on application://konsole.desktop This happens because 'konsole.desktop' resides in /usr/share/applications/kde4/konsole.desktop If I symlink or copy 'konsole.desktop' to /usr/share/applications/konsole.desktop, then everything works as it should, zeitgeist index's the event correctly and Konsole shows under 'Recently used' for Home and Applications lenses. ** Affects: unity (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/1251915 Title: Dash + zeitgeist does not log use of KDE applications for 'Recently used' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1251915] Re: Dash + zeitgeist does not log use of KDE applications for 'Recently used'
** Description changed: Using Saucy 13.10, when using KDE applications launched from the Dash, - they do no show up as 'Recently used' neither in the Home or + they do not show up as 'Recently used' neither in the Home or Applications lenses. Seems zeitgeist or the information presented to it cannot get the path to the KDE application's *.desktop file. Using 'konsole' as a KDE application example: ~ $ /usr/libexec/zeitgeist-fts --log-level=DEBUG ** (zeitgeist-fts:28799): DEBUG: zeitgeist-fts.vala:106: got insertion notification ** (zeitgeist-fts:28799): DEBUG: Indexing event with ID: 6382 ** (zeitgeist-fts:28799): WARNING **: Unable to get info on application://konsole.desktop This happens because 'konsole.desktop' resides in /usr/share/applications/kde4/konsole.desktop If I symlink or copy 'konsole.desktop' to /usr/share/applications/konsole.desktop, then everything works as it should, zeitgeist index's the event correctly and Konsole shows under 'Recently used' for Home and Applications lenses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1251915 Title: Dash + zeitgeist does not log use of KDE applications for 'Recently used' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1251915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170483] Re: The file manager (nautilus) handling the Desktop is not being enabled in live session
Still present in Saucy gnome-settings-daemon-3.8.5 0ubuntu9. Related bug here - https://bugs.launchpad.net/ubuntu-gnome/+bug/1198658 The gnome-settings-daemon patches mentioned above cause nautilus to segfault which to the user appears as no icons on the desktop. With those patches disabled, nautilus does not segfault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170483 Title: The file manager (nautilus) handling the Desktop is not being enabled in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1170483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170483] Re: The file manager (nautilus) handling the Desktop is not being enabled in live session
In reply to Comment #6: Based on this bug, 13.10 introduces a potential hierachical bug using gnome-settings-daemon-3.8.3~raring2-0ubuntu1 The bug manifests itself in 13.10 by exhibiting exactly the same symptoms as this bug even when 'show-desktop-icons' is enabled for org.gnome.desktop.background in dconf. In addition, the bug doesn't occur immediately on desktop session startup - but after some use, all desktop icons disappear and this last window minimise freeze bug starts to appear. Disabling and re-enabling 'show-desktop-icons' dconf entry for org.gnome.desktop.background mentioned above works around the bug. Disabling the following Ubuntu patches for gnome-settings-daemon fixes this: revert_background_dropping.patch 52_sync_background_to_accountsservice.patch git_revert_remove_automount_helper.patch But we're still left with the original bug of needing 'show-desktop- icons' dconf entry for org.gnome.desktop.background enabled. Feel free to link this bug to any other bugs that share the same symptom... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170483 Title: The file manager (nautilus) handling the Desktop is not being enabled in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1170483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
