from:"Cliff"

[digikam] [Bug 421043] Faces Detection crashes digiKam

2020-10-26 Thread Cliff Albert

https://bugs.kde.org/show_bug.cgi?id=421043

--- Comment #18 from Cliff Albert  ---
Here is another backtrace. This one has been made with 
  digikam-7.2.0-beta1-20201025T154101-x86-64-debug.appimage

The machine i'm using has been updated to Ubuntu 20.10:

Linux porkstation 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

I'm guessing something is also wrong with the debugging image of the 20201025
build as gdb gives a file does not exist message:


Thread 42 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff9f7fe640 (LWP 25961)]
0x7749dc17 in Digikam::LoadingTask::progressInfo (this=0xe2fcf70,
progress=0.30012) at
/b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavetask.cpp:100
100
/b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavetask.cpp: No
such file or directory.
(gdb) bt
#0  0x7749dc17 in Digikam::LoadingTask::progressInfo (this=0xe2fcf70,
progress=0.30012) at
/b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavetask.cpp:100
#1  0x7fffc8eac945 in DigikamJPEGDImgPlugin::DImgJPEGLoader::load
(this=0x7fff882da0f0, filePath=..., observer=0xe2fcf80) at
/b/dktemp/digikam-master/core/dplugins/dimg/jpeg/dimgjpegloader_load.cpp:443
#2  0x773af3aa in Digikam::DImg::load (this=this@entry=0xe2fd150,
filePath=..., loadFlagsInt=loadFlagsInt@entry=63,
observer=observer@entry=0xe2fcf80, rawDecodingSettings=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_fileio.cpp:132
#3  0x773b0400 in Digikam::DImg::load (this=this@entry=0xe2fd150,
filePath=..., observer=observer@entry=0xe2fcf80, rawDecodingSettings=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_fileio.cpp:62
#4  0x7747d02e in Digikam::PreviewLoadingTask::execute (this=0xe2fcf70)
at /b/dktemp/digikam-master/core/libs/threadimageio/preview/previewtask.cpp:310
#5  0x77492ffe in Digikam::LoadSaveThread::run (this=0xe2796c0) at
/b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavethread.cpp:154
#6  0x774b796e in Digikam::DynamicThread::Private::run (this=0xde6e7b0)
at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:191
#7  0x74180d87 in ?? () from
/tmp/.mount_digikaUIYI90/usr/lib/libQt5Core.so.5
#8  0x7417d335 in ?? () from
/tmp/.mount_digikaUIYI90/usr/lib/libQt5Core.so.5
#9  0x73b0e590 in start_thread (arg=0x7fff9f7fe640) at
pthread_create.c:463
#10 0x73a34223 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 421043] Faces Detection crashes digiKam

2020-10-19 Thread Cliff Albert

https://bugs.kde.org/show_bug.cgi?id=421043

--- Comment #15 from Cliff Albert  ---
I don't know if the patch already made it to
digikam-7.2.0-beta1-20201016T092735-x86-64-debug.appimage, but here is another
slightly different backtrace:

Thread 29 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff74dea700 (LWP 519207)]
0x7423e9d4 in ?? () from
/tmp/.mount_digikaj6ug8P/usr/lib/libQt5Core.so.5
(gdb) bt
#0  0x7423e9d4 in ?? () from
/tmp/.mount_digikaj6ug8P/usr/lib/libQt5Core.so.5
#1  0x742431d0 in operator<(QString const&, QString const&) () from
/tmp/.mount_digikaj6ug8P/usr/lib/libQt5Core.so.5
#2  0x773c8700 in qMapLessThanKey (key2=..., key1=...) at
././/include/QtCore/qmap.h:68
#3  QMapNode::lowerBound (akey=..., this=) at
././/include/QtCore/qmap.h:152
#4  QMapData::findNode (this=, akey=...) at
././/include/QtCore/qmap.h:284
#5  0x773c4a13 in QMap::contains (akey=...,
this=) at ././/include/QtCore/qmap.h:693
#6  Digikam::DImg::hasAttribute (this=this@entry=0xa71c9c0, key=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_props.cpp:254
#7  0x773c08a9 in Digikam::DImg::getUniqueHashV2 (this=0xa71c9c0) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_metadata.cpp:76
#8  0x773c2135 in Digikam::DImg::createHistoryImageId (this=, filePath=..., type=type@entry=Digikam::HistoryImageId::Current) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_metadata.cpp:328
#9  0x7725b9dd in Digikam::DImgLoader::readMetadata
(this=0x7fff5807d7e0, filePath=...) at
/b/dktemp/digikam-master/core/libs/dimg/loaders/dimgloader.cpp:229
#10 0x7fffc90c3ff9 in DigikamJPEGDImgPlugin::DImgJPEGLoader::load
(this=0x7fff5807d7e0, filePath=..., observer=0xa71c7f0) at
/b/dktemp/digikam-master/core/dplugins/dimg/jpeg/dimgjpegloader_load.cpp:56
#11 0x773bd66a in Digikam::DImg::load (this=this@entry=0xa71c9c0,
filePath=..., loadFlagsInt=loadFlagsInt@entry=63,
observer=observer@entry=0xa71c7f0, rawDecodingSettings=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_fileio.cpp:132
#12 0x773be6c0 in Digikam::DImg::load (this=this@entry=0xa71c9c0,
filePath=..., observer=observer@entry=0xa71c7f0, rawDecodingSettings=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_fileio.cpp:62
#13 0x774890ae in Digikam::PreviewLoadingTask::execute (this=0xa71c7e0)
at /b/dktemp/digikam-master/core/libs/threadimageio/preview/previewtask.cpp:310
#14 0x7749f07e in Digikam::LoadSaveThread::run (this=0xa670050) at
/b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavethread.cpp:154
#15 0x774c36fe in Digikam::DynamicThread::Private::run (this=0xa6678c0)
at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:191
#16 0x741a4d87 in ?? () from
/tmp/.mount_digikaj6ug8P/usr/lib/libQt5Core.so.5
#17 0x741a1335 in ?? () from
/tmp/.mount_digikaj6ug8P/usr/lib/libQt5Core.so.5
#18 0x73b31609 in start_thread (arg=) at
pthread_create.c:477
#19 0x73a58293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

-- 
You are receiving this mail because:
You are watching all bug changes.

[Bug 1896393] Re: gedit not responding to keystrokes

2020-10-16 Thread Cliff Carson

Problem is indeed intermittent.  Dumped systemctl -b 0 | tail -n 100
after noticing the failure/delay and see nothing in the messages (many
time no messages at all at the time of delay).  Another indicator of a
delay failure is when starting to edit new script then mouse wheel
(trying to page down in the file) fails to react for several seconds
(5-10 sec) then the screen pages.  The system monitor running at the
time shows normal low activity.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1896393] Re: gedit not responding to keystrokes

2020-10-16 Thread Cliff Carson

Problem is indeed intermittent.  Dumped systemctl -b 0 | tail -n 100
after noticing the failure/delay and see nothing in the messages (many
time no messages at all at the time of delay).  Another indicator of a
delay failure is when starting to edit new script then mouse wheel
(trying to page down in the file) fails to react for several seconds
(5-10 sec) then the screen pages.  The system monitor running at the
time shows normal low activity.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

Status in gedit package in Ubuntu:
  New

Bug description:
  Don't know how to further document this except was is observed during
  the gedit session.

  While typing information into the gedit window the keystrokes get
  delayed 1-2 seconds from the time the keys are struct and when the
  character(s) show up on the screen.  It's as if the system was too
  busy to service the key input but that doesn't appear to be the case.
  This problem doesn't occur on the current gedit running under 20.04.

  Any suggestions on how to document this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gedit 3.36.2-1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 13:03:43 2020
  InstallationDate: Installed on 2020-08-28 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1896393] Re: gedit not responding to keystrokes

2020-10-16 Thread Cliff Carson

Problem is indeed intermittent.  Dumped systemctl -b 0 | tail -n 100
after noticing the failure/delay and see nothing in the messages (many
time no messages at all at the time of delay).  Another indicator of a
delay failure is when starting to edit new script then mouse wheel
(trying to page down in the file) fails to react for several seconds
(5-10 sec) then the screen pages.  The system monitor running at the
time shows normal low activity.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[digikam] [Bug 421043] Faces Detection crashes digiKam

2020-10-15 Thread Cliff Albert

https://bugs.kde.org/show_bug.cgi?id=421043

Cliff Albert  changed:

   What|Removed |Added

 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1

--- Comment #13 from Cliff Albert  ---
Unfortunately the same error is popping up again with
digikam-7.2.0-beta1-20201013T065929-x86-64-debug.appimage running on Ubuntu
20.04.1 (Linux porkstation 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux)


[New Thread 0x7ffefdffb700 (LWP 19929)]
[Thread 0x7fffb508a700 (LWP 19928) exited]
[Thread 0x7ffefdffb700 (LWP 19929) exited]
Digikam::DImg::getUniqueHashV2: DImg::getUniqueHash called without
originalFilePath property set!
Thread 67 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff5f015700 (LWP 17252)]
0x741e13e1 in QMapDataBase::rebalance(QMapNodeBase*) () from
/tmp/.mount_digikay5n2NY/usr/lib/libQt5Core.so.5

(gdb) bt
#0  0x741e13e1 in QMapDataBase::rebalance(QMapNodeBase*) () from
/tmp/.mount_digikay5n2NY/usr/lib/libQt5Core.so.5
#1  0x741e19c4 in QMapDataBase::createNode(int, int, QMapNodeBase*,
bool) () from /tmp/.mount_digikay5n2NY/usr/lib/libQt5Core.so.5
#2  0x773c6183 in QMapData::createNode
(left=, parent=0x7fff6191f4e0, v=..., k=..., this=) at ././/include/QtCore/qmap.h:223
#3  QMap::insert (avalue=..., akey=..., this=0x7fff5401b540)
at ././/include/QtCore/qmap.h:719
#4  Digikam::DImg::setAttribute (this=, key=..., value=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_props.cpp:235
#5  0x7725a519 in Digikam::DImgLoader::imageSetAttribute
(this=, key=..., value=...) at
/b/dktemp/digikam-master/core/libs/dimg/loaders/dimgloader.cpp:142
#6  0x7725ba42 in Digikam::DImgLoader::readMetadata
(this=0x7fff619261c0, filePath=...) at
/b/dktemp/digikam-master/core/libs/dimg/loaders/dimgloader.cpp:233
#7  0x7fffc90c3ff9 in DigikamJPEGDImgPlugin::DImgJPEGLoader::load
(this=0x7fff619261c0, filePath=..., observer=0xaa53840) at
/b/dktemp/digikam-master/core/dplugins/dimg/jpeg/dimgjpegloader_load.cpp:56
#8  0x773bd66a in Digikam::DImg::load (this=this@entry=0xaa53a10,
filePath=..., loadFlagsInt=loadFlagsInt@entry=63,
observer=observer@entry=0xaa53840, rawDecodingSettings=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_fileio.cpp:132
#9  0x773be6c0 in Digikam::DImg::load (this=this@entry=0xaa53a10,
filePath=..., observer=observer@entry=0xaa53840, rawDecodingSettings=...) at
/b/dktemp/digikam-master/core/libs/dimg/dimg_fileio.cpp:62
#10 0x774890ae in Digikam::PreviewLoadingTask::execute (this=0xaa53830)
at /b/dktemp/digikam-master/core/libs/threadimageio/preview/previewtask.cpp:310
#11 0x7749f07e in Digikam::LoadSaveThread::run (this=0x2398ab0) at
/b/dktemp/digikam-master/core/libs/threadimageio/fileio/loadsavethread.cpp:154
#12 0x774c370e in Digikam::DynamicThread::Private::run (this=0xa4acef0)
at /b/dktemp/digikam-master/core/libs/threads/dynamicthread.cpp:191
#13 0x741a4d87 in ?? () from
/tmp/.mount_digikay5n2NY/usr/lib/libQt5Core.so.5
#14 0x741a1335 in ?? () from
/tmp/.mount_digikay5n2NY/usr/lib/libQt5Core.so.5
#15 0x73b31609 in start_thread (arg=) at
pthread_create.c:477
#16 0x73a58293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

