[gentoo-user] Re: Issues with Cando touch screen
On 07/07/2012 02:26 PM, Chandler Paul wrote: I should be able to easily do this simply by setting the option ThirdButtonEmulation in the evdev configuration file in /etc/X11/xorg.conf.d/ to on, however, this does not seem to make any difference even though I can see Xorg picking up the configuration option on boot in the logs. I had similar problems configuring a non-standard mouse. By using xev to examine mouse-clicks I discovered that the button numbering was completely different from what I expected. Maybe your touch screen is doing something similar?
Re: [gentoo-user] Dropbox settings get erased on reboot
On Sun, Jul 8, 2012 at 12:33 AM, Nilesh Govindrajan cont...@nileshgr.com wrote: For some strange reason, dropbox asks me to setup my account again after reboot, this doesn't happen on logout-login. I'm using gnome3 and emerged nautilus-dropbox, dropbox dropbox-cli. This didn't used to happen when I was using dropbox under ~/.dropbox-dist. Anybody facing this issue? I'm not...but I'm also not running GNOME on this machine, or using dropbox-cli here. In my case, I'm using net-misc/dropbox 1.2.48-r1 on x11-wm/awesome -- :wq
Re: [gentoo-user] Re: network scanner not seen by xsane on *some* systems
On Sat, Jul 07 2012, Michael Mol wrote: Stupid question...might your firewall be dropping packets? Check your firewall logs. Similarly, is there a difference in network connectivity between the machine that works and the two that don't? Also similarly, is the mfp on the wireless network along with the functioning box, while the two nonfunctioning boxes are on the wired side of your network? In that case, firewall and protection mechanisms on the router might be interfering. My home network is very simple cable modem -- linksys wet54g The 4 wired ports are connected to 1. ss: The officejet with the problem 2. lj: An irrelevant laserjet 3. allan: The desktop. Can print and scan (amd64) 4. ajglap: Main laptop. Can print, but not scan (~amd64) Wireless connections from the linksys to various devices including oldlap: backup laptop (~amd64) Yesterday I removed all printers from oldlap and reinstalled the officejet via hp-setup. It could neither print nor scan Today I removed all printers from oldlap and reinstalled the officejet via CUPS. It can print, but xsane reports no devices available. Both days oldlap can ping the officejet using URL: 192.168.1.50 allan
Re: [gentoo-user] Re: network scanner not seen by xsane on *some* systems
On Sun, Jul 8, 2012 at 10:57 AM, Allan Gottlieb gottl...@nyu.edu wrote: On Sat, Jul 07 2012, Michael Mol wrote: Stupid question...might your firewall be dropping packets? Check your firewall logs. Similarly, is there a difference in network connectivity between the machine that works and the two that don't? Also similarly, is the mfp on the wireless network along with the functioning box, while the two nonfunctioning boxes are on the wired side of your network? In that case, firewall and protection mechanisms on the router might be interfering. My home network is very simple cable modem -- linksys wet54g The 4 wired ports are connected to 1. ss: The officejet with the problem 2. lj: An irrelevant laserjet 3. allan: The desktop. Can print and scan (amd64) 4. ajglap: Main laptop. Can print, but not scan (~amd64) Wireless connections from the linksys to various devices including oldlap: backup laptop (~amd64) Yesterday I removed all printers from oldlap and reinstalled the officejet via hp-setup. It could neither print nor scan Today I removed all printers from oldlap and reinstalled the officejet via CUPS. It can print, but xsane reports no devices available. Both days oldlap can ping the officejet using URL: 192.168.1.50 OK, here's the order I'd tackle this in: 1) Get ajglap able to scan. 2) Test ajglap on the wireless, see if it's still able to scan. 3a) If ajglap can still scan, then the router is not getting in the way. Use the same procedure as in (1) to get oldlap working. 3b) If ajglap can no longer scan, then the router (which is probably doing arp and nd proxy, or possibly some form of layer 2 bridging) is hanging things up somehow. For getting ajglap to scan, I'd want to know the output of eix for the installed xsane packages on both ajglap and allan. Purpose: See the installed versions and USE flags. Depending on the results of that, I'd want to use wireshark to look for mdns traffic, or any other traffic incidental to scan attempts. I'd want to see what packets which show up during success cases, and I'd want to see what (if any) packets show up during failure cases. -- :wq
Re: [gentoo-user] Issues with Cando touch screen
On Sun, 08 Jul 2012 05:30:23 -0700 walt w41...@gmail.com wrote: I had similar problems configuring a non-standard mouse. By using xev to examine mouse-clicks I discovered that the button numbering was completely different from what I expected. Maybe your touch screen is doing something similar? A good suggestion, but after checking it doesn't look like that's the issue, I see Xev showing that the click events are returning button 1.
Re: [gentoo-user] Gentoo Wiki test page?
On 07/06/2012 10:25 PM, Walter Dnes wrote: Another option might be to simply work on the new page, and not publicize the URL until it's ready. Either that or a page in your user space (or the user page itself). Best, Sebastian
Re: [gentoo-user] Re: network scanner not seen by xsane on *some* systems (Solved)
On Sat, Jul 07 2012, walt wrote: On 07/07/2012 11:03 AM, Allan Gottlieb wrote: error: Unable to communicate with device (code=12): hp:/net/Officejet_7300_series?zc=HPCC9932 error: Unable to print to printer. Please check device and try again. Make me want to throw your laptop out of my window :) You can ping your printer, so I'd want to know what network traffic is going/coming from cups/hplip, if any. (I really like ngrep because it's absolutely trivial to use, so that's the tool I would use.) I saw this simple test on the hplip debugging website: Determine the IP address of your printer by printing out the network configuration page (or if you know it or can determine it in another way) Run: $ hp-makeuri ip-address For example: $ hp-makeuri 192.168.1.1 This will result in a device URI printed to the console. For example: hp:/net/Officejet_9100_series?ip=192.168.1.1 Copy this device URI Open the CUPS UI: http://localhost:631 (or YasT, etc) and install the printer by pasting the generated URI. I noticed that your hp:/etc URI looks reasonable, but I'd try using the ip address directly as an experiment. It's very quick even if it's useless :) OK lets try (on oldlap, where I tried yesterday and previously today) 1. Remove all printers (via cups) 2. hp-makeuri 192.168.1.50 CUPS URI: hp:/net/Officejet_7300_series?ip=192.168.1.50 SANE URI: hpaio:/net/Officejet_7300_series?ip=192.168.1.50 HP Fax URI: hpfax:/net/Officejet_7300_series?ip=192.168.1.50 3. Install (via cups) hp:/net/Officejet_7300_series?ip=192.168.1.50 Prints fine. 4. xsane hpaio:/net/Officejet_7300_series?ip=192.168.1.50 WORKS !! 5. xsane no arguments WORKS !! Let's try ajglap now (main laptop) 1. Remove all printers (via cups). 2. hp-makeuri 192.168.1.50 CUPS URI: hp:/net/Officejet_7300_series?ip=192.168.1.50 SANE URI: hpaio:/net/Officejet_7300_series?ip=192.168.1.50 HP Fax URI: hpfax:/net/Officejet_7300_series?ip=192.168.1.50 3. Install (via cups) hp:/net/Officejet_7300_series?ip=192.168.1.50 Prints fine. 4. xsane hpaio:/net/Officejet_7300_series?ip=192.168.1.50 Works 5. xsane no arguments Works Walt and michael, thanks so much. Walt, At least for me hp-setup is now replaced by hp-makeuri/cups as the favorite way to reinstall printers after an hplip or cups emerge. Again thank you. I can remember the last time I could print on both printers from all three system and could run xsane on all three as well. allan
[gentoo-user] profiling:/var/tmp/portage/xfce-base ... Cannot create directory
Hello! I noticed some strange messages in my ~/.xsession-errors log-file today. They look like this: profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-ice-layer.gcda:Skip profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-main.gcda:Skip . . . and so on. I haven't seen such messages before, that is why decided to ask here about what they mean. It is also strange that they mention the '/var/tmp/portage/' directory. Maybe something is wrong with installation system? Thanks. Vladimir - v...@ukr.net
Re: [gentoo-user] profiling:/var/tmp/portage/xfce-base ... Cannot create directory
On Sun, Jul 8, 2012 at 11:32 AM, v...@ukr.net wrote: Hello! I noticed some strange messages in my ~/.xsession-errors log-file today. They look like this: profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-ice-layer.gcda:Skip profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-main.gcda:Skip . . . and so on. I haven't seen such messages before, that is why decided to ask here about what they mean. It is also strange that they mention the '/var/tmp/portage/' directory. Maybe something is wrong with installation system? Thanks. Vladimir - v...@ukr.net Out of space? eclean-dist -pd possibly? Cheers, Mark
Re: [gentoo-user] start X - Segmentation fault
On 07/08/12 17:48, Michael Mol wrote: Re-emerge the drivers. I don't know a quick-and-easy way to scoop them all up, though. -- :wq I did: emerge $(qlist -IC x11-drivers) you can list the drivers by runing: qlist -IC x11-drivers It doesn't help. -- Joseph
Re: [gentoo-user] start X - Segmentation fault
On 07/08/12 16:08, Joseph wrote: On 07/08/12 17:48, Michael Mol wrote: Re-emerge the drivers. I don't know a quick-and-easy way to scoop them all up, though. -- :wq I did: emerge $(qlist -IC x11-drivers) you can list the drivers by runing: qlist -IC x11-drivers It doesn't help. Since in make.conf I have: VIDEO_CARDS=radeon vesa one of them should be able to start X after I recompile the drivers: qlist -IC x11-drivers x11-drivers/xf86-input-evdev x11-drivers/xf86-video-ati x11-drivers/xf86-video-vesa but it deosn't. What else to check. In the log I get: [ 805.883] 15: /usr/bin/X (0x40+0x24609) [0x424609] [ 805.883] Segmentation fault at address 0x9c [ 805.883] Fatal server error: [ 805.883] Caught signal 11 (Segmentation fault). Server aborting [ 805.883] [ 805.883] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 805.883] Please also check the log file at /var/log/Xorg.0.log for additional information. [ 805.883] [ 805.886] Output CRT1 disable success [ 805.891] Blank CRTC 0 success [ 805.891] Disable CRTC memreq 0 success [ 805.891] Disable CRTC 0 success [ 805.891] Blank CRTC 1 success [ 805.891] Disable CRTC memreq 1 success [ 805.891] Disable CRTC 1 success [ 805.891] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [ 805.891] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0 [ 805.891] (II) RADEON(0): MC_AGP_LOCATION : 0x [ 805.902] (II) RADEON(0): avivo_restore ! [ 806.002] Enable CRTC 0 success [ 806.002] Enable CRTC memreq 0 success [ 806.002] Unblank CRTC 0 success [ 806.005] Server terminated with error (1). Closing log file. -- Joseph
[gentoo-user] Re: Issues with Cando touch screen
On 07/08/2012 06:02 AM, Chandler Paul wrote: On Sun, 08 Jul 2012 05:30:23 -0700 walt w41...@gmail.com wrote: I had similar problems configuring a non-standard mouse. By using xev to examine mouse-clicks I discovered that the button numbering was completely different from what I expected. Maybe your touch screen is doing something similar? A good suggestion, but after checking it doesn't look like that's the issue, I see Xev showing that the click events are returning button 1. I'm happy to know that because I know nothing about touch-screens and I think I'd better learn now while I still have some brain cells left :) Can you generate any other events beside button1-down/up? Maybe by sliding your finger across the screen? I imagine that if I were designing such a gadget I'd want a finger-slide to translate to a scroll-wheel event. What events does your touchpad generate?
[gentoo-user] start X - Segmentation fault
After recent upgrade to Xorg-server-1.12.2 I get: Segmentation fault I recompiled x11-drivers: emerge $(qlist -IC x11-drivers) but I still get an error: [25.153] 14: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fef12ef62ec] [25.153] 15: /usr/bin/X (0x40+0x24a69) [0x424a69] [25.153] [25.153] Segmentation fault at address 0x9c [25.153] Fatal server error: [25.153] Caught signal 11 (Segmentation fault). Server aborting [25.153] [25.153] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [25.153] Please also check the log file at /var/log/Xorg.0.log for additional information. [25.153] [25.156] Output CRT1 disable success [25.156] Blank CRTC 0 success [25.156] Disable CRTC memreq 0 success [25.172] Disable CRTC 0 success [25.172] Blank CRTC 1 success [25.172] Disable CRTC memreq 1 success [25.172] Disable CRTC 1 success [25.172] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [25.172] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0 [25.172] (II) RADEON(0): MC_AGP_LOCATION : 0x [25.183] (II) RADEON(0): avivo_restore ! [25.283] Enable CRTC 0 success [25.283] Enable CRTC memreq 0 success [25.283] Unblank CRTC 0 success [25.286] Server terminated with error (1). Closing log file. Upgrade to all other boxes went fine except this one (the last one). I went back xorg-server-1.11.4-r1 but I still get the same error message. This was a box in remote location, so the upgrade was done via ssh and I was able to login via NX but when I tried to login locally (at the box I get: Segmentation fault What should I try next? -- Joseph
Re: [gentoo-user] start X - Segmentation fault
On Sun, Jul 8, 2012 at 5:41 PM, Joseph syscon...@gmail.com wrote: After recent upgrade to Xorg-server-1.12.2 I get: Segmentation fault I recompiled x11-drivers: emerge $(qlist -IC x11-drivers) but I still get an error: [25.153] 14: /lib64/libc.so.6 (__libc_start_main+0xec) [0x7fef12ef62ec] [25.153] 15: /usr/bin/X (0x40+0x24a69) [0x424a69] [25.153] [25.153] Segmentation fault at address 0x9c [25.153] Fatal server error: [25.153] Caught signal 11 (Segmentation fault). Server aborting [25.153] [25.153] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [25.153] Please also check the log file at /var/log/Xorg.0.log for additional information. [25.153] [25.156] Output CRT1 disable success [25.156] Blank CRTC 0 success [25.156] Disable CRTC memreq 0 success [25.172] Disable CRTC 0 success [25.172] Blank CRTC 1 success [25.172] Disable CRTC memreq 1 success [25.172] Disable CRTC 1 success [25.172] (II) RADEON(0): RADEONRestoreMemMapRegisters() : [25.172] (II) RADEON(0): MC_FB_LOCATION : 0x00e700c0 0x00e700c0 [25.172] (II) RADEON(0): MC_AGP_LOCATION : 0x [25.183] (II) RADEON(0): avivo_restore ! [25.283] Enable CRTC 0 success [25.283] Enable CRTC memreq 0 success [25.283] Unblank CRTC 0 success [25.286] Server terminated with error (1). Closing log file. Upgrade to all other boxes went fine except this one (the last one). I went back xorg-server-1.11.4-r1 but I still get the same error message. This was a box in remote location, so the upgrade was done via ssh and I was able to login via NX but when I tried to login locally (at the box I get: Segmentation fault What should I try next? Re-emerge the drivers. I don't know a quick-and-easy way to scoop them all up, though. -- :wq
Re: [gentoo-user] Re: Issues with Cando touch screen
On Sun, 08 Jul 2012 14:36:26 -0700 walt w41...@gmail.com wrote: Can you generate any other events beside button1-down/up? Maybe by sliding your finger across the screen? I imagine that if I were designing such a gadget I'd want a finger-slide to translate to a scroll-wheel event. What events does your touchpad generate? No, not yet. Such is possible with the use of other programs, however for the time being I really just want to get right clicking to work, along with being able to control windows. And my touch pad seems to generate the same button 1 events when I left click it, if that's what you were asking.
Re: [gentoo-user] Gentoo Wiki test page?
On Jul 9, 2012 12:49 AM, Sebastian Pipping sp...@gentoo.org wrote: On 07/06/2012 10:25 PM, Walter Dnes wrote: Another option might be to simply work on the new page, and not publicize the URL until it's ready. Either that or a page in your user space (or the user page itself). +1 for the user name space suggestion. By using your own sandbox, you can take your time polishing the page until it's fit for publication. Rgds,
Re: [gentoo-user] profiling:/var/tmp/portage/xfce-base ... Cannot create directory
On Jul 9, 2012 1:39 AM, Mark Knecht markkne...@gmail.com wrote: On Sun, Jul 8, 2012 at 11:32 AM, v...@ukr.net wrote: Hello! I noticed some strange messages in my ~/.xsession-errors log-file today. They look like this: profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-ice-layer.gcda:Skip profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-main.gcda:Skip . . . and so on. I haven't seen such messages before, that is why decided to ask here about what they mean. It is also strange that they mention the '/var/tmp/portage/' directory. Maybe something is wrong with installation system? Thanks. Vladimir - v...@ukr.net Out of space? eclean-dist -pd possibly? Or out of inodes. I've painstakingly learnt to host the portage build directory on reiserfs instead of ext3/4. Rgds,
Re: [gentoo-user] profiling:/var/tmp/portage/xfce-base ... Cannot create directory
On Mon, 9 Jul 2012 07:29:15 +0700 Pandu Poluan pa...@poluan.info wrote: On Jul 9, 2012 1:39 AM, Mark Knecht markkne...@gmail.com wrote: On Sun, Jul 8, 2012 at 11:32 AM, v...@ukr.net wrote: Hello! I noticed some strange messages in my ~/.xsession-errors log-file today. They look like this: profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-ice-layer.gcda:Skip profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-main.gcda:Skip . . . and so on. I haven't seen such messages before, that is why decided to ask here about what they mean. It is also strange that they mention the '/var/tmp/portage/' directory. Maybe something is wrong with installation system? Thanks. Vladimir - v...@ukr.net Out of space? eclean-dist -pd possibly? Or out of inodes. I've painstakingly learnt to host the portage build directory on reiserfs instead of ext3/4. Rgds, No, I don't think so. I've built things as large as Libreoffice on ext4 before. I can't imagine many situations where you could ever possibly run out of inodes.
Re: [gentoo-user] profiling:/var/tmp/portage/xfce-base ... Cannot create directory
You forgot to disable pgo when you compile some xfce-session . 2012/7/9 v...@ukr.net Hello! I noticed some strange messages in my ~/.xsession-errors log-file today. They look like this: profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-ice-layer.gcda:Skip profiling:/var/tmp/portage/xfce-base:Cannot create directory profiling:/var/tmp/portage/xfce-base/xfce4-session-4.6.1-r1/work/xfce4-session-4.6.1/xfce4-session/xfce4_session-main.gcda:Skip . . . and so on. I haven't seen such messages before, that is why decided to ask here about what they mean. It is also strange that they mention the '/var/tmp/portage/' directory. Maybe something is wrong with installation system? Thanks. Vladimir - v...@ukr.net
Re: [gentoo-user] start X - Segmentation fault
Joseph syscon...@gmail.com writes: This was a box in remote location, so the upgrade was done via ssh and I was able to login via NX but when I tried to login locally (at the box I get: Segmentation fault What should I try next? As you can log in remotely but get a segfault when logging in locally, could it be one of the PAM modules (one which is called for local login and starting X but not for ssh remote login) is segfaulting?
Re: [gentoo-user] Re: qemu not working on a P3M
On Sun, 2012-07-08 at 07:19 +0800, wdk@moriah wrote: if I try and use qemu-386 it has limited cmd line options according to -h, and barfs on any of the normal options such as -cdrom - hence my feeling its missing a wrapper. thanks, might have to do git to see if its different. BillK On 07/07/2012, at 22:32, walt w41...@gmail.com wrote: On 07/07/2012 07:14 AM, walt wrote: Qemu supplies two different binaries: one you can run as an unprivileged user (usually named qemu-i386 or whatever) and another that needs special privileges (usually named gemu-system-i386 or whatever). I just remembered that installing the git version actually does give you a binary named 'qemu' but I never understood how that relates to the other two binaries, so I've never used that one either :) Solved - might help others ... Thanks Walt for the hints. Most of the gentoo/qemu guides are seriously out of date and semi-useless. You need certain kernel features enabled, otherwise qemu will just silently give you very limited set of options and basically wont run, and wont tell you why. Which options ... I just turned on everything with VM in it. You need the following in make.conf: QEMU_SOFTMMU_TARGETS=i386 QEMU_USER_TARGETS=i386 to build x86 only qemu-kvm has simple script to start it up: moriah qemu # cat `which qemu-kvm` #!/bin/sh exec /usr/bin/qemu-system-x86_64 --enable-kvm $@ moriah qemu # Other qemu ebuilds dont install a similar script. The qemu-user ebuild installs static builds (or at least they have static in the name - why?) You need to run qemu-system-i386 to start the emulator. On a P3M I am using the app-emulation/qemu and app-emulation/kqemu ebuilds - not sure if I need kqemu so that needs testing when I get a guest installed. kqemu needs a user patch on 3.4.4 but builds and inserts ok once patched. The app-emulation/qemu-kvm installs but dies on a P3 when you try and run it - needs a cpu with the right VM facilities. Oh, and I installed from git to test ... and found it didnt have an uninstall. messy! Makes one appreciate ebuilds/gentoo and devs :) Part of my problem was using vmware and bochs/qemu for years and having legacy ideas on whats required. BillK
