[Bug 44002] Re: Trivial actions are not appearing immediately
I'm sure something can be done about this. I've just done an strace on the menu opening, it tries to do ~1500 file opens (most of which are for non-existent files). First of all, most of those should be preloaded (actually, they should be cached once, then the cache should be preloaded in one step). The argument that it takes up memory doesn't hold, because the memory is still taken up the first time I open the menu. Second of all, any refresh can be done incrementally. There's no reason to flush the entire menu and re-open 1500 files, when one or two might be new. And especially you don't need to do it on every boot. Third, even a refresh could be done in parallel, with a nice -n 10 to make sure things don't get unpleasant. Last, I don't even get it why it has to read the entire menu. If I'm going for the package manager I have no reason to wait for th 1500 file accesses, when it fact I'm only going to see about 20 icons on the way. -- Trivial actions are not appearing immediately https://bugs.launchpad.net/bugs/44002 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 90409] Re: metacity forgets (on Hostname) annotantion on remote apps sometimes
Yes, it seems to work now correctly. Thanks! -- metacity forgets (on Hostname) annotantion on remote apps sometimes https://bugs.launchpad.net/bugs/90409 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 121796] Re: multiple non-working Open WithGimp entries
I still have the not working issue even after the latest upgrades. (But I also have multiple entries, so that might contribute.) -- multiple non-working Open WithGimp entries https://bugs.launchpad.net/bugs/121796 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 132054] can't create new keyring
Public bug reported: Binary package hint: gnome-keyring-manager This is about Ubuntu Gutsy, freshly updated. I can't create any new keyrings (including the default one, if there are none) with the gnome keyring manager. When I try to create a new keyring (menu KeyringNew Keyring) the new name is added to the keyrings list, but it's not accessible. I get a Gnome-Keyring-Manager-WARNING **: Failed to get keyring info. error in the console. I've snooped around through the sources a bit, and as far as I can tell: (1) create_keyring_callback in gnome-keyring-manager-keyring-manager.c receives a (correct) GnomeKeyringResult of GNOME_KEYRING_RESULT_OK, which should indicate that adding the keyring was successful, but then (2) it runs gkm_keyring_manager_update_keyring_info on the new keyring, which (3) runs gnome_keyring_get_info on it, and (4) update_keyring_info_worker_callback receives a GNOME_KEYRING_RESULT_NO_SUCH_KEYRING status. Which doesn't seem right to me. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-keyring-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- can't create new keyring https://bugs.launchpad.net/bugs/132054 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 132054] Re: can't create new keyring
I added gnome-keyring to the affects list, as it seems there's the problem. -- can't create new keyring https://bugs.launchpad.net/bugs/132054 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 79633] Network-config doesn't start the network
You have been subscribed to a public bug: Binary package hint: gnome-system-tools Hi! I have a Dell Latitude D620 laptop, which includes both wireless and Ethernet adapters. For some reason, the network-admin applet doesn't seem to work anymore. It worked just fine a couple of hours ago. I have an ADSL modem+router that allows both wired and wireless connection at home. I prefer to use wireless, and it worked just fine until this morning. I went to school, where I use a wired connection. Everything (at home and at school) is DHCP-configured. For some reason when I got home I couldn't get the network-admin applet to do anything. I would click on the network icon on the panel, pick my ssid and enter the password for the wireless link, enable DHCP, click OK, and nothing happens. As far as I can tell, some Perl scripts are frozen: [EMAIL PROTECTED]:~$ ps -A -f |grep perl root 6151 1 0 21:09 ?00:00:00 perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m HostsConfig root 6155 1 0 21:09 ?00:00:00 perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m Platform root 6161 1 1 21:09 ?00:00:00 perl /usr/share//system-tools-backends-2.0/scripts/SystemToolsBackends.pl -m IfacesConfig bogdanb 6234 6057 0 21:09 pts/000:00:00 grep perl ** I couldn't get the wired connection either, but I'm not sure if it's because there's some process hanging. (I did kill the perl scripts before trying, though.) After several trials I had to enable the wired connection by hand (ifconfig eth0 up and dhclient eth0). I have no idea how to start the wireless by hand, though. Let me know if there's any info that I can give to elucidate this. ** Affects: gnome-system-tools (Ubuntu) Importance: Undecided Assignee: Ubuntu Desktop Bugs Status: Incomplete -- Network-config doesn't start the network https://bugs.launchpad.net/bugs/79633 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 79633] Re: Network-config doesn't start the network
Hi, thanks for reminding me of this. It's working now, you can close this safely. -- Network-config doesn't start the network https://bugs.launchpad.net/bugs/79633 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 132054] Re: can't create new keyring
Yes, it seems to be working now. Thanks! ** Changed in: gnome-keyring (Ubuntu) Status: Incomplete = Fix Released ** Changed in: gnome-keyring-manager (Ubuntu) Status: New = Fix Released -- can't create new keyring https://bugs.launchpad.net/bugs/132054 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 13199] Re: Drag n' Drop directories from File-Roller is somewhat tricky
This is an old bug as far as I know. Initially the behavior was the one described above, but now drag and drop doesn't work at all. There are some bugs registered on that, this should probably have it's name changed and linked as a duplicate. -- Drag n' Drop directories from File-Roller is somewhat tricky https://bugs.launchpad.net/bugs/13199 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 104739] [apport] gnome-panel crashed with SIGSEGV
Public bug reported: Binary package hint: gnome-panel The only possibly relevant operation I was doing was removing some kde packages (I use almost only gnome). More exactly I was almost done with: $ sudo aptitude remove kcontrol konqueror konsole kraptor kraptor-data ktorrent Maybe the application panel was changed and something went wrong. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Mon Apr 9 12:32:43 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 2.18.0-0ubuntu3 PackageArchitecture: i386 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/bogdanb ProcEnviron: LANGUAGE=en_US:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gnome-panel StacktraceTop: ?? () from /lib/tls/i686/cmov/libc.so.6 ?? () from /usr/lib/librsvg-2.so.2 ?? () ?? () ?? () Uname: Linux cimer 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-access pulse-rt scanner video ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/104739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 104739] Re: [apport] gnome-panel crashed with SIGSEGV
** Attachment added: CoreDump.gz http://librarian.launchpad.net/7222326/CoreDump.gz ** Attachment added: Dependencies.txt http://librarian.launchpad.net/7222327/Dependencies.txt ** Attachment added: Disassembly.txt http://librarian.launchpad.net/7222328/Disassembly.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/7222329/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/7222330/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/7222331/Registers.txt ** Attachment added: Stacktrace.txt http://librarian.launchpad.net/7222332/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://librarian.launchpad.net/7222333/ThreadStacktrace.txt -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/104739 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 105090] Keyboard Shortcuts config applet doesn't allow user shortcuts (among other things)
Public bug reported: Binary package hint: gnome-control-center I'm not sure what the package is, the program is gnome-keybinding- properties. This would be a very nice program, if it would be a bit more configurable. The most annoying thing is that it's impossible to add new operations. For instance, I would like to have a shortcut to rotate the orientation of my screen. That's an easy command, xrandr -o left -- why can't I add it there and use a shortcut for it? Second, I'd like to be able to enter several shortcuts (at least two) for some commands? Sometimes I like to have shortcuts in two different places, one for when I'm typing (so my hands are all over the keyboard) and one for when I'm doing something else and I just want to press a key combination one-handedly. Third, I'd like to be allowed to see (and change) what the built-in commands do (at least when it's accessible from a different command). This would allow me to learn and tweak the commands. Fourth, the applet is really fussy about Start-button shortcuts. For instance, right now I can't get the computer to lock the screen using start+L, though Ctrl+Alt works. (Start is reliably detected as Mod4, so it's reasonably-well configured.) Fifth, I'd like it to integrate commands from other applications I have installed that use global shortcuts. (For instance, I use Amarok with several global shortcuts. Why should I go somewhere different to configure them?) ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- Keyboard Shortcuts config applet doesn't allow user shortcuts (among other things) https://bugs.launchpad.net/bugs/105090 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 105090] Re: Keyboard Shortcuts config applet doesn't allow user shortcuts (among other things)
This is on latest Feisty, btw. -- Keyboard Shortcuts config applet doesn't allow user shortcuts (among other things) https://bugs.launchpad.net/bugs/105090 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 105101] the lock screen thing is slow to appear after opening the lid
Public bug reported: Binary package hint: gnome-screensaver This is on Ubuntu Feisty, up to date, running on a Dell Latitude D620 laptop (Intel video). I have the computer set up to lock the screen when I close the lid. (This mostly works.) When I open the lid, though, there's almost always a delay before the unlock window appears. I can open the lid, type the password, and still have to wait three-four seconds, sometimes more, before the enter password window appears. It receives the already-typed password and then goes away in a second or so. Note that the screen turns on pretty much instantly (the back-light is usually on by the time the screen is up). Also, the laptop is NOT in stand-by or anything, it's running normally. The password-entry box should appear instantly (by the time the back- light turns on) and disappear the moment enter is pressed. After all, it's an extremely resource-light application. (It's OK if the desktop takes a bit to redraw after; that's a potentially slow operation. But just showing the password box on a black screen should be very quick.) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: Unconfirmed -- the lock screen thing is slow to appear after opening the lid https://bugs.launchpad.net/bugs/105101 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 105101] Re: the lock screen thing is slow to appear after opening the lid
I don't think it's something particular to my machine. It doesn't happen to you, too? I tried this and it happens the same way with the screensaver. (I have it set up to just shut the screen off, and lock it.) When I move the mouse, the screen turns on, but it takes a couple of seconds for the password dialog to appear. (It takes a bit longer for the lid thing, but this way it can be tested with a desktop, too. However, a desktop screen tends to turn on a bit slower than a laptop's, so keep that in mind.) -- the lock screen thing is slow to appear after opening the lid https://bugs.launchpad.net/bugs/105101 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106570] keyboard shortcut-commands are hardcoded
Public bug reported: On Ubuntu Feisty -- and I presume all older variants -- all commands in the Keyboard Shortcuts applet are hard-coded. The program is gnome- keybinding-properties. The actions list should be completely configurable: * existing commands should be visible to and changeable by the user; * users and applications should be able to add new commands (or delete existing, unused ones that clutter the menu); * the organization of commands into sections, as well as adding and deleting sections, should be change-able. All this can be done without adding complexity for beginners. The first could be achieved by adding a right-click menu to commands (advanced users are already trained to try this). The second needs only an Add action button at the bottom, between Help and Close (applications could add new sections automatically when installed). The third can be done with drag and drop, and perhaps an Add section button. Bug #4265 is a special case of this bug. ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- keyboard shortcut-commands are hardcoded https://bugs.launchpad.net/bugs/106570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106570] Re: keyboard shortcut-commands are hardcoded
Some examples: 1) User X (semi-advanced user, but not experienced with Linux) would like to know how to lock out the screen from a script. He could right- click on the action and see that the command is gnome-screensaver- command --lock (or some variant thereof). 2) User Y (me) would like to have a shortcut to rotate the orientation of my screen. That's an easy command, xrandr -o left -- which could be added by clicking Add action. 3) User Z installs a new music player (say, Amarok), which has the useful Hide/Show window option. Instead of editing that through Amarok's menu (which is a new and unknown menu to the user), Amarok's installer could add a new action to the Sound section (which should probably be called multimedia, since the same keys are useful for video, too). 4) User Y (me, again) doesn't use workspaces that much. He would like to remove (or hide) half of the actions in the Window Management section, that clutter the window uselessly (for him). -- keyboard shortcut-commands are hardcoded https://bugs.launchpad.net/bugs/106570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 106573] can only add a single key combination to the keyboard shortcut applet
Public bug reported: On Ubuntu Feisty -- and I presume all older variants -- each action in the Keyboard Shortcuts applet can have only single shortcut attached. (The program is gnome-keybinding-properties.) There should be at least a pair of primary/secondary shortcuts for each action. (See for example Amarok's global shortcuts.) Example usage: I touch-type, and I usually have lots of shortcuts all over the keyboard that can be very easily typed when doing other work. However, many of them are hard to press one-handed, for example when I'm not working and I just want to skip a track. The reverse is also true: key combinations that are easy to press one-handed are unpleasant to use when touch-typing: these are touches close to the corners, and they need some finger-twisting to reach. ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- can only add a single key combination to the keyboard shortcut applet https://bugs.launchpad.net/bugs/106573 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12153] Re: Cannot use Windows key in keyboard shortcuts
This is still not working in Feisty. This thread seems a bit complex, bug #16815 seems to more closely match my problem. The key is recognized as a modifier (Mod4), but it only works for some commands. For instance, it works for starting a new terminal, but it doesn't work for locking the screen. -- Cannot use Windows key in keyboard shortcuts https://bugs.launchpad.net/bugs/12153 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 109356] the CPU History graph info is unclear
Public bug reported: Binary package hint: gnome-system-monitor Hi! This report is about System Monitor 2.18.1.1, running on Ubuntu Feisty. It would be a nice fix for Gutsy. Currently the CPU History graph in the System Monitor is a nice tool for a quick estimate of the current CPU usage, but only for a very rough estimate. The main problem is that the units are not very clear: the time axis is not marked at all, so I can at most estimate how long a spike took; the height is marked in percent -- but doesn't mention exactly of what. I'm using Ubuntu on a Centrino Duo laptop, which can change the frequency of each processor according to several factors. (I'm not sure if it can scale each core separately, though. The factors I know are load and whether or not I'm plugged in, there may be some other heuristics.) All this means that xy % processor usage can mean very different things in terms of how much work the computer is doing. At the very least, the legend below the graph -- [color] CPU#: ##.# % -- should be changed to something like [color] CPU#: ##.# % usage (at ## GHz) -- though this doesn't fix the graph. Maybe a different line (different shade or dotted) could indicate the frequency of the processor. ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: Unconfirmed -- the CPU History graph info is unclear https://bugs.launchpad.net/bugs/109356 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 109374] The History graphs really need history
Public bug reported: Binary package hint: gnome-system-monitor Hi! This report is about System Monitor 2.18.1.1, running on Ubuntu Feisty. It would be a nice fix for Gutsy. The System Monitor is a nice tool for a quick estimate of the current CPU usage, but it could be much more useful if it actually gave a bit more history. First of all, the time scale is not marked. So I estimate it always shows me approximately one minute of history, but I can't tell for sure unless I measure it by hand. (I mentioned this in bug #109356, too.) Second, it only starts recording the history from the moment I open the window. This means that if I open the window in response to unresponsiveness (for instance), I can't see which of the three graphs was actually the problem (CPU, memory or network); usually the window takes its sweet time to load, so the spike is probably gone by the time it shows up. Third, even if I left it open all the time to record such a spike, there's no kind of pan zoom, so I can't look more than a couple of minutes in the past. I'm entering this all together as it's a more of a wishlist (rather than just a wish for the program's wishlist). I'd like the program to go a bit the way of the battery monitor (and, why not, include that too; it's a system monitor, right?), and even a bit more (pan/zoom). I'm not sure exactly how the system monitor works, but I think a generic system monitor process would be a good idea: it would run continuously in the background, gathering all sorts of info (processor, memory, IO usage, power statistics, battery charge, etc) at predefined frequencies (of the top of my head, between once each second and once each minute might be reasonable). It can save parts of it (aggregates for longer periods) to disk, in such a way as to not consume lots of resources. These logs would be available to the users when they open the System Monitor window. (Conservative cost estimate: 32 bits/value, 100 values monitored, 1 Hz = ~1.5 MB per hour; this could be easily kept in RAM on new machines. However, whenever the hard drive is used we can also copy parts of it to disc, with low priority IO, so we don't change the spin-down frequency much. With a 100 MB hard-drive budget we could keep almost three days of history with second-precision. Most users won't need detailed measurement for that long in the past, so for things that go more than a day, or even an hour, we could aggregate stuff, so we only save per- minute statistics. So each day we'd have to input the last day's logs, about 40 MB of saved data, aggregate it (it only takes simple averaging, usually) and output ~ 0.7 MB for 1-minute precision, or ~140 kB for 5-minute precision. With another 100 MB, we could have these logs for 4 months (1 minute) or almost two years (5 minute). This doesn't mention compression -- most values don't need 32 bits, and don't change randomly all the time. I think this would be potentially very useful at little cost (my /var/log is 25 megs, 200 is just an order of magnitude above), and not at all intrusive for users who don't need it. And it could offer interesting options in the long term. Just an example: it would become feasible to actually find out how a driver update changes power usage, by gathering the logs from users who use the driver, a month before and after -- properly anonymized, of course -- and see if there's any correlation. If the log contains programs used -- this is more problematic -- we could even check how optimizations perform in the real world.) ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: Unconfirmed -- The History graphs really need history https://bugs.launchpad.net/bugs/109374 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 109374] Re: The History graphs really need history
If anyone is interested by this bug in the future, the specification was added at https://blueprints.launchpad.net/ubuntu/+spec/unified-system- monitoring (there is a link to the wiki there). Mr Bacher, any comments on the blueprint would be much appreciated :) -- The History graphs really need history https://bugs.launchpad.net/bugs/109374 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 82504] gnome-panel autohides inconsistently
Public bug reported: Binary package hint: gnome-panel Hi! I'm using Ubuntu Feisty (the latest version from the official repositories) and I have a bit of a problem with the gnome-panel. I set the panels in a very similar arrangement as the default one -- a panel on the top side of the screen and another on the bottom, with a few applets changed and shuffled. I set both panels to autohide, as I like having my full screen available for applications. I also tweaked a bit the settings using the configuration editor: I set the hide/unhide delay to zero, and the size when hidden also to zero. This works almost always exactly the way I wanted it: the panel disappear completely when not used, and appear instantly when needed. However, for some reason I can't determine, sometimes I notice that one of the panels (I've seen it happen to either at some point) remain unhidden, despite the mouse cursor being outside them, and even clicking inside the windows. If I enter the panel with the mouse (no click is necessary) it will then disappear when the cursor leaves it. Like I said, I haven't been able to notice exactly what causes the panel to remain up -- but it always happens after I did something with it (it never pops up by itself). It seems for some reason it misses (or doesn't receive) a mouse-leave event or something similar. Please let me know if I can help diagnosing this in any way. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-panel autohides inconsistently https://launchpad.net/bugs/82504 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 82504] Re: gnome-panel autohides inconsistently
No, I don't have any text-entry applet on either panel. About bug #45974 I doubt it's related: I did remove the default menu applet (the one with the Applications/Locations/System menus) and replaced it with the single-icon menu. However the same issue appears for both panels. bug #4873 seems to be about a sliding panel. Mine isn't sliding, it hides towards its edge rather than to the side. (It doesn't have the arrows either.) -- gnome-panel autohides inconsistently https://launchpad.net/bugs/82504 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 82504] Re: gnome-panel autohides inconsistently
After a bit of playing with the panels I found at least one reproducible case where the panel remains opened: 1) First set at least one panel to autohide. (I don't think it matters, but mine has hidden size and hide delay set to zero.) 2) Start Firefox, and resize it's window to smaller than the screen. 3) With Firefox having the focus, make the panel unhide by sliding the mouse over it. (Don't click it!) Keep the cursor there so the panel stays unhidden. 4) Press F11 on your keyboard. This will make Firefox go in full-screen mode, which means it goes above the panel. (Note that the panel is always on top of normal windows.) 5) Move the mouse out of the (hidden) panel's surface (to the middle of the screen, for instance). Keep it there. 6) Either (a) press F11 again to make Firefox a window or (b) press Alt- Tab to switch to another (not-fullscreen) window. (This will make Firefox loose its on top status.) Result: Now the panel is visible, but the mouse is not on it. Expected result: The panel should have hidden itself at step (4) or at step (5) -- because the cursor is no longer on it. -- gnome-panel autohides inconsistently https://launchpad.net/bugs/82504 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 82504] Re: gnome-panel autohides inconsistently
Yes, there's probably a large class of similar issues depending on unusual ways of losing focus. Looking at your thread, this seems to be at least influenced by metacity's focus behavior. I marked this as affecting metacity too, I think someone from there needs to at least take a look at it. ** Also affects: metacity (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-panel autohides inconsistently https://launchpad.net/bugs/82504 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80755] Re: extracting doesn't work right
I've noticed this with all archive types I tried (rar, tar.gz, tar.bz2, zip). The archive is on the Desktop (but it happens even if it isn't). The home folder is on a different partition than the root, but this shouldn't be visible to the program, right? The same thing happens if I click Extract on the toolbar or in the file's right-click menu. It happens with any kind of archive contents. -- extracting doesn't work right https://launchpad.net/bugs/80755 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80755] Re: extracting doesn't work right
OK, I noticed something that may give the solution: To extract something, you are displayed a dialog named Extract which allows you to pick the destination of the files and some options. The dialog is a variant of the standard Open/Save dialogs of Gnome. These dialogs have on the top side a list of buttons that mirror the path of the displayed directory. In my case, this means a button for my home folder, followed by a button for the Desktop (the displayed folder) and preceded by a left-pointing arrow to go higher in the hierarchy. (There's also a Create folder button.) To the left of this string of buttons, there's a button with an edit text icon. When clicked, this hides/displays a line of text-entry just below the buttons, labeled Location. You can enter a relative path in that line, and navigating around using the icons below changes its contents in some weird way. OK, the point is, the problem I reported above only shows when that line is displayed. If the line is hidden, everything works OK. (i.e., the extract button works.) If the line is displayed, it only works after rummaging a bit through the files. I'm not sure what's wrong with it, but I believe it thinks you didn't choose a directory until you do some navigation. There must be some hidden variable there, because the line is empty when the dialog is displayed, and it doesn't work, but after walking a bit on the disk and returning to the desktop it's still empty, the whole dialog looks exactly the same as in the beginning, but now it works. -- extracting doesn't work right https://launchpad.net/bugs/80755 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 83034] panel-autohide leaves a one-pixel line on the desktop
Public bug reported: Binary package hint: gnome-panel Hi! I have a bit of a weird issue. I set both panels (in the usual topbottom configuration, with some widgets changed) to autohide, and I changed the settings in the configuration editor to have the size on auto-hide of zero. (I also changed the delay to zero, but I doubt this matters.) The weird thing is that they still leave exactly one pixel visible. I actually didn't notice this for top panel because it's a bit darker. I tried and this happens for side panels too. It's not really a huge issue, but it's still weird. This is on Feisty, freshly updated from the normal repositories. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed -- panel-autohide leaves a one-pixel line on the desktop https://launchpad.net/bugs/83034 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 83034] Re: panel-autohide leaves a one-pixel line on the desktop
By the way, if you don't know how to check this, the relevant keys are in the Configuration Editor, the node: /apps/panel/toplevels/whatever panel you have/auto_hide_size Set it to zero, set the panel to autohide (check key auto_hide right above the other), then move the mouse on and off the panel to make it hide. You might need to temporarily disable the wallpaper and/or change the desktop color to notice the line (black works best for me, but I guess it depends on your theme). -- panel-autohide leaves a one-pixel line on the desktop https://launchpad.net/bugs/83034 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 83034] Re: panel-autohide leaves a one-pixel line on the desktop
I don't mean to bug you, but wouldn't it be better to mark this as affects upstream with a link to the bug you gave? I was under the impression that that way the bug manager will automatically follow the status of that bug and notify us if it's fixed, isn't that right? -- panel-autohide leaves a one-pixel line on the desktop https://launchpad.net/bugs/83034 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84722] deskbar-applet requires too many keystrokes
Public bug reported: Binary package hint: deskbar-applet The deskbar applet is a bit annoying by needing too many clicks/keystrokes to use. There's a bit too much redundancy. Consider the attached screenshot: I write picard in the entry. The first line accessible with the arrows is the Action category -- which is unnecessary because there's no other category right now. Also, assuming the deskbar guessed right, it seems that you have to click 'down' twice to get at the first result. (I know I just have to press Enter, but that's not obvious; perhaps the active line should be selected, so I have a suggestion of what would happen when I press Enter.) Then, running Picard is presented twice. There's no difference between the two options. Perhaps they should be combined, or at least move the least likely one at the bottom of the list (the one taken from the apps menu is prettier). As it is now, if I wanted to actually search for picard in beagle, I would have to press 'down' four times, then Enter, when it fact it is the second option. As it should be, the first entry should be always selected (and activated at the first Enter press), the 'search in picard' should be immediately below it, and the first 'down arrow' press should select it. Another thing: since the deskbar is supposed to allow keyboard navigation, the most likely entries should have shortcuts, either like Alt+3 to _run_ the third option or Alt+b to choose beagle search, Alt+g for google, etc. for some standard ones. Actually, since beagle also searches for applications and stuff, perhaps it would be nice to actually display beagle search _results_ in real time in the box. It would jump over one new window display and one Enter press. ** Affects: deskbar-applet (Ubuntu) Importance: Undecided Status: Unconfirmed -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84722] Re: deskbar-applet requires too many keystrokes
Nevermind that last paragraph, I just found out it can do live search. ** Attachment added: screenshot of the issues in the first post http://librarian.launchpad.net/6398010/screenshot.png -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84722] Re: deskbar-applet requires too many keystrokes
But I still don't like it because of navigation issues :-) For the same simple search (picard), I get a screen-high list of things --- with a scrollbar, that can' be mouse-clicked! -- that is near-impossible to walk through. In this example, categories with more than, say, five entries, should display only the likeliest three (or the first if there's no other info) and allow easy navigation: for instance, in this example: - the Files section should display only three entries, among which should be the picard folder (that's currently near the bottom) - the Files section should have an Alt-F shortcut marked near its title. When I press it, the section should be selected, and: - left/right should navigate between pages - space should toggle between the contracted and and expanded list - enter should probably open the first hit, and 'down arrow' should probably select the second hit. ** Attachment added: too large list http://librarian.launchpad.net/6398022/Screenshot2.png -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 84722] Re: deskbar-applet requires too many keystrokes
Here's a sketch of how it could (and I think it should) work by default (compare with the previous too large list screenshot): *) sections: - Section markers can't be selected (only action-lines can be), but the one containing the currently selected action is active. Up-down skips the section markers. - The currently inactive sections have shortcuts to be reached quickly. - the active section shows useful keys: up/down, space for a short section, left/right, space for a large section. Up/down work for large selections too, of course, but left/right is a bit more important (it changes the page). - space toggles the current section between normal (at-most-three entries), expanded (see last panel) and compacted. When one selection is expanded this way, the others are compacted. I think expanded status should be forgotten between uses, but compacted should be remembered (as it is now). - the active section should be visibly marked as selected by color (it was too hard to draw, I show this as a bar of color). This should be less striking than the color used to highlight the current action (black in my sketch, it could just be darker). - sections with more than 4 entries are paged by each 3 elements (unless there are no other sections for a particular search) - sections with few entries (which are not paged) don't display the number on the right. *) Actions: - sections are paged/compacted so that no more than a dozen actions are shown - users can add a short-cut for important actions -- Alt-G for google in this case. - All other visible actions are given a number from 1 to 0 as a shortcut. Pressing Alt+4 in the first panel would open album.py - Except: the currently selected action has Enter shown. The numbers are recycled when the selection is moved with up/down. (see last panel) - Also, actions with shortcuts are skipped. - Since no more than 10-12 actions are shown, we shouldn't run out of numbers. The left panel is what should be shown after just typing picard. Note: - the redundant execute picard is hidden from the actions - the most likely choice (Launch picard) is selected. It shows Enter to the left, meaning that Enter will execute that option. - pressing Alt+1-9 or Alt-G would execute the respective action. - pressing down would select search for picard using beagle - launch picard will show (alt+)1 as a shortcut, because enter now starts the search Pressing Alt+F moves to the middle panel: - the files section is active - since it has many results, it's paged into threes. If the 'web' section wouldn't be there, it could be paged into sixes. - because it's now active, it shows useful key-strokes - because it's paged, left-right can cycle between pages; space would move to the right-most panel - because it's no longer active, the Actions section shows a short-cut instead of actions. - the Open [folder] picarded action is the first in the active section, so it's selected - it gets the enter shortcut, and the numbers are redistributed. - down would move to open album.py - up would move the selection to Search for picard using Beagle, and the Actions section would become active. Pressing space expands the current section if it's paged. This moves to the rightmost panel (but the list of files shouldn't change, neither the selection): - all inactive sections are colapsed - pressing their shortcut would de-expand and de-activate the files section. - even short sections show the number of actions in this state - the active section expands to fill all 10 action-slots available - pressing space again would reverse the expansion - any sections 'colapsed' before the expansion remain colapsed - if it has more than 10 entries, it is still paged with left/right ** Attachment added: mock of desired navigation http://librarian.launchpad.net/6399505/sketch.png -- deskbar-applet requires too many keystrokes https://launchpad.net/bugs/84722 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87796] the calendar of the clock applet is slow
Public bug reported: Binary package hint: gnome-panel The gnome panel has a clock applet that displays a clock on any panel, in several different display modes. When clicked, the clock displays a calendar view of the current month, with the 'today' date selected. The problem is that the display is slow. The first time I open the calendar in a session, it takes several seconds to display the window. After that, it's a bit better, but it still takes around a second to show the calendar window. It takes about a second to hide it, too. This on a Centrino Duo with hardly any CPU load... It's not a show-stopper by any means, but it creates a very strong sensation of unresponsiveness. I also have the impression that the first, longer, delay actually freezes the panel for a few seconds, but since it only happens once per session I can't tell with certainty. Considering that things like Gaim display their much larger window without any noticeable delay, this is a bit embarrassing. (This is on freshly-updated Ubuntu Feisty.) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed -- the calendar of the clock applet is slow https://launchpad.net/bugs/87796 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I already said this, but I think I should stress it again: it's not the actual act of rebooting/shutting down/etc that causes the freeze, it's the chooser window. The computer freezes even if I try to cancel the shut-down. In contrast, sudo shutdown -[r|h] now works. I'm frustrated because I have no idea where to look for more diagnostics. I tried (from a console) listing the processes before and after the window is displayed and I saw no relevant changes. I don't know who owns that window, is it the panel? ** Also affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24669] Re: Applications menu lags to refresh cache after installing new application
I couldn't open the link to upstream, not sure if it's a temporary problem. This and bug #44002 are probably instances of the same problem: the first time the menu is displayed, and after a change, it is completely regenerated. It looks very bad, because it feels like the whole interface froze. (It doesn't, but since the user's focus is on the menu, it seems that way.) I know the menu is regenerated on changes, but there's no need to regenerate the entire menu. Most of the time there's only one or two entry added/removed. The menu should be displayed from the cache, and only the changed items should be modified. Even more, usually the change is in a sub-menu, so we might have time to add/remove it before the user reaches it. Anyway, removing or adding an entry after the menu is displayed would be much less annoying than having the whole menu freeze for five seconds or more. Another idea would be to monitor the directories in the background when possible (there's a kernel extension for that) and add the entry even before the user clicks the menu. The delay also appears when the user clicks for the first time the menu, _each session_. Someone said fixing this would add a startup delay, but that's wrong. The right way is to cache the last-used menu (before the shutdown), and do just an incremental update at start-up. Second, we could populate the menu in the background, on a low-priority thread. This way the start-up is not greatly affected. (And the system is a bit unresponsive at the start, anyway, so the menu wouldn't be noticed.) Since dual- and multi-core processors are more and more common, parallel start-up should be much more often used. -- Applications menu lags to refresh cache after installing new application https://launchpad.net/bugs/24669 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 13199] Re: Drag n' Drop directories from File-Roller is somewhat tricky
It might be, but as long as Ubuntu doesn't offer an alternative that works as users expect it --- since Ubuntu is desktop-oriented, there are some things people expect --- it's an Ubuntu problem. We don't even tell people the program in question is File-Roller. We call it Archive manager. For anyone that's not very familiar with computer insides, that's Ubuntu's archive manager. I agree that this might need upstream attention, but what's an Ubuntu bug if this isn't one? I mean, if a program distributed by default on all Ubuntu distributions works badly because of upstream, isn't that an Ubuntu problem too? (What if it looks ugly? What if it looks defective? (like this one) What if it deletes hard-drives?) -- Drag n' Drop directories from File-Roller is somewhat tricky https://launchpad.net/bugs/13199 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
Oh, and it never ever happened with anything else, and it always happens with the shutdown options screen, so I'm more inclined to think it the screen rather than xorg. ** Also affects: gnome-desktop (Ubuntu) Importance: Undecided Status: Unconfirmed -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
It's an Intel Mobile 945GM/GMS/940GML Express Integrated Graphics Controller. That's what Device manager says, I have no idea how to figure out which one it is. It's a Dell Latitude laptop that wasn't purchased by me. The Dell site says 950, but that might be a newer edition. I didn't pick the graphics driver either, it's what Ubuntu chose. I don't know where to look for it, but xorg.conf says i810, I guess that should be it. I don't use any composite manager. It would be very weird if it's the video driver. The freeze is exactly when the window should go away; I'd expect it when it shows up. Anyway, the apps keep going on, as far as I can tell, and I can switch to the console and back. When I switch back, the place where the shut-down options window was is not redrawn (it's white as is usual for a frozen window). The cursor looks OK, but doesn't do anything. If it's xorg, where should I look for error logs? I checked /var/log/Xorg.*, I didn't see any problem there. -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I linked this with gnome-desktop too, because it seems to be a GUI problem. At least, someone there should know where to look next. I still don't know who's responsible for the shutdown dialog. -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
Again writing to say that this is not a shutdown issue, it's only the window that freezes. /usr/bin/gnome-power-cmd.sh works correctly. ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I also linked this to gnome-power-manager. I don't think they own the shutdown dialog, but they might now who does. Please let us know if you have any info where to look! -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I'm not totally convinced. Yes, Xorg shouldn't freeze in general, but the shutdown dialog does (and is supposed to) take control over the entire display. If that freezes somehow but doesn't crash, Xorg really has no way of knowing. As far as I can tell, X _doesn't_ freeze, it continues to work in the background, but the display it taken up by the unresponsive shutdown dialog. I don't really know how else could X react to this. As far as xorg knows, the app may be some sort of screen lock. I don't know who's responsible for the shutdown window. While I agree that some of the opened affects won't be related, I'm just trying to find them, and I expect gnome-desktop to know something about that shutdown dialog. It's a desktop feature, isn't it? Even if it's not a bug in the shutdown dialog, I really need to find someone who works on it, because they're the only ones who can find out what's wrong. -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I looked again a bit, and it seems bug 24307 is the same issue. So, would you agree that I open this for gnome-session? -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I'm sorry for spamming the bug list. I don't really expect people to jump to fix the bug, but I'd like at least to know what package is responsible for it (maybe I can reinstall it), places to look for error messages, anything. I tried checking the logs you mentioned. This is what I did: I opened a terminal, typed date (Thu Mar 1 22:06:22 CET 2007), then I clicked shutdown-reboot, the window froze, I switched to a console, typed date again (Thu Mar 1 22:06:46 CET 2007) then I rebooted with sudo shutdown -r now. I couldn't find anything in syslog nor in messages between the two moments. Xorg.0.log has no timestamps, but as far as I can figure it out Synaptics DeviceOff called is the first line after starting the reboot. I'll attach them anyway, in case anyone might notice anything. I also saved the entire contents of the /var/log directory (without any sub- directories), so if there's another file that might be useful, please let me know. ** Attachment added: /var/log/messages http://librarian.launchpad.net/6583421/messages -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
** Attachment added: /var/log/syslog http://librarian.launchpad.net/6583422/syslog -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
** Attachment added: /var/log/Xorg.0.log http://librarian.launchpad.net/6583427/Xorg.0.log -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
These have all been saved the first reboot after a freeze. ** Attachment added: /var/log/Xorg.0.log.old http://librarian.launchpad.net/6583429/Xorg.0.log.old -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
I tried using different video drivers. The experimental i810 and vesa drivers cause the exact same behavior (the dialog freezes), so it's very likely not a driver issue. (I couldn't get fbdev and vga to work at all, though.) Do you think I should link this to a X11 or GDM package? Which one? How about gnome-session? (see bug #24307) -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
It doesn't happen with network-manager uninstalled! How did you know?! window freeze: when I click any button (including cancel!), the button remains pressed, the window remains visible, and the (darkened) desktop too. The mouse cursor still moves, but clicks don't do anything. If I switch to a console and come back to X, sometimes the background (darkened desktop with icons, etc.) is visible, sometimes it's just black (which is by desktop color). The place where the shutdown dialog was is rendered just as a white rectangle. I tried waiting at least a quarter of an hour with no change. Ctrl+alt+backspace goes back to the login window quite quickly, though. When I login again I usually get some warnings about application crashes, but not consistently. -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
But why would it wait for network events even when I'm canceling the shutdown? The fact that it does seems to be a bug in the shutdown dialog, right? Which leads us back to my first problem, where should I report this? -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 89345] [apport] gconf-helper crashed with SIGSEGV
Public bug reported: Probably crashed on shutdown, I got the report after a reboot. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Mar 3 01:18:26 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/pulse/gconf-helper Package: pulseaudio-module-gconf 0.9.5-5ubuntu3 ProcCmdline: /usr/lib/pulse/gconf-helper ProcCwd: / ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libgconf-2.so.4 ?? () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgconf-2.so.4 Uname: Linux bogdanb-d620 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux UserGroups: audio ** Affects: gconf (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gconf-helper crashed with SIGSEGV https://launchpad.net/bugs/89345 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 90409] metacity forgets (on Hostname) annotantion on remote apps sometimes
Public bug reported: Binary package hint: metacity Hi! This report is about the latest Metacity on Feisty. Metacity usually tries to add an (on Hostname) annotation to applications that run on remote hosts but use the local machine's X server. For instance, I run Amarok on another computer using ssh -fnX Hostname.local amarok, and the hostname is normally displayed in the window's titlebar. I'm not sure what causes the problem, but often the annotation disappears. In Amarok's case, it always disappears if I reduce it to a Notification Area icon. When I restore the window, it looks just like a local window. When Amarok changes its title (for example, when the track changes) the annotation returns. It doesn't disappear if I minimize it, just if I iconize it. I'm almost sure I've seen this for other applications, too, but this is the one I can consistently reproduce the bug with. ** Affects: metacity (Ubuntu) Importance: Undecided Status: Unconfirmed -- metacity forgets (on Hostname) annotantion on remote apps sometimes https://launchpad.net/bugs/90409 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80256] Re: Synaptic package manager hard to find in Feisty gnome-control-center
Sebastian, I was just going to enter a long ranty bug report (as in usability issue) about the control-center, and while I was going to be nice about it I think it would just get closed right away. However I do like Ubuntu enough that I wouldn't really like to drop it. I don't like mailing lists for things where I just want to follow an issue, but I may try for this one. What do you think is a proper place to talk about it? It's not this issue in particular that's my problem; I've made myself a menu entry already. It's a bit more general, and it's going to be annoying to the developers no matter how nice I'll be about it... -- Synaptic package manager hard to find in Feisty gnome-control-center https://launchpad.net/bugs/80256 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80755] extracting doesn't work right
Public bug reported: Binary package hint: file-roller I'm not sure what's wrong, this may be an issue with the file selector, but extracting files with file-roller is a pain. For example, I open an archive with just one file, click on extract, and I get presented with a location selector; it's pointed by default on my desktop. If I now click OK (because I want to put the file on the desktop), it doesn't work. If I select another directory, then it works for that directory. But moving back to the desktop makes it not work again. I have to select a different partition first, then go back to the desktop to make it work. This is very annoying. Also, drag and drop doesn't work at all right now. I used to have issues before (I had to drag the file without releasing until the progress bar for the extraction was done), but this seems different. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: Unconfirmed -- extracting doesn't work right https://launchpad.net/bugs/80755 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80755] Re: extracting doesn't work right
** Attachment added: The apport file with my config http://librarian.launchpad.net/5805524/file-roller.eRTg3a.apport -- extracting doesn't work right https://launchpad.net/bugs/80755 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80758] video thumbnails no longer work
Public bug reported: Binary package hint: nautilus I used to have thumbnails for (most) video files shown in nautilus. A while ago it stopped generating new thumbnails. (Video files that already have thumbnails calculated still have their thumbnails shown correctly.) When I look at a new video file, the computing preview icon is shown for a while, then the normal video icon (just a roll of film on my theme) is shown. I couldn't figure out what's wrong -- I assume the thumbnailer crashes, but I have no idea where to look for errors. I don't even know exactly what package generates the thumbnails and how. Are there several options? (As in, does it always use totem, or can I tell it to use mplayer or vlc to generate the thumbnails?) I can look for more info if someone directs me. (A few other issues, perhaps someone can help me: how do I get nautilus to rebuild the thumbnail for a file, other than deleting all thumbnails? And how do I get it to build higher-resolution thumbnails?) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Unconfirmed -- video thumbnails no longer work https://launchpad.net/bugs/80758 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80758] Re: gnome-video-thumbnailer started to crash
The error mentioned GStreamer, so perhaps it's related to that. ** Also affects: gstreamer (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-video-thumbnailer started to crash https://launchpad.net/bugs/80758 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80758] Re: gnome-video-thumbnailer started to crash
Can anyone please tell me where to report this, dpkg -S gnome-video- thumbnailer didn't find anything. -- gnome-video-thumbnailer started to crash https://launchpad.net/bugs/80758 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80758] Re: video thumbnails no longer work
OK, I digged a bit more and I found out how thumbnails get generated. The thumbnailer registered for the files (or at least some that I tried) is /usr/bin/gnome-video-thumbnailer -s %s %u %o, which looks OK. I tried running it by hand with /usr/bin/gnome-video-thumbnailer -s 128 '/media/testfile.avi' output.png (which seems to be the correct way) and I got (process:21395): GStreamer-WARNING **: The GStreamer function gst_init_get_option_group() was called, but the GLib threading system has not been initialised yet, something that must happen before any other GLib function is called. The application needs to be fixed accordingly, please file a bug against this application. GThread-ERROR **: GThread system may only be initialized once. aborting... Aborted (core dumped) If you need the core dump, please tell me where I can find it, I never knew where they are placed. ** Summary changed: - video thumbnails no longer work + gnome-video-thumbnailer started to crash -- gnome-video-thumbnailer started to crash https://launchpad.net/bugs/80758 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80764] Re: can't return to normal window manager
But isn't the Desktop Effects applet supposed to deal with that? And anyway, metacity --replace isn't supposed to do that too? (And any other window manager, in general.) ** Also affects: metacity (Ubuntu) Importance: Undecided Status: Unconfirmed ** Also affects: desktop-effects (Ubuntu) Importance: Undecided Status: Unconfirmed -- can't return to normal window manager https://launchpad.net/bugs/80764 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80755] Re: extracting doesn't work right
Feisty. It's all in the apport file. -- extracting doesn't work right https://launchpad.net/bugs/80755 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80764] Re: can't return to normal window manager
I don't have it on the panel, I have it in the GNOME Control Center. (GCC is a single window with icons replacing all the Preferences/Settings menus. It appeared recently in Feisty.) I don't see any corresponding panel applet on my system, but I think you could just make yourself a custom application launcher that launches desktop-effects. I think I did have an app that I manually installed which added a panel applet. Try looking for a package named compiz-settings or beryl- settings, depending which one you use. -- can't return to normal window manager https://launchpad.net/bugs/80764 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80899] gnome-about-me has no documentation
Public bug reported: Binary package hint: gnome-control-center Currently there is no easily-accessible information about what exactly the gnome-about-me applet does with the information it is supplied with. There is a Help button that is unimplemented (it prints Help goes here on the console). I searched for 15 minutes on Google and I still couldn't find anything about it, except some bug reports that mention it. Especially in this age of social engineering, spam spyware -- though Linux is not yet much affected by the latter -- and all sorts of privacy abuse I think we should be very careful to train our users to be security conscious. Right now the applet is just an invitation for users to give away a lot of private information, without any explanation as to what that information is used to and what applications have access to it. As I assume the applet isn't doing anything much for now, there should be at least a help window telling people that. If there is any support for an application to retrieve the information there (e.g. DBUS) I think it is a priority that work should be done on basic privacy measures. (e.g., the user should be able to choose what info is public (thus easily accessible for every program, for instance Gaim) and what info is not (thus programs may request it, and the user is asked to confirm). The private part, at least, should be encrypted in some way.) I really look up to just entering my photo once and having it available on any chat/phone/etc application that I may install, without having to remember where I put it. Come to think of it, one could make an entire program only for the photo thing. (Multiple photos, per-program attribution, friends have free access to all of them (or at least some) so they can tag me which whatever they choose, perhaps seasonal changes, automatic capture/change of the portrait when a video camera is available (in concert with the preferred snapshot application), temporary picture analogue to the status-text in IM programs, blah, blah...) And some network-of-trust thing would be very useful (and a nice excuse for more GPG), for things like allow these persons to see where I am using the laptop's GPS OK, I'll stop day-dreaming now. This bug report is just about knowing that I can enter my info there and trust it won't be beamed to every site I access, etc. ** Affects: control-center (Ubuntu) Importance: Undecided Status: Unconfirmed -- gnome-about-me has no documentation https://launchpad.net/bugs/80899 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 80899] Re: gnome-about-me has no documentation
I'll look into the specs thing (thanks, I didn't know it existed). Of course, it's quite certainly a duplicate of bug #3574. I would have preferred it insisted more on the privacy issues -- and on the very basic fact that, as of now, I don't really know what's the actual purpose of that applet, I can only speculate -- but still, if that help button is actually implemented I can add a more specific bug. (Or reopen this one.) Also, because of the same privacy issues I'm not happy with that bug being marked as low priority. I'm not sure how this works, am I supposed to close the bug myself? Can I even do it? -- gnome-about-me has no documentation https://launchpad.net/bugs/80899 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39127] Re: Does not cooperate with unrar-free
I've just tried opening a random rar I've got from the net. It works with unrar and rar-nonfree, but not with only rar-free. However, it may have been just an unsupported version of file. -- Does not cooperate with unrar-free https://bugs.launchpad.net/bugs/39127 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119135] wrong quote; entity
Public bug reported: Binary package hint: gdm File /usr/share/gnome/help/gdm/es/gdm.xml contains a wrong quote; entity instead of the correct quot; one. I noticed this during the update from Feisty to Gutsy. ** Affects: gdm (Ubuntu) Importance: Undecided Status: Unconfirmed -- wrong quote; entity https://bugs.launchpad.net/bugs/119135 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 119196] gconftool-2 reports memory corruption
Public bug reported: Binary package hint: gconf2 Hello. I've just updated from Feisty to Gutsy (using the update manager) and during the update I've seen many warnings like the one below. ***MEMORY-WARNING***: gconftool-2[28570]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon... I don't know which package exactly contains gconftool, but I suppose the gconf guys would know. I've seen the same error during a dpkg-reconfigure _after_ the update, so it's very likely still a problem in Gutsy. ** Affects: gconf2 (Ubuntu) Importance: Undecided Status: Unconfirmed -- gconftool-2 reports memory corruption https://bugs.launchpad.net/bugs/119196 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gconf2 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120844] Re: vlc crashes at start
*** This bug is a duplicate of bug 120278 *** https://bugs.launchpad.net/bugs/120278 Yes, when I run it like that it doesn't crash anymore. -- vlc crashes at start https://bugs.launchpad.net/bugs/120844 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee (via bug 120278). -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 121796] multiple non-working Open WithGimp entries
Public bug reported: Binary package hint: gimp Hello! I'm using Gutsy (after updating from Dapper through all versions). The right-click Open With menu for image files (at least for JPEGs) has four consecutive [Open with GIMP Image Editor] options, neither of which works. (I remember sometimes one of them works, but today neither does.) I can start the GIMP normally from the Applications menu. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- multiple non-working Open WithGimp entries https://bugs.launchpad.net/bugs/121796 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 122044] Nautilus crashes when viewing certain files' properties
Public bug reported: Binary package hint: nautilus Hello! I've noticed Nautilus crashes (and restarts correctly) when I open the Property page of certain files (right-click properties). This happens on Ubuntu Gutsy, freshly updated. I've seen this with Flash, mpg and avi files, at least: nautilus: symbol lookup error: /usr/lib/nautilus/extensions-1.0/libtotem-properties-page.so: undefined symbol: totem_interface_load_with_root [crash and restart just after] ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes when viewing certain files' properties https://bugs.launchpad.net/bugs/122044 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 121796] Re: multiple non-working Open WithGimp entries
I have just completed a dist-upgrade (and, indeed, xsane was updated), but GIMP still won't start from the right-click menu. I remind you that I GIMP starts normally from the Applications menu, and I can open the images with drag-and-drop just fine. On the other hand, even if the GIMP would start, there's still the problem with the multiple (four, right now) entries in the right-click menu. I suspect the install scripts of the package have some kind of bug. (I didn't notice this with anything but GIMP, but it could also be a bug in whatever package manages the right-click menu. BTW, I'm using Gnome for everything.) I've looked at the debug suggestions, but I can't find anything that applies to my case. The problem is that GIMP doesn't start only when I use the right-click menu of a file, so I can't attach any debuggers and such. GIMP starts normally when I start it myself, with only these warnings: Executable not found: '/usr/lib/gimp/2.0/plug-ins/psd_save' Executable not found: '/usr/lib/gimp/2.0/plug-ins/gifload' Executable not found: '/usr/lib/gimp/2.0/plug-ins/tiff' Executable not found: '/usr/lib/gimp/2.0/plug-ins/psd' Executable not found: '/usr/lib/gimp/2.0/plug-ins/gif' But it behaves the same for all kinds of files, including---which bugs me---JPEGs. I have started Nautilus from a command line so I can see its messages (I assume it's responsible for the right-click menu), and it doesn't display anything when I use the right-click menu. Nothing happens, apparently. I've checked the logs, too, I didn't see anything remotely relevant. Any idea where Nautilus keeps it's right-click menu settings, so I can check what's going on? -- multiple non-working Open WithGimp entries https://bugs.launchpad.net/bugs/121796 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 121796] Re: multiple non-working Open WithGimp entries
Hello Justin, Yes, I've kept up with the updates and it's still happening. Note that I don't think this is a problem with the GIMP itself, it works correctly when I start it from the command line or the application menu. It's very likely a problem with the way it registers itself to Nautilus' open-with list. (The fact that I have four different entries is a good hint...) Regards, Bogdan -- multiple non-working Open WithGimp entries https://bugs.launchpad.net/bugs/121796 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 121796] Re: multiple non-working Open WithGimp entries
Hello again! I've been scouring the web and the various /usr/share/mime* directories on my computer, and I can't figure out where is Nautilus keeping the file that tells it JPEGs can be opened with application X. Anyone can point me to it, so I can take a look and see what's wrong? -- multiple non-working Open WithGimp entries https://bugs.launchpad.net/bugs/121796 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gimp in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 88015] Re: shutdown window freezes everytime
Right now it doesn't happen anymore, so perhaps something other change fixed it. There was a discussion about a race or something in the fade- in/out code somewhere, I'm not sure if it just happens that the race doesn't occur for me anymore or if it's fixed for good. -- shutdown window freezes everytime https://launchpad.net/bugs/88015 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 93661] Re: [apport] gconf-helper crashed with SIGSEGV
** Attachment added: CoreDump.gz http://librarian.launchpad.net/6854675/CoreDump.gz ** Attachment added: Dependencies.txt http://librarian.launchpad.net/6854676/Dependencies.txt ** Attachment added: Disassembly.txt http://librarian.launchpad.net/6854677/Disassembly.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6854678/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6854679/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/6854680/Registers.txt ** Attachment added: Stacktrace.txt http://librarian.launchpad.net/6854681/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://librarian.launchpad.net/6854682/ThreadStacktrace.txt -- [apport] gconf-helper crashed with SIGSEGV https://launchpad.net/bugs/93661 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 93661] [apport] gconf-helper crashed with SIGSEGV
Public bug reported: Binary package hint: gconf I rebooted the computer with the lid down by mistake, and for some reason (bug in the video drivers, probably) the screen never comes back when I do that, so I had to do a forced shut-down. So it's probably not gconf's fault, but still, I always get crash reports after computer crashes, and always only from gconf... ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Mon Mar 19 12:03:00 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/pulse/gconf-helper Package: pulseaudio-module-gconf 0.9.5-5ubuntu4 PackageArchitecture: i386 ProcCmdline: /usr/lib/pulse/gconf-helper ProcCwd: / ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libgconf-2.so.4 ?? () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgobject-2.0.so.0 ?? () from /usr/lib/libgconf-2.so.4 Uname: Linux cimer 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux UserGroups: audio ** Affects: gconf (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gconf-helper crashed with SIGSEGV https://launchpad.net/bugs/93661 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95946] Re: nautilus freezes when displaying a root system over sshfs
I can't reproduce it now, even without the debugging. It's weird, I got several weird behaviors out of it yesterday, but nothing today. You should probably close the bug now, I'll re-open it if it starts acting up again and I can get a trace. By the way, what is the difference between the *-dbgsym packages described in the link you gave me and the *-dbg packages that are in the official repositories? -- nautilus freezes when displaying a root system over sshfs https://launchpad.net/bugs/95946 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95946] Re: nautilus freezes when displaying a root system over sshfs
I'm not sure if it's the same bug, but it happened again. This time, it wasn't a root file-system, but it was mounted with sshfs. Nautilus stays at 100% processor usage. I took an strace while it was doing that (I didn't kill it). Then I also took an strace of the sshfs process that mounted that filesystem, and the ssh process that provided the transport. (The last two seemed to freeze, though.) Note the the straces are not really simultaneous. But since nautilus seems to be in a loop, this might be interesting. I'm not sure what to do with gdb, since nautilus doesn't crash all by itself. Is it interesting to get a backtrace when I kill it? Any change from a normal backtrace? ** Attachment added: strace-nautilus.log http://librarian.launchpad.net/7113438/strace-nautilus.log -- nautilus freezes when displaying a root system over sshfs https://bugs.launchpad.net/bugs/95946 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95946] Re: nautilus freezes when displaying a root system over sshfs
The command line was sshfs [EMAIL PROTECTED]:/media/LACIE /media/LACIE -o rw,noexec,nosuid,nodev ** Attachment added: strace-sshfs.log http://librarian.launchpad.net/7113477/strace-sshfs.log -- nautilus freezes when displaying a root system over sshfs https://bugs.launchpad.net/bugs/95946 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95946] Re: nautilus freezes when displaying a root system over sshfs
Command line was ssh -x -a -oClearAllForwardings=yes -2 [EMAIL PROTECTED] -s sftp. Unfortunately this one seems to have froze right after I started the trace, I'm not sure if it does this all the time. ** Attachment added: strace-ssh.log http://librarian.launchpad.net/7113840/strace-ssh.log -- nautilus freezes when displaying a root system over sshfs https://bugs.launchpad.net/bugs/95946 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95946] Re: nautilus freezes when displaying a root system over sshfs
Update: this time, Nautilus entered the same loop when I started it. It did this several times, so I stopped it (nautilus -q worked) and I started it under strace. Maybe it's useful. It froze when I ctrl-C it. Nautilus starts, never displays any window, and enters what seems to be a loop, printing all the messages here. When I pressed Ctrl-C, it froze completely. ** Attachment added: strace-nautilus-restart.log http://librarian.launchpad.net/7113883/strace-nautilus-restart.log ** Changed in: nautilus (Ubuntu) Status: Rejected = Unconfirmed ** Changed in: sshfs-fuse (Ubuntu) Status: Rejected = Unconfirmed -- nautilus freezes when displaying a root system over sshfs https://bugs.launchpad.net/bugs/95946 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102890] [apport] gnome-panel crashed with SIGSEGV
Public bug reported: Binary package hint: gnome-panel I have gnome panel crashes almost every time when it's updated. Presumably the installer restarts it and something goes wrong. One thing that might be relevant or not: also each time the panel is updated, about the same time it crashes, the gnome-power-manager icon (which I have set to be always visible, this is on a laptop) detaches from the panel and appears in it's own tiny window (a box only large enough for the battery icon to fit, with a title-bar that contains only a default window icon). This window appears on the task bar; it can be minimized, but it doesn't respond to close-window commands. I can kill it, and restarting the power manager puts the icon in the right place on the new panel. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Wed Apr 4 15:32:52 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 2.18.0-0ubuntu3 PackageArchitecture: i386 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/bogdanb ProcEnviron: LANGUAGE=en_US:en PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: gnome-panel Stacktrace: #0 0xb74ae9a4 in ?? () from /lib/tls/i686/cmov/libc.so.6 #1 0x0016 in ?? () #2 0x0016 in ?? () #3 0x0001 in ?? () #4 0x in ?? () StacktraceTop: ?? () from /lib/tls/i686/cmov/libc.so.6 ?? () ?? () ?? () ?? () Uname: Linux cimer 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-access pulse-rt scanner video ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: Unconfirmed ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/102890 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102890] Re: [apport] gnome-panel crashed with SIGSEGV
** Attachment added: CoreDump.gz http://librarian.launchpad.net/7142512/CoreDump.gz ** Attachment added: Dependencies.txt http://librarian.launchpad.net/7142513/Dependencies.txt ** Attachment added: Disassembly.txt http://librarian.launchpad.net/7142514/Disassembly.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/7142515/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/7142516/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/7142517/Registers.txt ** Attachment added: ThreadStacktrace.txt http://librarian.launchpad.net/7142518/ThreadStacktrace.txt ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/102890 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102890] Re: [apport] gnome-panel crashed with SIGSEGV
I marked this as affecting power-manager, since it seems it might be a (minor) bug with it. The behavior described above happens always (or almost, as far as I can remember) on updates, but only with the gnome- power-manager icon. It did happen a couple of times with other icons, but much less often. (Admittedly, this could be because (and I speculate) the power-manager is the first (or last) icon started, or some other similar corner case. Doesn't hurt to check.) -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/102890 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102890] Re: [apport] gnome-panel crashed with SIGSEGV
If I understand correctly, to run valgrind one must be able to reproduce a crash while valgrind is running. Am I right? In that case, I'm not sure how to do it, it happens during updates. I'll try to downgrade it, see what happens. By the way, the gnome-power-manager icon leaves the panel even on a normal kill. The panel restarts automatically, but the power-manager icon remains detached. -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/102890 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 102890] Re: [apport] gnome-panel crashed with SIGSEGV
Turns out I don't know how to downgrade something So, I don't really know how to use Valgrind in this situation. -- [apport] gnome-panel crashed with SIGSEGV https://bugs.launchpad.net/bugs/102890 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 95946] nautilus freezes when displaying a root system over sshfs
Public bug reported: Binary package hint: nautilus Not sure if it's a Nautilus or a sshfs bug, I'll report it as both. I'm using up-to-date Feisty on two laptops connected to the same LAN, through a WiFi router (one is on Ethernet, the other on WiFi). I'm using fuse sshfs to mount the fs of one computer on the other. This is because the fixed computer has a big drive, and the WiFi one is more comfortable as a desktop. Until recently I only had mounted a part of the remote file system, i.e. the big drive where most files are. This worked without a hitch. Today I tried mounting the entire root file system, so that I can access the remote home directory too. This sort of works, but when I open the remote root directory in Nautilus, the root icons are displayed, but after a while Nautilus freezes. (This includes all windows and the desktop.) I tried running it from the console, but it doesn't show anything when it freezes. If I force-close the window, Nautilus restarts normally, and it works until I try to view the remote root directory again. This never happened before with the files-only directory mounted. I suspect something funny happens when it's trying to look inside the /proc or /dev directory, but I can't really tell for sure. I can't find anything relevant in the logs. Any ideas? ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Unconfirmed ** Affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: Unconfirmed ** Also affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: Unconfirmed -- nautilus freezes when displaying a root system over sshfs https://launchpad.net/bugs/95946 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 268956] Re: [intrepid] unknown media type during update
Unless I'm doing something wrong, it's not there: $ grep -r all/all /usr/share/applications ~/.local $ grep -r uri/mms /usr/share/applications ~/.local $ grep -r uri/rtsp /usr/share/applications ~/.local $ grep -r fonts/package /usr/share/applications ~/.local $ grep -r interface/x-winamp-skin /usr/share/applications ~/.local $ grep -r uri/pnm /usr/share/applications ~/.local However, $ sudo update-mime-database /usr/share/mime Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' Unknown media type in type 'uri/mms' Unknown media type in type 'uri/mmst' Unknown media type in type 'uri/mmsu' Unknown media type in type 'uri/pnm' Unknown media type in type 'uri/rtspt' Unknown media type in type 'uri/rtspu' Unknown media type in type 'fonts/package' Unknown media type in type 'interface/x-winamp-skin' $ grep -r interface/x-winamp-skin /usr/share/mime /usr/share/mime/globs:interface/x-winamp-skin:*.wsz /usr/share/mime/types:interface/x-winamp-skin /usr/share/mime/packages/kde.xml: mime-type type=interface/x-winamp-skin /usr/share/mime/subclasses:interface/x-winamp-skin application/zip /usr/share/mime/globs2:50:interface/x-winamp-skin:*.wsz /usr/share/mime/interface/x-winamp-skin.xml:mime-type xmlns=http://www.freedesktop.org/standards/shared-mime-info; type=interface/x-winamp-skin $ grep -r uri/mms /usr/share/mime /usr/share/mime/uri/mmst.xml:mime-type xmlns=http://www.freedesktop.org/standards/shared-mime-info; type=uri/mmst /usr/share/mime/uri/mmsu.xml:mime-type xmlns=http://www.freedesktop.org/standards/shared-mime-info; type=uri/mmsu /usr/share/mime/uri/mms.xml:mime-type xmlns=http://www.freedesktop.org/standards/shared-mime-info; type=uri/mms /usr/share/mime/types:uri/mms /usr/share/mime/types:uri/mmst /usr/share/mime/types:uri/mmsu /usr/share/mime/packages/kde.xml: mime-type type=uri/mms /usr/share/mime/packages/kde.xml: mime-type type=uri/mmst /usr/share/mime/packages/kde.xml: mime-type type=uri/mmsu $ grep -r all/all /usr/share/mime /usr/share/mime/all/all.xml:mime-type xmlns=http://www.freedesktop.org/standards/shared-mime-info; type=all/all /usr/share/mime/all/allfiles.xml:mime-type xmlns=http://www.freedesktop.org/standards/shared-mime-info; type=all/allfiles /usr/share/mime/types:all/all /usr/share/mime/types:all/allfiles /usr/share/mime/packages/kde.xml: mime-type type=all/all /usr/share/mime/packages/kde.xml: mime-type type=all/allfiles $ dpkg-query -S /usr/share/mime/packages/kde.xml kdelibs5-data: /usr/share/mime/packages/kde.xml $ aptitude show kdelibs5-data Package: kdelibs5-data State: installed Automatically installed: no Version: 4:4.1.1+really4.1.1-0ubuntu3 [snip] -- [intrepid] unknown media type during update https://bugs.launchpad.net/bugs/268956 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 268956] Re: [intrepid] unknown media type during update
By the way, $ aptitude why kdelibs5-data i kdelibs5 Depends kdelibs5-data (= 4:4.1.1+really4.1.1-0ubuntu3) $ aptitude why kdelibs5 i amarok2 Depends kdelibs5 (= 4:4.0.0-0ubuntu2~gutsy1~ppa1) I have deb http://ppa.launchpad.net/kubuntu-members-kde4/ubuntu intrepid main in my apt/sources.list, but I have no idea how to determine if my package comes from there or from the normal repositories. -- [intrepid] unknown media type during update https://bugs.launchpad.net/bugs/268956 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 268956] Re: [intrepid] unknown media type during update
After purging amarok2 and all kdelibs5 stuff, update-mime-database stopped giving the error. If Ivan confirms that his system is in a similar situation, I think we can mark this 'invalid'. Sorry for the spamming :) -- [intrepid] unknown media type during update https://bugs.launchpad.net/bugs/268956 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 274584] [NEW] [intrepid] libgnomeprint2.2-0 depends on dummy package libcupsys2
Public bug reported: Binary package hint: libgnomeprint2.2-0 As can be seen below, libgnomeprint2.2-0 depends on libcupsys2, which is a dummy package. I know that's what dummy packages are for, but I'm filing this bug in case someone forgot to change the dependencies. This is on an up-to-date Intrepid. $ aptitude why libcupsys2 i serpentineDepends python-gnome2-desktop (= 2.14.0-3) i A python-gnome2-desktop Depends libgnomeprint2.2-0 (= 2.17.0) i A libgnomeprint2.2-0Depends libcupsys2 (= 1.3.4) $ aptitude show libcupsys2 libgnomeprint2.2-0 Package: libcupsys2 State: installed Automatically installed: yes Version: 1.3.8-11ubuntu1 Priority: extra Section: oldlibs Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] Uncompressed Size: 90.1k Depends: libcups2 Provided by: libcups2 Description: Common UNIX Printing System (transitional package) This is a dummy package to ease transition to new package name. ** Affects: libgnomeprint (Ubuntu) Importance: Undecided Status: New -- [intrepid] libgnomeprint2.2-0 depends on dummy package libcupsys2 https://bugs.launchpad.net/bugs/274584 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnomeprint in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278815] [NEW] [intrepid] libgnome-desktop dependency missing somewhere
Public bug reported: Binary package hint: gnome-control-center Hello! I noticed this weird situation today (on an up-to-date Intrepid): $ gnome-at-properties gnome-at-properties: error while loading shared libraries: libgnome-desktop-2.so.2: cannot open shared object file: No such file or directory $ aptitude why libgnome-desktop-2 Unable to find a reason to install libgnome-desktop-2. $ aptitude search libgnome-desktop p libgnome-desktop-2- Utility library for loading .desktop files - runtime files i A libgnome-desktop-2-7 - Utility library for loading .desktop files - runtime files p libgnome-desktop-dev - Utility library for loading .desktop files - development files After installing by hand libgnome-desktop-2 things started working again. I think a dependency got forgotten somewhere by mistake. I've put this under gnome-control-center, but it may be that the dependency got lost somewhere above it. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- [intrepid] libgnome-desktop dependency missing somewhere https://bugs.launchpad.net/bugs/278815 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 278815] Re: libgnome-desktop dependency missing somewhere
Thanks Sebastian, that was exactly the problem. No idea where those usr/local binaries came from :) Sorry for the spam everyone. ** Changed in: gnome-control-center (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) Status: Incomplete = Invalid -- libgnome-desktop dependency missing somewhere https://bugs.launchpad.net/bugs/278815 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 274584] Re: [intrepid] libgnomeprint2.2-0 depends on dummy package libcupsys2
** Also affects: libgnomecups (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [intrepid] libgnomeprint2.2-0 depends on dummy package libcupsys2 + [intrepid] some packages still depend on dummy package libcupsys2 ** Description changed: - Binary package hint: libgnomeprint2.2-0 + [edit: This bug originally referred to libgnomeprint2.2-0, but has been + updated.] - As can be seen below, libgnomeprint2.2-0 depends on libcupsys2, which is - a dummy package. I know that's what dummy packages are for, but I'm - filing this bug in case someone forgot to change the dependencies. + There are still a few packages that depend on libcupsys2, which is a + dummy package. I know that's what dummy packages are for, but I'm filing + this bug as a reminder to update the dependencies. - This is on an up-to-date Intrepid. + This is on an up-to-date Intrepid. I've attached to bug to libgnomecups + because that's what I have installed at the moment; should I link it to + all packages below? + $ aptitude search '?depends(libcupsys2)' + p eggcups - notification area icon for printing jobs + p flphoto - Image manager with great printing function + p kdelibs5-dev- development files for the KDE 4 core libra + p libfox-1.6-0- The FOX C++ GUI Toolkit + p libfox-1.6-dev - Development files for the FOX C++ GUI Tool + p libfox1.4 - The FOX C++ GUI Toolkit + p libfox1.4-dev - Development files for the FOX C++ GUI Tool + i A libgnomecups1.0-1 - GNOME library for CUPS interaction + p libgnomecups1.0-dev - GNOME library for CUPS interaction (header + p libnet-cups-perl- Provides an interface for printing with CU + p libqt3-mt-dev - Qt development files (Threaded) + p lsb-printing- Linux Standard Base 3.2 Printing package + p rezound - Audio file editor + p scribus-ng - Open Source Desktop Page Layout - developm + p xpp - X Printing Panel - $ aptitude why libcupsys2 - i serpentineDepends python-gnome2-desktop (= 2.14.0-3) - i A python-gnome2-desktop Depends libgnomeprint2.2-0 (= 2.17.0) - i A libgnomeprint2.2-0Depends libcupsys2 (= 1.3.4) - - $ aptitude show libcupsys2 libgnomeprint2.2-0 + $ aptitude show libcupsys2 Package: libcupsys2 State: installed Automatically installed: yes Version: 1.3.8-11ubuntu1 Priority: extra Section: oldlibs Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] Uncompressed Size: 90.1k Depends: libcups2 Provided by: libcups2 Description: Common UNIX Printing System (transitional package) This is a dummy package to ease transition to new package name. -- [intrepid] some packages still depend on dummy package libcupsys2 https://bugs.launchpad.net/bugs/274584 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnomecups in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 274584] Re: [intrepid] some packages still depend on dummy package libcupsys2
According to Sebastian's suggestion, marking invalid on libgnomecups. Re-submitted under Ubuntu as Bug #279345. ** Changed in: libgnomecups (Ubuntu) Status: New = Invalid -- [intrepid] some packages still depend on dummy package libcupsys2 https://bugs.launchpad.net/bugs/274584 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnomecups in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279345] Re: [intrepid] some packages still depend on dummy package libcupsys2
Sebastian, I'm not sure who opened the task for each package; I just opened it for Ubuntu and asked about linking. Next time I'll open separate bugs from the start. -- [intrepid] some packages still depend on dummy package libcupsys2 https://bugs.launchpad.net/bugs/279345 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnomecups in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 279345] Re: [intrepid] some packages still depend on dummy package libcupsys2
Sebastian, since we're on the subject, there are a couple hundred non- transitional packages which depend on transitional ones: $ aptitude search '?depends(~dtransitional)?not(~dtransitional)'|wc -l 243 It seems a huge job for someone to go through all of those, verify them (the query it's probably not very precise) and create separate bugs for each. I think it would be more appropriate to create a generic bug like this one, which lists the problem and the query. Bug-fixers would just take the query and fix whatever they can, and perhaps add separate bugs for each issue they fix. Then, when the number of packages involved gets to a few dozen we can create the rest of the bugs. What do you think? -- [intrepid] some packages still depend on dummy package libcupsys2 https://bugs.launchpad.net/bugs/279345 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libgnomecups in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
