[Bug 1875062] Re: [20.04] Keyboard layout changes during installation before typing username/password

2024-04-15 Thread Dag Bjerkeli
Sorry, it was of course 24.04 I were testing. 24.04 beta and the preview
image was also of 24.04.

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

Title:
  [20.04] Keyboard layout changes during installation before typing
  username/password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions


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

[Bug 1875062] Re: [20.04] Keyboard layout changes during installation before typing username/password

2024-04-15 Thread Dag Bjerkeli
I've just tested this, and can confirm that there is a bug regarding
keyboard layout in 22.04 beta. As this time the error also appears when
you select the keyboard initially it could a new error.

I also have a preview image of 22.04 dated mars 27th that does not have
the error, even after updated installer.


** Attachment added: "Entering æøå after selecting Norwegian keyboard does not 
show correct keys"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+attachment/5765721/+files/not%20norwegian%20in%20install.png

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

Title:
  [20.04] Keyboard layout changes during installation before typing
  username/password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions


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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2022-02-18 Thread Dag Bjerkeli
The ascii flow didn't turn out well. Attaching a PNG that hopefully is
better.


** Attachment added: "3 ways of selecting the language"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+attachment/5561938/+files/Selection%20language%20flow.drawio.png

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions


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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2022-02-18 Thread Dag Bjerkeli
I've done some more testing on the daily images from today and
yesterday. In one sequence I'm able to get correct keyboard throughout
the installation. I've tried to illustrate it with this ASCII flow-chart

Welcome --(NOR)-+
   ||
 (ENG) TRY? --- YES --+
   || |
  TRY  INST  INST
   || |
  INST FAIL  OK
   |
 (NOR)
   |
  FAIL

From welcome screen

1) No language selection, select try ubuntu. From desktop start installation 
and choose Norwegian
2) Select Norwegian go straight to installation
3) Select Norwegian, select try ubuntu. From desktop start installation and 
verify Norwegian

All installations 3rd party and updates were selected. And were done in
vmWare Workstation.

I hope this might be of some help in reproducing the situation.

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1875062/+subscriptions


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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2022-01-20 Thread Dag Bjerkeli
The installation process is at the point where I'm creating user, that
is entering username and password. Noticed that typing Norwegian
characters in name field produces unwanted result.

** Attachment added: "syslog while installing"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+attachment/946/+files/syslog-jammy-desktop-20220120.txt

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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


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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2022-01-20 Thread Dag Bjerkeli
Hi I just tried install of jammy-desktop-amd64.iso (download yesterday) and ran 
into the keybord issue straight away. So I can provide some info:
'locale'
LANG=C.UTF-8
LANGUAGE=
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=


ubuntu@ubuntu:/var/log$ setxkbmap -query
rules:  evdev
model:  pc105
layout: us,us
variant:,
ubuntu@ubuntu:/var/log$ 

syslog attached as file: syslog-jammy-desktop-20220120.txt

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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


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

[Bug 1946196] Re: Additional Drivers fails with pk-client-error-quark: Cannot download packages whilst offline (257)

2021-10-10 Thread Dag Bjerkeli
I ran into this today. My system has packagekit 1.2.2-2ubuntu3, so it
does not look like it is related to bug 1943189.

Since this computer currently is used for testing, I'm in no hurry to
install the NVIDIA drivers so I can do some further testing, if needed.

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

Title:
  Additional Drivers fails with pk-client-error-quark: Cannot download
  packages whilst offline (257)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1946196/+subscriptions


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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2021-03-12 Thread Dag Bjerkeli
I have just tested 20.10 and 20.04.02.
For 20.10 it's OK
For 20.04.02 the bug is still present.

These tests were done on both VMware 16.1 and VirtualBox 6.1 both of
those on same Ubuntu 20.04.02 host.

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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

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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2021-01-18 Thread Dag Bjerkeli
I've conducted a test for some ISO's that I've got:

* Groovy from 8th Oct 2020
* 20.04.01
* 20.10
* Hirsute from 17th Jan 2021

The last three were downloaded 17th Jan.

All versions had correct keyboard layout where one could test the keyboard.
Likewise all installs had correct layout after installation.

But 20.04.01 and Hirsute had incorrect keyboard-layout when username and
password were to be chosen.

The keyboard layout that I tested was Norwegian.

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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

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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2020-10-08 Thread Dag Bjerkeli
I've checked with Norwegian keyboard and settings as I originally did.
And I did not experience the problem described earlier.

I've tested both UTF-8 characters and keyboard layout.

So this appears to be solved.

Good woork!

/dag

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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

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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2020-07-04 Thread Dag Bjerkeli
I've tried groovy-desktop-amd64 downloaded yesterday (July 3rd).

Attempt 1
---
- Did you boot under BIOS or UEFI?
BIOS

- If BIOS, did you select the keyboard from the bootloader (purple screen)?
Not sure what screen this should be.

- Which boot option did you use?
Ubuntu

**Welcome**
   -> Selecting Norsk Bokmål (Norwegian)
   -> Installer Ubuntu (Install Ubuntu)