-- 
You are receiving this mail because:
You are watching all bug changes.

RE: pharmacy

2020-10-09 Thread cliff--- via Sprinklerforum

Maybe in a Galaxy far, far away - but not in this world that I'm aware of.

Cliff Whitfield

-Original Message-
From: Sprinklerforum  On Behalf 
Of Travis Mack via Sprinklerforum
Sent: Friday, October 9, 2020 5:20 PM
To: sprinklerforum@lists.firesprinkler.org
Cc: travis.m...@mfpdesign.com
Subject: pharmacy

Is there any world where a small pharmacy - say 1000 sq ft - could be 
considered light hazard?  The plans show racks for the storage of the meds / 
pill bottles.  Dealing with some issues on a pre-engineered job that the FPE 
did it as LH.  The problem compounds when the water supply is very marginal and 
the jurisdiction does not all QR reduction for OH areas.

Travis Mack, CFPS, CWBSP, RME-G, SET
Engineering Manager
MFP Design
3356 E Vallejo Ct
Gilbert, AZ 85298
NEW EXTENSION: 480-505-9271 ext. 700
NEW MOBILE: 480-272-2471
travis.m...@mfpdesign.com
www.mfpdesign.com

Send large files to us via: https://www.hightail.com/u/MFPDesign
LinkedIn: https://www.linkedin.com/in/travismack

“The bitterness of poor quality remains long after the sweetness of low price 
is forgotten.”

Need/Want a faster way to check material pricing?  Build a material quote?  
Check availability ?   Searching for an invoice?
*If you do not already have an account with ferguson.com, click here to 
register.* **Have a Ferguson account? Download the Ferguson app for on-the-go 
access to your favorite ferguson.com features. Apple iOS devices or Android 
devices**

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org

-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org

[jira] [Commented] (CONFIGURATION-793) Error reading a list of complex objects from JSON after 2.3

2020-10-06 Thread Cliff Evans (Jira)



[ 
https://issues.apache.org/jira/browse/CONFIGURATION-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17208846#comment-17208846
 ] 

Cliff Evans commented on CONFIGURATION-793:
---

Unfortunately, coming up with a fix looks way too complex for the time I have 
available.  What I have been able to do though, is rework my original test to 
work with the test that [~oheger] added when the change that introduced the bug 
was done.  I wouldn't be sure whether the right place for the fix would be 
around 
org.apache.commons.configuration2.AbstractYAMLBasedConfiguration#constructHierarchy,
 or in the code that accessed the in memory copy of the configuration.  I hope 
that this might help zero in on the issue and lead someone more skilled than I 
to the correct fix for it.  I've updated the main description above with this 
information.

> Error reading a list of complex objects from JSON after 2.3
> ---
>
> Key: CONFIGURATION-793
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-793
> Project: Commons Configuration
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: JDK 11.0.4
>Reporter: Cliff Evans
>Priority: Major
>
> We have just attempted to move from version 2.2 to 2.7 and have encountered 
> and issue whilst attempting to read a List from a JSON formatted 
> configuration file.
> The issue appears to have been introduced in 2.3.
> Adding the following tests to 
> org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
> change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)
> https://issues.apache.org/jira/browse/CONFIGURATION-686 appears to have fixed 
> access to lists of complex objects using the dot notation for strings (see 
> testGetProperty_dictionaryInList() in TestJSONConfiguration) but has broken 
> access to the list of complex objects.
>  
> {noformat}
> @Test
> public void testGetList_nested_with_list()
> {
> assertEquals(Arrays.asList("col1", "col2"),
>  jsonConfiguration.getList(String.class, "key4.key5"));
> }
> @Test
> public void testGetList() {
> final List configList = jsonConfiguration.getList(Map.class, 
> "capitals");
> assertEquals(configList.size(), 2);
> assertEquals(configList.get(0).get("country"), "USA");
> assertEquals(configList.get(0).get("capital"), "Washington");
> assertEquals(configList.get(1).get("country"), "UK");
> assertEquals(configList.get(1).get("capital"), "London");
> }
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONFIGURATION-793) Error reading a list of complex objects from JSON after 2.3

2020-10-06 Thread Cliff Evans (Jira)



 [ 
https://issues.apache.org/jira/browse/CONFIGURATION-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cliff Evans updated CONFIGURATION-793:
--
Description: 
We have just attempted to move from version 2.2 to 2.7 and have encountered and 
issue whilst attempting to read a List from a JSON formatted configuration file.

The issue appears to have been introduced in 2.3.

Adding the following tests to 
org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)

https://issues.apache.org/jira/browse/CONFIGURATION-686 appears to have fixed 
access to lists of complex objects using the dot notation for strings (see 
testGetProperty_dictionaryInList() in TestJSONConfiguration) but has broken 
access to the list of complex objects.

 
{noformat}
@Test
public void testGetList_nested_with_list()
{
assertEquals(Arrays.asList("col1", "col2"),
 jsonConfiguration.getList(String.class, "key4.key5"));
}

@Test
public void testGetList() {
final List configList = jsonConfiguration.getList(Map.class, 
"capitals");

assertEquals(configList.size(), 2);
assertEquals(configList.get(0).get("country"), "USA");
assertEquals(configList.get(0).get("capital"), "Washington");
assertEquals(configList.get(1).get("country"), "UK");
assertEquals(configList.get(1).get("capital"), "London");
}
{noformat}
 

  was:
We have just attempted to move from version 2.2 to 2.7 and have encountered and 
issue whilst attempting to read a List from a JSON formatted configuration file.

The issue appears to have been introduced in 2.3.

Adding the following tests to 
org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)

 
{noformat}
@Test
public void testGetList_nested_with_list()
{
assertEquals(Arrays.asList("col1", "col2"),
 jsonConfiguration.getList(String.class, "key4.key5"));
}

@Test
public void testGetList() {
final List configList = jsonConfiguration.getList(Map.class, 
"capitals");

assertEquals(configList.size(), 2);
assertEquals(configList.get(0).get("country"), "USA");
assertEquals(configList.get(0).get("capital"), "Washington");
assertEquals(configList.get(1).get("country"), "UK");
assertEquals(configList.get(1).get("capital"), "London");
}
{noformat}
 


> Error reading a list of complex objects from JSON after 2.3
> ---
>
> Key: CONFIGURATION-793
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-793
> Project: Commons Configuration
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: JDK 11.0.4
>Reporter: Cliff Evans
>Priority: Major
>
> We have just attempted to move from version 2.2 to 2.7 and have encountered 
> and issue whilst attempting to read a List from a JSON formatted 
> configuration file.
> The issue appears to have been introduced in 2.3.
> Adding the following tests to 
> org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
> change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)
> https://issues.apache.org/jira/browse/CONFIGURATION-686 appears to have fixed 
> access to lists of complex objects using the dot notation for strings (see 
> testGetProperty_dictionaryInList() in TestJSONConfiguration) but has broken 
> access to the list of complex objects.
>  
> {noformat}
> @Test
> public void testGetList_nested_with_list()
> {
> assertEquals(Arrays.asList("col1", "col2"),
>  jsonConfiguration.getList(String.class, "key4.key5"));
> }
> @Test
> public void testGetList() {
> final List configList = jsonConfiguration.getList(Map.class, 
> "capitals");
> assertEquals(configList.size(), 2);
> assertEquals(configList.get(0).get("country"), "USA");
> assertEquals(configList.get(0).get("capital"), "Washington");
> assertEquals(configList.get(1).get("country"), "UK");
> assertEquals(configList.get(1).get("capital"), "London");
> }
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONFIGURATION-793) Error reading a list of complex objects from JSON after 2.3

2020-10-06 Thread Cliff Evans (Jira)



 [ 
https://issues.apache.org/jira/browse/CONFIGURATION-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cliff Evans updated CONFIGURATION-793:
--
Summary: Error reading a list of complex objects from JSON after 2.3  (was: 
Error reading a list from JSON after 2.3)

> Error reading a list of complex objects from JSON after 2.3
> ---
>
> Key: CONFIGURATION-793
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-793
> Project: Commons Configuration
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: JDK 11.0.4
>Reporter: Cliff Evans
>Priority: Major
>
> We have just attempted to move from version 2.2 to 2.7 and have encountered 
> and issue whilst attempting to read a List from a JSON formatted 
> configuration file.
> The issue appears to have been introduced in 2.3.
> Adding the following tests to 
> org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
> change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)
>  
> {noformat}
> @Test
> public void testGetList_nested_with_list()
> {
> assertEquals(Arrays.asList("col1", "col2"),
>  jsonConfiguration.getList(String.class, "key4.key5"));
> }
> @Test
> public void testGetList() {
> final List configList = jsonConfiguration.getList(Map.class, 
> "capitals");
> assertEquals(configList.size(), 2);
> assertEquals(configList.get(0).get("country"), "USA");
> assertEquals(configList.get(0).get("capital"), "Washington");
> assertEquals(configList.get(1).get("country"), "UK");
> assertEquals(configList.get(1).get("capital"), "London");
> }
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (CONFIGURATION-793) Error reading a list from JSON after 2.3

2020-10-06 Thread Cliff Evans (Jira)



 [ 
https://issues.apache.org/jira/browse/CONFIGURATION-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Cliff Evans updated CONFIGURATION-793:
--
Description: 
We have just attempted to move from version 2.2 to 2.7 and have encountered and 
issue whilst attempting to read a List from a JSON formatted configuration file.

The issue appears to have been introduced in 2.3.

Adding the following tests to 
org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)

 
{noformat}
@Test
public void testGetList_nested_with_list()
{
assertEquals(Arrays.asList("col1", "col2"),
 jsonConfiguration.getList(String.class, "key4.key5"));
}

