primordic/IssueDupesLite huggingface dataset:
Repository: pocoproject/poco

Issue #990: Potential race condition in `Poco::File` on Windows
Created: 2015-10-16T15:28:50Z
I recently watched a CppCon talk where the speaker said that to delete a directory tree on Windows, one should first rename files to a random name in %TEMP%, then delete.
I noticed that Poco::File::remove(bool recursive) is using the same algorithm on both UNIX and Windows.
https://github.com/pocoproject/poco/blob/develop/Foundation/src/File.cpp#L262
https://github.com/pocoproject/poco/blob/develop/Foundation/src/File_UNIX.cpp#L368
https://github.com/pocoproject/poco/blob/develop/Foundation/src/File_WIN32.cpp#L305
The Windows algorithm should be changed to avoid this potential data race.

Duplicate issue #1479: poco directory remove bug
Created: 2016-11-03T11:02:51Z
poco::File remove() if directory is so deep, delete directory will talk error: directory is not empty

Closing comment (2016-11-03T13:44:02Z): Duplicate of #990
Repository: pocoproject/poco

Issue #1236: Remove Poco::Data::Row::checkEmpty() as it prevents Row from being used with all NULL rows
Created: 2016-04-11T08:27:29Z
Since rows that contain all NULL values can happen in real life, the calls to checkEmpty() in addSortField() and removeSortField() seriously affect usability of Row, especially for iterating over RecordSets. Removing the check does not seem to have any consequences, as this is only used when comparing rows using operator < ().
There don't seem to be any issues with all null Row values, except if sorting (operator <()) is used, e.g. inserting a Row into a std::setPoco::Data::Row. Attempting to add a Row containing all null values to a std::setPoco::Data::Row will result in an Poco::InvalidAccessException() in operator < ().

Duplicate issue #1242: Poco::Data::RowFormatter generate exception if the first column of first row is null
Created: 2016-04-15T11:18:04Z
Poco::Data::RowFormatter generate exception if the first column of first row is null.
Can reproduce the error using the following code:

//
//
// To build: clang++ -I/usr/local/include -L/usr/local/lib  -o test main.cpp -lPocoFoundation -lPocoData -lPocoDataSQLite
//
//


#include<iostream>

#include<Poco/Data/Session.h>
#include<Poco/Data/SQLite/Connector.h>
#include<Poco/Data/RecordSet.h>
#include<Poco/Data/Statement.h>
#include<Poco/Exception.h>

using Poco::Data::Keywords::now;

int main()
{
  int stage=0;

  try
  {
    Poco::Data::SQLite::Connector::registerConnector();
    Poco::Data::Session session(Poco::Data::SQLite::Connector::KEY,":memory:");

    stage=1;
    session<<"create table Abc( a text, b text);", now;

    stage=2;
    //session<<"insert into Abc(a,b) values('Hello','world');",now;
    session<<"insert into Abc(a,b) values(null,'world');",now;
    session<<"insert into Abc(a,b) values('Hello','world');",now;

    stage=3;
    Poco::Data::Statement statement(session);

    stage=4;
    statement<<"select a,b from Abc;",now;

    stage=5;
    Poco::Data::RecordSet recordSet(statement);

    stage=6;
    // Will generate exception if the first column of first row is null.
    std::cout<<recordSet;
    // Will see from the console:
    // Exception at stage 6:
    // Illegal state: All values are empty.
  }
  catch(Poco::Exception &e)
  {
    std::cout<<"Exception at stage "<<stage<<":"<<std::ends;
    std::cout<<e.displayText()<<std::ends;
  }

  return 0;
}

Closing comment (2016-04-15T14:22:40Z): I can confirm that it's related to #1236. The fix for #1236 also solves this issue.
Repository: pop-os/cosmic

Issue #314: App grid takes up most of screen at 1366x768 resolution
Created: 2022-02-21T12:21:26Z
I'm sorry but this problem return in the last update :(

Originally posted by @rickm00 in #264 (comment)

Duplicate issue #334: Wrong size of the application menu
Created: 2022-04-26T19:39:07Z
There is a problem with the application menu, in some others resolutions of the screen the applications menu is proportionate, but in the resolution 1366x768 (16:9) it is not and does not enter the screen, this is a screenshot:

Closing comment (2022-04-26T19:55:51Z): Duplicate of #314
Repository: pop-os/cosmic

Issue #141: [Feature] Keyboard navigation in Workspaces view
Created: 2021-07-07T14:57:16Z
Since we have disabled searching by typing in the Workspaces view, it would be possible to add things like hjkl bindings for switching workspaces.
Seems like something worth exploring.

Duplicate issue #48: Workspaces overview: should up and down arrows change workspaces?
Created: 2021-05-24T15:08:17Z
Binding different hotkeys in different views might require some pretty big modifications to Gnome, but I think being able to look through my workspaces with my arrow keys (maybe also J and K?) while I'm in the workspaces overview. PgUp/PgDn currently do what I'm referring to though, so maybe that's good enough?

Closing comment (2021-07-26T21:54:26Z): Binding different hotkeys in different views might require some pretty big modifications to Gnome

Luckily this doesn't seem to be too difficult.
I don't recall seeing this issue earlier, but I guess it's much the same as #141. I think I'll close it since that is more general (also posing the question of whether other bindings might be useful).
Repository: pop-os/cosmic

