[Touch-packages] [Bug 304632] Re: DarkRoom makes radio buttons in Firefox difficult to interpret
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/304632 Title: DarkRoom makes radio buttons in Firefox difficult to interpret Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork In Firefox (3.0.4) under Ubuntu 8.10 with the DarkRoom theme, radio buttons are ambiguous. Unselected radio buttons have an orange highlight as if they are being hovered over (and don't have a 'bullet point' inside them). Selected radio buttons are completely black/brown as if they have been selected. See attached picture that illustrates the difference. In the Human theme, selected radio buttons have an orange border with a bullet point inside them, while non-selected radio buttons are white. With the DarkRoom theme, it would be expected that selected radio buttons would have a bullet point inside them and be darker than unselected radio buttons. This is with: ubuntu-artwork: Installed: 46.3 Candidate: 46.3 Version table: *** 46.3 0 500 http://nz.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/304632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 363980] Re: Fuzzy icons in UNR
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/363980 Title: Fuzzy icons in UNR Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork This is a small point and really only goes to the aesthetics of Jaunty's UNR. The following icons look fuzzy on my Acer Aspire One: Preferences/Appearance Preferences/Keyboard Shortcuts Preferences/SCIM Input Method Setup Preferences/Windows Administration/Calibrate Touchscreen Administration/Software Sources Administration/Synaptic Package Manager All other icons look sharp (in the default install anyway - I haven't added any apps yet), which serves to highlight the contrast between sharp and fuzzy. :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/363980/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 249409] Re: In the "NewHuman" theme, the end of the window border is not defined
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/249409 Title: In the "NewHuman" theme, the end of the window border is not defined Status in human-theme: Expired Status in ubuntu-themes package in Ubuntu: Expired Bug description: In the New Human theme, there is no distinction between the window border and the window controls. Having the metacity theme and the gtk theme look as one is helpful, aesthetically speaking but usability speaking, it is hard to tell where the user can drag the window (the window border) and where he cannot (the window controls) without pressing alt. I would suggest doing something similar to the KDE's Oxygen Theme's window kwin and qt theme. To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/249409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 337507] Re: darkroom theme text color too light for gnome-control-center
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/337507 Title: darkroom theme text color too light for gnome-control-center Status in ubuntu-themes package in Ubuntu: Expired Bug description: window of the gnome-control-center does not work well with the included darkroom theme in Jaunty. the color of the menu is merely readable. maybe the graphical appearance of the window need some adjustment. 1) Description: Ubuntu jaunty (development branch) Release: 9.04 2) gnome-control-center: Installiert: 1:2.25.90-0ubuntu4 Kandidat: 1:2.25.90-0ubuntu4 Versions-Tabelle: *** 1:2.25.90-0ubuntu4 0 500 http://de.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status 3) I thought the fond in the control-center would bee readable 4) the buttons in the menu are only readable when you place the mouse cursor above them so they are highlighted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/337507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 288877] Re: [DarkRoom] Add solid color to the top of tabs
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/288877 Title: [DarkRoom] Add solid color to the top of tabs Status in ubuntu-themes package in Ubuntu: Expired Bug description: I think adding a top solid color stripe on notebook tabs make them more easy to see, for example, on Firefox. I've attach a patch and two examples, Firefox with current DarkRoom, and Firefox with DarkRoom and top-colored tabs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/288877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 287065] Re: Darkroom and Darklooks make GTK1 apps unreadable
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/287065 Title: Darkroom and Darklooks make GTK1 apps unreadable Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork Hello, I really like the new dark themes in Ubuntu, however they make working with GTK1 apps impossible, see the attached screenshot of a window in GRASS. This applies to both the Darlooks as well as the DarkRoom themes. The normal Clearlooks theme works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/287065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 249409] Re: In the "NewHuman" theme, the end of the window border is not defined
[Expired for human-theme because there has been no activity for 60 days.] ** Changed in: human-theme Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/249409 Title: In the "NewHuman" theme, the end of the window border is not defined Status in human-theme: Expired Status in ubuntu-themes package in Ubuntu: Expired Bug description: In the New Human theme, there is no distinction between the window border and the window controls. Having the metacity theme and the gtk theme look as one is helpful, aesthetically speaking but usability speaking, it is hard to tell where the user can drag the window (the window border) and where he cannot (the window controls) without pressing alt. I would suggest doing something similar to the KDE's Oxygen Theme's window kwin and qt theme. To manage notifications about this bug go to: https://bugs.launchpad.net/human-theme/+bug/249409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362313] Re: PulseAudio can't find Bluetooth device after reconnecting
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1362313 Title: PulseAudio can't find Bluetooth device after reconnecting Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 165057] Re: Floating Ubuntu SVG is too complex
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/165057 Title: Floating Ubuntu SVG is too complex Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: gnome-screensaver The SVG file for the Floating Ubuntu screensaver is too complex, resulting in the screensaver being rather slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/165057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 299278] Re: [DarkRoom] insufficient contrast in Firefox Preferences window
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/299278 Title: [DarkRoom] insufficient contrast in Firefox Preferences window Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork When using the DarkRoom theme in intrepid (8.10), the Preferences window in Firefox has text that is nearly unreadable. In particular, I am referring to the "Main", "Tabs", "Content", "Applications", "Privacy", "Security", and "Advanced" headings across the top of the preferences window. See attached screenshot for example. Note that the Add-ons window in Firefox exhibits the same undesirable behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/299278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 146700] Re: The human gnome-searchtool icon maximum size is 24x24 making it unclear as a desktop launcher
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/146700 Title: The human gnome-searchtool icon maximum size is 24x24 making it unclear as a desktop launcher Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork locate gnome-searchtool.png shows that the human theme has only 16x16, 22x22, 24x24 images for the gnome-searchtool.png Adding the tracker search tool launcher on the desktop shows it hazy. It does not have a 32x32 or large image size. I think all icons should look good as a desktop launcher, at least the tango alternative is scalable. Using Ubuntu 7.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/146700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 274603] Re: Epiphany start page lacks IRC link
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/274603 Title: Epiphany start page lacks IRC link Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork The file available at file:///usr/share/ubuntu- artwork/home/locales/index-C.html mentions the IRC channel #ubuntu, but does not provide an irc:// protocol link to allow for opening it with Pidgin (or another IRC client). Rather, it is just plain text. This is in Intrepid, as of the 25th of September. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/274603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 288641] Re: DarkRoom does not support all window-border buttons
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/288641 Title: DarkRoom does not support all window-border buttons Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork Metacity maintains a layout for the buttons in the window-border (gconf-key /apps/metacity/general/button_layout). By default, this layout is "menu:minimize,maximize,close". However there are several other options that can be added there, like stick and above. These buttons are not supported by DarkRoom (in intrepid). It would be nice if it does support them. An example theme that supports those buttons is the Crux theme in a default ubuntu-installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/288641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 92910] Re: Human emblems don't refresh properly when enlarged
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/92910 Title: Human emblems don't refresh properly when enlarged Status in ubuntu-themes package in Ubuntu: Expired Bug description: Steps to reproduce using default icon sets: crux, tangerine, human, mist, 1. Go to your home folder and enlarge any of the above icon themes to 150%. 2. Enter one of the folders and then back out to the original directory. You will now notice the sub icons (small icons around the main folder icon) are cut off on their sides. The problem isn't present in icons sets like Tango, where the sub icons are placed underneath the folder and not to its right side. This issue was present in Edgy as well. ProblemType: Bug Architecture: i386 Date: Fri Mar 16 16:54:49 2007 DistroRelease: Ubuntu 7.04 Uname: Linux jlamp-ubuntu 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/92910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 279237] Re: light fonts are difficult to read under some conditions
[Expired for ubuntu-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/279237 Title: light fonts are difficult to read under some conditions Status in ubuntu-themes package in Ubuntu: Expired Bug description: Binary package hint: ubuntu-artwork Although there are some bug reports for this already, they are under specific apps or dialogs, so I felt compelled to enter my own report. The new theme is very nice, however sometimes the light fonts are placed on light backgrounds, creating nearly impossible to read text. Attached is a screenshot of firefox, although other programs are also affected. Another example is IDLE - the code completion feature as well as the docstring tooltip Also dark fonts may occasionally be placed on a dark background, resulting in a similar problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/279237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362313] Re: PulseAudio can't find Bluetooth device after reconnecting
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1362313 Title: PulseAudio can't find Bluetooth device after reconnecting Status in bluez package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693019] Re: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: Paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker konf
[Expired for iproute2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: iproute2 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1693019 Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: Paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker konfigurera. Status in iproute2 package in Ubuntu: Expired Bug description: Can not find it just don’t download it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: libjasper1: Install iproute2: Configure libjasper1: Configure NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:34:50 2017 ErrorMessage: Paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker konfigurera. InstallationDate: Installed on 2017-04-29 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3.16.04.1 failed to install/upgrade: Paketet är i ett väldigt dåligt inkonsistent läge; du bör ominstallera det innan du försöker konfigurera. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1693019/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700759] Re: python3-click-package : Conflicts: python3-click but 6.2-2ubuntu1 is to be installed (ubuntu 16.04)
just to add, i have ubuntu-sdk-team/ppa/ubuntu ppa installed for the sdk, maybe it conflicts with it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1700759 Title: python3-click-package : Conflicts: python3-click but 6.2-2ubuntu1 is to be installed (ubuntu 16.04) Status in click package in Ubuntu: New Bug description: i can't upgrade my system because i keep getting this error "Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: python3-click-package : Conflicts: python3-click but 6.2-2ubuntu1 is to be installed E: Broken packages" i'm using ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1700759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones
** Tags added: xenial ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1025388 Title: Internal mic stops working when plugging in headphones Status in pulseaudio package in Ubuntu: Confirmed Bug description: I am currently running Quantal and when I plug headphones into my headphone socket (which has an icon of a headset next to it, so I presume it can take some kind of headset), the internal mic on my laptop stops working. If I unplug the headphones the internal mic works as normal. I tried this with two different sets of headphones (one of which has a mic, and the other I think has a mic too). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: pulseaudio 1:2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6 Uname: Linux 3.5.0-4-generic i686 ApportVersion: 2.3-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jono 1860 F pulseaudio /dev/snd/pcmC0D0c: jono 1860 F...m pulseaudio Date: Mon Jul 16 11:01:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET56WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1025388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1543755] Re: "sudo bluetoothd --compat" fails with "SDP session setup failed, disabling bluetooth"
Sorry, but 16.10 reached end-of-life four days ago: https://wiki.ubuntu.com/Releases ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1543755 Title: "sudo bluetoothd --compat" fails with "SDP session setup failed, disabling bluetooth" Status in bluez package in Ubuntu: Invalid Bug description: `sudo bluetoothd --compat --nodetach` fails with `SDP session setup failed, disabling bluetooth`. That is unexplicable and not helpful, please provide usable feedback and instructions how to handle the problem. $ obexpushd -B -n obexpushd 0.11.2 Copyright (C) 2006-2010 Hendrik Sattler This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. Listening on bluetooth/[00:00:00:00:00:00]:9 SDP session setup failed, disabling bluetooth net_init() failed ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 Uname: Linux 4.4.1-040401-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 9 20:32:08 2016 InstallationDate: Installed on 2013-10-17 (845 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm btusb bnep bluetooth MachineType: LENOVO IdeaPad U410 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.1-040401-generic root=UUID=8c488557-8173-43a2-a3a8-df0a24695c08 ro rootflags=subvol=ubuntu-main-root quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to wily on 2015-11-19 (82 days ago) dmi.bios.date: 09/25/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 65CN90WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo U410 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr65CN90WW:bd09/25/2012:svnLENOVO:pnIdeaPadU410:pvrLenovoU410:rvnLENOVO:rnLenovo:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoU410: dmi.product.name: IdeaPad U410 dmi.product.version: Lenovo U410 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 84:A6:C8:63:22:B5 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:1003513 acl:2928 sco:0 events:2524 errors:0 TX bytes:36304 acl:872 sco:0 commands:1396 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1543755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580394] Re: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power
Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1547024 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1580394 Title: [Latitude 3340, Realtek ALC3234] MATE - Headphone Static on Battery Power Status in alsa-driver package in Ubuntu: New Bug description: I have noticed that when I am on battery power on a Dell Latitude 3340 laptop with headphones plugged in , and there is no audio playing on the computer, there is a consistent static sound that comes through the headphones at a constant volume that is not affected by changing the volume level. I think it may be picking up some kind of analog loopback signal because keyboard presses and disk activity seem to influence the noise. When I plug the power cable into the laptop , the static immediately goes away. I reported this earlier to the upstream Linux Kernel bug tracker, but it seems to be fixed in any distro running a 4.4 kernel or greater that I have tested , Except for Ubuntu MATE 16.04 LTS 64-bit. This make me think it is not a kernel level issue and is found somewhere either in the audio settings on Ubuntu MATE or a pulseaudio bug. I cannot reproduce it on any other 16.04 distro version, but it also affects all the 14.04.4 distros as well. Running amixer -c 1 set "Loopback Mixing" "Disabled" does not prevent the static. The BIOS Firmware version is up to date. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu-mate 1718 F pulseaudio /dev/snd/controlC0: ubuntu-mate 1718 F pulseaudio CasperVersion: 1.376 CurrentDesktop: MATE Date: Wed May 11 00:43:52 2016 LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd11/04/2015:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1580394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704297] Re: Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected)
** Summary changed: - Parrot Zik headphones stuck in A2DP profile + Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1704297 Title: Bluetooth audio stuck in A2DP profile ([pulseaudio] module- bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705903] Re: audio settings dont allow selecting profile for bluetooth speakers
*** This bug is a duplicate of bug 1704297 *** https://bugs.launchpad.net/bugs/1704297 This sounds close to bug 1704297, and you have the same error message in your log. So let's handle it there... ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Tags added: a2dp ** This bug has been marked a duplicate of bug 1704297 Bluetooth audio stuck in A2DP profile ([pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1705903 Title: audio settings dont allow selecting profile for bluetooth speakers Status in pulseaudio package in Ubuntu: New Bug description: Testing Ubuntu 17.10 daily amd64 encrypted home. On previous versions of Ubuntu (eg. 16.04) in the audio settings when selecting a bluetooth speaker a profile (HSP or A2DP) could be selected. I connected my bluetooth speaker it shows up in the audio settings, i selected the bluetooth speaker as output but every sound still comes from built in laptop speakers not from the bluetooth ones. from syslog: "pulseaudio[5109]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile" "pulseaudio[1525]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302253] Re: [Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card
** Summary changed: - [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card + [Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1302253 Title: [Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Confirmed Bug description: No sound on any package, sound settings shows "Dummy Output". Just allowed Software Updater to install large upgrade, 300+ packages. . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/pcmC1D7p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 3 18:30:55 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-30 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA ATI SB Symptom_Jack: Green Line Out, Rear Title: [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/19/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-78LMT-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1302253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376270] Re: ISSUE with Realteck ALC887 -- no work
*** This bug is a duplicate of bug 1302253 *** https://bugs.launchpad.net/bugs/1302253 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1302253, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1302253 [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1376270 Title: ISSUE with Realteck ALC887 -- no work Status in pulseaudio package in Ubuntu: New Bug description: Analog Audio doen't work. Chipset Realtek ALC887 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D2', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Oct 1 15:41:23 2014 InstallationDate: Installed on 2014-09-16 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FB APD W dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFBAPDW:bd07/15/2014:svnAPD:pnALDA+:pvrALDA+C:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALDA+ dmi.product.version: ALDA+C dmi.sys.vendor: APD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1376270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363710] Re: [GA-970A-DS3, Realtek ALC887-VD, ] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1302253 *** https://bugs.launchpad.net/bugs/1302253 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1302253, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1302253 [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1363710 Title: [GA-970A-DS3, Realtek ALC887-VD,] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: No sound from card after 14.04 upgrade ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D2c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Aug 31 19:30:09 2014 InstallationDate: Installed on 2013-12-16 (258 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA ATI SB Symptom_Jack: Green Line Out, Rear Title: [GA-970A-DS3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card UpgradeStatus: Upgraded to trusty on 2014-08-17 (14 days ago) dmi.bios.date: 01/09/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd01/09/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1363710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705943] Re: No sound on 17.04 [System Product Name, Realtek ALC887-VD, Green Line Out, Rear]
*** This bug is a duplicate of bug 1302253 *** https://bugs.launchpad.net/bugs/1302253 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1302253, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1302253 [GA-78LMT-USB3, Realtek ALC887-VD, Green Line Out, Rear] Pulseaudio fails to detect card -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1705943 Title: No sound on 17.04 [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] Status in pulseaudio package in Ubuntu: New Bug description: I upgraded from 16.10 to 17.04 using Software Updater on 2017-07-22. The upgrade is working well except for almost complete lack of sound; the only time I've heard sound is with the 1st set (but not 2nd set) of test tones during the ubuntu-bug submission process for this bug. It is not a hardware issue since my machine is a dual boot with Windows 10 and sound works on Windows. pavucontrol says I have "Built- in Audio Digital Stereo (IEC958)" and indicates the system is not muted and shows a visual indicator of sound being played when I play a test sound. aplay -l gives the following: List of PLAYBACK Hardware Devices card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 0/1 Subdevice #0: subdevice #0 Thank you for your help, and I'll be happy to provide further info as needed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Jul 23 16:10:22 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-27 (238 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to zesty on 2017-07-22 (1 days ago) dmi.bios.date: 07/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd07/16/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705943/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705882] Re: Bluetooth connection to device fails from Ubuntu 16.04
I was experiencing similar problems, sometimes, until recently. The problem went away for me more recently in 17.10. Can you please try live booting: http://cdimage.ubuntu.com/daily-live/current/ and see if the problem is fixed there in 17.10? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1705882 Title: Bluetooth connection to device fails from Ubuntu 16.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to a bluetooth IOIO device fails using a USB bluetooth adapter from a Ubuntu 16.04 system. The same device could be successfully connected using two non-Ubuntu systems: a) The same system hardware setup (dual-boot) running Windows 8 could connect without any problems. Also could run applications using serial-port associated with this connection. b) Android Note 4 device using bluetooth was able to successfully connect and run apps. Therefore, it was concluded that the Ubuntu 16.04 bluetooth service has a problem. Note: The USB bluetooth adapter used: BTA8000 from Cirago on the ubuntu system as well as the IOIO device. The adapters on the device and system have been verified to have different MAC addresses and works well with other devices. Procedure: Using the Bluetooth control in system-tray -> Bluetooth settings -> +, the device was located as IOIO (8A:22). Here, device was clicked upon, changed PIN to 4545 and pressing next resulted in the device being successfully added. However, the system-tray status of the device continues to say Connection is OFF. Attempting to turnon connection results in changing the system-tray blue-tooth icon to Keys-Icon for few seconds and then reverting back to the bluetooth icon. The device remains in disconnected state and cannot be accessed. The btmon trace (log-line 1277) and bluetoothd syslog (log-line 405) logs seem to indicate that the local host is sending a disconnect request after receiving a SDP: Service Search Attribute Response from the device. The src/device.c:connect_profiles() /org/bluez/hci0/dev_00_1B_DC_06_8A_22 (all), client :1.73 must result in connection setup - not disconnect. Log information was collected for the above procedure. systemInfo.txt: Information about the system bluetooth. syslog.blue: syslog with busr/lib/bluetooth/bluetoothd --noplugin=sap -d in /lib/systemd/system/bluetooth.service btmon.log: result of running sudo btmon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 23 01:28:38 2017 InstallationDate: Installed on 2017-06-03 (49 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Hewlett-Packard HP ENVY dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed root=UUID=1c1d284c-53a1-46dc-bc01-8555da60ad7e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181C dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv7NotebookPC:pvr088A1130592620100:rvnHewlett-Packard:rn181C:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY dv7 Notebook PC dmi.product.version: 088A1130592620100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:1B:DC:06:89:C5 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:242328 acl:898 sco:0 events:316 errors:0 TX bytes:11991 acl:125 sco:0 commands:112 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1705882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1705861] Re: Update OpenCV to 3.x
*it helped.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1705861 Title: Update OpenCV to 3.x Status in opencv package in Ubuntu: Fix Committed Bug description: This is really a continuation to this: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1540168 The conclusion in that bug report seems to be "Won't fix" for 16.04, with a promise for inclusion in "zesty+1". I'm not sure if that means 17.04.2 or not. Just wanted to put a placeholder here as a reminder. OpenCV 2.4.x is seriously outdated and lacking in functionality. Those of us that needed 3.x, end up building it from source, since even ppa options seems to be poorly maintained. That makes it hard to collaborate with others on OpenCV projects. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1705861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598759] Re: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved
Still true for Zesty. ** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1598759 Title: AppArmor nameservice abstraction doesn't allow communication with systemd-resolved Status in AppArmor: Triaged Status in apparmor package in Ubuntu: Fix Released Status in ntp package in Ubuntu: Invalid Status in apparmor source package in Yakkety: Fix Released Status in ntp source package in Yakkety: Invalid Bug description: [ Impact ] Processes confined by AppArmor profiles making use of the nameservice AppArmor abstraction are unable to access the systemd-resolved network name resolution service. The nsswitch.conf file shipped in Yakkety puts the nss-resolve plugin to use which talks to systemd-resolved over D-Bus. The D-Bus communication is blocked for the confined processes described above and those processes will fallback to the traditional means of name resolution. [ Test Case ] * Use ntpd to test: $ sudo apt-get install -y ntp ... $ sudo systemctl stop ntp # in another terminal, watch for AppArmor denials $ dmesg -w # in the original terminal, start ntp $ sudo systemctl start ntp # You'll see a number of denials on the system_bus_socket file: audit: type=1400 audit(1476240762.854:35): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=3867 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=126 ouid=0 * Use tcpdump to test: # Capture traffic on whichever network interface you're currently using $ sudo tcpdump -i eth0 # Look in /var/log/syslog for denials on the system_bus_socket file: audit: type=1400 audit(1476240896.021:40): apparmor="DENIED" operation="connect" profile="/usr/sbin/tcpdump" name="/run/dbus/system_bus_socket" pid=4106 comm="tcpdump" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 In both situations, ntpd and tcpdump will seemingly work as expected due to the name resolution fallback configured in nsswitch.conf. However, neither confined process will be using systemd-resolved for name resolution. [ Regression Potential ] This fix will allow ntp, tcpdump, cupsd, dhclient, and other confined- by-default programs to start using systemd-resolved. There is some potential for regression since those applications have not been previously using systemd-resolved. [ Original bug description ] On this plain install of Xenial apparmor complains about ntpd: [ 19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the problem: #include To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1598759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634418] Re: In 16.10, several apps want write access to /run/systemd/journal/socket
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1634418
Title:
In 16.10, several apps want write access to
/run/systemd/journal/socket
Status in AppArmor:
New
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Several app try to write into /run/systemd/journal/socket
Maybe this should be an abstraction ?
Firefox:
audit: type=1400 audit(1476701934.614:4137): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/run/systemd/journal/socket" pid=25552 comm="firefox"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
evince:
audit: type=1400 audit(1476705359.562:4182): apparmor="DENIED"
operation="sendmsg" profile="/usr/bin/evince"
name="/run/systemd/journal/socket" pid=27271 comm="evince" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=0
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-25.27-generic 4.8.1
Uname: Linux 4.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Oct 18 11:00:02 2016
InstallationDate: Installed on 2015-10-04 (379 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-25-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Oct 18 09:01:30 franck-ThinkPad-T430s dbus[5726]: apparmor="DENIED"
operation="dbus_signal" bus="session" path="/org/gnome/GConf/Server"
interface="org.gnome.GConf.Server" member="Bye" name=":1.128" mask="receive"
pid=8287 label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=7443
peer_label="unconfined"
Oct 18 09:02:58 franck-ThinkPad-T430s dbus[3449]: [system] AppArmor D-Bus
mediation is enabled
Oct 18 10:50:57 franck-ThinkPad-T430s dbus[3455]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (3 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1634418/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705954] Re: package libxcb-sync1:i386 1.10-2ubuntu1 failed to install/upgrade: package libxcb-sync1:i386 is already installed and configured
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1705954 Title: package libxcb-sync1:i386 1.10-2ubuntu1 failed to install/upgrade: package libxcb-sync1:i386 is already installed and configured Status in libxcb package in Ubuntu: New Bug description: i d ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxcb-sync1:i386 1.10-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.25 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashReports: 640:0:116:3368297:2017-07-23 17:02:35.437282562 -0500:2017-07-23 17:02:36.437282562 -0500:/var/crash/libxcb-present0:i386.0.crash 600:0:116:435633:2017-07-23 17:01:34.301285266 -0500:2017-07-23 17:01:35.301285266 -0500:/var/crash/libxcb-sync1:i386.0.crash 644:0:116:0:2017-07-23 17:02:45.461282051 -0500:2017-07-23 17:02:45.461282051 -0500:/var/crash/libxcb-present0:i386.0.upload 600:0:116:435638:2017-07-23 17:01:35.341285178 -0500:2017-07-23 17:01:35.309285179 -0500:/var/crash/libxdamage1:i386.0.crash Date: Sun Jul 23 17:01:35 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 3.16.0-77-generic, x86_64: installed DuplicateSignature: package:libxcb-sync1:i386:1.10-2ubuntu1:package libxcb-sync1:i386 is already installed and configured ErrorMessage: package libxcb-sync1:i386 is already installed and configured GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0623] InstallationDate: Installed on 2017-07-22 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 5349 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-77-generic root=UUID=a7d9c8bb-70f9-4af2-a874-f1edd268b8ea ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxcb Title: package libxcb-sync1:i386 1.10-2ubuntu1 failed to install/upgrade: package libxcb-sync1:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: HMA51_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.05:bd07/28/2011:svnAcer:pnAspire5349:pvrV1.05:rvnAcer:rnHMA51_HR:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5349 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 23 16:20:25 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9964 vendor AUO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1705954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705954] [NEW] package libxcb-sync1:i386 1.10-2ubuntu1 failed to install/upgrade: package libxcb-sync1:i386 is already installed and configured
Public bug reported: i d ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxcb-sync1:i386 1.10-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.25 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashReports: 640:0:116:3368297:2017-07-23 17:02:35.437282562 -0500:2017-07-23 17:02:36.437282562 -0500:/var/crash/libxcb-present0:i386.0.crash 600:0:116:435633:2017-07-23 17:01:34.301285266 -0500:2017-07-23 17:01:35.301285266 -0500:/var/crash/libxcb-sync1:i386.0.crash 644:0:116:0:2017-07-23 17:02:45.461282051 -0500:2017-07-23 17:02:45.461282051 -0500:/var/crash/libxcb-present0:i386.0.upload 600:0:116:435638:2017-07-23 17:01:35.341285178 -0500:2017-07-23 17:01:35.309285179 -0500:/var/crash/libxdamage1:i386.0.crash Date: Sun Jul 23 17:01:35 2017 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 3.16.0-77-generic, x86_64: installed DuplicateSignature: package:libxcb-sync1:i386:1.10-2ubuntu1:package libxcb-sync1:i386 is already installed and configured ErrorMessage: package libxcb-sync1:i386 is already installed and configured GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0623] InstallationDate: Installed on 2017-07-22 (1 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b209 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 5349 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-77-generic root=UUID=a7d9c8bb-70f9-4af2-a874-f1edd268b8ea ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: libxcb Title: package libxcb-sync1:i386 1.10-2ubuntu1 failed to install/upgrade: package libxcb-sync1:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: HMA51_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.05:bd07/28/2011:svnAcer:pnAspire5349:pvrV1.05:rvnAcer:rnHMA51_HR:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5349 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Jul 23 16:20:25 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9964 vendor AUO xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1705954 Title: package libxcb-sync1:i386 1.10-2ubuntu1 failed to install/upgrade: package libxcb-sync1:i386 is already installed and configured Status in libxcb package in Ubuntu: New Bug description: i d ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libxcb-sync1:i386 1.10-2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-77.99~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.25 AptdaemonVersion: 1.1.1-1ubuntu5.2 Architecture: amd64 CompizPlugins: No value set for
[Touch-packages] [Bug 1705951] [NEW] Freezes, crashes, returns to login screen.
Public bug reported: I have a PC with a nVidia GeForce 6800XT graphics card. I installed ubuntu 17.10 and have had many problems with crashes and freezes. After login, the normal screen appears, the screen flashes and the top bar disappears, flashes again and appears normal, but frozen. Clicking again blinks back to the login screen. In order to access the system I was forced to install GNOME Classic. I noticed that in ubuntu 17.04 and ubuntu GNOME 16.04 it works normal. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.agp.gpu: Fast Writes:Supported SBA:Supported AGP Rates: 8x 4x Registers: 0xff000e1b:0x1f000302 .proc.driver.nvidia.agp.host-bridge: Host Bridge:PCI device 1106:0308 Fast Writes:Supported SBA:Supported AGP Rates: 8x 4x Registers: 0x1f000a1b:0x0b02 .proc.driver.nvidia.agp.status: Status: Enabled Driver: AGPGART AGP Rate: 8x Fast Writes:Disabled SBA:Enabled .proc.driver.nvidia.gpus.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1) ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jul 23 18:13:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.11.0-10-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation NV40 [GeForce 6800 XT] [10de:0048] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-07-17 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic root=UUID=7a3a72ab-cccf-4c14-97c3-1dcd85b1aca8 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/08/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5VDC-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd11/08/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5VDC-X:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 23 18:12:42 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputMicrosoft Basic Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1705951 Title: Freezes, crashes, returns to login screen. Status in xorg package in Ubuntu: New Bug description: I have a PC with a nVidia GeForce 6800XT graphics card. I installed ubuntu 17.10 and have had many problems with crashes and freezes. After login, the normal screen appears, the screen flashes and the top bar disappears, flashes again and appears normal, but frozen. Clicking again blinks back
[Touch-packages] [Bug 1705947] [NEW] crash in libvte when dealing with large amounts of data
Public bug reported: On an arm64 system (Cortex-A57 based AMD Overdrive), dumping a lot of data to a gnome-terminal window crashes the gnome-terminal-server process. For instance, doing something like $ hexdump -C /dev/urandom will crash within a matter of seconds with the following backtrace Vte:ERROR:/build/vte2.91-uFdgfJ/vte2.91-0.44.2/./src/vtestream- file.h:790:unsigned int _vte_boa_uncompress(char*, unsigned int, const char*, unsigned int): assertion failed (z_ret == Z_OK): (4294967293 == 0) Thread 1 "gnome-terminal-" received signal SIGABRT, Aborted. 0xb724cb74 in raise () from /lib/aarch64-linux-gnu/libc.so.6 (gdb) bt #0 0xb724cb74 in raise () from /lib/aarch64-linux-gnu/libc.so.6 #1 0xb724df5c in abort () from /lib/aarch64-linux-gnu/libc.so.6 #2 0xb7419704 in g_assertion_message (domain=domain@entry=0xb7fa6d40 "Vte", file=file@entry=0xb7faefc8 "/build/vte2.91-uFdgfJ/vte2.91-0.44.2/./src/vtestream-file.h", line=line@entry=790, func=func@entry=0xb7faee48 <_vte_boa_uncompress::__PRETTY_FUNCTION__> "unsigned int _vte_boa_uncompress(char*, unsigned int, const char*, unsigned int)", message=message@entry=0x976a40 "assertion failed (z_ret == Z_OK): (4294967293 == 0)") at ../../../../glib/gtestutils.c:2433 #3 0xb7419ad4 in g_assertion_message_cmpnum (domain=0xb7fa6d40 "Vte", file=0xb7faefc8 "/build/vte2.91-uFdgfJ/vte2.91-0.44.2/./src/vtestream-file.h", line=790, func=0xb7faee48 <_vte_boa_uncompress::__PRETTY_FUNCTION__> "unsigned int _vte_boa_uncompress(char*, unsigned int, const char*, unsigned int)", expr=, arg1=, cmp=0xb7faa220 "==", arg2=, numtype=) at ../../../../glib/gtestutils.c:2489 #4 0xb7fa3cdc in _vte_boa_uncompress (dstlen=65512, srclen=7197, src=0xfffeeb78 "", dst=) at ././src/vtestream-file.h:790 #5 _vte_boa_read_with_overwrite_counter (boa=0x510c20, offset=offset@entry=0, data=, overwrite_counter=overwrite_counter@entry=0xec74) at ././src/vtestream-file.h:911 #6 0xb7fa4094 in _vte_boa_read (data=, offset=0, boa=) at ././src/vtestream-file.h:922 #7 _vte_file_stream_read (astream=0x54a8a0, offset=24, data=0xecb0 "\001", len=24) at ././src/vtestream-file.h:1138 #8 0xb7f7d93c in _vte_ring_read_row_record (ring=0x7e47b8, position=, record=0xecd0) at ././src/ring.cc:124 #9 _vte_ring_discard_one_row (ring=0x7e47b8) at ././src/ring.cc:417 #10 _vte_ring_maybe_discard_one_row (ring=0x7e47b8) at ././src/ring.cc:439 #11 _vte_ring_insert (ring=ring@entry=0x7e47b8, position=position@entry=1) at ././src/ring.cc:551 #12 0xb7f8012c in VteTerminalPrivate::ring_insert (this=this@entry=0x7e46e0, position=1, fill=fill@entry=false) at ././src/vte.cc:247 #13 0xb7f82204 in VteTerminalPrivate::ring_append (fill=false, this=0x7e46e0) at ././src/vte.cc:257 #14 VteTerminalPrivate::insert_rows (cnt=1, this=) at ././src/vte.cc:2419 #15 VteTerminalPrivate::update_insert_delta (this=0x7e46e0) at ././src/vte.cc:2465 #16 0xb7f8f324 in VteTerminalPrivate::process_incoming (this=this@entry=0x7e46e0) at ././src/vte.cc:3808 #17 0xb7f8ffe0 in VteTerminalPrivate::time_process_incoming (this=this@entry=0x7e46e0) at ././src/vte.cc:10652 #18 0xb7f900c0 in VteTerminalPrivate::process (this=this@entry=0x7e46e0, emit_adj_changed=emit_adj_changed@entry=true) at ././src/vte.cc:10676 #19 0xb7f903c4 in update_repeat_timeout (data=) at ././src/vte.cc:10819 #20 0xb73f2634 in g_timeout_dispatch (source=0x9c6db0, callback=, user_data=) at ../../../../glib/gmain.c:4674 #21 0xb73f1a50 in g_main_dispatch (context=0x4ae300) at ../../../../glib/gmain.c:3203 #22 g_main_context_dispatch (context=context@entry=0x4ae300) at ../../../../glib/gmain.c:3856 #23 0xb73f1df0 in g_main_context_iterate (context=context@entry=0x4ae300, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../../../../glib/gmain.c:3929 #24 0xb73f1eb4 in g_main_context_iteration (context=context@entry=0x4ae300, may_block=may_block@entry=1) at ../../../../glib/gmain.c:3990 #25 0xb75b9a00 in g_application_run (application=0x6d1130, argc=0, argv=0x0) at ../../../../gio/gapplication.c:2381 #26 0x0041506c in ?? () The crash is caused by a failed assertion, i.e., that uncompress() returns Z_OK. I have managed to debug it a bit, and it appears that uncompress returns Z_DATA_ERROR because the compressed input is corrupted, and interestingly, consists of all zeroes. Note that this is an arm64 system, which has a weakly ordered memory model, so this could be a synchronization issue. The exact same bug has been reported here, running on an arm64 based Chromebook. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862591 The reason I am reporting this against glib2.0 and not vte2.91 is that the issue only occurs on zesty (not on yakkety), and the version of vte between the two is identical.
[Touch-packages] [Bug 1705861] Re: Update OpenCV to 3.x
Thank you for the detailed explanation. I helped to make sense of all this. ** Changed in: opencv (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1705861 Title: Update OpenCV to 3.x Status in opencv package in Ubuntu: Fix Committed Bug description: This is really a continuation to this: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1540168 The conclusion in that bug report seems to be "Won't fix" for 16.04, with a promise for inclusion in "zesty+1". I'm not sure if that means 17.04.2 or not. Just wanted to put a placeholder here as a reminder. OpenCV 2.4.x is seriously outdated and lacking in functionality. Those of us that needed 3.x, end up building it from source, since even ppa options seems to be poorly maintained. That makes it hard to collaborate with others on OpenCV projects. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1705861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705943] [NEW] No sound on 17.04 [System Product Name, Realtek ALC887-VD, Green Line Out, Rear]
Public bug reported: I upgraded from 16.10 to 17.04 using Software Updater on 2017-07-22. The upgrade is working well except for almost complete lack of sound; the only time I've heard sound is with the 1st set (but not 2nd set) of test tones during the ubuntu-bug submission process for this bug. It is not a hardware issue since my machine is a dual boot with Windows 10 and sound works on Windows. pavucontrol says I have "Built-in Audio Digital Stereo (IEC958)" and indicates the system is not muted and shows a visual indicator of sound being played when I play a test sound. aplay -l gives the following: List of PLAYBACK Hardware Devices card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 0/1 Subdevice #0: subdevice #0 Thank you for your help, and I'll be happy to provide further info as needed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Jul 23 16:10:22 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-27 (238 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] No sound at all UpgradeStatus: Upgraded to zesty on 2017-07-22 (1 days ago) dmi.bios.date: 07/16/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1701 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1701:bd07/16/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1705943 Title: No sound on 17.04 [System Product Name, Realtek ALC887-VD, Green Line Out, Rear] Status in pulseaudio package in Ubuntu: New Bug description: I upgraded from 16.10 to 17.04 using Software Updater on 2017-07-22. The upgrade is working well except for almost complete lack of sound; the only time I've heard sound is with the 1st set (but not 2nd set) of test tones during the ubuntu-bug submission process for this bug. It is not a hardware issue since my machine is a dual boot with Windows 10 and sound works on Windows. pavucontrol says I have "Built- in Audio Digital Stereo (IEC958)" and indicates the system is not muted and shows a visual indicator of sound being played when I play a test sound. aplay -l gives the following: List of PLAYBACK Hardware Devices card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 0/1 Subdevice #0: subdevice #0 Thank you for your help, and I'll be happy to provide further info as needed. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Jul 23 16:10:22 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-27 (238 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful Symptom_Card: Built-in Audio - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed
[Touch-packages] [Bug 1705935] Re: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1705935 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in ntp package in Ubuntu: New Bug description: My update not working ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 AptOrdering: linux-libc-dev: Install ntp: Configure linux-libc-dev: Configure Architecture: i386 Date: Sun Jul 23 19:33:33 2017 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.11:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-06-20 (398 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126 NtpStatus: Error: command ['ntpq', '-p'] failed with exit code 127: ntpq: error while loading shared libraries: /usr/lib/i386-linux-gnu/libopts.so.25: invalid ELF header ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=c7a0ffbe-0794-4105-9953-532f3e1ed5c0 ro profile RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1705935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705935] [NEW] package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: My update not working ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 AptOrdering: linux-libc-dev: Install ntp: Configure linux-libc-dev: Configure Architecture: i386 Date: Sun Jul 23 19:33:33 2017 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.11:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-06-20 (398 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126 NtpStatus: Error: command ['ntpq', '-p'] failed with exit code 127: ntpq: error while loading shared libraries: /usr/lib/i386-linux-gnu/libopts.so.25: invalid ELF header ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=c7a0ffbe-0794-4105-9953-532f3e1ed5c0 ro profile RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 rosa third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1705935 Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in ntp package in Ubuntu: New Bug description: My update not working ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.25 AptOrdering: linux-libc-dev: Install ntp: Configure linux-libc-dev: Configure Architecture: i386 Date: Sun Jul 23 19:33:33 2017 DuplicateSignature: package:ntp:1:4.2.6.p5+dfsg-3ubuntu2.14.04.11:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-06-20 (398 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126 NtpStatus: Error: command ['ntpq', '-p'] failed with exit code 127: ntpq: error while loading shared libraries: /usr/lib/i386-linux-gnu/libopts.so.25: invalid ELF header ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=c7a0ffbe-0794-4105-9953-532f3e1ed5c0 ro profile RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: ntp Title: package ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1705935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703326] Re: Lock screen wallpaper is a plain blue screen
** Description changed: The default lock screen wallpaper in Artful is currently a plain blue screen. - This is probably because the default wallpaper file doesn't exist on - Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg). + We just need to set a gsettings override in ubuntu-settings for + org.gnome.desktop.screensaver picture-uri + + The easy fix for now is to just use the same as the existing Ubuntu + default background but Design could later provide an alternate + background. + + Users can change the lockscreen background in gnome-control-center's + Settings>Background + + Original Report + --- + This is probably because the default wallpaper file doesn't exist on Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg). This should be the default wallpaper. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1703326 Title: Lock screen wallpaper is a plain blue screen Status in ubuntu-settings package in Ubuntu: Triaged Bug description: The default lock screen wallpaper in Artful is currently a plain blue screen. We just need to set a gsettings override in ubuntu-settings for org.gnome.desktop.screensaver picture-uri The easy fix for now is to just use the same as the existing Ubuntu default background but Design could later provide an alternate background. Users can change the lockscreen background in gnome-control-center's Settings>Background Original Report --- This is probably because the default wallpaper file doesn't exist on Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg). This should be the default wallpaper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1703326/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703326] Re: Lock screen wallpaper is a plain blue screen
** Package changed: gsettings-desktop-schemas (Ubuntu) => ubuntu- settings (Ubuntu) ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1703326 Title: Lock screen wallpaper is a plain blue screen Status in ubuntu-settings package in Ubuntu: Triaged Bug description: The default lock screen wallpaper in Artful is currently a plain blue screen. We just need to set a gsettings override in ubuntu-settings for org.gnome.desktop.screensaver picture-uri The easy fix for now is to just use the same as the existing Ubuntu default background but Design could later provide an alternate background. Users can change the lockscreen background in gnome-control-center's Settings>Background Original Report --- This is probably because the default wallpaper file doesn't exist on Artful (/usr/share/backgrounds/gnome/adwaita-lock.jpg). This should be the default wallpaper. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1703326/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
Same here with 16.04.2 (4.8.0-58-generic x86_64, no VM) and Realtek8111 (PCI 10ec:8168 rev 06). Worked before with 12.04, now it's shutting down the interface every few days. Regarding the Networkmanager restart: Not for me, the PID is still the same. Maybe the timing from the latest event may help: Jul 23 13:51:19 braindead5 dhclient[26468]: DHCPREQUEST of 192.168.0.5 on enp8s0 to 192.168.0.1 port 67 (xid=0x75dc0193) Jul 23 13:51:19 braindead5 dhclient[26468]: DHCPACK of 192.168.0.5 from 192.168.0.1 Jul 23 13:51:19 braindead5 dhclient[26468]: bound to 192.168.0.5 -- renewal in 17447 seconds. So the IP is valid for more than 4h. But about an hour later: Jul 23 14:57:51 braindead5 avahi-daemon[907]: Withdrawing address record for 192.168.0.5 on enp8s0. Jul 23 14:57:51 braindead5 avahi-daemon[907]: Leaving mDNS multicast group on interface enp8s0.IPv4 with address 192.168.0.5. Jul 23 14:57:51 braindead5 avahi-daemon[907]: Interface enp8s0.IPv4 no longer relevant for mDNS. Jul 23 14:57:51 braindead5 org.kde.kdeconnect[1675]: "No such interface 'org.freedesktop.DBus.Properties' on object at path /" Jul 23 14:57:56 braindead5 kernel: [1879701.611525] nfs: server 192.168.0.1 not responding, timed out The interface was shut down (no IP, only visible with ifconfig -a), but it had link state (green LED). There were no other messages regarding Networkmanager etc. at that time. It's hard to tell if the NFS problems are caused by the avahi-stuff or both share the same root cause. In my experience, NFS usually "finds" missing connectivity very fast, so it should complain before avahi... Also on all other occurences the avahi message was before NFS. I've now stopped the avahi-daemon. If it happens again, I will look if dhclient runs and if there are increasing RX packets and visible broadcast data from other hosts at the dead interface. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705915] [NEW] VPN network menu items disappear after suspend
Public bug reported: This is not consistent, but sometimes after suspending when i reconnect the VPN menu items (using OpenVPN) are gone. I can launch the VPN by going to Network Settings and toggling a particular VPN setting off and then back on. Tried "sudo service network-manager restart" but no help. Using fully updated 16.04.2 LTS on ThinkPad T460. network-manager 1.2.6-0ubuntu0.16.04.1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1705915 Title: VPN network menu items disappear after suspend Status in network-manager package in Ubuntu: New Bug description: This is not consistent, but sometimes after suspending when i reconnect the VPN menu items (using OpenVPN) are gone. I can launch the VPN by going to Network Settings and toggling a particular VPN setting off and then back on. Tried "sudo service network-manager restart" but no help. Using fully updated 16.04.2 LTS on ThinkPad T460. network-manager 1.2.6-0ubuntu0.16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1705915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705903] Re: audio settings dont allow selecting profile for bluetooth speakers
** Description changed: Testing Ubuntu 17.10 daily amd64 encrypted home. On previous versions of Ubuntu (eg. 16.04) in the audio settings when selecting a bluetooth speaker a profile (HSP or A2DP) could be selected. I connected my bluetooth speaker it shows up in the audio settings, i selected the bluetooth speaker as output but every sound still comes from built in laptop speakers not from the bluetooth ones. from syslog: + + "pulseaudio[5109]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile" "pulseaudio[1525]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" ** Description changed: Testing Ubuntu 17.10 daily amd64 encrypted home. On previous versions of Ubuntu (eg. 16.04) in the audio settings when selecting a bluetooth speaker a profile (HSP or A2DP) could be selected. I connected my bluetooth speaker it shows up in the audio settings, i selected the bluetooth speaker as output but every sound still comes from built in laptop speakers not from the bluetooth ones. from syslog: - "pulseaudio[5109]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile" "pulseaudio[1525]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1705903 Title: audio settings dont allow selecting profile for bluetooth speakers Status in pulseaudio package in Ubuntu: New Bug description: Testing Ubuntu 17.10 daily amd64 encrypted home. On previous versions of Ubuntu (eg. 16.04) in the audio settings when selecting a bluetooth speaker a profile (HSP or A2DP) could be selected. I connected my bluetooth speaker it shows up in the audio settings, i selected the bluetooth speaker as output but every sound still comes from built in laptop speakers not from the bluetooth ones. from syslog: "pulseaudio[5109]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile" "pulseaudio[1525]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703625] Re: package vlc-plugin-visualization 2.2.4-14ubuntu2.1 failed to install/upgrade: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2
** Changed in: vlc (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1703625 Title: package vlc-plugin-visualization 2.2.4-14ubuntu2.1 failed to install/upgrade: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2 Status in apport package in Ubuntu: Invalid Status in vlc package in Ubuntu: Incomplete Bug description: package vlc-plugin-visualization 2.2.4-14ubuntu2.1 failed to install/upgrade: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: vlc-plugin-visualization 2.2.4-14ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 Architecture: amd64 Date: Tue Jul 11 17:51:17 2017 ErrorMessage: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2 InstallationDate: Installed on 2017-07-04 (6 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: vlc Title: package vlc-plugin-visualization 2.2.4-14ubuntu2.1 failed to install/upgrade: подпроцесс dpkg-deb --fsys-tarfile возвратил код ошибки 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1703625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705903] [NEW] audio settings dont allow selecting profile for bluetooth speakers
Public bug reported: Testing Ubuntu 17.10 daily amd64 encrypted home. On previous versions of Ubuntu (eg. 16.04) in the audio settings when selecting a bluetooth speaker a profile (HSP or A2DP) could be selected. I connected my bluetooth speaker it shows up in the audio settings, i selected the bluetooth speaker as output but every sound still comes from built in laptop speakers not from the bluetooth ones. from syslog: "pulseaudio[1525]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful gnome-17.10 julyshakedown ** Tags added: gnome-17.10 julyshakedown ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1705903 Title: audio settings dont allow selecting profile for bluetooth speakers Status in pulseaudio package in Ubuntu: New Bug description: Testing Ubuntu 17.10 daily amd64 encrypted home. On previous versions of Ubuntu (eg. 16.04) in the audio settings when selecting a bluetooth speaker a profile (HSP or A2DP) could be selected. I connected my bluetooth speaker it shows up in the audio settings, i selected the bluetooth speaker as output but every sound still comes from built in laptop speakers not from the bluetooth ones. from syslog: "pulseaudio[1525]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1705903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705861] Re: Update OpenCV to 3.x
Thanks for taking your time to report this issue and help making Ubuntu better. >"zesty+1". I'm not sure if that means 17.04.2 or not. +1 is referring to the next release after zesty, i.e. artful (17.10). Presumably the original comment was written before the new code name was announced. Artful currently contains opencv 3.1.0+dfsg1-1~exp1ubuntu1 (with a newer version waiting in -proposed), see https://launchpad.net/ubuntu/+source/opencv. Once a newer version is available in the development version in Ubuntu, most upgrade request issues are considered fixed, because a newer version is available and people will upgrade at some point. In some cases, it makes sense to offer the newer version for older releases as well though, you can take a look at how on "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport. (In some cases, individual fixes are also applied to older releases (Stable Release Upgrades)). So it might be possible to get a backport of 3.1 available in 16.04 for instance. I am not familiar with this library, but be aware that newer version of libraries often require newer version of their dependencies, so it might not be straight-forward to copy over the sources to 16.04 and rebuild them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1705861 Title: Update OpenCV to 3.x Status in opencv package in Ubuntu: New Bug description: This is really a continuation to this: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1540168 The conclusion in that bug report seems to be "Won't fix" for 16.04, with a promise for inclusion in "zesty+1". I'm not sure if that means 17.04.2 or not. Just wanted to put a placeholder here as a reminder. OpenCV 2.4.x is seriously outdated and lacking in functionality. Those of us that needed 3.x, end up building it from source, since even ppa options seems to be poorly maintained. That makes it hard to collaborate with others on OpenCV projects. thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1705861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705889] Re: package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcrypt
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1705889 Title: package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in heimdal package in Ubuntu: New Bug description: I was installing packages using the terminal when I encountered this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Jul 22 15:07:00 2017 ErrorMessage: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-07-16 (371 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1705889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705889] [NEW] package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcry
Public bug reported: I was installing packages using the terminal when I encountered this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Jul 22 15:07:00 2017 ErrorMessage: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-07-16 (371 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1705889 Title: package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in heimdal package in Ubuntu: New Bug description: I was installing packages using the terminal when I encountered this error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat Jul 22 15:07:00 2017 ErrorMessage: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-07-16 (371 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: heimdal Title: package libhcrypto4-heimdal:amd64 1.7~git20150920+dfsg-4ubuntu1 [modified: usr/lib/x86_64-linux-gnu/libhcrypto.so.4.1.0] failed to install/upgrade: package libhcrypto4-heimdal:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1705889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705884] [NEW] Black screen
Public bug reported: black screen when lock. Black screen not able to recover login info to re-enter gnome. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jul 23 11:29:32 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 420] [174b:1162] InstallationDate: Installed on 2017-06-04 (49 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Packard Bell imedia S3810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=61dd95f6-c8ec-48c9-82fd-87eee44dd781 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: imedia S3810 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd08/19/2010:svnPackardBell:pnimediaS3810:pvr:rvnPackardBell:rnimediaS3810:rvr:cvnPackardBell:ct3:cvr: dmi.product.name: imedia S3810 dmi.sys.vendor: Packard Bell version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1705884 Title: Black screen Status in xorg package in Ubuntu: New Bug description: black screen when lock. Black screen not able to recover login info to re-enter gnome. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jul 23 11:29:32 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 420] [10de:0de2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology GF108 [GeForce GT 420] [174b:1162] InstallationDate: Installed on 2017-06-04 (49 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Packard Bell imedia S3810 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic root=UUID=61dd95f6-c8ec-48c9-82fd-87eee44dd781 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P01-A4 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: imedia S3810 dmi.board.vendor: Packard Bell dmi.chassis.type: 3 dmi.chassis.vendor: Packard Bell dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP01-A4:bd08/19/2010:svnPackardBell:pnimediaS3810:pvr:rvnPackardBell:rnimediaS3810:rvr:cvnPackardBell:ct3:cvr: dmi.product.name: imedia S3810 dmi.sys.vendor: Packard Bell version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to:
[Touch-packages] [Bug 1568787] Re: resolvconf does not reliable receive nameserver information from NetworkManager
I first experience this issue with nm version 1.8.2-1ubuntu1 in an - as of writing fully updated - 17.04. Syslog will be attached, from that you can see that dnsmask gets the nameserver, networkmanager gets it too, but it doesn't make to resolv.conf, that will only have the stub resolver. /etc/resolv.conf is a link ending in /run/resolvconf/resolv.conf. Workaround is to manually add the nameserver to resolv conf and comment out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf which is really annoying on a laptop which you move around a lot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1568787 Title: resolvconf does not reliable receive nameserver information from NetworkManager Status in dbus package in Ubuntu: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: resolvconf does not reliable receive nameserver information from NetworkManager. In the journal I see things like: Apr 11 11:13:52 ottawa dnsmasq[3122]: setting upstream servers from DBus Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver fe80::1#53 Apr 11 11:13:52 ottawa dnsmasq[3122]: using nameserver 192.168.1.254#53 Apr 11 11:13:52 ottawa dbus[978]: [system] Rejected send message, 13 matched rules; type="method_return", sender=":1.99" (uid=0 pid=3122 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=1017 comm="/usr/sbin/NetworkManager --no-daemon ") Apr 11 11:04:21 ottawa NetworkManager[1017]: DNS: starting dnsmasq... Apr 11 11:04:21 ottawa NetworkManager[1017]: dnsmasq not available on the bus, can't update servers. Apr 11 11:04:21 ottawa NetworkManager[1017]: [1460369061.825658] [dns-manager/nm-dns-dnsmasq.c:387] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Doing this via dbus seems really odd, but I suspect messages between NetworkManager and the dnsmasq it spawns should not be rejected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq-base 2.75-1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 11 11:17:34 2016 InstallationDate: Installed on 2016-01-26 (76 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1568787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop
Same issue on Acer Aspire V15 Nitro with Ubuntu 17.04, Nvidia binary driver 375.66 and Nvidia Geforce 1060 mobile + Intel HD Graphics 630. The HDMI is hardwired to the Nvidia GPU and no Nvidia audio device is listed with lspci, aplay -l or in /proc/asound. The Nvidia never shows up, even on boot with HDMI cable plugged in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1377653 Title: HDMI sound output not detected / NVIDIA optimus laptop Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Hi, not sure if this is an alsa or nvidia/nouveau bug. HDMI audio output doesn't appear in sound settings output panel. Audio works well on internal speakers, but it seems there is no way to make it output to hdmi... The laptop has optimus NVIDIA+Intel. The behaviour is the same with nouveau or nvidia proprietary driver. Please let me know if further testing is required ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sam2295 F pulseaudio CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Sun Oct 5 17:05:35 2014 InstallationDate: Installed on 2014-04-21 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.215 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1377653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705882] [NEW] Bluetooth connection to device fails from Ubuntu 16.04
Public bug reported: Bluetooth connection to a bluetooth IOIO device fails using a USB bluetooth adapter from a Ubuntu 16.04 system. The same device could be successfully connected using two non-Ubuntu systems: a) The same system hardware setup (dual-boot) running Windows 8 could connect without any problems. Also could run applications using serial-port associated with this connection. b) Android Note 4 device using bluetooth was able to successfully connect and run apps. Therefore, it was concluded that the Ubuntu 16.04 bluetooth service has a problem. Note: The USB bluetooth adapter used: BTA8000 from Cirago on the ubuntu system as well as the IOIO device. The adapters on the device and system have been verified to have different MAC addresses and works well with other devices. Procedure: Using the Bluetooth control in system-tray -> Bluetooth settings -> +, the device was located as IOIO (8A:22). Here, device was clicked upon, changed PIN to 4545 and pressing next resulted in the device being successfully added. However, the system-tray status of the device continues to say Connection is OFF. Attempting to turnon connection results in changing the system-tray blue-tooth icon to Keys- Icon for few seconds and then reverting back to the bluetooth icon. The device remains in disconnected state and cannot be accessed. The btmon trace (log-line 1277) and bluetoothd syslog (log-line 405) logs seem to indicate that the local host is sending a disconnect request after receiving a SDP: Service Search Attribute Response from the device. The src/device.c:connect_profiles() /org/bluez/hci0/dev_00_1B_DC_06_8A_22 (all), client :1.73 must result in connection setup - not disconnect. Log information was collected for the above procedure. systemInfo.txt: Information about the system bluetooth. syslog.blue: syslog with busr/lib/bluetooth/bluetoothd --noplugin=sap -d in /lib/systemd/system/bluetooth.service btmon.log: result of running sudo btmon ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 23 01:28:38 2017 InstallationDate: Installed on 2017-06-03 (49 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Hewlett-Packard HP ENVY dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed root=UUID=1c1d284c-53a1-46dc-bc01-8555da60ad7e ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181C dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd11/02/2012:svnHewlett-Packard:pnHPENVYdv7NotebookPC:pvr088A1130592620100:rvnHewlett-Packard:rn181C:rvr52.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY dv7 Notebook PC dmi.product.version: 088A1130592620100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:1B:DC:06:89:C5 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:242328 acl:898 sco:0 events:316 errors:0 TX bytes:11991 acl:125 sco:0 commands:112 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "log.tar.gz" https://bugs.launchpad.net/bugs/1705882/+attachment/4919585/+files/log.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1705882 Title: Bluetooth connection to device fails from Ubuntu 16.04 Status in bluez package in Ubuntu: New Bug description: Bluetooth connection to a bluetooth IOIO device fails using a USB bluetooth adapter from a Ubuntu 16.04 system. The same device could be successfully connected using two non-Ubuntu systems: a) The same system hardware setup (dual-boot) running Windows 8 could connect without any problems. Also could run applications using serial-port associated with this connection. b) Android Note