@Test
public void testGetList() {
final List configList = jsonConfiguration.getList(Map.class, 
"capitals");

assertEquals(configList.size(), 2);
assertEquals(configList.get(0).get("country"), "USA");
assertEquals(configList.get(0).get("capital"), "Washington");
assertEquals(configList.get(1).get("country"), "UK");
assertEquals(configList.get(1).get("capital"), "London");
}
{noformat}
 

  was:
We have just attempted to move from version 2.2 to 2.7 and have encountered and 
issue whilst attempting to read a List from a JSON formatted configuration file.

The issue appears to have been introduced in 2.3.

The test below demonstrates the issue.  This test will pass against 2.2 but 
fail agains 2.3 (and 2.7.)

 
{noformat}
package org.apache.commons.configuration2;

import org.apache.commons.configuration2.ex.ConfigurationException;
import org.junit.Test;

import java.io.ByteArrayInputStream;
import java.io.InputStream;
import java.util.List;
import java.util.Map;

import static java.nio.charset.StandardCharsets.UTF_8;
import static org.junit.Assert.assertNotNull;

public class ConfigurationTest {

   private static final String JSON = "{\n" +
  "\"myList\": [\n" +
  "{\n" +
  "  \"att1\": \"one\"\n" +
  "}\n" +
  "]" +
  "}\n";

   @Test
   public void loadConfiguration()
 throws ConfigurationException {
  JSONConfiguration jsonConfiguration = new JSONConfiguration();
  InputStream inputStream = new ByteArrayInputStream(JSON.getBytes(UTF_8));
  jsonConfiguration.read(inputStream);

  final List configList = jsonConfiguration.getList(Map.class, 
"myList");

  assertNotNull(configList);
   }

}
{noformat}
 


> Error reading a list from JSON after 2.3
> 
>
> Key: CONFIGURATION-793
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-793
> Project: Commons Configuration
>  Issue Type: Bug
>Affects Versions: 2.3
> Environment: JDK 11.0.4
>Reporter: Cliff Evans
>Priority: Major
>
> We have just attempted to move from version 2.2 to 2.7 and have encountered 
> and issue whilst attempting to read a List from a JSON formatted 
> configuration file.
> The issue appears to have been introduced in 2.3.
> Adding the following tests to 
> org.apache.commons.configuration2.TestJSONConfiguration will demonstrate the 
> change.  These tests will pass against 2.2 but fail agains 2.3 (and 2.7.)
>  
> {noformat}
> @Test
> public void testGetList_nested_with_list()
> {
> assertEquals(Arrays.asList("col1", "col2"),
>  jsonConfiguration.getList(String.class, "key4.key5"));
> }
> @Test
> public void testGetList() {
> final List configList = jsonConfiguration.getList(Map.class, 
> "capitals");
> assertEquals(configList.size(), 2);
> assertEquals(configList.get(0).get("country"), "USA");
> assertEquals(configList.get(0).get("capital"), "Washington");
> assertEquals(configList.get(1).get("country"), "UK");
> assertEquals(configList.get(1).get("capital"), "London");
> }
> {noformat}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: [Gimp-user] text mode, need instruct sequence

2020-10-05 Thread Cliff Pratt via gimp-user-list

Ok, I now have 2.8.22 running in Ubuntu in a VM. That's as close as I can
get to your setup - Debian 9 and Gimp 2.8.?.

This is vanilla, out of the box, no configuration.

I created a new blank image, and selected the text tool. In the Tool
Options the font is "Sans", the size is 18 px and the colour is black.

In the tool options I change the font to "Serif", size to 36 px and the
colour to green. All this in theText Tool Options. *Note that this changes
the default foreground colour to green*.

I click on the canvas and drag to get a text box. Type "Abcd". The font is
"Serif" and the colour is green, and the size shows as 36 px.

I decide that I want the test to be blue and 42 px and the font to be sans.
I make sure the text box is selected.

I click the font button and select "Sans" in the drop down list in the Tool
Options. The text immediately changes to Sans. It stays green and 36 px.

I change the colour to blue and the size to 42 px in the Tool Options.
Those attributes change immediately. Changing one has no effect on the
other and changes are immediate.

*Note that this does not change the default foreground colour which remains
green*.

If I click and drag another text box elsewhere, it takes the size and the
font from the first box, but it shows the colour from the default
foreground when I type some text. But if I type some text and* then *change
the colour in the tool options it doesn't change the default foreground
colour.

I haven't seen it 'reset' any other options. If I had to guess, I'd guess
that you have another, invisible text box, you've clicked in that and it
uses the font and size option from that box. That's why I asked how many
layers you have.

Cheers,

Cliff

On Sat, Oct 3, 2020 at 10:05 AM Gene Heskett  wrote:

> Greetings all;
>
> I, like Ruben Safir, am A. tired of the lack of good docs, and B. the
> churn in how it works. I just had occasion to caption some pix as an aid
> to my wife who is not a computer whiz, in setting up a piano keyboard,
> and the air was quite blue around me by the time I got done because
> every time I tried to set one option in the text panel it reset
> everything else back to the defaults.  And an 18 px black character
> isn't more than a visible dot on an 8x10 printout, so I click on the
> size and add a zero to make 180 px. Then I am going to put it in a black
> area of the printout, so I select the color white and hit enter and it
> resets the size to 18px and the font back to sans from sans serif. Thats
> bs at its finest.  So is the text box when its under the top ruler and
> you can't see that its decided to reset everything back to the defaults.
> So please tell me the correct sequence of key or mouse strokes to set
> that up and if possible set it as the defaults so I don't have to get so
> frustrated just to add a line or 3 of text captions to a picture.
> You've made 4 hours of very frustrating work out of captioning 6 photo's
> that ought to be 3 minutes plus print time each. If this worked. But
> IMNSHO it sucks dead toads thru soda straws. So please make it
> _Just_Work_, write some docs that tell us how to use it, and then stop
> the churn.
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/gene>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>

-- 
My Amazon author page : https://amazon.com/author/cliffpratt
My Facebook author page : https://www.facebook.com/cliffprattauthor
My Search on Kobo : https://www.kobo.com/search?query=Cliff+Pratt
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] text mode, need instruct sequence

2020-10-03 Thread Cliff Pratt via gimp-user-list

There's a flatpak on gimp.org. If you want a Debian version, there is one
of those too, available through the debian repositories. Both
2.10.something. Where did you get your 2.8 version from?

Cliff

On Sun, Oct 4, 2020 at 5:26 PM Gene Heskett  wrote:

> On Sunday 04 October 2020 00:10:53 Rick Strong wrote:
>
> > Here's an ex cathedra thought: why don't you upgrade to version 2.10?
> >
> I grabbed the bz2 srcs about an hour ago but theres too many missing
> dependencies.  Is there a downloadble deb that will install of stretch?
>
> > Cheers,
> > RS
>
>
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page <http://geneslinuxbox.net:6309/gene>
> ___
> gimp-user-list mailing list
> List address:gimp-user-list@gnome.org
> List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
> List archives:   https://mail.gnome.org/archives/gimp-user-list
>


-- 
My Amazon author page : https://amazon.com/author/cliffpratt
My Facebook author page : https://www.facebook.com/cliffprattauthor
My Search on Kobo : https://www.kobo.com/search?query=Cliff+Pratt
___
gimp-user-list mailing list
List address:gimp-user-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
List archives:   https://mail.gnome.org/archives/gimp-user-list

Re: [Gimp-user] text mode, need instruct sequence

2020-10-03 Thread Cliff Pratt via gimp-user-list

I'm using 2.10.20 and it works as I describe above. I have been using the
Gimp since 2.8 and before, and it has always worked that way.

What version are you using, and did you try what I described or did you
just read it?

How many text layers do you have?

Cliff

On Sun, Oct 4, 2020 at 4:33 PM Gene Heskett  wrote:

> On Saturday 03 October 2020 21:23:35 Cliff Pratt via gimp-user-list
> wrote:
>
> > Hm, how many text layers do you have?
> >
> > If I create a text layer I can create it with the particular font and
> > font size. When I create another text layer, I can set the font, etc
> > in the new layer to something different. If I then decide that the
> > font is wrong in the first text layer, and I select that text layer,
> > it comes up with the font and font size that I selected in the first
> > place ie, what it was when I left that layer. If I go back to the
> > other text layer it shows the font and font size that it was when I
> > left THAT layer.
> >
> > So
> > 1) I create a text box/layer (call it One), set the font to something,
> > and the font size to 16 pts. I type something eg One. [I create a text
> > box by clicking on the text tool, and clicking on the canvas.]
> > 2) I create a second text box/layer. (call it Two). I set the font to
> > 64 pts. I type something eg Two. [I create a new text box by clicking
> > somewhere outside the first text box.]
> > 3) I decide that the font size in One is too small. I switch to that
> > text layer [By clicking in the text box.]. *The font size now shows 16
> > pts*. I change the font size. I don't delete the text. I just change
> > the font size (to say 32 pts).
> > 4) I switch to layer Two. *The font size now shows 64 pts*.
> > 5) If I switch between text layers the font size alternates between 16
> > and 64 pts.
> >
> > Each 'line of text' is in a separate text layer. Each text layer
> > retains the font, font size and other attributes that it had when you
> > last left it. Any new layer contains the attributes of the previous
> > text layer that you created.
> >
> > Cheers,
> >
> > Cliff
> >
> > On Sat, Oct 3, 2020 at 11:02 PM Rick Strong  wrote:
> > > My eyes are nearly 80 years old, I am going blind in one of them and
> > > I can easily read 18 pt type.
> > > Anyway, you need something larger. OK. Try double clicking on the
> > > "A" tool and setting the type specs in the dialogue/tab that comes
> > > up on the right. Screenshot attached. I assume you are using the
> > > latest version.
> > >
> > > Rick
> > >
> > > -Original Message-
> > > From: Gene Heskett
> > > Sent: Friday, October 02, 2020 7:38 PM
> > > To: Rick Strong
> > > Cc: gimp-user-list@gnome.org
> > > Subject: Re: [Gimp-user] text mode, need instruct sequence
> > >
> > > On Friday 02 October 2020 18:36:07 you wrote:
> > > > Gene,
> > > >
> > > > By my reckoning, an 18 px letter is less than 1 pt high on an 300
> > > > dpi print—virtually invisible. Try setting the text size to 18
> > > > pts. (POINTS, not pixels) to be legible.
> > >
> > > I have done that, Rick, but 18 pts isn't near big enough for older
> > > eyes either, so you backspace to get rid of the dust specs, look up
> > > to the text box and its reset to 18px. Frustrating is a very weak
> > > description. You spend 10 minutes bounceing from one place in that
> > > tool, to another trying to get it to keep what you selected long
> > > enough to type one line of text. Repeat for every line of text you
> > > want to overlay on a pix.
> > >
> > > > Good luck.
> > >
> > > I don't need luck, I need instructions that work, please read my
> > > whole message.
>
> And so far, for all the pontificating here, none of which seems to apply
> to the 2.8 I am trying to use. That alone is more than ample evidence of
> the control churn as far as I am concerned.  I have changed the font,
> color and size, then clicked save at the bottom of my tool edit window
> until I've about wore out the mouse and the save button.  But the next
> time I launch GIMP, its still black, sans, and 18 px.  If you can make
> 2.8 text Just Work so setting one thing does NOT restore the totally
> useless defaults for everything else, AND the save and restore buttons
> actually do that, I need the exact sequence of operations that ACTUALLY
> DO make it work in the 2.8 being published by debian.
>
> OR push debian to update it to your version of 2.10