Issue #65: Using the show applications button on dock while in the workspaces menu takes it back to the desktop.
Created: 2021-06-05T06:07:12Z

Duplicate issue #164: Unexpected behaviour with "Show Applications" icon in dock.
Created: 2021-07-19T18:59:12Z
When the workspaces view is open and you click on "Show Applications", workspaces view gets closed and you go back to the desktop. It is the same behaviour you would expect by clicking on "Show Applications" while already in applications.
Here is how I can reproduce it:

Activate "Show Applications Icon in Dock" option under settings
Open workspaces view and click on "Show Applications" in the dock.
Applications will not open and instead you will return to desktop.

Expected behaviour is that it would show applications.

Closing comment (2021-07-19T19:38:37Z): duplicate of #65
Repository: pop-os/cosmic

Issue #314: App grid takes up most of screen at 1366x768 resolution
Created: 2022-02-21T12:21:26Z
I'm sorry but this problem return in the last update :(

Originally posted by @rickm00 in #264 (comment)

Duplicate issue #316: Application launcher and some additional suggestions
Created: 2022-03-08T05:24:15Z
Application launcher takes more space so i cant access work spaces properly
*allow work spaces  to be accessed with application launcher when pressing (super+a) and allow launcher to open in overview so it would be easy to shift application from the launcher itself.

*

Closing comment (2022-07-11T18:31:20Z): I think this is a duplicate of #314
We can reopen if I'm mistaken

Ah, my bad
I remember searching for "too big" and "size" not yielding results, so I opened another issue
Thanks for clearing me up! 👍
Repository: pop-os/cosmic

Issue #300: [bug] Keyboard shortcut `Super`+`Alt`+`Up` twice summons a broken version of the old Applications picker
Created: 2022-01-19T16:15:45Z
Pressing this key combo once takes me to the Workspaces view. Pressing it again keeps the workspace picker visible, but displays application icons. I'm not sure what the key combo is supposed to do, but we probably don't want it doing this.

Duplicate issue #339: Pressing Super + Alt + Up keys twice brings up the default GNOME apps library
Created: 2022-05-05T02:01:27Z
Distribution: Pop!_OS 22.04 LTS
Related Application and/or Package Version: gnome-shell v42
Issue/Bug Description: When you press Super + Alt + Up once, it brings up the workspaces menu. If you press it again, it will open up old GNOME apps library, instead of the Pop_OS default "Show Applications" app.
Steps to reproduce:

Press Super + Alt + Up keys
On workspaces screen, press Super + Alt + Up keys again

Expected behavior:

Do nothing, OR
Open the "Show Applications" Pop_OS app.

Closing comment (2022-05-05T15:04:59Z): Duplicate of #300
Repository: pop-os/cosmic

Issue #264: Applications library: better support for smaller resolutions
Created: 2021-12-15T06:58:47Z
I tried installing Pop OS 21.10 on my laptop, but when I open the Applications Menu the size is large and different from Release Image, how do I fix it? My resolution is 1366x768
On My PC

Release Image

Duplicate issue #273: Cosmic applicatins  launcher doesn't adapt to the resolution screen
Created: 2021-12-20T19:33:34Z
The application launcher doesn't adapt in other monitors and display resolution, for example laptops and PC Desktopa

Closing comment (2021-12-21T15:48:18Z): Thanks for the info. Closing as a duplicate of #264
Repository: pop-os/cosmic

Issue #110: [Feature Request] Make workspace gestures respect "natural scrolling"
Created: 2021-07-01T14:36:17Z
Hi,
currently the gestures to switch the workspace work like this:

swipe down: change to the workspace below, i.e. the current workspace will animate upwards out of view
and vice versa

For basic scrolling there is already a toggle in the "Mouse & Touchpad" settings to use "natural scrolling", which I personally find more natural to use with a touchpad.
Maybe the gestures to change the workspace could respect that setting, too?

Duplicate issue #248: Adjust 4-finger swipe up and down to accomodate natural scrolling
Created: 2021-11-24T22:45:51Z
When enabling the Natural Scrolling option, the four-finger swipe up and down gestures don't change.
Expected behavior:

Default scrolling: Swipe down goes to next desktop, scrolling the screen upward in the process
Natural scrolling: Swipe down goes the previous desktop, scrolling the screen downward in the process

Actual behavior:
Regardless of natural scrolling configuration, swipe down always goes to the next desktop (as in, it scrolls the screen upward to go to a desktop sitting below the current desktop). This is a little confusing with natural scrolling enabled as it seems to be backward compared to everything else. COSMIC should check/watch the value of org.gnome.desktop.peripherals.touchpad.natural-scroll and reverse the actions of GESTURE_UP and GESTURE_DOWN according to the setting.

Closing comment (2021-11-29T15:37:20Z): Thank you for the report! I'm closing it as a duplicate of #110. In that issue, I also posted a workaround which you can use to fix it until a fix becomes available.
Repository: pop-os/cosmic

Issue #137: Notifications cut off when date and time set to left
Created: 2021-07-06T02:06:58Z
I set Settings->General-> Date & Time Notification Position to Left.
The notifications now get cut off by the left edge of the screen as they are centred under the date and time.

