[Desktop-packages] [Bug 1858200] Re: pulseaudio produces garbage on HDMI after 19.10
I was looking at the wrong beast. Upgrading kernel solved the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1858200 Title: pulseaudio produces garbage on HDMI after 19.10 Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 19.10, the sound output to HDMI is garbage. The sound is great on local output, on bluetooth headphones, etc. But when outputting to a HDMI TV it is garbage. I tried different users with the same problem. If I boot on Windows, the output is fine, which discards any physical problem, cables and TV as the source of the problem. I did delete any user pulseaudio configuration (and tried as a different one). I purged all system wide configuration and reinstalled the default pulseaudio configs with: apt-get -o DPkg::options::=--force-confmiss --reinstall install pulseaudio On 19.04 and before this problem did not happen at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raul 4850 F pulseaudio /dev/snd/controlC0: raul 4850 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 3 09:33:11 2020 InstallationDate: Installed on 2014-05-12 (2062 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216 mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858200/+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 1858200] [NEW] pulseaudio produces garbage on HDMI after 19.10
Public bug reported: After upgrading from 19.04 to 19.10, the sound output to HDMI is garbage. The sound is great on local output, on bluetooth headphones, etc. But when outputting to a HDMI TV it is garbage. I tried different users with the same problem. If I boot on Windows, the output is fine, which discards any physical problem, cables and TV as the source of the problem. I did delete any user pulseaudio configuration (and tried as a different one). I purged all system wide configuration and reinstalled the default pulseaudio configs with: apt-get -o DPkg::options::=--force-confmiss --reinstall install pulseaudio On 19.04 and before this problem did not happen at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raul 4850 F pulseaudio /dev/snd/controlC0: raul 4850 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 3 09:33:11 2020 InstallationDate: Installed on 2014-05-12 (2062 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216 mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1858200 Title: pulseaudio produces garbage on HDMI after 19.10 Status in pulseaudio package in Ubuntu: New Bug description: After upgrading from 19.04 to 19.10, the sound output to HDMI is garbage. The sound is great on local output, on bluetooth headphones, etc. But when outputting to a HDMI TV it is garbage. I tried different users with the same problem. If I boot on Windows, the output is fine, which discards any physical problem, cables and TV as the source of the problem. I did delete any user pulseaudio configuration (and tried as a different one). I purged all system wide configuration and reinstalled the default pulseaudio configs with: apt-get -o DPkg::options::=--force-confmiss --reinstall install pulseaudio On 19.04 and before this problem did not happen at all. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.4.5-050405-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: raul 4850 F pulseaudio /dev/snd/controlC0: raul 4850 F pulseaudio CurrentDesktop: KDE Date: Fri Jan 3 09:33:11 2020 InstallationDate: Installed on 2014-05-12 (2062 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.pulse.default.pa: [modified] modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-12-22T00:17:51.785216 mtime.conffile..etc.pulse.system.pa: 2019-12-22T00:16:08.693216 To manage
Re: [Desktop-packages] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1
Yes Em sex, 16 de nov de 2018 07:25, Daniel van Vugt < daniel.van.v...@canonical.com escreveu: > Is this bug still a problem in the latest updates to 18.04? > > ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) > > ** Also affects: gnome-shell (Ubuntu) >Importance: Undecided >Status: New > > ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) > > ** No longer affects: mutter (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1761773 > > Title: > Touch Screen stop working on 18.04 beta1 > > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > The touch screen on a HP TouchSmart works fine on other releases. > On the beta of 18.04 it stopped to work. > > Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen > > On 16.04 it is recognized as TOUCHSCREEN by X.org. > On 18.04 beta 1, it is recognized as mouse. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu5 > ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 > Uname: Linux 4.15.0-13-generic x86_64 > ApportVersion: 2.20.9-0ubuntu2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 6 11:39:07 2018 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] > InstallationDate: Installed on 2018-04-05 (0 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180327) > MachineType: HP-Pavilion FQ429AA-AC4 IQ510br > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic > root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/10/2008 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 5.06 > dmi.board.name: EVE > dmi.board.vendor: PEGATRON CORPORATION. > dmi.board.version: 1.04 > dmi.chassis.asset.tag: Asset-1234567890 > dmi.chassis.type: 3 > dmi.chassis.vendor: Hewlett-Packard > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: > dmi.product.family: 103C_53316J > dmi.product.name: FQ429AA-AC4 IQ510br > dmi.sys.vendor: HP-Pavilion > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.91-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1761773/+subscriptions > -- 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/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg-server package in Ubuntu: Incomplete Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType:
[Desktop-packages] [Bug 1793334] [NEW] Chromium does not pick default pulseaudio sink
Public bug reported: When changing the default sink (builtin audio) to USB audio (PCM2902) headphone, all desktop uses the new default sink. All but Chromium (and Chrome). For both Chromium (and Chrome), I have to change the output device in the application tab (PA). As soon as the audio pauses in Chrome/Chromium, it will resume in the builtin output audio device sink. This happens on a per tab basis (probably different process). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 19 11:54:57 2018 Desktop-Session: 'plasma' '/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/usr/share/plasma:/home/raul/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2014-05-12 (1591 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' Load-Avg-1min: 1.06 Load-Processes-Running-Percent: 0.1% MachineType: Notebook P870KM_KM1 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-34-generic root=UUID=ba6a2d10-738f-42dc-9b8a-e68c8cc5d368 ro rootflags=subvol=@ SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-27 (145 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/22/2017:svnNotebook:pnP870KM_KM1:pvrNotApplicable:rvnNotebook:rnP870KM_KM1:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P870KM_KM1 dmi.product.version: Not Applicable dmi.sys.vendor: Notebook etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (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 chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1793334 Title: Chromium does not pick default pulseaudio sink Status in chromium-browser package in Ubuntu: New Bug description: When changing the default sink (builtin audio) to USB audio (PCM2902) headphone, all desktop uses the new default sink. All but Chromium (and Chrome). For both Chromium (and Chrome), I have to change the output device in the application tab (PA). As soon as the audio pauses in Chrome/Chromium, it will resume in the builtin output audio device sink. This happens on a per tab basis (probably different process). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 69.0.3497.81-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 19 11:54:57 2018 Desktop-Session: 'plasma' '/etc/xdg/xdg-plasma:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' '/usr/share/plasma:/home/raul/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2014-05-12 (1591 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' Load-Avg-1min: 1.06 Load-Processes-Running-Percent: 0.1% MachineType: Notebook P870KM_KM1 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-34-generic root=UUID=ba6a2d10-738f-42dc-9b8a-e68c8cc5d368 ro rootflags=subvol=@ SourcePackage: chromium-browser UpgradeStatus: Upgraded to bionic on 2018-04-27 (145 days ago) dmi.bios.date: 02/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: P870KM_KM1 dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias:
[Desktop-packages] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1
I created inside /etc/x11/xorg.conf.d/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream
I have a lot of computers in my office that needs this drive to work. Neither Nouveau or VESA works with them. If this decision persists I will have to move to another distribution (which I hope to avoid). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1748000 Title: Remove from the archive: this legacy driver is unmaintained upstream Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Bug description: This driver branch is now dead upstream, so it should be removed from bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1748000/+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 1769969] [NEW] GDM3 does not start if SDDM is installed (18.04)
Public bug reported: After upgrading my office machines to 18.04, some machines did not start the GDM3. After some testing the problem was that the ones that it did not work, had SDDM installed too (KDE environment in those machines). The upgrade were from 17.10 and 16.04. Note that reistalling sddm, gdm3, lightdm, dpkg-reconfigure gdm3, none worked. On gdm3 side: systemctl is-active gdm3 reports static (which might be the problem). After removing sddm and rebooting, everything worked as expected. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1769969 Title: GDM3 does not start if SDDM is installed (18.04) Status in gdm3 package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: After upgrading my office machines to 18.04, some machines did not start the GDM3. After some testing the problem was that the ones that it did not work, had SDDM installed too (KDE environment in those machines). The upgrade were from 17.10 and 16.04. Note that reistalling sddm, gdm3, lightdm, dpkg-reconfigure gdm3, none worked. On gdm3 side: systemctl is-active gdm3 reports static (which might be the problem). After removing sddm and rebooting, everything worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1769969/+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 1761773] Re: Touch Screen stop working on 18.04 beta1
The simplest solution was to add the configuration: Section "InputClass" Identifier "NextWindows 1900 HID Touchscreen" MatchUSBID "1926:0003" Driver "evdev" EndSection -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1761773] Re: Touch Screen stop working on 18.04 beta1
Removing xserver-xorg-input-libinput did the tricky. Now it uses evdev. However, that shouldn't need be necessary. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1761773] Re: Touch Screen stop working on 18.04 beta1
The problem might also involve udev, as by these lines: [ 800.429] (II) event5 - NextWindow Touchscreen: is tagged by udev as: Tablet [ 800.429] (EE) event5 - NextWindow Touchscreen: libinput bug: missing tablet capabilities: btn-stylus resolution.Ignoring this device. [ 800.429] (II) event5 - NextWindow Touchscreen: device is a tablet [ 800.429] (II) event5 - failed to create input device '/dev/input/event5'. udev should recognize as TouchScreen, not Tablet. On previous Xorgs, evdev was used, not libinput. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1761773] Re: Touch Screen stop working on 18.04 beta1
Upgraded to beta 2 and the same issue continues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1761773] [NEW] Touch Screen stop working on 18.04 beta1
Public bug reported: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1761773] Re: Touch Screen stop working on 18.04 beta1
** Attachment added: "X.org logs from 16.04 (Install Media Try Ubuntu option) where it works" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+attachment/5104182/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1761773 Title: Touch Screen stop working on 18.04 beta1 Status in xorg package in Ubuntu: New Bug description: The touch screen on a HP TouchSmart works fine on other releases. On the beta of 18.04 it stopped to work. Bus 005 Device 002: ID 1926:0003 NextWindow 1900 HID Touchscreen On 16.04 it is recognized as TOUCHSCREEN by X.org. On 18.04 beta 1, it is recognized as mouse. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 6 11:39:07 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G98M [GeForce 9300M GS] [10de:06e9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron G98M [GeForce 9300M GS] [1b0a:9010] InstallationDate: Installed on 2018-04-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: HP-Pavilion FQ429AA-AC4 IQ510br ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=0c40330f-866b-42e4-a61d-3ca0daf9ee6f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.06 dmi.board.name: EVE dmi.board.vendor: PEGATRON CORPORATION. dmi.board.version: 1.04 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.06:bd07/10/2008:svnHP-Pavilion:pnFQ429AA-AC4IQ510br:pvr:rvnPEGATRONCORPORATION.:rnEVE:rvr1.04:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: FQ429AA-AC4 IQ510br dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761773/+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 1568339] Re: Libreoffice does not update printer list
Just did a full upgrade to 16.04. cups is 2.1.3-4 libreoffice is 1:5.1.2-0ubuntu1 (5.1.2.2) The scenario: 1 - Cups is my localhost: raul@nostromo:~$ cat /etc/cups/client.conf raul@nostromo:~$ lpstat -a EPSON_L355_Series accepting requests since Sáb 23 Abr 2016 17:22:15 BRT HP-LaserJet-1200 accepting requests since Sáb 02 Abr 2016 17:45:49 BRT Xerox_Phaser_3200MFP accepting requests since Sáb 05 Mar 2016 15:31:34 BRT The Libreoffice Printer Dialog is attached to comment #2. So far so good. 2 - Change client.conf to use a remote server: raul@nostromo:~$ cat /etc/cups/client.conf ServerName impressoras2 raul@nostromo:~$ lpstat -a CPD accepting requests since Seg 25 Abr 2016 08:06:59 BRT CPD-Cond accepting requests since Qua 26 Ago 2015 17:28:58 BRT CPD-Normal accepting requests since Qua 26 Ago 2015 17:36:20 BRT CPD-P-C-2 accepting requests since Qua 26 Ago 2015 17:39:08 BRT CPD-P-Cond accepting requests since Qua 26 Ago 2015 17:38:39 BRT CPD-P-Norm accepting requests since Qua 26 Ago 2015 17:37:30 BRT ECOMMERCE accepting requests since Seg 25 Abr 2016 08:00:07 BRT EPSON_LX-300-RAW accepting requests since Ter 12 Abr 2016 08:00:05 BRT HP_LaserJet_1200 accepting requests since Qui 10 Mar 2016 08:01:21 BRT LX-300-A accepting requests since Sex 16 Mai 2014 14:43:17 BRT LX-300-B accepting requests since Sex 16 Mai 2014 14:43:36 BRT Padrao accepting requests since Sex 16 Mai 2014 14:39:28 BRT saci accepting requests since Sex 22 Abr 2016 14:26:00 BRT Zebra accepting requests since Sex 16 Mai 2014 14:44:48 BRT The Libreoffice Printer Dialog is still the attached to comment #2. The printer list is not refreshed. Some libreoffice internal cache. 3 - Close every instance of libreoffice running and start it again. The Libreoffice Printer Dialog is the attached to comment #3. This is what was expected on step 2. This seems to be the same bug in https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235, except that it does not work in this situation. As I mentioned, this is present for many years now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1568339 Title: Libreoffice does not update printer list Status in libreoffice package in Ubuntu: Incomplete Bug description: When Libreoffice is started it reads the printer list and saves it. When there is a change related to cups (new printers) or change the cups server, libreoffice needs to be restarted (all insteances) to acknowledge the new printers. When I change offices, I need to update the /etc/cups/client.conf (or use a localhost cups server at home). If I have libreoffice open, it will not find any printer. This is a duplicated issue of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235 But that was focused on a specific printer model while the problem is more abroad. I have seen it from 12.04 to 15.10. Libreoffice 3.x to 5.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+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 1568339] Re: Libreoffice does not update printer list
I did some digging and the printer list is pulled when I first hit CONTROL-P (File->Print). So, if I change the client.conf before trying to use the printer, it will get the current list even after it has started up. It will not update any time later on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1568339 Title: Libreoffice does not update printer list Status in libreoffice package in Ubuntu: Incomplete Bug description: When Libreoffice is started it reads the printer list and saves it. When there is a change related to cups (new printers) or change the cups server, libreoffice needs to be restarted (all insteances) to acknowledge the new printers. When I change offices, I need to update the /etc/cups/client.conf (or use a localhost cups server at home). If I have libreoffice open, it will not find any printer. This is a duplicated issue of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235 But that was focused on a specific printer model while the problem is more abroad. I have seen it from 12.04 to 15.10. Libreoffice 3.x to 5.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+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 1568339] Re: Libreoffice does not update printer list
** Attachment added: "1-Libre Office Writer 5.1.2.2 on 16.04 Printer Dialog 1" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+attachment/4646398/+files/LO51-Printer_Dialog_1.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1568339 Title: Libreoffice does not update printer list Status in libreoffice package in Ubuntu: Incomplete Bug description: When Libreoffice is started it reads the printer list and saves it. When there is a change related to cups (new printers) or change the cups server, libreoffice needs to be restarted (all insteances) to acknowledge the new printers. When I change offices, I need to update the /etc/cups/client.conf (or use a localhost cups server at home). If I have libreoffice open, it will not find any printer. This is a duplicated issue of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235 But that was focused on a specific printer model while the problem is more abroad. I have seen it from 12.04 to 15.10. Libreoffice 3.x to 5.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+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 1568339] Re: Libreoffice does not update printer list
** Attachment added: "2-Libre Office Writer 5.1.2.2 on 16.04 Printer Dialog 2 - After LO Restart" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+attachment/4646405/+files/LO51-Printer_Dialog_2.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1568339 Title: Libreoffice does not update printer list Status in libreoffice package in Ubuntu: Incomplete Bug description: When Libreoffice is started it reads the printer list and saves it. When there is a change related to cups (new printers) or change the cups server, libreoffice needs to be restarted (all insteances) to acknowledge the new printers. When I change offices, I need to update the /etc/cups/client.conf (or use a localhost cups server at home). If I have libreoffice open, it will not find any printer. This is a duplicated issue of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235 But that was focused on a specific printer model while the problem is more abroad. I have seen it from 12.04 to 15.10. Libreoffice 3.x to 5.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+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 911235] Re: [Upstream] LibreOffice doesn't update printer list on netbook WiFi to router to ethernet to PC w/ cups server usb to HP OfficeJet Pro 8500
It still happens on 16.04. Please see bug https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/911235 Title: [Upstream] LibreOffice doesn't update printer list on netbook WiFi to router to ethernet to PC w/ cups server usb to HP OfficeJet Pro 8500 Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) Ubuntu 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installiert: 1:3.4.4-0ubuntu1 Kandidat: 1:3.4.4-0ubuntu1 Versionstabelle: *** 1:3.4.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen on a netbook WiFi connected to router to ethernet to PC hosting cups server USB connected to HP OfficeJet Pro 8500 is with the printer off, LibreOffice Writer running, is when one turns the printer on Writer immediately recognizes the printer is available to be printed to. 4) What happens instead is the printer is not available to be printed to. This occurs every time this is tested. However, Evince and Firefox can print to the printer with no problem. WORKAROUND: Turn on the printer, restart Writer. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Tue Jan 3 14:40:37 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-11-17 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/911235/+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 1568339] [NEW] Libreoffice does not update printer list
Public bug reported: When Libreoffice is started it reads the printer list and saves it. When there is a change related to cups (new printers) or change the cups server, libreoffice needs to be restarted (all insteances) to acknowledge the new printers. When I change offices, I need to update the /etc/cups/client.conf (or use a localhost cups server at home). If I have libreoffice open, it will not find any printer. This is a duplicated issue of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235 But that was focused on a specific printer model while the problem is more abroad. I have seen it from 12.04 to 15.10. Libreoffice 3.x to 5.x ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1568339 Title: Libreoffice does not update printer list Status in libreoffice package in Ubuntu: New Bug description: When Libreoffice is started it reads the printer list and saves it. When there is a change related to cups (new printers) or change the cups server, libreoffice needs to be restarted (all insteances) to acknowledge the new printers. When I change offices, I need to update the /etc/cups/client.conf (or use a localhost cups server at home). If I have libreoffice open, it will not find any printer. This is a duplicated issue of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/911235 But that was focused on a specific printer model while the problem is more abroad. I have seen it from 12.04 to 15.10. Libreoffice 3.x to 5.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1568339/+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 911235] Re: [Upstream] LibreOffice doesn't update printer list on netbook WiFi to router to ethernet to PC w/ cups server usb to HP OfficeJet Pro 8500
This still happens on 15.10 and libreoffice 5.x up to today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/911235 Title: [Upstream] LibreOffice doesn't update printer list on netbook WiFi to router to ethernet to PC w/ cups server usb to HP OfficeJet Pro 8500 Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) Ubuntu 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installiert: 1:3.4.4-0ubuntu1 Kandidat: 1:3.4.4-0ubuntu1 Versionstabelle: *** 1:3.4.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen on a netbook WiFi connected to router to ethernet to PC hosting cups server USB connected to HP OfficeJet Pro 8500 is with the printer off, LibreOffice Writer running, is when one turns the printer on Writer immediately recognizes the printer is available to be printed to. 4) What happens instead is the printer is not available to be printed to. This occurs every time this is tested. However, Evince and Firefox can print to the printer with no problem. WORKAROUND: Turn on the printer, restart Writer. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Tue Jan 3 14:40:37 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-11-17 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/911235/+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 1336005] [NEW] akonadi-server too dependent on MySQL and prevent percona instalation
Public bug reported: There are a few serious packaging problems with akonadi: 1 - akonadi-server depends on akonadi-backend-mysql. It can also work with postgresql and sqllite, but mysql is mandatory, it should be optional. 2 - akonadi-backend depends on either mysql-server-core-5.5 or mariadb- server-core-5.5 2.1 - depending on a specific version of mysql is very bad. If there is a need for a feature on 5.5, it should be something like: mysql-server-core = 5.5. As 5.6 has all feature of 5.5, it still cannot be installed. The same goes to the clients too. 2.2 - the percona-server-(server|client) should be added to the mix. PPA: http://www.percona.com/doc/percona-server/5.5/installation/apt_repo.html Basically the choice is either use mysql|mariadb 5.5 or no kde. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: akonadi-server 1.12.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 30 16:56:55 2014 InstallationDate: Installed on 2014-05-12 (49 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: akonadi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: akonadi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1336005 Title: akonadi-server too dependent on MySQL and prevent percona instalation Status in “akonadi” package in Ubuntu: New Bug description: There are a few serious packaging problems with akonadi: 1 - akonadi-server depends on akonadi-backend-mysql. It can also work with postgresql and sqllite, but mysql is mandatory, it should be optional. 2 - akonadi-backend depends on either mysql-server-core-5.5 or mariadb-server-core-5.5 2.1 - depending on a specific version of mysql is very bad. If there is a need for a feature on 5.5, it should be something like: mysql-server-core = 5.5. As 5.6 has all feature of 5.5, it still cannot be installed. The same goes to the clients too. 2.2 - the percona-server-(server|client) should be added to the mix. PPA: http://www.percona.com/doc/percona-server/5.5/installation/apt_repo.html Basically the choice is either use mysql|mariadb 5.5 or no kde. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: akonadi-server 1.12.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jun 30 16:56:55 2014 InstallationDate: Installed on 2014-05-12 (49 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: akonadi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1336005/+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 1247528] Re: Build and distribute intel-virtual-output
This tool is very important and it is already built, but not packaged: http://askubuntu.com/questions/380844/intel-virtual-output-command-for-saucy-13-10-with-dual-monitor-setup-and-hybrid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1247528 Title: Build and distribute intel-virtual-output Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: xserver-xorg-video-intel 2.99.904 adds support for virtual displays that can be used to clone to discrete outputs. The tool to do this is included with the xserver-xorg-video-intel source (with not-so-great man page and all), but the binary is currently not shipped by Ubuntu. The tool will allocate a virtual output for the specified outputs on a different X server (or for all outputs with the -a parameter). It will also copy over resolution information etc from xrandr. You can then use your desktop environment's display tool to configure these external displays the way you would normally do in a non-hybrid situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1247528/+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 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging
Same here. The problem is related to Oxygen indeed. (as #7 pointed) Changing the gtk theme to something else solved the problem. Happened with: oracle's java 6,7,8 and openjdk 7. Tested on all version of ApacheDS (Directory Studio) from 1.5 to 2.0. -rsd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: to reproduce, I open the Variables view in eclipse and step through the application. the eclipse jvm crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2202aa] gtk_tree_view_get_background_area+0x8a # # Core dump written. Default location: /home/juergen/core or core.11567 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid11567.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # This did not happen in ubuntu 13.04. using KDE as a desktop (installed ubuntu, installed kde packages) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 10 07:25:17 2013 InstallationDate: Installed on 2010-11-24 (1020 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1223181/+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 1094973] [NEW] udev + usb_modeswitch fails if modem is on USB 3
Public bug reported: If I plug my modem on a USB 3 instead of a USB 2 it fails to do the switch. It will work fine if I: 1 - extract /usr/share/usb_modeswitch/configPack.tar.gz from usb-modeswitch-data to /etc/usb_modeswitch.d/ 2 - run the command: sudo usb_modeswitch -v 19d2 -p 2000 -s 10 -I -c /etc/usb_modeswitch.d/19d2\:2000 (btw: why are these configs tared in -data?!?) If I plug directly on a USB 2 udev works out of the box. 12.10 64bits - 3.5.0-21-generic On a Dell XPS L502X. lspci -vv attached, more info below. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: usb-modeswitch 1.2.3+repack0-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Dec 31 23:33:00 2012 InstallationDate: Installed on 2012-12-26 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: usb-modeswitch UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ** Attachment added: lspci -vv https://bugs.launchpad.net/bugs/1094973/+attachment/3471639/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1094973 Title: udev + usb_modeswitch fails if modem is on USB 3 Status in “usb-modeswitch” package in Ubuntu: New Bug description: If I plug my modem on a USB 3 instead of a USB 2 it fails to do the switch. It will work fine if I: 1 - extract /usr/share/usb_modeswitch/configPack.tar.gz from usb-modeswitch-data to /etc/usb_modeswitch.d/ 2 - run the command: sudo usb_modeswitch -v 19d2 -p 2000 -s 10 -I -c /etc/usb_modeswitch.d/19d2\:2000 (btw: why are these configs tared in -data?!?) If I plug directly on a USB 2 udev works out of the box. 12.10 64bits - 3.5.0-21-generic On a Dell XPS L502X. lspci -vv attached, more info below. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: usb-modeswitch 1.2.3+repack0-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Dec 31 23:33:00 2012 InstallationDate: Installed on 2012-12-26 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: usb-modeswitch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1094973/+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 1094973] Re: udev + usb_modeswitch fails if modem is on USB 3
This is the kernel log on a USB 3: usb 3-2: new high-speed USB device number 21 using xhci_hcd usb 3-2: New USB device found, idVendor=19d2, idProduct=2000 usb 3-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 usb 3-2: Product: ONDA CDMA Technologies MSM usb 3-2: Manufacturer: ONDA,Incorporated usb 3-2: SerialNumber: 1234567890ABCDEF usb 3-2: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes usb 3-2: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes scsi47 : usb-storage 3-2:1.0 scsi 47:0:0:0: CD-ROM ONDA USB SCSI CD-ROM USB PQ: 0 ANSI: 2 sr1: scsi-1 drive sr 47:0:0:0: Attached scsi CD-ROM sr1 sr 47:0:0:0: Attached scsi generic sg2 type 5 And this is on a USB2: usb 2-1.2: new high-speed USB device number 19 using ehci_hcd usb 2-1.2: New USB device found, idVendor=19d2, idProduct=2000 usb 2-1.2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 usb 2-1.2: Product: ONDA CDMA Technologies MSM usb 2-1.2: Manufacturer: ONDA,Incorporated usb 2-1.2: SerialNumber: 1234567890ABCDEF scsi44 : usb-storage 2-1.2:1.0 scsi 44:0:0:0: CD-ROM ONDA USB SCSI CD-ROM USB PQ: 0 ANSI: 2 sr1: scsi-1 drive sr 44:0:0:0: Attached scsi CD-ROM sr1 sr 44:0:0:0: Attached scsi generic sg2 type 5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1094973 Title: udev + usb_modeswitch fails if modem is on USB 3 Status in “usb-modeswitch” package in Ubuntu: New Bug description: If I plug my modem on a USB 3 instead of a USB 2 it fails to do the switch. It will work fine if I: 1 - extract /usr/share/usb_modeswitch/configPack.tar.gz from usb-modeswitch-data to /etc/usb_modeswitch.d/ 2 - run the command: sudo usb_modeswitch -v 19d2 -p 2000 -s 10 -I -c /etc/usb_modeswitch.d/19d2\:2000 (btw: why are these configs tared in -data?!?) If I plug directly on a USB 2 udev works out of the box. 12.10 64bits - 3.5.0-21-generic On a Dell XPS L502X. lspci -vv attached, more info below. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: usb-modeswitch 1.2.3+repack0-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Dec 31 23:33:00 2012 InstallationDate: Installed on 2012-12-26 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: usb-modeswitch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1094973/+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 1094973] Re: udev + usb_modeswitch fails if modem is on USB 3
This is the lsusb -v for the modem on the USB3 before usb_modeswitch: -- 8 --- Bus 003 Device 021: ID 19d2:2000 ZTE WCDMA Technologies MSM MF627/MF628/MF628+/MF636+ HSDPA/HSUPA Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x19d2 ZTE WCDMA Technologies MSM idProduct 0x2000 MF627/MF628/MF628+/MF636+ HSDPA/HSUPA bcdDevice0.00 iManufacturer 3 ONDA,Incorporated iProduct2 ONDA CDMA Technologies MSM iSerial 4 1234567890ABCDEF bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) - 8 -- This is the output after modemswitch (sucessfully): -- 8 --- Bus 003 Device 026: ID 19d2:0037 ZTE WCDMA Technologies MSM Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x19d2 ZTE WCDMA Technologies MSM idProduct 0x0037 bcdDevice0.00 iManufacturer 3 ONDA,Incorporated iProduct2 ONDA CDMA Technologies MSM iSerial 4 1234567890ABCDEF bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes
[Desktop-packages] [Bug 1094973] Re: udev + usb_modeswitch fails if modem is on USB 3
This are the lsbusb on the USB 2 before and after udev/usb_modeswitch: Bus 002 Device 019: ID 19d2:2000 ZTE WCDMA Technologies MSM MF627/MF628/MF628+/MF636+ HSDPA/HSUPA Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x19d2 ZTE WCDMA Technologies MSM idProduct 0x2000 MF627/MF628/MF628+/MF636+ HSDPA/HSUPA bcdDevice0.00 iManufacturer 3 ONDA,Incorporated iProduct2 ONDA CDMA Technologies MSM iSerial 4 1234567890ABCDEF bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Device Qualifier (for other device speed): bLength10 bDescriptorType 6 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 bNumConfigurations 1 Device Status: 0x (Bus Powered) --- 8 --- Bus 002 Device 020: ID 19d2:0037 ZTE WCDMA Technologies MSM Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x19d2 ZTE WCDMA Technologies MSM idProduct 0x0037 bcdDevice0.00 iManufacturer 3 ONDA,Incorporated iProduct2 ONDA CDMA Technologies MSM iSerial 4 1234567890ABCDEF bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 108 bNumInterfaces 4 bConfigurationValue 1 iConfiguration 1 ZTE Configuration bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 32 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol
[Desktop-packages] [Bug 1094973] Re: udev + usb_modeswitch fails if modem is on USB 3
This is the usb_modeswitch output on the USB 3: $ sudo usb_modeswitch -v 19d2 -p 2000 -s 10 -I -c /etc/usb_modemswitch.d/19d2\:2000 -W * usb_modeswitch: handle USB devices with multiple modes * Version 1.2.3 (C) Josua Dietze 2012 * Based on libusb0 (0.1.12 and above) ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x19d2 DefaultProduct= 0x2000 TargetVendor= 0x19d2 TargetProduct= not set TargetClass=not set TargetProductList=0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0066,0091,0108,0117,0128,0157,1402,2002,2003 DetachStorageOnly=0 HuaweiMode=0 SierraMode=0 SonyMode=0 QisdaMode=0 GCTMode=0 KobilMode=0 SequansMode=0 MobileActionMode=0 CiscoMode=0 MessageEndpoint= not set MessageContent=5553424312345678061e00 MessageContent2=5553424312345679061b000200 MessageContent3=555342431234567020008c85010101180101010101 NeedResponse=1 ResponseEndpoint= not set InquireDevice disabled Success check enabled, max. wait time 10 seconds System integration mode disabled usb_set_debug: Setting debugging level to 15 (on) usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 004 skipping descriptor 0x30 skipped 1 class/vendor specific endpoint descriptors usb_os_find_devices: Found 025 on 003 usb_os_find_devices: Found 002 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 004 on 002 usb_os_find_devices: Found 002 on 002 usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 003 on 001 skipping descriptor 0xFF skipping descriptor 0xB skipped 2 class/vendor specific endpoint descriptors skipped 7 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 28 class/vendor specific interface descriptors skipped 2 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device Looking for target devices ... searching devices, found USB ID 1d6b:0003 searching devices, found USB ID 19d2:2000 found matching vendor ID searching devices, found USB ID 045e:074f searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 8086:0189 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 0408:2fb1 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 No devices in target mode or class found Looking for default devices ... searching devices, found USB ID 1d6b:0003 searching devices, found USB ID 19d2:2000 found matching vendor ID found matching product ID adding device searching devices, found USB ID 045e:074f searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 8086:0189 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 0408:2fb1 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 Found device in default mode, class or configuration (1) Accessing device 025 on bus 003 ... Getting the current device configuration ... OK, got current device configuration (1) Using first interface: 0x00 Using endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) - Manufacturer: ONDA,Incorporated Product: ONDA CDMA Technologies MSM Serial No.: 1234567890ABCDEF - Looking for active driver ... OK, driver found (usbfs) OK, driver usbfs detached Setting up communication with interface 0 Check that you have permissions to write to 003/025 and, if you don't, that you set up hotplug (http://linux-hotplug.sourceforge.net/) correctly. USB error: could not claim interface 0: Device or resource busy Could not claim interface (error -16). Skipping message sending Checking for mode switch (max. 10 times, once per second) ... Searching for target devices ... usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 004 skipping descriptor 0x30 skipped 1 class/vendor specific endpoint descriptors usb_os_find_devices: Found 002 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 004 on 002 usb_os_find_devices: Found 002 on 002 usb_os_find_devices: Found 001 on 002 error obtaining child
[Desktop-packages] [Bug 1094973] Re: udev + usb_modeswitch fails if modem is on USB 3
Finally, this is the same usb_modeswitch, but now on the USB2 (without udev, for comparison): * usb_modeswitch: handle USB devices with multiple modes * Version 1.2.3 (C) Josua Dietze 2012 * Based on libusb0 (0.1.12 and above) ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x19d2 DefaultProduct= 0x2000 TargetVendor= 0x19d2 TargetProduct= not set TargetClass=not set TargetProductList=0001,0002,0015,0016,0017,0031,0037,0052,0055,0063,0064,0066,0091,0108,0117,0128,0157,1402,2002,2003 DetachStorageOnly=0 HuaweiMode=0 SierraMode=0 SonyMode=0 QisdaMode=0 GCTMode=0 KobilMode=0 SequansMode=0 MobileActionMode=0 CiscoMode=0 MessageEndpoint= not set MessageContent=5553424312345678061e00 MessageContent2=5553424312345679061b000200 MessageContent3=555342431234567020008c85010101180101010101 NeedResponse=1 ResponseEndpoint= not set InquireDevice disabled Success check enabled, max. wait time 10 seconds System integration mode disabled usb_set_debug: Setting debugging level to 15 (on) usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_devices: Found 001 on 004 skipping descriptor 0x30 skipped 1 class/vendor specific endpoint descriptors usb_os_find_devices: Found 002 on 003 skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 003 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 019 on 002 usb_os_find_devices: Found 004 on 002 usb_os_find_devices: Found 002 on 002 usb_os_find_devices: Found 001 on 002 error obtaining child information: Inappropriate ioctl for device error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 003 on 001 skipping descriptor 0xFF skipping descriptor 0xB skipped 2 class/vendor specific endpoint descriptors skipped 7 class/vendor specific interface descriptors skipping descriptor 0x25 skipped 1 class/vendor specific endpoint descriptors skipped 28 class/vendor specific interface descriptors skipped 2 class/vendor specific interface descriptors usb_os_find_devices: Found 002 on 001 usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device Looking for target devices ... searching devices, found USB ID 1d6b:0003 searching devices, found USB ID 045e:074f searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 19d2:2000 found matching vendor ID searching devices, found USB ID 8086:0189 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 0408:2fb1 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 No devices in target mode or class found Looking for default devices ... searching devices, found USB ID 1d6b:0003 searching devices, found USB ID 045e:074f searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 19d2:2000 found matching vendor ID found matching product ID adding device searching devices, found USB ID 8086:0189 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 searching devices, found USB ID 0408:2fb1 searching devices, found USB ID 8087:0024 searching devices, found USB ID 1d6b:0002 Found device in default mode, class or configuration (1) Accessing device 019 on bus 002 ... Getting the current device configuration ... OK, got current device configuration (1) Using first interface: 0x00 Using endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) - Manufacturer: ONDA,Incorporated Product: ONDA CDMA Technologies MSM Serial No.: 1234567890ABCDEF - Looking for active driver ... OK, driver found (usb-storage) OK, driver usb-storage detached Setting up communication with interface 0 Using endpoint 0x01 for message sending ... Trying to send message 1 to endpoint 0x01 ... OK, message successfully sent Reading the response to message 1 (CSW) ... OK, response successfully read (13 bytes). Trying to send message 2 to endpoint 0x01 ... OK, message successfully sent Reading the response to message 2 (CSW) ... OK, response successfully read (13 bytes). Trying to send message 3 to endpoint 0x01 ... OK, message successfully sent Reading the response to message 3 (CSW) ... OK, response successfully read (0 bytes). Resetting response endpoint 0x81 USB error: could not clear/halt ep 129: Protocol error Could not reset endpoint (probably harmless): -71 Resetting message endpoint 0x01 USB error: could not clear/halt ep 1: Protocol error Could not reset endpoint (probably harmless): -71 USB error: could not release intf 0: No such device Device is gone, skipping any further commands Checking for mode switch (max. 10 times, once per second) ...
[Desktop-packages] [Bug 1094973] Re: udev + usb_modeswitch fails if modem is on USB 3
This is a dup of 979697 using options usb-storage delay_use=3 solves the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1094973 Title: udev + usb_modeswitch fails if modem is on USB 3 Status in “usb-modeswitch” package in Ubuntu: New Bug description: If I plug my modem on a USB 3 instead of a USB 2 it fails to do the switch. It will work fine if I: 1 - extract /usr/share/usb_modeswitch/configPack.tar.gz from usb-modeswitch-data to /etc/usb_modeswitch.d/ 2 - run the command: sudo usb_modeswitch -v 19d2 -p 2000 -s 10 -I -c /etc/usb_modeswitch.d/19d2\:2000 (btw: why are these configs tared in -data?!?) If I plug directly on a USB 2 udev works out of the box. 12.10 64bits - 3.5.0-21-generic On a Dell XPS L502X. lspci -vv attached, more info below. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: usb-modeswitch 1.2.3+repack0-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Mon Dec 31 23:33:00 2012 InstallationDate: Installed on 2012-12-26 (5 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: usb-modeswitch UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1094973/+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 979697] Re: Modeswitching modem not working with some USB 3.0 host controllers
*** This bug is a duplicate of bug 992639 ***
https://bugs.launchpad.net/bugs/992639
I think it is the other way around as this one is older and have the
solution.
#992639 even refers to the solution here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/979697
Title:
Modeswitching modem not working with some USB 3.0 host controllers
Status in The Linux Kernel:
Invalid
Status in Usb Modeswitch:
New
Status in “libusb” package in Ubuntu:
Invalid
Status in “linux” package in Ubuntu:
Invalid
Status in “usb-modeswitch” package in Ubuntu:
Confirmed
Bug description:
Modem switches fine in USB2 ports, but when connected to USB3 port, it
does not work.
The log says it is switching:
Apr 12 10:42:11 marius-T1005 usb_modeswitch: switching device 19d2:0166 on
006/0
02
but the USB device ID does not change:
Bus 006 Device 002: ID 19d2:0166 ZTE WCDMA Technologies MSM
When connected to a USB2/combined USB2/eSata, it gives:
Bus 001 Device 036: ID 19d2:0167 ZTE WCDMA Technologies MSM
and working modem.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: usb-modeswitch 1.2.3+repack0-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
Date: Thu Apr 12 10:43:59 2012
EcryptfsInUse: Yes
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
TERM=xterm
PATH=(custom, user)
LANG=nb_NO.UTF-8
SHELL=/bin/bash
SourcePackage: usb-modeswitch
UpgradeStatus: No upgrade log present (probably fresh install)
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: marius 2044 F pulseaudio
CRDA:
country NO:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0x9820 irq 52'
Mixer name : 'Realtek ALC269VB'
Components : 'HDA:10ec0269,1458b100,00100100'
Controls : 16
Simple ctrls : 9
DistroRelease: Ubuntu 12.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=49e028f9-7435-4850-8244-8523020782de
KnownReport: https://bugs.launchpad.net/bugs/452814
MachineType: GIGABYTE T1005
Package: usb-modeswitch 1.2.3+repack0-1ubuntu2
PackageArchitecture: i386
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
TERM=xterm
PATH=(custom, user)
LANG=nb_NO.UTF-8
SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic-pae
root=UUID=f1d0446d-3ea3-46a7-9842-8773acca78e6 ro quiet splash i8042.noloop=1
vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
RelatedPackageVersions:
linux-restricted-modules-3.2.0-23-generic-pae N/A
linux-backports-modules-3.2.0-23-generic-pae N/A
linux-firmware1.78
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Tags: precise precise
Uname: Linux 3.2.0-23-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/30/2010
dmi.bios.vendor: GIGABYTE
dmi.bios.version: GSBF05
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: T1005
dmi.board.vendor: GIGABYTE
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnGIGABYTE:bvrGSBF05:bd08/30/2010:svnGIGABYTE:pnT1005:pvrGSBF05:rvnGIGABYTE:rnT1005:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: T1005
dmi.product.version: GSBF05
dmi.sys.vendor: GIGABYTE
mtime.conffile..etc.usb.modeswitch.conf: 2012-04-12T10:51:06.199846
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog [ALC269VB Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC269VB Analog
[Desktop-packages] [Bug 873792] Re: libreoffice spellchecker/autocorrect does not work when document is created in the file manager
Created with a right click on konqueror ** Attachment added: test file https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873792/+attachment/2610013/+files/test.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/873792 Title: libreoffice spellchecker/autocorrect does not work when document is created in the file manager Status in “libreoffice” package in Ubuntu: Incomplete Bug description: When creating an empty libre office writes document in konqueror, the spellchecker and auto correct features does not work. It does work if the file is created inside libreoffice itself. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Thu Oct 13 22:38:25 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873792/+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 873792] Re: libreoffice spellchecker/autocorrect does not work when document is created in the file manager
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/873792 Title: libreoffice spellchecker/autocorrect does not work when document is created in the file manager Status in “libreoffice” package in Ubuntu: New Bug description: When creating an empty libre office writes document in konqueror, the spellchecker and auto correct features does not work. It does work if the file is created inside libreoffice itself. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: libreoffice 1:3.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 Architecture: amd64 Date: Thu Oct 13 22:38:25 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/873792/+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