Re: [Gimp-user] text mode, need instruct sequence

2020-10-03 Thread Cliff Pratt via gimp-user-list

Hm, how many text layers do you have?

If I create a text layer I can create it with the particular font and font
size. When I create another text layer, I can set the font, etc in the new
layer to something different. If I then decide that the font is wrong in
the first text layer, and I select that text layer, it comes up with the
font and font size that I selected in the first place ie, what it was when
I left that layer. If I go back to the other text layer it shows the font
and font size that it was when I left THAT layer.

So
1) I create a text box/layer (call it One), set the font to something, and
the font size to 16 pts. I type something eg One. [I create a text box by
clicking on the text tool, and clicking on the canvas.]
2) I create a second text box/layer. (call it Two). I set the font to 64
pts. I type something eg Two. [I create a new text box by clicking
somewhere outside the first text box.]
3) I decide that the font size in One is too small. I switch to that text
layer [By clicking in the text box.]. *The font size now shows 16 pts*. I
change the font size. I don't delete the text. I just change the font size
(to say 32 pts).
4) I switch to layer Two. *The font size now shows 64 pts*.
5) If I switch between text layers the font size alternates between 16 and
64 pts.

Each 'line of text' is in a separate text layer. Each text layer retains
the font, font size and other attributes that it had when you last left it.
Any new layer contains the attributes of the previous text layer that you
created.

Cheers,

Cliff

On Sat, Oct 3, 2020 at 11:02 PM Rick Strong  wrote:

> My eyes are nearly 80 years old, I am going blind in one of them and I can
> easily read 18 pt type.
> Anyway, you need something larger. OK. Try double clicking on the "A" tool
> and setting the type specs in the dialogue/tab that comes up on the right.
> Screenshot attached. I assume you are using the latest version.
>
> Rick
>
> -Original Message-
> From: Gene Heskett
> Sent: Friday, October 02, 2020 7:38 PM
> To: Rick Strong
> Cc: gimp-user-list@gnome.org
> Subject: Re: [Gimp-user] text mode, need instruct sequence
>
> On Friday 02 October 2020 18:36:07 you wrote:
>
> > Gene,
> >
> > By my reckoning, an 18 px letter is less than 1 pt high on an 300 dpi
> > print—virtually invisible. Try setting the text size to 18 pts.
> > (POINTS, not pixels) to be legible.
>
> I have done that, Rick, but 18 pts isn't near big enough for older eyes
> either, so you backspace to get rid of the dust specs, look up to the
> text box and its reset to 18px. Frustrating is a very weak description.
> You spend 10 minutes bounceing from one place in that tool, to another
> trying to get it to keep what you selected long enough to type one line
> of text. Repeat for every line of text you want to overlay on a pix.
>
> > Good luck.
>
> I don't need luck, I need instructions that work, please read my whole
> message.
>
> > RS
>
> My whole point is that there is no way to set the defaults AND setting
> anything else restores the default of 18 px, switches it back to sans
> font, and the selected color back to black.  Changing ANY of those
> settings should change them at the very least for the lifetime of the
> current session. ANY TIME YOU CHANGE ONE THING, IT RESETS EVERYTHING
> ELSE BACK TO THE DEFAULTS. INCLUDING CHANGING WHERE YOU WANT TO PUT IT
> BY LEFT CLICKING THE SCREEN WHERE YOU WANT TO START TYPING. And if your
> put it here click is too high, the box disappears under the friggin
> ruler at the top of the screen so that you can't see if its decided to
> restore all the defaults
>
> Since you have not addressed my main bitch at all, how about telling us
> how to change the text defaults to something that IS usable and by
> makeing those the defaults, 90% of the frustrations would be addressed.
> Maybe _you_ have a sequence that works, but no one has told the users.
> Put it in a format I can print and tape to the wall for next time.
>
> > -Original Message-
> > From: Gene Heskett
> > Sent: Friday, October 02, 2020 5:05 PM
> > To: gimp-user-list@gnome.org
> > Subject: [Gimp-user] text mode, need instruct sequence
> >
> > Greetings all;
> >
> > I, like Ruben Safir, am A. tired of the lack of good docs, and B. the
> > churn in how it works. I just had occasion to caption some pix as an
> > aid to my wife who is not a computer whiz, in setting up a piano
> > keyboard, and the air was quite blue around me by the time I got done
> > because every time I tried to set one option in the text panel it
> > reset everything else back to the defaults.  And an 18 px black
> > character isn't more than a visible dot on an 8x10 printout, so I
> >

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The problem is with Pithos 1.5 which I recently installed.  It has two
optional setting.  One looks like it disables the screen saver (screen
blanking) and the other is not to pause in screen saver mode (my problem
os loosing audio).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The problem is with Pithos 1.5 which I recently installed.  It has two
optional setting.  One looks like it disables the screen saver (screen
blanking) and the other is not to pause in screen saver mode (my problem
os loosing audio).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Noticed that in the last week or so when my system is playing audio
  when the screen timer expires the screen blanks but also the audio
  stops playing.  Starting up as soon as the screen returns (moving the
  mouse).  Was setting up a trial run to document by playing audio and
  setting the screen to blank after 1 minute.  When the minute expired
  the screen start the blank but I got a crash in gnome-shell.  The
  screen was returned to normal and I got a bug report notification
  which I sent. After another minute (did nothing else on the system)
  and the screen started to blank and this time completed the process.
  As soon as the blanking process was complete the sound turned off.
  Moving the mouse returned the screen and the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 15:18:19 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-09-29 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The problem is with Pithos 1.5 which I recently installed.  It has two
optional setting.  One looks like it disables the screen saver (screen
blanking) and the other is not to pause in screen saver mode (my problem
os loosing audio).

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The audio feed from the io ports is indeed going to a stand alone
bluetooth transmitter located central in the house.  I did split off the
audio cable to feed a stereo located next to the desktop.  The stereo
also looses the audio feed when the screen blanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The audio feed from the io ports is indeed going to a stand alone
bluetooth transmitter located central in the house.  I did split off the
audio cable to feed a stereo located next to the desktop.  The stereo
also looses the audio feed when the screen blanks.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Desktop-packages] [Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

The audio feed from the io ports is indeed going to a stand alone
bluetooth transmitter located central in the house.  I did split off the
audio cable to feed a stereo located next to the desktop.  The stereo
also looses the audio feed when the screen blanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Noticed that in the last week or so when my system is playing audio
  when the screen timer expires the screen blanks but also the audio
  stops playing.  Starting up as soon as the screen returns (moving the
  mouse).  Was setting up a trial run to document by playing audio and
  setting the screen to blank after 1 minute.  When the minute expired
  the screen start the blank but I got a crash in gnome-shell.  The
  screen was returned to normal and I got a bug report notification
  which I sent. After another minute (did nothing else on the system)
  and the screen started to blank and this time completed the process.
  As soon as the blanking process was complete the sound turned off.
  Moving the mouse returned the screen and the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 15:18:19 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-09-29 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

the bud id of the associated crash 1898090

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Noticed that in the last week or so when my system is playing audio
  when the screen timer expires the screen blanks but also the audio
  stops playing.  Starting up as soon as the screen returns (moving the
  mouse).  Was setting up a trial run to document by playing audio and
  setting the screen to blank after 1 minute.  When the minute expired
  the screen start the blank but I got a crash in gnome-shell.  The
  screen was returned to normal and I got a bug report notification
  which I sent. After another minute (did nothing else on the system)
  and the screen started to blank and this time completed the process.
  As soon as the blanking process was complete the sound turned off.
  Moving the mouse returned the screen and the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 15:18:19 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-09-29 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

the bud id of the associated crash 1898090

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-02 Thread Cliff Carson

the bud id of the associated crash 1898090

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-01 Thread Cliff Carson

I'm using the Audio IO ports to connect to a Bluetooth transmitter to
provide whole house sound.  The only audio device in this system is a
follows;

*-multimedia:0
 description: Audio device
 product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
 vendor: Intel Corporation
 physical id: 3
 bus info: pci@:00:03.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:39 memory:dfd34000-dfd37fff

This setup has been working for a long time up until very recently.
Found the crash file from yesterday and submit a new bug because I don't
know for certain that this problem and the crash are related.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Noticed that in the last week or so when my system is playing audio
  when the screen timer expires the screen blanks but also the audio
  stops playing.  Starting up as soon as the screen returns (moving the
  mouse).  Was setting up a trial run to document by playing audio and
  setting the screen to blank after 1 minute.  When the minute expired
  the screen start the blank but I got a crash in gnome-shell.  The
  screen was returned to normal and I got a bug report notification
  which I sent. After another minute (did nothing else on the system)
  and the screen started to blank and this time completed the process.
  As soon as the blanking process was complete the sound turned off.
  Moving the mouse returned the screen and the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 15:18:19 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-09-29 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-01 Thread Cliff Carson

I'm using the Audio IO ports to connect to a Bluetooth transmitter to
provide whole house sound.  The only audio device in this system is a
follows;

*-multimedia:0
 description: Audio device
 product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
 vendor: Intel Corporation
 physical id: 3
 bus info: pci@:00:03.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:39 memory:dfd34000-dfd37fff

This setup has been working for a long time up until very recently.
Found the crash file from yesterday and submit a new bug because I don't
know for certain that this problem and the crash are related.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1897959] Re: Audio Shuts Down with Screen Blanking

2020-10-01 Thread Cliff Carson

I'm using the Audio IO ports to connect to a Bluetooth transmitter to
provide whole house sound.  The only audio device in this system is a
follows;

*-multimedia:0
 description: Audio device
 product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
 vendor: Intel Corporation
 physical id: 3
 bus info: pci@:00:03.0
 version: 06
 width: 64 bits
 clock: 33MHz
 capabilities: bus_master cap_list
 configuration: driver=snd_hda_intel latency=0
 resources: irq:39 memory:dfd34000-dfd37fff

This setup has been working for a long time up until very recently.
Found the crash file from yesterday and submit a new bug because I don't
know for certain that this problem and the crash are related.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1897959] [NEW] Audio Shuts Down with Screen Blanking