**Tastaturutforming** (Keyboard layout?)
Testing the keyboard in the input field -> OK Norwegian characters appears as 
they should.

Selecting defaults for remaining screens until **Hvem er du** (Who are you?)
Entering Norwegian keys in the name field gives wrong characters.


Attempt 2
---
Same as Attempt 1. But at the window **Tastaturutforming** I selected
US keyboard
Then Continue
Then Back from the Oppdateringer og annen programvare (Updates and other 
software?) window.
Selecting Norwegian as keyboard layout.

Selecting defaults for remaining screens until **Hvem er du** (Who are you?)
Entering Norwegian keys in the name field gives CORRECT characters.

so I can confirm Gunnar Hjalmarssons observations.

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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

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

Re: [Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2020-06-25 Thread Dag Bjerkeli
I would also need an ISO to start with.

Den 25.06.2020 18:55, skrev Gunnar Hjalmarsson:
> On 2020-06-25 18:24, Brian Murray wrote:
>> There is an updated version of ubiquity (20.04.15.1) in the
>> -proposed pocket which may address this issue. Could you please test
>> it?
> How would you go about doing that? Is there an ISO with that ubiquity
> version somewhere?
>

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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

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

[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password

2020-04-27 Thread Dag Bjerkeli
** Summary changed:

- Incorrect keyboard layout for selecting username and password during install 
of 20.04
+ [20.04] Keyboard layout not enabled immediately during installation when 
typing username/password

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

Title:
  [20.04] Keyboard layout not enabled immediately during installation
  when typing username/password

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

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

[Bug 1875062] [NEW] Incorrect keyboard layout for selecting username and password during install of 20.04

2020-04-25 Thread Dag Bjerkeli
Public bug reported:

During a fresh install of Ubuntu 20.04, selecting Norwegian keyboard is
provided and keys are responding correctly at that stage. But later when
entering user information the keyboard setting is wrong.

It looks like it have fallen back to English keyboard-layout.
I failed to log in after my first install, so a new attempt I tried to write 
some special letters in the name field, and noticed that I got the wrong 
characters for the key.

The install is done i VMware workstation 15.

In the attached screendump, the characters (';[":{) after my name should
have been (æøåÆØÅ) that is norwegian characters.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 25 19:27:41 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
InstallationDate: Installed on 2020-04-25 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: ubiquity
Symptom: installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15

** Attachment added: "partman syslog and screendump from install."
   
https://bugs.launchpad.net/bugs/1875062/+attachment/5360434/+files/attachments.zip

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

Title:
  Incorrect keyboard layout for selecting username and password during
  install of 20.04

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

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

[Bug 1752159] [NEW] package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: underprosessen installerte post-installation-skript returnerte feilstatus 1

2018-02-27 Thread Dag Bjerkeli
Public bug reported:

Did a first time upgrade of an 17.10.1 installation on a PC with encrypted 
disk, and I did
sudo apt update
sudo apt upgrade

PC was rebooted after install.

I had problems connecting to internett during install and the
instructions to enter EFI I was not able to complete.

Additional information:
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: grub-common 2.02~beta3-4ubuntu7.1
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Tue Feb 27 20:53:27 2018
ErrorMessage: underprosessen installerte post-installation-skript returnerte 
feilstatus 1
InstallationDate: Installed on 2018-02-27 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Fila eller mappa finnes ikke: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: grub2
Title: package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: 
underprosessen installerte post-installation-skript returnerte feilstatus 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade:
  underprosessen installerte post-installation-skript returnerte
  feilstatus 1

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

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

[Bug 1726465] Re: package mysql-server-5.7 5.7.20-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2017-11-04 Thread Dag Bjerkeli
Complains about changes in /etc/mysql/mysql.conf.d/mysqld.cnf
Upgrading from 17.04 to 17.10 gave this error. Error also present in during the 
upgrade process.

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

Title:
  package mysql-server-5.7 5.7.20-0ubuntu0.16.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1726465/+subscriptions

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

[Bug 1660316] Re: apparmor denial of CUPS

2017-06-08 Thread Dag Bjerkeli
I finally got to check the status of this on Ubuntu 17.04. Same computer but 
upgraded ubuntu.
Print from LibreOffice gave this in log (dmesg):
[491184.232027] audit: type=1400 audit(1496903835.766:41): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cupsd" pid=21237 comm="lpd" 
capability=12  capname="net_admin"

Applying the workaround resulted in no apperrors in dmesg.

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

Title:
  apparmor denial of CUPS

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

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


[Bug 1660316] Re: apparmor denial of CUPS

2017-05-23 Thread Dag Bjerkeli
Meanwhile I've upgraded the computer to 17.04, but I have not checked
the presence of the bug after the upgrade. I will check tomorrow when I
get access to the computer.

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

Title:
  apparmor denial of CUPS

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

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


[Bug 1660316] Re: apparmor denial of CUPS

2017-01-30 Thread Dag Bjerkeli
This was raised from the C308 printer, which I just had installed. The
C650 was the old printer that we got, and I _think_ printing was working
on that machine.

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

Title:
  apparmor denial of CUPS

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

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


[Bug 1660316] [NEW] apparmor denial of CUPS

2017-01-30 Thread Dag Bjerkeli
Public bug reported:

Printing is enabled when doing sudo aa-complain cupsd

Here is an extract of /var/log/syslog:

Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929457] audit: type=1400 
audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 
comm="apparmor_parser"
Jan 30 12:41:59 dag-TS-P500 kernel: [  868.929744] audit: type=1400 
audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser"
Jan 30 12:41:59 dag-TS-P500 kernel: [  868.945422] audit: type=1400 
audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 
comm="apparmor_parser"
Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817070] audit: type=1400 
audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 
comm="apparmor_parser"
Jan 30 12:42:10 dag-TS-P500 kernel: [  879.817342] audit: type=1400 
audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser"
Jan 30 12:42:10 dag-TS-P500 kernel: [  879.837254] audit: type=1400 
audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 
comm="apparmor_parser"
Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: 
downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: 
Error when getting information for file '/home/dag/.glvndcEQzqA': No such file 
or directory
Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service...
Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 
'org.freedesktop.hostname1'
Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service.
Jan 30 12:42:26 dag-TS-P500 kernel: [  895.746636] audit: type=1400 
audit(1485776546.086:43): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12  capname="net_admin"
Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary 
Directories...
Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary 
Directories.
Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.OneConf'
Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.OneConf'
Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: 
WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file 
or directory: 
'/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts'
Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service 
name='com.ubuntu.sso'
Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 
'com.ubuntu.sso'
Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 
audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 
comm="apparmor_parser"
Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 
audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser"
Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 
audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 
comm="apparmor_parser"
Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 
audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"
Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 
audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12  capname="net_admin"

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: cups 2.2.0-2
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CupsErrorLog: E [30/Jan/2017:12:31:00 +0100] [cups-deviced] PID 6055 
(gutenprint52+usb) stopped with status 1!
Date: Mon Jan 30 13:11:33 2017
InstallationDate: Installed on 2016-02-22 (342 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lpstat:
 device for KONICA-MINOLTA-C650-Series: 

[Bug 1354007] Re: Suspend fails on a Dell XPS 13 laptop

2014-09-15 Thread Dag Bjerkeli
Just tested a new upstream kernel:

# uname -a
Linux dag-XPS-13 3.17.0-031700rc5-generic #201409142135 SMP Mon Sep 15 01:36:30 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Bug still exists.

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

Title:
  Suspend fails on a Dell XPS 13 laptop

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

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


[Bug 1354007] Re: Suspend fails on a Dell XPS 13 laptop

2014-09-01 Thread Dag Bjerkeli
Just tested a new upstream kernel:

 uname -a
Linux dag-XPS-13 3.17.0-031700rc3-generic #201408312235 SMP Mon Sep 1 02:36:10 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Bug still exists.

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

Title:
  Suspend fails on a Dell XPS 13 laptop

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

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


[Bug 1354007] Re: Suspend fails on a Dell XPS 13 laptop

2014-08-14 Thread Dag Bjerkeli
Just tested new upstream kernel:
uname -a
Linux dag-XPS-13 3.16.1-031601-generic #201408140014 SMP Thu Aug 14 04:15:26 
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Bug still exists.

3.5.0-40 still works as expected.

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

Title:
  Suspend fails on a Dell XPS 13 laptop

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

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


[Bug 1354007] Re: Suspend fails on a Dell XPS 13 laptop

2014-08-08 Thread Dag Bjerkeli
Just tested with:
dag@dag-XPS-13:~$ uname -a
Linux dag-XPS-13 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:36:11 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
dag@dag-XPS-13:~$ 

Bug still exists.

** Tags added: kernel-bug-exists-upstream

** 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/1354007

Title:
  Suspend fails on a Dell XPS 13 laptop

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

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


[Bug 1354007] [NEW] Suspend fails on a Dell XPS 13 laptop

2014-08-07 Thread Dag Bjerkeli
Public bug reported:

At one point suspending the computer stopped working. It just goes back
on right away. Monitor goes black a short while but comes back on after
2-3 sec. I'm running Ubuntu 14.04 and I've tested some earlier kernels
that I've got. The latetes that I have where suspend works is 3.5.0-40
and my first that it fails is 3.8.0-42.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dag3107 F pulseaudio
CurrentDesktop: Unity
Date: Thu Aug  7 14:52:13 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20120703-2
HibernationDevice: RESUME=UUID=7d745b67-04ae-4ea5-be75-d96a3a7cfa10
InstallationDate: Installed on 2013-06-22 (410 days ago)
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 
20120703-15:08
MachineType: Dell Inc. XPS L322X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=be1af9d9-106a-4e17-b79d-6865c56cf880 ro acpi_sleep=nonvs quiet splash 
vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic  N/A
 linux-firmware 1.127.5
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-22 (106 days ago)
dmi.bios.date: 08/28/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0PJHXN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: XPS L322X
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug trusty

** Attachment added: wakeup file as described in DebuggingKernelSuspend
   https://bugs.launchpad.net/bugs/1354007/+attachment/4171983/+files/wakeup

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

Title:
  Suspend fails on a Dell XPS 13 laptop

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

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