[Bug 1701788] Re: /usr/bin/plasmashell debug symbols are not provided by plasma-workspace-dbgsym

2022-04-10 Thread Jonathan Watts
Since the problem is with `plasma-workspace-dbgsym`, how would the
availability of `plasma-workspace-dev` affect this issue?

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

Title:
  /usr/bin/plasmashell debug symbols are not provided by plasma-
  workspace-dbgsym

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1701788/+subscriptions


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

[Bug 1894991] Re: Unable to boot with kernels 5.4.0-45 or 5.4.0-47

2020-09-10 Thread Jonathan Watts
*** This bug is a duplicate of bug 1894378 ***
https://bugs.launchpad.net/bugs/1894378

** This bug has been marked a duplicate of bug 1894378
   Cannot boot after updating kernel to version 5.4.0-45

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

Title:
  Unable to boot with kernels 5.4.0-45 or 5.4.0-47

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

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

[Bug 1894991] Re: Unable to boot with kernels 5.4.0-45 or 5.4.0-47

2020-09-09 Thread Jonathan Watts
** Summary changed:

- Unable to boot with kernels 5.4.0.45 or 5.4.0.47
+ Unable to boot with kernels 5.4.0-45 or 5.4.0-47

** Description changed:

  When trying to boot either of the 2 kernel versions above, the computer
  displays the "Kubuntu" logo for a minute or so, then goes to a text
  "(initramfs)" prompt.  It appears to be unable to see my SSD correctly
  (despite grub just loading from it!), as "ls /dev" shows only "nvme0",
  not "nvme0n1".
  