2020-09-30 Thread Cliff Carson

Public bug reported:

Noticed that in the last week or so when my system is playing audio when
the screen timer expires the screen blanks but also the audio stops
playing.  Starting up as soon as the screen returns (moving the mouse).
Was setting up a trial run to document by playing audio and setting the
screen to blank after 1 minute.  When the minute expired the screen
start the blank but I got a crash in gnome-shell.  The screen was
returned to normal and I got a bug report notification which I sent.
After another minute (did nothing else on the system) and the screen
started to blank and this time completed the process.  As soon as the
blanking process was complete the sound turned off.  Moving the mouse
returned the screen and the sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 30 15:18:19 2020
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2020-09-29 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

** Attachment added: "Snippet of the journal at the time of the failures.  
About 15:11 and 15:12"
   
https://bugs.launchpad.net/bugs/1897959/+attachment/5415798/+files/PowerOffAudio.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1897959] [NEW] Audio Shuts Down with Screen Blanking

2020-09-30 Thread Cliff Carson

Public bug reported:

Noticed that in the last week or so when my system is playing audio when
the screen timer expires the screen blanks but also the audio stops
playing.  Starting up as soon as the screen returns (moving the mouse).
Was setting up a trial run to document by playing audio and setting the
screen to blank after 1 minute.  When the minute expired the screen
start the blank but I got a crash in gnome-shell.  The screen was
returned to normal and I got a bug report notification which I sent.
After another minute (did nothing else on the system) and the screen
started to blank and this time completed the process.  As soon as the
blanking process was complete the sound turned off.  Moving the mouse
returned the screen and the sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 30 15:18:19 2020
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2020-09-29 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

** Attachment added: "Snippet of the journal at the time of the failures.  
About 15:11 and 15:12"
   
https://bugs.launchpad.net/bugs/1897959/+attachment/5415798/+files/PowerOffAudio.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Noticed that in the last week or so when my system is playing audio
  when the screen timer expires the screen blanks but also the audio
  stops playing.  Starting up as soon as the screen returns (moving the
  mouse).  Was setting up a trial run to document by playing audio and
  setting the screen to blank after 1 minute.  When the minute expired
  the screen start the blank but I got a crash in gnome-shell.  The
  screen was returned to normal and I got a bug report notification
  which I sent. After another minute (did nothing else on the system)
  and the screen started to blank and this time completed the process.
  As soon as the blanking process was complete the sound turned off.
  Moving the mouse returned the screen and the sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.38.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
  Uname: Linux 5.8.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu48
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 30 15:18:19 2020
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2020-09-29 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1897959] [NEW] Audio Shuts Down with Screen Blanking

2020-09-30 Thread Cliff Carson

Public bug reported:

Noticed that in the last week or so when my system is playing audio when
the screen timer expires the screen blanks but also the audio stops
playing.  Starting up as soon as the screen returns (moving the mouse).
Was setting up a trial run to document by playing audio and setting the
screen to blank after 1 minute.  When the minute expired the screen
start the blank but I got a crash in gnome-shell.  The screen was
returned to normal and I got a bug report notification which I sent.
After another minute (did nothing else on the system) and the screen
started to blank and this time completed the process.  As soon as the
blanking process was complete the sound turned off.  Moving the mouse
returned the screen and the sound.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10
Uname: Linux 5.8.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Sep 30 15:18:19 2020
DisplayManager: gdm3
GsettingsChanges:
 
InstallationDate: Installed on 2020-09-29 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

** Attachment added: "Snippet of the journal at the time of the failures.  
About 15:11 and 15:12"
   
https://bugs.launchpad.net/bugs/1897959/+attachment/5415798/+files/PowerOffAudio.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897959

Title:
  Audio Shuts Down with Screen Blanking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Re: [VBox-users] macOS Kernel signing woes

2020-09-28 Thread Cliff

System Integrity Protection.

Cliff

> On Sep 28, 2020, at 16:28, Alan  wrote:
> 
> What is SIP please?
> 
> On Mon 28 Sep 2020 at 23:21, Thad Humphries  <mailto:thad.humphr...@gmail.com>> wrote:
> On Mon, Sep 28, 2020 at 5:04 PM Tim Streater  <mailto:timstrea...@greenbee.net>> wrote:
> On 28 Sep 2020, at 11:38, Tim Streater  <mailto:timstrea...@greenbee.net>> wrote:
> 
> 
> 
> > I was using VirtualBox 6.1.12 under macOS Mojave 10.14.6 quite happily until
> 
> > two days ago. I then installed Apple's Security Update 2020-005, which is I
> 
> > imagine responsible for the following.
> 
> >
> 
> > The next time I wanted to start a VM, I was informed that a new version of
> 
> > VirtualBox, 6.1.14, was available, so I downloaded and attempted to install
> 
> > it. The install failed near the end of the process; the executable was 
> > written
> 
> > but I think a kernel module was prevented from being installed. Trying to 
> > run
> 
> > a VM gave a message about a missing kernel module. I was also unable to
> 
> > re-install 6.1.12 which now fails at install in the same way.
> 
> 
> 
> I was eventually able to install, and run the VMs, by disabling SIP on my 
> machine. This is not ideal as both disabling and later re-enabling it each 
> requires two restarts.
> 
> 
> 
> -- 
> Cheers -- Tim
> 
> Thank you, Tim, for reporting this. I have two Macs running Mojave 10.14.6. 
> I'll know not to update VBox 6.1.12 until there's some word of a fix.
> 
> I have a third Mac running Catalina 10.15.7. Has anyone seen problems with 
> VBox 6.1.14 on Catalina?
> 
> 
> -- 
> "Hell hath no limits, nor is circumscrib'd In one self-place; but where we 
> are is hell, And where hell is, there must we ever be" --Christopher Marlowe, 
> Doctor Faustus (v. 111-13)
> 
> 
> ___
> 
> VBox-users-community mailing list
> 
> VBox-users-community@lists.sourceforge.net 
> <mailto:VBox-users-community@lists.sourceforge.net>
> 
> https://lists.sourceforge.net/lists/listinfo/vbox-users-community 
> <https://lists.sourceforge.net/lists/listinfo/vbox-users-community>
> 
> ___
> 
> Unsubscribe:  mailto:vbox-users-community-requ...@lists.sourceforge.net 
> <mailto:vbox-users-community-requ...@lists.sourceforge.net>?subject=unsubscribe
> 
> -- 
> Sent from iPhone
> ___
> VBox-users-community mailing list
> VBox-users-community@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vbox-users-community
> ___
> Unsubscribe:  
> mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe

___
VBox-users-community mailing list
VBox-users-community@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
___
Unsubscribe:  
mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe

[jira] [Created] (CONFIGURATION-793) Error reading a list from JSON after 2.3

2020-09-28 Thread Cliff Evans (Jira)

Cliff Evans created CONFIGURATION-793:
-

 Summary: Error reading a list from JSON after 2.3
 Key: CONFIGURATION-793
 URL: https://issues.apache.org/jira/browse/CONFIGURATION-793
 Project: Commons Configuration
  Issue Type: Bug
Affects Versions: 2.3
 Environment: JDK 11.0.4
Reporter: Cliff Evans


We have just attempted to move from version 2.2 to 2.7 and have encountered and 
issue whilst attempting to read a List from a JSON formatted configuration file.

The issue appears to have been introduced in 2.3.

The test below demonstrates the issue.  This test will pass against 2.2 but 
fail agains 2.3 (and 2.7.)

 
{noformat}
package org.apache.commons.configuration2;

import org.apache.commons.configuration2.ex.ConfigurationException;
import org.junit.Test;

import java.io.ByteArrayInputStream;
import java.io.InputStream;
import java.util.List;
import java.util.Map;

import static java.nio.charset.StandardCharsets.UTF_8;
import static org.junit.Assert.assertNotNull;

public class ConfigurationTest {

   private static final String JSON = "{\n" +
  "\"myList\": [\n" +
  "{\n" +
  "  \"att1\": \"one\"\n" +
  "}\n" +
  "]" +
  "}\n";

   @Test
   public void loadConfiguration()
 throws ConfigurationException {
  JSONConfiguration jsonConfiguration = new JSONConfiguration();
  InputStream inputStream = new ByteArrayInputStream(JSON.getBytes(UTF_8));
  jsonConfiguration.read(inputStream);

  final List configList = jsonConfiguration.getList(Map.class, 
"myList");

  assertNotNull(configList);
   }

}
{noformat}
 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

RE: Small Hose Stations

2020-09-26 Thread cliff--- via Sprinklerforum

Tony,

My understanding is that the hose stations are served from different system
risers (or associated piping).  I believe the theory is that the hose
stations can be used for 'cleanup' after the system that has been activated
is shut down.  If the hoses are supplied from adjacent systems, they are
still active once the other system is taken out of service.

As long as you are connected to a different zone than the one where the hose
station is located, I believe this is acceptable.

Cliff Whitfield, SET
President

Fire Design, Inc.
600 W. Bypass Hwy. 19E
Suite 202
Burnsville, NC 28714
Ph: 828-284-4772
 


-Original Message-
From: Sprinklerforum  On
Behalf Of Tony Silva via Sprinklerforum
Sent: Saturday, September 26, 2020 4:55 PM
To: sprinklerforum@lists.firesprinkler.org
Cc: Tony Silva 
Subject: Small Hose Stations

In a storage occupancy that requires small hose stations complying with NFPA
13, an acceptable method of connection is to supply from an "Adjacent
Sprinkler System". Some hose stations fall right in the boundary between two
zones. The contractor wants to supply these hose stations from either one of
these adjacent zones. I am of the opinion that these hose stations should be
supplied from a zone that is not serviced by these hose stations, requiring
longer supply piping.

Any thoughts? What is your position on this issue?

Thanks,

Tony
___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org

[Bug 1896393] Re: gedit not responding to keystrokes

2020-09-22 Thread Cliff Carson

Trying to produce the error delay in a restrictive environment without
great success.  Did get gedit running on some of my c++ programs
thinking maybe it was a plugin that was working.  Did see that when I
was looking at a line and moving the cursor with the arrow keys that
there was a definite delay.  As I moved the cursor across the line not
every key (arrow right/left) was immediate as I would expect (system was
doing nothing else).  Did dump the journal at the time and passing the
snippet of the time I started gedit and when I observed the delay.  Will
continue to try to better document this problem.

