[Bug 1875577] Re: Encrypted swap won't load on 20.04 with zfs root
Could you please backport this to focal, too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875577 Title: Encrypted swap won't load on 20.04 with zfs root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781654] [NEW] No way of displaying a tooltip in fallback mode
Public bug reported: Current status notifier/application indicator implementations such as KDE Plasma or the Xfce Status Notifier Plugin display the indicators "title" and "icon-desc" or "attention-icon-desc" properties in a tooltip. In fallback mode, i.e. when the icon is a tray icon, does not show a tooltip and neither provides an API to make use of the tooltip functionality of the GtkStatusIcon. This is specifically a problem for my project package-update-indicator which notifies of available package updates with an icon. If users miss the associated notification or do not use a notification daemon it is rather confusing without a tooltip providing the name of the indicator it belongs to as well as an brief explanation like "Updates available". I've created a patch which replicates the behavior of KDE Plasma or the Xfce Status Notifier Plugin in fallback mode by displaying a tooltip with the contents of the "title" and "icon-desc" or "attention-icon- desc". ** Affects: libappindicator (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/1781654 Title: No way of displaying a tooltip in fallback mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1781654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382977]
(In reply to Norbert Preining from comment #5) I just tried the patch from the second attachment (from Guido) on Debian/sid, but it does not fix everything. The selected application is now used, but changing the default application is still broken. In particular, right clicking on an item I see Open with A but when I right-click - Properties and check the Open with droplist, then there is a different value written. It seems that another place needs fixing, I cannot reproduce that here and I don't see how this is possible, the combobox in the properties dialog uses a ThunarChooserButton which calls g_app_info_get_default_for_type() to preselect the default application. So the preselected application in the properties dialog should always be correct and reflect what ~/.config/mimeapps.list contains. The context menu is what should be fixed by this patch (by calling the g_app_info_get_default_for_type() as the combobox does). Have you properly applied the patch before building thunar and are you sure you are actually running the rebuilt version? If yes, then please provide some more detailed information on how to reproduce this. In particular, temporarily remove ~/.config/mimeapps.list, log out and back in, change the default association of some filetype and then report what the context menu shows, what the property dialog combobox has preselected and what the contents of ~/.config/mimeapps.list are and what your glib version is. or do I need to use *both* of the attached patches in this bug? No, the second one is just a refactored version of the first one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382977 Title: Thunar open default not respecting mimetype To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1382977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382977]
(In reply to Eric Koegel from comment #9) Created attachment 5715 [details] Guido's patch This is Guido's patch in a git am-able format. Thanks, but Evangelos should be credited for investigating and fixing this, I only did some minor refactoring. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382977 Title: Thunar open default not respecting mimetype To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1382977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178373]
(In reply to Eric Koegel from comment #20) Created attachment 5541 [details] Suspend/hibernate upower 0.99 (no logind) So this version makes upower optional but still uses the shutdown helper. A couple of notes: - OpenBSD supports hibernation via /usr/sbin/ZZZ or /usr/sbin/apm -Z - on FreeBSD you might want to call /usr/sbin/acpiconf -s 3 for suspend for consistency, /usr/sbin/zzz still supports APM but I doubt there is any APM-supporting hardware left - on FreeBSD you can check for suspend/hibernate support by looking at the hw.acpi.supported_sleep_state property through the sysctl API, see sysctl(3)[1] and acpi(4)[2] [1] http://www.freebsd.org/cgi/man.cgi?query=sysctlsektion=3apropos=0manpath=FreeBSD+10.0-stable [2] http://www.freebsd.org/cgi/man.cgi?query=acpiapropos=0sektion=4manpath=FreeBSD+10.0-stablearch=defaultformat=html Also the long term plan still is to use a DBus-actiavted helper instead of sudo? Where should this live, both xfce4-session and xfce4-power-manager need to make use of it but either one depending on the other would probably not be nice. People run Xfce without xfpm and and xfpm is used outside Xfce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178373 Title: Restart spawns a password box To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1178373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178373]
(In reply to Eric Koegel from comment #16) (In reply to Guido Berhoerster from comment #15) (In reply to Eric Koegel from comment #14) Created attachment 5498 [details] Suspend/hibernate upower 0.99 (no logind) Since everyone else is doing the logind piece, I wrote a small patch so xfce4-session will work with upower 0.99 but without logind. Although I think it would be a good thing not to rely on logind, please do not extend this crude and ugly sudo hack that BSD and Solaris users have to put up with, but replace xfsm-shutdown-helper with a small DBus service and use PolicyKit to authorize access to shutdown/suspend methods. xfsm-shutdown-helper should just go away, PolicyKit is nowadays available even on the BSDs and Solaris. Indeed, I can look into doing that. I didn't know how long it would take to get a new project accepted by distros, especially something running as root. In the meantime, extending shutdown-helper will work until I (or someone) makes a daemon for that. I don't think that it's big deal, it will not be used by most major Linux distros anyway since they are all systemd-based and there is already precedence with xfpm-backlight-helper which gets executed as root through polkit. Speaking of, could you just execute xfpm-pm-helper through pkexec instead of sudo in the same way it is done with xfpm-backlight-helper? xfpm-pm-helper should probably disabled by default on Linux since distros either carry upower 0.99 or they have upower = 0.99 and systemd. Finally it'd be nice to install all of these helpers under $(libexecdir) instead of $(bindir) since they're not meant to be executed directly by the user and clutter $PATH. Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178373 Title: Restart spawns a password box To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1178373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301873]
(In reply to Olivier Fourdan from comment #25) (In reply to ale.carrazzoni from comment #24) So it should be fixed in GTK+ then? ... I just find unfortunate that GTK+ relies on such a mechanism. Exactly, so if you merge it, can you for this reason please add a wm tweak setting to enforce window decorations, i.e. keep the status quo? Anyhow, as we have a patch ready thanks to Alistair, I agree that patch should be merged. So what about the theming issue, do you wan to go with the flipped pixmaps? You also didn't comment on the issue Martin raised? @Matthias: Could give some feedback on a possible solution from the GTK side for non-GNOME environments where CSDs doe not fit well, especially my suggestion in comment#21? If needed I can also open a RFE on the GTK bugtracker to discuss this further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301873 Title: Add support for title-less windows To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1301873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301873]
I think that although CSD might be a good fit for GNOME they are problematic in Xfce for various well-known reasons: * CSD look out of place in a heterogeneous application environment (which is much more likely for Xfce than GNOME or KDE users since Xfce does not have such a broad range of native applications) where windows of applications using different toolkits such as GTK2 (most of Xfce for the time being), Qt, or Java are combined * xfwm4 has the ability to forcibly close windows of hung applications which is impossible with CSD and they cannot even be moved * xfwm4 allows to roll up a window, show a window on all workspaces or always keep it on the top layer, all of which is impossible with CSD * xfwm4 allows to customize the buttons shown in the titlebar, e.g. a button for pinng or rolling up windows, all of which is lost with CSD and leads to inconsistencies because such buttons are not even supported * xfwm4 allows to customize mouse actions on top of the window decorations such as double-clicking the title-bar or rolling up the window with the mouse-wheel, all of which is impossible with CSD Thus, CSD are IMO generally undesirable and unsuitable for Xfce and the above patch should not be merged. Rather, and not only because this affects Xfce but also setups which only use a window manager without a complete DE, or more importantly KDE, I think it is not unreasonable for asking the Gtk side to add a setting for disabling CSD. By that I mean not drawing its own border and hiding client window controls and disabling the MWM hints that disable the window manager's decorations. From reading about CSD on Matthias blog I figure that it is currently only possible to change the order of client side window controls and their appearance on dialog windows. Matthias, could you implement something like that as an xsetting? Our xfsettingsd could then use that setting to disable CSD by default when running an Xfce session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301873 Title: Add support for title-less windows To manage notifications about this bug go to: https://bugs.launchpad.net/xfwm4/+bug/1301873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932177]
(In reply to comment #15) (In reply to comment #14) Fixed in Factory. it's back again in 12.3-RC1 (or never got fixed?) ! I'm using 12.3-RC1 plus updates and run XFCE4. /usr/bin/gnome-keyring-daemon --daemonize --login gets started and it's loading offering all my ssh-keys, which is a no-go! when debugging my ssh-agent problems, I found the hint in some discussions to rename/remove nome-keyring-daemon (or remove execute permission). this worked fine for me -- until bug #805048: NetworkManager needs gnome-keyring-daemon to ask for wifi passphrases :-(( so gnome-keyring-daemon is back in businees, and trashes my ssh usage:-( looking for other solutions I found e.g. http://ubuntuforums.org/showthread.php?t=1655397 but sudo gconftool-2 --direct --config-source xml:readwrite:/etc/gconf/gconf.xml.mandatory --type bool --set /apps/gnome-keyring/daemon-components/ssh FALSE does not help. https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/932177/comments/20 does not work either for me, the key daemon still loads/offers all ssh keys (output of ssh-add -l). for now I've hacked the gnome-keyring-daemon to garble the path to my keys: diff ( strings /usr/bin/gnome-keyring-daemon~ ) ( strings /usr/bin/gnome-keyring-daemon ) 9543c9543 ~/.ssh --- ~/@ssh but of corse that's not the way to go:-( so my question for running XFCE4: how can I disable the ssh-agent functionality for gnome-keyring-daemon these days ??? That's currently not possible, you can either start all components of gnome-keyring-daemon (by enabling GNOME compatibility mode) or not start it at all. This bug was about making it work properly at all which has been the case since 12.1. The ability to selectively enable/disable components is a different issue and would need to be addressed upstream. Please file a new enhancement request, preferably on the upstream tracker or here if you want me to forward it for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932177 Title: XFCE (and other non-GNOME) desktops do not initialise gnome-keyring correctly / WARNING: gnome-keyring:: couldn't connect to PKCS11 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/932177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 803858] Re: Unable to switch between Chinese and English in LightDM
There several assumptions in the above list which cannot be taken as given: 1) the users language preference in known and can be easily set at the time an account is created 2) there is an user interface in the desktop environment to select the language of a session 3) every user of the system will be able to navigate in the system's default language to this interface in order to change it to his preferred/native language The first assumption is Ubuntu-specific, e.g. it is currently not possible to select the preferred language when creating users through YaST in openSUSE. E.g. in a large computer lab an admin creating accounts may not know what languages a user speaks. The second assumption is GNOME/KDE-centric, there is e.g. no native UI to switch the user's language in Xfce, LXDE, or when using a plain window manager. Even if there is, it will be very difficult for a user to find it if he/she does not understand the default language. Use cases where this becomes a problem are e.g. computer labs in public libraries or universities and even in my own household where not everyone speaks the preferred/native language of the owner of each computer. So I support the request to add this functionality back to LightDM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/803858 Title: Unable to switch between Chinese and English in LightDM To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/803858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 483116] Re: Screen can't dpms off/standby/shutdown, wakes instantly
*** This bug is a duplicate of bug 453812 *** https://bugs.launchpad.net/bugs/453812 This problem is as you wrote in the description closely related to, but not the same as bug #415023, rather it is a duplicate of bug #453812 which is linked to the appropriate upstream bug. In short, the keypress events that are observed here are resulting from the Intel Xorg driver setting the brightness to 0 before turning off the screen via DPMS. ** This bug is no longer a duplicate of bug 415023 brightness is broken on MSI WIND U100 ** This bug has been marked a duplicate of bug 453812 [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME) -- Screen can't dpms off/standby/shutdown, wakes instantly https://bugs.launchpad.net/bugs/483116 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 453812] Re: [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME)
Just for reference, the problem here is that the MSI Wind UXXX and its OEM variants generate keypress events in hardware each time the brightness level is changed which is a source of trouble (e.g. see bug #415023). Since the Intel Xorg driver sets the brightness to 0 before turning the screen off via DPMS, keypress events are generated which cause power management software such as gnome-power-manaager, powerdevil, or xfce4-power-manager to immediately turn it back on. the details are in the upstream bug. -- [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME) https://bugs.launchpad.net/bugs/453812 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 466253] Re: Brightness readjustment on continuous loop on startup
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- Brightness readjustment on continuous loop on startup https://bugs.launchpad.net/bugs/466253 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 415023] Re: brightness is broken on MSI WIND U100
** Bug watch added: GNOME Bug Tracker #601410 https://bugzilla.gnome.org/show_bug.cgi?id=601410 ** Changed in: gnome-power Remote watch: GNOME Bug Tracker #599112 = GNOME Bug Tracker #601410 -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 453812] Re: [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME)
Adding dmesg output, I have the same hardware and same problem. ** Attachment added: dmesg http://launchpadlibrarian.net/35485167/dmesg.txt ** Tags removed: needs-lspci-vvnn needs-xorglog ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete = Confirmed -- [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME) https://bugs.launchpad.net/bugs/453812 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 453812] Re: [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME)
** Bug watch added: freedesktop.org Bugzilla #24770 https://bugs.freedesktop.org/show_bug.cgi?id=24770 ** Also affects: xserver-xorg-video-intel via https://bugs.freedesktop.org/show_bug.cgi?id=24770 Importance: Unknown Status: Unknown -- [i945] [karmic] regression: I can't turn off LVDS on my MSI Wind (Intel 945GME) https://bugs.launchpad.net/bugs/453812 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 415023] Re: brightness is broken on MSI WIND U100
Disabling KMS just makes the problem appear less often. This is ultimately a bug in the MSI BIOS, if it chooses to handle the brightness keys in hardware it shouldn't emit keypress events. The power managers such as g-p-m, powerdevel, and xfce4-power-manager need to be told to work around this. For powerdevil patching hal-info would be sufficient as Felix Geyer has suggested, gnome-power-manager doesn't read this because it uses xrandr instead of HAL so I don't know how to fix it. Regarding xfce4-power-manager I don't know either. This bug is filed against powerdevil, gnome-power-manager, xfce4-power- manager, and hal-info and these need to be fixed. -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 415023] Re: brightness is broken on MSI WIND U100
A workaround is per defintion not a solution to the underlying problem which I and others have described a couple of times. However, with kernel modesetting disabled I have not been able to reproduce the second issue that I mentioned in comment #80. Can you please describe how to reproduce the flickering that you experience while kms is disabled? -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 452693] Re: screen brightness flickering up and down at startup for a while and everytime i try to adjust the brightness
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- screen brightness flickering up and down at startup for a while and everytime i try to adjust the brightness https://bugs.launchpad.net/bugs/452693 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 415023] Re: brightness is broken on MSI WIND U100
Please read comment 37, comment 65 and comment 69. The problem has been completely triaged, the MSI Wind handles brightness through the BIOS BUT each change of brightness levels also emits a keypress event which is then handled by gnome-power-manager, powerdevil, or xfce4-power-manager. There are two different problems: The first issue with this is that each keypress changes brightness twice, resulting effectively in only 4 instead of 8 levels that the hardware is capable of. This is happens with all previous releases of Ubuntu as well. The second issue is new in 9.10 and has been intoduced with kernel modesetting, that is gnome-power-manager and equivalents start switching back and forth between two adjacent brightness levels either due to a rounding bug or feedback loop (remeber that each time brightness levels are changed in software keypresses are emitted as well). There is actually a workaround for the second issue (the flickering people report over and over) and that is disabling kernel modesetting by passing nomodeset to the kernel at boot time. The solution to this problem is that power management software needs to be told that the brightness keys are handled in hardware. In the past this could be done by setting the HAL property laptop_panel.brightness_in_hardware to true as Felix Geyer has pointed out, however this is not read by gnome-power-manager because it handles the backlight through xrandr instead of HAL. -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 415023] Re: brightness is broken on MSI WIND U100
A possible workaround to avoid the flicker (at least in my case) is to disable kernel modesetting, that way g-p-m does not seem to get out of sync, although it is still buggy in that each brightness keypress is handeled twice, that is both by g-p-m and in hardware. The main problem is making g-p-m not react to the brightness key presses. The MSI Wind apparently handles them in the BIOS while still passing through keypress events which are noticed and reacted upon by g-p-m. Adding the brightness_in_hardware setting to HAL is not a proper solution because the Intel xorg driver supports handling the backlight through xrandr which g-p-m prefers over HAL and HAL support will most likely be dropped from g-p-m once all other drivers support this through xrandr as well. An please STOP spamming this bug with pointless and completely irrelevant comments, it makes the ubuntu bugtracker such a pain to use when one has to wade through dozens if not hundreds of posts to find some relevant information. -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 381461] Re: [i945gme] brightness fluxuates wildly on KMS (karmic)
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- [i945gme] brightness fluxuates wildly on KMS (karmic) https://bugs.launchpad.net/bugs/381461 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 458791] Re: the backlight is flashing
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- the backlight is flashing https://bugs.launchpad.net/bugs/458791 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 459777] Re: Brightness control behaves chaotically
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- Brightness control behaves chaotically https://bugs.launchpad.net/bugs/459777 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 415023] Re: brightness is broken on MSI WIND U100
Once again, you do not need to press a key, if you adjust the brightness in software the hardware emits a keypress. The main issue is that brightness adjustments need to be either handled in hardware or in software, i.e. by g-p-m, powerdevil etc, and that right now it is handled by both. This is broken in 9.04 as well, using the keys you effectively get only 4 brightness levels although it is capable of 8, there is just no flickering, which seems to be caused by a rounding bug when using kernel modesetting. The solution as I see it is that either MSI updates their BIOS or g-p-m and friends do not attempt to handle it. I don't know the equivalent of setting laptop_panel.brightness_in_hardware to true in HAL when using xrandr. I have asked on the gpm list but really don't have time to investigate any more into this. -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 441761] Re: Brightness is reset continuously
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- Brightness is reset continuously https://bugs.launchpad.net/bugs/441761 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 415023] Re: brightness is broken on MSI WIND U100
** Bug watch added: GNOME Bug Tracker #599112 https://bugzilla.gnome.org/show_bug.cgi?id=599112 ** Also affects: gnome-power via https://bugzilla.gnome.org/show_bug.cgi?id=599112 Importance: Unknown Status: Unknown -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 426010] Re: LCD brightness fluctuates on Gnome login
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- LCD brightness fluctuates on Gnome login https://bugs.launchpad.net/bugs/426010 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 413399] Re: [Karmic] [i945] Screen flickers due to constantly changing brightness level
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- [Karmic] [i945] Screen flickers due to constantly changing brightness level https://bugs.launchpad.net/bugs/413399 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 454276] Re: Screen brightness hops up and down
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- Screen brightness hops up and down https://bugs.launchpad.net/bugs/454276 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 447764] Re: MSI Wind U100 - brightness adjustment problem
*** This bug is a duplicate of bug 415023 *** https://bugs.launchpad.net/bugs/415023 ** This bug has been marked a duplicate of bug 415023 brightness is broken on MSI WIND U100 -- MSI Wind U100 - brightness adjustment problem https://bugs.launchpad.net/bugs/447764 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 415023] Re: brightness is broken on MSI WIND U100
Looking into this problem I just found four more duplicates of this bug and have counted about 45 people confirming this bug. This issue should at the very least be mentioned in the release notes, given the popularity of the MSI Wind U90, U120, U123, U100 models (as well as the various OEM versions such as the Medion Akoya E1210, Advent 4211, LG X110 etc.) I predict loads of duplicate reports after the release. -- brightness is broken on MSI WIND U100 https://bugs.launchpad.net/bugs/415023 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase-workspace in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 339091] Re: [i945] X freezes a few minutes after resuming
Does downgrading xserver-xorg-video-intel to version 2.4 work around this problem? -- [i945] X freezes a few minutes after resuming https://bugs.launchpad.net/bugs/339091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 251122] Re: vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
Marius Gedminas wrote: Guido, thank you for that reference! Do you have a link to the other side of the discussion (i.e. with Bram and other Vim developers, assuming there are other Vim developers)? From the thread referenced in the bugzilla entry it does seem as if it's Vim that's using a library incorrectly. Sorry, that was private correspondence with Bram. Basically vim has its own main loop and enters and leaves the GTK main loop at pretty much any event. Bram is fine with this but the GTK devs disapprove this usage. Point is, that GTK changed its behavior in an undocumented way and that the GTK folks acknowledge this as a problem. So it's either the GTK devs revert the behavior of RecentManager or somebody makes substantial changes to vim. If you want even more details on the vim side you can take a look at the GTK specific code here: http://vim.svn.sourceforge.net/viewvc/vim/vim7/src/gui_gtk_x11.c?view=markup http://vim.svn.sourceforge.net/viewvc/vim/vim7/src/gui_gtk.c?view=markup If you want to discuss this further I think it would be more appropriate if you mail me privately or take this to vim-...@vim.org . -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 251122] Re: vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
This problem cannot be easily fixed in vim, it uses GTK in a slightly unusual way and relied on the documented behavior of gtk_main_quit() which the GTK devs silently changed in 2.10.0 (by making RecentManager save the recently used files list). A real fix depends on the GTK devs reverting this undocumented behavior for which I have filed a RFE at http://bugzilla.gnome.org/show_bug.cgi?id=546691 . So if you care about this feel free to bug the GTK folks about it, complaining here will gain you nothing. -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 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 251122] Re: vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
As I already mentioned above the recently used files list is rewritten when quitting the last level of the GTK main loop, that is gtk_main_loop_level reaches 0. However the write happens only if the recent manager singleton exists which appears to be created lazily on the first invocation of GtkFileChooser. This allows for a simple but ugly workaround, namely using the depreceated GtkFileSelection instead. The code is still in vim, it is activated by commenting out the USE_FILE_CHOOSER define in src/gui_gtk.c. I have tested this with vim 7.1-056 in Ubuntu and this has gone into vim 7.2 upstream, see patch 7.2b.026. -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 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 251122] Re: vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
After some further digging into into the issue and with helpful hints from some friendly GTK developers I figured out the problem. It's basically that various GTK event handlers of the vim GTK2 GUI quit the gtk main loop (see the event handlers in src/gui_gtk_x11.c) which implicitly causes GTK to save the recently used files list. I have notified the author of vim. -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 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 251122] Re: vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
** Description changed: - Binary package hint: vim-gnome - After the first invocation of the GTK2-filechooser dialog, GTK's list of recently used files (~/.recently-used.xbel) gets written on events such as every single keypress, mouseclick etc. This causes considerable I/O activity and, when .recently-used.xbel is reasonably large, also a considerable slowdown of vim. - This affects the GTK2 flavor of vim as this bug is obviously specific to - GTK2. This occurs at least under Ubuntu 7.10 (vim- + This affects the GTK2 flavors of vim as this bug is obviously specific + to GTK2. This occurs at least under Ubuntu 7.10 (vim- gnome_7.1-056+2ubuntu2), 8.04 (vim-gnome_7.1-138+1ubuntu3), Debian unstable (see linked Debian Bug), and Fedora 9 (vim-X11-7.1.291-1.fc9.i386), but not under Ubuntu 7.04 (vim- gnome_7.0-164+1ubuntu7.2) and RHEL/CentOS 5.2 (vim-x11-7.0.109-3.el5.3.i386). + + Further testing revealed that the bug seems to occur with GTK 2.10, + this is supported by the fact that vim does not use GTK's recently used + files list directly and that the recently used files functionality was + added to the GtkFileChooser in GTK 2.11. + + Steps to reproduce: + strace -erename,open vim -g -f -i NONE -n -u NONE -U NONE + then use the Open/Save file dialog in vim + after that every keypress, mouseclick, mouse entering the vim window should result in ~/.recently-used.xbel getting rewritten -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 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 152784] Re: Mouse wheel scroll very slow
*** This bug is a duplicate of bug 251122 *** https://bugs.launchpad.net/bugs/251122 ** This bug has been marked a duplicate of bug 251122 vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written -- Mouse wheel scroll very slow https://bugs.launchpad.net/bugs/152784 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 251122] [NEW] vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
Public bug reported: Binary package hint: vim After the first invocation of the GTK2-filechooser dialog, GTK's list of recently used files (~/.recently-used.xbel) gets written on events such as every single keypress, mouseclick etc. This causes considerable I/O activity and, when .recently-used.xbel is reasonably large, also a considerable slowdown of vim. This affects the GTK2 flavor of vim as this bug is obviously specific to GTK2. This occurs at least under Ubuntu 7.10 (vim- gnome_7.1-056+2ubuntu2), 8.04 (vim-gnome_7.1-138+1ubuntu3), Debian unstable (see linked Debian Bug), and Fedora 9 (vim-X11-7.1.291-1.fc9.i386), but not under Ubuntu 7.04 (vim- gnome_7.0-164+1ubuntu7.2) and RHEL/CentOS 5.2 (vim-x11-7.0.109-3.el5.3.i386). ** Affects: vim Importance: Unknown Status: Unknown ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #456897 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456897 ** Also affects: vim via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=456897 Importance: Unknown Status: Unknown -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 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 251122] Re: vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written
I have forwarded this to [EMAIL PROTECTED] ** Description changed: - Binary package hint: vim + Binary package hint: vim-gnome After the first invocation of the GTK2-filechooser dialog, GTK's list of recently used files (~/.recently-used.xbel) gets written on events such as every single keypress, mouseclick etc. This causes considerable I/O activity and, when .recently-used.xbel is reasonably large, also a considerable slowdown of vim. This affects the GTK2 flavor of vim as this bug is obviously specific to GTK2. This occurs at least under Ubuntu 7.10 (vim- gnome_7.1-056+2ubuntu2), 8.04 (vim-gnome_7.1-138+1ubuntu3), Debian unstable (see linked Debian Bug), and Fedora 9 (vim-X11-7.1.291-1.fc9.i386), but not under Ubuntu 7.04 (vim- gnome_7.0-164+1ubuntu7.2) and RHEL/CentOS 5.2 (vim-x11-7.0.109-3.el5.3.i386). -- vim-gtk/-gnome use of gtk-filechooser causes recently used files list to be constantly written https://bugs.launchpad.net/bugs/251122 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 152784] Re: Mouse wheel scroll very slow
Please have a look at Bug #251122 and see if purging ~/.recently- used.xbel resolves the slowness issue. If this is the case, this bug should be marked a duplicate of Bug #251122 and subsequently closed as it has nothing to do with mousewheel scrolling. -- Mouse wheel scroll very slow https://bugs.launchpad.net/bugs/152784 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 188925] Re: Upgrade of glibc causes root filesystem not to be mounted ro on shutdown
I made a small init script in order to see if there are any unusual processess with open filehandles blocking the remount, however I couldn't spot anything on first sight. I used the following script: lsof #!/bin/sh lsof | tee /root/lsof.out sync; sync lsof and made it run just before umountfs and umountroot on shutdown/reboot (via update-rc.d lsof start 35 0 6 .). The output is attached. ** Attachment added: lsof.out http://launchpadlibrarian.net/11752660/lsof.out -- Upgrade of glibc causes root filesystem not to be mounted ro on shutdown https://bugs.launchpad.net/bugs/188925 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188925] Re: Upgrade of glibc causes root filesystem not to be mounted ro on shutdown
** Attachment added: screenshot of mount failing to mount / ro http://launchpadlibrarian.net/11752649/umountroot-output.png -- Upgrade of glibc causes root filesystem not to be mounted ro on shutdown https://bugs.launchpad.net/bugs/188925 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 188925] [NEW] Upgrade of glibc causes root filesystem not to be mounted ro on shutdown
Public bug reported: After upgrading the glibc packages the root filesystem cannot be mounted ro by /etc/init.d/umountroot during the following shutdown/reboot, resulting in a mount: / is busy Error (see also attached screenshot). This is very BAD and may cause data loss. I have tested this on fresh installed and otherwise unmodified X/K/Ubuntu 7.10 after an upgrade of the packages libc6 and libc6-i686 from version 2.6.1-1ubuntu9 to version 2.6.1-1ubuntu10 in gutsy-updates. It is easily reproducible in a VM as well as on physical hardware (see below). Steps to Reproduce: 1. install any Ubuntu 7.10 flavour with default settings (in a VM or your hardware) 2. on the first boot use grub's edit function to remove the quiet and splash options from the kernel line so you can see what's going on during boot/shutdown 3. boot 4. upgrade the libc6 and libc6-i686 packages from version 2.6.1-1ubuntu9 to version 2.6.1-1ubuntu10 5. edit /etc/default/rcS anch change VERBOSE=no to VERBOSE=yes in order to make the init scripts' output more verbose 6. switch to a vt and reboot the system 7. at the end of the shutdown/reboot process observe the following error: 8 * Mounting root filesystem read-only... mount: / is busy [fail] 8 ** Affects: glibc (Ubuntu) Importance: Undecided Status: New -- Upgrade of glibc causes root filesystem not to be mounted ro on shutdown https://bugs.launchpad.net/bugs/188925 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
