[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Same problem with my OneAudio headset. I try to enable HSP/FSP profile and it says unavailable. It worked OK in 18.04 then I upgraded to 20.04 and it stopped working. 4 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "0" alsa.card_name = "HDA NVidia" alsa.long_card_name = "HDA NVidia at 0xf608 irq 65" alsa.driver_name = "snd_hda_intel" device.bus_path = "pci-:07:00.1" sysfs.path = "/devices/pci:00/:00:03.1/:07:00.1/sound/card0" device.bus = "pci" device.vendor.id = "10de" device.vendor.name = "NVIDIA Corporation" device.product.id = "10f8" device.product.name = "TU104 HD Audio Controller" device.string = "0" device.description = "TU104 HD Audio Controller" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: unknown) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-stereo-extra3: Digital Stereo (HDMI 4) Output (priority 5700, available: no) output:hdmi-surround-extra3: Digital Surround 5.1 (HDMI 4) Output (priority 600, available: no) output:hdmi-surround71-extra3: Digital Surround 7.1 (HDMI 4) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.pci-_07_00.1.hdmi-stereo/#5: TU104 HD Audio Controller Digital Stereo (HDMI) sources: alsa_output.pci-_07_00.1.hdmi-stereo.monitor/#7: Monitor of TU104 HD Audio Controller Digital Stereo (HDMI) ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: yes) properties: device.icon_name = "video-display" device.product.name = "34GL750 " hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-3: HDMI / DisplayPort 4 (priority 5600, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "2" alsa.card_name = "Valve VR Radio & HMD Mic" alsa.long_card_name = "Valve Corporation Valve VR Radio & HMD Mic at usb-:08:00.3-1.3.3, full spee" alsa.driver_name = "snd_usb_audio" device.bus_path = "pci-:08:00.3-usb-0:1.3.3:1.1" sysfs.path = "/devices/pci:00/:00:07.1/:08:00.3/usb5/5-1/5-1.3/5-1.3.3/5-1.3.3:1.1/sound/card2" udev.id = "usb-Valve_Corporation_Valve_VR_Radio___HMD_Mic_0F1B3BE619-LYM-01" device.bus = "usb" device.vendor.id = "28de" device.vendor.name = "Valve Software" device.product.id = "2102" device.product.name = "Valve VR Radio & HMD Mic" device.serial = "Valve_Corporation_Valve_VR_Radio___HMD_Mic_0F1B3BE619-LYM" device.string = "2" device.description = "Valve VR Radio & HMD Mic" module-udev-detect.discovered = "1" device.icon_name = "audio-card-usb" profiles: input:mono-fallback: Mono Input (priority 1, available: unknown) input:multichannel-input: Multichannel Input (priority 1, available: unknown) off: Off (priority 0, available: unknown)
[Desktop-packages] [Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
Adding to a sudo-enabled group is not enough? Since /etc/passwd and /etc/shadow do not have 'account type' fields, what does it mean to be an administrator? Belong to the admin group? adm? sudo? Why did gnome-control-center asked specifically for patola's password? What if there were two people with 'administrator' types? Should it instead ask for the root password then? [22:08] [7973] [patola@buzinskas patola]% id uid=1000(patola) gid=1000(patola) groups=1000(patola),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1001(procer3d) [22:08] [7974] [patola@buzinskas patola]% id razgriz uid=1002(razgriz) gid=1003(razgriz) groups=1003(razgriz),1001(procer3d) [22:08] [7975] [patola@buzinskas patola]% id felipe uid=1001(felipe) gid=1002(felipe) groups=1002(felipe),1001(procer3d) [22:08] [7976] [patola@buzinskas patola]% id ayrton uid=1003(ayrton) gid=1004(ayrton) groups=1004(ayrton),1001(procer3d) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
Attachment screen showing the logged in user is indeed razgriz, but it asks for patola's password ** Attachment added: "unlock button askin password for wrong user" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+attachment/5133306/+files/Selection_001.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: New Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768995] [NEW] The "Unlock" button of user administration asks for wrong user
Public bug reported: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaultsenv_reset Defaultsmail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification rootALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudo ALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d = expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user Status in gnome-control-center package in Ubuntu: New Bug description: I have just installed a quite vanilla Ubuntu 18.04 setup with just 4 users: patola, razgriz, ayrton, felipe. The first user, uid 1000, was patola. As patola, I also have done the adduser and passwd for them. Then razgriz logged in to the machine (he's on the procer3d group). When he tried to go to control center, details, users, and he clicked on the "Unlock" button, the dialog asked for patola's password, not his password I don't know if the sudoers file has any impact on it, but here it is: # # This file MUST be edited with the 'visudo' command as root. # # Please consider adding local content in /etc/sudoers.d/ instead of # directly modifying this file. # # See the man page for details on how to write a sudoers file. # Defaults env_reset Defaults mail_badpass Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" # Host alias specification # User alias specification # Cmnd alias specification # User privilege specification root ALL=(ALL:ALL) ALL # 3DProcer %procer3d ALL=(ALL) NOPASSWD: ALL # Members of the admin group may gain root privileges #%admin ALL=(ALL) ALL # Allow members of group sudo to execute any command #%sudoALL=(ALL:ALL) ALL # See sudoers(5) for more information on "#include" directives: #includedir /etc/sudoers.d ===== expected behaviour: gnome-control-center should ask for razgriz' password, he was the one logged in (patola was not at the time). Instead, it asked for patola's password. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 3 19:17:49 2018 InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications ab
[Desktop-packages] [Bug 1562387] Re: digimend / wacom drivers do not recognize chinese clone
Jason, The edits on 10-evdev.conf are not unnecessary. If general-purpose drivers are loaded before the huion drivers, the huion drivers are not loaded. The catch-all rule in 10-evdev.conf prevents the correct drivers from being loaded. I'll see if I file a bug report in linuxwacom to see if they can integrate the huion entries. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1562387 Title: digimend / wacom drivers do not recognize chinese clone Status in xf86-input-wacom package in Ubuntu: New Bug description: I have a chinese Gaomon 860T tablet, it is a clone of a Huion H610 tablet which in turn should be supported by digimend drivers (which are installed and loaded). However, it is only partially recognized as such - xsetwacom does not recognize, but libwacom-list-local-devices does, also xinput list correctly lists them but the wacom tablet entry in system settings says "No tablet detected". I am left-handed and I need the system settings wacom configuration to work so that I can use the tablet as left-handed tablet. This is a showstopper for me and I need that working to do my job. Here are the commands I used. I am using stock digimend-dkms from Ubuntu repository, which seems to be up-to-date with digimend github: [17:01] [4853] [patola@trololo /tmp]% xsetwacom --list devices [17:01] [4854] [patola@trololo /tmp]% /usr/bin/libwacom-list-local-devices [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [17:01] [4855] [patola@trololo /tmp]% dpkg -l | grep digimend ii digimend-dkms 6 all A collection of graphics tablet drivers by DIGImend project [17:04] [4856] [patola@trololo /tmp]% xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB USB Keykoard id=9[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouseid=10 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pad id=11 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pen id=12 [slave pointer (2)] ⎜ ↳ HUION PenTablet Mouse id=13 [slave pointer (2)] ⎜ ↳ HUION PenTablet Consumer Control id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ USB USB Keykoard id=8[slave keyboard (3)] ↳ HUION PenTablet System Controlid=14 [slave keyboard (3)] ↳ HUION PenTablet Keyboard id=15 [slave keyboard (3)] [17:04] [4857] [patola@trololo /tmp]% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1562387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1562387] Re: digimend / wacom drivers do not recognize chinese clone
However, I was able to get progress on this issue: now xsetwacom works. What was happening is that the first dbus entry for evdev had a catchall rule for tablets which assigned evdev drivers to the tablet before the wacom drivers would have a chance. So I editted: /usr/share/X11/xorg.conf.d/10-evdev.conf and commented the catchall tablet rules and then added /usr/share/X11/xorg.conf.d/50-huion.conf With these contents: # Huion tablets Section "InputClass" Identifier "Huion class" MatchProduct "HUION" MatchIsTablet "on" MatchDevicePath "/dev/input/event*" Driver "wacom" EndSection Section "InputClass" Identifier "Huion buttons" MatchProduct "HUION" MatchIsKeyboard "on" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection Section "InputClass" Identifier "Huion scroll" MatchProduct "HUION" MatchIsPointer "off" MatchIsKeyboard "off" MatchIsTouchpad "off" MatchIsTablet "off" MatchIsTouchscreen "off" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection And now the tablet is recognized by xsetwacom: [17:31] [4961] [patola@trololo patola]% xsetwacom --list HUION PenTablet Pen stylus id: 10 type: STYLUS HUION PenTablet Pad pad id: 11 type: PAD However, the System Settings Wacom entry still does not recognize it, "No tablet detected". I guess I will have to do it manually in the meanwhile? BTW, this is issue #26 from digimend drivers: https://github.com/DIGImend/digimend-kernel-drivers/issues/26 So there IS a bug to be fixed in xserver-xorg-core: /usr/share/X11/xorg.conf.d/10-evdev.conf and huion configuration. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1562387 Title: digimend / wacom drivers do not recognize chinese clone Status in xf86-input-wacom package in Ubuntu: New Bug description: I have a chinese Gaomon 860T tablet, it is a clone of a Huion H610 tablet which in turn should be supported by digimend drivers (which are installed and loaded). However, it is only partially recognized as such - xsetwacom does not recognize, but libwacom-list-local-devices does, also xinput list correctly lists them but the wacom tablet entry in system settings says "No tablet detected". I am left-handed and I need the system settings wacom configuration to work so that I can use the tablet as left-handed tablet. This is a showstopper for me and I need that working to do my job. Here are the commands I used. I am using stock digimend-dkms from Ubuntu repository, which seems to be up-to-date with digimend github: [17:01] [4853] [patola@trololo /tmp]% xsetwacom --list devices [17:01] [4854] [patola@trololo /tmp]% /usr/bin/libwacom-list-local-devices [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [17:01] [4855] [patola@trololo /tmp]% dpkg -l | grep digimend ii digimend-dkms 6 all A collection of graphics tablet drivers by DIGImend project [17:04] [4856] [patola@trololo /tmp]% xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB USB Keykoard id=9[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouseid=10 [slave pointer (2
[Desktop-packages] [Bug 1562387] Re: digimend / wacom drivers do not recognize chinese clone
I apologize, I did not tell my computer configuration: Ubuntu 15.10 64 bits with all patches applied [17:25] [4958] [patola@trololo patola]% lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:desktop-4.1-amd64:desktop-4.1-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:graphics-4.1-amd64:graphics-4.1-noarch:languages-3.2-amd64:languages-3.2-noarch:languages-4.0-amd64:languages-4.0-noarch:languages-4.1-amd64:languages-4.1-noarch:multimedia-3.2-amd64:multimedia-3.2-noarch:multimedia-4.0-amd64:multimedia-4.0-noarch:multimedia-4.1-amd64:multimedia-4.1-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:printing-4.1-amd64:printing-4.1-noarch:qt4-3.1-amd64:qt4-3.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1562387 Title: digimend / wacom drivers do not recognize chinese clone Status in xf86-input-wacom package in Ubuntu: New Bug description: I have a chinese Gaomon 860T tablet, it is a clone of a Huion H610 tablet which in turn should be supported by digimend drivers (which are installed and loaded). However, it is only partially recognized as such - xsetwacom does not recognize, but libwacom-list-local-devices does, also xinput list correctly lists them but the wacom tablet entry in system settings says "No tablet detected". I am left-handed and I need the system settings wacom configuration to work so that I can use the tablet as left-handed tablet. This is a showstopper for me and I need that working to do my job. Here are the commands I used. I am using stock digimend-dkms from Ubuntu repository, which seems to be up-to-date with digimend github: [17:01] [4853] [patola@trololo /tmp]% xsetwacom --list devices [17:01] [4854] [patola@trololo /tmp]% /usr/bin/libwacom-list-local-devices [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [17:01] [4855] [patola@trololo /tmp]% dpkg -l | grep digimend ii digimend-dkms 6 all A collection of graphics tablet drivers by DIGImend project [17:04] [4856] [patola@trololo /tmp]% xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB USB Keykoard id=9[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouseid=10 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pad id=11 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pen id=12 [slave pointer (2)] ⎜ ↳ HUION PenTablet Mouse id=13 [slave pointer (2)] ⎜ ↳ HUION PenTablet Consumer Control id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
[Desktop-packages] [Bug 1562387] Re: digimend / wacom drivers do not recognize chinese clone
bound it to the package containing xsetwacom ** Package changed: transgui (Ubuntu) => xf86-input-wacom (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1562387 Title: digimend / wacom drivers do not recognize chinese clone Status in xf86-input-wacom package in Ubuntu: New Bug description: I have a chinese Gaomon 860T tablet, it is a clone of a Huion H610 tablet which in turn should be supported by digimend drivers (which are installed and loaded). However, it is only partially recognized as such - xsetwacom does not recognize, but libwacom-list-local-devices does, also xinput list correctly lists them but the wacom tablet entry in system settings says "No tablet detected". I am left-handed and I need the system settings wacom configuration to work so that I can use the tablet as left-handed tablet. This is a showstopper for me and I need that working to do my job. Here are the commands I used. I am using stock digimend-dkms from Ubuntu repository, which seems to be up-to-date with digimend github: [17:01] [4853] [patola@trololo /tmp]% xsetwacom --list devices [17:01] [4854] [patola@trololo /tmp]% /usr/bin/libwacom-list-local-devices [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [Device] Name=Huion H610 Pro DeviceMatch=usb:256c:006e:HUION PenTablet Pen;usb:256c:006e:HUION PenTablet Pad; Class=Bamboo Width=10 Height=6 IntegratedIn= Layout=huion-h610-pro.svg Styli=0xd; [Features] Reversible=true Stylus=true Ring=false Ring2=false Touch=false TouchSwitch=false StatusLEDs= NumStrips=0 Buttons=8 [Buttons] Left=A;B;C;D;E;F;G;H; Right= Top= Bottom= Touchstrip= Touchstrip2= OLEDs= Ring= Ring2= RingNumModes=0 Ring2NumModes=0 StripsNumModes=0 --- [17:01] [4855] [patola@trololo /tmp]% dpkg -l | grep digimend ii digimend-dkms 6 all A collection of graphics tablet drivers by DIGImend project [17:04] [4856] [patola@trololo /tmp]% xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB USB Keykoard id=9[slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouseid=10 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pad id=11 [slave pointer (2)] ⎜ ↳ HUION PenTablet Pen id=12 [slave pointer (2)] ⎜ ↳ HUION PenTablet Mouse id=13 [slave pointer (2)] ⎜ ↳ HUION PenTablet Consumer Control id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ USB USB Keykoard id=8[slave keyboard (3)] ↳ HUION PenTablet System Controlid=14 [slave keyboard (3)] ↳ HUION PenTablet Keyboard id=15 [slave keyboard (3)] [17:04] [4857] [patola@trololo /tmp]% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1562387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1068994] Re: button1 gets stuck after a while
On Thu, Apr 18, 2013 at 6:04 AM, Till Kamppeter <1068...@bugs.launchpad.net>wrote: > Test tarball from comment #78 updated. > > ** Attachment added: "xorg-server_1.13.3-0ubuntu7~ppa1_armhf.tar.bz2" > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1068994/+attachment/3647306/+files/xorg-server_1.13.3-0ubuntu7%7Eppa1_armhf.tar.bz2 > Right click bug still there... (installed the new xserver debs and rebooted) -- Cláudio "Patola" Sampaio IRC: ptl - Yahoo: patolaaa Campinas, SP - Brazil. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the "button" appears to be stuck "down". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1068994] Re: button1 gets stuck after a while
On Thu, Apr 18, 2013 at 5:07 AM, Till Kamppeter <1068...@bugs.launchpad.net>wrote: > Yes, I can reproduce this, using the right-click emulator of onboard > makes the touch clicking fail. Probably I did not see this earlier as I > Yeah... I was also able to replicate it, whenever I use the right-mouse from onboard the mouse click gets lost. But since you fixed the left-click bug, why are you so pessimistic about this other bug? Wouldn't the same modifications be doable with this one? Best regards, -- Cláudio "Patola" Sampaio IRC: ptl - Yahoo: patolaaa Campinas, SP - Brazil. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the "button" appears to be stuck "down". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1068994] Re: button1 gets stuck after a while
On Wed, Apr 17, 2013 at 7:48 AM, Till Kamppeter <1068...@bugs.launchpad.net>wrote: > Unfortunately, the PPA does not build packages for the Nexus 7 (armhf > platform). Therefore I attach a patch with the binary .deb packages > which I have built and tested on my Nexus 7. I did not see the problem > occur with them, so they most probably fix this bug. > (...) > > ** Attachment added: "xserver-xorg_1.13.3-0ubuntu5_armhf.tar.bz2" > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1068994/+attachment/3646422/+files/xserver-xorg_1.13.3-0ubuntu5_armhf.tar.bz2 > FINALLY!! It is working, I've spent about 20 minutes trying to make it stop working to no avail. So, your patch seems to have resolved the problem. Congratulations, I don't think I should tell you how important is this bug... Thank you very much! For me, it will make the difference between playing for a few seconds and actually using desktop ubuntu on a tablet. Thank you again! Best regards, -- Cláudio "Patola" Sampaio IRC: ptl - Yahoo: patolaaa Campinas, SP - Brazil. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the "button" appears to be stuck "down". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1068994] Re: button1 gets stuck after a while
On Wed, Apr 17, 2013 at 6:15 AM, Till Kamppeter <1068...@bugs.launchpad.net>wrote: > I have built xorg-server with my patch also on the Nexus7 now and it > works perfectly there with the desktop and all applications, too, and on > the Nexu7 XBMC and Chromium's web apps work with touch. > > It also seems to fix the Nexus 7. > Do you have the .deb so others can test it? Thanks! -- Cláudio "Patola" Sampaio IRC: ptl - Yahoo: patolaaa Campinas, SP - Brazil. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the "button" appears to be stuck "down". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 991347] Re: After upgrade to 12.04 resolvconf seems ok but does not work
== OUTPUT OF dig @200.212.223.43 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @200.212.223.43 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached == == OUTPUT OF dig @8.8.8.8 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @8.8.8.8 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4509 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.terra.com.br. IN A ;; ANSWER SECTION: www.terra.com.br. 345 IN A 200.154.56.80 ;; Query time: 142 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Mon Apr 30 07:46:49 2012 ;; MSG SIZE rcvd: 50 == == OUTPUT OF dig @8.8.4.4 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @8.8.4.4 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39943 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.terra.com.br. IN A ;; ANSWER SECTION: www.terra.com.br. 345 IN A 200.154.56.80 ;; Query time: 145 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Mon Apr 30 07:46:49 2012 ;; MSG SIZE rcvd: 50 == == OUTPUT OF dig @200.212.223.044 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @200.212.223.044 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached == == OUTPUT OF dig @208.53.170.32 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @208.53.170.32 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached == == OUTPUT OF dig @200.212.223.100 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @200.212.223.100 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached == == OUTPUT OF dig @143.106.2.5 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @143.106.2.5 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached == == OUTPUT OF dig @200.162.192.51 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @200.162.192.51 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31137 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 6 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;www.terra.com.br. IN A ;; AUTHORITY SECTION: terra.com.br. 11171 IN NS d.dns.terra.com.br. terra.com.br. 11171 IN NS b.dns.terra.com.br. terra.com.br. 11171 IN NS a.dns.terra.com. terra.com.br. 11171 IN NS c.dns.terra.com. ;; ADDITIONAL SECTION: d.dns.terra.com.br. 10144 IN A 200.215.194.1 d.dns.terra.com.br. 10144 IN 2001:12c0:0:2151:200:154:46:21 b.dns.terra.com.br. 10144 IN A 200.215.193.1 b.dns.terra.com.br. 10144 IN 2001:12c0:0:2151:200:154:46:20 a.dns.terra.com.96545 IN A 200.215.193.1 c.dns.terra.com.96545 IN A 200.215.194.1 ;; Query time: 15 msec ;; SERVER: 200.162.192.51#53(200.162.192.51) ;; WHEN: Mon Apr 30 07:47:49 2012 ;; MSG SIZE rcvd: 235 == == OUTPUT OF dig @200.162.192.50 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @200.162.192.50 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 8237 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;www.terra.com.br. IN A ;; Query time: 16 msec ;; SERVER: 200.162.192.50#53(200.162.192.50) ;; WHEN: Mon Apr 30 07:47:49 2012 ;; MSG SIZE rcvd: 34 == == OUTPUT OF dig @200.162.192.49 www.terra.com.br == ; <<>> DiG 9.8.1-P1 <<>> @200.162.192.49 www.terra.com.br ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached == =
[Desktop-packages] [Bug 991347] Re: After upgrade to 12.04 resolvconf seems ok but does not work
About the last comment: I do not understand very well what's going on. Here's what I did: * Before looking at these comments, I removed all wired connections from network manager configuration. I rebooted the server and the resulting resolv.conf was not referencing 127.0.0.1 anymore, but the DNS servers from dhcp directly; I re-added a wired connection from the main adapter (eth0) with DHCP and the same stuff happened. * After that I noticed that the dnsmasq package wasn't installed. I forgot to add the line from ps -ef that showed that dnsmasq was running as a child process from NetworkManager (I even remember the --no-hosts parameter) even without the dnsmasq package being there * I installed dnsmasq just to see what would happen, and the resolv.conf referencing 127.0.0.1 became active again, and again, it does not work if I configure my DHCP server to lend it many servers. However, if I tested with one DNS server and four DNS servers, and both worked OK. * This "new" dnsmasq process is not a child from NetworkManager and does not have the file /var/run/nm-dns-dnsmasq.conf - what is going on, does Networkmanager has a different dnsmasq that comes with it? * As you can see, before this day I only had dnsmasq-base and not dnsmasq installed: [patola@bmw patola]% grep dnsmasq /var/log/dpkg.log 2012-04-06 09:05:34 upgrade dnsmasq-base 2.57-1ubuntu1 2.59-4 2012-04-06 09:05:34 status half-configured dnsmasq-base 2.57-1ubuntu1 2012-04-06 09:05:36 status unpacked dnsmasq-base 2.57-1ubuntu1 2012-04-06 09:05:37 status half-installed dnsmasq-base 2.57-1ubuntu1 2012-04-06 09:05:39 status half-installed dnsmasq-base 2.57-1ubuntu1 2012-04-06 09:05:41 status half-installed dnsmasq-base 2.57-1ubuntu1 2012-04-06 09:05:45 status unpacked dnsmasq-base 2.59-4 2012-04-06 09:05:45 status unpacked dnsmasq-base 2.59-4 2012-04-07 02:19:55 configure dnsmasq-base 2.59-4 2.59-4 2012-04-07 02:19:55 status unpacked dnsmasq-base 2.59-4 2012-04-07 02:19:56 status half-configured dnsmasq-base 2.59-4 2012-04-07 02:19:57 status installed dnsmasq-base 2.59-4 2012-04-30 01:24:28 install dnsmasq 2.59-4 2012-04-30 01:24:28 status half-installed dnsmasq 2.59-4 2012-04-30 01:24:29 status half-installed dnsmasq 2.59-4 2012-04-30 01:24:31 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:32 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:33 configure dnsmasq 2.59-4 2012-04-30 01:24:33 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:33 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:34 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:34 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:34 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:34 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:34 status unpacked dnsmasq 2.59-4 2012-04-30 01:24:34 status half-configured dnsmasq 2.59-4 2012-04-30 01:24:37 status installed dnsmasq 2.59-4 * I have a central server on my intranet that also does DNS resolution and caching. Is dnsmasq really needed on this scenario? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/991347 Title: After upgrade to 12.04 resolvconf seems ok but does not work Status in “network-manager” package in Ubuntu: Incomplete Bug description: I was using a simple scheme for DNS resolution before upgrading from 11.10 to 12.04: there are three interfaces on the computer, eth0 is the main one, acquires IP and DNS automatically from 10.0.0.1, which is also the default route. But after upgrade to the new DNS scheme on ubuntu 12.04, it does not work. Everything seems in order: /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp --- /etc/resolv.conf (link to ../run/resolvconf/resolv.conf): -- # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search patola.org - /var/run/nm-dns-dnsmasq.conf: -- server=200.212.223.43 server=8.8.8.8 server=8.8.4.4 server=200.212.223.44 server=208.53.170.32 server=200.212.223.100 server=143.106.2.5 server=200.162.192.51 server=200.162.192.50 server=200.162.192.49 server=200.162.192.52 - under /etc/resolvconf/resolv.conf.d: base - null, 0 bytes head: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN -- original: --- # Generated by NetworkManager domain patol
[Desktop-packages] [Bug 991347] Re: After upgrade to 12.04 resolvconf seems ok but does not work
Stéphane, I will wait from a response from Steve before posting all these digs, ok? Or do you still want me to try using all these dns servers so that DNS resolution does not work again and digging on all? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/991347 Title: After upgrade to 12.04 resolvconf seems ok but does not work Status in “network-manager” package in Ubuntu: Incomplete Bug description: I was using a simple scheme for DNS resolution before upgrading from 11.10 to 12.04: there are three interfaces on the computer, eth0 is the main one, acquires IP and DNS automatically from 10.0.0.1, which is also the default route. But after upgrade to the new DNS scheme on ubuntu 12.04, it does not work. Everything seems in order: /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp --- /etc/resolv.conf (link to ../run/resolvconf/resolv.conf): -- # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search patola.org - /var/run/nm-dns-dnsmasq.conf: -- server=200.212.223.43 server=8.8.8.8 server=8.8.4.4 server=200.212.223.44 server=208.53.170.32 server=200.212.223.100 server=143.106.2.5 server=200.162.192.51 server=200.162.192.50 server=200.162.192.49 server=200.162.192.52 - under /etc/resolvconf/resolv.conf.d: base - null, 0 bytes head: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN -- original: --- # Generated by NetworkManager domain patola.org search patola.org nameserver 200.212.223.43 nameserver 8.8.8.8 nameserver 8.8.4.4 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 200.212.223.44 nameserver 208.53.170.32 nameserver 200.212.223.100 nameserver 143.106.2.5 nameserver 200.162.192.51 nameserver 200.162.192.50 nameserver 200.162.192.49 nameserver 200.162.192.52 - In other words, all these server are the right ones, however, when I try to do a DNS query, it goes like that: [root@bmw ~]# dig www.terra.com.br ; <<>> DiG 9.8.1-P1 <<>> www.terra.com.br ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53771 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 6 ;; QUESTION SECTION: ;www.terra.com.br.IN A ;; AUTHORITY SECTION: terra.com.br. 71303 IN NS d.dns.terra.com.br. terra.com.br. 71303 IN NS b.dns.terra.com.br. terra.com.br. 71303 IN NS a.dns.terra.com. terra.com.br. 71303 IN NS c.dns.terra.com. ;; ADDITIONAL SECTION: d.dns.terra.com.br. 70276 IN A 200.215.194.1 d.dns.terra.com.br. 70276 IN 2001:12c0:0:2151:200:154:46:21 b.dns.terra.com.br. 70276 IN A 200.215.193.1 b.dns.terra.com.br. 70276 IN 2001:12c0:0:2151:200:154:46:20 a.dns.terra.com. 156677 IN A 200.215.193.1 c.dns.terra.com. 156677 IN A 200.215.194.1 ;; Query time: 17 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun Apr 29 15:05:37 2012 ;; MSG SIZE rcvd: 235 In other words, it returns a null response!!! No address! As soon as I change 127.0.0.1 on /etc/resolv.conf to a real DNS server, it works again. But of course, when configured this way it never uses dnsmasq. Why has the conversion not worked? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: resolvconf 1.63ubuntu11 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu6 Architecture: amd64 Date: Sun Apr 29 14:46:00 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to precise on 2012-04-06 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/991347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~deskt
[Desktop-packages] [Bug 991347] Re: After upgrade to 12.04 resolvconf seems ok but does not work
Steve Langasek, I do not have bind installed, but I have some packages named bind9-host, libbind9-60 and libbind9-80. They must not be interfering with dnsmasq, bind9-host doesn't even have an executable other than "host". Reducing the number of nameservers actually worked! I editted my dhcpd.conf on the DHCP server and made it use only "8.8.8.8" (google server). It resolves ok: [patola@bmw patola]% ls -la /etc/resolv.conf ; cat /etc/resolv.conf ; ping -c3 www.terra.com.br lrwxrwxrwx 1 root root 29 Abr 7 12:51 /etc/resolv.conf -> ../run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search patola.org PING www.terra.com.br (200.154.56.80) 56(84) bytes of data. 64 bytes from www.terra.com.br (200.154.56.80): icmp_req=1 ttl=247 time=54.4 ms 64 bytes from www.terra.com.br (200.154.56.80): icmp_req=2 ttl=247 time=31.1 ms 64 bytes from www.terra.com.br (200.154.56.80): icmp_req=3 ttl=247 time=29.9 ms --- www.terra.com.br ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 29.975/38.512/54.437/11.272 ms -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/991347 Title: After upgrade to 12.04 resolvconf seems ok but does not work Status in “network-manager” package in Ubuntu: Incomplete Bug description: I was using a simple scheme for DNS resolution before upgrading from 11.10 to 12.04: there are three interfaces on the computer, eth0 is the main one, acquires IP and DNS automatically from 10.0.0.1, which is also the default route. But after upgrade to the new DNS scheme on ubuntu 12.04, it does not work. Everything seems in order: /etc/network/interfaces: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp --- /etc/resolv.conf (link to ../run/resolvconf/resolv.conf): -- # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search patola.org - /var/run/nm-dns-dnsmasq.conf: -- server=200.212.223.43 server=8.8.8.8 server=8.8.4.4 server=200.212.223.44 server=208.53.170.32 server=200.212.223.100 server=143.106.2.5 server=200.162.192.51 server=200.162.192.50 server=200.162.192.49 server=200.162.192.52 - under /etc/resolvconf/resolv.conf.d: base - null, 0 bytes head: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN -- original: --- # Generated by NetworkManager domain patola.org search patola.org nameserver 200.212.223.43 nameserver 8.8.8.8 nameserver 8.8.4.4 # NOTE: the libc resolver may not support more than 3 nameservers. # The nameservers listed below may not be recognized. nameserver 200.212.223.44 nameserver 208.53.170.32 nameserver 200.212.223.100 nameserver 143.106.2.5 nameserver 200.162.192.51 nameserver 200.162.192.50 nameserver 200.162.192.49 nameserver 200.162.192.52 - In other words, all these server are the right ones, however, when I try to do a DNS query, it goes like that: [root@bmw ~]# dig www.terra.com.br ; <<>> DiG 9.8.1-P1 <<>> www.terra.com.br ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53771 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 6 ;; QUESTION SECTION: ;www.terra.com.br.IN A ;; AUTHORITY SECTION: terra.com.br. 71303 IN NS d.dns.terra.com.br. terra.com.br. 71303 IN NS b.dns.terra.com.br. terra.com.br. 71303 IN NS a.dns.terra.com. terra.com.br. 71303 IN NS c.dns.terra.com. ;; ADDITIONAL SECTION: d.dns.terra.com.br. 70276 IN A 200.215.194.1 d.dns.terra.com.br. 70276 IN 2001:12c0:0:2151:200:154:46:21 b.dns.terra.com.br. 70276 IN A 200.215.193.1 b.dns.terra.com.br. 70276 IN 2001:12c0:0:2151:200:154:46:20 a.dns.terra.com. 156677 IN A 200.215.193.1 c.dns.terra.com. 156677 IN A 200.215.194.1 ;; Query time: 17 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Sun