Sep 22 15:51:18 cliffps chromium_chromium.desktop[6876]: 
[6876:15002:0922/155118.463902:ERROR:get_updates_processor.cc(258)] 
PostClientToServerMessage() failed during GetUpdates with error 2
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Activating service name='org.gnome.gedit' requested by ':1.39' (uid=1000 
pid=1871 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Successfully activated service 'org.gnome.gedit'
Sep 22 15:54:42 cliffps wpa_supplicant[894]: wlp3s0: Reject scan trigger since 
one is already pending
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: (II) Axis 0x1 value 
-429 is outside expected range [-26, 548]
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: See 
https://wayland.freedesktop.org/libinput/doc/1.16.1/absolute_coordinate_ranges.html
 for details
Sep 22 15:55:42 cliffps systemd[1590]: Started Application launched by 
gsd-media-keys.
Sep 22 15:55:42 cliffps systemd[1590]: Started VTE child process 15458 launched 
by gnome-terminal-server process 2731.
Sep 22 15:55:42 cliffps systemd[1590]: 
app-gnome-x\x2dterminal\x2demulator-15449.scope: Succeeded.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Desktop-packages] [Bug 1896393] Re: gedit not responding to keystrokes

2020-09-22 Thread Cliff Carson

Trying to produce the error delay in a restrictive environment without
great success.  Did get gedit running on some of my c++ programs
thinking maybe it was a plugin that was working.  Did see that when I
was looking at a line and moving the cursor with the arrow keys that
there was a definite delay.  As I moved the cursor across the line not
every key (arrow right/left) was immediate as I would expect (system was
doing nothing else).  Did dump the journal at the time and passing the
snippet of the time I started gedit and when I observed the delay.  Will
continue to try to better document this problem.

Sep 22 15:51:18 cliffps chromium_chromium.desktop[6876]: 
[6876:15002:0922/155118.463902:ERROR:get_updates_processor.cc(258)] 
PostClientToServerMessage() failed during GetUpdates with error 2
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Activating service name='org.gnome.gedit' requested by ':1.39' (uid=1000 
pid=1871 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Successfully activated service 'org.gnome.gedit'
Sep 22 15:54:42 cliffps wpa_supplicant[894]: wlp3s0: Reject scan trigger since 
one is already pending
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: (II) Axis 0x1 value 
-429 is outside expected range [-26, 548]
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: See 
https://wayland.freedesktop.org/libinput/doc/1.16.1/absolute_coordinate_ranges.html
 for details
Sep 22 15:55:42 cliffps systemd[1590]: Started Application launched by 
gsd-media-keys.
Sep 22 15:55:42 cliffps systemd[1590]: Started VTE child process 15458 launched 
by gnome-terminal-server process 2731.
Sep 22 15:55:42 cliffps systemd[1590]: 
app-gnome-x\x2dterminal\x2demulator-15449.scope: Succeeded.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

Status in gedit package in Ubuntu:
  New

Bug description:
  Don't know how to further document this except was is observed during
  the gedit session.

  While typing information into the gedit window the keystrokes get
  delayed 1-2 seconds from the time the keys are struct and when the
  character(s) show up on the screen.  It's as if the system was too
  busy to service the key input but that doesn't appear to be the case.
  This problem doesn't occur on the current gedit running under 20.04.

  Any suggestions on how to document this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gedit 3.36.2-1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 13:03:43 2020
  InstallationDate: Installed on 2020-08-28 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1896393] Re: gedit not responding to keystrokes

2020-09-22 Thread Cliff Carson

Trying to produce the error delay in a restrictive environment without
great success.  Did get gedit running on some of my c++ programs
thinking maybe it was a plugin that was working.  Did see that when I
was looking at a line and moving the cursor with the arrow keys that
there was a definite delay.  As I moved the cursor across the line not
every key (arrow right/left) was immediate as I would expect (system was
doing nothing else).  Did dump the journal at the time and passing the
snippet of the time I started gedit and when I observed the delay.  Will
continue to try to better document this problem.

Sep 22 15:51:18 cliffps chromium_chromium.desktop[6876]: 
[6876:15002:0922/155118.463902:ERROR:get_updates_processor.cc(258)] 
PostClientToServerMessage() failed during GetUpdates with error 2
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Activating service name='org.gnome.gedit' requested by ':1.39' (uid=1000 
pid=1871 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Successfully activated service 'org.gnome.gedit'
Sep 22 15:54:42 cliffps wpa_supplicant[894]: wlp3s0: Reject scan trigger since 
one is already pending
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: (II) Axis 0x1 value 
-429 is outside expected range [-26, 548]
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: See 
https://wayland.freedesktop.org/libinput/doc/1.16.1/absolute_coordinate_ranges.html
 for details
Sep 22 15:55:42 cliffps systemd[1590]: Started Application launched by 
gsd-media-keys.
Sep 22 15:55:42 cliffps systemd[1590]: Started VTE child process 15458 launched 
by gnome-terminal-server process 2731.
Sep 22 15:55:42 cliffps systemd[1590]: 
app-gnome-x\x2dterminal\x2demulator-15449.scope: Succeeded.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: AutoSPRINK Test Calc

2020-09-22 Thread cliff--- via Sprinklerforum

Hi Brian,

Sure.  Email it to me off forum.  I'll be glad to help you with it.

Cliff Whitfield, SET
President

Fire Design, Inc.
600 W. Bypass Hwy. 19E
Suite 202
Burnsville, NC 28714
Ph: 828-284-4772
 


-Original Message-
From: Sprinklerforum  On
Behalf Of Brian Harris via Sprinklerforum
Sent: Tuesday, September 22, 2020 8:04 AM
To: sprinklerforum@lists.firesprinkler.org
Cc: Brian Harris 
Subject: AutoSPRINK Test Calc

Would anybody on here that uses AutoSPRINK be willing to take a look at a
file I'm working on? Calc's are way off, IMO, and I'm think it's something
wonky with my file.

Brian Harris, CET
BVS Systems Inc.
Design Manager
bvssystemsinc.com<http://bvssystemsinc.com/>
Phone: 704.896.9989
Fax: 704.896.1935

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org

[Desktop-packages] [Bug 1896393] Re: gedit not responding to keystrokes

2020-09-21 Thread Cliff Carson

Only observed this delay using gedit.  Other input programs (chrome,
libreoffice, thunderbird) do not have this delay.  It doesn't occur on
every key stroke but as I'm editing some program source I see it
frequently.  I've had the system monitor running and when I see the
delay checking the cpu activity doesn't show any spike around the time I
was typing.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

Status in gedit package in Ubuntu:
  New

Bug description:
  Don't know how to further document this except was is observed during
  the gedit session.

  While typing information into the gedit window the keystrokes get
  delayed 1-2 seconds from the time the keys are struct and when the
  character(s) show up on the screen.  It's as if the system was too
  busy to service the key input but that doesn't appear to be the case.
  This problem doesn't occur on the current gedit running under 20.04.

  Any suggestions on how to document this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gedit 3.36.2-1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 13:03:43 2020
  InstallationDate: Installed on 2020-08-28 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1896393] Re: gedit not responding to keystrokes

2020-09-21 Thread Cliff Carson

Only observed this delay using gedit.  Other input programs (chrome,
libreoffice, thunderbird) do not have this delay.  It doesn't occur on
every key stroke but as I'm editing some program source I see it
frequently.  I've had the system monitor running and when I see the
delay checking the cpu activity doesn't show any spike around the time I
was typing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1896393] Re: gedit not responding to keystrokes

2020-09-21 Thread Cliff Carson

Only observed this delay using gedit.  Other input programs (chrome,
libreoffice, thunderbird) do not have this delay.  It doesn't occur on
every key stroke but as I'm editing some program source I see it
frequently.  I've had the system monitor running and when I see the
delay checking the cpu activity doesn't show any spike around the time I
was typing.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Desktop-packages] [Bug 1896393] [NEW] gedit not responding to keystrokes

2020-09-20 Thread Cliff Carson

Public bug reported:

Don't know how to further document this except was is observed during
the gedit session.

While typing information into the gedit window the keystrokes get
delayed 1-2 seconds from the time the keys are struct and when the
character(s) show up on the screen.  It's as if the system was too busy
to service the key input but that doesn't appear to be the case.  This
problem doesn't occur on the current gedit running under 20.04.

Any suggestions on how to document this problem?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gedit 3.36.2-1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 13:03:43 2020
InstallationDate: Installed on 2020-08-28 (22 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

Status in gedit package in Ubuntu:
  New

Bug description:
  Don't know how to further document this except was is observed during
  the gedit session.

  While typing information into the gedit window the keystrokes get
  delayed 1-2 seconds from the time the keys are struct and when the
  character(s) show up on the screen.  It's as if the system was too
  busy to service the key input but that doesn't appear to be the case.
  This problem doesn't occur on the current gedit running under 20.04.

  Any suggestions on how to document this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gedit 3.36.2-1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 13:03:43 2020
  InstallationDate: Installed on 2020-08-28 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Bug 1896393] [NEW] gedit not responding to keystrokes

2020-09-20 Thread Cliff Carson

Public bug reported:

Don't know how to further document this except was is observed during
the gedit session.

While typing information into the gedit window the keystrokes get
delayed 1-2 seconds from the time the keys are struct and when the
character(s) show up on the screen.  It's as if the system was too busy
to service the key input but that doesn't appear to be the case.  This
problem doesn't occur on the current gedit running under 20.04.

Any suggestions on how to document this problem?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gedit 3.36.2-1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 13:03:43 2020
InstallationDate: Installed on 2020-08-28 (22 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1896393] [NEW] gedit not responding to keystrokes

2020-09-20 Thread Cliff Carson

Public bug reported:

Don't know how to further document this except was is observed during
the gedit session.

While typing information into the gedit window the keystrokes get
delayed 1-2 seconds from the time the keys are struct and when the
character(s) show up on the screen.  It's as if the system was too busy
to service the key input but that doesn't appear to be the case.  This
problem doesn't occur on the current gedit running under 20.04.

Any suggestions on how to document this problem?

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: gedit 3.36.2-1
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 20 13:03:43 2020
InstallationDate: Installed on 2020-08-28 (22 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896393

Title:
  gedit not responding to keystrokes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1896393/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Elecraft] FS W2 Wattmeter HF + VHF/UHF couplers [updated]

2020-09-16 Thread Cliff Frescura

The DCV/U-200 has been sold.  W2 with HF coupler still available.

Thanks,

Cliff K3LL/6

-Original Message-
From: elecraft-boun...@mailman.qth.net  On 
Behalf Of Cliff
Frescura
Sent: Wednesday, September 16, 2020 8:47 AM
To: elecraft@mailman.qth.net
Subject: [Elecraft] FS W2 Wattmeter HF + VHF/UHF couplers

I have for sale:

1. W2 wattmeter with DCHF-2000 1.8 - 54 MHz 2KW coupler, coupler cable, and 
power cable
(power pole end).  Modified to turn on when power is applied: $285 
2. DCV/U-200 144 MHz - 450 MHz 200W coupler with coupler cable (coupler only): 
$90

W2 with both couplers : $350

Pictures available upon request.

ConUS shipping included via USPS Priority mail.  Payment via PayPal or Zelle.  
No returns.

Please reply off list.

73,

