[Bug 1791058] Re: Wifi disconnects very very often and is hard to reconnect
Further on this bug: The wifi I am using is a 5GH AC network. When it disconnects, which is very often, such as every 10 minutes, sometimes it can reconnect by simply restarting the network-manager service, i.e $ service network-manager restart But sometimes this doesn't work and the only solution is to reboot! This problem is really painful, I am desperate for a solution or work around as I need this laptop nearly all the time. I do not have the courage to time to try an upgrade to 18.04 at the present time. Any thoughts would be great! Cheers, Bob -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1791058 Title: Wifi disconnects very very often and is hard to reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1791058/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1791058] [NEW] Wifi disconnects very very often and is hard to reconnect
Public bug reported: I have an Intel AC 7256 wifi adapter. Since at least 6 months, the wifi constantly disconnects and is very hard to reconnect by restarting the network-manager service. This is really painful. I see lots of questions on Ubuntu stack exchange, but no appropriate answers. Some output: $ lspci -nnk | grep 0280 -A2 02:00.0 Network controller [0280]: Intel Corporation Wireless 7265 [8086:095a] (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5110] Kernel driver in use: iwlwifi $ dmesg | grep iwl [2.255195] iwlwifi :02:00.0: Direct firmware load for iwlwifi-7265D-19.ucode failed with error -2 [2.256074] iwlwifi :02:00.0: Direct firmware load for iwlwifi-7265D-18.ucode failed with error -2 [2.274898] iwlwifi :02:00.0: loaded firmware version 17.352738.0 op_mode iwlmvm [2.322979] iwlwifi :02:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210 [2.323299] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [2.325591] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [2.403344] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [4.590676] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.591435] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.661301] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [4.661923] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5323.096942] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5323.097620] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5323.158679] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5323.159212] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5370.610087] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5370.610526] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5370.671749] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5370.672338] iwlwifi :02:00.0: L1 Enabled - LTR Enabled [ 5705.684169] iwlwifi :02:00.0: No association and the time event is over already... [ 5709.274041] iwlwifi :02:00.0: No association and the time event is over already... $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 2: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 3: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no I am getting desperate for a solution, but am not prepared to try an upgrade to 18.04 at this time due to criticality of the machine for work. Any help would be greatly appreciated. Thanks, BOb ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gvfs-backends 1.28.2-1ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Sep 6 13:00:52 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-network InstallationDate: Installed on 2015-05-11 (1213 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1791058 Title: Wifi disconnects very very often and is hard to reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1791058/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1464561] [NEW] Hotkey enable/disable touchpad does nothing
Public bug reported: Running Xubuntu on an Asus UX303LN laptop. The touchpad disable/enable hotkey (F9) does nothing. This makes it very hard to use the machine since the touchpad is constantly capturing random "mouse movements", making it impossible to enter text in the right place. When I use the machine I have an external bluetooth mouse, and disable the touhpad in the settings menu, so I can type, but it would be much better to have the option to use the touchpad, and switch it on/off. Also, if the bluetooth connection is lost, then I can do nothing and have to reboot! I have no idea how to debug this but would be happy to help. Another hotkey that does not work is F2 "airplane mode". This one is of no importance to me, but I mention it for completeness. I am really hoping for a fix! I am a Ubuntu beta-tester from long ago, and helped on the 1st 64bit version! Let me know, please!, Cheers, Bob I have attached all the files specified on the hotkey bug reporting page. I put them in an archive since that seems to be the only option for attaching multiple files? udevadm info --export-db > udev-db.txt dmesg > dmesg.log sudo lsinput > lsinput.log xkbcomp -xkb :0 - > xkbcomp.txt setxkbmap -print > xkbmap.txt ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jun 12 10:05:56 2015 InstallationDate: Installed on 2015-05-11 (31 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 064e:9700 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX303LNB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed root=UUID=eba1a0f5-161a-4061-99a4-b5598f7692c1 ro quiet splash vt.handoff=7 SourcePackage: systemd UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX303LNB.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX303LNB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.203:bd12/10/2014:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX303LNB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hotkey touchpad vivid ** Attachment added: "contains hotkey bug reporting outputs" https://bugs.launchpad.net/bugs/1464561/+attachment/4413664/+files/HotkeyReports.tar.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1464561 Title: Hotkey enable/disable touchpad does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464561/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 987220] Re: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI
This afffects me on 12.04 running on an Asus EEEpc 1201n It is systematic, the computer never completely powers off anymore, altough it used to some time ago. Also, I run Gnome not Unity. Cheers, Bob -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/987220 Title: [Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 963125] Re: Some metacity shortcuts get changed into lists and stop working
I do not use unity, but gnome and xfce and this bug just appeared today for me! What a terrible regression... Any workarounds? I tired to set the navigation on keyboard settings, but it was already set to alt-tab Please help! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/963125 Title: Some metacity shortcuts get changed into lists and stop working To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/963125/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726100] Re: cannot login after upgrade 10.4 to 10.10
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/726100 Title: cannot login after upgrade 10.4 to 10.10 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726100] [NEW] cannot login after upgrade 10.4 to 10.10
Public bug reported: Binary package hint: gnome-screensaver I am running amd64, the real time kernel. Since the update from 10.4 to 10.10 I cannot login as normal, since my password seems to be unrecognized in the graphic boot account selection screed. I must use the grub menu to select the recovery mode kernel, then resume boot and login at the command line prompt then startx. The password works at the command line. I tried to report this bug a month ago but couldn't get to the system to make the report. If I try to select the latest generic kernel, I get a cryptdisk error and then the boot loops. I am available to try to help to work on this, it is very painful. Please advise if you think a clean install of 10.10 would solve the issues. Thanks, Bob. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-screensaver 2.30.0-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-11.154-rt Uname: Linux 2.6.31-11-rt x86_64 Architecture: amd64 Date: Sun Feb 27 18:20:26 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None ProcEnviron: LANGUAGE=en_BE:en_US:en_GB:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue WindowManager: gnome-wm ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/726100 Title: cannot login after upgrade 10.4 to 10.10 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 718388] Re: cannot log in after upgrade from 10.4 to 10.10 on amd64
so that's it? I upgrade from a working system 10.4 to an unusable 10.10 and no help is available? What has happened to the days when Ubuntu support was the best around? I'm very disappointed. Thanks anyway, Bob On Mon, Feb 14, 2011 at 12:36 PM, Sebastien Bacher wrote: > could be a bug but it's not a gdm one if kernels or login don't work and > the description list several issues and lacks details to be useful, it > can be converted back to a bug when someone got useful informations for > it to be worked > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/718388 > > Title: > cannot log in after upgrade from 10.4 to 10.10 on amd64 > -- 50°48'39.85"N 4°25'20.29"E -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/718388 Title: cannot log in after upgrade from 10.4 to 10.10 on amd64 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 718388] Re: cannot log in after upgrade from 10.4 to 10.10 on amd64
Hi! Are you saying that this is no longer being treated as a bug? Surely, it *IS* a bug? Thanks, Bob On Mon, Feb 14, 2011 at 10:53 AM, Sebastien Bacher wrote: > ** Changed in: gdm (Ubuntu) > Status: New => Invalid > > ** Converted to question: > https://answers.launchpad.net/ubuntu/+source/gdm/+question/145315 > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/718388 > > Title: > cannot log in after upgrade from 10.4 to 10.10 on amd64 > -- 50°48'39.85"N 4°25'20.29"E -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/718388 Title: cannot log in after upgrade from 10.4 to 10.10 on amd64 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 718388] Re: cannot log in after upgrade from 10.4 to 10.10 on amd64
Thanks for looking into the bug. I am totally blocked now. Is there anything I can do to gain access to my machine? Thanks, Bob. On Sun, Feb 13, 2011 at 10:01 PM, Fabio Marconi wrote: > ** Package changed: ubuntu => gdm (Ubuntu) > > ** Tags added: lucid > > ** Tags added: lucid2maverick > ** Tags removed: lucid > > -- > You received this bug notification because you are a direct subscriber > of the bug. > https://bugs.launchpad.net/bugs/718388 > > Title: > cannot log in after upgrade from 10.4 to 10.10 on amd64 > -- 50°48'39.85"N 4°25'20.29"E -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/718388 Title: cannot log in after upgrade from 10.4 to 10.10 on amd64 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 16472] Re: Login Screen Resolution
same issue on amd64 with Gutsy 7.10. I tried the plain login screen solution - no help, I inspected my xorg.conf, but it seems correct, I treid the aticonfig but this crashed even if aticonfig --help worked (I filed a bug report). Anyone else with an idea? -- Login Screen Resolution https://bugs.launchpad.net/bugs/16472 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 188152] [NEW] aticonfig crashes
Public bug reported: Binary package hint: gdm I have been having the login screen resolution problem bug #16472 and tried to run aticonfig as suggested but this crashes on my AMD64 running gutsy 7.10. Any help woul dbe appreciated. This is the output: $ sudo aticonfig --initial --input=/etc/X11/xorg.conf Uninitialised file found, configuring. Using /etc/X11/xorg.conf Saved back-up to /etc/X11/xorg.conf.original-1 *** glibc detected *** aticonfig: munmap_chunk(): invalid pointer: 0x7fff5a89d980 *** === Backtrace: = /lib/libc.so.6(cfree+0x1b6)[0x2adf51052826] aticonfig[0x4148ed] aticonfig[0x414849] aticonfig[0x40c6e5] aticonfig(XOpenDisplay+0x2bd)[0x402485] aticonfig(XOpenDisplay+0x141)[0x402309] /lib/libc.so.6(__libc_start_main+0xf4)[0x2adf50ffab44] aticonfig(XOpenDisplay+0x62)[0x40222a] === Memory map: 0040-0042 r-xp 08:01 6950388 /usr/bin/aticonfig 0052-00526000 rw-p 0002 08:01 6950388 /usr/bin/aticonfig 00526000-00547000 rw-p 00526000 00:00 0 [heap] 2adf5020b000-2adf50228000 r-xp 08:01 16810057 /lib/ld-2.6.1.so 2adf50228000-2adf5022c000 rw-p 2adf50228000 00:00 0 2adf50427000-2adf50429000 rw-p 0001c000 08:01 16810057 /lib/ld-2.6.1.so 2adf50429000-2adf5043 r-xp 08:01 1114271 /usr/lib/libXrandr.so.2.1.0 2adf5043-2adf5062f000 ---p 7000 08:01 1114271 /usr/lib/libXrandr.so.2.1.0 2adf5062f000-2adf5063 rw-p 6000 08:01 1114271 /usr/lib/libXrandr.so.2.1.0 2adf5063-2adf50639000 r-xp 08:01 1114119 /usr/lib/libXrender.so.1.3.0 2adf50639000-2adf50838000 ---p 9000 08:01 1114119 /usr/lib/libXrender.so.1.3.0 2adf50838000-2adf50839000 rw-p 8000 08:01 1114119 /usr/lib/libXrender.so.1.3.0 2adf50839000-2adf5084a000 r-xp 08:01 1114254 /usr/lib/libXext.so.6.4.0 2adf5084a000-2adf50a49000 ---p 00011000 08:01 1114254 /usr/lib/libXext.so.6.4.0 2adf50a49000-2adf50a4a000 rw-p 0001 08:01 1114254 /usr/lib/libXext.so.6.4.0 2adf50a4a000-2adf50b54000 r-xp 08:01 6952269 /usr/lib/libX11.so.6.2.0 2adf50b54000-2adf50d54000 ---p 0010a000 08:01 6952269 /usr/lib/libX11.so.6.2.0 2adf50d54000-2adf50d5b000 rw-p 0010a000 08:01 6952269 /usr/lib/libX11.so.6.2.0 2adf50d5b000-2adf50d5c000 rw-p 2adf50d5b000 00:00 0 2adf50d5c000-2adf50ddc000 r-xp 08:01 7405640 /lib/libm-2.6.1.so 2adf50ddc000-2adf50fdb000 ---p 0008 08:01 7405640 /lib/libm-2.6.1.so 2adf50fdb000-2adf50fdd000 rw-p 0007f000 08:01 7405640 /lib/libm-2.6.1.so 2adf50fdd000-2adf5112f000 r-xp 08:01 16810067 /lib/libc-2.6.1.so 2adf5112f000-2adf5132e000 ---p 00152000 08:01 16810067 /lib/libc-2.6.1.so 2adf5132e000-2adf51331000 r--p 00151000 08:01 16810067 /lib/libc-2.6.1.so 2adf51331000-2adf51333000 rw-p 00154000 08:01 16810067 /lib/libc-2.6.1.so 2adf51333000-2adf51338000 rw-p 2adf51333000 00:00 0 2adf51338000-2adf5133a000 r-xp 08:01 6947972 /usr/lib/libXau.so.6.0.0 2adf5133a000-2adf51539000 ---p 2000 08:01 6947972 /usr/lib/libXau.so.6.0.0 2adf51539000-2adf5153a000 rw-p 1000 08:01 6947972 /usr/lib/libXau.so.6.0.0 2adf5153a000-2adf5153b000 rw-p 2adf5153a000 00:00 0 2adf5153b000-2adf5154 r-xp 08:01 6952252 /usr/lib/libXdmcp.so.6.0.0 2adf5154-2adf5173f000 ---p 5000 08:01 6952252 /usr/lib/libXdmcp.so.6.0.0 2adf5173f000-2adf5174 rw-p 4000 08:01 6952252 /usr/lib/libXdmcp.so.6.0.0 2adf5174-2adf51742000 r-xp 08:01 7405638 /lib/libdl-2.6.1.so 2adf51742000-2adf51942000 ---p 2000 08:01 7405638 /lib/libdl-2.6.1.so 2adf51942000-2adf51944000 rw-p 2000 08:01 7405638 /lib/libdl-2.6.1.so 2adf51944000-2adf51946000 rw-p 2adf51944000 00:00 0 2adf51946000-2adf51953000 r-xp 08:01 7405701 /lib/libgcc_s.so.1 2adf51953000-2adf51b53000 ---p d000 08:01 7405701 /lib/libgcc_s.so.1 2adf51b53000-2adf51b54000 rw-p d000 08:01 7405701 /lib/libgcc_s.so.1 7fff5aAborted (core dumped) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- aticonfig crashes https://bugs.launchpad.net/bugs/188152 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 23820] Re: Oct. 12 updates killed my Ubuntu: window manager hangs at login
Indeed, this is a thing of the past! Ubuntu is better than ever! I appreciate all the good work you guys are doing and I support free software at every chance I get! Thanks to you all! GF -- Oct. 12 updates killed my Ubuntu: window manager hangs at login https://launchpad.net/bugs/23820 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] Re: cannot associate file type with open command
I confirm that this now works on my AMD64 setup! thanks for the good work Ubuntu Team! GF -- cannot associate file type with open command https://launchpad.net/bugs/28621 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 16753] Re: KINO: can't use "open file" menu
Before I try all the work on the debugging instructions, are you sure it will give useful information? Kino doesn't "crash" it just reports an error and continues. Let me know, g -- KINO: can't use "open file" menu https://launchpad.net/bugs/16753 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] Re: [Bug 28621] Re: cannot associate file type with open command
I'm sorry but I don't have Dapper and cannot upgrade until it is ready for fear of losing my work platform... do let me know if there is any news, though. cheers, GF On 4/13/06, Daniel Holbach <[EMAIL PROTECTED]> wrote: > > It'd be great if you could test that with current Dapper - I just tried it > and it works nicely for me. > -- > cannot associate file type with open command > https://launchpad.net/malone/bugs/28621 > -- cannot associate file type with open command https://launchpad.net/bugs/28621 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 16753] Re: KINO: can't use "open file" menu
I have re-installed the 0.80 version, which is in fact Kino 0.7.5 according to the about menu. The problem persists, on my AMD64 breezy (fully up to date). When I try to use the open file to load, I get the following: (kino:15322): Gtk-WARNING **: Ignoring the separator setting >> Leaving Editor >> Left Editor >> Starting Editor Any ideas? -- KINO: can't use "open file" menu https://launchpad.net/bugs/16753 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug report changed: https://launchpad.net/malone/bugs/28621 Comment: Here it is! thanks for the persistence! $ gnomevfs-info doc.lyx Name : doc.lyx Type : Regular MIME type : application/x-lyx Size : 33854 Blocks: 72 I/O block size: 4096 Local : YES SUID : NO SGID : NO Sticky: NO Permissions : 600644 Link count: 1 UID : 1000 GID : 1000 Access time : Sun Feb 19 20:01:03 2006 Modification time : Sun Feb 19 20:01:03 2006 Change time : Sun Feb 19 20:01:03 2006 Device # : 2049 Inode # : 16187415 Readable : YES Writable : YES Executable: NO -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug report changed: https://launchpad.net/malone/bugs/28621 Comment: Thanks, but I already have that desktop: $ cat /usr/share/applications/lyx-qt.desktop [Desktop Entry] Encoding=UTF-8 Name=Lyx Comment=WYSIWYM document processor Exec=lyx-qt Icon=lyx-icon.xpm StartupNotify=false Terminal=false Type=Application Categories=Qt;Application;Office; MimeType=text/plain; So, still awaiting a fix... -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug report changed: https://launchpad.net/malone/bugs/28621 Comment: The answers are below: I log on as "bob": ~$ ls -al .local/share/ total 12 drwx-- 3 bob bob 4096 2005-02-24 13:31 . drwx-- 3 bob bob 4096 2005-02-24 13:31 .. drwx-- 2 bob bob 4096 2006-01-20 00:21 applications I did what you said, and got the association to work, perfectly... ~/.local/share/applications$ cat gconf-editor-usercreated.desktop [Desktop Entry] Encoding=UTF-8 Name=gconf-editor MimeType=text/plain; Exec=/usr/bin/gconf-editor Type=Application Terminal=false NoDisplay=true And when I do that, the gconf-editor appears in the property dialog of the list of associated applications. However, when I try the same for file doc.lyx, it fails. Here's the content of the file: ~/.local/share/applications$ more gconf-editor-usercreated.desktop [Desktop Entry] Encoding=UTF-8 Name=gconf-editor MimeType=application/x-lyx; Exec=/usr/bin/gconf-editor Type=Application Terminal=false NoDisplay=true When I do this, gconf-editor does not appear in properties dialog as an associtated application and double click does not call it. I am at a loss Thanks again! -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug report changed: https://launchpad.net/malone/bugs/28621 Comment: Thanks for considering this "minor" bug! The association does not appear in the properties tab, nor does it appear in the context menu, which only proposes "Open with", from which I can choose an application. Cheers! GF. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug report changed: https://launchpad.net/malone/bugs/28621 Description changed to: On Breezy, AMD64, when I try to add an open command by right click on icon, then properties, then Open with, I can select the application - in this case lyx-qt, but after clicking "Add" the association doesn't appear. Is it possible that I must be logged in as Root to do this? By the way, since the move from bugzilla, I've lost track of my open bugs? formly registered as [EMAIL PROTECTED] In any case, I continue to strongly support Ubuntu - It's made my world a better place in which to live! GF. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug report changed: https://launchpad.net/malone/bugs/28621 Comment: Yes, there is an entry created. But the open command still fails. I tried it for emacs. This is the content of ~/.local/share/applications/emacs21-usercustom-3.desktop [Desktop Entry] Version=1.0 Encoding=UTF-8 Name=Emacs 21 (X11) GenericName=Emacs Comment=GNU Emacs 21 Text Editor Exec=/usr/bin/emacs21 TryExec=emacs21 Terminal=false Type=Application Icon=/usr/share/emacs/21.4/etc/gnu-32x32.xpm Categories=Application;Utility;TextEditor; MimeType=application/x-lyx; NoDisplay=true -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28621] cannot associate file type with open command
Public bug reported: https://launchpad.net/malone/bugs/28621 Affects: gnome-desktop (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: On Breezy, AMD64, when I try to add an open command by right click on icon, then properties, then Open with, I can select the application - in this cas lyx-qt, but after clicking "Add" the association doesn't appear. Is it possible that I must be logged in as Root to do this? By the way, since the move from bugzilla, I've lost track of my open bugs? formly registered as [EMAIL PROTECTED] In any case, I continue to strongly support Ubuntu - It's made my world a better place in which to live! GF. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com http://lists.ubuntu.com/mailman/listinfo/desktop-bugs