Duplicate issue #203: Notifications cut off if clock is set to left side and dock is set to right side
Created: 2021-08-26T12:36:14Z
Distribution:
NAME="Pop!_OS"
VERSION="21.04"
Related Application and/or Package Version:
I don't know.
Issue/Bug Description:
Part of the notification is off the screen.
Steps to reproduce (if you know):
When setting up Pop!_OS, turn off the Applications and Workspaces button (from top bar). And set the Time and date thingy to the left side.
Expected behavior:
The notifications should display properly, and not go off the screen.
Other Notes:

Closing comment (2022-02-07T12:52:30Z): Duplicate of #137 ? This one seems to suggest it's unrelated to the dock position
Repository: pop-os/cosmic

Issue #56: When dock is disabled, don't reserve space for it in Workspaces view
Created: 2021-05-27T15:58:48Z
When the dock is disabled, its space (on whichever edge of the screen it's configured for) is reserved but empty in the Workspaces overview.
Left example:


Right example:


Bottom example (issue doesn't seem to affect the windows vertically):

Duplicate issue #174: Workspace switcher making room for dock even if disabled.
Created: 2021-07-26T18:23:37Z
If the workspace switcher and the dock are on the left side and you turn off the dock in settings (but the extension is still enabled) the switcher makes room for the dock.

Version
pop-cosmic:
Installed: 0.1.0~1627319375~21.04~d22439e
Expected results
Switcher shouldn't make room for the dock.

Closing comment (2021-07-28T14:28:28Z): Duplicate of #56.
Repository: pop-os/cosmic

Issue #110: [Feature Request] Make workspace gestures respect "natural scrolling"
Created: 2021-07-01T14:36:17Z
Hi,
currently the gestures to switch the workspace work like this:

swipe down: change to the workspace below, i.e. the current workspace will animate upwards out of view
and vice versa

For basic scrolling there is already a toggle in the "Mouse & Touchpad" settings to use "natural scrolling", which I personally find more natural to use with a touchpad.
Maybe the gestures to change the workspace could respect that setting, too?

Duplicate issue #59: Conflict between touchégg gestures and those of default gnome in wayland on non-gtk windows. 
Created: 2021-05-28T08:23:41Z

Closing comment (2021-07-20T18:23:39Z): This is a duplicate of #110. Even though this one was filed first, that issue seems to have more information, so I'm going to close this one.
Repository: pop-os/pop

Issue #62: Can't right-click current directory in Nautilus List View (when scroll bars are present)
Created: 2017-11-02T19:49:59Z
When in List View in Nautilus I am unable to select the directory I'm currently on.
Example:

Select a directory with a lot of files.
Change to list view and make sure a scrollbar appears
Try to add a new directory to directory you are in using the right-click.

Duplicate issue #2106: Can't rightclick in file manager list view
Created: 2021-12-22T19:08:32Z
Distribution: 21.10
Related Application: Files
Issue/Bug Description: When using the list view and files fill the entire window, there is no empty spot to right click and get the folder-related context menu with "New Folder", "Open in Terminal" etc.
Steps to reproduce:

Switch Files to use the list view.
Open a folder with enough files to fill the whole window.
Try to open the folder-related context menu.

Expected behavior: It should only bring up the file-related context menu when right clicked near the file name or icon. Any other empty spot should bring up the folder-related context menu.
Other Notes: It works as expected in grid view.

Closing comment (2021-12-22T19:38:44Z): I'm closing this as a duplicate of #62 and will post the same info there.
Repository: pop-os/pop

Issue #2487: Sound not working
Created: 2022-06-23T05:28:51Z
sound card on my laptop is realtek alc298.
Cat /etc/os-release:
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Describe issue:
Sound does not work on internal laptop speakers. laptop is samsung galaxybook pro 360 13.3" with core i7 1165g7
sound card is realtek alc298
Sound settings shows tiger lake-LP smart sound technology audio controller
sound settings shows appropriate output fluctuations from videos and music, but no sound reaches speakers.
to reproduce: install pop_os on laptop and try running sound from onboard speakers.
expected behavior:
sound should play from built in speakers.
Other Notes:
sound works perfectly through connected bluetooth devices, and through 3.5mm audio jack.
sound is not muted, and alsa mixer has been used to ensure this.

Duplicate issue #2686: Sound Dummy Output after system's previous update
Created: 2022-11-07T12:28:01Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Issue/Bug Description:
After system updates from 03 Nov 2022 my laptop can't recognize all audio devices such as speakers and microphones. There is only  'Dummy Output' in the Output chapter of the Sound Settings tab.
How can I fix it?
Steps to reproduce (if you know):
Expected behavior:
Get my sound back
Other Notes:

Closing comment (2022-11-07T16:49:45Z): I believe this is a duplicate of #2487
If so, kernel 6.0.6 should fix the problem.
Repository: pop-os/pop

Issue #2182: Firefox doesn't open correctly
Created: 2022-01-21T10:06:56Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="21.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.10"
VERSION_ID="21.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=impish
UBUNTU_CODENAME=impish
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
firefox:
Installed: 96.0+build2-0ubuntu0.21.10.1
Candidate: 96.0+build2-0ubuntu0.21.10.1
Version table:
*** 96.0+build2-0ubuntu0.21.10.1 500
500 http://us.archive.ubuntu.com/ubuntu impish-security/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
100 /var/lib/dpkg/status
93.0+build1-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
Issue/Bug Description:

Click on Firefox
Firefox opens but doesn't render correctly - shows a double top bar
See image - note the double top bar - one is belonging to pop and the other is firefox



Steps to reproduce (if you know):
Expected behaviour:
Firefox should start and work correctly
Other Notes:
Firefox is unusable - I have tried resetting Gnome with ALT and F2 and then entering r.  I have to log out and log back in or sometimes even have to restart the laptop

Duplicate issue #2231: Firefix not opening properly
Created: 2022-02-24T04:17:58Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="21.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.10"
VERSION_ID="21.10"
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
firefox:
Installed: 97.0+build2-0ubuntu0.21.10.1
Candidate: 97.0+build2-0ubuntu0.21.10.1
Version table:
*** 97.0+build2-0ubuntu0.21.10.1 500
500 http://us.archive.ubuntu.com/ubuntu impish-security/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
100 /var/lib/dpkg/status
Issue/Bug Description:
When opening Firefox it does not always render properly. Only a kind of frame that duplicates the desktop background appears. It is not possible to interact with the frame, but it disappears when Firefox is closed via the dock. Firefox will open normally after several attempts.
Steps to reproduce (if you know):
Open Firefox.
Expected behavior:
Firefox open normally.
Other Notes:
This is happening with Librewolf as well
librewolf:
Installed: 97.0.1-1
Candidate: 97.0.1-1
Version table:
*** 97.0.1-1 500
500 http://deb.librewolf.net impish/main amd64 Packages
100 /var/lib/dpkg/status

Closing comment (2022-02-24T16:21:45Z): duplicate of #2182
Repository: pop-os/pop

Issue #409: Keyboard shortcut settings being ignored at random
Created: 2019-01-11T22:48:43Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.10"
VERSION_ID="18.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
keyboard shortcuts
Issue/Bug Description:
I set a new keyboard shortcut for view split left and view split right, it works for a while. Randomly, one of them will just stop working and I have to reset it.

Steps to reproduce (if you know):
Set the shortcut and go about your business, sometimes it happens after rebooting.
Expected behavior:
Keyboard shortcut that is set triggers the corresponding action
Other Notes:

Duplicate issue #796: keyboard shortcuts for split view not woeking after modification
Created: 2019-12-24T15:50:37Z
Distribution (run cat /etc/os-release):
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Pop!_OS 19.10"
NAME="Pop!_OS"
VERSION="19.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.10"
VERSION_ID="19.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=eoan
UBUNTU_CODENAME=eoan
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Issue/Bug Description:
I've just changed the default keyboard shortcut for splitting views from Ctrl + Supr + arrow key to Supr + arrow keys.
Toggle maximization state (Supr + up):  works fine
Restore window (Supr + down): works fine
View split on left (Supr + left): not working (the window doesn't move at all)
View split on right (Supr + right): not working the window doesn't move at all)
Steps to reproduce (if you know):
Expected behavior:
View split on left (Supr + left): should move the window to the left and take half of the space
View split on right (Supr + right): nshould move the window to the right and take half of the space
Other Notes:

Closing comment (2019-12-24T16:58:36Z): Duplicate of #409
Repository: pop-os/pop

Issue #41: Display Settings Doesn't Show Apply Button on Load
Created: 2017-10-31T16:07:14Z
From @skulkingfox on October 1, 2017 0:55
If this is a bug, please use the template below. If this is a feature request, question, or a general discussion topic - please post on our subreddit https://reddit.com/r/pop_os - as that is the proper forum for those types of posts.
Issue/Bug Description
When in the Display Settings with multiple monitors using the Join Displays tab changing the position of the monitors and/or changing the primary monitor does not cause the Apply button to appear. You have to swap to another displays option tab (like mirror) for the apply button to appear, then swap back, redo the changes you want and then hit apply.
At this point, the changes save/apply and all is well.

Copied from original issue: pop-os/iso#109

Duplicate issue #6: [DUPLICATE]Unable apply changes to external monitor scale.
Created: 2017-10-31T15:39:15Z
From @jgreat on October 23, 2017 18:0
If this is a bug, please use the template below. If this is a feature request, question, or a general discussion topic - please post on our subreddit https://reddit.com/r/pop_os - as that is the proper forum for those types of posts.
Reporter info
* Distribution - (run ```cat /etc/os-release```)
NAME="Pop!_OS"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 17.10 (Artful Aardvark)"
VERSION_ID="17.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com/"
BUG_REPORT_URL="https://github.com/system76/pop-distro/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful

 
 * Related Application and/or Package Version - Not sure, what is the setting package 

Issue/Bug Description
Just changing the scale on external monitor doesn't show "Apply" button
Steps to reproduce (if you know)
Open up settings -> Devices -> Displays
Select external monitor
Only change the scale (100 to 200)
Screen doesn't scale and no Apply button shows up.

Expected behaviour
Screen scales or apply button is shown.
Other Notes
Copied from original issue: pop-os/iso#185

Closing comment (2017-10-31T16:35:06Z): Appears to be a duplicate of #41
Repository: pop-os/pop

Issue #1178: nvidia proprietary driver does not work in 20.01 media
Created: 2020-08-05T13:40:43Z
Distribution (run cat /etc/os-release):
20.01 Nvidia
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Nvidia driver does not work. System runs at 640x480 resolution on GTX 580, probably as result of using the fallback modesetting or VESA driver
Issue/Bug Description:
The screen resolution is very low (nearly unusuable) during installation, and Nvidia driver does not work on GTX 580
Steps to reproduce (if you know):
Boot 20.01 live media
Expected behavior:
Nvidia driver works and screen is running at a usable resolution
Other Notes:
I was able to bumble my way through the installation (lots of tabbing and guessing). The graphics issue persists from the live image to the installed os. Issue can be fixed by manually installing the latest Nvidia proprietary driver after OS installation is complete.

Duplicate issue #1177: disk error during installation
Created: 2020-08-05T13:34:41Z
Distribution (run cat /etc/os-release):
20.01
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
installer
Issue/Bug Description:
Installer throws a storage error during installation.
Steps to reproduce (if you know):
Boot the Nvidia live media
Expected behavior:
OS installation completes successfully
Other Notes:
Issue can be remediated by forcibly killing the installer, running a full update, then restarting the installer

Closing comment (2020-08-12T14:43:59Z): There is not currently a text mode for the installer. We would need the installer.log file to see what caused the installation to fail, but this otherwise seems like a duplicate of #1178.
If the built-in NVIDIA driver in the NVIDIA iso doesn't work well, I would try using the Intel/AMD driver instead, since it will use the open-source Nouveau driver, and Nouveau sometimes works better on older cards than it does on newer ones. You may need to press "e" at the initial "Try or Install Pop!_OS" screen and add nouveau.modeset=0 to the end of the kernel options before booting.
Glad to hear you were able to get a working driver installed from NVIDIA's website.
Repository: pop-os/pop

Issue #2487: Sound not working
Created: 2022-06-23T05:28:51Z
sound card on my laptop is realtek alc298.
Cat /etc/os-release:
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Describe issue:
Sound does not work on internal laptop speakers. laptop is samsung galaxybook pro 360 13.3" with core i7 1165g7
sound card is realtek alc298
Sound settings shows tiger lake-LP smart sound technology audio controller
sound settings shows appropriate output fluctuations from videos and music, but no sound reaches speakers.
to reproduce: install pop_os on laptop and try running sound from onboard speakers.
expected behavior:
sound should play from built in speakers.
Other Notes:
sound works perfectly through connected bluetooth devices, and through 3.5mm audio jack.
sound is not muted, and alsa mixer has been used to ensure this.

Duplicate issue #2679: "Dummy Output" as the audio output.
Created: 2022-11-04T10:34:29Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os
Issue/Bug Description:
After recent system updates I've "lost" built-in audio.
"Dummy Output" as the audio output.
inxi -A
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio
    driver: sof-audio-pci-intel-tgl
  Sound Server-1: ALSA v: k6.0.3-76060003-generic running: yes
  Sound Server-2: PipeWire v: 0.3.59 running: yes

lspci -nnk | grep -A2 Audio
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
	Subsystem: Dell Tiger Lake-LP Smart Sound Technology Audio Controller [1028:0a7c]
	Kernel driver in use: sof-audio-pci-intel-tgl
	Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

uname -r
6.0.3-76060003-generic

systemctl --user status pipewire
Started PipeWire Multimedia Service.
  mod.rt: RTKit error: org.freedesktop.DBus.Error.InvalidArgs
  mod.rt: could not set nice-level to -11: input-output error

Expected behavior:
Buit-in audio works
Other Notes:
USB headphones have no issues by the way.
Solution from the https://support.system76.com/articles/audio/ does not help.

Closing comment (2022-11-04T14:57:49Z): I think this is a duplicate of #2487. Can reopen if I'm mistaken.
Repository: pop-os/pop

Issue #1786: At low screen resolutions, Applications icons oversized after restart
Created: 2021-07-06T07:04:37Z
Distribution:

NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute

Issue/Bug Description:


I clean installed POP OS 3 times but after some time or some restarts Application icons are oversized in show applications


I'm new to Linux so if I have done some mistakes please help me.


Screenshot is attached below



Thank you

Duplicate issue #1821: [ACER Aspire] The application launcher appears zoomed
Created: 2021-07-20T12:37:40Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="21.04"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.04"
VERSION_ID="21.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
LOGO=distributor-logo-pop-os
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
The problem happens in application launcher
Issue/Bug Description:
The application launcher appears zoomed The application launcher appears zoomed, after a normal start and the bug disappears after a restart
Steps to reproduce (if you know):
Just normal boot and start applications launcher
Expected behavior:
Reboot device
Device information : https://linux-hardware.org/?probe=752b78a545#Logs

Closing comment (2021-07-20T14:06:19Z): Based on the description and the screen resolution indicated by the URL you provided, I'm closing this as a duplicate of #1786. If this is a different issue, please provide a screenshot to demonstrate.
Repository: pop-os/pop

Issue #1850: os-release file isn't available for snap install scripts
Created: 2021-08-03T07:41:10Z
Distribution (run cat /etc/os-release):
Pop_OS! 21.04
Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Zoom snap
Issue/Bug Description:
During snap install, script fails trying to read /etc/os-release, it's symlinked to /etc/pop-os/os-release who's not readable due to apparmor restrictions
Steps to reproduce (if you know):
Just run
snap install zoom-client
Expected behavior:
zoom-client snap install doesn't fail thanks to /etc/os-release who is symlinked to a readable file available for snap install scripts
Other Notes:
See zoom-snap related issue

Duplicate issue #2146: Use hardlink instead of softlink on /etc/os-release
Created: 2022-01-03T21:15:10Z
Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="20.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
LOGO=distributor-logo-pop-os

Issue/Bug Description:
We deliver our software as a SNAP package. On our software we use python-distro to identify different linux distributions. When using this without a SNAP it's working just fine. But inside a SNAP package, we have some trouble accessing the information from /etc/os-release.
It seems only to be an issue on PopOS. We get a permission denied error when reading the os-release file. Some PopOS users reported that using a hardlink instead of a softlinke that points to /etc/pop-os/os-release fixes the issue.
Like so:
sudo mv /etc/os-release /etc/os-release-backup
sudo ln /etc/pop-os/os-release /etc/os-release

We have tried to fix this from our side with the SNAP package, but it seems not possible and they are pointing in the direction of PopOS to resolve this issue.
I would like to ask, if it's maybe possible to change the default to a hardlink so that end-users don't have to mess with this themselfs.
Kind regards,
Bobslept

Closing comment (2022-01-03T21:20:20Z): This seems related to (or a duplicate of) #1850.
Repository: posit-dev/py-shiny

Issue #956: Shiny create needs dir flag
Created: 2024-01-02T21:24:59Z
For writing tests for shiny create we intend to use a temp directory and it would be easy if shiny create allows user to pass a dir or -d flag that user can specify the directory of the app.
The tests will invoke shiny create via the command line/shell to test true E2E and then start the app to check for console errors.
@gshotwell

Duplicate issue #963: Add directory flag to shiny create
Created: 2024-01-03T13:45:19Z
This will help with backwards compatability, and also make testing easier.

Closing comment (2024-01-03T13:46:32Z): Duplicate of #956
Repository: posit-dev/py-shiny

Issue #1166: Should add support for modules with Express syntax
Created: 2024-02-29T22:29:26Z

Duplicate issue #1182: Should add support for writing modules using Shiny Express syntax
Created: 2024-03-04T19:24:35Z

Closing comment (2024-03-04T19:38:48Z): Duplicate of #1166.
Repository: posit-dev/py-shiny

Issue #121: request headers
Created: 2022-04-13T20:39:50Z
Would like to have access to request headers both used during the initial UI load and also associated with the current session.
Originally encountered this when trying to validate that Shiny-Server-Credentials is correctly proxied through Connect, but this applies to any header use.

Duplicate issue #122: support an equivalent to session$user and session$group
Created: 2022-04-13T20:43:09Z
The Shiny-Server-Credentials header can be used to communicate the user name and group membership for the user actively interacting with R+Shiny. It would be helpful to have the same concept, here.
https://github.com/rstudio/shiny/blob/fd7518018cbb2ec0b89960c922e34576d5dbc1e7/R/shiny.R#L760-L766
The JSON has the shape:
{"user":"alice","groups":["admins","people"]}

Closing comment (2022-04-13T20:43:32Z): Related to #121, which asks for more general access to request headers.
Repository: posit-dev/py-shiny

Issue #158: `input_selectize()`/`update_selectize()` should allow for custom selectize.js options
Created: 2022-05-11T20:31:53Z
And some options need to be literal JS code (in R folks currently do this via I()) https://shiny.rstudio.com/articles/selectize.html

Duplicate issue #704: Passing additional options to input.select
Created: 2023-08-24T19:40:00Z
Hi,
Is it possible to pass additional options to input.select? The use case is to allow users to create additional items by passing something similar to R where we do options = list(create = TRUE)
I don't seen an example of the options argument from the R documentation in the python documentation but perhaps I am missing something obvious
     options
     A list of options. See the documentation of selectize.js(https://selectize.dev/docs/usage) for possible options (character 
    option values inside [base::I()](https://rdrr.io/r/base/AsIs.html) will be treated as literal JavaScript code; see 
    [renderDataTable()](https://shiny.posit.co/r/reference/shiny/latest/renderDataTable.html) for details).

thanks a million,
Iain

Closing comment (2023-11-01T14:29:19Z): Duplicate of #158 . Closing here
Repository: posit-dev/py-shiny

Issue #634: Index issues with render.table and render.data_frame
Created: 2023-07-21T12:59:04Z
I ran into a bit of unexpected behaviour rendering data tables. When calculating group-wise statistics in pandas we don't include the grouping column by default in the rendered table unless the user sets index=True. There are two issues with this:

The default for printing pandas tables includes the index, so we should follow that pattern
render.data_frame doesn't seem to have support for printing indexes, or at least follows a different API pattern

from shiny import App, render, ui, reactive
import pandas

import pandas as pd

data = {
    "group": ["A", "A", "B", "B", "A", "B", "A", "B"],
    "value1": [10, 20, 30, 40, 50, 60, 70, 80],
    "value2": [5, 15, 25, 35, 45, 55, 65, 75],
}

df = pd.DataFrame(data)

means_by_group = (
    df.set_index("group")
    .groupby(level="group")
    .agg({"value1": "mean", "value2": "mean"})
)
app_ui = ui.page_fluid(ui.output_table("table"), ui.output_data_frame("df"))


def server(input, output, session):
    @output
    @render.table(index=True)
    def table():
        return means_by_group

    @output
    @render.data_frame()
    def df():
        return means_by_group


app = App(app_ui, server)

Duplicate issue #676: Data frame selected rows intermittently returning None Type
Created: 2023-08-11T14:09:02Z
When selecting the fourth (not the 1-3rd) entry of the data_frame example the row selection produces a None value which causes an error. Weirdly this seems to be specific to that particular entry and persists you reorder or filter the data.

Closing comment (2023-08-11T16:11:34Z): The bug is caused by the index being dropped which seems to be what the data frame relies on for selection. A workaround is to call df.reset_index() after filtering. This is possibly related to #634.
Repository: posit-dev/py-shiny

Issue #1118: Modify data grid to work well with fill/fillable
Created: 2024-02-12T14:14:16Z
Currently dataframes do not look particularly good when they're included in a filling layout. Some things we want to solve:

Data grids should properly fill their parent
When included in  a card it would be nice if the pagination and footers were pushed to the bottom of the card.

Duplicate issue #924: `render.DataGrid()` doesn't fill it's container properly
Created: 2023-12-18T23:48:49Z
The table here should fill the card, but currently doesn't, seemingly because the div.shiny-data-grid needs a html-fill-item class

Closing comment (2024-02-14T00:02:33Z): Duplicate of #1118
Repository: posit-dev/py-shiny

Issue #869: Unhelpful express error message: `Error loading ASGI app. Attribute not found in module "shiny.express.app"`
Created: 2023-12-07T16:58:50Z
At least one way to repro this is to run an app that attempts to import something that doesn't exist in shiny.express.layout
from shiny.express import layout

print(layout.foo)

Duplicate issue #937: In Express mode, an `AttributeError` during `tagify()` results in unhelpful error
Created: 2023-12-22T17:48:06Z
Example:
from shiny.express import input, ui

with ui.nav_panel(title="One"):
    "one"

with ui.sidebar():
    "hello"
Results in this error:
ERROR:    Error loading ASGI app. Attribute "_2f_Users_2f_winston_2f_Projects_2f_py_2d_shiny_2f_examples_2f_express_2f_sidebar_5f_app_2e_py" not found in module "shiny.express.app".

Closing comment (2023-12-23T03:18:02Z): This error happens when an AttributeError is raised when a tagify() method is called on an object in the UI, and Uvicorn specifically looks for AttributeErrors and prints a customized error message.
It's very similar to #869, except that in that case, the AttributeError was raised during the initial evaluation of the code, whereas in this case, the AttributeError is raised later, when tagify() is called.
The running of tagify() happens here:

  
    
      py-shiny/shiny/_app.py
    
    
         Line 390
      in
      1ae8479
    
  
  
    

        
          
           rendered = HTMLDocument(ui_res).render(lib_prefix=lib_prefix)
Repository: posit-dev/py-shiny

Issue #163: Building docs results in `ImportError: no module named shiny` 
Created: 2022-05-17T19:51:36Z
When I build the docs, I see this new error, as of e8764fa (#156):
$ make html
Running Sphinx v4.5.0
loading pickled environment... done
[autosummary] generating autosummary for: index.rst, reference/shiny.App.LIB_PREFIX.rst, reference/shiny.App.SANITIZE_ERRORS.rst, reference/shiny.App.SANITIZE_ERROR_MSG.rst, reference/shiny.App.init_starlette_app.rst, reference/shiny.App.rst, reference/shiny.App.run.rst, reference/shiny.App.stop.rst, reference/shiny.Inputs.rst, reference/shiny.Module.rst, ..., reference/shiny.ui.update_checkbox_group.rst, reference/shiny.ui.update_date.rst, reference/shiny.ui.update_date_range.rst, reference/shiny.ui.update_navs.rst, reference/shiny.ui.update_numeric.rst, reference/shiny.ui.update_radio_buttons.rst, reference/shiny.ui.update_select.rst, reference/shiny.ui.update_slider.rst, reference/shiny.ui.update_text.rst, reference/shiny.ui.update_text_area.rst
Failed to import shiny.ui.tags.
Possible hints:
* KeyError: 'i'
* KeyError: 'shiny'
WARNING: [autosummary] failed to import shiny.App.
Possible hints:
* ImportError: no module named shiny
* KeyError: 'i'
* KeyError: 'shiny'
WARNING: [autosummary] failed to import shiny.App.LIB_PREFIX.
Possible hints:
* ImportError: no module named shiny.App
* KeyError: 'i'
* KeyError: 'shiny'
WARNING: [autosummary] failed to import shiny.App.SANITIZE_ERRORS.
Possible hints:
* ImportError: no module named shiny.App
* KeyError: 'i'
* KeyError: 'shiny'
WARNING: [autosummary] failed to import shiny.App.SANITIZE_ERROR_MSG.
Possible hints:
* ImportError: no module named shiny.App
* KeyError: 'i'
* KeyError: 'shiny'

....

Duplicate issue #308: send_custom_message API reference example isn't working
Created: 2022-08-10T12:48:38Z
send_custom_message method in shiny.Session is not work properly.
I tested it locally and confirm that with the native pyshiny docs as has the same problem.
Please check out the example:
https://shiny.rstudio.com/py/api/reference/shiny.Session.send_custom_message.html#shiny.Session.send_custom_message

Closing comment (2022-08-10T17:36:26Z): It looks like the the only difference between the API reference example, and version in shiny/examples/send_custom_message/app.py is that the selector is "" instead of "<p>". I'm guessing this has to do with escaping when the API docs are generated. (Related to #163, #164)
Repository: posit-dev/py-shiny

Issue #158: `input_selectize()`/`update_selectize()` should allow for custom selectize.js options
Created: 2022-05-11T20:31:53Z
And some options need to be literal JS code (in R folks currently do this via I()) https://shiny.rstudio.com/articles/selectize.html

Duplicate issue #509: Add `options` argument for input_selectize
Created: 2023-05-24T05:32:17Z
I noticed in py-shiny input_selectize doesn't have the options argument. Would be great to have that. Thanks.
https://shiny.posit.co/r/reference/shiny/1.7.4/selectinput

Closing comment (2023-06-05T14:37:37Z): Turns out this is a duplicate of #158
Repository: posit-dev/py-shiny

Issue #1107: `ui.input_task_button` doesn't work inside module
Created: 2024-02-05T17:14:33Z
It seems to me that the freshly introduced input_task_button doesn't work with shiny modules.
The following code:
from shiny import App, module, reactive, render, ui


@module.ui
def button_ui():
    return ui.p(
        # ui.input_task_button("btn", label="Click me!"),
        ui.input_action_button("btn", label="Click me!"),
        ui.output_text("text_counter"),
    )


@module.server
def button_server(input, output, session):
    counter = reactive.Value(0)
    @render.text
    def text_counter():
        return f"Button clicked {counter()} times"
    
    @reactive.effect
    @reactive.event(input.btn)
    def increment_counter():
        counter.set(counter() + 1)


app_ui = ui.page_fluid(
    button_ui("button")
)


def server(input, output, session):
    button_server("button")


app = App(app_ui, server)
Work with ui.input_action_button it works, but with ui.input_task_button I get the following message in the terminal:
INFO:     connection open
_send_error_response: The string 'button-btn' is not a valid id; only letters, numbers, and underscore are permitted
INFO:     connection closed

Am I write, or the input_task_button should be used in a different way?

shiny == 0.7.0, python == 3.10.13

Duplicate issue #1115: ExtendedTask not allowed in modules
Created: 2024-02-09T14:07:30Z
Hi,
I am having issues using an extended task within a module as a result of how module component id's are concatenated.
For example if there is a dashboard page which contains a module with a input_task_button (id = "files_submit"), the id will be
dashboard_page-files_submit

which results in the error :
_send_error_response: The string 'dashboard_page-files_submit' is not a valid id; only letters, numbers, and underscore are permitted

Is this a know issue with a workaround?

Closing comment (2024-02-12T13:47:14Z): I'm pretty certain this is a duplicate of #1107, so I'm going to close the issue. Feel free to reply if they are different issues.
Repository: powerline/powerline

Issue #418: Allow *merging* as opposed to *overwriting* of config [$15 awarded]
Created: 2013-04-10T08:21:08Z
Currently, to make a single small change to any config, one has to replicate the entire config file in ~/.config/powerline. This means that if there are any upstream changes to the config file, they will be ignored in the local installation.
This makes the config files fairly useless. Keeping track of upstream changes and updating your local config files every time something changes is too much effort.
Instead config files should be merged. i.e. base config should be read from the distributed default config files. Then if a user config file exists, it should be merged with the base config instead of replacing it completely.
This will require some changes to the config schema. For example, to allow turning off segments by using a 'display' key instead of checking for their presence.

The $15 bounty on this issue has been claimed at Bountysource.

Duplicate issue #609: vim: empty config.json causes powerline to freak out
Created: 2013-07-24T05:44:13Z
Steps to reproduce:

Get Powerline set up with vim
mkdir -p ~/.config/powerline
echo '{}' > ~/.config/powerline/config.json
Watch the massive tracebacks

What I expected:
Powerline would read in the default/shipped config.json and merge in my changes from ~/.config/powerline (if any).
Notes
I'm only interested in changing a few settings. I want the rest to remain stable with what powerline ships. i.e. I want Lokaltog and company to manage most of my config with one or two overrides.
This also makes experimentation easier as a new user.  Not to mention having to look up vim -u /dev/null config.json as a way to edit a file without using my (now broken) .vimrc.
Ciao!

Closing comment (2013-07-24T06:35:42Z): Duplicate of #418.
24.07.13, 09:44, "Christian Höltje" notifications@github.com":

Steps to reproduce:Get Powerline set up with vimmkdir -p ~/.config/powerlineecho '{}' > ~/.config/powerline/config.jsonWatch the massive tracebacksWhat I expected:
Powerline would read in the default/shipped config.json and merge in my changes from ~/.config/powerline (if any).Notes
I'm only interested in changing a few settings. I want the rest to remain stable with what powerline ships. i.e. I want Lokaltog and company to manage most of my config with one or two overrides.
This also makes experimentation easier as a new user.  Not to mention having to look up vim -u /dev/null config.json as a way to edit a file without using my (now broken) .vimrc.
Ciao!
—
Reply to this email directly or view it on GitHub.