Cliff K3LL/6



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to c...@cfcorp.com 




__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

[Elecraft] FS W2 Wattmeter HF + VHF/UHF couplers

2020-09-16 Thread Cliff Frescura

I have for sale:

1. W2 wattmeter with DCHF-2000 1.8 - 54 MHz 2KW coupler, coupler cable, and 
power cable
(power pole end).  Modified to turn on when power is applied: $285 
2. DCV/U-200 144 MHz - 450 MHz 200W coupler with coupler cable (coupler only): 
$90

W2 with both couplers : $350

Pictures available upon request.

ConUS shipping included via USPS Priority mail.  Payment via PayPal or Zelle.  
No returns.

Please reply off list.

73,

Cliff K3LL/6



__
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:Elecraft@mailman.qth.net

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to arch...@mail-archive.com

[Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10

2020-09-11 Thread Cliff Carson

Looks like the problem is corrected with the new updates on 9/11/20.
Function keys work and the alt-ctl-t and alt-ctl-c also work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10

2020-09-11 Thread Cliff Carson

Looks like the problem is corrected with the new updates on 9/11/20.
Function keys work and the alt-ctl-t and alt-ctl-c also work.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc

[Kernel-packages] [Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10

2020-09-08 Thread Cliff Carson

Forgot to mention some Hot Keys don't work either.  Launch a terminal
(ctl-alt-t) and launch the calculator (ctl-alt-c) not functioning.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt

[Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10

2020-09-08 Thread Cliff Carson

Forgot to mention some Hot Keys don't work either.  Launch a terminal
(ctl-alt-t) and launch the calculator (ctl-alt-c) not functioning.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1894733] Lsusb-v.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408414/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad

[Kernel-packages] [Bug 1894733] Lsusb.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408412/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad

[Kernel-packages] [Bug 1894733] Lsusb-t.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408413/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad

[Kernel-packages] [Bug 1894733] UdevDb.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408421/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad

[Kernel-packages] [Bug 1894733] acpidump.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408423/+files/acpidump.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: C

[Kernel-packages] [Bug 1894733] ProcCpuinfo.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408415/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bug

[Kernel-packages] [Bug 1894733] PulseList.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408419/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.laun

[Kernel-packages] [Bug 1894733] WifiSyslog.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408422/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.laun

[Kernel-packages] [Bug 1894733] ProcModules.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408418/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bug

[Kernel-packages] [Bug 1894733] ProcCpuinfoMinimal.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408416/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go

[Kernel-packages] [Bug 1894733] ProcInterrupts.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408417/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
htt

[Kernel-packages] [Bug 1894733] RfKill.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408420/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad

[Bug 1894733] ProcModules.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408418/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] Lsusb-v.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408414/+files/Lsusb-v.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] ProcCpuinfo.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408415/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] RfKill.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408420/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] WifiSyslog.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408422/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] ProcInterrupts.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408417/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] ProcCpuinfoMinimal.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408416/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] Lsusb.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408412/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] IwConfig.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408409/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] PulseList.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408419/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1894733] Lspci.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408410/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad

[Kernel-packages] [Bug 1894733] Lspci-vt.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408411/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.laun

[Kernel-packages] [Bug 1894733] IwConfig.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408409/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.laun

[Kernel-packages] [Bug 1894733] CRDA.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408408/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8
  and fn-9) and airplane mode (fn-f11) The problem does not occur in
  20.04 (kernel 5.4) on the same laptop, all function keys work.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu

[Bug 1894733] Lspci.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408410/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] Lsusb-t.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408413/+files/Lsusb-t.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] UdevDb.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408421/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] acpidump.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408423/+files/acpidump.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10

2020-09-07 Thread Cliff Carson

apport information

** Tags added: apport-collected

** Description changed:

  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8 and
  fn-9) and airplane mode (fn-f11) The problem does not occur in 20.04
  (kernel 5.4) on the same laptop, all function keys work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu45
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  cliff  1445 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-08-28 (9 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
+ MachineType: CLEVO CO. W35_37ET
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
+ RelatedPackageVersions:
+  linux-restricted-modules-5.8.0-18-generic N/A
+  linux-backports-modules-5.8.0-18-generic  N/A
+  linux-firmware1.190
+ Tags:  groovy
+ Uname: Linux 5.8.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/14/2012
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 4.6.5
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: W35_37ET
+ dmi.board.vendor: CLEVO CO.
+ dmi.board.version: N/A
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: CLEVO CO.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: W35_37ET
+ dmi.product.sku: To be filled by O.E.M.
+ dmi.product.version: N/A
+ dmi.sys.vendor: CLEVO CO.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408407/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu

[Bug 1894733] Lspci-vt.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408411/+files/Lspci-vt.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Kernel-packages] [Bug 1894733] Re: Most fn keys don't work on Puget laptop running 20.10

2020-09-07 Thread Cliff Carson

apport information

** Tags added: apport-collected

** Description changed:

  The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
  not work.  Tried both kernels available (5.4 and 5.8) with the same
  results.  The only fn keys that appear to work are brightness (fn-f8 and
  fn-9) and airplane mode (fn-f11) The problem does not occur in 20.04
  (kernel 5.4) on the same laptop, all function keys work.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-18-generic 5.8.0-18.19
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cliff  1445 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Mon Sep  7 11:23:56 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  MachineType: CLEVO CO. W35_37ET
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-18-generic N/A
   linux-backports-modules-5.8.0-18-generic  N/A
   linux-firmware1.190
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu45
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  cliff  1445 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
+ DistroRelease: Ubuntu 20.10
+ InstallationDate: Installed on 2020-08-28 (9 days ago)
+ InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
+ MachineType: CLEVO CO. W35_37ET
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
+ ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
+ RelatedPackageVersions:
+  linux-restricted-modules-5.8.0-18-generic N/A
+  linux-backports-modules-5.8.0-18-generic  N/A
+  linux-firmware1.190
+ Tags:  groovy
+ Uname: Linux 5.8.0-18-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/14/2012
+ dmi.bios.release: 4.6
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 4.6.5
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: W35_37ET
+ dmi.board.vendor: CLEVO CO.
+ dmi.board.version: N/A
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: CLEVO CO.
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: W35_37ET
+ dmi.product.sku: To be filled by O.E.M.
+ dmi.product.version: N/A
+ dmi.sys.vendor: CLEVO CO.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1894733/+attachment/5408407/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The v

[Bug 1894733] CRDA.txt

2020-09-07 Thread Cliff Carson

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1894733/+attachment/5408408/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894733] [NEW] Most fn keys don't work on Puget laptop running 20.10

2020-09-07 Thread Cliff Carson

Public bug reported:

