[Touch-packages] [Bug 1164016] Re: restore type-ahead find
Why don't we have both options? Why removing something that we like
(find folder/file with a letter) and insisting on something else
(search)? I am trying to get used to this new behavior for almost a
week, but it is just slowing me down.
This could be implemented as simple as this:
## keypress event
switch (option_search_or_locate ) {
case 1: locate_folder (char_pressed); break;
case 2: search (char_pressed); break;
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1164016
Title:
restore type-ahead find
Status in Nautilus:
Expired
Status in nautilus package in Ubuntu:
Fix Released
Status in ubuntu-settings package in Ubuntu:
Fix Released
Bug description:
GNOME removed type-ahead find in Nautilus 3.6, not without
controversy:
https://mail.gnome.org/archives/nautilus-
list/2012-August/msg2.html
Now when you type in a Nautilus window, Nautilus immediately performs
a search in the current directory and all its subdirectories. I
personally find this annoying. If I want to search, I'll click the
search icon. Often I'm looking at a long directory listing and simply
want to jump to a certain point in it, and type-ahead find works great
for that.
Would Ubuntu consider patching type-ahead find back in?
To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
In Ubuntu 18.04 this problem is now present again :-( it is really annoying... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1513024] Re: Display-server randomly crashing in Ubuntu 15.10 after upgrade
I experience similar problem but with Intel graphic card i915. And mostly when using Google Chrome, LibreOffice or Viber. For example, I clicked Tools -> Options in LibreOffice and I was returned to login screen. Or I was zooming google maps... or when talking to someone on Viber... I believe it has to do something with hardware accelerator or openGL? (I am just an ordinary user so do not take my comments so seriously). I noticed that LibreOffice does not allow to enable Hardware Accelerator from time to time... When Ubuntu 15.10 was published, this was happening more often. Now, it happenes rarely. But unexpected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1513024 Title: Display-server randomly crashing in Ubuntu 15.10 after upgrade Status in xorg package in Ubuntu: Incomplete Bug description: On: Ubuntu 15.10 After some random amount of time (at first correlated with actions such as switching between screens, max-/minimising windows, but now also sometimes not), the display server seems to die completely, restarting after a few seconds to dump me at the login screen. Getting errors like: $ dmesg ... [ 239.809761] WARNING: CPU: 0 PID: 1879 at /build/linux-AxjFAn/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 i915_gem_track_fb+0x129/0x140 [i915]() [ 239.809762] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits)) [ 239.809763] Modules linked in: [ 239.809765] rfcomm msr acpi_call(OE) pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) openafs(POE) binfmt_misc bnep btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media arc4 intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel iwlmvm aes_x86_64 lrw gf128mul glue_helper mac80211 ablk_helper cryptd joydev input_leds snd_seq_midi serio_raw snd_seq_midi_event snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi thinkpad_acpi snd_rawmidi nvram iwlwifi snd_seq snd_hda_intel rtsx_pci_ms memstick snd_hda_codec lpc_ich cfg80211 snd_hda_core snd_hwdep snd_pcm mei_me ie31200_edac mei snd_seq_device edac_core shpchp snd_timer snd soundcore [ 239.809798] ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 mac_hid xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 rtsx_pci_sdmmc nouveau i915 mxm_wmi ttm e1000e i2c_algo_bit psmouse ahci drm_kms_helper libahci ptp rtsx_pci pps_core drm wmi video [ 239.809822] CPU: 0 PID: 1879 Comm: Xorg Tainted: P OE 4.2.0-16-generic #19-Ubuntu [ 239.809824] Hardware name: LENOVO 20AWS37E00/20AWS37E00, BIOS GLET77WW (2.31 ) 01/27/2015 [ 239.809825] 2aa5ef7b 8800a922fac8 817e8c09 [ 239.809827] 8800a922fb20 8800a922fb08 8107b3c6 [ 239.809829] 880425a47840 0010 8804256a 8804256a [ 239.809831] Call Trace: [ 239.809836] [] dump_stack+0x45/0x57 [ 239.809841] [] warn_slowpath_common+0x86/0xc0 [ 239.809843] [] warn_slowpath_fmt+0x55/0x70 [ 239.809853] [] i915_gem_track_fb+0x129/0x140 [i915] [ 239.809868] [] intel_prepare_plane_fb+0xe7/0x1a0 [i915] [ 239.809874] [] drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper] [ 239.809887] [] ? drm_atomic_check_only+0x215/0x540 [drm] [ 239.809901] [] intel_atomic_commit+0x42/0x100 [i915] [ 239.809910] [] drm_atomic_commit+0x37/0x60 [drm] [ 239.809915] [] drm_atomic_helper_plane_set_property+0x87/0xc0 [drm_kms_helper] [ 239.809922] [] ? _object_find+0x69/0xa0 [drm] [ 239.809930] [] drm_mode_plane_set_obj_prop+0x2d/0x90 [drm] [ 239.809939] [] drm_mode_obj_set_property_ioctl+0x1c6/0x270 [drm] [ 239.809944] [] drm_ioctl+0x125/0x610 [drm] [ 239.809947] [] ? fsnotify+0x316/0x4a0 [ 239.809954] [] ? drm_mode_obj_get_properties_ioctl+0xa0/0xa0 [drm] [ 239.809957] [] do_vfs_ioctl+0x295/0x480 [ 239.809959] [] ? __sb_end_write+0x35/0x70 [ 239.809961] [] ? vfs_write+0x15a/0x1a0 [ 239.809963] [] SyS_ioctl+0x79/0x90 [ 239.809966] [] entry_SYSCALL_64_fastpath+0x16/0x75 [ 239.809967] ---[ end trace d4f1687d97169580 ]--- [ 240.634359] nouveau E[ PIBUS][:02:00.0] HUB0: 0x6013d4 0x5704 (0x1c708200) [ 240.634368] nouveau E[ PIBUS][:02:00.0] GPC0: 0x4188ac 0x0001 (0x1c70822e) where the latter part also appears in the error log after xserver crashed, briefly visible before its restart. Any help is
[Touch-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
The same happened to me today when I installed audacity. I am using Ubuntu 14.10. The problem was solved from comment number #12: I went into Audacity and changed the microphone source in the drop-down menu from sysdefault: Headphone Mic:0 to sysdefault: Internal Mic:0 and it fixed it.! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in alsa-driver package in Ubuntu: Expired Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. Steps to reproduce : 1) Install audacity 2.0.3 from official Ubuntu repositories 2) Open Audacity and play something with it 3) That's it : no more headphones sound. - alsa log created with 'alsa-info.sh' (https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/ - pulse log when I plug in my headphones, I run a MP3 file with VLC, close VLC then unplug headphones (https://wiki.ubuntu.com/PulseAudio/Log) : http://paste.ubuntu.com/7131713/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
