[Bug 1164016] Re: restore type-ahead find
I don't know how long it will take, but in the meantime Ubuntu could ship the patch maintained by the Arch community: https://aur.archlinux.org/cgit/aur.git/tree/nautilus-restore- typeahead.patch?h=nautilus-typeahead It looks like this patch is kept up to date pretty well. There is a similar patch for gtk3 to make the file chooser dialog have type-ahead. It's the best of both worlds, since you can still tap ctrl-f to search. Whilst it would be nice for the Nautilus devs to upstream the patch or for there to be a dialog about what kind of patch they might accept (if any), in the meantime distros can include the patch, there is little downside since the patch is maintained and not bit rotting. Canonical would not be committing themselves to maintaining it by including it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164016] Re: restore type-ahead find
I don't think it's true that an option is always good. I think software should endeavour to have decent default options, and if multiple use cases can be accommodated without an option, then that is preferable. But you're right, a recursive search with ctrl-f vs typeahaed with simple typing would accomplish what everyone wants without an option. I'm using the 'search in current folder only' setting in order to make the search more like typeahead, but this has the downside that I have to go into the settings to do an actual recursive search. In reality, recursive search is useful, and I want to use it, but it's different to typeahead and it's a shame I have to pick one or the other. Ideally for me would be typing is just going to select things similarly to the old typeahead behaviour, and ctrl-f would do a search, either in the current folder or recursively depending on a checkbox that would ideally be in the main interface next to the search box rather than in the settings menu - since one often wants one or the other, it's not really an all-time preference. I do think things will eventually go back this way. There is currently wasted effort trying to make search meet the requirements of type-ahead, whereas this would be unnecessary if typeahead existed too. Search is becoming a bit of a frankenstein trying to be both, with returning items from the current folder first, and having the search-in-current-folder- only setting being global. It should just be search - features should do one thing each instead of trying to please everyone. I understand that search has been improved a lot in response to complaints about type-ahead being removed, and this shows that the devs are trying to meet people's use cases. But ultimately I think it is misguided and making the search implementation more complex than it otherwise would need to be. They are really are different features. So I know there has been a lot of vitriol over this issue, but I would encourage the nautilus devs to consider that they should become different features once again. Ctrl-f to search will not confuse anybody, type-ahead will not confuse anybody, whereas the current search is trying to be both and so can behave unexpectedly in terms of the order of search results and whether the search is recursive. Presumably this means code complexity too. I also understand that the old type-ahead code was holding back the codebase and so it was desirable to excise it. I imagine new typeahead functionality, working as much as possible within the current codebase and its future directions, would be more amenable to nautilus dev approval than just restoring the old code. For example, we probably don't need the popup box in the bottom right as you type. It should just be type a few characters and have a few-second timeout before forgetting them, just like it is on other platforms such as windows and macos (I think). It seems similar to me to the case or removing nautilus handling the desktop. The code was holding back the codebase, but now we see that a desktop extension for gnome-shell is in development by the main nautilus dev. I do think Nautilus can satisfy everyone's preferences here, and I do think typeahead will eventually be re implemented once tensions die down, especially if the nautilus devs can do it on their terms instead of rejecting a patch that just re-adds code that they don't want to maintain. A good typeahead implementation would even allow Nautilus to remove code that customises how the search works to make it more useful as typeahead - there would no longer be a need for that if typeahead were present in its own right. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326582] Re: sort order of files listings in nautilus is not alphabetical
On major problem with this search order is that it conflicts with the order of files in Nautilius in the non-search view. In my home folder I have 'thesis' and 'tmp' subfolders, and they are shown in that order. I type 't' expecting 'thesis' to be the first result so that I can hit enter and navigate to the 'thesis' folder. However 'tmp' comes up first because Nautilus's search view is sorting by length before aphabetically, or something (not sure what the exact algorithm is). This is one of the behaviours preventing the new search interface from being used for keyboard navigation as a replacement for the removed typeahead functionality. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/326582 Title: sort order of files listings in nautilus is not alphabetical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/326582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767027] Re: Search current folder only in nautilus doesn't work (Ubuntu 18.04)
I tested with nautilus 1:3.26.4-0~ubuntu18.04.1 and the issue is fixed for me. Thank you! :) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib
Has this been fixed upstream? Looking at the changelog, there has been a related change, but I'm not sure if it resolves the issue yet, it now says they're both executables. https://github.com/file/file/blob/219846094c7593e27453e62855e61181089c48cf/ChangeLog file 5.3.3: python3.6: ELF 64-bit LSB pie executable x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.4.0, with debug_info, not stripped libpython3.6m.so.1.0: ELF 64-bit LSB pie executable x86-64, version 1 (SYSV), dynamically linked, with debug_info, not stripped file 5.3.2: python3.6: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.4.0, with debug_info, not stripped libpython3.6m.so.1.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, with debug_info, not stripped -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747711 Title: file mis-identifies modern executables as application/x-sharedlib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1747711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655835] Re: avahi-daemon consumes 100% CPU time after a period of networked Desktop use
Still present in 18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/655835 Title: avahi-daemon consumes 100% CPU time after a period of networked Desktop use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/655835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Lubomir, what changes were required on top of the arch patch to work with 3.26.3? I'm using the Arch patch as-is on Ubuntu 18.04 and there don't appear to be any problems that I've noticed so far. But assuming your changes are necessary, could you publish them somewhere? It would be great to maybe have a public git repo that people could contribute to to maintain patches for the latest few versions of Nautilus that are in common use. Ubuntu devs - now that there is a working patch again (and seemingly the will to maintain it by the arch community and others), might Ubuntu be able to ship a patched nautilus once more restoring this behaviour? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
That example was my home directory, and all the files were either in my home directory or a subfolder. Attached is another example from within the root directory a python project 'zprocess', searching for 'py'. Here is the result of the find command (excluding hidden files and folders): zprocess $ find . -not -path '*/\.*' -name '*py*' | sort ./doc/conf.py ./run_tests.py ./setup.py ./tests/output_redirection.py ./tests/tests.py ./zprocess/clientserver.py ./zprocess/examples/example_client.py ./zprocess/examples/example_server.py ./zprocess/examples/processclass_example.py ./zprocess/__init__.py ./zprocess/locking/__init__.py ./zprocess/locking/__main__.py ./zprocess/process_class_wrapper.py ./zprocess/process_tree.py ./zprocess/remote/__main__.py ./zprocess/security.py ./zprocess/utils.py ./zprocess/zlog/__init__.py ./zprocess/zlog/__main__.py As far as I can tell, it is performing search as if 'search in subfolders' option was set to 'On this computer only', even though the preferences interface shows it set to 'never'. If I search a remote location it appears to correctly limit search to the current directory. ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138287/+files/nautilus_bug_2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
Attached is a screenshot of the preferences dialog with my current settings. ** Attachment added: "Settings dialog" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138288/+files/nautilus_settings.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
I'm using 1:3.26.3-0ubuntu4 Attached is a screenshot demonstrating the problem ** Attachment added: "screenshot of nautilus bug" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138067/+files/nautilus_search_bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484043] Re: double click full screen plugin - undesired behaviour
No longer valid due to overlay scrollbars ** Changed in: eog (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/484043 Title: double click full screen plugin - undesired behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/484043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767030] [NEW] Nautilus does not focus search bar upon typing if search bar already is visible
Public bug reported: (Nautilus 3.26.3 on Ubuntu 18.04, but bug has been present as long as the new search box has existed to my knowledge) If you start typing in nautilus, so long as no text field anywhere is focused, the search box will appear and get focus, so you end up typing into it. However, if the search box is already visible but does not have focus (for example, by tapping ctrl-f and then clicking outside the search box), then typing does not re-focus the search box. This is jarring since you can be looking at a normal view of a folder (not at search results), and out of habit expect that you can start typing to search. Even if you tap ctrl-f, this makes an empty search box *vanish*, so you have to tap ctrl-f *twice* to get it focused (or click on it of course) Solutions include: * Make an empty search box always vanish upon losing focus * Make an empty search box, if still visible, gain focus again if the user starts typing. The first solution is probably cleanest since there is no use case I can think of for leaving an empty search box visible if the user is not about to type into it. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767030 Title: Nautilus does not focus search bar upon typing if search bar already is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767027] [NEW] Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
Public bug reported: I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding that Nautilus searches all subfolders when I start typing, not just the present folder, even though I have the "search only current folder" option selected in its preferences, and "Only searching the current folder" does appear in the GUI as I am searching. Nonetheless results appear from subfolders (which I wouldn't mind, but which I turn off due to its poor performance compared to current-folder-only). ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
Agreed. Distinguishing between monitors serves no purpose. Like everyone else I have strong muscle memory to look to the top right of my screen when I want to see status indicators, or to look to the top to see the time, or to move my mouse to the top right to change the volume. This muscle memory has no concept of whether I am looking at my 'primary' monitor or not, and feels a half second of confusion each time I try to do one of these things on a second monitor, which is the hallmark of bad interface design. I think I'm subconsciously adapting to just not use the second monitor much, and that's a stupid outcome too. Of course indicators have nothing to do with the specific monitor they're on, but they have nothing to do with the primary monitor either, so why are they there? They're there to give quick visual and interactive access to certain frequently accessed information and functionality, quick enough that you apparently don't want to have to hit a few keypresses to get them. By the same logic you shouldn't have to drag your mouse over increasingly large screen real estate. Unity had it right in this regard. There should be just monitors, no primary or secondary. It's a pointless distinction, and whilst I accept it might be technically difficult to achieve given the current architecture of gnome-shell, to insist on it as a design decision is silly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721537] Re: No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist-upgrade
This problem seems to be the same as in the following two Ubuntu stackexchange posts: https://askubuntu.com/questions/768463/laptop-headphone-jack-produces-no-sound https://askubuntu.com/questions/219342/no-sound-output-from-headphone-jack-ubuntu12-04/859931 A temporary solution mentioned in those threads is: alsactl restore which fixes the problem for me. Might be a problem with Dell hardware specifically - a few comments mention Dell models. In any case it doesn't seem like a new problem since the two stackexchange posts are from 2016 and 2012. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721537 Title: No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist- upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1721537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721537] Re: No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist-upgrade
I am also having this problem on a Dell Precision 5520 (which is similar hardware to both the Dell XPS 15 and Dell XPS 13). Headphone output worked initially since install and then stopped working mid-session after unplugging and re-plugging the headphones. I was adjusting the "Alert volume" setting in sound settings at the time, which may or may not be relevant. Reebooting, unplugging and replugging, etc, nothing seems to bring it back. I am on Ubuntu 17.10 having installed fresh at the time of Beta 2, and the problem started occurring whilst I was fully updated today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721537 Title: No sound from headphone jack on xps13 9350 after ubuntu 17.10 dist- upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1721537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421044] Re: Too easy to accidentally restart computer when 'restart to complete update' box pop up
Tested update-manager 1:0.196.13 on trusty, waited until an update happened that required a restart, and indeed the 'restart later' button had focus. Pressing spacebar dismissed the box without restarting the computer. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421044 Title: Too easy to accidentally restart computer when 'restart to complete update' box pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1421044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1421044] [NEW] Too easy to accidentally restart computer when 'restart to complete update' box pop up
Public bug reported: I was typing an email whilst an update was in progress, and when the 'restart to complete update' box popped up, I accidentally restarted my computer. I'm not sure whether this took one or two taps of the spacebar, but happened from me simply continuing to type for a second or so when the box popped up. If the box is to grab focus regardless of what the user is doing, then it needs to *not* have the 'restart now' button focused and ready for an enter key or spacebar. It would be better if no button had focus, so that an actual click was required to take action. What I expected to happen: Nothing, ideally. It's ok if my typing is interrupted, but nothing else should happen if I'm in the middle of typing when the box pops up. What happened: My computer restarted. Ubuntu version: 14.04 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: I was typing an email whilst an update was in progress, and when the 'restart to complete update' box popped up, I accidentally restarted my computer. I'm not sure whether this took one or two taps of the spacebar, but happened from me simply continuing to type for a second or so when the box popped up. If the box is to grab focus regardless of what the user is doing, then it needs to *not* have the 'restart now' button focused and ready for an enter key or spacebar. It would be better if no button had focus, so that an actual click was required to take action. + + What I expected to happen: Nothing, ideally. It's ok if my typing is + interrupted, but nothing else should happen if I'm in the middle of + typing when the box pops up. + + What happened: My computer restarted. + + Ubuntu version: 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1421044 Title: Too easy to accidentally restart computer when 'restart to complete update' box pop up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1421044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067557] Re: zlib1g 1.2.7 and libxml2 2.8 too new for each other?
Oh I see. Well that helps me a bit, thanks! Apologies for the misplaced blame on libxml2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067557 Title: zlib1g 1.2.7 and libxml2 2.8 too new for each other? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1067557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067557] Re: zlib1g 1.2.7 and libxml2 2.8 too new for each other?
This bug concerns both zlibg1 and libxml2, though it more concerns which versions are packaged with Ubuntu. ** Package changed: ubuntu => libxml2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067557 Title: zlib1g 1.2.7 and libxml2 2.8 too new for each other? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1067557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067557] [NEW] zlib1g 1.2.7 and libxml2 2.8 too new for each other?
Public bug reported: After an upgrade to Ubuntu 12.10 (64 bit, from 12.04) I appear to have zlib1g:i386 version 1:1.2.7.dfsg-13 and libxml2:i386 version 2.8.0+dfsg1-5ubuntu2. These appear to be the newest versions in the repositories. Running a third party proprietary program (Guitar Pro) that relies on libxml2:i386, I get the following error: /opt/GuitarPro6/launcher.sh ./GuitarPro: /opt/GuitarPro6/./libz.so.1: version `ZLIB_1.2.3.3' not found (required by /usr/lib/i386-linux-gnu/libxml2.so.2) I've read elsewhere [1] that zlib > 1.2.5 breaks libxml2 < 2.7.6.dfsg-2, so I'm wondering whether perhaps zlib 1.2.7 might break libxml2 2.8 as well, but that this isn't reflected in the dependencies. Apologies if this is actually a bug with Guitar Pro. It's not even supported on Ubuntu > 10.04 32bit (grumble grumble), so I'm playing with fire anyhow trying to get it to work. But it was working before with zlib1g:i386 (1:1.2.3.4.dfsg-3ubuntu4) and libxml2:i386 (2.7.8.dfsg-5.1ubuntu4.1)! So I'd like to know if there's any suggestions as to what I can do about this, or if it's likely to be a bug. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589134 ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067557 Title: zlib1g 1.2.7 and libxml2 2.8 too new for each other? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1067557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041523] Re: ccsm crashed with SIGSEGV in ? [libkconfig4.so] from ccsCopyBackendInfoFromBackend() from addBackendInfo() from getBackendInfoFromDir() from ccsGetExistingBackends()
No problem, thanks for the suggestion! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041523 Title: ccsm crashed with SIGSEGV in ? [libkconfig4.so] from ccsCopyBackendInfoFromBackend() from addBackendInfo() from getBackendInfoFromDir() from ccsGetExistingBackends() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041523] Re: ccsm crashed with SIGSEGV in ? [libkconfig4.so] from ccsCopyBackendInfoFromBackend() from addBackendInfo() from getBackendInfoFromDir() from ccsGetExistingBackends()
Well that's all well and good that that backend isn't supported, but how does one switch backends so that one can launch ccsm without a segfault? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041523 Title: ccsm crashed with SIGSEGV in ? [libkconfig4.so] from ccsCopyBackendInfoFromBackend() from addBackendInfo() from getBackendInfoFromDir() from ccsGetExistingBackends() To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005729] Re: gnome-terminal resizes to max height when mousing over gnome panel
I'm experiencing this bug too. The deciding factor as to which windows move and which don't, when I mouse-over the launchers on gnome-panel, appears to be whether that window has at any point in the past had an overlap outside of the screen struts, ie it has been anywhere that a newly created or maximised window could not be. So if I drag a window halfway off the bottom of the screen, or a few pixels underneath a panel, even if I drag it back, it will then move around randomly whenever I mouse-over the launchers on gnome-panel. It's kinda weird. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005729 Title: gnome-terminal resizes to max height when mousing over gnome panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1005729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919000] Re: hdfview launcher doesn't escape spaces in filepaths
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919000 Title: hdfview launcher doesn't escape spaces in filepaths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jhdf/+bug/919000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919000] [NEW] hdfview launcher doesn't escape spaces in filepaths
Public bug reported: Double clicking a hdf5 file sometimes results in hdfview opening but not displaying the file. This happens when there is a space somewhere in the filepath. It can be fixed by changing one line in the launcher /usr/bin/hdfview from: run_java ncsa.hdf.view.HDFView -root /usr/share/doc/libjhdf-doc/ $* to: run_java ncsa.hdf.view.HDFView -root /usr/share/doc/libjhdf-doc/ "$*" ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: hdfview 2.6.1-2 [modified: usr/bin/hdfview] ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Jan 20 11:44:53 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: jhdf UpgradeStatus: Upgraded to oneiric on 2011-12-20 (30 days ago) ** Affects: jhdf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919000 Title: hdfview launcher doesn't escape spaces in filepaths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jhdf/+bug/919000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 724369] Re: Port to gnome-panel 3 and gtk 3
Thanks guys, it's working great! I'm able to build and add to the panel as normal. Didn't think I'd be saying this so soon, but I dare say that with an indicator applet, gnome-panel 3 is a viable option for those that want to use Ubuntu but aren't keen on Unity or Gnome Shell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/724369 Title: Port to gnome-panel 3 and gtk 3 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/724369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626481] Re: maximized windows drop shadow on adjacent screen
Workaround: in CCSM, Window Decorations, change 'Shadow windows' from 'any' to 'any & !state=maxvert'. This will exclude maximized windows from being decorated with a shadow. Maybe this could be set by default? This is also useful for some panels/taskbars which would could otherwise have a shadow over them. What led me to this problem was that I wanted a tint2 panel to not be on top of all windows (because it being on top stopped hot corners from working), but also not have a shadow on top of it when a window was maximized. The above fix works perfectly! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/626481 Title: maximized windows drop shadow on adjacent screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/626481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303697] Re: [fglrx] vsync issues - screen tearing unrelated to compiz
Holy Jesus I never thought I'd see the day. Tearing gone on a System76 Panp7 running Ubuntu 10.10 with ccc 11.1 and after doing: sudo aticonfig --set-pcs-u32=DDX,EnableTearFreeDesktop,1 ...Now to go check how the Plymouth issues are doing... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/303697 Title: [fglrx] vsync issues - screen tearing unrelated to compiz -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 550004] Re: "Open with Other Application" remember feature does not work
Still experiencing this bug in Nautilus 1:2.32.0-0ubuntu1.1 under ubuntu 10.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/550004 Title: "Open with Other Application" remember feature does not work -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664273] Re: Window picker doesn't give back key binding
-- Window picker doesn't give back key binding https://bugs.launchpad.net/bugs/664273 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664273] [NEW] Window picker doesn't give back key binding
Public bug reported: Binary package hint: compiz After leaving the window picker through use of a hot corner, the keybinding for 'zoom window' is not returned, and so that key cannot be used with other programs unless compiz is restarted. Steps to reproduce: In the 'scale addons' plugin, set a single key for 'zoom window'. I'll use spacebar as an example. In simple ccsm, set a hot corner to 'initiate window picker'. Put your mouse in that corner to initiate the window picker. Put your mouse in the same corner again to return from the window picker. Expected behaviour: spacebar (or whatever key was set) should be able to be used normally whilst not in the window picker. Actual behaviour: After using the window picker, spaces can't be typed anymore. xev instead registers a press of the spacebar as: FocusOut event, serial 36, synthetic NO, window 0x561, mode NotifyGrab, detail NotifyAncestor FocusIn event, serial 36, synthetic NO, window 0x561, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 36, synthetic NO, window 0x0, keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This problem only occurs when using a hot corner to both enter and exit the window picker. If say super-w is used to enter, and corner to exit, or corner to enter and super-w to exit, or super-w to both enter and exit, the spacebar continues to work normally. I'm using ubuntu 10.10 64 bit, with compiz 1:0.8.6-0ubuntu9, as listed by the package manager. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: compiz 1:0.8.6-0ubuntu9 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 CompizPlugins: [core,ccp,move,resize,place,decoration,commands,text,regex,gnomecompat,workarounds,imgjpeg,crashhandler,dbus,mousepoll,shift,png,svg,grid,wall,animation,animationaddon,obs,wobbly,expo,scale,ezoom,scaleaddon] Date: Thu Oct 21 13:20:16 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Lsusb: Bus 002 Device 003: ID 147e:1000 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76, Inc. Pangolin Performance PackageArchitecture: all PciDisplay: 02:00.0 VGA compatible controller [0300]: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] [1002:9553] (prog-if 00 [VGA controller]) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=625ed789-1cb3-4081-9c7e-f812810b5126 ro quiet splash acpi_os_name=Linux acpi_osi=Linux vga=795 ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash RelatedPackageVersions: xserver-xorg 1:7.5+6ubuntu3 libgl1-mesa-glx 7.9~git20100924-0ubuntu2 libdrm2 2.4.21-1ubuntu2.1 xserver-xorg-video-intel 2:2.12.0-1ubuntu5 xserver-xorg-video-ati 1:6.13.1-1ubuntu5 SourcePackage: compiz XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 06/07/2010 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: CALPELLACRB.86C..X.00 dmi.board.asset.tag: Tag 12345 dmi.board.name: W76x/M77xCUH dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: CLEVO dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrCALPELLACRB.86C..X.00:bd06/07/2010:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp7:rvnCLEVO:rnW76x/M77xCUH:rvrNotApplicable:cvnCLEVO:ct9:cvrN/A: dmi.product.name: Pangolin Performance dmi.product.version: panp7 dmi.sys.vendor: System76, Inc. system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.35-22-generic ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Window picker doesn't give back key binding https://bugs.launchpad.net/bugs/664273 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303697] Re: [fglrx] vsync issues - screen tearing unrelated to compiz
Still present with the newest driver (fglrx 2.8.753) running on an otherwise fresh lucid install -- [fglrx] vsync issues - screen tearing unrelated to compiz https://bugs.launchpad.net/bugs/303697 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484043] Re: double click full screen plugin - undesired behaviour
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/35775567/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/35775568/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/35775569/ProcStatus.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/35775570/XsessionErrors.txt -- double click full screen plugin - undesired behaviour https://bugs.launchpad.net/bugs/484043 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 484043] [NEW] double click full screen plugin - undesired behaviour
Public bug reported: Binary package hint: eog This bug/feature request regards eye of gnome 2.28.1, which I'm running on ubuntu 9.10. When the "Fullscreen with double click" plugin is enabled, and when viewing a large image full screen, there is is scroll bar on the right. Clicking the scroll arrows scrolls as desired, but if you click too rapidly, it counts as a double-click and the image reverts back to being displayed in a window. The same applies when viewing in a window and scrolling, double-clicking the scroll arrows triggers the image to be displayed fullscreen. Since clicking scroll buttons rapidly is pretty common, I think the desired behaviour for this should be that double clicks be ignored on the scrollbar and only trigger the fullscreen/window change when they are on the image itself. ProblemType: Bug Architecture: amd64 Date: Tue Nov 17 17:50:35 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/eog InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) Package: eog 2.28.1-0ubuntu1 ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: eog Uname: Linux 2.6.31-14-generic x86_64 ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- double click full screen plugin - undesired behaviour https://bugs.launchpad.net/bugs/484043 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