The volume up/down (fn-f5 and fn-f6) and enable bluetooth (fn-f12) do
not work.  Tried both kernels available (5.4 and 5.8) with the same
results.  The only fn keys that appear to work are brightness (fn-f8 and
fn-9) and airplane mode (fn-f11) The problem does not occur in 20.04
(kernel 5.4) on the same laptop, all function keys work.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-18-generic 5.8.0-18.19
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  cliff  1445 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Mon Sep  7 11:23:56 2020
InstallationDate: Installed on 2020-08-28 (9 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
MachineType: CLEVO CO. W35_37ET
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-18-generic N/A
 linux-backports-modules-5.8.0-18-generic  N/A
 linux-firmware1.190
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W35_37ET
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894733

Title:
  Most fn keys don't work on Puget laptop running 20.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1894733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1894452] [NEW] shutdown delay because of cups

2020-09-06 Thread Cliff Carson

Public bug reported:

Both my desktop and laptop running 20.10 have a 90 second delay shutting
down (power off or restart).  Getting message;

A stop job is Running for Make remote CUPS printers available locally

After 90 seconds the shutdown continues to completion.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: cups 2.3.3-2ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sun Sep  6 18:10:20 2020
InstallationDate: Installed on 2020-08-28 (9 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
KernLog:
 
Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
MachineType: CLEVO CO. W35_37ET
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W35_37ET
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894452

Title:
  shutdown delay because of cups

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1894452/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Desktop-packages] [Bug 1894452] [NEW] shutdown delay because of cups

2020-09-06 Thread Cliff Carson

Public bug reported:

Both my desktop and laptop running 20.10 have a 90 second delay shutting
down (power off or restart).  Getting message;

A stop job is Running for Make remote CUPS printers available locally

After 90 seconds the shutdown continues to completion.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: cups 2.3.3-2ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sun Sep  6 18:10:20 2020
InstallationDate: Installed on 2020-08-28 (9 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
KernLog:
 
Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
MachineType: CLEVO CO. W35_37ET
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W35_37ET
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1894452

Title:
  shutdown delay because of cups

Status in cups package in Ubuntu:
  New

Bug description:
  Both my desktop and laptop running 20.10 have a 90 second delay
  shutting down (power off or restart).  Getting message;

  A stop job is Running for Make remote CUPS printers available locally

  After 90 seconds the shutdown continues to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups 2.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep  6 18:10:20 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  KernLog:
   
  Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
  MachineType: CLEVO CO. W35_37ET
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1894452/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to :

[Touch-packages] [Bug 1894452] [NEW] shutdown delay because of cups

2020-09-06 Thread Cliff Carson

Public bug reported:

Both my desktop and laptop running 20.10 have a 90 second delay shutting
down (power off or restart).  Getting message;

A stop job is Running for Make remote CUPS printers available locally

After 90 seconds the shutdown continues to completion.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: cups 2.3.3-2ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Sun Sep  6 18:10:20 2020
InstallationDate: Installed on 2020-08-28 (9 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
KernLog:
 
Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
MachineType: CLEVO CO. W35_37ET
Papersize: letter
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W35_37ET
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W35_37ET
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

** Affects: cups (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1894452

Title:
  shutdown delay because of cups

Status in cups package in Ubuntu:
  New

Bug description:
  Both my desktop and laptop running 20.10 have a 90 second delay
  shutting down (power off or restart).  Getting message;

  A stop job is Running for Make remote CUPS printers available locally

  After 90 seconds the shutdown continues to completion.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: cups 2.3.3-2ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep  6 18:10:20 2020
  InstallationDate: Installed on 2020-08-28 (9 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  KernLog:
   
  Lpstat: device for ENVY_4500: hp:/net/ENVY_4500_series?ip=192.168.1.131
  MachineType: CLEVO CO. W35_37ET
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/ENVY_4500.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/ENVY_4500.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=292706c2-98fe-4370-a52f-7e67774018c7 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/14/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W35_37ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/14/2012:br4.6:svnCLEVOCO.:pnW35_37ET:pvrN/A:rvnCLEVOCO.:rnW35_37ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W35_37ET
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1894452/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Geoserver-users] Problems implementing where_clause in SQL

2020-08-30 Thread Cliff Patterson

Hello,

I am using SQL Views in Geoserver on a PostGIS store. I am using Geoserver
version 2.16.2.

I need to pass a dynamic statement in the WHERE clause, but since the query
counts any combination of 15 columns to filter the points before counting
the number of points per polygon, normal parameters will not work. I am
trying to (a) understand how to use the :where_cluase: parameter in a SQL
view, and (b) more specifically how to send parameters to it from Leaflet
-- what is the correct syntax?

The SQL View Query is the following:

WITH selection AS (
SELECT a.id, count(b.geom) AS total
FROM boundary_poly a LEFT JOIN businesses b
ON st_contains(a.geom,b.geom)
WHERE deleted_at IS NULL :where_clause:
GROUP BY a.id)
SELECT a.id, a.geom, a.cdname,
CASE WHEN b.total IS NULL THEN 0
ELSE b.total END
FROM boundary_poly a FULL OUTER JOIN selection b
ON a.id = b.id

I am trying to send parameters to the :where_clause: from Leaflet like this
but it does not work;

var boundaries = L.tileLayer.wms(geoserver + '/geoserver/ows?', {
layers: 'workspace:boundaries',
format: 'image/png',
transparent: true,
tileSize: 2048,
viewparams: 'where_clause:wineries=1'
}).addTo(map);

It does not load but I get a 200 on the call. Eventually, I will need to
pass a WHERE clause that could be like any of these:
"p1=1 OR p2=1 ORp3=1"
"p7=1 OR p15=1"
"p5=1"

Any clarification on how to properly use the :where_clause: placeholder
would be a huge help!

Thanks,
Cliff
___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [dpdk-users] Sending Packets on Multiple PMD ports with only 1 core.

2020-08-20 Thread Cliff Burdick

There shouldn't be any problem doing that. Just pass a different port to
the sending functions.


On Thu, Aug 20, 2020, 03:51 Alireza Sanaee  wrote:

> Dear all,
>
> I would like to send packet from multiple PMD port using one core, I'm
> just wondering if this is practical at all or not. Has somebody had some
> previous experiment with this?
>
> Thanks,
> Alireza
>
>

Re: [Qpid-Proton-C] reconnection

2020-08-19 Thread Cliff Jansen

There is nothing wrong with your current strategy.  You could
alternatively create a new connection on the same proactor instance.
You can also reuse a connection with a new transport, for example by
calling pn_proactor_release_connection() when you get the
PN_TRANSPORT_CLOSED event and before calling pn_proactor_connect2() to
the same address or to a failover address.

I am not aware that any of the above is a best practice in any way.
Any saved teardown and re-setup operations probably occur infrequently
enough in the life of the application such that you should just pick
whichever best suits the design of your application.

In any of the above scenarios, the application needs to track which
deliveries were not settled and re-send the associated messages.  The
proton engine does not transfer/preserve delivery or other link state
from the old link object to the new one when you recreate the link.

On Fri, Aug 14, 2020 at 1:33 PM Adrian Florea  wrote:
>
> Hi,
>
> I have a C app using Proton-C and it is connected to an AMQP provider.
> Periodically, the AMQP provider is closing the connection and I need to
> reconnect (my app is supposed to run, ideally, 24/7).
>
> Currently, I handle this by simply catching the related transport events in
> the Proactor event loop and then, when I get those errors, I free the
> proactor, free the AMQP message and then go back to the initial Proactor
> loop  similar behavior as it happens when the program first starts. It
> works.
>
> My question is: is there any best practice to handle a reconnect, less
> invasive than just freeing the Proactor and starting from scratch ?
>
> Additionally, is there a way so I reconnect and also keep my link objects
> and "reuse" / "re-attach" them after the reconnect ?
>
> Many thanks,
> Adrian

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: [dpdk-users] rte_flow() usage of htonl() for ipv4 addr masks?

2020-08-09 Thread Cliff Burdick

It should convert to network order, although many applications it won't
matter since they use all F's. If you follow the code in flow_filtering,
indeed it's using:

#define FULL_MASK 0x /* full mask */

So it won't make any difference. The example should probably be
updated, though..

On Sun, Aug 9, 2020 at 7:03 PM Arvind Narayanan 
wrote:

> Hi,
>
> In the flow_filtering sample application, the IP's mask was set without
> using htonl().
>
> https://github.com/DPDK/dpdk/blob/master/examples/flow_filtering/flow_blocks.c#L85
>
> Another DPDK page  shows
> how a testpmd command is translated to C code.
> On this page though, Example 4.2 (Range IPv4 drop) has used htonl() to set
> the mask.
>
> Any clarification on how to load the mask would be helpful.
>
> Thanks,
> Arvind
>

RE: Pump Suction Pressure (NPSH)

2020-08-06 Thread cliff--- via Sprinklerforum

Brian,

I may be looking at this too 'simply', but wouldnt your suction pressure be
the static pressure at the flow test location plus or minus any pressure
gain or loss for any difference between the elevation of the flow test and
the fire pump suction?

Cliff Whitfield, SET
President

Fire Design, Inc.
600 W. Bypass Hwy. 19E
Suite 202
Burnsville, NC 28714
Ph: 828-284-4772
 


-Original Message-
From: Sprinklerforum  On
Behalf Of Brian Harris via Sprinklerforum
Sent: Thursday, August 6, 2020 11:24 AM
To: sprinklerforum@lists.firesprinkler.org
Cc: Brian Harris 
Subject: Pump Suction Pressure (NPSH)

We're replacing a pump in an existing system and the pump vendor wants to
know the pump suction pressure. Since we didn't do the original system and I
know nothing about it what is a practical way of determining the pump
suction to tell the vendor?

Brian Harris, CET
BVS Systems Inc.
Design Manager
bvssystemsinc.com<http://bvssystemsinc.com/>
Phone: 704.896.9989
Fax: 704.896.1935

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
Sprinklerforum mailing list
Sprinklerforum@lists.firesprinkler.org
http://lists.firesprinkler.org/listinfo.cgi/sprinklerforum-firesprinkler.org

[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-31 Thread Cliff Carson

My resync is working fine again.  Thanks for your attention to this bug-
report.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

Status in rsync package in Ubuntu:
  Triaged
Status in rsync package in Debian:
  Fix Released

Bug description:
  After installation of rsync.3.2.1 my attempt to sync fails with chroot
  error.  The rsyncd.log indicates that rsync can't find the directories
  I want to sync.

  2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 
873
  2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings 
failed: No such file or directory (2)

  Dropping back to Ubuntu 20.04 and rsync works again.  The rsync update
  was install 7/18.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: rsync 3.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 23 10:28:17 2020
  InstallationDate: Installed on 2020-07-06 (16 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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

[Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-31 Thread Cliff Carson

My resync is working fine again.  Thanks for your attention to this bug-
report.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-30 Thread Cliff Carson

Appears to me is that failure criteria is if the directory being
rsync'ed is off of my home it will fail.  Hard to believe I'm the only
one seeing this.  Again this 20.10 system was functioning normally until
7/18 when 3.2.1 was installed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  After installation of rsync.3.2.1 my attempt to sync fails with chroot
  error.  The rsyncd.log indicates that rsync can't find the directories
  I want to sync.

  2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 
873
  2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings 
failed: No such file or directory (2)

  Dropping back to Ubuntu 20.04 and rsync works again.  The rsync update
  was install 7/18.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: rsync 3.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 23 10:28:17 2020
  InstallationDate: Installed on 2020-07-06 (16 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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

[Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-30 Thread Cliff Carson

Appears to me is that failure criteria is if the directory being
rsync'ed is off of my home it will fail.  Hard to believe I'm the only
one seeing this.  Again this 20.10 system was functioning normally until
7/18 when 3.2.1 was installed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-30 Thread Cliff Carson

Have a /etc/rsyncd.conf that moves data from path = /mnt/testrsync
directory on my desktop to my laptop and it works.  Changing the
/etc/rsyncd.conf to path = /home/cliff/Bin fails with a chroot failure
(unable to find the path).  Copied the /mnt to my home directory (cp -r
/mnt ./) so the only difference was the mnt was not root owner.  Changed
the /etc/rsyncd.conf path = /home/cliff/mnt/testrsync and it fails with
a chroot error.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  After installation of rsync.3.2.1 my attempt to sync fails with chroot
  error.  The rsyncd.log indicates that rsync can't find the directories
  I want to sync.

  2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 
873
  2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings 
failed: No such file or directory (2)

  Dropping back to Ubuntu 20.04 and rsync works again.  The rsync update
  was install 7/18.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: rsync 3.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 23 10:28:17 2020
  InstallationDate: Installed on 2020-07-06 (16 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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

[Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-30 Thread Cliff Carson

Have a /etc/rsyncd.conf that moves data from path = /mnt/testrsync
directory on my desktop to my laptop and it works.  Changing the
/etc/rsyncd.conf to path = /home/cliff/Bin fails with a chroot failure
(unable to find the path).  Copied the /mnt to my home directory (cp -r
/mnt ./) so the only difference was the mnt was not root owner.  Changed
the /etc/rsyncd.conf path = /home/cliff/mnt/testrsync and it fails with
a chroot error.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-29 Thread Cliff Carson

No differences between /home/cliff/Bin and /mnt/testrsync (0755) both
owned by cliff:cliff.  In building my test cast wanted to duplicated the
target directories as much as I could.

No I use the systemctl start/stop rsync so the answer is the daemon is
running under root.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Touch-packages] [Bug 1888685] Re: rsync fails after installing level 3.2.1

2020-07-29 Thread Cliff Carson

No differences between /home/cliff/Bin and /mnt/testrsync (0755) both
owned by cliff:cliff.  In building my test cast wanted to duplicated the
target directories as much as I could.

No I use the systemctl start/stop rsync so the answer is the daemon is
running under root.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1888685

Title:
  rsync fails after installing level 3.2.1

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  After installation of rsync.3.2.1 my attempt to sync fails with chroot
  error.  The rsyncd.log indicates that rsync can't find the directories
  I want to sync.

  2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 
873
  2020/07/18 11:00:01 [5786] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5786] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5786] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5794] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5794] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync allowed access on module Bin_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5794] rsync: [Receiver] chroot /home/cliff/Bin failed: 
No such file or directory (2)
  2020/07/18 11:00:01 [5795] name lookup failed for 192.168.1.159: Name or 
service not known
  2020/07/18 11:00:01 [5795] connect from UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync allowed access on module Drawings_dir from 
UNKNOWN (192.168.1.159)
  2020/07/18 11:00:01 [5795] rsync: [Receiver] chroot /home/cliff/Drawings 
failed: No such file or directory (2)

  Dropping back to Ubuntu 20.04 and rsync works again.  The rsync update
  was install 7/18.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: rsync 3.2.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 23 10:28:17 2020
  InstallationDate: Installed on 2020-07-06 (16 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.rsync: 2020-07-06T11:31:56.141217

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1888685/+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

< 1 2 3 4 5 6 7 8 9 10 >

301 - 400 of 18301 matches

Mail list logo