- The last working kernel version for me is 5.4.0.42.
+ The last working kernel version for me is 5.4.0-42.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-42-generic 5.4.0-42.46
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  jonathan   1405 F pulseaudio
-  /dev/snd/pcmC0D7p:   jonathan   1405 F...m pulseaudio
-  /dev/snd/controlC1:  jonathan   1405 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  jonathan   1405 F pulseaudio
+  /dev/snd/pcmC0D7p:   jonathan   1405 F...m pulseaudio
+  /dev/snd/controlC1:  jonathan   1405 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Sep  9 07:00:44 2020
  InstallationDate: Installed on 2019-04-19 (508 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  IwConfig:
-  lono wireless extensions.
-  
-  enp37s0   no wireless extensions.
+  lono wireless extensions.
+ 
+  enp37s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  LANGUAGE=en_US:en_GB
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US:en_GB
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=dac14ca1-9a81-4be6-ab89-e46dfa7c4a15 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-5.4.0-42-generic N/A
-  linux-backports-modules-5.4.0-42-generic  N/A
-  linux-firmware1.187.3
+  linux-restricted-modules-5.4.0-42-generic N/A
+  linux-backports-modules-5.4.0-42-generic  N/A
+  linux-firmware1.187.3
  RfKill:
-  
+ 
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: A320M-HDV R4.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd11/22/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

Title:
  Unable to boot with kernels 5.4.0-45 or 5.4.0-47

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

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

[Bug 1894991] [NEW] Unable to boot with kernels 5.4.0-45 or 5.4.0-47

2020-09-09 Thread Jonathan Watts
Public bug reported:

When trying to boot either of the 2 kernel versions above, the computer
displays the "Kubuntu" logo for a minute or so, then goes to a text
"(initramfs)" prompt.  It appears to be unable to see my SSD correctly
(despite grub just loading from it!), as "ls /dev" shows only "nvme0",
not "nvme0n1".

The last working kernel version for me is 5.4.0-42.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jonathan   1405 F pulseaudio
 /dev/snd/pcmC0D7p:   jonathan   1405 F...m pulseaudio
 /dev/snd/controlC1:  jonathan   1405 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Sep  9 07:00:44 2020
InstallationDate: Installed on 2019-04-19 (508 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
IwConfig:
 lono wireless extensions.

 enp37s0   no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=en_US:en_GB
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=dac14ca1-9a81-4be6-ab89-e46dfa7c4a15 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-42-generic N/A
 linux-backports-modules-5.4.0-42-generic  N/A
 linux-firmware1.187.3
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: A320M-HDV R4.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd11/22/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug focal

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

Title:
  Unable to boot with kernels 5.4.0-45 or 5.4.0-47

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

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

[Bug 1701788] Re: /usr/bin/plasmashell debug symbols are not provided by plasma-workspace-dbgsym

2019-05-21 Thread Jonathan Watts
Encountered the same situation...getting a recurring crash in
plasmashell under Kubuntu 19.04 (but only when I've left the computer
unattended for hours; it's never occurred when I'm sitting at the
terminal).  Crash handler told me which debug symbols I needed for a
useful bug report, so I found the appropriate packages and installed all
of them (including 'plasma-workspace-dbgsym' for
'/usr/bin/plasmashell'), but the crash handler still claims I am missing
debug symbols for '/usr/bin/plasmashell'.

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

Title:
  /usr/bin/plasmashell debug symbols are not provided by plasma-
  workspace-dbgsym

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1701788/+subscriptions

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

[Bug 1787861] Re: Displays not detected/positioned correctly when disconnected/reconnected

2018-08-21 Thread Jonathan Watts
I really hate intermittent bugs.  The previous two times (before just
now) that I turned the AV receiver & TV back on, everything reverted to
normal (VGA-0 off, HDMI-0 on at 1920x1080 60 hz at 0x0, DVI-D-0 offset
to 1920x0).  However, just now, turning the AV receiver & TV on resulted
in:  VGA-0 on, 1024x768 at 2944x0; HDMI-0 on, 1920x1080 60 hz at 0x0;
DVI-D-0 on, 1920x1080 at 1920x0.

However, just running 'xrandr > xrandr.output3' (i.e., just outputting
the current xrandr state to a text file) caused the monitors to reset to
the correct values (although 'xrandr.output3' still showed the incorrect
values).  Running 'xrandr' again showed the correct values.

I will try to install the latest upstream kernel this weekend and see if
that makes any difference.

** Attachment added: "xrandr output after turning HDMI accessories back on 
(failed to restore previous settings)"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787861/+attachment/5178982/+files/xrandr.output3

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

Title:
  Displays not detected/positioned correctly when
  disconnected/reconnected

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

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

[Bug 1787861] Re: Displays not detected/positioned correctly when disconnected/reconnected

2018-08-20 Thread Jonathan Watts
Added 'xrandr' output after the AV Receiver and TV are turned off--note
that VGA-0 has turned itself on, which shouldn't happen.

** Attachment added: "xrandr output after turning of HDMI accessories"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787861/+attachment/5178199/+files/xrandr.output2

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

Title:
  Displays not detected/positioned correctly when
  disconnected/reconnected

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

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

[Bug 1787861] [NEW] Displays not detected/positioned correctly when disconnected/reconnected

2018-08-19 Thread Jonathan Watts
Public bug reported:

I just upgraded from Ubuntu 16.04 LTS to 18.04 LTS.  Previously, this
was all working correctly:  I have 3 displays connected to an nVidia GT
730.  VGA-0 (an old 21-inch CRT) is never enabled (just haven't got
around to removing it).  DVI-D-0 is the primary display, always
connected and turned on, in 1920x1080 60hz.  HDMI-0 is a secondary
display (actually, linked to my AV receiver and then to my 55" HDTV),
and it is turned on when I want the big screen (1920x1080 60hz,
positioned to the left of the primary), turned off the rest of the time.

Now, whenever I turn off my secondary HDMI display, my third (VGA)
display is automatically enabled.  Furthermore, when I then turn the
secondary display back on, it is set to the wrong mode (interlaced at 30
Hz instead of progressive scan at 60 Hz) and in the wrong position (to
the right of the main display, when I want it to the left).  Running the
correct 'xrandr' command to reset all three displays to the correct
conditions instead results in random behavior--instead of a 3840x1080
screen, with the primary display offset to +1920x0, I usually end up
with both displays set to span the entire 3840x1080 area, offset to +0x0
(so they're mirroring each other).  Sometimes the VGA display remains
turned on with a random (not actually displayable) resolution, sometimes
it does not.  Trying to force the displays into the correct mode with
further 'xrandr' commands does not work; I have to reboot the machine to
get the displays back to where they belong.

This is the 'xrandr' command that SHOULD reset the displays to the
correct modes/positions (the primary DVI display is already in the
correct mode, so I don't specify that):  xrandr --output VGA-0 --off
--output DVI-D-0 --primary --output HDMI-0 --size 1920x1080 --rate 60
--left-of DVI-D-0

Occasionally, it does work correctly, but most of the time, it does not
(see above).

Under 16.04 LTS, I did have an issue for a long time where the secondary
HDMI display would be set to an interlaced mode when I turned it back on
(but otherwise, everything was correct--and a simple 'xrandr -output
HDMI-0 --auto' fixed it); that problem was corrected with a kernel
upgrade a short time ago (maybe 3 months?--unfortunately, I never filed
a bug and just lived with it, so I'm not sure exactly when the problem
went away, either).

Attached is the output of 'xrandr' with everything set correctly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  jonathan   2183 F pulseaudio
 /dev/snd/controlC1:  jonathan   2183 F pulseaudio
 /dev/snd/controlC0:  jonathan   2183 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Aug 19 15:38:09 2018
HibernationDevice: RESUME=UUID=e0d7d646-78bf-474b-916a-ad6f8523c1b5
InstallationDate: Installed on 2015-08-17 (1098 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: System manufacturer System Product Name
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=2cd20c22-0c69-4ae2-b81c-11fd8501a2ec ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-32-generic N/A
 linux-backports-modules-4.15.0-32-generic  N/A
 linux-firmware 1.173.1
RfKill:
 
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-15 (4 days ago)
dmi.bios.date: 06/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0307
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88T-M LE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0307:bd06/14/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88T-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic display multimonitor xrandr

** Attachment added: "'xrandr' output with correct modes & positions"
   
https://bugs.launchpad.net/bugs/1787861/+attachment/5177693/+files/xrandr.output

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

Title:
  Displays not detected/positioned correctly 

[Bug 1604090] Re: package dovecot-core 1:2.2.22-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-10-06 Thread Jonathan Watts
I just got this error while installing upgrades, but I'm pretty sure
it's because I never actually got around to configuring dovecot after
installing it initially.

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

Title:
  package dovecot-core 1:2.2.22-1ubuntu2 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/dovecot/+bug/1604090/+subscriptions

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


[Bug 74664] Re: Boot parameters not passed to init scripts

2006-12-09 Thread Jonathan Watts
I can confirm this bug.  It's causing problems with my dual boot setup
(native Kubuntu or Kubuntu under coLinux on WinXP), as I was relying on
passing a COLINUX variable to my colinux script so I can use the correct
set of config files (fstab, network/interfaces, etc.).

** Changed in: upstart (Ubuntu)
   Status: Unconfirmed = Confirmed

-- 
Boot parameters not passed to init scripts
https://launchpad.net/bugs/74664

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