[Bug 1879976] Re: pads revert to same workspace after loging out and back in
Hi Howard, Would you mind to specify in more detail how the issue can be reproduced? For example - Install Ubuntu 18.0.4 - Install Xpad 5.0 - Create note on workspace 1 - Switch to workspace 2 - ... Also, does the problem happen also with Xpad 5.4 or 5.5? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1879976] Re: pads revert to same workspace after loging out and back in
Xpad heavily depends on GTK, an application framework, which (IMHO) has the tendency to break things. Which desktop environment is used by PopOS? Is that Lxqt, KDE plasma, gnome, ... ? On Sun, 24 May 2020 at 15:35, Alan Griffith <1879...@bugs.launchpad.net> wrote: > Yes, it worked right before and doesn't now. I don't know what could have > been different to reproduce the change > > On Sun, May 24, 2020 at 3:00 AM Arthur Borsboom < > 1879...@bugs.launchpad.net> > wrote: > > > Do I understand it correct that both Xpad 5.0 and 5.4 have the same issue > > and is unrelated to the PopOS upgrade, since the issue is in both PopOS > > versions with both Xpad versions? > > > > > > On Fri, 22 May 2020 at 22:25, Alan Griffith <1879...@bugs.launchpad.net> > > wrote: > > > > > I tried installing popos 19.10 in a vm, updating all packages to latest > > > 19.10 version, installing xpad, creating notes, moving to different > > > workspaces and logging out and logging back in. All notes moved back to > > the > > > same workspace > > > > > > > > > On Fri, May 22, 2020 at 2:46 PM Alan Griffith > wrote: > > > > > > > The previous OS release https://packages.ubuntu.com/eoan/xpad has > > > 5.4.0-1 > > > > the same as the current release > https://packages.ubuntu.com/focal/xpad > > > > > > > > I tested xpad 5.0.0-1 from > > > > https://mirrors.edge.kernel.org/ubuntu/pool/universe/x/xpad/ on the > > > > current version of PopOS and the notes move back to the same > workspace > > > > after logging out and in > > > > > > > > On Fri, May 22, 2020 at 1:10 PM Arthur Borsboom < > > > > 1879...@bugs.launchpad.net> wrote: > > > > > > > >> Do you know which version was being used in Pop!_OS 19.10 ? > > > >> Are you are able to downgrade to that version to test if it makes a > > > >> difference? > > > >> > > > >> On Thu, 21 May 2020 at 19:40, Alan Griffith < > > 1879...@bugs.launchpad.net > > > > > > > >> wrote: > > > >> > > > >> > xpad 5.4.0-1 > > > >> > > > > >> > On Thu, May 21, 2020, 12:25 Arthur Borsboom < > > > 1879...@bugs.launchpad.net > > > >> > > > > >> > wrote: > > > >> > > > > >> > > Which version of Xpad shows this behavior? > > > >> > > > > > >> > > -- > > > >> > > You received this bug notification because you are subscribed to > > the > > > >> bug > > > >> > > report. > > > >> > > https://bugs.launchpad.net/bugs/1879976 > > > >> > > > > > >> > > Title: > > > >> > > pads revert to same workspace after loging out and back in > > > >> > > > > > >> > > Status in Xpad: > > > >> > > New > > > >> > > Status in Ubuntu: > > > >> > > New > > > >> > > > > > >> > > Bug description: > > > >> > > pads revert to same workspace after logging out and back in > > > >> > > This started happening after upgrading to Pop!_OS 20.04 LTS > from > > > >> 19.10. > > > >> > > > > > >> > > To manage notifications about this bug go to: > > > >> > > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > > > >> > > > > > >> > > > > >> > -- > > > >> > You received this bug notification because you are subscribed to > > Xpad. > > > >> > Matching subscriptions: Arthur Borsboom > > > >> > https://bugs.launchpad.net/bugs/1879976 > > > >> > > > > >> > Title: > > > >> > pads revert to same workspace after loging out and back in > > > >> > > > > >> > Status in Xpad: > > > >> > New > > > >> > Status in Ubuntu: > > > >> > New > > > >> > > > > >> > Bug description: > > > >> > pads revert to same workspace after logging out and back in > > > >> > This started happening after upgrading to Pop!_OS 20.04 LTS from > > > >> 19.10. > > > >> > > > >
Re: [Bug 1879976] Re: pads revert to same workspace after loging out and back in
Do I understand it correct that both Xpad 5.0 and 5.4 have the same issue and is unrelated to the PopOS upgrade, since the issue is in both PopOS versions with both Xpad versions? On Fri, 22 May 2020 at 22:25, Alan Griffith <1879...@bugs.launchpad.net> wrote: > I tried installing popos 19.10 in a vm, updating all packages to latest > 19.10 version, installing xpad, creating notes, moving to different > workspaces and logging out and logging back in. All notes moved back to the > same workspace > > > On Fri, May 22, 2020 at 2:46 PM Alan Griffith wrote: > > > The previous OS release https://packages.ubuntu.com/eoan/xpad has > 5.4.0-1 > > the same as the current release https://packages.ubuntu.com/focal/xpad > > > > I tested xpad 5.0.0-1 from > > https://mirrors.edge.kernel.org/ubuntu/pool/universe/x/xpad/ on the > > current version of PopOS and the notes move back to the same workspace > > after logging out and in > > > > On Fri, May 22, 2020 at 1:10 PM Arthur Borsboom < > > 1879...@bugs.launchpad.net> wrote: > > > >> Do you know which version was being used in Pop!_OS 19.10 ? > >> Are you are able to downgrade to that version to test if it makes a > >> difference? > >> > >> On Thu, 21 May 2020 at 19:40, Alan Griffith <1879...@bugs.launchpad.net > > > >> wrote: > >> > >> > xpad 5.4.0-1 > >> > > >> > On Thu, May 21, 2020, 12:25 Arthur Borsboom < > 1879...@bugs.launchpad.net > >> > > >> > wrote: > >> > > >> > > Which version of Xpad shows this behavior? > >> > > > >> > > -- > >> > > You received this bug notification because you are subscribed to the > >> bug > >> > > report. > >> > > https://bugs.launchpad.net/bugs/1879976 > >> > > > >> > > Title: > >> > > pads revert to same workspace after loging out and back in > >> > > > >> > > Status in Xpad: > >> > > New > >> > > Status in Ubuntu: > >> > > New > >> > > > >> > > Bug description: > >> > > pads revert to same workspace after logging out and back in > >> > > This started happening after upgrading to Pop!_OS 20.04 LTS from > >> 19.10. > >> > > > >> > > To manage notifications about this bug go to: > >> > > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > >> > > > >> > > >> > -- > >> > You received this bug notification because you are subscribed to Xpad. > >> > Matching subscriptions: Arthur Borsboom > >> > https://bugs.launchpad.net/bugs/1879976 > >> > > >> > Title: > >> > pads revert to same workspace after loging out and back in > >> > > >> > Status in Xpad: > >> > New > >> > Status in Ubuntu: > >> > New > >> > > >> > Bug description: > >> > pads revert to same workspace after logging out and back in > >> > This started happening after upgrading to Pop!_OS 20.04 LTS from > >> 19.10. > >> > > >> > To manage notifications about this bug go to: > >> > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > >> > > >> > >> > >> -- > >> Arthur Borsboom > >> Phone: +31629089953 > >> > >> -- > >> You received this bug notification because you are subscribed to the bug > >> report. > >> https://bugs.launchpad.net/bugs/1879976 > >> > >> Title: > >> pads revert to same workspace after loging out and back in > >> > >> Status in Xpad: > >> New > >> Status in Ubuntu: > >> New > >> > >> Bug description: > >> pads revert to same workspace after logging out and back in > >> This started happening after upgrading to Pop!_OS 20.04 LTS from > 19.10. > >> > >> To manage notifications about this bug go to: > >> https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > >> > > > > -- > You received this bug notification because you are subscribed to Xpad. > Matching subscriptions: Arthur Borsboom > https://bugs.launchpad.net/bugs/1879976 > > Title: > pads revert to same workspace after loging out and back in > > Status in Xpad: > New > Status in Ubuntu: > New > > Bug description: > pads revert to same workspace after logging out and back in > This started happening after upgrading to Pop!_OS 20.04 LTS from 19.10. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > -- Arthur Borsboom Phone: +31629089953 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1879976] Re: pads revert to same workspace after loging out and back in
Do you know which version was being used in Pop!_OS 19.10 ? Are you are able to downgrade to that version to test if it makes a difference? On Thu, 21 May 2020 at 19:40, Alan Griffith <1879...@bugs.launchpad.net> wrote: > xpad 5.4.0-1 > > On Thu, May 21, 2020, 12:25 Arthur Borsboom <1879...@bugs.launchpad.net> > wrote: > > > Which version of Xpad shows this behavior? > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1879976 > > > > Title: > > pads revert to same workspace after loging out and back in > > > > Status in Xpad: > > New > > Status in Ubuntu: > > New > > > > Bug description: > > pads revert to same workspace after logging out and back in > > This started happening after upgrading to Pop!_OS 20.04 LTS from 19.10. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > > > > -- > You received this bug notification because you are subscribed to Xpad. > Matching subscriptions: Arthur Borsboom > https://bugs.launchpad.net/bugs/1879976 > > Title: > pads revert to same workspace after loging out and back in > > Status in Xpad: > New > Status in Ubuntu: > New > > Bug description: > pads revert to same workspace after logging out and back in > This started happening after upgrading to Pop!_OS 20.04 LTS from 19.10. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > -- Arthur Borsboom Phone: +31629089953 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879976] Re: pads revert to same workspace after loging out and back in
Which version of Xpad shows this behavior? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525656] Re: Update Xpad to bugfix release 4.8
Yes, I agree. In the past I have contacted Bart Martens (Debian package maintainer for Xpad) many times, but he hasn't responded a single time. So that seems to be a death end. If you know a different option, go for it. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525656 Title: Update Xpad to bugfix release 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1525656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525656] Re: Update Xpad to bugfix release 4.8
Hi Amr, I have no experience with a debdiff, neither with packaging in general; I am not a package maintainer. I am only developing/maintaining the source code of the Xpad software. Are you able to create a Debian package of the latest Xpad? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525656 Title: Update Xpad to bugfix release 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1525656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1119420] Re: The notification area whitelist is missing from 13.04, making some applications unusable
** Changed in: xpad Milestone: 4.7 => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1119420 Title: The notification area whitelist is missing from 13.04, making some applications unusable To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1119420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415138] Re: xpad welcome text not selectable
** Package changed: xpad (Ubuntu) => xpad ** Changed in: xpad Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415138 Title: xpad welcome text not selectable To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1415138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385540] Re: xpad crashed with SIGSEGV in g_object_unref()
This problem has been resolved in Xpad 4.3. At this moment of writing, the latest released Xpad version is 4.5 and within one month v4.6 is expected. Please upgrade Xpad in the Debian repository. ** Changed in: xpad (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385540 Title: xpad crashed with SIGSEGV in g_object_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/1385540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273474] Re: xpad needs improvements in Unity session
*** This bug is a duplicate of bug 1310291 *** https://bugs.launchpad.net/bugs/1310291 ** This bug has been marked a duplicate of bug 1310291 Xpad isn't returned back to the Ubuntu Desktop screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273474 Title: xpad needs improvements in Unity session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/1273474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273474] Re: xpad needs improvements in Unity session
*** This bug is a duplicate of bug 1310291 *** https://bugs.launchpad.net/bugs/1310291 Confirmed Ubuntu 15.10 and Xpad 4.5 ** Also affects: xpad Importance: Undecided Status: New ** Changed in: xpad Importance: Undecided => High ** Changed in: xpad Status: New => Confirmed ** Changed in: xpad Milestone: None => 4.6 ** Changed in: xpad Assignee: (unassigned) => Arthur Borsboom (arthurborsboom) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273474 Title: xpad needs improvements in Unity session To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1273474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451170] Re: [alsa-devel] [PATCH v2- ALSA 1/3] HDA - Allow hda_jack_tbl to use another nid for pin sense
Hi Raymond, Do you need more testing on the Asus N751JK by me? Do you need help from other developers? On 6 October 2015 at 10:22, Arthur Borsboom <arthurborsb...@gmail.com> wrote: > Asus N751JK - ALC668 - hdajacksenseresults: > > - > > Nothing plugged in: > > Pin 0x12 (Internal Mic): present = No > Pin 0x14 (Internal Speaker): present = No > Pin 0x15 (Black Headphone, Left side): present = No > Pin 0x16 (Not connected): present = No > Pin 0x18 (Not connected): present = No > Pin 0x19 (Pink Mic, Left side): present = No > Pin 0x1a (Internal Speaker): present = No > Pin 0x1b (Black Mic, Left side): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Not connected): present = No > Pin 0x1f (Not connected): present = No > > --- > > Only headset plugged in: > > Pin 0x12 (Internal Mic): present = No > Pin 0x14 (Internal Speaker): present = No > Pin 0x15 (Black Headphone, Left side): present = Yes > Pin 0x16 (Not connected): present = No > Pin 0x18 (Not connected): present = No > Pin 0x19 (Pink Mic, Left side): present = No > Pin 0x1a (Internal Speaker): present = No > Pin 0x1b (Black Mic, Left side): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Not connected): present = No > Pin 0x1f (Not connected): present = No > > --- > > Only headphones plugged in: > > Pin 0x12 (Internal Mic): present = No > Pin 0x14 (Internal Speaker): present = No > Pin 0x15 (Black Headphone, Left side): present = Yes > Pin 0x16 (Not connected): present = No > Pin 0x18 (Not connected): present = No > Pin 0x19 (Pink Mic, Left side): present = No > Pin 0x1a (Internal Speaker): present = No > Pin 0x1b (Black Mic, Left side): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Not connected): present = No > Pin 0x1f (Not connected): present = No > > --- > > Only microphone plugged in: > > Pin 0x12 (Internal Mic): present = No > Pin 0x14 (Internal Speaker): present = No > Pin 0x15 (Black Headphone, Left side): present = Yes > Pin 0x16 (Not connected): present = No > Pin 0x18 (Not connected): present = No > Pin 0x19 (Pink Mic, Left side): present = No > Pin 0x1a (Internal Speaker): present = No > Pin 0x1b (Black Mic, Left side): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Not connected): present = No > Pin 0x1f (Not connected): present = No > > --- > > Only subwoofer plugged in: > > Pin 0x12 (Internal Mic): present = No > Pin 0x14 (Internal Speaker): present = No > Pin 0x15 (Black Headphone, Left side): present = No > Pin 0x16 (Not connected): present = No > Pin 0x18 (Not connected): present = No > Pin 0x19 (Pink Mic, Left side): present = No > Pin 0x1a (Internal Speaker): present = Yes > Pin 0x1b (Black Mic, Left side): present = No > Pin 0x1d (Not connected): present = No > Pin 0x1e (Not connected): present = No > Pin 0x1f (Not connected): present = No > > Note that I have used hdajackretask to assing pin 0x1a -> LFE, apparently > resulting in jack detection for the subwoofer. > > On 5 October 2015 at 06:51, Raymond Yau <superquad.vort...@gmail.com> > wrote: > >> >> > >> > Do you need any testing from my side to be able to finish the >> developing? >> > >> >> >> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1451170/comments/22 >> >> It seem that asus n550lf which also use alc668 codec but headset mic pin >> node 0x1b is detectable >> >> Can you confirm that your headset mic node is not detectable by >> hdajacksensetest ? >> >> This mean that the model "headset-sonicmaster" will be quite confusing >> when asus notebooks have different ways of headset implementation >> > > > > -- > Arthur Borsboom > Mob: +31629089953 > Email: arthurborsb...@gmail.com > Skype: Arthur Borsboom, The Hague, The Netherlands > > [image: View Arthur's LinkedIn profile] > <http://uk.linkedin.com/in/arthurborsboom> > -- Arthur Borsboom Mob: +31629089953 Email: arthurborsb...@gmail.com Skype: Arthur Borsboom, The Hague, The Netherlands [image: View Arthur's LinkedIn profile] <http://uk.linkedin.com/in/arthurborsboom> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451170 Title: [ ASUS N550LF , Realtek ALC668, Speaker, Internal] To much sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1451170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451170] Re: [alsa-devel] [PATCH v2- ALSA 1/3] HDA - Allow hda_jack_tbl to use another nid for pin sense
Asus N751JK - ALC668 - hdajacksenseresults: - Nothing plugged in: Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Left side): present = No Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = No Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No --- Only headset plugged in: Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Left side): present = Yes Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = No Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No --- Only headphones plugged in: Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Left side): present = Yes Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = No Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No --- Only microphone plugged in: Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Left side): present = Yes Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = No Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No --- Only subwoofer plugged in: Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Left side): present = No Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = Yes Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No Note that I have used hdajackretask to assing pin 0x1a -> LFE, apparently resulting in jack detection for the subwoofer. On 5 October 2015 at 06:51, Raymond Yau <superquad.vort...@gmail.com> wrote: > > > > > Do you need any testing from my side to be able to finish the developing? > > > > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1451170/comments/22 > > It seem that asus n550lf which also use alc668 codec but headset mic pin > node 0x1b is detectable > > Can you confirm that your headset mic node is not detectable by > hdajacksensetest ? > > This mean that the model "headset-sonicmaster" will be quite confusing > when asus notebooks have different ways of headset implementation > -- Arthur Borsboom Mob: +31629089953 Email: arthurborsb...@gmail.com Skype: Arthur Borsboom, The Hague, The Netherlands [image: View Arthur's LinkedIn profile] <http://uk.linkedin.com/in/arthurborsboom> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451170 Title: [ ASUS N550LF , Realtek ALC668, Speaker, Internal] To much sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1451170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332819] [NEW] Xpad - version 4.3 released
Public bug reported: Ubuntu has an old version of Xpad in the repositories, which is a stripped version of v4.2. Version 4.2 and 4.3 have been released and it is advised to add/update them in the repositories. Download latest version: https://launchpad.net/xpad Changelog V4.2: https://launchpad.net/xpad/trunk/4.2 Changelog V4.3: https://launchpad.net/xpad/trunk/4.3 ** Affects: xpad (Ubuntu) Importance: Undecided Status: New ** Tags: xpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332819 Title: Xpad - version 4.3 released To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/1332819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1119420] Re: The notification area whitelist is missing from 13.04, making some applications unusable
** Changed in: xpad Status: New = Confirmed ** Changed in: xpad Importance: Undecided = Medium ** Changed in: xpad Milestone: None = 4.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1119420 Title: The notification area whitelist is missing from 13.04, making some applications unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-ubuntu/+bug/1119420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800701] Re: init: plymouth-stop pre-start process terminated with status 1(plymouth-stop called multiple times due to race?)
I still have the message appearing in Lubuntu 14.04 arthur@AOD270:~$ dmesg | grep plymouth -i [ 17.431099] init: plymouth-stop pre-start process (1146) terminated with status 1 arthur@AOD270:~$ uname -a Linux AOD270 3.13.0-12-generic #32-Ubuntu SMP Fri Feb 21 17:45:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800701 Title: init: plymouth-stop pre-start process terminated with status 1 (plymouth-stop called multiple times due to race?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/800701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 917356] Re: Xpad needs update to version 4.1
Hi Rom, Although it is not an exact answer to your question, this might help you to decide what to do. https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/917356 Greetings, Arthur. ** Changed in: xpad (Ubuntu) Assignee: (unassigned) = Arthur Borsboom (arthurborsboom) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917356 Title: Xpad needs update to version 4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/917356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120660] Re: Kernel Panic when running 'sudo dpkg --configure -a' ?
Yep, got the same issue on trusty. The last thing on the console I see is setting up libc6:amd64 and then it changes into a black screen with a blinking cursor. When I boot by adding text to grub I see a kernel panic which I am unable to capture in a log file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120660 Title: Kernel Panic when running 'sudo dpkg --configure -a' ? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1120660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889536] Re: after removing the initial xpad note xpad closes and in next start displays ' Could not acquire name on session bus'
Hi George, I haven't received a response for more than two months. Therefore I am closing this bugreport. If the problem still exists, please let me know, then I will reopen the bugreport again. Regards, Arthur Borsboom. ** Changed in: xpad (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889536 Title: after removing the initial xpad note xpad closes and in next start displays ' Could not acquire name on session bus' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/889536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889536] Re: after removing the initial xpad note xpad closes and in next start displays ' Could not acquire name on session bus'
Haha... no problem George. Thanks for giving the feedback after all. It helps. Cheers, Arthur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889536 Title: after removing the initial xpad note xpad closes and in next start displays ' Could not acquire name on session bus' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/889536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889536] Re: after removing the initial xpad note xpad closes and in next start displays ' Could not acquire name on session bus'
Hi George, Although it is a long time ago, thanks for reporting this bug. Recently I have release a new version of Xpad v4.2, which can be found here. https://launchpad.net/xpad/+milestone/4.2 If you are still strugling with this issue, would you mind to verify if this is resolved in this new version? Regards, Arthur Borsboom. ** Changed in: xpad (Ubuntu) Status: New = Incomplete ** Changed in: xpad (Ubuntu) Assignee: (unassigned) = Arthur Borsboom (arthurborsboom) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889536 Title: after removing the initial xpad note xpad closes and in next start displays ' Could not acquire name on session bus' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpad/+bug/889536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213575] Re: ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20130517/utaddress-251)
I have the same messages in dmesg (full log attached). Below the snippets as stated in this and the duplicate bugs. [0.385033] \_SB_.PCI0:_OSC invalid UUID [0.385162] \_SB_.PCI0:_OSC invalid UUID ... [0.385179] acpi PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM [2.059650] pci :00:1d.7: EHCI: BIOS handoff failed (BIOS bug?) 01010001 ... [ 12.645198] ACPI Warning: 0x0428-0x042f SystemIO conflicts with Region \PMIO 1 (20130725/utaddress-251) [ 12.645209] ACPI Warning: 0x0428-0x042f SystemIO conflicts with Region \SWC1 2 (20130725/utaddress-251) [ 12.645227] ACPI Warning: 0x0530-0x053f SystemIO conflicts with Region \GPIO 1 (20130725/utaddress-251) [ 12.645240] ACPI Warning: 0x0500-0x052f SystemIO conflicts with Region \GPIO 1 (20130725/utaddress-251) [ 12.645245] lpc_ich: Resource conflict(s) found affecting gpio_ich I have had these messages as long as I can remember and at least with kernel 3.8, 3.10, 3.11.6, and now 3.12.0 rc7. Running Lubuntu x64. Laptop model: Acer Aspire AOD270 BIOS: v1.10 (released in october 2013) I am not having direct negative impacts, however as I understood power management can be improved, and thus battery life. Is there anything that I or the Linux community can do to fix this, or do I need to ask Acer to fix the BIOS? If I need to ask Acer to fix this, what exactly do I need to ask for? ** Attachment added: Dmesg log file https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213575/+attachment/3896164/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213575 Title: ACPI Warning: 0x0428-0x042f SystemIO conflicts with Region \PMIO 1 (20130517/utaddress-251) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907705] Re: Add a panel icon
** Changed in: xpad Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907705 Title: Add a panel icon To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/907705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907705] Re: Add a panel icon
** Changed in: xpad Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907705 Title: Add a panel icon To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/907705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907705] Re: Add a panel icon
** Tags added: icon tray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907705 Title: Add a panel icon To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/907705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907705] Re: Add a panel icon
** Changed in: xpad Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907705 Title: Add a panel icon To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/907705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907705] Re: Add a panel icon
** Changed in: xpad Milestone: None = 4.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907705 Title: Add a panel icon To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/907705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 800701] Re: init: plymouth-stop pre-start process terminated with status 1(plymouth-stop called multiple times due to race?)
I'm seeing the same error message on Lubuntu 13.10 x64. Any new suggestions to solve this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/800701 Title: init: plymouth-stop pre-start process terminated with status 1 (plymouth-stop called multiple times due to race?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/800701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190170] Re: no gui shutdown in lubuntu
I have upgraded Lubuntu x64 from 13.04 to 13.10. I believe I have the latest lxsession, however the two logout methods (by start-menu and by lxpanel) are not working for me. When I press the shutdown button on my keyboard, Lubuntu shuts down immediately. I have run dpkg-reconfigure lxsession, but it had no effect. Kernel: Linux AOD270 3.10.0-2-generic #10-Ubuntu SMP Fri Jul 5 18:03:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Lxsession: Architecture: amd64, Version: 0.4.9.2-0ubuntu5 Maybe the bug is still in the x64 version? If not, what do you suggest to fix this minor issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190170 Title: no gui shutdown in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1190170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1190170] Re: no gui shutdown in lubuntu
Hi Erick, I have fixed the issue manually, by changing the following files. /usr/share/applications/lubuntu-logout.desktop (Fixed logout/power button on the taskbar on the right) /home/arthur/.config/lxpanel/Lubuntu/config (Fixed logout button in the start menu on the left) /usr/share/lxpanel/profile/Lubuntu (no effect for current user) /usr/share/lubuntu/openbox/menu.xml (no effect for current user) /usr/share/lubuntu/openbox/rc.xml (no effect for current user) /usr/share/lubuntu/openbox/qt-rc.xml (no effect for current user) Find and replace - Find: lxsession-default quit - Replace: lxsession-logout I hope this helps to speed up the official release of Lubuntu 13.10. If I can help somewhere else, let me know. Greetings, Arthur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190170 Title: no gui shutdown in lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1190170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
